# Patent

## Title
External evaluation processes

## Abstract

Methods and apparatus, including computer program products, for managing data. The technique includes defining a secondary data set in a primary data set, linking the secondary data set to state information of the primary data set, transmitting the secondary data set to an external entity, receiving a modified secondary data set from the external entity and linking the modified secondary data set to a version of the primary data set stored with reference to state the information. The state information defines the state of the primary data set at the time the secondary data set is defined. The link between the modified secondary data set and the primary data set allows access by a user of a modified primary data set if the primary data set has changed with reference to the state information.

## Background
CROSS-REFERENCE TO RELATED APPLICATIONS
This application claims priority to U.S. Provisional Application No. 60/367,397, which was filed on Mar. 21, 2002. The contents of U.S. Provisional Application No. 60,367,397 are hereby incorporated by reference into this application as if set forth herein in full. This application is a continuation of U.S. patent application Ser. No. 10/328,716, which was filed on Dec. 23, 2002 now U.S. Pat. No. 7,133,878. The contents of U.S. patent application Ser. No. 10/328,716 are hereby incorporated by reference into this application as if set forth herein in full.


BACKGROUND
The present invention relates to data processing, and more particularly, to managing data received from external processes.
An important factor in the success of businesses in the current era is the ability to flexibly react to the requirements of the market. Shorter product cycles require decreased product development times and quicker introduction to market while increased customer demands for individual solutions increases the number of variants.
These factors require businesses to be able to proceed simultaneously with the definition of the product requirements and its structure, while participating in collaborative processes with external entities such as subcontractors and development partners. New products must be introduced rapidly to market based on internally and externally defined requirements. In order to do this, different approaches must be considered, and input can be provided by external entities performing external evaluation processes.
External processes can include, for example, verification processes, costing evaluations and crash tests (for automobile production systems).
SUMMARY OF THE INVENTION
The present invention provides methods and apparatus, including computer program products, for managing data.
In general, in one aspect, the invention features methods and apparatus implementing a technique for managing data. The technique includes defining a secondary data set in a primary data set, linking the secondary data set to state information of the primary data set, transmitting the secondary data set to an external entity, receiving a modified secondary data set from the external entity and linking the modified secondary data set to a version of the primary data set stored with reference to state the information. The state information defines the state of the primary data set at the time the secondary data set is defined. The link between the modified secondary data set and the primary data set allows access by a user of a modified primary data set if the primary data set has changed with reference to the state information.
Particular implementations can include one or more of the following features. Linking the secondary data set to the state information can include associating the secondary data set with the primary data set at a time t1. Linking the modified secondary data set to the version of the primary data set stored with reference to the state information can include linking the modified secondary data set to the version of the primary data set existing at a time t1.
The version of the primary data set stored with reference to the state information can be linked to the modified primary data set. Linking the version of the primary data set stored with reference to the state information to the modified primary data set can include linking the version of the primary data set stored with reference to the state information to a version of the primary data set at a time t2, where the version of the primary data set at time t2 represents the current state of the primary data set.
The extended data can be received and linked to the modified secondary data set, the extended data including data added to the secondary data set for processes performed at the external entity. The secondary data set to the external entity can be transmitted to a verification entity, a cost calculating entity, an evaluation entity or a crash test entity. Processes can be performed on the secondary data set at the external entity to obtain the modified set. The processes performed on the secondary data set can include performing evaluations using the secondary data set. A user can be provided with a user interface to access the modified secondary data set.
The technique can also include determining if the modified secondary data set is relevant to the modified primary data set, and linking the modified secondary data set to the modified primary data set if the modified secondary data set is relevant to the modified primary data set. The determination if the modified secondary data set is relevant to the modified primary data set can include receiving input from a user indicating that the modified secondary data set is relevant to the modified primary data set.
In general, in one aspect, the invention features an external data management system. The system can include a data storage system and a product record user interface, where the data storage system stores a historic version of a product record and a current version of the product record. The historic version of a product record can include a link to external data, where the external data is received from an external entity and includes results of evaluations performed on a product structure based on the historic version of the product record. The current version of the product record can include a link to the historic version of the product record. The product record user interface presents a user with a current version of the product record including a user interface control. The user interface control represents the link to the historic version of the product record, and allows the user to access the historic version of the product record, including the external data, through the product record user interface.
Particular implementations can include one or more of the following features. The external data can include extended data used by the external entity to perform the evaluations on the product structure. The data storage system can be part of a central module including long-term storage of data related to the product creation process.
The invention can be implemented to realize one or more of the following advantages. A central data storage stores all objects related to a product creation process, and transmits data, such as product structure, to other entities to perform evaluations. If the product structure has changed when the results of the evaluations are returned, the evaluation results can be stored with the corresponding historic product structure, i.e., the product structure existing at the time the product structure data was sent to the evaluating entity. A user can navigate between the current product structure and the results of evaluations performed on the historic product structure through an evaluation results tool including navigational links between the current product structure and the evaluation results at the corresponding historic product structure. The navigational links can also include links to additional data used in the evaluation process. The access to the results of the evaluations performed on the historic product structure, and the additional data used to perform the evaluations, allows a user to determine if the evaluations are relevant to the current product structure. The evaluation results tool provides users, such as designers, quick access to relevant evaluation results.
The details of one or more implementations of the invention are set forth in the accompanying drawings and the description below. Other features and advantages of the invention will become apparent from the description, the drawings, and the claims.



BRIEF DESCRIPTION OF THE DRAWINGS
FIG. 1 is a block diagram illustrating an implementation of a product creation system.
FIG. 2 is a block diagram illustrating an implementation of a data store in an entity of a product creation system.
FIG. 3 is a block diagram illustrating a class record within a product record of the product creation system.
FIG. 4 is a block diagram illustrating an implementation of an external data management system in a product creation system.
FIG. 5 is a block diagram illustrating an implementation of a product record including a link to historic data.
FIG. 6 is a block diagram illustrating an implementation of a historic product record.
FIG. 7 is a block diagram illustrating an implementation of an external data record.
FIG. 8 is a flow diagram illustrating one implementation of a method for managing external data in a product creation system.



Like reference numbers and designations in the various drawings indicate like elements.
DETAILED DESCRIPTION
As shown in FIG. 1, an external data management system can be implemented in a product creation system. The product creation system includes a central module 110 and entity modules 120. Each of modules 110, 120 includes a data store 115, 125, and engines 112, 122. Engines 112, 122 can represent one or more engines for performing processes in modules 110, 120.
The central module 110 represents a centralized control for a product creation process. The entity modules 120 represent entities involved in the product creation process. Typically, many entities can participate in the development of a product.
The entities can include internal and external entities. For example, entity modules 120 can include modules for testing, cost management, verification, and digital mockup. These entity modules 120 can forward data to the central module 110 which other services use for their processes. The central module 110 and the entity modules 120 can communicate through a network 130.
The central module 110 includes a central data store 115 that stores master data for a product creation process. The central data can be accessed by the entity modules 120 or transmitted to the entity modules 120 through network 130. Each of the entity modules 120 includes a data store 125 for storing the data received from the central module 110 and for additional entity specific data developed in a given entity module 120. For example, if the entity module 120 is a verification module, the corresponding data store 125 can store additional data used to complete a verification process. The entity specific data can be transmitted to the central data store 115.
Data for the product creation process can be stored in records in the data stores 115, 125. The data includes objects associated with the product creation process. These objects can include product classes, attributes, product line designs, parts lists, materials lists, quality characteristics, and requirements. The objects can be organized in the data store with relation to products, product lines, and classes of products, as described below with reference to FIG. 2 and FIG. 3.
The entity modules 120 can perform evaluations related to the product creation process in parallel or asynchronously through engines 122. Each developing entity module 120 can develop different versions of each object of the product creation process. Each evaluating entity module 120 can perform evaluations based on different versions of products or product lines stored in the central module 110.
The central module 110 and the entity modules 120 can include one or more computer systems, computer applications and/or individual or groups of users. The processes performed at the central module 110 and the entity modules 120 can be performed in engines 112 by computer applications and/or users. Each entity module 120 can include modules to perform evaluations such as cost calculations, crash tests, verifications and other evaluations related to a product creation process.
FIG. 2 is a block diagram illustrating an example of a product record 220 stored in a data store 115, 125. The product associated with the product record 220 can include a specific product or a product line. The product record 220 can include object records 230, such as, for example, one or more class records. Classes can include, in the example of an automobile creation process, types, models, body styles, and sizes. Class records can contain information about classes or sub-classes of the product(s). Thus, each object record 230 in a first tier 240 can have one or more object records 230 in a second tier 250 associated with it.
Object records 230 can be organized in a variety of ways. In one implementation, the object records 230 can be organized in a tree structure with broader objects including narrower objects (or sub-objects) in its branches. For example, a first tier 240 of automobile classes can include types of automobiles, such as economy car, luxury car or sports car. Then, a second tier of automobile classes 250 can include models that are available under that type definition.
In a more general case, the product record 220 can include other types of objects and relationships between these objects. For example, object records 230 can include information about materials, structures, and/or goals.
FIG. 3 is a block diagram illustrating a class record 230 within the product record (FIG. 2). Object record 230 can include a variety of documents, such as a specification document 320, a computer-aided design (“CAD”) Document 330 and a Parts/Materials document 340.
The specification document 320 can include attribute records 322. Each attribute record 322 can contain information about an attribute associated with the product. Attributes can include component information such as engine type (e.g., 95 HP, 110 HP, 125 HP, etc.) or brake type (e.g., disc or drum), or characteristics such as body color (e.g., black, silver, red, etc.) or fuel efficiency (e.g., 25 m.p.g.). Each attribute record 322 can include a value for each attribute. For example, if the attribute record 322 stores information for the attribute “engine power,” the information stored in the attribute record can include a value of “110 HP.”
FIG. 4 is a block diagram illustrating an implementation of an external data management system in a product creation system. Central module 110 includes product structures (T1) and (T2), stored in locations 410, 430 of data store 115. Central module 110 also includes a remodel engine 420.
Product structure (T1), stored in location 410, includes a product structure at time T1. The product structure can include all objects stored for a product. The remodel engine 420 integrates information received from other modules and/or changes to the product structure (T1).
The product structure (T2), stored in location 430, includes the product structure at time T2. The product structure (T2) includes a product structure defined in the remodel engine 420, incorporating the information or changes to the product structure (T1). The time T2 represents the time when central module 110 receives evaluation results data from entity module 120.
The entity module 120 includes a product structure (T1) stored in location 460, an evaluation engine 440, and results (T2), stored in location 450. Entity module 120 receives the product structure information into location 460 at time T1. The evaluation engine 440 performs evaluations based on the product structure (T1). The results of the evaluation, results (T2), are stored in location 450, and sent to the central module 110 at a time T2.
For example, the entity module 120 can include a module that performs car crash tests. The entity module 120 receives product structure (T1) at location 460, performs the car crash tests through evaluation engine 440, and stores the results (T2) in location 450. The entity module can locally extend the available data, i.e., product structure (T1), by including extended data 470. Extended data 470 can be used by entity module 120 to add context to the product structure (T1) in performing the evaluations in evaluation engine 440. In the car crash test example, the extended data can include a full fuel tank. The entity module 120 then transmits the results to central module 110. The extended data 470 is only relevant for the correct product structure, i.e., the product structure existing at T1 which is used to perform the evaluations. The extended data 470 is linked to product structure (T1), but does not become part of product structure (T1).
The central module 110 stores the received results, results (T2) with the product structure (T1) in location 410. The product structure (T2) stored in location 430 can include a link to the product structure (T1). The link to product structure (T1) in product structure (T2) can be labeled a historic product structure in a user interface. Thus, a virtual link is defined between the product structure (T2) and the results (T2) by adding the results (T2) to the product structure (T1). A user can access the results through a link to the product structure (T1) in a user interface.
FIG. 5 is a block diagram illustrating an implementation of a product record including a link to historic data. The product record 220 can be part of the product structure (T2) module 430. The product record 220 is shown as a tree structure including a plurality of objects 230. The product record also includes a link to a historic structure 510. The historic structure can be the product structure (T1) stored in location 410. A user interface of the product record 220 can include the tree structure with a branch to historic structure 510 at every object 230 which has a corresponding historic object 530.
As shown in FIG. 5, historic product record 520 can include historic object records 530 associated with the historic product record 520. Each historic object record 530 is linked to a corresponding object record 230 in the current product record 220 which has a corresponding historic object 530.
The historic structure 510 can be different from the product structure 220. For example, the product record 220 can include changes in types of classes 230 defined or changes within class records 230, such as changes to attributes 322. Further, object records 230 in product record 220 may not correspond to historic object records 530. If an object record 230 has been added to product record 220 that was not in historic structure 510, there will not be a link from the historic structure 510 to the added object record 230. If an object record 530 that existed in the historic structure 510 has been deleted, and thus, no longer exists in the current product record 220, there will be no link from the deleted historic object record 530 to the current product record 220.
FIG. 6 is a block diagram illustrating an implementation of a historic product record 510. As described above, the historic structure 510 can include the product structure (T1) stored in location 410.
The historic product structure 510 includes a link to extended data 650 and evaluation results 640, which includes results (T2), received from entity module 120. The evaluation results 640 can include a link to extended data 650, which can include the extended data 470 used by the entity module 120 to perform evaluations.
FIG. 7 is a block diagram illustrating an implementation of a user interface 700 of an external data record 640. The user interface 700 can include results from one or more entity modules 120. For example, the user interface 700 can display cost calculations performed by a cost management module, weight calculations performed by a verification module, and crash test results performed by a crash test module. Each listing of an evaluation result can include a scalar value, if a scalar value can be listed, and/or a user interface control 710 representing a link to a corresponding results record for the evaluation listed. In one implementation, the scalar value field can include the user interface control 710 to the corresponding results record for the evaluation listed.
The results can be listed by type of results, such as cost calculations, and date of results. The listing of the results can also include a user interface control representing a link to extended data used in obtaining the results.
A user can view a result record for a specific evaluation by selecting the user interface control 710 corresponding to the evaluation. Referring to FIG. 6, the result record can include the results 640 of the specific evaluation and a listing of or a user interface control representing a link to extended data 650 used to perform the evaluation.
Thus, for example, a user seeing that the cost of a part has been rising over the course of a year can select the user interface control 710 to retrieve the associated results record. The results record 710, and extended data, can include a link to the historic structure, which can indicate that some aspect of the part was substituted, increasing costs.
The user interface 700 can also include a traffic light symbol 720 or other indicator of what results corresponding to the traffic light symbol 720 suggest. For example, if the results of a crash test are negative, the traffic light 720 can include shading in the area corresponding to the red light. If the results indicate that a closer look should be given to the structure, the traffic light 720 can include shading in the area corresponding to the yellow light. If the results for the crash test were good, the traffic light 720 can include shading in the area corresponding to the green light.
FIG. 8 is a flow diagram illustrating one implementation of a method for managing external data in a product creation system.
At step 810, a secondary data set is defined in the central module 110. The secondary data set can include a copy of the product structure (T1), representing a product record 220 at time T1. At step 820, the central module 110 links the secondary data set to state information of a primary data set. The primary data set can include product structure (T1). The state information can include the time, T1, the secondary data set is created and sent to an external entity.
At step 830, the central module 110 transmits the secondary data set to an external entity, such as entity module 120. The external entity can perform evaluations on the secondary data set. The evaluations can include cost calculations, verification, crash tests, or other tests that the central module would like performed based on the product structure 220.
At step 840, the central module 110 receives a modified secondary data set. The modified secondary data set can include the results of the evaluations performed at the external entity. The central module 110 can also receive extended data with the results of the evaluations. The extended data can include data used by the external entity to perform evaluations. For example, for weight calculations for a car, the extended data can include the addition of a driver and/or 5 gallons of gasoline in the fuel tank.
At step 850, the central module 110 links the modified secondary data set to the primary data set based on the state information. If the primary data set or product record 220 has been modified, the modified secondary data set is stored with a record of the primary data set corresponding to the state information. Thus, if the state information includes a reference to a product structure at a time T1, the modified secondary data set can be stored with the product structure (T1) in location 410. The link between the modified secondary data set and the primary data set allows access by a user of a modified primary data set
The method can also include linking the modified primary data set, represented by the product structure (T2), to the primary data set at time T1. Thus, the product structure (T2), stored in location 430 is linked to the product structure (T1). The product structure (T1) is labeled as a historic structure 510 in the product structure (T2).
The invention can be implemented in digital electronic circuitry, or in computer hardware, firmware, software, or in combinations of them. The invention can be implemented as a computer program product, i.e., a computer program tangibly embodied in an information carrier, e.g., in a machine-readable storage device or in a propagated signal, for execution by, or to control the operation of, data processing apparatus, e.g., a programmable processor, a computer, or multiple computers. A computer program can be written in any form of programming language, including compiled or interpreted languages, and it can be deployed in any form, including as a stand-alone program or as a module, component, subroutine, or other unit suitable for use in a computing environment. A computer program can be deployed to be executed on one computer or on multiple computers at one site or distributed across multiple sites and interconnected by a communication network.
Method steps of the invention can be performed by one or more programmable processors executing a computer program to perform functions of the invention by operating on input data and generating output. Method steps can also be performed by, and apparatus of the invention can be implemented as, special purpose logic circuitry, e.g., an FPGA (field programmable gate array) or an ASIC (application-specific integrated circuit).
Processors suitable for the execution of a computer program include, by way of example, both general and special purpose microprocessors, and any one or more processors of any kind of digital computer. Generally, a processor will receive instructions and data from a read-only memory or a random access memory or both. The essential elements of a computer are a processor for executing instructions and one or more memory devices for storing instructions and data. Generally, a computer will also include, or be operatively coupled to receive data from or transfer data to, or both, one or more mass storage devices for storing data, e.g., magnetic, magneto-optical disks, or optical disks. Information carriers suitable for embodying computer program instructions and data include all forms of non-volatile memory, including by way of example semiconductor memory devices, e.g., EPROM, EEPROM, and flash memory devices; magnetic disks such as internal hard disks and removable disks; magneto-optical disks; and CD-ROM and DVD-ROM disks. The processor and the memory can be supplemented by, or incorporated in special purpose logic circuitry.
To provide for interaction with a user, the invention can be implemented on a computer having a display device such as a CRT (cathode ray tube) or LCD (liquid crystal display) monitor for displaying information to the user and a keyboard and a pointing device such as a mouse or a trackball by which the user can provide input to the computer. Other kinds of devices can be used to provide for interaction with a user as well; for example, feedback provided to the user can be any form of sensory feedback, such as visual feedback, auditory feedback, or tactile feedback; and input from the user can be received in any form, including acoustic, speech, or tactile input.
The invention can be implemented in a computing system that includes a back-end component, e.g., as a data server, or that includes a middleware component, e.g., an application server, or that includes a front-end component, e.g., a client computer having a graphical user interface or an Web browser through which a user can interact with an implementation of the invention, or any combination of such back-end, middleware, or front-end components. The components of the system can be interconnected by any form or medium of digital data communication, e.g., a communication network. Examples of communication networks include a local area network (“LAN”), a wide area network (“WAN”), and the Internet.
The computing system can include clients and servers. A client and server are generally remote from each other and typically interact through a communication network. The relationship of client and server arises by virtue of computer programs running on the respective computers and having a client-server relationship to each other.
The invention has been described in terms of particular embodiments. Other embodiments are within the scope of the following claims. For example, the steps of the invention can be performed in a different order and still achieve desirable results.

## Claims

1. A system to manage external data in a product creation process, the system comprising:
a data storage system configured to store:
a historic version of a product record in the product creation process of a physical product, the historic version of the product record including a first product structure and a link to external data, the first product structure comprising a plurality of object records regarding respective aspects of the physical product, the first product structure being indicative of relationships of the plurality of object records to one another, the external data including results of evaluations performed by an external entity on the first product structure, and
a current version of the product record including a second product structure and a link to the historic version of the product record, the second product structure including changes to the first product structure based on the results of the evaluations; and

a processor configured to provide a user interface to present:
the current version of the product record, and
a user interface control representing the link to the historic version of the product record, the user interface control to provide access to the historic version of the product record and to the external data.

2. A computer program product, tangibly stored on machine-readable medium, the computer program product comprising instructions operable to cause one or more programmable processors to:
store, in a data storage system:
a historic version of a product record in a product creation process of a physical product, the historic version of the product record including a first product structure and a link to external data, the first product structure comprising a plurality of object records regarding respective aspects of the physical product, the first product structure being indicative of relationships of the plurality of object records to one another, the external data being received from an external entity and including results of evaluations performed by the external entity on the first product structure, and
a current version of the product record including a second product structure and a link to the historic version of the product record, the second product structure including changes to the first product structure based on the results of the evaluations; and

provide a user interface for presenting:
the current version of the product record, and
a user interface control representing the link to the historic version of the product record, the user interface control providing access to the historic version of the product record and to the external data.

3. The system of claim 1, wherein the external data includes extended data used by an external entity to perform the evaluations on the product structure.

4. The system of claim 1, wherein the data storage system and the processor are part of a central module.

5. The system of claim 1, further comprising a remodel engine configured to define the second product structure by integrating the external data received from an external entity into the first product structure.

6. The system of claim 1, wherein the processor is further configured to transmit the first product structure to an external entity.

7. The system of claim 1, wherein the user interface is configured to display the current version of the product record as a tree structure having branches that connect objects of the current version of the record with corresponding historic objects of the historic version of the product record.

8. The system of claim 1, wherein the processor is further configured to display the results through the user interface, the results being organized by type and date.

9. The system of claim 1, wherein the aspects of the physical product to which the object records relate include at least one of product classes, attributes, product line designs, parts lists, materials lists, quality characteristics, and requirements.

10. The system of claim 1, wherein the object records are organized in the first product structure with relation to products, product lines, and/or classes of products.

11. The computer program product of claim 2, further comprising instructions operable to cause the one or more programmable processors to define the second product structure by integrating the external data received from the external entity into the first product structure.

12. The computer program product of claim 2, further comprising instructions operable to cause the one or more programmable processors to transmit the first product structure to the external entity.

13. The computer program product of claim 2, further comprising instructions operable to cause the one or more programmable processors to integrate additional external data received from a second external entity into the first product structure, the additional external data including results of evaluations performed on the first product structure at the second external entity.

14. The system of claim 5, wherein the remodel engine is further configured to integrate additional external data received from a second external entity into the first product structure, the additional external data including results of evaluations performed on the first product structure at the second external entity.

15. The computer program product of claim 2, wherein the object records are organized in the first product structure with relation to products, product lines, and/or classes of products.

16. The computer program product of claim 2, wherein the aspects of the physical product to which the object records relate include at least one on product classes, attributes, product line designs, parts lists, materials lists, quality characteristics, and requirements.