CN114911511A - Software technology state management system - Google Patents
Software technology state management system Download PDFInfo
- Publication number
- CN114911511A CN114911511A CN202210532968.3A CN202210532968A CN114911511A CN 114911511 A CN114911511 A CN 114911511A CN 202210532968 A CN202210532968 A CN 202210532968A CN 114911511 A CN114911511 A CN 114911511A
- Authority
- CN
- China
- Prior art keywords
- software
- finished product
- ecp
- data
- 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.)
- Pending
Links
Images
Classifications
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
-
- G—PHYSICS
- G06—COMPUTING; CALCULATING OR COUNTING
- G06F—ELECTRIC DIGITAL DATA PROCESSING
- G06F8/00—Arrangements for software engineering
- G06F8/70—Software maintenance or management
- G06F8/71—Version control; Configuration management
-
- 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
Abstract
The invention relates to the technical field of product technology management and information, in particular to a software technology state management system which comprises a software information examination module, a software process planning module, a software MBOM construction module, a software BBOM management module and a basic data configuration module. Through the system, the relevance and the accuracy of the version of the airborne software are realized, and the problem that the relevance relation between software and hardware cannot be traced can be effectively solved.
Description
Technical Field
The invention relates to the technical field of product technology management and information technology, in particular to a software technology state management system.
Background
At present, software management faces problems and challenges of scattered software data, untimely supplier data collaboration, incapability of tracing software and hardware association relation and the like, and needs to be effectively supported and controlled by an informatization means, in order to complete a technical state management system, product data management covers the whole life cycle of product and software delivery guarantee, finished hardware and software are separately managed by design, airplane matching software is taken as a CI item and is included in BOM to guarantee the controlled management of the technical state of the software whole life cycle, a software management system is taken as an information center and an integrated frame which are designed and manufactured uniformly in a model development task process, business personnel are supported to manage related processes of all software data involved in the manufacturing process, and the integrity, consistency, effectiveness and traceability of the software and the related data of the software are guaranteed.
Disclosure of Invention
In order to solve the technical problems, the invention provides a software technology state management system, which realizes the relevance and accuracy of an airborne software version and can effectively solve the problem that the correlation between software and hardware cannot be traced.
The invention is realized by adopting the following technical scheme:
a software technology state management system, characterized by: the system comprises a software information examination module, a software process planning module, a software MBOM construction module, a software BBOM management module and a basic data configuration module;
the software information examination module is used for examining software information, namely when the software is created and examined by a design institute EBOM (electronic book management System), software CI (public information interface), DSI (digital information interface) and related files thereof are synchronized to a manufacturing plant through a software ECP (electronic control unit), and after the manufacturing plant finishes manufacturability examination, examination opinions are fed back to the design institute to finish the software information examination;
the software process planning module is used for analyzing the influence of each professional department of the engineering department on the issued or changed software data in the process of examining the software information, identifying whether the software process planning module is related to the professional department or not and making processing measures, and specifically comprises the following steps: verifying a process planning flow, planning a software ECP process, checking a process planning result and synchronizing an SERP; the process planning flow verification comprises integrity verification, ECP (electronic control protocol) verification whether zero change exists and ECO verification whether the CI large version in the ECP has associated top layer change; the software ECP process plan comprises the following steps: obtaining and adjusting a checking structure list, setting a checking person, performing primary process planning, performing secondary professional process planning, performing primary professional review, performing project primary review and circulation;
the software MBOM construction module is used for starting software MCO after finishing process review and primary planning, finishing creation and updating of an association relation between a finished product and the software, generating a change record of the association relation between the finished product and the software at the same time, starting a task to corresponding process personnel for the MCO caused by change, confirming change information of the finished product and the software, starting a distribution and circulation flow for a software circulation unit when the MCO is released, and releasing the MCO information to an SERP system;
the software BBOM management module is used for acquiring execution records in real time through finished products or software DSI in the BBOM, determining the number of shelves when the finished products are installed on an airplane, and reversely checking the filling and upgrading records of the finished product associated software according to the AO where the resident finished products are located, thereby determining the software installation version information of the number of shelves, and simultaneously providing an interface for acquiring the software upgrading and filling execution information in the premises;
the basic data configuration module is used for providing a software distribution unit configuration function, a software MCO examiner configuration function and a process approval process configuration function.
The system also comprises a software information viewing module and a software data statistics and summary module, wherein the software information viewing module is used for providing a related software viewing function of a finished product in the EBOM/MBOM structure of the product, displaying the related software information of the finished product and filtering according to the number of frames; the software data statistics and summarization module is used for providing a software data statistics and summarization function and providing a software version inventory report, a software finished product association statistics report, software ECP statistics, a full-machine software version configuration table and a software executable file query and statistics function.
The software information examination module is specifically used for software top-level synchronization and initial issuing of software CI, software DSI and software data files; the software top-level synchronization specifically refers to: sending the top-level nodes and the software CIs of the airplane PBS software in the system to a manufacturing plant in batch, and implementing the data synchronization process of the ECO plant by changing the top-level nodes, the attributes of the software CIs and the addition and deletion of the software CIs through the top-level change once the top-level nodes and the software CIs are issued; the software CI, the software DSI and the software data file are firstly issued specifically as follows: and issuing through the zero change software ECP, distributing and reading after entering a manufacturing factory, and acquiring the specific distribution unit according to the configuration of the software circulation unit.
The process planning flow verification specifically comprises the following steps: after the software ECP is sent to a manufacturing plant system, integrity check is firstly carried out, whether synchronous data contain all ECP data is confirmed, if the synchronous data do not contain all ECP data, a design place is fed back, if the synchronous data contain all ECP data, whether the ECP is zero change is continuously checked, if the ECP is not zero change, process planning is required, if the ECP is zero change, whether a CI large version in the ECP is related to a top-layer change ECO is continuously checked, if the ECP is related, the process planning is required, and if the ECP is not related, a circulation flow is directly started.
The software ECP process plan specifically comprises the following steps:
obtaining and adjusting an examination and signing structure list: acquiring all resident finished product information finished product list items according to the sent ECP associated CI list as list items in the process task; if the ECP is associated with no software CI, searching the software DSI associated with the ECP, and searching the CI according to the software DSI;
setting a label reader: a technical department responsible person of the technical department of the technical process countersigning assignment initializes a primary and a secondary signing personnel, sets the signing personnel according to all software CI related to ECP, all finished product figure numbers of resident finished product information of each software CI, PBS codes of DSI on an EBOM where all finished product figure numbers are located, and acquires process signing process configuration rules according to the PBS codes of all DSI;
and (3) process level planning: the method comprises the steps that first-level aviation management and avionics major are carried out, first-level process planning task allocation is carried out, wherein an allocated list obtains a software CI list from an associated object of an ECP, and a finished product list of resident finished product information is obtained according to the software list;
and (3) secondary professional process planning: the second-level specialties of flight management and avionics receive the process first-level planning task of the ECP, and the process planning information needs to be verified and filled when the task is completed;
primary professional main examination: after the second-level profession finishes the process planning, the first-level profession mainly examines the first-level planning content filled in by the second-level profession, and the planning content is checked according to the software CI or professional dimensions; if the process planning content is not perfect, a second-level specialty can be rejected for modification;
and (4) project main review and examination: and the project main audit receives a project main audit task, in the task, process planning main audit summary data are checked, and in the main audit summary, process planning opinions are checked according to finished product dimensions or professional dimensions respectively.
The creation and updating of the finished product and software association relation specifically refers to: after the MCO is created, extracting software CI associated finished product information to form a finished product and software association relation table, and comparing the software CI related to the change with the finished product association to form a finished product and software association change record; the method for generating the finished product and software associated change record comprises the following steps: comparing the finished product number and the software CI number by taking the finished product number and the software CI number as a reference, if no record exists, adding newly, and if a record exists, modifying; if the attribute is newly added, only the value is obtained after the attribute is changed, if the attribute is modified, whether the attribute is changed before the attribute is changed or not is judged, and the value before the attribute is changed and the value after the attribute is changed is displayed; and if the CI version is upgraded, the DSI numbers corresponding to the two CI versions are required to be obtained as the DSI numbers before and after the change, and if the DSI version is upgraded, the DSI numbers are listed before and after the change.
The software BBOM management module is used for acquiring a software execution record, namely acquiring a resident finished product number according to software DSI; finding a finished product installation record according to the number of the shelves and the finished product number to obtain a finished product quality number; and acquiring software filling and upgrading records according to the finished product quality numbers.
The system adopts standard REST to carry out data interaction, and the REST bottom layer adopts XML to carry out data exchange.
The system also comprises a data management module used for realizing data exchange, data tracking and data format conversion.
Compared with the prior art, the invention has the beneficial effects that:
1. the invention realizes factory software design cooperation through software information examination, realizes software process management through software MBOM construction, realizes influence analysis and change plan of software change through software process plan, realizes software physical state control through software BBOM management, realizes whole process control on airborne software technical state, constructs a software technical state control environment, realizes effective control on airborne software technical state, realizes the relevance and accuracy of airborne software version, and meets the requirement of tracing software and hardware relevance relation.
Drawings
The invention will be described in further detail with reference to the following description taken in conjunction with the accompanying drawings and detailed description, in which:
FIG. 1 is a schematic flow diagram of the present invention;
FIG. 2 is a schematic diagram of a software data factory synchronization process according to the present invention;
FIG. 3 is a schematic diagram of a software process planning flow according to the present invention;
FIG. 4 is a schematic diagram illustrating an inspection flow of the MBOM in the present invention;
FIG. 5 is a schematic diagram of data flow of the software BBOM in the present invention.
Detailed Description
Example 1
As a basic implementation mode of the invention, the invention comprises a software technology state management system which comprises a software information examination module, a software process planning module, a software MBOM construction module, a software BBOM management module and a basic data configuration module.
The software information examination module is used for examining software information, namely when the software is created and examined by a design institute EBOM, software CI, software DSI and relevant files thereof are synchronized to a manufacturing plant through a software ECP, and after the manufacturing plant finishes technological examination, examination opinions are fed back to the design institute to finish the examination of the software information.
The software process planning module is used for analyzing the influence of each professional department of the engineering department on the issued or changed software data, identifying whether the software process planning module is related to the professional department or not and making processing measures in the process of software information examination. The method specifically comprises the following steps: verifying a process planning flow, planning a software ECP process, checking a process planning result and synchronizing an SERP. The process planning flow verification comprises integrity verification, ECP verification whether zero change exists or not and verification whether an associated top layer change ECO exists in a CI large version in the ECP or not. The software ECP process plan comprises the following steps: obtaining and adjusting a checking structure list, setting a checking person, performing primary process planning, performing secondary professional process planning, performing primary professional review, performing project primary review and circulation.
The software MBOM construction module is used for starting software MCO after finishing process review and first-level planning, finishing creation and updating of the association relationship between finished products and the software, generating a change record of the association relationship between the finished products and the software at the same time, starting tasks for corresponding process personnel for MCO caused by change, confirming change information of the finished products and the software, starting a distribution and circulation process for a software circulation unit when the MCO is released, and releasing MCO information to an SERP system.
The software BBOM management module is used for acquiring execution records in real time through finished products or software DSI in the BBOM, and reversely checking finished product related software filling and upgrading records according to AO where the resident finished products are located when the finished products are installed on an airplane, so that installation version information of the set number software is determined, and an interface is provided for acquiring software upgrading and filling execution information in a station.
The basic data configuration module is used for providing a software distribution unit configuration function, a software MCO examiner configuration function and a process approval process configuration function.
Example 2
The invention comprises a software technology state management system as a preferred embodiment of the invention, which comprises a software information examination module, a software process planning module, a software MBOM construction module, a software BBOM management module, a basic data configuration module, a software information viewing module and a software data statistics and summary module. In this embodiment, the BOM is a bill of materials, the MBOM is a manufacturing bill of materials, the BBOM is an installation bill of materials, the EBOM is a design bill of materials, and the MCO is an engineering change instruction.
The software information examination module is used for examining software information, namely when the software is created and examined by a design institute EBOM, software CI, software DSI and relevant files thereof are synchronized to a manufacturing plant through a software ECP, and after the manufacturing plant finishes technological examination, examination opinions are fed back to the design institute to finish the examination of the software information.
The software process planning module is used for analyzing the influence of each professional department of the engineering department on the issued or changed software data, identifying whether the software process planning module is related to the professional department or not and making processing measures in the process of software information examination. The method specifically comprises the following steps: verifying a process planning flow, planning a software ECP process, checking a process planning result and synchronizing an SERP. The process planning flow verification comprises integrity verification, ECP verification whether zero change exists or not and verification whether an associated top layer change ECO exists in a CI large version in the ECP or not. The software ECP process plan comprises the following steps: obtaining and adjusting a checking structure list, setting a checking person, performing primary process planning, performing secondary professional process planning, performing primary professional review, performing project primary review and circulation.
The software MBOM construction module is used for starting the software MCO after finishing process examination and primary planning, finishing creation and updating of the association relation between the finished product and the software, generating a change record of the association relation between the finished product and the software at the same time, starting a task to corresponding process personnel for the MCO caused by change, confirming the change information of the finished product and the software, starting a distribution and circulation flow for a software circulation unit when the MCO is released, and releasing the MCO information to an SERP system.
The software information viewing module is used for providing a function of viewing the associated software of the finished product in the EBOM/MBOM structure of the product, displaying the information of the associated software of the finished product and filtering according to the number of shelves.
The software data statistics and summarization module is used for providing a software data statistics and summarization function and providing a software version inventory report, a software finished product association statistics report, software ECP statistics, a full-machine software version configuration table and a software executable file query and statistics function.
The software BBOM management module is used for acquiring execution records in real time through finished products or software DSI in the BBOM, and reversely checking finished product related software filling and upgrading records according to AO where the resident finished products are located when the finished products are installed on an airplane, so that installation version information of the set number software is determined, and an interface is provided for acquiring software upgrading and filling execution information in a station.
The basic data configuration module is used for providing a software distribution unit configuration function, a software MCO examiner configuration function and a process approval process configuration function.
Example 3
As the best mode of execution of the invention, the invention comprises a software technical state management system, which comprises a software information examination module, a software process planning module, a software MBOM construction module, a software BBOM management module, a basic data configuration module, a software information examination module, a software data statistics and summarization module and a data management module by referring to an attached figure 1 and an attached figure 2 of the specification. Each module is specifically described below:
the software information examination module: the method is used for examining software information, and specifically comprises the following steps: when the software is created and audited by the EBOM, the software CI, the software DSI and the related files thereof are synchronized to the manufacturing plant through the ECP, and after the manufacturability audit is finished by the manufacturing plant, the audit opinions are fed back to the EBOM to finish the software information audit.
And (4) software top synchronization. The initial build of the software top-level structure is similar to the synchronization of the hardware top-level to the factory. And sending the top-level nodes of the airplane PBS software in the system and the software CI to the factory together in batches. Once the software top-level node and the software CI are issued. If the top node of the software is changed, the attribute of the software CI is changed, and the addition and deletion of the software CI are implemented by changing the data synchronization process of the ECO factory through the top.
And software CI, software DSI and software data files are issued for the first time. Software CI, software DSI and software data file are issued for the first time, the software is issued through zero change software ECP, distribution and circulation are carried out after the software is delivered to a factory, and specific distribution units are configured and obtained according to the software circulation units.
The software process planning module comprises: in the process of software information examination, after the software ECP is issued to the plant, a first-level planning flow is started in the plant, and each professional department of the engineering department analyzes the influence of the issued or changed software data, identifies whether the software data is related to the professional department, and makes a treatment measure. Referring to the attached figure 3 of the specification, the method specifically comprises the following steps:
and (5) verifying the process planning flow. After the software ECP is sent to a manufacturing plant system, integrity check is firstly carried out, whether synchronous data contain all ECP data is confirmed, if the synchronous data do not contain all ECP data, a design place is fed back, if the synchronous data contain all ECP data, whether the ECP is zero change is continuously checked, if the ECP is not zero change, process planning is required, if the ECP is zero change, whether a CI large version in the ECP is related to a top-layer change ECO is continuously checked, if the ECP is related, the process planning is required, and if the ECP is not related, a circulation flow is directly started.
And (4) planning the ECP process by software. And adjusting on the basis of the process of signing in the factory change process, keeping integrity verification, and acquiring and adjusting an examination and signing structure list. And acquiring all the finished product inventory items of the resident finished product information according to the sent ECP associated CI list as inventory items in the process task. And if the ECP association has no software CI, searching the software DSI associated with the ECP, and searching the CI according to the software DSI. The technical department of the technical process countersigning assignment engineering initializes a primary and a secondary signing personnel, and sets the signing personnel according to all software CI related to ECP, all finished product figure numbers of resident finished product information of each software CI, PBS codes of DSI on an EBOM where all finished product figure numbers are located and configuration rules of a process signing process acquired according to the PBS codes of all DSI. A process level plan state is created and set.
And performing process level planning task assignment by flight management and avionics level major, wherein an assigned list obtains a software CI list from an associated object of the ECP. And acquiring a finished product list of the resident finished product information according to the software list.
And the secondary specialties of the flight management and the avionics receive the process primary planning task of the ECP, and the process planning information needs to be verified and filled when the task is completed. The process plan fills in the field description. The number corresponds to the product drawing number, and the security level corresponds to the security level of the product. The model of the finished product corresponds to the model of the finished product, the name of the finished product corresponds to the name of the finished product, and the cabin in which the finished product is located obtains all the affiliated cabins of all DSIs in which the finished product is located. CI list ECP associated software CI list, if ECP associated software CI does not exist, then finding ECP associated software DSI, and finding CI according to software DSI. And obtaining the shelf effectiveness of the software CI by effectiveness. The change type of the CI is checked by the user for the change type of each CI. Whether the fields are relevant to the present profession or not is checked by the user, the following primary plan information is required to be filled in only if yes is selected, and the following fields required to be filled in are not displayed if no is selected. Whether the filling work is carried out or not is selected by a user. And if the off-position upgrading is carried out, the user selects 'yes' or 'no', and the off-position upgrading is a necessary item. The associated CI is selected by the user, and may be multiple. The pop-up window can input the number and the CI list in the name searching system, display the number, the name and the version, and respectively display a plurality of versions for multiple selections. The matching change is selected by the user and is a necessary item, and the user selects 'no matching' without filling. If the user has matched the following items: the method comprises the steps of 'hardware matching' and 'software matching', if the 'hardware matching' is selected, matching ECP needs to be selected, a pop-up window can input a software ECP list in a number and name searching system, and numbers and names are displayed and can be selected more. And the model of the matched finished product is automatically brought out. The user can manually input the ECP number and the matched finished product model. If 'software matching' is selected, matching ECP needs to be selected, a pop-up window can input a serial number and a name to search a software ECP list in the system, and the serial number and the name can be displayed and selected more. And the matched finished product model, namely the 'resident finished product model' of the ECP is automatically brought out. And after upgrading, installing test inspection opinions, adding a line, increasing selected test units and execution contents, and deleting a line of test units and execution contents. The test unit is selected by the user, and the selection range of the test unit is consistent with the execution unit of the ECO level plan. The execution content is filled in by the user.
The primary professional main reviews the primary planning content filled in by the primary professional. After the second-level profession finishes the process planning, the task is transmitted to a first-level professional main review link, the first-level professional main review link can review the first-level planning content filled in by the second-level professional, and the planning content can be checked according to software CI or professional dimension. If the process planning content is not perfect, the second-level specialties can be rejected for modification. If the examination is passed, the task can be completed, and the task is transferred to a project main review link.
After the first-level major passes, the project main audit receives a project main audit task, process planning main audit summary data can be checked in the task, and process planning opinions can be checked according to finished product dimensions or professional dimensions respectively in the main audit summary. And after the project main review is passed, finishing the process planning flow and starting a circulation flow for a software distribution unit.
And checking a process planning result. After the process planning is completed, the process planning result can be checked through the process planning page on the software ECP detail page.
The SERP is synchronized. And after the main audit of the ECP process planning project passes, the ECP primary planning content of the software is sent to the SERP through system integration.
The software MBOM construction module comprises: referring to the attached figure 4 of the specification, because software does not exist independently and needs to be matched with finished products, the software does not plan the segment position and the MCI independently and does not consume materials, and the software is embodied in the MBOM in the association relationship between the finished products and the software. And after the EBOM software management information is issued, namely after the process examination and the first-level plan are finished, triggering the finished product and the software to be associated with the MCO, and establishing the association relationship between the finished product and the software.
Software MCO task assignment. After the MCO is changed by software, if the task needs to be started and submitted is judged, the examiner is obtained and the task is started and submitted according to the finished product word head associated with the software CI in the MCO from the configuration of the examiner of the software MCO, and the subsequent examiner is selected by a submitter. MCO number back-filling. After the MCO is created, in the process, a function is added, and the MCO number is filled back to the MCO number of the associated ECP attribute.
And generating an association relation. After the MCO is created, software CI related finished product information is extracted to form a finished product and software association relation table, and the software CI related to the change is compared with the finished product to form a finished product and software association change record. The method for generating the finished product and software associated change record comprises the following steps: comparing the finished product number and the software CI number by taking the finished product number and the software CI number as a reference, if no record exists, adding newly, and if a record exists, modifying; if the attribute is newly added, only the value is obtained after the attribute is changed, if the attribute is modified, whether the attribute is changed before the attribute is changed or not is judged, and the value before the attribute is changed and the value after the attribute is changed is displayed. And if the DSI is upgraded, the DSI numbers corresponding to the two CI versions are acquired and used as the DSI numbers before and after the change, and if the DSI is upgraded, the DSI numbers are listed before and after the change.
And the finished product is associated with the software to change the record for viewing. When the MCO is changed by software, the function of checking MCO change records is provided, when the MCO is opened, finished products corresponding to the MCO and the software associated change records are displayed, and when the MCO change records are checked, the software CI version column is not displayed; the software changes the MCO detail page and does not provide the function of opening MPE and invalidating MCO.
When the MCO is changed by software, the finished product and software association relation table and the finished product and software association change record table are released to the global database, and an SERP interface is called to push an MCO notification. And when the software is released, starting a circulation flow for the software distribution unit, and acquiring the circulation flow from the configuration of the software distribution unit by the circulation unit.
A software information viewing module: and in the EBOM \ MBOM structure of the product, providing a function of viewing the associated software of the finished product and displaying the information of the associated software of the finished product. Meanwhile, the filtration can be carried out according to the number of times. Under the control of the model, in the EBOM/MBOM structure of the product, a related software tab is added on the right side of the finished product to display the finished product and all related software information. And acquiring the associated software of the finished product from the finished product and software association relation table according to the finished product CP code, and displaying the associated software in an associated software list, wherein only the items containing the input shelves are displayed in the associated software list if the batch shelf number has a value.
Software data statistics summarization module: the model management and control-statistics report is added with a software statistics report function, and functions of software version inventory report, software finished product association statistics report, software ECP statistics, full-machine software version configuration table, software executable file query statistics and the like are provided.
The software BBOM management module: referring to the attached figure 5 of the specification, after the software is filled, installed and upgraded in real time, corresponding software upgrading and filling records can be formed, execution records are obtained in real time through finished products or software DSI in a BBOM, because the software does not exist independently, the software must be matched with the finished products, the number of shelves can be determined after the finished products are installed on an airplane, and the finished product-related software filling and upgrading records are checked back according to AO where the resident finished products are located, so that the installation version information of the software of the number of shelves is determined, and meanwhile, an interface is provided for obtaining the software upgrading and filling execution information in the houses.
And acquiring a software execution record. And acquiring the resident finished product number according to the software DSI, finding a finished product installation record according to the number of the shelves and the finished product number, and acquiring a finished product quality number. And acquiring software filling and upgrading records according to the finished product quality numbers.
And performing information feedback. The software technology state management system provides an interface for a design station to acquire software upgrading and filling execution information in real time so as to clarify the execution state of related software and support design change influence analysis of the design station.
The basic data configuration module: the software passes through the unit configuration. Under a menu of model management and control, system support and system maintenance, in a system configuration function, a configuration software distribution unit is added in the process of configuring newly added type software distribution. The section is a software distribution unit, the key value is a distribution unit name, such as a check detection part, a purchase part and the like, and the value is a unit brevity code.
In the system support-system maintenance-system configuration, in the software distribution type, the configuration of software MCO examiners is added, and the MCO examiners are configured according to CI headers. Section filling software MCO examiner, key value elastic CI word head, value filling examiner job number.
A data management module: providing data exchange functionality. Based on the open standard, the built-in finished product technical state management system for manufacturing provides common functions such as service searching, accessing, routing and the like, and is also provided with a data object based on XML, so that data interaction and interoperation among services support information (data) integration, process integration and application integration are facilitated. Supporting enterprise-level quality of service. The supported enterprise-level service quality comprises message security, failure recovery, state diagnosis, service management, service audit, message reliable transmission, transaction integrity and the like, and provides the data exchange process and the data tracking capability. Providing a data format conversion function. A heterogeneous data format conversion mapping tool for graphic visualization is provided, which can convert data from one format into another format easily, conveniently and quickly. The input data and the output data can be converted between different formats, such as structured XML, non-XML or Java object data, so that heterogeneous applications can be quickly integrated without considering the format adopted by the representation data. Providing full support for REST. The method not only supports REST access provided by different systems, but also can encapsulate the existing service application into REST for multiplexing. Standard protocols commonly used for REST are supported. And adopting standard REST for data interaction. The standard REST is a relatively mature data exchange mode suitable for cross-platform; the connecting technical requirement and the limitation of an operating platform can be reduced; and the REST bottom layer adopts XML to exchange data, so that maintenance and interaction are facilitated.
The system also integrates a plurality of commonly used system adapters and provides adapter customization development capability: the system integrates common adapters in various enterprise applications, such as a file adapter supporting reading and writing of structured and unstructured files, a database adapter supporting Access of various databases, such as Oracle, DB2, SQL Server, SyBase, MySql, Excel, Access and the like, a communication adapter supporting various communication protocols, such as FTP, SMTP/POP3, REST and the like, reduces the development workload of programmers through the existing adapters, and realizes the rapid application integration capability.
The system also integrates monitoring and management functions: the management console based on the browser is provided, and can be used for carrying out state query and monitoring management on monitoring nodes, services, components and business processes.
In summary, after reading the present disclosure, those skilled in the art should make various other modifications without creative efforts according to the technical solutions and concepts of the present disclosure, which are within the protection scope of the present disclosure.
Claims (9)
1. A software technology state management system, characterized by: the system comprises a software information examination module, a software process planning module, a software MBOM construction module, a software BBOM management module and a basic data configuration module;
the software information examination module is used for examining software information, namely when the creation of the software is examined by a design institute EBOM, software CI, software DSI and associated files thereof are synchronized to a manufacturing plant through a software ECP, and after the manufacturability examination is finished in the manufacturing plant, examination opinions are fed back to the design institute to finish the software information examination;
the software process planning module is used for analyzing the influence of each professional department of the engineering department on the issued or changed software data in the process of examining the software information, identifying whether the software process planning module is related to the professional department or not and making processing measures, and specifically comprises the following steps: verifying a process planning flow, planning a software ECP process, checking a process planning result and synchronizing an SERP; the process planning flow verification comprises integrity verification, ECP (electronic control protocol) zero change verification and ECO (electronic signature) verification, wherein the ECP is verified to be zero change, and whether a CI (electronic signature) large version in the ECP has an associated top layer change ECO; the software ECP process plan comprises the following steps: obtaining and adjusting a checking structure list, setting a checking person, performing primary process planning, performing secondary professional process planning, performing primary professional review, performing project primary review and circulation;
the software MBOM construction module is used for starting software MCO after finishing process review and primary planning, finishing creation and updating of an association relation between a finished product and the software, generating a change record of the association relation between the finished product and the software at the same time, starting a task to corresponding process personnel for the MCO caused by change, confirming change information of the finished product and the software, starting a distribution and circulation flow for a software circulation unit when the MCO is released, and releasing the MCO information to an SERP system;
the software BBOM management module is used for acquiring execution records in real time in a BBOM through finished products or software DSI, determining the number of frames when the finished products are installed on an airplane, and reversely checking filling and upgrading records of finished product related software according to the AO where the resident finished products are located, so as to determine the software installation version information of the number of frames, and simultaneously providing an interface for acquiring software upgrading and filling execution information in the houses;
the basic data configuration module is used for providing a software distribution unit configuration function, a software MCO examiner configuration function and a process approval process configuration function.
2. A software technology state management system according to claim 1, characterized in that: the system also comprises a software information viewing module and a software data statistics and summary module, wherein the software information viewing module is used for providing a related software viewing function of a finished product in the EBOM/MBOM structure of the product, displaying the related software information of the finished product and filtering according to the number of frames; the software data statistics and summarization module is used for providing a software data statistics and summarization function and providing a software version inventory report, a software finished product association statistics report, software ECP statistics, a full-machine software version configuration table and a software executable file query and statistics function.
3. A software technology state management system according to claim 1, characterized in that: the software information examination module is specifically used for software top-level synchronization and initial issuing of software CI, software DSI and software data files; the software top-level synchronization specifically refers to: sending the top-level nodes and the software CIs of the airplane PBS software in the system to a manufacturing plant in batch, and implementing the data synchronization process of the ECO plant by changing the top-level nodes, the attributes of the software CIs and the addition and deletion of the software CIs through the top-level change once the top-level nodes and the software CIs are issued; the software CI, the software DSI and the software data file are firstly issued specifically as follows: and issuing through the zero change software ECP, distributing and reading after entering a manufacturing factory, and acquiring the specific distribution unit according to the configuration of the software circulation unit.
4. A software technology state management system according to claim 1, characterized in that: the process planning flow verification specifically comprises the following steps: after the software ECP is sent to a manufacturing plant system, integrity check is firstly carried out, whether synchronous data contain all ECP data is confirmed, if the synchronous data do not contain all ECP data, a design place is fed back, if the synchronous data contain all ECP data, whether the ECP is zero change is continuously checked, if the ECP is not zero change, process planning is required, if the ECP is zero change, whether a CI large version in the ECP is related to a top-layer change ECO is continuously checked, if the ECP is related, the process planning is required, and if the ECP is not related, a circulation flow is directly started.
5. A software technology state management system according to claim 1, characterized in that: the software ECP process plan specifically comprises the following steps:
obtaining and adjusting an examination and signing structure list: acquiring all resident finished product information finished product list items according to the sent ECP associated CI list as list items in the process task; if the ECP is associated with no software CI, searching the software DSI associated with the ECP, and searching the CI according to the software DSI;
setting a label reader: a technical department responsible person of the technical department of the technical process countersigning assignment initializes a primary and a secondary signing personnel, sets the signing personnel according to all software CI related to ECP, all finished product figure numbers of resident finished product information of each software CI, PBS codes of DSI on an EBOM where all finished product figure numbers are located, and acquires process signing process configuration rules according to the PBS codes of all DSI;
and (3) process level planning: the method comprises the steps that first-level aviation management and avionics major are carried out, first-level process planning task allocation is carried out, wherein an allocated list obtains a software CI list from an associated object of an ECP, and a finished product list of resident finished product information is obtained according to the software list;
and (3) secondary professional process planning: the second-level specialties of flight management and avionics receive the process first-level planning task of the ECP, and the process planning information needs to be verified and filled when the task is completed;
primary professional main examination: after the second-level professional finishes the process planning, the first-level professional mainly examines the first-level planning content filled in by the second-level professional, and examines the planning content according to software CI or professional dimensions; if the process planning content is not perfect, a second-level specialty can be rejected for modification;
and (4) project main review and examination: and the project main audit receives a project main audit task, in the task, process planning main audit summary data are checked, and in the main audit summary, process planning opinions are checked according to finished product dimensions or professional dimensions respectively.
6. A software technology state management system according to claim 1, characterized in that: the creation and updating of the finished product and software association specifically refers to: after the MCO is created, extracting software CI (contact information) associated finished product information to form a finished product and software association relation table, and comparing the software CI related to the change with the finished product association to form a finished product and software association change record; the method for generating the finished product and software association change record comprises the following steps: comparing the finished product number and the software CI number by taking the finished product number and the software CI number as a reference, if no record exists, adding newly, and if a record exists, modifying; if the attribute is newly added, only the value is obtained after the attribute is changed, if the attribute is modified, whether the attribute is changed before the attribute is changed or not is judged, and the value before the attribute is changed and the value after the attribute is changed is displayed; and if the DSI is upgraded, the DSI numbers corresponding to the two CI versions are acquired and used as the DSI numbers before and after the change, and if the DSI is upgraded, the DSI numbers are listed before and after the change.
7. A software technology state management system according to claim 1, characterized in that: the software BBOM management module is used for acquiring a software execution record, namely acquiring a resident finished product number according to software DSI; finding a finished product installation record according to the number of the shelves and the finished product number to obtain a finished product quality number; and acquiring software filling and upgrading records according to the finished product quality numbers.
8. A software technology state management system according to claim 1, characterized in that: the system adopts standard REST to carry out data interaction, and the REST bottom layer adopts XML to carry out data exchange.
9. A software technology state management system according to claim 1, characterized in that: the system also comprises a data management module used for realizing data exchange, data tracking and data format conversion.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210532968.3A CN114911511A (en) | 2022-05-17 | 2022-05-17 | Software technology state management system |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202210532968.3A CN114911511A (en) | 2022-05-17 | 2022-05-17 | Software technology state management system |
Publications (1)
| Publication Number | Publication Date |
|---|---|
| CN114911511A true CN114911511A (en) | 2022-08-16 |
Family
ID=82768645
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202210532968.3A Pending CN114911511A (en) | 2022-05-17 | 2022-05-17 | Software technology state management system |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN114911511A (en) |
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115222376A (en) * | 2022-09-21 | 2022-10-21 | 成都飞机工业（集团）有限责任公司 | Aircraft tool changing method, device, equipment and storage medium |
-
2022
- 2022-05-17 CN CN202210532968.3A patent/CN114911511A/en active Pending
Cited By (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN115222376A (en) * | 2022-09-21 | 2022-10-21 | 成都飞机工业（集团）有限责任公司 | Aircraft tool changing method, device, equipment and storage medium |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US8336022B2 (en) | Method and apparatus for creating a configurable browser-based forms application | |
| US6487469B1 (en) | System and method for integrating schedule and design environments | |
| CN110781236A (en) | Method for constructing government affair big data management system | |
| US6370542B1 (en) | Method and apparatus for knowledge acquisition and management | |
| US8612249B2 (en) | Systems and methods for managing regulatory information | |
| US8024373B2 (en) | Computer-implemented system for producing, processing and managing structured data sets | |
| CN106445536B (en) | Automatic business design management system | |
| CA2445195A1 (en) | Software suitability testing system | |
| CN112579609A (en) | Method and system for realizing data standardization management and sharing based on data asset directory | |
| CN114519085A (en) | Data standardization management method and sharing system | |
| CN113592680A (en) | Service platform based on regional education big data | |
| CN112308727A (en) | Insurance claim settlement service processing method and device | |
| US7827533B2 (en) | Analytical server, program analysis network system, and program analysis method | |
| CN114911511A (en) | Software technology state management system | |
| JP2003015869A (en) | Program, method and system for supporting development | |
| CN110909070A (en) | Test data multi-view display system based on technical state | |
| US20100010842A1 (en) | Computer-Implemented Systems and methods for Producing, Processing and Managing Structured Data Sets | |
| CN116303641B (en) | Laboratory report management method supporting multi-data source visual configuration | |
| US20140324508A1 (en) | Business service management system | |
| CN113240231B (en) | Finished product technical state management system | |
| CN114169776A (en) | Task processing method and device | |
| JP5583306B1 (en) | Information system and updating method thereof | |
| TWI778433B (en) | Data management system and method for data synchronization | |
| KR20080001248A (en) | System for quality control of database | |
| JP2019101829A (en) | Software component management system, computor, and method |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination |