CN102054220B - Software interface management system and method thereof - Google Patents

Software interface management system and method thereof Download PDF

Info

Publication number
CN102054220B
CN102054220B CN201010545559.4A CN201010545559A CN102054220B CN 102054220 B CN102054220 B CN 102054220B CN 201010545559 A CN201010545559 A CN 201010545559A CN 102054220 B CN102054220 B CN 102054220B
Authority
CN
China
Prior art keywords
interface
module
product
version
control module
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.)
Active
Application number
CN201010545559.4A
Other languages
Chinese (zh)
Other versions
CN102054220A (en
Inventor
P·斯里尼瓦桑
C·A·吉兰德斯
D·G·博尔斯特鲁姆
T·W·海恩斯
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
GM Global Technology Operations LLC
Original Assignee
GM Global Technology Operations LLC
Priority date (The priority date 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 date listed.)
Filing date
Publication date
Priority claimed from US12/696,357 external-priority patent/US8645233B2/en
Application filed by GM Global Technology Operations LLC filed Critical GM Global Technology Operations LLC
Publication of CN102054220A publication Critical patent/CN102054220A/en
Application granted granted Critical
Publication of CN102054220B publication Critical patent/CN102054220B/en
Active legal-status Critical Current
Anticipated expiration legal-status Critical

Links

Images

Classifications

    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q10/00—Administration; Management
    • G06Q10/06—Resources, workflows, human or project management; Enterprise or organisation planning; Enterprise or organisation modelling
    • G—PHYSICS
    • G06—COMPUTING; CALCULATING OR COUNTING
    • G06Q—INFORMATION AND COMMUNICATION TECHNOLOGY [ICT] SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES; SYSTEMS OR METHODS SPECIALLY ADAPTED FOR ADMINISTRATIVE, COMMERCIAL, FINANCIAL, MANAGERIAL OR SUPERVISORY PURPOSES, NOT OTHERWISE PROVIDED FOR
    • G06Q50/00—Systems or methods specially adapted for specific business sectors, e.g. utilities or tourism
    • G06Q50/04—Manufacturing
    • Y—GENERAL TAGGING OF NEW TECHNOLOGICAL DEVELOPMENTS; GENERAL TAGGING OF CROSS-SECTIONAL TECHNOLOGIES SPANNING OVER SEVERAL SECTIONS OF THE IPC; TECHNICAL SUBJECTS COVERED BY FORMER USPC CROSS-REFERENCE ART COLLECTIONS [XRACs] AND DIGESTS
    • Y02—TECHNOLOGIES OR APPLICATIONS FOR MITIGATION OR ADAPTATION AGAINST CLIMATE CHANGE
    • Y02P—CLIMATE CHANGE MITIGATION TECHNOLOGIES IN THE PRODUCTION OR PROCESSING OF GOODS
    • Y02P90/00—Enabling technologies with a potential contribution to greenhouse gas [GHG] emissions mitigation
    • Y02P90/30—Computing systems specially adapted for manufacturing

Landscapes

  • Engineering & Computer Science (AREA)
  • Business, Economics & Management (AREA)
  • Human Resources & Organizations (AREA)
  • Economics (AREA)
  • Strategic Management (AREA)
  • General Physics & Mathematics (AREA)
  • Tourism & Hospitality (AREA)
  • Entrepreneurship & Innovation (AREA)
  • Theoretical Computer Science (AREA)
  • Marketing (AREA)
  • General Business, Economics & Management (AREA)
  • Physics & Mathematics (AREA)
  • Operations Research (AREA)
  • Quality & Reliability (AREA)
  • Game Theory and Decision Science (AREA)
  • Development Economics (AREA)
  • Educational Administration (AREA)
  • Manufacturing & Machinery (AREA)
  • Health & Medical Sciences (AREA)
  • General Health & Medical Sciences (AREA)
  • Primary Health Care (AREA)
  • Management, Administration, Business Operations System, And Electronic Commerce (AREA)
  • Stored Programmes (AREA)

Abstract

The invention provides a software interface management system and a method thereof.An interface control module comprises a link generation module that generates a first link between a provider module and a consumer module.An interface contract module generates an interface contract.The interface contract corresponds to an interface of a product that includes the first link.The interface contract defines the interface based on a bill of materials (BOM).An interface assembly module assembles modules including the provider module and the consumer module to generate the product.An interface viewing module displays logical and physical views of the product on a display at least one of before and after assembly of the product.

Description

Software interface management system and method
The cross reference of related application
The application requires the rights and interests of the U.S. Provisional Application 61/259398 of submitting on November 9th, 2009.Above-mentioned disclosed content is all incorporated to herein by reference.
Technical field
The present invention relates to the management system based on product and content.
Background technology
The background technology that this part provides is described the ins and outs that object is that large volume description is invented.The described the present inventor's of this background technology part work and this background technology describe when application is submitted to not as the other side of prior art, all can not be considered to clearly or impliedly prior art of the present disclosure.
In the research and development of product with in producing, relate to some different processing stage.These processing stage can comprise for example demand, exploitation, foundation, test, calibration, checking and launch phase.The company with a large amount of different business can development and production large-tonnage product.Every kind of product (for example, vehicle) can have some different sub-products that are associated (for example, engine controller, gearbox controller etc.).Each product and/or sub-product can have the issue being associated.Each issue can have the series, type year, version and the step (cadence) that are associated.Step refers to concrete date issued.Each product and/or sub-product can have the Bill of Material (BOM) (BOM) being associated.Therefore at the development and production of each product stage management product, may be, complicated and chaotic.
Summary of the invention
In one embodiment, interface control module comprises the link generation module that produces the first link between supplier's module and consumer's module.Interface contract module produces interface contract.Interface contract is corresponding to the interface of product that comprises the first link.Interface contract has defined interface based on Bill of Material (BOM) (BOM).Multiple modules that interface compilation module collects including supplier's module and consumer's module are to produce product.Interface is watched the logic and the Physical View that in module at least one situation before the compilation of this product and afterwards, on display, show this product.
In further feature, above-described system and method is implemented by the computer program of being carried out by one or more processors.Computer program can reside on tangible computer-readable medium, such as but not limited to storer, non-volatile data storage device, and/or other tangible storage medium being applicable to.
The present invention also provides following technical scheme.
1. an interface control module, comprising:
Link generation module, produces the first link between supplier's module and consumer's module;
Interface contract module, produces interface contract,
Wherein:
Described interface contract is corresponding to the interface that comprises the described first product linking; With
Described interface contract defines described interface based on Bill of Material (BOM) (BOM);
Interface compilation module, the module of compilation including described supplier's module and described consumer's module is to produce product; With
Interface Observation Blocks shows logic and the Physical View of described product on display at least one situation before the compilation of described product and afterwards.
2. as the interface control module of technical scheme 1, it is characterized in that, described interface contract comprises supplier's identifier (ID), consumer ID, interface definition object ID, link ID and data object ID.
3. as the interface control module of technical scheme 1, it is characterized in that, described interface contract is between characteristic element.
4. as the interface control module of technical scheme 3, it is characterized in that, described characteristic element comprises at least one in assembly and interface definition object.
5. as the interface control module of technical scheme 1, it is characterized in that, described interface contract is between the various level content-level item of BOM.
6. as the interface control module of technical scheme 5, it is characterized in that, described content-level item comprises two or more among control system, group style, ring style and feature.
7. as the interface control module of technical scheme 1, it is characterized in that, described supplier from described consumer in different BOM levels.
8. as the interface control module of technical scheme 1, it is characterized in that, also comprise Product-level interface module, described Product-level interface module is identified the interface being associated with each level of BOM.
9. as the interface control module of technical scheme 1, it is characterized in that, described interface Observation Blocks shows the link of the intermodule of product when showing the logic of product and Physical View, comprises described the first link between described supplier and described consumer.
10. as the interface control module of technical scheme 1, it is characterized in that, described interface contract module is set up the second interface contract based on first interface contract.
11. as the interface control module of technical scheme 1, it is characterized in that:
Described supplier is interface definition object, and described consumer is the first assembly; And
Described link generation module is created in the link of second between data object and described interface definition object.
12. as the interface control module of technical scheme 11, it is characterized in that, described interface generation module is created in the 3rd link between the second assembly and described interface definition object.
13. as the interface control module of technical scheme 12, it is characterized in that, the first link described in described interface contract module definition, the second link and the 3rd link.
14. as the interface control module of technical scheme 1, it is characterized in that, also comprises Interface status module, and described Interface status module is determined the ready grade of interface based on workflow status,
Wherein, described compilation module is based on described ready grade compilation product.
15. as the interface control module of technical scheme 1, it is characterized in that, also comprises that interface is searched and analysis module, and described interface is searched with the interface of analysis module based on being associated with product and searched the product line storer of described product and analyze described product.
16. as the interface control module of technical scheme 1, it is characterized in that, the first version of second version of described interface compilation module based on described supplier's module but not described supplier's module and based on described the first link described supplier's module of compilation and described consumer's module
Wherein, the date issued of described first version is before the date issued of described the second version.
17. as the interface control module of technical scheme 16, it is characterized in that,
Described first version is linked to the first data object but is not linked to the second data object; With
Described the second version is linked to described the second data object but is not linked to described the first data object.
18. as the interface control module of technical scheme 17, it is characterized in that, the third edition of described interface compilation module based on described supplier's module originally collect described supplier's module and described consumer's module,
Wherein:
The date issued of described the second version is before the date issued of described third edition basis;
The described third edition is originally linked to described the second data object;
The second version of described supplier's module is that the first version based on described the second data object collects; With
The third edition of described supplier's module is originally that the second version based on described the second data object collects.
19. as the interface control module of technical scheme 1, it is characterized in that, described interface Observation Blocks shows the link between each module of multiple control modules and shows the link between described multiple control module on display.
20. 1 kinds of product line administration modules, comprise according to the interface control module of technical scheme 10, and comprise:
Display; With
The product line storer of memory interface contract.
Further range of application of the present disclosure will become clear in the detailed description providing from behind.Should be appreciated that and describe in detail and concrete example is all only for illustration purpose but not be intended to limit the scope of the present disclosure.
Accompanying drawing explanation
To understand more completely the disclosure from the detailed description and the accompanying drawings, wherein:
Fig. 1 is according to the functional block diagram of a part for the Content Management System based on product line of embodiment of the present disclosure;
Fig. 2 is the functional block diagram of the Content Management System based on product line of Fig. 1;
Fig. 3 is the product line procedure chart according to embodiment of the present disclosure;
Fig. 4 is according to the functional block diagram of the production system that comprises product line administration module of embodiment of the present disclosure;
Fig. 5 is according to the functional block diagram of the product line administration module with multiple administration and supervision authorities of embodiment of the present disclosure;
Fig. 6 is the exemplary Content Management framework based on product line according to embodiment of the present disclosure;
Fig. 7 is exemplary products exploitation and the process of establishing according to embodiment of the present disclosure;
Fig. 8 is the exemplary products linear system row issue matrix according to embodiment of the present disclosure;
Fig. 9 is the exemplary engineering exploded view according to embodiment of the present disclosure;
Figure 10 is the exemplary loop engineering window (ring project window) according to embodiment of the present disclosure;
Figure 11 is exemplary Bill of Material (BOM) (BOM) window according to embodiment of the present disclosure;
Figure 12 distributes window according to the exemplary persona of embodiment of the present disclosure;
Figure 13 is the exemplary loop entitlement configuration management window according to embodiment of the present disclosure;
Figure 14 is the exemplary products line properties window according to embodiment of the present disclosure;
Figure 15 checks window according to the exemplary loop of embodiment of the present disclosure;
Figure 16 is the life cycle figure according to embodiment of the present disclosure;
Figure 17 is the interface control system according to embodiment of the present disclosure;
Figure 18 is the interface data model according to embodiment of the present disclosure;
Figure 19 is the level interface schema according to embodiment of the present disclosure;
Figure 20 is the example interface contract according to embodiment of the present disclosure;
Figure 21 is the many interface schemas according to embodiment of the present disclosure;
Figure 22 is according to the figure of the multiple interface contracts of the diagram of embodiment of the present disclosure;
Figure 23 is according to the logical diagram of the control module of utilizing the generation of interface data model of embodiment of the present disclosure;
Figure 24 be according to another embodiment of the present disclosure with the different and logical diagram of the multi-control modular system of control module independently;
Figure 25 is according to the logical diagram of the multi-control module product of the logic interfacing between the multiple control modules of being shown in of another embodiment of the present disclosure; With
Figure 26 is the view of the product collection of the multi-product of product line series engineering.
Embodiment
Following description is only exemplary in essence, is never intended to limit the present invention and application or purposes.For purposes of clarity, will use identical label to represent identical element in the accompanying drawings.As used herein, at least one in phrase A, B and C it should be understood that the logic (A or B or C) of having used nonexcludability logical "or".Should be understood that, in the situation that not changing the principle of the invention, the step in method can be performed with different orders.
As used herein, term module refers to processor (shared, special or cluster) and/or storer, the combinational logic circuit of special IC (ASIC), controller, electronic circuit, the one or more software of execution or firmware program and/or other suitable assembly of institute's representation function is provided.
In addition, multiple variable mark and value are disclosed in the following description.These variable marks and value are only as example.Variable mark be arbitrarily provide and can each for indicating or indicate different items.For example, variable mark N can be used for indicating multiple modules or indicates multiple interface contracts.This value is also also can varying depending on the application of providing arbitrarily.
The proprietary content of public and product of managing the control module of for example vehicle is a challenge.Control module can be developed and have the increase formula issue of some versions and the work product being associated in the time range of several years.System and method described below provides the framework of support for the each side of the some dissimilar Content Management of multiple product lines of complicated type spectrum.
In Fig. 1, show a part for the Content Management System (PBCMS) 10 based on product line.PBCMS10 can be described as the globally accessible application of the Content Management based on product line (ASPEN) system.PBCMS10 provides and has controlled product line Governance framework under development environment with management development data.PBCMS10 also provides Data lifecycle management system, and this system can be used for the information of exploitation, management, link, integrated and trade-to product content.That the information of product content can comprise record and/or exploitation for the information of feature, object, assembly and interface and for the control exploitation based on product line, set up, the information of test, calibration and checking object.PBCMS10 provides for developing, algorithm and the software of integrated, calibration and checking product.Fig. 2 also illustrates the structure of PBCMS10.
PBCMS10 comprises the remote-control device 16 of application server 12, product line storer 14 and any amount.Application server 12 is positioned at middle position and comprises that product line administration module 18 is with the product of management product line style spectrum and the content being associated.Application server 12 can be by any access of remote-control device 16.
Term " product line " can refer to the one or more methods for the public and modified characteristics of all different products of complex management product type spectrum.Product line can refer to specific product and corresponding module and content thereof.Product type spectrum can comprise hundreds of product.These products can be similarly, for example various control modules, but each is unique.Public characteristic is that share in two or more products and/or identical feature.Modified characteristics is be for example used in the first product but not be used in the feature in the second product.Modified characteristics can be the feature that is exclusively used in individually single product or single product group.
Application server 12 comprises product line administration module 18, content management software exploitation (CMSD) module 20 and application server for storage device 24.CMSD module 20 comprises and can be used for producing developing software of customized software.Product line administration module 18 provides the software development support that comprises versioned, expansion etc.Product line administration module 18 provides each layer-management of product line, and its band is useful on " fine granularity " object decomposition that efficient data is shared.Administration and supervision authorities are shown in Figure 5.
18 storages of product line administration module management data relation are to provide the analysis ability (comprising tracking power) for the various products of whole product type spectrum.Product line administration module 18 provides band to be useful on the Method and kit for of the prediction bug check of efficient and positive lock and object, the public and data that modified characteristics is associated including public and modification assembly and interface.Data can comprise BOM software, component software, interface software, data dictionary entry, arthmetic statement file, source code, automatic coding etc.Data dictionary entry can refer to for example, data about the manual input of assembly, interface or the consumer that is associated special parameter (engine speed) used.Consumer is described below.Automatic coding can refer to the code being produced by (based on model) code generator.
Can be by thousands of assembly and combination of interfaces to set up specific control module.Assembly can be for example for example, for carrying out module and/or the particular code collection (, Electronic Throttle Control module, cruise control module, cylinder deactivation module, engine speed determination module etc.) of a certain task and a certain group task.Interface can refer to the interface of each intermodule that a certain parameter is provided of control module.As example, interface can be between engine speed determination module and cruise control module.Engine speed determination module and cruise control module can be parts for engine control module.Engine speed determination module can provide present engine speed to cruise control module.Interface can be used and with reference-to storage and by the second module, be obtained the parameter being stored in storer by the first module.Interface between control module can be associated with message, and this message can transmit or transmit between control module, for example, between engine control module and transmission control module.
Each assembly and interface can have the object being associated, and this assembly or interface are identified and defined to this object, comprise the attribute of identifying this object.Attribute can comprise that object, module name, classification, measuring unit, type, minimum and maximum magnitude, minimum and ultimate resolution, initial value, one or more style (being one or more modification), the calibration of such as assembly divide etc.Multiple attributes of object can be defined by data dictionary entry (DDE).Application server for storage device 24 is stored content management software development library 26, and it is used by CMSD module 20 and product line administration module 18.
Application server 12 and product line storer 14 provide central data bank with access product line information.Application server 12 and product line storer 14 provide to for reusing, derive, the single information source of improvement and/or refinement the work product automatic coding of specific control module (for example for).Product line storer 14 manages for storing with product line the product line data that are associated.Product line storer 14 can be stored the software and the data that are associated with CMSD module 20 and/or product line administration module 18.
Remote-control device 16 comprises user interface 30 and product line control module 32.Each comprised keyboard, display, mouse and/or other user's interface device for communicating by letter with product line control module 32 in user interface 30.Product line control module 32 is communicated by letter with application server 12 by wired and/or wireless link.Remote-control device 16 allows various slip-stick artists, such as design engineer, Developmental Engineer, sets up the remote accesses such as slip-stick artist, BOM Engineer and uses application server 12 and obtain the data and/or the software that are stored in product line storer 14.
As used herein, the BOM of simple form can refer to feature inventory, for example, for forming the assembly of product and the inventory of interface (wherein each has specific function or function group).Product line control module 32 allows slip-stick artist's access application server 12 and designs and/or set up product, for example control module.BOM can also comprise regular group, and this rule group is identified the feature in the version that is included in ring; Be included in the version in ring style; Be included in the ring style in group style, be included in the group style in control system; Be included in control system in product etc.Rule group can comprise other BOM relevant information, for example feature, assembly and interface message.
Product can refer to control module (for example, engine control module, transmission control module, hybrid power control module etc.).The exemplary formation step by step of control module has been shown in Fig. 7.Each control module of product type spectrum has one group of selected group style, each group of style has one group of selected ring style, and each ring style can have one group of ring style child release, and each ring style child release has a stack features (for example, assembly and/or interface).Assembly, interface, group style and ring style further describe hereinafter.
Product line administration module 18 and/or product line control module 32 can allow for example design engineer's design and/or (for example select component software, cruise and control software object and code, cylinder deactivation software object and code etc.) and/or interface to set up control module based on BOM.BOM can be stored in product line storer 14.Example interface is and the parameter interface that (such as engine speed, temperature, oil pressure etc.) are associated is provided.Interface can be between hardware and software element or between software module.Interface can refer to identification and be produced and the signal of reception or the object of output by hardware unit and/or software module.Based on selected feature, assembly and/or interface, set up slip-stick artist then addressable PBCMS10 to start based on selected public and modified characteristics the generation that control module is set up.Public and modified characteristics can comprise component software and/or the interface by design engineer, selected.This and other example further describe hereinafter.
PBCMS10 allows early stage input feature vector, assembly and interface requirement and the data entry in product development, and BOM automatically upgrades for the downstream in manufacture process and upgrades.Data in the early stage input of manufacture process can be reused several times in the downstream procedures in manufacture process.Between different product and in the downstream procedures of the manufacture process of single product, all implement to reuse.PBCMS10 provides " fine granularity " management of the feature, assembly and the interface that are associated with the control module of each product or production.PBCMS10 produces BOM to allow assembly and the automatic of interface between ring style, group style, control system, produce sector, vehicle etc. to share and upgrade.Data after the early stage fine granularity management of manufacture process has stoped in manufacture process are manually inputted.As example, when engine speed determination module is updated, comprise these engine speed determination modules and/or utilize from the BOM of the control module of the engine speed signal of these engine speed determination modules and be automatically updated.
PBCMS10 allows newly-established version to replace existing version automatically to produce ring style new and/or that upgrade, group style, control system and/or control module.This has saved the time and has stoped chaotic behavior and/or stoped inconsistent in BOM.Inconsistent in BOM, for example inconsistent in version that can use and ring styles needs, can postpone or stop the foundation of product and/or cause mistake in the product of having set up.
Refer again to now Fig. 2, show the exemplary construction of PBCMS10.PBCMS10 comprises application server 12, product line storer 14 and one or more remote-control device (in remote-control device 16 has been shown in Fig. 1).Application server 12 comprises product line administration module 18, CMSD module 20 and application server for storage device 24.Product line administration module 18 can comprise algorithm management module 40, non-vehicle-mounted administration module 42, calibration module 44 and test case administration module 46.Remote-control device 16 comprises product line control module 32, and product line control module 32 can comprise algorithm management module 50, non-vehicle-mounted administration module 52, calibration module 54 and test case administration module 56, and these can be corresponding with the item separately in administration module 40-46.
The addressable one or more external tools 58 of control module 50-56.External tool can be stored on remote-control device 16, in application server for storage device 24, in product line storer 14 and/or can be stored in that other is local and can be accessed by remote-control device 16.
Algorithm control and management module 40 and 50 can be used for producing software algorithm.The addressable external tool of algorithm control module 50, for example computational language Software tool (for example, Matlab).Non-vehicle-mounted control and administration module 42 and 52 can be used for producing for example diagnostic software.Calibrate control and management module 44 and 54 for generation of calibration software and/or calibrate assembly, version, ring style, group style, control system and/or the product set up.Calibration control and management module 44 and 54 addressable external tools, for example calibration instrument instrument.
Test case control and management module 46 and 56 is for generation of testing software and/or test the item of having set up, for example one or more assemblies, interface, version, ring style, group style, control system and/or product.Test case control and management module 46 and 56 addressable external tools, for example, for testing the test board of built vertical item.
Product line control module 18 is supported user interface 30 and provides to show and open ability.Product line administration module 18 provides the combination of life cycle data, data analysis, data translation, data reusing, data link and data sharing ability.
Application server 12 and product line storer 14 can pass through remote-control device 16 by global access from each geographic position.One or more in remote-control device 16 can be with application server 12 at same position.Product line storer 14 can be the central data bank of the content information based on product line.Product line storer 14 comprises various databases.These databases can comprise algorithm data-base 60, non-vehicle-mounted data storehouse 62, calibration data base 64 and test case database 66, and they can be corresponding to control and management module 40-46 and 50-56.Database also can comprise the database being associated with the administration and supervision authorities of PBCMS10, for example mapping database 68, BOM database 70, entitlement database 72, assembly and interface database 74, level and decomposition data storehouse 76, life cycle management database 78 and other database 80.Database 68-80 one-tenth individual data capable of being combined storehouse.Database also can comprise that for example software produces, control and management database 82, and these databases 82 are stored for example CMSD module 20, product line control and management module 40-46 and 50-56 (being designated as 82) and other module 84.
In Fig. 3, show product line procedure chart.The development and production of product can comprise different phase, and for example algorithm changes demand (ACR) or algorithm incipient stage 90, algorithm stipulations stage 92, implement software stage 94, software establishment stage 96, test and Qualify Phase 98, calibration phase 100 and validation phase 102.Can be based on including carrying out and management phase 92-102 from the information regular group of product line administration module 18.One or more BOM that product line administration module 18 can be based on received and the serial issuing time being produced by factory management module (FMM) 104 produce above-mentioned information and regular group.
ACR or algorithm incipient stage 90 can be called as demand stage and can comprise the input of engineering demand, calibration data, variable, interface message and/or data dictionary entry.The algorithm stipulations stage 92 comprises information based on inputting in demand stage and/or based on arthmetic statement file (ADD) and the assembly of design defect pattern impact analysis (DFMEA) report and/or the design of interface.DFMEA report can be produced by product line administration module 18.
The implement software stage 94 comprises for the code development of assembly or sub-product and structure; Each in assembly or sub-product has corresponding code set.The implement software stage 94 can be based on being produced by product line administration module 18 software information and be performed.Software information can comprise the scope of Interface Engineering automatic coding, interface layer automatic coding, data object automatic coding, consistent calibration division information, initial value and test case.Automatic coding refers to by product line administration module 18 based on BOM and the selected ring style code of generation automatically.
Software establishment stage 96 comprises and is compiled in the code set producing in implement software stages 94 process to set up product.In this stage, software collection is combined and compiled.Combination can be set up information and carry out based on what produced by product line administration module 18.The information of foundation can comprise calibration division document, calibration range boundary, descriptor, software compilation information and set up automatic information.
Controller test and Qualify Phase 98 comprise test and the checking of the product to producing at software establishment stage 96.Test and Qualify Phase 98 can be based on being produced by product line administration module 18 authorization information and be performed, these authorization informations are for example scope, initial value, calibration and the variable change of the test case issued from upper one (last).
Calibration phase 100 comprises the calibration of the product to test in test and Qualify Phase 98 and checking.Calibration phase 100 can be based on being produced by product line administration module 18 calibration information and be performed, for example set up product, responsibility matrix, laboratory document, the calibration variation from upper one (last) issue and the calibration users' guidebook that upgrades.Validation phase 102 comprises coming into force to the product at calibration phase 100 alignments.After the validation phase, product can be published.This can be described as launch phase.
In Fig. 4, show production system 120.Production system 120 comprises product line administration module 18 ', technique computes system 122, and embedded coding module 124.Product line administration module 18 ' comprises code and BOM maker module 126 and configuration management (CM) cooperative module 128.The addressable product line storer 14 of product line administration module 18 '.The data that received and produced by code and BOM maker module 126 and CM cooperative module 128 can be stored in product line storer 14.
Code and BOM maker module 126 receive the engineering demand being associated with one or more products, for example engineering demand of the assembly to specific control module and interface.Engineering demand can comprise for example, by slip-stick artist (Developmental Engineer) initial DDE and the interface message (IF) producing.Engineering demand can be supplied directly to product line administration module 18 ', as signal DDE+IF 1shown in, or can be provided by technique computes system.As example, technique computes system 122 can be moved based on Matlab, receives demand model and DDE and IF are provided to product line administration module 18 '.This is by signal DDE+IF 2illustrate.Code and BOM maker module 126 can be provided for the placeholder of development data and other work item.
Code and BOM maker module 126 produce various types of codes and engineering information based on engineering demand.Code and engineering information comprise DDE and IF source code, interface layer automatic coding, data object automatic coding, DDE and IF arthmetic statement file, Interface Engineering, product line and control module BOM, the report of DFMEA template, as shown in corresponding signal DDE+IF3, ITAutucode, DOAutocode, DDE+IFADDs, IFProjects, PLCBOMs and DFMEA.Signal DDE+IF1 that can be based on received and DDE+IF2 and/or the product line BOM management data being received by code and BOM maker module 126 produce these signals.Product line BOM management data can refer to the data or the demand that from the BOM manager of the system-level structure of management product engineering, receive.
Embedded coding module 124 produces engineering automatic coding ProjectAutocode based on signal DDE+IF3.CM cooperative module 128 is based on select the product of module 130 to select the signal product that collects from product.Product selects module 130 to operate by for example setting up slip-stick artist.Selecting after product, CM cooperative module 128 is based on DDE+IF3, ITAutocode, DOAutocode, DDE+IFADDs, IFProjects and/or BOM signal compilation product.This product also can the hand weaving code based on being received by CM cooperative module 128 collects.
In operation, code and BOM maker module 126 are caught the assembly of one or more products (for example one or more control modules) and data object, demand for control and the feature of interface.This is included as each product acquisition loop style information, version information, group style information, subsystem or control system information etc. to produce PLCBOMs.Only, as example, code and BOM maker module 126 can be associated with the first and second periods of exploitation and process of establishing, as shown in Figure 7.CM cooperative module 128 can be associated with the 3rd of exploitation and process of establishing, the 4th and the 5th period.
In Fig. 5, show the product line administration module 18 with administration and supervision authorities ", for example, in the product line administration module 18 in Fig. 1-4 and product line administration module 18 ' one.These administration and supervision authorities provide the support to fine granularity object by the development data managerial ability of every layer.Each administration and supervision authorities can be single different administration module, one group of dedicated management module, or can be arranged in Sharing Management module.One or more administration modules of the first administration and supervision authorities can be shared by the second administration and supervision authorities.Multiple administration and supervision authorities can be provided by single administration module.Administration and supervision authorities comprise product line administration and supervision authorities 140, BOM administration and supervision authorities 142, ownership management layer 144, level and decomposition layer 146, mapping and relation management layer 148 and Version Control and life cycle management layer 150.
Product line administration and supervision authorities 140 provide product line framework, by this product line framework, can implement exploitation and the process of establishing of product for the BOM being associated date issued.Product line Governance framework can comprise product line hierarchy management and stream special (series issue) and the special BOM management of control module.The example of product line framework has been shown in Fig. 6.The example of exploitation and process of establishing has been shown in Fig. 7, and this process can be managed by product line administration and supervision authorities 140.The function of product line administration and supervision authorities 140 is further described with reference to the framework of Fig. 6.
BOM administration and supervision authorities 142 allow product line BOM generation and the management of (comprising product BOM and control module BOM).BOM administration and supervision authorities 142 produce the exploitation that for example can be used for as shown in Figure 7 and the BOM rule group of process of establishing.When selecting the feature of version and content and can service regeulations group when each content-level item of compilation product.Content-level item can comprise ring style, group style, control system.According to product line BOM and/or the product line BOM rule group compilation content-level item that is associated.
Ownership management layer 144 is used to record the entitlement of each content-level item, such as the entitlement of each assembly, interface, ring style, group style, control system etc.Data and/or code-group can belong to or be assigned to one or more individualities.Each owner can have distribution role, and this distribution role can be by ownership management layer 144 record.The example of entitlement configuration management layer window is shown in Figure 13.
Level and decomposition layer 146 can be used for producing and manage production algorithm content (PAC) level or tree for series, type year, issue and step.Series, type year, issue and the step of product are indicated by a series of values, and for example, 11.10.2.1 refers to 11 series, type year 2010, issue 2 and the first step and readjusts the distribution cloth.When step is 1, pace value can not used when identification specific PAC, engineering and/or product.The level of example and the decomposition being associated are shown in Fig. 9,10 and 14.
Mapping and relation management layer 148 for example, for setting up the relation between BOM and content-level item, between BOM, assembly, interface, version and/or ring style.Mapping and relation management layer 148 can be called as software configuration administration and supervision authorities.These interfaces can have the message that is associated of for example transmitting between control module.Exemplary ring style distributes window shown in Figure 12.
Version Control and life cycle management layer 150 issue and the cut-off date for managing version and recording each version.When a upper version is changed, redaction or baseline version can be established.After predetermined amount of time and/or when redaction is established, product administration module can be freezed (prevention is changed) specific version.Version Control and life cycle management layer 150 can be identified state and the stage of particular version, comprise that whether version is in exploitation, foundation, calibration and/or checking.Version and life cycle management figure are shown in Figure 16.
Product line administration module 18 " can support " directly " to write mechanism, such as office tools, graphic user interface (GUI), third party's application etc.Product line administration module 18 " can comprise provide this support directly write layer and/or module.
In Fig. 6, the Content Management framework based on product line being provided by the PBCMS10 shown in Fig. 1 and 2 is provided the frame diagram illustrating.Storage Content Management framework based on product line is for generation of the product line BOM can be used in development and production process.Content Management framework based on product line allows the definition role of the proprietorial identification of the input of public and modified characteristics and management, public and modified characteristics and record, public and modified characteristics, ring style, group style, control system, etc.This can be shown by one or more common configuration windows (showing example arrangement window 148).
Engineering BOM150 and control module BOM152 produce based on inputted information.The engineering BOM of the product line BOM154 of particular delivery based on being associated and/or the control module BOM being associated and product line issue matrix 155 produce.Then product line BOM154 can be used for producing BOM rule group (for example, describe with reference to the embodiment of Fig. 7 regular group) and set up product in one or more exploitations and process of establishing, as shown in product development and process of establishing Figure 156.
In Fig. 7, show exemplary products exploitation and process of establishing.In one embodiment, product development and process of establishing be based on software and for exploitation with set up control module.Product development and process of establishing can comprise five periods.The first and second periods can be by product line administration module 18 " ' management, for example product line administration module 18,18 ', 18 based on product line BOM " in one.Three, the 4th and the 5th period can be by product line administration module 18 " ' carry out automatically to set up for example control module based on product line BOM.
Interim at first o'clock, be assigned to the addressable PBCMS at remote-control device place of Developmental Engineer of special characteristic (for example specific components and/or interface) to define and/or to produce this feature and the message being associated.This feature and the message being associated can be used the technique computes system 122 of for example Fig. 4 to define.This feature and the message being associated can produce based on identifying a BOM rule group of the version that be associated with this feature.Application server can provide a BOM rule group to this remote-control device.This allows to PBCMS input and by PBCMS exploitation and management object, assembly, interface, feature, message etc.
Feature can have version (for example, the V of any amount 1, V 2... Vn, wherein n is integer).Version V2 issues after version V1, and version V3 issues after version V2, etc.Each extra version upgrades on last version.The construction cycle being associated with each version can partly overlap.For example, be that the cruise control module that 2011 and 2012 vehicle models are developed can be developed in the same time cycle.
Interim at second o'clock, the feature 160 of feature group 162 is associated with each ring style version 164 of ring style group 166, from product line memory copy, and combines.Exemplary ring style is fuel control loop, spark control loop, emission control ring etc.The feature being associated with this version, for example assembly and/or interface, the 2nd BOM rule group that can be based on being provided by product line BOM is by slip-stick artist or by product line administration module 18 " ' select.Produce the version of each ring style.The two BOM rule group of these versions based on from product line BOM and being associated with each ring style.The second period can be by product line administration module 18 " ' automatically perform or feature selecting input that can be based on slip-stick artist's input and being performed.
Interim at the 3rd o'clock, based on the group style version 168 of setting up vertical group style group 170 from the 3rd BOM rule of product line administration module.Exemplary group style comprises moment of torsion, engine, platform, vehicle etc.Product line administration module 18 " ' based on the 3rd BOM rule group, selected ring style is combined to set up group style.
Interim at the 4th o'clock, based on from product line administration module 18 " ' the 4th BOM rule set up the control system version 174 of vertical control system group 176.Product line administration module 18 " ' based on the 4th BOM rule group, selected group of style combined to set up control system version.Exemplary control system is powertrain control system.
Interim at the 5th o'clock, based on from product line administration module 18 " ' the 5th BOM rule set up vertical control module 178.Product line administration module 18 " ' based on selected one or more control system and the 5th BOM rule group compilation control module.Exemplary control module is engine control module, transmission control module and hybrid power control module.Five BOM rule group can be that differ from one another and independent of each otherly maybe can interdepend and/or can be a part for single BOM rule superset.
Although the specific style identifier (ID) for control system, group style, ring style and feature is provided herein, and these ID, only for example object, also can be used other ID.In addition, although for the style in concrete level content-level provides an ID, this ID is alternatively for identifying the style in different level content-level.For example, cruise to control and can be the assembly in the layer 5 level content-level of Fig. 9 or can be the group style in the 3rd level content-level as shown in figure 14, and there is corresponding ring style and feature.Term " level content-level " is here referred to as " level ".Every one-level or level branch can refer to for example, for example, content for specific supplier (, supplier's module) or consumer's (, consumer's module).Supplier and consumer will describe below with reference to Figure 17.
In Fig. 8, show exemplary product line series issue matrix 200.Product line series issue matrix 200 is three-dimensional matrices, and wherein these dimensions are main issue, type year and step.Product line series issue matrix 200 also can be identified the version number of each issue.Step issue refers to two issues between main date issued.Product line series issue matrix is used when the product line BOM snapshot of setting up for developing and set up product.Each three items of value (for example 08.08.21) can refer to the version for the specific products on particular delivery date and/or the feature of this product.
In Fig. 9, show exemplary engineering exploded view.Engineering exploded view could for example be produced and belong to this project exploded view information by level and decomposition layer 146 can be stored in database 68,70 and 76 one or more.Engineering exploded view the level being provided by PBCMS and/or product line administration module is provided and configures, for example, by PBCMS10 or product line administration module 18,18 ', 18 ", 18 " ' in one provide.Show some different levels.Every one-level can be associated with particular file folder or sub-folder group or by its representative.First or the superlative degree be product algorithm content (PAC) series level.PAC series level can for example refer to control module or control module group (such as engine control module, transmission control module, hybrid power control module etc.), the content of control module and/or the particular series of control module.Every one-level of level configuration can comprise the level branch of any amount.The first order branch of the first order can refer to a for example PAC, and the first order branch of the second level can refer to the 2nd PAC.
One or more second level under the first order comprise one or more product line levels and/or one or more BOM level.Product line level can refer to control module.Level under product line level can be identified the content of the product that can be used for this product line level.BOM level can comprise engineering BOM, control module BOM, product BOM etc.One or more third level under the second level are group style levels.One or more fourth stages under the third level are ring style levels.Under the fourth stage one or more the stepless be feature level, for example feature, interface level (for example form interface layer (FIL) level) and component level.
In Figure 10, show exemplary ring engineering window 230.The information that belongs to engineering window 230 can be stored in database 68,70 and 76 one or more.Engineering window 230 comprises left-hand side (LHS) 232 and right-hand side (RHS) 234.LHS232 provides to the access path of product line hierarchical tree, and this hierarchical tree is called as superset sometimes.Group style, ring style and/or feature can be selected and can on RHS234, see the description of selected style or feature on LHS232.As example, show just at selected phase device ring (PHSR).For PHSR, various items can show with the owner of the state of the style being associated, version, version, each item and date issued.Exemplary item list is shown in Figure 10.Sample list comprises ring level view, consumer's interface, interface layer, work document and PHSR function.
In Figure 11, show the exemplary bill of materials (BOM) window 240.The information that belongs to BOM window 240 can be stored in one or more in database 68,70 and 76.BOM window 240, as shown, for control module and comprise group style choice box 242 and ring style choice box 244.Group style choice box 242 provides the phase strain type of group style list and each style.Ring style choice box 244 provides the list of ring style and corresponding modification.
In Figure 12, show exemplary style and distribute window 250.Style distributes window 250 to be provided and the information that belongs to style distribution window can be stored in one or more in database 68,70 and 76 by mapping and relation management layer 148.Style distributes window 250 to comprise LHS252 and RHS254.LHS252 has the product line hierarchical tree for group, ring and/or feature selecting.RHS254 comprises the item list with version row.This item list is shown in Figure 12 and comprise interface and/or function.Version row are designated as FUNC (for function), MSG (for message) and NF (for non-function).Version row comprise the choice box for selecting item, and the input signal of these items based on user is comprised in each version and is listed as in the each version being associated.In the example illustrating, item comprises the distinct interface for phaser ring style.Version row comprise function row, message column and non-function row.
For each phaser ring interface, function, message and/or non-function can be selected.When selecting certain function at choice box, this function is just provided to particular version.This message when selecting certain message at choice box (signal being associated with this interface is provided to another control module).When non-function choice box is selected while not carrying out this function with indication, this function is not provided to particular version.For example, the product of certain version may not have Electronic Throttle Control, so some function may not be provided.Choice box in non-function row is selected to stop this function to be provided.
In Figure 13, show exemplary ring ownership management window 260.The information that belongs to ring ownership management window 260 can be stored in database 68-78 one or more.The LHS262 that ring ownership management window 260 comprises with the list of ring style.The RHS264 that ring ownership management window 260 also comprises with territory and analog value.These values indicate the owner of title, type specification and institute's ring selection style.The owner in RHS264 is worth frame can be selected to open owner's entry window 266.Owner's entry window 266 allows owner ID to be changed and increases and/or remove the owner.The owner refers to the people who is responsible for this specific ring style.The owner can be provided to content-level item, such as control module, control system, group style, ring style, feature, BOM etc.
In Figure 14, show exemplary product line properties window 270.The information that belongs to product line properties window 270 can be stored in database 68,70,76 one or more.Product line properties window 270 illustrates product line BOM.Product line properties window comprises LHS272 and RHS274.LHS272 provides product line hierarchical tree.RHS274 provides item list and corresponding style, version, state, the owner, date issued etc.Item shown in Figure 14 is group style.
In Figure 15, show exemplary ring and check window 280.Belong to ring and check that the information of window 280 can be stored in database 68,70,76 one or more.Ring inspection window 280 can be selected and open from ring engineering window 282.Ring checks that ring style title, ring style upper strata (for example organizing ID), the interface of consuming, interface layer, the interface providing, calibration, variable, constant, type, quantity (slews), work document, ring style function and the version being associated, state and proprietorial attribute are provided in window 280 identifications.These attributes can accessed and change.Some attribute can be opened to obtain extra information.For example, ring style function can be opened (for example double-clicking the respective block in window 280) to obtain function definition.The change of these attributes can be carried out by the people who has mandate, for example owner and/or system manager.This can comprise user ID and/or password.
In Figure 16, show exemplary life cycle Figure 30 0.Product line administration module, for example module 18,18 ', 18 ", 18 " ' in one, via Version Control and life cycle management (VCLC) the layer 150 each object of management and the features that are associated.Life cycle management information can be stored in database 68,70,76,78 one or more.Each object and the feature being associated are managed independently.Version Control is followed the trail of parallel issuing with series with life cycle management layer 150.In Figure 16, issued in parallel refers to the feature of exploitation when another version of same feature or product is developed or the version of product.As example, in Figure 16, version issue 11.12.1.1 is developed in version issue 11.11.3.1 exploitation.The second version of exploitation after the first version at this feature or product that serial issue refers to feature or product is developed.As example, in Figure 16, version issue 11.11.2.1 is family release, because its exploitation after issue 11.11.1.1.
PBCMS, for example PBCMS10, provides revision and Version Control ability.VCLC layer 150 is for revising the version of previous generation.VCLC layer 150 also can be used for copying and improving or upgrades previous version to set up redaction.VCLC layer 150 can be carried out branch and the merging of version.In Figure 16, by providing branch based on version 11.10.2.1 generation version 11.12.1.1 and 11.11.1.1.In Figure 16, by merging version 11.10.2.22 and 11.11.2.1, set up version 11.12.1.1.Each object and/or associated features can be identified by unique ID.This unique ID can keep locking to all versions.Each object and/or the feature being associated also can have user-defined title, and this title is attribute and can between version, changes.
PBCMS10 is enable system engineering and structure management in tissue.In exploitation and process of establishing, the knowledge of early stage invention is hunted down and maintains to prevent its loss.PBCMS10 stops data to be inputted again, the confusion during content of management product type spectrum, and the problem that stops the collaborative problem between slip-stick artist and/or be associated with feature, assembly, interface etc.PBCMS10 also allows data reusing, the integrated and robotization in product development and transmission.In exploitation and process of establishing, provide in early days stable data group.
PBCMS10 allows the light management to complex product type spectrum, be convenient to and simple and stable global collaboration is provided, realize the robotization of product development and foundation, what allow the enforcement of product and the basis of inspection, integrated data and process and allow data reuses to improve output and quality.
In Figure 17, show interface control system 350.Interface control system 350 comprises product line administration module 18 iV, product line administration module 18 iVcomprise interface control module 352.Interface control module 352 comprises url management module 354, interface contract module 356, Product-level interface module 358 and interface Observation Blocks 360.One or more products and the product line series issue engineering being associated can comprise the superset of interface.Interface control module 352 for developing in exploitation and/or the different phase of manufacture process, manage, store, reuse, observation and analysis interface.
Link generation module 354 produces the link between supplier's module and consumer's module.Supplier's module, for example, refers to the module that produces parameter value, and this parameter value is provided to consumer's module.Module can the person of being to provide, consumer and/or supplier and consumer.Can produce link and point to supplier's module from consumer's module.Supplier's module can produce parameter signal, and this parameter signal is received by consumer's module.This is shown in Figure 18.
Interface contract module 356 produces interface contract 361, and interface contract 361 is created between supplier's module and consumer's module.Can be by supplier's module (being called server end) defining interface contract when supplier's assembly is executed the task for consumer's module (being called client).Interface contract can be defined by the one or more reusable standalone object entry in tool database 363, product line storer 14 ', and/or is defined by interface contract module 356.Each interface contract is associated with one or more products (control module), and wherein product is configured by the one or more BOM based on corresponding product line engineering.Product line administration module 18 iVbased on the special interface group of corresponding BOM compilation product.Interface contract can be stored in product line storer 14 '.
Each interface can be that specific product line issue (product) is signed and definition special also can comprising.Signature can be issue special and when interface is established, set up and can and also can identify the owner by interface ID recognition interface.Interface can have one or more modification.Modification can be assigned to the some different products in product line series.One group interface can be defined local assembly and the external module for module to be consumed and/or product in component level, ring level, group level or control system level.
Interface contract can be identified and define one or more suppliers and consumer's module relationship of one or more products and comprise supplier and consumer ID, interface definition object ID, related object ID, link ID, signal and/or message id etc.Interface contract can be between the each module between different and long-range control module, in control module, and/or between contract level item, control system, group style, ring style and feature etc.Interface contract can for example, in (between group style and ring style) between the content of the level of different layerings; The level of layering can be single control module or different control modules.Interface contract can be associated with the version of specific control module, supplier, consumer and/or control module or issue, supplier and/or consumer.Interface status module can be by interface flag (marking) for to be associated with specific products.The interface contract that some are exemplary has been shown in Figure 20-22.Interface contract can recognize link each level content-level and the level branch between supplier's device and consumer devices.Interface contract also can be identified linking of being associated with one or more interfaces, signal, message and/or data object.
Interface contract module 356 can be used for setting up new contract.Interface contract module 356 can be provided to first pre-contract link, copy first pre-contract (for example, first pre-contract being saved as to new contract) or not with reference to previous contract and produce new contract.Newly-established contract can be changed individually.This allows to reuse and inherit the contract version information of previous generation storage.In administration module, the ability of each interface provides the fine granularity of interface reuse and change.
Product-level interface module 358 records and identifies the interface that is used by the level of layering and/or be associated with the level of layering.The first order can have S sub level and consumer and/or the interface of S sub each had respective numbers of concentrating, and wherein S is greater than 1 integer.358 identifications of Product-level interface module are associated with the first order with each consumer who is associated in S sub level and interface.This will further describe in Figure 19.
Interface Observation Blocks 360 (product Observation Blocks) is before the compilation of product and/or after the compilation of product, on display 362, show logic and the Physical View of product.Display 362 can be positioned at one of them place of the remote-control device 16 of Fig. 1.This comprises logic and the Physical View of display module interface, control module and/or product.This allows deviser or slip-stick artist to observe work product in the commitment of design process.
Interface control module 352 or product line administration module 18 iVcan also comprise compilation module, for example interface compilation module 370, this module can collect control module, module, control system, group, ring etc.Interface control module 352 also can comprise that Interface status module 372 and interface searches and analyze (ISAA) module 374.Interface status module 372 is determined the workflow status of interface.The state of Interface status module 372 based on workflow determined the ready grade of interface.Interface compilation module 370 can be based on ready grade compilation product module and/or product.Interface status module 372 can produce consumption indicator signal and/or when issue indicator signal is ready for consumption enforcement and/or is ready for issue with indication interface.Consumption and issue indicator signal can be based on supplier and/or consumer workflow status.
ISAA module 374 is searched the product line storer 14 ' of interface the interface of analyzing stored.ISAA module 374 is based upon the interface of product foundation product is analyzed.This can occur in the early stage of design process.For example can analyze the control module shown in Figure 23-26 and product.Analysis can be included as product and one group of input of example is provided, based on this product and this input, produce output (comprising the run time version of product), and analyzes output based on input.Can carry out different analytic processes.Comprise test, calibration and proof procedure.
Referring now to Figure 18, wherein show interface data model 400.For the issue of each product, in product, can there is the link between thousands of suppliers and consumer.Interface data model 400 illustrated between supplier's (or Provider Interface) 402 and consumer's (or consumer's interface) 404 be associated with interface contract link and the example of signal or message.Link can refer to the connection between designator or consumer and the supplier from consumer to supplier.Each Provider Interface and consumer's interface can be the entities of linkable standalone version.Provider Interface can comprise interface definition object, data object and related object.Interface definition object, data object and related object are version objects.
PBCMS can have different control module BOM406.Each control module BOM406 can have supplier and consumer BOM modification 408,410.Supplier and consumer BOM modification 408,410 for example, be associated with supplier 402, consumer 404 and/or their interface definition object (interface definition object 412) and therefore with above-mentioned every link.Interface definition object 412 can be the data object being linked, and these data objects that are linked can be linked to related object.Two data objects 414 and a related object 416 are illustrated.Interface definition object can refer to and the assembly or the code-group that produce data object (for example parameter value) and be associated.For example, engine speed determines that assembly and function (being called getenginespeed ()) can produce engine speed value EngineSpeed, and wherein getenginespeed () is interface definition object and EngineSpeed is supplemental characteristic object.
As shown in Figure 18, interface definition object 412 can have multiple interface definition edition 4s 20, and wherein each interface definition edition 4 20 can be linked to one or more data objects, for example data object 414.Data object 414 also can have different edition 4 22.And each data object 414 can be linked to one or more related objects, for example related object 416, this related object can have corresponding related versions 424.Link between between supplier 402 and consumer 404, between interface definition object 412 and data object 414 and data object 414 and related object 416 can be produced and be stored by link generation module 354.
Show the virtual cpi person node 430 for the intergrade between supplier 402 and consumer 404.Dummy node 430 can refer to level or the level branch between supplier 402 and consumer 404.Virtual cpi person node 430 is associated with above-described level mapping.Dummy node can refer to control system level, group style level and/or the ring style level between for example supplier 402 and consumer 404.Although link provides the direct mapping between supplier 402 and consumer 404, the signal providing between supplier 402 and consumer 404 or message can be through the levels of multiple layerings.
In Figure 19, show level interface schema.Level interface schema has illustrated the interface being associated with the ring style A of group A and the ring style B of group B.Ring style A can have assembly or interface definition object AC1-AC4, they each can with one or more being associated in interface I1-I7.Ring style B can have assembly or interface definition object B C1-BC4, they each can with one or more being associated in interface I1-I7.The node that system operator one of can be clicked in ring style A and B also can provide the interface list being associated with this ring style.For example, the node of ring style A can provide the list that comprises interface I1-I5, because these are and one or more interfaces that are associated in interface definition object AC1-AC4.Node can be dummy node, the node that is produced and stored by Product-level interface module 358 and/or the visual node that can be selected by system operator.
In Figure 20, show exemplary interface contract 450.Shown interface contract 450 represents the contract between the first and second assemblies 452,454 and interface definition object 456.The first and second assemblies 452,454 are used the data object 458 being produced by interface definition object 456.Only, as example, the first assembly 452 can be the Control Component that cruises, and the second assembly 454 can be fuel cut-off assembly.Each of cruising in Control Component and fuel cut-off assembly can usage data object, for example engine speed value.Show link and signal between assembly 452,454 and interface definition object 456.
In Figure 21, show many interface schemas.Many interface schemas have illustrated the link between multiple consumers 480 and Provider Interface defining objects 482.Each in consumer 480 can be used the one or more data objects 484 that produced by Provider Interface defining objects 482.Provider Interface defining objects 482 can have multiple edition 4s 86.According to consumer's version, the latest edition (example is version 11.10.21.00 as shown) that consumer 480 can automatic reception Provider Interface defining objects 482.This is due to the link between consumer 480 and Provider Interface defining objects 482 and the definition being associated.Similarly, each version of Provider Interface defining objects 482 can be linked to one or more in data object 484 and latest edition (the version 11.10.17.01 and the 11.10.21.00 that for example, illustrate) that can automatic reception related data object.
In Figure 22, show multiple interface contracts 500,502,504.Especially, show three interface contracts 500,502,504.Interface contract 500,502,504 can be separate and can be associated with multiple products and/or be copied and use by these products.First, second, and third interface contract 500,502,504 is associated with the first product.First and the 3rd interface contract 500,504 be associated with the second product.First interface contract 500 illustrated between the first assembly 506 and first interface defining objects 508 and the second assembly 510 and first interface defining objects 508 between contract.First interface defining objects 508 is linked to the first data object 512.
The second interface contract 502 is exclusively used in the first product also can be between the 3rd assembly 520 of the first product and the 3rd interface definition object 522.The 3rd assembly 520 can be that one of them in the first assembly 506 and the second assembly 510 maybe can be different from the first assembly 506 and the second assembly 510.
The 3rd interface contract 504 between the 5th, the 6th and the 7th assembly 530,532,534 and the 3rd interface definition object 536, the 3rd interface definition object linking to the three data objects 538.The 3rd interface definition object 536 can be identical or different with first interface defining objects 508.
With reference to Figure 17 and Figure 23, show the logical diagram of product 550 (being depicted as control module).Shown product 550 comprises physical interface layer 552, hardware extraction layer 554, serial communication layer 556 and the interface watch window 558 of software (SW) layer.Physical interface layer 552 can comprise the difference input 560 from for example sensor, converter and/or other control inputs device.Physical layer 550 can provide various output 562 based on input 566.Output 562 can be for example provided to actuator, valve etc. (such as phaser operation valve, Fuel Control System, spark ignition system etc.).Hardware extraction layer input 564 (for example hardware I/O HWIO) can input 560 generations based on Physical layer.Physical layer output 562 can produce based on hardware extraction layer input 564.The input and output of hardware extraction layer input and output 564,566 suppliers corresponding to control module 550 and consumer's module 570.
The logical diagram of Figure 23 has illustrated the link between supplier and consumer's module 570, and this can be observed by system operator.Interface Observation Blocks 360 can for example for example, provide the link interface view of control module 550 on display (display 362), for example as shown in figure 23.Interface Observation Blocks 360 can illustrate link not at the same level.As shown, link can be between supplier and consumer's module 570.Link can be between supplier supplier's module or consumer's module and consumer's module 572.For example, module X is as the supplier of module Y.Module X comprises submodule x1, x2 and x3.Module x1 is as the supplier of module x2 and x3.Model x2 is as consumer.Module x2 is as consumer and supplier.
With reference to Figure 24, show with the different and logical diagram of the multi-control modular system 600 of control module 602 independently.Multi-control modular system 600 can be vehicle control system, and this system comprises network 604, for example vehicle local network.Network 604 provides the communication between control module 602 in bus 606.Show each interface link view of control module 602.Shown multi-control modular system 600 can be observed on display 362.
Referring now to Figure 25, show the logical diagram with the multi-control module product 620 of the logic interfacing between multiple control modules 622.The SW layer of multi-control module product 620 comprises multiple control modules 622, and multiple control modules 622 can be integrated in single control module, as shown.Show the intermodule link 626 between internal chaining 624 and the control module 622 of each control module 622.Although shown, be single product, the figure of multiple products of Figure 24 is convertible into the figure of Figure 25 so that observe the mutual relationship of (being between control module) between product.Multi-control module product, for example multi-control module product 620, can observe at display 362.
In Figure 26, show the product group of multiple products 640 of product line series engineering.Multiple products 640 are depicted as control module.Each in product 640 is independent of one another, or each in product 640 can be the version being associated with single product.Product 640 can be associated with one or more engineerings.In one embodiment, each in product 640 is associated from different vehicle issues.Product line series engineering can be observed on display 362.
Interface management provides Organizational practices, cooperation and parallel software development, the assets (content) of the exploitation of functional and physical arrangement is reused and shared and support that software is integrated in software product line development environment as described herein.Interface management ability defines and management interface in functional demand and software design procedure step perspectively and dynamically.This has guaranteed stable cooperation and integrated in the case of complicated global software product line type spectrum.Interface management provides the mechanism of defining interface contract, between the communications component by interface contract in software systems, sets up and interacts.
Extensive instruction of the present disclosure can different forms be implemented.Therefore, although the disclosure has comprised particular instance, true scope of the present disclosure should not be so limited, because other improvement will become apparent those skilled in the art after study accompanying drawing, instructions and follow-up claim.

Claims (20)

1. an interface control module, comprising:
Link generation module, produces the first link between supplier's module and consumer's module;
Interface contract module, produces interface contract,
Wherein:
Described interface contract is corresponding to the interface that comprises the described first product linking; With
Described interface contract defines described interface based on Bill of Material (BOM) (BOM);
Interface compilation module, the module of compilation including described supplier's module and described consumer's module is to produce product; With
Interface Observation Blocks shows logic and the Physical View of described product on display at least one situation before the compilation of described product and afterwards.
2. interface control module as claimed in claim 1, is characterized in that, described interface contract comprises supplier's identifier (ID), consumer ID, interface definition object ID, link ID and data object ID.
3. interface control module as claimed in claim 1, is characterized in that, described interface contract is between characteristic element.
4. interface control module as claimed in claim 3, is characterized in that, described characteristic element comprises at least one in assembly and interface definition object.
5. interface control module as claimed in claim 1, is characterized in that, described interface contract is between the various level content-level item of BOM.
6. interface control module as claimed in claim 5, is characterized in that, described content-level item comprises two or more among control system, group style, ring style and feature.
7. interface control module as claimed in claim 1, is characterized in that, described supplier's module from described consumer's module in different BOM levels.
8. interface control module as claimed in claim 1, is characterized in that, also comprises Product-level interface module, and described Product-level interface module is identified the interface being associated with each level of BOM.
9. interface control module as claimed in claim 1, it is characterized in that, described interface Observation Blocks shows the link of the intermodule of product when showing the logic of product and Physical View, comprises described the first link between described supplier's module and described consumer's module.
10. interface control module as claimed in claim 1, is characterized in that, described interface contract module is set up the second interface contract based on first interface contract.
11. interface control modules as claimed in claim 1, is characterized in that:
Described supplier's module is interface definition object, and described consumer's module is the first assembly; And
Described link generation module is created in the link of second between data object and described interface definition object.
12. as the interface control module of claim 11, it is characterized in that, described link generation module is created in the 3rd link between the second assembly and described interface definition object.
13. as the interface control module of claim 12, it is characterized in that, the first link described in described interface contract module definition, the second link and the 3rd link.
14. interface control modules as claimed in claim 1, is characterized in that, also comprise Interface status module, and described Interface status module is determined the ready grade of interface based on workflow status,
Wherein, described interface compilation module is based on described ready grade compilation product.
15. interface control modules as claimed in claim 1, is characterized in that, also comprise that interface is searched and analysis module, and described interface is searched with the interface of analysis module based on being associated with product and searched the product line storer of described product and analyze described product.
16. interface control modules as claimed in claim 1, it is characterized in that, the first version of second version of described interface compilation module based on described supplier's module but not described supplier's module and based on described the first link described supplier's module of compilation and described consumer's module
Wherein, the date issued of described first version is before the date issued of described the second version.
17. as the interface control module of claim 16, it is characterized in that,
Described first version is linked to the first data object but is not linked to the second data object; With
Described the second version is linked to described the second data object but is not linked to described the first data object.
18. as the interface control module of claim 17, it is characterized in that, the third edition of described interface compilation module based on described supplier's module originally collect described supplier's module and described consumer's module,
Wherein:
The date issued of described the second version is before the date issued of described third edition basis;
The described third edition is originally linked to described the second data object;
The second version of described supplier's module is that the first version based on described the second data object collects; With
The third edition of described supplier's module is originally that the second version based on described the second data object collects.
19. interface control modules as claimed in claim 1, is characterized in that, described interface Observation Blocks shows the link between each module of multiple interface control modules and shows the link between described multiple interface control module on display.
20. 1 kinds of product line administration modules, comprise the interface control module according to claim 10, and comprise:
Display; With
The product line storer of memory interface contract.
CN201010545559.4A 2009-11-09 2010-11-09 Software interface management system and method thereof Active CN102054220B (en)

Applications Claiming Priority (4)

Application Number Priority Date Filing Date Title
US25939809P 2009-11-09 2009-11-09
US61/259398 2009-11-09
US12/696357 2010-01-29
US12/696,357 US8645233B2 (en) 2009-11-09 2010-01-29 Software interface management systems and methods

Publications (2)

Publication Number Publication Date
CN102054220A CN102054220A (en) 2011-05-11
CN102054220B true CN102054220B (en) 2014-04-16

Family

ID=43958512

Family Applications (1)

Application Number Title Priority Date Filing Date
CN201010545559.4A Active CN102054220B (en) 2009-11-09 2010-11-09 Software interface management system and method thereof

Country Status (2)

Country Link
CN (1) CN102054220B (en)
DE (1) DE102010050385A1 (en)

Families Citing this family (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN112578771B (en) * 2020-12-14 2022-05-17 东风汽车集团有限公司 Vehicle data management method and device, electronic equipment and storage medium

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6035297A (en) * 1996-12-06 2000-03-07 International Business Machines Machine Data management system for concurrent engineering
US6711550B1 (en) * 2000-03-31 2004-03-23 Ford Motor Company Method and system for capacity planning
US6975914B2 (en) * 2002-04-15 2005-12-13 Invensys Systems, Inc. Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with unified messaging interface

Family Cites Families (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6873997B1 (en) * 1999-08-04 2005-03-29 Agile Software Corporation Data management system and method for automatically propagating information to disparate information systems from a central location

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US6035297A (en) * 1996-12-06 2000-03-07 International Business Machines Machine Data management system for concurrent engineering
US6711550B1 (en) * 2000-03-31 2004-03-23 Ford Motor Company Method and system for capacity planning
US6975914B2 (en) * 2002-04-15 2005-12-13 Invensys Systems, Inc. Methods and apparatus for process, factory-floor, environmental, computer aided manufacturing-based or other control system with unified messaging interface

Also Published As

Publication number Publication date
CN102054220A (en) 2011-05-11
DE102010050385A1 (en) 2011-06-09

Similar Documents

Publication Publication Date Title
CN104992256A (en) Product-line based content management system and method thereof
CN102054219A (en) Product-line based content management system and method thereof
CA2723933C (en) Methods and systems for developing, debugging, and executing data integration applications
US20120054147A1 (en) System and method for extract, transform, and load workflow generation
CN100593794C (en) Long-distance controlling apparatus used for crops production expert diagnosing system and method thereof
McKay et al. A representation scheme for digital product service system definitions
US20150262124A1 (en) Artificial intelligence system and method for processing multilevel bills of materials
MX2008001785A (en) Automated batch manufacturing.
CN105654228A (en) Common plant model for modelling of physical plant items of production plant
CN106372044A (en) Method for generating typed dimension XBRL (Extensible Business Reporting Language) report based on report form
EP2804061B1 (en) Method for monitoring a process and/or production plant
WO2018236886A1 (en) System and method for code and data versioning in computerized data modeling and analysis
CN105260300B (en) Service test method based on accounting standard universal classification standard application platform
CN105654226A (en) Common plant model for modelling of physical plant items of production plant
Birk et al. A real-world application of process mining for data-driven analysis of multi-level interlinked manufacturing processes
CN102054220B (en) Software interface management system and method thereof
CN110633267B (en) Method and system capable of supporting multi-service report function
JP2018205908A (en) Plant design apparatus, plant design method, and plant design program
CN103970676A (en) Computer-implemented method and system for data management of product variants in control unit development
Kim et al. Comparing object-oriented and relational data models for project control
KR20150065292A (en) Erp program conversion method using relation data base
CN116361298B (en) Method and device for automatically acquiring SAP data to generate report form for EAS
US11243760B2 (en) Automated generation and consistency checking of software objects
Zwemer et al. Technote: application of MBE to Energy Engineering
Dickerson et al. A service oriented virtual environment for complex system analysis: Preliminary Report

Legal Events

Date Code Title Description
C06 Publication
PB01 Publication
C10 Entry into substantive examination
SE01 Entry into force of request for substantive examination
C14 Grant of patent or utility model
GR01 Patent grant