CN111726390A - Interface data interaction method, device, equipment and storage medium based on Teamcenter - Google Patents
Interface data interaction method, device, equipment and storage medium based on Teamcenter Download PDFInfo
- Publication number
- CN111726390A CN111726390A CN202010373365.4A CN202010373365A CN111726390A CN 111726390 A CN111726390 A CN 111726390A CN 202010373365 A CN202010373365 A CN 202010373365A CN 111726390 A CN111726390 A CN 111726390A
- Authority
- CN
- China
- Prior art keywords
- data
- instruction
- configuration
- teamcenter
- receiving
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Granted
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
- H04L67/00—Network arrangements or protocols for supporting network services or applications
- H04L67/2866—Architectures; Arrangements
- H04L67/30—Profiles
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F9/00—Arrangements for program control, e.g. control units
- G06F9/06—Arrangements for program control, e.g. control units using stored programs, i.e. using an internal store of processing equipment to receive or retain programs
- G06F9/44—Arrangements for executing specific programs
- G06F9/451—Execution arrangements for user interfaces
Landscapes
- Engineering & Computer Science (AREA)
- Software Systems (AREA)
- Theoretical Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Human Computer Interaction (AREA)
- Physics & Mathematics (AREA)
- General Engineering & Computer Science (AREA)
- General Physics & Mathematics (AREA)
- Stored Programmes (AREA)
- Information Retrieval, Db Structures And Fs Structures Therefor (AREA)
Abstract
The invention relates to the field of software engineering, and discloses a Teamcenter-based interface data interaction method, a device, equipment and a storage medium, wherein the method comprises the following steps: receiving a first configuration instruction, and creating a data set according to the first configuration instruction; receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction; receiving a third configuration instruction, and setting an association relation between the data set and the data configuration file according to the third configuration instruction; and acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of a Teamcenter. The invention can realize data interaction between the Teamcenter system and other systems, realize data cascade between multiple systems and enable data outside the Teamcenter system to be in seamless connection with the Teamcenter system.
Description
Technical Field
The invention relates to the field of software engineering, in particular to a Teamcenter-based interface data interaction method and device, computer equipment and a storage medium.
Background
The Teamcenter system provides a complete product life cycle management scheme and is very widely applied. In the Teamcenter system, the values for all attributes can only come from their own database. When a module in the Teamcenter system needs to use data of other systems, data interfaces need to be developed on the two systems at the same time to realize data interaction.
However, developing the data interface generates higher development cost, and increases the development period, and the Teamcenter system data update needs to satisfy the trigger condition, and cannot acquire new data in time.
Disclosure of Invention
Therefore, in order to solve the above technical problems, it is necessary to provide a Teamcenter-based interface data interaction method, device, computer device and storage medium, so as to improve the processing efficiency and processing cost of the Teamcenter system for receiving external data.
A Teamcenter-based interface data interaction method comprises the following steps:
receiving a first configuration instruction, and creating a data set according to the first configuration instruction;
receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction;
receiving a third configuration instruction, and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
and acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of a Teamcenter.
A Teamcenter-based interface data interaction device comprises:
the system comprises a first configuration module, a second configuration module and a data processing module, wherein the first configuration module is used for receiving a first configuration instruction and creating a data set according to the first configuration instruction;
the second configuration module is used for receiving a second configuration instruction and importing a data configuration file matched with the data set according to the second configuration instruction;
the third configuration module is used for receiving a third configuration instruction and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
and the analysis module is used for acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of the Teamcenter.
A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the Teamcenter-based interface data interaction method when executing the computer program.
A computer-readable storage medium, which stores a computer program that, when executed by a processor, implements the aforementioned Teamcenter-based interface data interaction method.
The interface data interaction method, the interface data interaction device, the computer equipment and the storage medium based on the Teamcenter establish a data set according to a first configuration instruction by receiving the first configuration instruction; receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction; receiving a third configuration instruction, and setting an association relation between the data set and the data configuration file according to the third configuration instruction; and acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of a Teamcenter. According to the invention, the data configuration file set outside is configured in the Teamcenter, so that data interaction between the Teamcenter system and other systems is realized; meanwhile, the data configuration file is easy to edit and verify, so that the development of system interfaces can be reduced; the data configuration file also contains the hierarchical relationship of the attributes, so that the cascade of data among multiple systems can be realized, the tight integration among the systems is improved, and the data outside the Teamcenter system is seamlessly connected with the Teamcenter system.
Drawings
In order to more clearly illustrate the technical solutions of the embodiments of the present invention, the drawings needed to be used in the description of the embodiments of the present invention will be briefly introduced below, and it is obvious that the drawings in the following description are only some embodiments of the present invention, and it is obvious for those skilled in the art that other drawings can be obtained according to these drawings without inventive labor.
FIG. 1 is a schematic diagram of an application environment of a Teamcenter-based interface data interaction method according to an embodiment of the present invention;
FIG. 2 is a flow chart of the Teamcenter-based interface data interaction method according to an embodiment of the present invention;
FIG. 3 is a display of results on a user interface of the Teamcenter system in one embodiment of the present invention;
FIG. 4 is a display of results on a user interface of the Teamcenter system in one embodiment of the present invention;
FIG. 5 is a schematic structural diagram of a Teamcenter-based interface data interaction device according to an embodiment of the present invention;
FIG. 6 is a schematic diagram of a computer device according to an embodiment of the invention.
Detailed Description
The technical solutions in the embodiments of the present invention will be clearly and completely described below with reference to the drawings in the embodiments of the present invention, and it is obvious that the described embodiments are some, not all, embodiments of the present invention. All other embodiments, which can be derived by a person skilled in the art from the embodiments given herein without making any creative effort, shall fall within the protection scope of the present invention.
The interface data interaction method based on the terminal provided by the embodiment can be applied to an application environment as shown in fig. 1, in which a client communicates with a server. The client includes, but is not limited to, various personal computers, notebook computers, smart phones, tablet computers, and portable wearable devices. The server can be implemented by an independent server or a server cluster composed of a plurality of servers.
In an embodiment, as shown in fig. 2, a Teamcenter-based interface data interaction method is provided, which is described by taking the example that the method is applied to the server side in fig. 1, and includes the following steps:
s10, receiving a first configuration instruction, and creating a data set according to the first configuration instruction;
s20, receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction;
s30, receiving a third configuration instruction, and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
s40, acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of the Teamcenter.
In this embodiment, the first configuration instruction may be an instruction generated after a user performs an input operation, or may be an instruction generated after a pre-configured executable script program is run. The first configuration instruction may create a data set in the Teamcenter system. In the menu of the Teamcenter system, an option is included to create a data set. The first configuration instruction may refer to a click operation on the option. The data set is one type of data defined by the Teamcenter system. After a data set is newly created, when the data set has associated data, the data associated with the data set can be opened at the terminal.
Similarly, the second configuration command may be a command generated after the user performs an input operation, or may be a command generated after a pre-configured executable script program is executed. The Teamcenter system includes a user interface for importing data profiles. The second configuration instruction may refer to an instruction generated by a number of operations input on the user interface. These operations include, but are not limited to, operations to select an adaptation type, operations to find a data profile storage location. Through the second configuration instruction, a data configuration file matched with the data set can be imported. The data configuration file is a pre-configured formatted file, such as an XML (extensible markup language) file.
The third configuration command may be a command generated after the user performs an input operation, or may be a command generated after a pre-configured executable script program is executed. The Teamcenter system includes a user interface for setting the association. The association includes, but is not limited to, a registration type and a style sheet type. The registration type may be a type preset by the Teamcenter system, such as "factory BOP". The style sheet type can be a type preset by a Teamcenter system or a type customized by the Teamcenter system. The third configuration instruction may refer to an instruction generated by several operations input on the user interface for setting the association relationship. These operations include, but are not limited to, operations to select a type of registration, operations to select a type of style sheet.
In the data configuration file, the storage location of the target data is configured. The target data refers to external data that the Teamcenter system needs to use other systems. The target data may be obtained according to a storage location configured by the data configuration file. The target data comprises a number of data objects. The data configuration file has predefined attributes of a plurality of data objects. I.e. several columns of attributes defining a class in the data configuration file. These attribute columns may define the hierarchical relationship between the attributes. For example, one attribute of a certain data object is BU (abbreviation of Business unit), and the other attribute is Machine Type. One BU corresponds to multiple Machine types. The Machine types corresponding to different BUs are also generally different. The target data may be parsed according to the attribute relationship defined in the data configuration file to obtain a parsing result that may be recognized by the Teamcenter system. As shown in fig. 3 and 4, fig. 3 and 4 are analysis results displayed on a user interface of the terminal system. Neither the "BU" attribute (labeled 1) in fig. 3 and 4 is a Teamcenter system owned attribute, nor the "Machine Type" attribute (labeled 2) in fig. 3 and 4 is a Teamcenter system owned attribute.
In some cases, to facilitate distinguishing the source of attributes, attributes that are not from the local database may be defined by setting up a special identification. For example, it can be set as: renderingHint is "iaclov".
Optionally, before step S20, that is, before the receiving the second configuration instruction and importing the data configuration file matched with the data set according to the second configuration instruction, the method further includes:
s201, receiving a first editing instruction, and setting a storage path of the target data according to the first editing instruction, wherein the data configuration file comprises the storage path.
In this embodiment, the first editing instruction may be an instruction generated after a user performs an input operation, or may be an instruction generated after a pre-configured executable script program is run. The first editing instruction is used for editing the data configuration file and setting a storage path of the target data. Here, the target data is the source data as compared to the Teamcenter system. In the data configuration file, the statements that can be used to configure the storage path can be expressed as: fromDB ═ Name1: Name2: Name 3. Where Name1 denotes a database Name, Name2 denotes a data table Name, and Name3 denotes a field Name. The first editing instructions may also set the source of the database in a data configuration file. For example, it can be set as: name1 Name4/Name 5. The Name4 is the IP address of the database, and the Name5 is the Name of the storage directory of the database.
Optionally, before step S20, that is, before the receiving the second configuration instruction and importing the data configuration file matched with the data set according to the second configuration instruction, the method further includes:
s202, receiving a second editing instruction, and setting the attribute and the hierarchical relation of the data objects according to the second editing instruction, wherein the data configuration file comprises a plurality of data objects.
In this embodiment, the second editing instruction may be an instruction generated after the user performs an input operation, or may be an instruction generated after a pre-configured executable script program is run. The data configuration file includes a number of data objects that match data objects in the target data. The second editing instructions may set the attributes of the data objects and their hierarchical relationships in the data configuration file. Generally, one data object corresponds to a plurality of attributes. There is a hierarchical relationship between these attributes. For example, a data object includes an A attribute and a B attribute. The A attribute includes a1、a2、a3Three options, when the A attribute is a1When B attribute includes B11、b12、b13Three options.
Optionally, the second editing instruction includes a first sub-editing instruction and a second sub-editing instruction, the data object includes a first data object and a second data object, and the attribute includes a first attribute and a second attribute;
step S202, namely, the receiving a second editing instruction, and setting the attribute and the hierarchical relationship of the data object according to the second editing instruction, includes:
s2021, receiving the first sub editing instruction, and setting a first attribute of the first data object as a parent value list according to the first sub editing instruction;
s2022, receiving the second sub-editing instruction, and setting the second attribute of the second data object as a sub-value list according to the second sub-editing instruction.
In this embodiment, the second editing instruction includes a first sub-editing instruction and a second sub-editing instruction, the data object includes a first data object and a second data object, and the attribute includes a first attribute and a second attribute. The first child editing instruction may be for defining the first attribute as a list of parent values and the second child editing instruction may be for defining the second attribute as a list of parent values. The second data object is the data object after the first attribute of the first data object is designated as a certain setting option.
In an example, a first child edit instruction can configure a first attribute as a list of parent values via ispresent. The second sub-edit instruction configures the second attribute as a sub-value list via ischoldren. The list of sub-values is configured by isChildren, whose values need to correspond to ispresent. The query condition correspondence database field may also be configured through the conditionDB.
The hierarchy between attributes may be more than two levels. For example, the second attribute may be a list of child values of the first attribute, and may be a list of parent values of the third attribute. Therefore, multi-level cascade can be realized, and when the value of the parent value list is selected in the system interface of the Teamcenter system, the list content of the child value list changes dynamically.
It is noted that here, the first attribute may be an attribute owned by the Teamcenter system, and the second attribute may be an attribute of the external system. By defining the relationship between the attributes in the configuration file, seamless connection between data outside the Teamcenter system (i.e., target data) and the Teamcenter system can be realized.
Optionally, after step S30, that is, after the receiving the second configuration instruction and importing the data configuration file matched with the data set according to the second configuration instruction, the method further includes:
s301, receiving a viewing instruction, and opening the data configuration file in a designated viewer according to the viewing instruction;
s302, receiving a modification instruction, and modifying the data configuration file in the designated viewer according to the modification instruction.
In this embodiment, the viewing instruction may be an instruction generated after the user performs an input operation. The designated viewer may be a browser owned by the Teamcenter system, or may be a generic text browser, such as a "notepad". When the data configuration file has data errors, a user can check the content of the data configuration file by checking the instruction and check whether the file has syntax errors.
The modification instruction may be an instruction generated after the user performs an input operation. When the grammar error exists in the data configuration file, the user can modify the data configuration file through the modification instruction. Due to the editability of the data configuration file, the data configuration file is convenient to modify, and a complex interface development program is avoided.
It should be understood that, the sequence numbers of the steps in the foregoing embodiments do not imply an execution sequence, and the execution sequence of each process should be determined by its function and inherent logic, and should not constitute any limitation to the implementation process of the embodiments of the present invention.
In an embodiment, a Teamcenter-based interface data interaction device is provided, and the Teamcenter-based interface data interaction device corresponds to the Teamcenter-based interface data interaction method in the embodiment one to one. As shown in fig. 5, the Teamcenter-based interface data interaction device includes a first configuration module 10, a second configuration module 20, a third configuration module 30 and a parsing module 40. The functional modules are explained in detail as follows:
a first configuration module 10, configured to receive a first configuration instruction, and create a data set according to the first configuration instruction;
a second configuration module 20, configured to receive a second configuration instruction, and import a data configuration file matched with the data set according to the second configuration instruction;
a third configuration module 30, configured to receive a third configuration instruction, and set an association relationship between the data set and the data configuration file according to the third configuration instruction;
and the analysis module 40 is used for acquiring target data according to the data configuration file, analyzing the target data to acquire an analysis result, and displaying the analysis result on a user interface of the Teamcenter.
Optionally, the Teamcenter-based interface data interaction apparatus further includes:
the first editing module is used for receiving a first editing instruction and setting a storage path of the target data according to the first editing instruction, wherein the data configuration file comprises the storage path.
Optionally, the Teamcenter-based interface data interaction apparatus further includes:
and the second editing module is used for receiving a second editing instruction, setting the attribute and the hierarchical relationship of the data object according to the second editing instruction, and the data configuration file comprises a plurality of data objects.
Optionally, the second editing instruction includes a first sub-editing instruction and a second sub-editing instruction, the data object includes a first data object and a second data object, and the attribute includes a first attribute and a second attribute;
the second configuration module 20 includes:
the first sub editing unit is used for receiving the first sub editing instruction and setting a first attribute of the first data object as a parent value list according to the first sub editing instruction;
and the second sub-editing unit is used for receiving the second sub-editing instruction and setting the second attribute of the second data object as a sub-value list according to the second sub-editing instruction.
Optionally, the Teamcenter-based interface data interaction apparatus further includes:
the viewing module is used for receiving a viewing instruction and opening the data configuration file in a specified viewer according to the viewing instruction;
and the modification module is used for receiving a modification instruction and modifying the data configuration file in the specified viewer according to the modification instruction.
For specific limitations of the Teamcenter-based interface data interaction device, reference may be made to the above limitations of the Teamcenter-based interface data interaction method, which is not described herein again. The modules in the above-mentioned Teamcenter-based interface data interaction device can be wholly or partially implemented by software, hardware and their combination. The modules can be embedded in a hardware form or independent from a processor in the computer device, and can also be stored in a memory in the computer device in a software form, so that the processor can call and execute operations corresponding to the modules.
In one embodiment, a computer device is provided, which may be a server, and its internal structure diagram may be as shown in fig. 6. The computer device includes a processor, a memory, a network interface, and a database connected by a system bus. Wherein the processor of the computer device is configured to provide computing and control capabilities. The memory of the computer device comprises a nonvolatile storage medium and an internal memory. The non-volatile storage medium stores an operating system, a computer program, and a database. The internal memory provides an environment for the operation of an operating system and computer programs in the non-volatile storage medium. The database of the computer device is used for storing data related to the Teamcenter-based interface data interaction method. The network interface of the computer device is used for communicating with an external terminal through a network connection. The computer program is executed by a processor to implement a Teamcenter-based interface data interaction method.
In one embodiment, a computer device is provided, comprising a memory, a processor, and a computer program stored on the memory and executable on the processor, the processor implementing the following steps when executing the computer program:
receiving a first configuration instruction, and creating a data set according to the first configuration instruction;
receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction;
receiving a third configuration instruction, and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
and acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of a Teamcenter.
In one embodiment, a computer-readable storage medium is provided, having a computer program stored thereon, which when executed by a processor, performs the steps of:
receiving a first configuration instruction, and creating a data set according to the first configuration instruction;
receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction;
receiving a third configuration instruction, and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
and acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of a Teamcenter.
It will be understood by those skilled in the art that all or part of the processes of the methods of the embodiments described above can be implemented by hardware instructions of a computer program, which can be stored in a non-volatile computer-readable storage medium, and when executed, can include the processes of the embodiments of the methods described above. Any reference to memory, storage, database, or other medium used in the embodiments provided herein may include non-volatile and/or volatile memory, among others. Non-volatile memory can include read-only memory (ROM), Programmable ROM (PROM), Electrically Programmable ROM (EPROM), Electrically Erasable Programmable ROM (EEPROM), or flash memory. Volatile memory can include Random Access Memory (RAM) or external cache memory. By way of illustration and not limitation, RAM is available in a variety of forms such as Static RAM (SRAM), Dynamic RAM (DRAM), Synchronous DRAM (SDRAM), Double Data Rate SDRAM (DDRSDRAM), Enhanced SDRAM (ESDRAM), Synchronous Link DRAM (SLDRAM), Rambus Direct RAM (RDRAM), direct bus dynamic RAM (DRDRAM), and memory bus dynamic RAM (RDRAM).
It will be apparent to those skilled in the art that, for convenience and brevity of description, only the above-mentioned division of the functional units and modules is illustrated, and in practical applications, the above-mentioned function distribution may be performed by different functional units and modules according to needs, that is, the internal structure of the apparatus is divided into different functional units or modules to perform all or part of the above-mentioned functions.
The above-mentioned embodiments are only used for illustrating the technical solutions of the present invention, and not for limiting the same; although the present invention has been described in detail with reference to the foregoing embodiments, it will be understood by those of ordinary skill in the art that: the technical solutions described in the foregoing embodiments may still be modified, or some technical features may be equivalently replaced; such modifications and substitutions do not substantially depart from the spirit and scope of the embodiments of the present invention, and are intended to be included within the scope of the present invention.
Claims (10)
1. A Teamcenter-based interface data interaction method is characterized by comprising the following steps:
receiving a first configuration instruction, and creating a data set according to the first configuration instruction;
receiving a second configuration instruction, and importing a data configuration file matched with the data set according to the second configuration instruction;
receiving a third configuration instruction, and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
and acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of a Teamcenter.
2. The Teamcenter-based interface data interaction method of claim 1, wherein before receiving a second configuration instruction and importing a data configuration file matching the data set according to the second configuration instruction, the method further comprises:
receiving a first editing instruction, and setting a storage path of the target data according to the first editing instruction, wherein the data configuration file comprises the storage path.
3. The Teamcenter-based interface data interaction method of claim 1, wherein before receiving a second configuration instruction and importing a data configuration file matching the data set according to the second configuration instruction, the method further comprises:
and receiving a second editing instruction, and setting the attribute and the hierarchical relationship of the data objects according to the second editing instruction, wherein the data configuration file comprises a plurality of data objects.
4. The Teamcenter-based interface data interaction method of claim 3, wherein the second editing instruction comprises a first sub-editing instruction and a second sub-editing instruction, the data object comprises a first data object and a second data object, and the attribute comprises a first attribute and a second attribute;
the receiving a second editing instruction, and setting the attribute and the hierarchical relationship of the data object according to the second editing instruction, includes:
receiving the first sub editing instruction, and setting a first attribute of the first data object as a parent value list according to the first sub editing instruction;
and receiving the second sub-editing instruction, and setting the second attribute of the second data object as a sub-value list according to the second sub-editing instruction.
5. The Teamcenter-based interface data interaction method of claim 1, wherein after receiving a second configuration instruction and importing a data configuration file matching the data set according to the second configuration instruction, the method further comprises:
receiving a viewing instruction, and opening the data configuration file in a designated viewer according to the viewing instruction;
and receiving a modification instruction, and modifying the data configuration file in the specified viewer according to the modification instruction.
6. A Teamcenter-based interface data interaction device is characterized by comprising:
the system comprises a first configuration module, a second configuration module and a data processing module, wherein the first configuration module is used for receiving a first configuration instruction and creating a data set according to the first configuration instruction;
the second configuration module is used for receiving a second configuration instruction and importing a data configuration file matched with the data set according to the second configuration instruction;
the third configuration module is used for receiving a third configuration instruction and setting the association relationship between the data set and the data configuration file according to the third configuration instruction;
and the analysis module is used for acquiring target data according to the data configuration file, analyzing the target data to obtain an analysis result, and displaying the analysis result on a user interface of the Teamcenter.
7. The Teamcenter-based interface data interaction device of claim 6, further comprising:
the first editing module is used for receiving a first editing instruction and setting a storage path of the target data according to the first editing instruction, wherein the data configuration file comprises the storage path.
8. The Teamcenter-based interface data interaction device of claim 6, further comprising:
and the second editing module is used for receiving a second editing instruction, setting the attribute and the hierarchical relationship of the data object according to the second editing instruction, and the data configuration file comprises a plurality of data objects.
9. A computer device comprising a memory, a processor and a computer program stored in the memory and executable on the processor, wherein the processor implements the Teamcenter-based interface data interaction method according to any one of claims 1 to 5 when executing the computer program.
10. A computer-readable storage medium, in which a computer program is stored, which, when being executed by a processor, implements the Teamcenter-based interface data interaction method according to any one of claims 1 to 5.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010373365.4A CN111726390B (en) | 2020-05-06 | 2020-05-06 | Interface data interaction method, device, equipment and storage medium based on Teamcenter |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010373365.4A CN111726390B (en) | 2020-05-06 | 2020-05-06 | Interface data interaction method, device, equipment and storage medium based on Teamcenter |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN111726390A true CN111726390A (en) | 2020-09-29 |
| CN111726390B CN111726390B (en) | 2022-11-25 |
Family
ID=72564263
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010373365.4A Active CN111726390B (en) | 2020-05-06 | 2020-05-06 | Interface data interaction method, device, equipment and storage medium based on Teamcenter |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN111726390B (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113779641A (en) * | 2021-09-02 | 2021-12-10 | 新奥数能科技有限公司 | Data configuration method and device, computer equipment and computer readable storage medium |
Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100223297A1 (en) * | 2007-03-30 | 2010-09-02 | Alibaba Group Holding Limited | Data Merging in Distributed Computing |
| US20120254836A1 (en) * | 2011-03-30 | 2012-10-04 | Timothy Aaron Storer | Apparatus, System, and Method for Managing Industrial Software Configurations |
| CN103250112A (en) * | 2010-09-30 | 2013-08-14 | 施耐德电气美国股份有限公司 | Power monitoring device simulation using a database profile generated from real time-value data |
| US9348569B1 (en) * | 2012-09-11 | 2016-05-24 | Emc Corporation | Method and system for a configurable automation framework |
| US20160154627A1 (en) * | 2014-11-27 | 2016-06-02 | Siemens Product Lifecycle Management Software Inc. | Representation, comparison, and troubleshooting of native data between environments |
| CN107273104A (en) * | 2016-04-08 | 2017-10-20 | 阿里巴巴集团控股有限公司 | A kind of processing method and processing device of configuration data structure |
| WO2017202219A1 (en) * | 2016-05-23 | 2017-11-30 | 中兴通讯股份有限公司 | Method and device for processing configuration file, olt and onu |
| US20180157686A1 (en) * | 2016-12-05 | 2018-06-07 | Sap Se | System and method for datastore management framework |
| CN109348052A (en) * | 2016-06-12 | 2019-02-15 | 苹果公司 | For managing the user interface of controllable external equipment |
| CN109858081A (en) * | 2018-12-25 | 2019-06-07 | 郑州日产汽车有限公司 | Vehicle product data design collaboration method based on Teamcenter |
| CN110474959A (en) * | 2019-07-12 | 2019-11-19 | 平安普惠企业管理有限公司 | Data interactive method, device, computer equipment and storage medium |
| US20190370889A1 (en) * | 2017-02-28 | 2019-12-05 | Siemens Product Lifecycle Management Software Inc. | System and method for visual traceability of requirements for products |
| CN110889582A (en) * | 2019-10-10 | 2020-03-17 | 中国第一汽车股份有限公司 | Method for realizing PBOM visualization based on Teamcenter |
-
2020
- 2020-05-06 CN CN202010373365.4A patent/CN111726390B/en active Active
Patent Citations (13)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20100223297A1 (en) * | 2007-03-30 | 2010-09-02 | Alibaba Group Holding Limited | Data Merging in Distributed Computing |
| CN103250112A (en) * | 2010-09-30 | 2013-08-14 | 施耐德电气美国股份有限公司 | Power monitoring device simulation using a database profile generated from real time-value data |
| US20120254836A1 (en) * | 2011-03-30 | 2012-10-04 | Timothy Aaron Storer | Apparatus, System, and Method for Managing Industrial Software Configurations |
| US9348569B1 (en) * | 2012-09-11 | 2016-05-24 | Emc Corporation | Method and system for a configurable automation framework |
| US20160154627A1 (en) * | 2014-11-27 | 2016-06-02 | Siemens Product Lifecycle Management Software Inc. | Representation, comparison, and troubleshooting of native data between environments |
| CN107273104A (en) * | 2016-04-08 | 2017-10-20 | 阿里巴巴集团控股有限公司 | A kind of processing method and processing device of configuration data structure |
| WO2017202219A1 (en) * | 2016-05-23 | 2017-11-30 | 中兴通讯股份有限公司 | Method and device for processing configuration file, olt and onu |
| CN109348052A (en) * | 2016-06-12 | 2019-02-15 | 苹果公司 | For managing the user interface of controllable external equipment |
| US20180157686A1 (en) * | 2016-12-05 | 2018-06-07 | Sap Se | System and method for datastore management framework |
| US20190370889A1 (en) * | 2017-02-28 | 2019-12-05 | Siemens Product Lifecycle Management Software Inc. | System and method for visual traceability of requirements for products |
| CN109858081A (en) * | 2018-12-25 | 2019-06-07 | 郑州日产汽车有限公司 | Vehicle product data design collaboration method based on Teamcenter |
| CN110474959A (en) * | 2019-07-12 | 2019-11-19 | 平安普惠企业管理有限公司 | Data interactive method, device, computer equipment and storage medium |
| CN110889582A (en) * | 2019-10-10 | 2020-03-17 | 中国第一汽车股份有限公司 | Method for realizing PBOM visualization based on Teamcenter |
Non-Patent Citations (2)
| Title |
|---|
| "CAD杂志信息化产品推荐", 《CAD/CAM与制造业信息化》 * |
| 方水良等: "PDM组件开发及其在多种应用软件中的集成", 《计算机工程与应用》 * |
Cited By (2)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN113779641A (en) * | 2021-09-02 | 2021-12-10 | 新奥数能科技有限公司 | Data configuration method and device, computer equipment and computer readable storage medium |
| CN113779641B (en) * | 2021-09-02 | 2024-03-05 | 新奥数能科技有限公司 | Data configuration method, device, computer equipment and computer readable storage medium |
Also Published As
| Publication number | Publication date |
|---|---|
| CN111726390B (en) | 2022-11-25 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US20210279115A1 (en) | Automated api code generation | |
| US8302092B2 (en) | Extensible data driven deployment system | |
| CN109857630B (en) | Code detection method, system and equipment | |
| Wittern et al. | Opportunities in software engineering research for web API consumption | |
| US20160246582A1 (en) | Generic Semantic Configuration Service | |
| CN111414350B (en) | Service generation method and device | |
| US20170351506A1 (en) | Automating feature graduation | |
| US20180150530A1 (en) | Method, Apparatus, Computing Device and Storage Medium for Analyzing and Processing Data | |
| US11720532B2 (en) | System and method for customized graphQL data-handling scripts | |
| RU2639667C2 (en) | Context invitation in trial version of application | |
| WO2020192141A1 (en) | Method and device for simulating interface, computer apparatus, and storage medium | |
| US20150074045A1 (en) | Business Rule Management System | |
| CN110162464A (en) | Mcok test method and system, electronic equipment and readable storage medium storing program for executing | |
| CN111726390B (en) | Interface data interaction method, device, equipment and storage medium based on Teamcenter | |
| CN112328342A (en) | To-do item processing method and device based on online document | |
| CN115543419A (en) | Method, device, equipment and storage medium for generating software development kit | |
| US20140359258A1 (en) | Declarative Configuration Elements | |
| CN112306533A (en) | Front-end framework automatic conversion method and device, computer equipment and storage medium | |
| US20230169975A1 (en) | Enabling speech interactions on web-based user interfaces | |
| WO2022099913A1 (en) | Interface configuration method and apparatus, and device and medium | |
| US11366642B1 (en) | Change migration: processes for ensuring successful deployment of design changes | |
| KR102349344B1 (en) | Source code automatic generation system using dataized variable and source code automatic generation method thereof | |
| CN115374083A (en) | Data source switching method and device, electronic equipment and storage medium | |
| CN112988298A (en) | Visual interface configuration method and device, computer equipment and storage medium | |
| CN114546418A (en) | application platform of aPaaS all-in-one machine |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |