Method, device and system for relationship modeling management based on product BOM structure

Abstract

The embodiment of the present disclosure discloses a product BOM structure-based relationship modeling management method, device and system, the method comprises: importing product design data generated from a product design tool, extracting type information of each component in the product design and relationship information between each component; defining related information of a plurality of object models, which is used for structured representation of each component type of the product, contained attributes, and a life cycle of each component type and a life cycle state thereof, and defining an entity storage structure based on the related information of the object models for structured storage of product data; defining related information of a relationship model between the plurality of object models; based on the related information of the object models and the related information of the relationship model, creating a page model using a visual what-you-see-is-what-you-get page modeling tool, the page model being used for showing related information of business data generated by the object models and the relationship model.

Description

Technical Field

[0001] This disclosure relates to the field of product design technology, specifically to a method, apparatus, and system for relationship modeling and management based on product BOM structure. Background Technology

[0002] Traditional BOM (Bill of Materials) management software is only designed for a single product stage, typically using a single, mature database table corresponding to a single data structure. Data variability is low, generally with no status or version changes. Data relationships are relatively simple, and these relationships generally do not change state. Data structure consistency requirements are low; apart from metadata, business data is generally not shared. However, for the entire product BOM lifecycle, the BOM data structure is highly dynamic. Users need to be able to dynamically define model structure types and dynamically add attributes. Data variability is high, with each data entry subject to lifecycle management and version control. Data relationships are more complex, and these relationships have state changes that can be traced and compared.

[0003] Most BOM management systems on the market today are based on file storage rather than object-based database management. This makes it impossible to maintain data consistency throughout the product lifecycle, and prevents BOM data from being progressively routed down the product lifecycle. Instead, files flow through each stage, not data. This makes managing very large model design environments difficult, as the attribute states of each model cannot be extracted or transferred.

[0004] In conclusion, there is an urgent need for an object modeling management system and methodology that can integrate BOM data throughout the entire product lifecycle, helping enterprises achieve data integration, building a bridge for data resource sharing and integration between all stages from design to manufacturing, and improving enterprise management efficiency. Summary of the Invention

[0005] This disclosure provides a method, apparatus, and system for relationship modeling and management based on product BOM structure.

[0006] In a first aspect, this disclosure provides a relationship modeling and management method based on product BOM structure, including:

[0007] Import product design data generated by the product design tool, and extract the type information of each component in the product design and the relationship information between each component from the imported product design data;

[0008] Based on the type information of each component in the product design, define the relevant information of multiple object models to structurally represent the types of each component, the attributes they contain, the life cycle of each component type and its life cycle status, and define an entity storage structure based on the relevant information of the object models for the structured storage of product data.

[0009] Based on the relationship information of each component in the product design and the relevant information of the multiple object models, define the relevant information of the relationship model between the multiple object models;

[0010] Based on the relevant information of the object model and the relevant information of the relationship model, a page model is created using a visual WYSIWYG page modeling tool. The page model is used to display the relevant information of the business data generated by the object model and the relationship model.

[0011] Furthermore, the method also includes:

[0012] Retrieve stored business data; the business data includes object data and relationship data;

[0013] Add, edit, and remove object data;

[0014] The acquired object data is parsed according to the type and attribute information defined in the corresponding object model, and the object data is split into basic object attribute data and dynamic object attribute data, and finally stored in the entity storage structure corresponding to the object model.

[0015] Adding and removing relational data;

[0016] The acquired relational data is parsed according to the corresponding relational model, and then parsed into relational association data and relational attribute data, which are finally stored in the entity storage structure corresponding to the relational model; the business data is loaded and displayed using the page model.

[0017] Monitor the lifecycle status of the business data and perform corresponding operations on the business data based on the lifecycle status; wherein, changes in the lifecycle status are approved by calling the corresponding approval process configured when defining the lifecycle; user revision operations on business data or creation of change baselines are approved by calling the corresponding approval process, and the status of the process instance is monitored by starting the corresponding task, and intervention operations are performed on the process instance.

[0018] Furthermore, the method also includes:

[0019] Manage the addition and removal of relationship data between object data corresponding to the object model under multiple stages of BOM relationship view, as well as the conversion of BOM relationship view at different stages, and control the consistency of object data;

[0020] Transform relational data under different relational views to make business data between different views continuous and transferable;

[0021] Log data generated by transforming business data and relational data.

[0022] Furthermore, the method also includes:

[0023] Relevant data is obtained from the BOM data storage module to trace the flow of the entire product lifecycle. The relevant data includes historical data of various versions of the object model, relationship change data when different BOM views are converted, historical running data of various processes, and log data of various business data operations. The relevant data is then assembled and displayed.

[0024] Secondly, this disclosure provides a relationship modeling and management device based on a product BOM structure, characterized in that it includes:

[0025] The import module is configured to import product design data generated from the product design tool and extract the type information of each component in the product design and the relationship information between each component from the imported product design data.

[0026] The first definition module is configured to define relevant information of multiple object models based on the type information of each component in the product design. This is used to structurally represent the types of each component in the product, the attributes they contain, the life cycle of each component type and its life cycle status. Based on the relevant information of the object models, an entity storage structure is defined for the structured storage of product data.

[0027] The second definition module is configured to define the relevant information of the relationship model between the multiple object models based on the relationship information of each component in the product design and the relevant information of the multiple object models;

[0028] A creation module is configured to create a page model using a visual, WYSIWYG page modeling tool based on information related to the object model and information related to the relationship model. The page model is used to display information related to the business data generated by the object model and the relationship model.

[0029] Thirdly, this disclosure provides a relationship modeling and management system based on a product BOM structure, characterized by comprising: a BOM object modeling part, a BOM management part, and a data processing part; the BOM object modeling part includes: a BOM object modeling module, a BOM relationship modeling module, and a BOM page modeling module; the BOM management part includes: a BOM object management module, a BOM process management module, and a BOM relationship view management module; the data processing part includes: a BOM data storage module, a BOM data import module, a BOM data conversion module, and a BOM data traceability module;

[0030] The BOM object modeling module defines relevant information for the BOM object model based on the type information of each component in the product design extracted from the product design data. The relevant information for the BOM object model includes the object type, derivation relationship, basic attributes, custom attributes, object lifecycle, object version rules, and validation rules.

[0031] The BOM relationship modeling module defines relevant information about the BOM relationship model based on the relationships between various components in the product design extracted from the product design data. This information includes basic information about the relationship model, the attributes contained in the relationship, the start and end points of the relationship, the cardinality of the relationship, object revision rules, and object cloning rules. The basic information about the relationship model includes name, icon, and description.

[0032] The BOM page modeling module provides a visual configuration for the predefined BOM object model and BOM relationship model, and generates the corresponding page model. The page model is used to display the business data generated based on the BOM object model and BOM relationship model.

[0033] The BOM object management module is used to manage the business data of the BOM object model. For different object types in different BOM object models, different page models are called to add and modify the corresponding object type data. The BOM object management module provides users with checkout, check-in, revision and baseline functions.

[0034] The BOM process management module manages the running status of all approval processes related to the BOM object model, as well as process instances in non-running states. It manages process initiation and closure, process operation, process approval, and template usage through approval methods. During the operation of a business process instance, it detects whether the business process instance is blocked at the current step by probing the range of the BPMstepTime value of the currently running business process instance. If a blockage is confirmed, the BOM process management module pauses the business process instance and promptly notifies the process approval person to conduct a detailed check on the running status of the business process instance.

[0035] The BOM relationship view management module adopts a multi-view approach to manage different needs at each stage of product design, process, and manufacturing. Each view is associated with a predefined BOM relationship model, allowing for the addition of relationship instances between BOM object models and the maintenance of relationship attributes. Multiple views can be converted between different views based on the BOM relationship model.

[0036] The BOM data storage module receives business data from the already edited and generated object model and imported data from the BOM data import, stores the imported data, and displays the current data storage status.

[0037] The BOM data import module extracts and imports the BOM information of each component from the product data designed in the product design tool. The BOM information includes model data, business data, and relational data. The extracted model data includes object type information, object attribute information, object version information, object lifecycle status information, role / department information, and role / permission information. The extracted business data includes object reference information, object representation reference information, object instance information, and object form instance information. The extracted relational data includes aggregation relationships, instance ownership information, and pointing relationships.

[0038] The BOM data conversion module converts different views based on the BOM relationship model. It records a conversion log, which includes function operation codes, relationship model change information, parent node object information before the change, target node object information before the change, relationship data identifiers before the change, parent node object information after the change, target node object information after the change, and relationship data identifiers after the change. The BOM data conversion module also collects the identifiers of abnormal objects, the type identifiers of abnormal objects, the cause codes of the abnormalities, the duration of the abnormalities, and the alarm identifiers for abnormalities.

[0039] The BOM data traceability module provides functions including BOM view traceability analysis, BOM object historical version traceability analysis, and BOM object usage traceability analysis. Among them, the BOM view traceability analysis function traces the relationship structure of the selected object data in different views and displays the changes of the selected object in different views according to the conversion log recorded by the BOM data conversion module. The BOM object historical version viewing function displays the information of each revision version of the object based on the completed revision process records of the selected object. The BOM object usage traceability function displays the usage of the selected object in various views, and traces the selected object upwards from its original view, expanding layer by layer until the top-level node.

[0040] The function can be implemented by hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above function.

[0041] In one possible design, the above-described device includes a memory and a processor. The memory stores one or more computer instructions that support the device in performing the corresponding methods described above, and the processor is configured to execute the computer instructions stored in the memory. The device may also include a communication interface for communicating with other devices or communication networks.

[0042] Fourthly, embodiments of this disclosure provide an electronic device including a memory, a processor, and a computer program stored in the memory, wherein the processor executes the computer program to implement the method described in any of the above aspects.

[0043] Fifthly, embodiments of this disclosure provide a computer-readable storage medium for storing computer instructions used by any of the above-described devices, which, when executed by a processor, are used to implement the methods described in any of the above aspects.

[0044] In a sixth aspect, embodiments of this disclosure provide a computer program product comprising computer instructions which, when executed by a processor, are used to implement the methods described in any of the preceding aspects.

[0045] The technical solutions provided in this disclosure can include the following beneficial effects:

[0046] This disclosure enables the rapid formation of a structured, flexible, and unified core product data model by modeling objects and relationships. Different forms of BOM models are created at different stages of product design, process, and production. These models are interdependent and progressively layered, and their influence extends throughout the entire design and manufacturing process. BOM object modeling management ensures data is passed down the hierarchy without distortion, supports data backtracking throughout the product lifecycle, and serves as the foundation and bridge for data resource sharing and integration between all stages from design to manufacturing.

[0047] It should be understood that the above general description and the following detailed description are exemplary and explanatory only, and are not intended to limit this disclosure. Attached Figure Description

[0048] Other features, objects, and advantages of this disclosure will become more apparent from the following detailed description of non-limiting embodiments, taken in conjunction with the accompanying drawings. In the drawings:

[0049] Figure 1 A flowchart is shown illustrating a relationship modeling and management method based on a product BOM structure according to an embodiment of the present disclosure;

[0050] Figure 2 A schematic diagram of the structure of a relationship modeling management system based on a product BOM structure according to an embodiment of the present disclosure is shown;

[0051] Figure 3 A flowchart illustrating the overall implementation of a relationship modeling and management method based on a product BOM structure according to an embodiment of the present disclosure is shown.

[0052] Figure 4 This is a schematic diagram of the structure of an electronic device suitable for implementing a relational modeling and management method based on a product BOM structure according to an embodiment of the present disclosure. Detailed Implementation

[0053] In the following, exemplary embodiments of the present disclosure will be described in detail with reference to the accompanying drawings to enable those skilled in the art to readily implement them. Furthermore, for clarity, portions unrelated to the description of the exemplary embodiments have been omitted from the drawings.

[0054] In this disclosure, it should be understood that terms such as “comprising” or “having” are intended to indicate the presence of features, figures, steps, behaviors, components, parts or combinations thereof disclosed in this specification, and do not preclude the possibility of the presence or addition of one or more other features, figures, steps, behaviors, components, parts or combinations thereof.

[0055] It should also be noted that, unless otherwise specified, the embodiments and features described in this disclosure can be combined with each other. This disclosure will now be described in detail with reference to the accompanying drawings and embodiments.

[0056] This disclosure rapidly forms a structured, flexible, and unified core product data model by modeling objects and relationships. Different forms of BOM models are created at different stages of product design, process, and production. These models are interdependent and progressively layered, and their influence extends throughout the entire design and manufacturing process. BOM object modeling management ensures data is passed down the hierarchy without distortion, supports data backtracking throughout the product lifecycle, and serves as the foundation and bridge for data resource sharing and integration between all stages from design to manufacturing.

[0057] The technical problem this disclosure aims to solve is to meet the needs of BOM data resource sharing and integrated storage across all stages from product design to manufacturing. It proposes an object modeling management method and system based on the interconnection of product BOM data. This method utilizes object modeling to convert file-type design drawings into model data based on predefined object models, allowing the data to circulate throughout the product lifecycle. This achieves interconnection of model data and resource sharing and integration, and provides traceability analysis capabilities. It can continuously optimize and configure various models, meeting the needs of collaborative work and data interconnection across all stages of a company's product development.

[0058] Figure 1 A flowchart illustrating a relationship modeling and management method based on a product BOM structure according to an embodiment of this disclosure is shown. Figure 1 As shown, the method includes the following steps:

[0059] Import product design data generated by the product design tool, and extract the type information of each component in the product design and the relationship information between each component from the imported product design data;

[0060] Based on the type information of each component in the product design, define the relevant information of multiple object models to structurally represent the types of each component, the attributes they contain, the life cycle of each component type and its life cycle status, and define an entity storage structure based on the relevant information of the object models for the structured storage of product data.

[0061] Based on the relationship information of each component in the product design and the relevant information of the multiple object models, define the relevant information of the relationship model between the multiple object models;

[0062] Based on the relevant information of the object model and the relationship model, a page model is created using a visual WYSIWYG page modeling tool. The page model is used to display relevant information of the business data generated by the object model and the relationship model.

[0063] In this embodiment, product design data generated by design tools such as CAD drawing tools, for example, designing a skateboard, which includes a board, wheels, and bearings, will ultimately generate skateboard object models, board object models, wheel object models, and bearing object models by extracting these parts from the product design data. Simultaneously, the design drawing will indicate that the skateboard is composed of a board, wheels, and bearings, thus generating a relationship model between the skateboard object and the board, wheel, and bearing objects.

[0064] In some embodiments, the method further includes:

[0065] Retrieve stored business data; the business data includes object data and relationship data;

[0066] Add, edit, and remove object data; parse the acquired object data according to the type and attribute information defined in the corresponding object model, split the object data into basic object attribute data and dynamic object attribute data, and finally store it in the entity storage structure corresponding to the object model;

[0067] The acquired relational data is parsed according to the corresponding relational model, and then parsed into relational association data and relational attribute data, which are finally stored in the entity storage structure corresponding to the relational model; the business data is loaded and displayed using the page model.

[0068] Monitor the lifecycle status of the business data and perform corresponding operations on the business data based on the lifecycle status; wherein, changes in the lifecycle status are approved by calling the corresponding approval process configured when defining the lifecycle; user revision operations on business data or creation of change baselines are approved by calling the corresponding approval process, and the status of the process instance is monitored by starting the corresponding task, and intervention operations are performed on the process instance.

[0069] Business data includes object data and relational data. Taking skateboards as an example again, if a user imports information about skateboard number 001, including information such as name, number, lifecycle status, and responsible person, the system will find the object model of the skateboard and assemble the imported information into basic attribute data (name, number, lifecycle status) and dynamic attribute data (responsible person) according to the attribute definition of the object model. Then, according to the entity storage structure (database table) defined by the object model, the system will perform the corresponding save operation.

[0070] Lifecycle and lifecycle state are defined when defining the object model. Different object models have different lifecycles, which can be defined by the administrator according to business needs. At the same time, functional permissions can be defined for different states. For example, users can perform check-in and check-out operations in the "working" state, but not in the "published" state.

[0071] In some embodiments, the method further includes:

[0072] Manage the addition and removal of relationship data between object data corresponding to the object model under multiple stages of BOM relationship view, as well as the conversion of BOM relationship view at different stages, and control the consistency of object data;

[0073] Adding and removing relational data;

[0074] Transform relational data under different relational views to make business data between different views continuous and transferable;

[0075] Log data generated by transforming business data and relational data.

[0076] In some embodiments, the BOM relationship view management module adopts a multi-view approach. These views are sequentially divided into Design BOM (EBOM), Process BOM (PBOM), Manufacturing BOM (MBOM), Delivery BOM (BBOM), Assurance BOM (SBOM), and Operations BOM (OBOM).

[0077] In some embodiments, different views may be used at different stages. For example, the EBOM view is used in the product design stage, while the MBOM view is used in the product manufacturing stage. The object data in different stages all come from the same object model, only the relational data is different. This ensures that the object data is a unified data source throughout the entire process, thus guaranteeing data consistency.

[0078] In some embodiments, relational data under different relational views can be transformed, but object data remains unchanged. This ensures that object data is consistent across different views and that relational data is traceable.

[0079] In some embodiments, the method further includes:

[0080] Relevant data is obtained from the BOM data storage module to trace the flow of the entire product lifecycle. The relevant data includes historical data of various versions of the object model, relationship change data when different BOM views are converted, historical running data of various processes, and log data of various business data operations. The relevant data is then assembled and displayed.

[0081] Among them, relationship change data can be understood as the trace data of relationship data changes under different relationship views.

[0082] The historical operation data of each process can be understood as the approval process when the life cycle status changes as mentioned above, as well as the historical operation data involved in the approval process corresponding to operations such as revision and baseline change, including but not limited to approval opinions, process opening time, process processing time, etc. This data can reflect whether the approval process runs smoothly and which part of the process can be optimized.

[0083] Figure 2 A schematic diagram of a relationship modeling and management system based on a product BOM structure according to an embodiment of this disclosure is shown. Figure 2As shown, the system includes a BOM object modeling section, a BOM management section, and a data processing section. The BOM object modeling section includes: a BOM object modeling module, a BOM relationship modeling module, and a BOM page modeling module. The BOM management section includes: a BOM object management module, a BOM process management module, and a BOM relationship view management module. The data processing section includes: a BOM data storage module, a BOM data import module, a BOM data conversion module, and a BOM data traceability module.

[0084] The BOM object modeling module is implemented as follows: After system startup, the BOM object modeling module can define relevant information about the BOM object model according to user requirements. This information includes the type of the BOM object, the derivation relationships between objects, the basic attributes of the BOM object, the custom attributes of the BOM object, the lifecycle of the BOM object, the versioning rules of the BOM object, and validation rules. The BOM relationship modeling module can define relevant information about the relationship model according to user requirements. This information includes the basic information of the relationship model, the attributes contained in the relationship model, and the start and end points of the relationship model. All relationship models have a start point and an end point; the arrow always points to the end point. All relationships exist between two business objects or between a business object and a relationship: one at the start point and one at the end point. The "Type / Relationship" of the starting point can be the same as that of the ending point. The cardinality of the relationship model indicates the number of connections of this type a single object can have, including one or more. The object's revision rules specify how revisions to connected objects should be handled. These rules are intended to assist users and reduce manual connection activities. There are three types of revision rules: None, Float, and Replicate. When the connecting end uses the "None" rule, revising the starting object does not change the established connections, meaning the revised object will not automatically be associated with it. The Float revision rule specifies that the relationship should be moved whenever an object is revised. When using the Float revision rule, the unrevised (or older) object loses its connection to its other end, which will automatically be attached to the revised object. Now, the older version of the object will be unattached, while the new version will have the relationship. The Replicate revision rule automatically creates new connections whenever an object at one end is revised, which can result in an object potentially having multiple connections of the same relationship type simultaneously. Therefore, any join end using the copy revision rule must also use the cardinality described earlier in this chapter; if a cardinality of 1 is used, copying will not work. This floating of the join ensures that the latest versions of objects are linked together. The object cloning rule, which is the same as the revision rule, is the rule used when cloning objects at the join end.

[0085] The object type defines a business object and its set of attributes. One type can be derived from another, and derived types share characteristics with their parent and sibling classes. Attribute definitions describe the basic and characteristic information of the business object. Defining the object's lifecycle allows for the management and control of the BOM object's state throughout the design and manufacturing process, as well as the control of permissions in different states. Defining version rules allows for version changes during object revisions. Defining validation rules allows for validation during the creation, modification, and deletion of BOM objects, ensuring their correctness. The defined object model satisfies the characteristics of BOM data structure—high dynamism and high consistency requirements—allowing data to be shared and transferred across different stages such as product design, process, and production.

[0086] The BOM page modeling module provides a visual page modeling configuration for pre-created BOM object models and BOM relationship models, used to display business data generated based on the BOM object models and BOM relationship models. This primarily includes form modeling tools and view modeling tools. The form modeling tool uses a drag-and-drop modular approach for both B / S and C / S basic graphical user interfaces (GUIs). Based on basic controls, advanced controls, layout controls, custom buttons, and custom styles, it quickly builds data entry form page models corresponding to the BOM object model and BOM relationship model. The data format of the form page model is XML, with XML elements representing specific form control elements. The XML element name is the name of the form control element, and the parameters within the XML element are the configurable parameters of the form control element. The view modeling tool uses a drag-and-drop modular approach for both B / S and C / S basic GUIs. Based on view layout controls, list display controls, BOM tree display controls, and form detail controls, it quickly builds diverse data display page models corresponding to the BOM object model and BOM relationship model. The data format of the view page model is XML, with XML elements representing specific view control elements. The XML element name is the name of the view control element, and the parameters within the XML element are the configurable parameters of the view control element.

[0087] The BOM management section is implemented as follows:

[0088] The BOM object management module allows for the addition and modification of corresponding object type data by calling different page models for different object types; it also allows direct import of products designed in the design software via the BOM import function. The object management module manages BOM object business data. After BOM object modeling in the BOM object modeling module and page modeling in the BOM page modeling module are completed, the BOM object management module can call different page models for different object types to add and modify corresponding object type data; it also allows direct import of products designed in the design software via the BOM import function.

[0089] The BOM object management module can provide the following functions:

[0090] The BOM object is checked out before its attributes can be modified. The checkout function consists of two actions: first, the checked object is locked to make it read-only and prevent it from being checked out by other users; then, the business data of the checked object is copied. Subsequent revision operations are performed on the copied data, which ensures that the object will not affect normal operation or be affected by revisions by other users at the same time.

[0091] Provides a check-in function. After modifying the attributes of the checked-in BOM object, a check-in operation is required to make it effective. The check-in function includes two actions: first, change the original object data to historical version data, and then increase the version number of the checked-in copy object data to the current version number and set it to the check-in status.

[0092] It provides lifecycle flow functionality. Different object types will have different lifecycles and lifecycle stages defined in the BOM modeling module according to business needs, as well as approvers for each stage. Once the object data is created, it is in the first stage of the lifecycle. Whenever a stage change is required, the corresponding approver needs to approve it before the stage status will be changed.

[0093] The BOM modeling module provides a revision function. Different object types will have different lifecycles defined in the BOM modeling module according to business needs. Each lifecycle will be bound to a different revision process. When revising, different revision processes will be activated according to the object type of the object being revised. When important attributes of an object are changed, the revision process needs to be initiated. The entire revision process can be tracked and managed. After the revision process is approved, the version of the business data will be upgraded, and the original version will become the historical version.

[0094] Provides a baseline function, which can create an initial baseline and add BOM objects to this baseline. The product baseline is used to solidify the technical state of a product at a certain stage and ensure that the state is permanently saved. The product structure tree under this baseline is solidified, and all its parts and design document versions will no longer change with later modifications.

[0095] The BOM process management module manages the running status of all BOM object-related approval processes, as well as process instances in non-running states. For example, when a part is created, it is in the "Creation" stage of the part lifecycle process. At this time, the engineer conducts detailed design of the part in all aspects. Once the design is completed, the engineer submits the part to the "Review" stage of the part lifecycle process for review. If the reviewer finds errors in the design, it is rejected and returned to the engineer. The engineer then modifies the part according to the review comments and resubmits it, and so on. If the review is approved, the part is submitted to the "Issuance" stage of the part lifecycle process, and the part is frozen. If modifications are needed, a revision process needs to be initiated to revise the part to a new version, and then modifications are made on the new version. The system manages the initiation and closure of processes, process operation, process approval, template usage, and approval methods. During the execution of a business process instance, the system detects the health of the process at the current step by probing the range of the process step processing time (BPMstepTime) value (this range has a lower limit, generally 14000s, with no upper limit). When the lower limit is exceeded, it indicates that the current step is blocked for an extended period. The BOM process management module needs to pause the process instance and promptly notify the process approval person to conduct a detailed check of the process instance's running status. For business process instances that have completed their running state, the BOM process management module needs to detect their completion status, set the running status of the business process instance to non-running state, disconnect the business process instance from the corresponding form, and delete the business process instance from the running status queue.

[0096] The BOM relationship view management module employs a multi-view approach. Based on the different needs of each stage of product design, process, and manufacturing, BOMs can be categorized into different types, and the structure and attributes of BOMs at different stages vary significantly. Therefore, a multi-view management approach is adopted. These views are sequentially divided into Design BOM (EBOM), Process BOM (PBOM), Manufacturing BOM (MBOM), Delivery BOM (BBOM), Assurance BOM (SBOM), and Operations BOM (OBOM). Each view can be linked to a predefined BOM relationship model, allowing for the addition of relationship instances between BOM objects and the maintenance of relationship attributes. The multiple BOM views are hierarchical and interdependent, and different BOM view conversions can be performed based on the BOM relationship model.

[0097] The data processing is implemented as follows: Tasks involving data import, transformation, storage, and traceability will be performed on business data and historical data generated during the product lifecycle. Data import tasks will be established. Based on the configuration, the system will extract product data from the product design software. The extracted model data includes object type information, object attribute information, object version information, object lifecycle status information, role / department information, role / permission information, object reference information, object representation reference information, object instance information, and object representation instance information. The extracted core model relationship data includes aggregation, instance affiliation, and pointer. The imported model attribute information table, which combines the above data items, is shown below.

[0098]

[0099] In addition, for imported data that encounters anomalies during the import process, the BOM data import module also needs to collect the identifier of the abnormal data, the identifier of the abnormal data object type, the error reason code, the duration of the error, and the error alarm identifier. The above attributes form the abnormal model information attribute table as shown below.

[0100]

[0101] The BOM data import module extracts component BOM information designed in CAD design tools and imports it into this system. The extracted model data includes object type information (OMTypeInfo), object attribute information (OMAttributeInfo), object version information (OMVersionInfo), object lifecycle status information (OMLifecycleInfo), role / department information (RoleDepartInfo), and role / authority information (RoleAuthInfo). The extracted core model business data includes object reference information (Reference), object representation reference information (RepReference), object instance information (Instance), and object form instance information (RepInstance). The extracted core model relationship data includes aggregation (Aggregation), instance ownership (IsInstanceOf), and pointers (PointsTo). In addition, for imported data that encounters exceptions during import, the BOM data import module also needs to collect the exception data identifier (ObjectID), exception data object type identifier (OMTypeID), exception reason code (ExceptionReasonCode), exception duration (ExceptionDuringTime), and exception alarm identifier (ExceptionFlag). Data import methods include proactive import, periodic cyclic import, and condition-triggered import.

[0102] The default data import method is proactive, but it can also be configured for scheduled import. For design data with high business sensitivity, a condition-triggered import method can be used. Imported BOM data can be passed down through the BOM data conversion module to different BOM views. The conversion process replaces and expands the existing BOM structure based on the relational model definition and the relational model associated with the BOM view, and records a conversion log. The conversion log includes the function operation code FunOperationCode, relational model change information OMRelationChangeInfo, parent node object information before the change (PrimaryParentObject), target node object information before the change (PrimaryTargetObject), relational data identifier (PrimaryLinkID), parent node object information after the change (CurrentParentObject), target node object information after the change (CurrentTargetObject), and relational data identifier (CurrentLinkID). The conversion log model attribute information table, which combines the above data items, is shown below.

[0103]

[0104] The BOM data import and conversion modules transfer data to the data storage module for storage. The default storage strategy is "8+64," meaning a minimum storage unit of 8 bytes and a data block size of 64 MB. The storage strategy follows a sequence of "multi-machine multi-backup strategy + distributed storage strategy + incremental backup strategy + global overall backup strategy," selecting "local disk storage + remote disk + data center storage + remote network storage" to meet the storage capacity requirements for massive amounts of data.

[0105] The data storage module receives the edited and generated object model business data and the data imported by the BOM data import module. It stores the data and checks the current data storage status, namely the current hard disk space utilization, data storage location and directory index status. It selects a data storage strategy, which includes the current minimum storage unit size (8B, 64B, 128B), data block size (64MB, 128MB, 256MB), global local data storage, single-machine single backup strategy, single-machine multiple backup strategy, multi-machine multiple backup strategy, distributed storage strategy, incremental backup strategy, and global overall backup strategy. It selects a storage source, namely local disk storage, remote disk, data center storage, and remote network storage, to meet the data storage capacity.

[0106] The BOM data conversion module: Multiple BOM views are hierarchical and interdependent, allowing for view conversion between different BOMs based on the BOM relationship model. The relationship model defines not only relationships between objects but also relationships between objects and relationships, enabling the replacement of existing relationships with new ones or the extension of existing object attributes. The conversion between BOM views is sequential and progressive: Design BOM (EBOM), Process BOM (PBOM), Manufacturing BOM (MBOM), Delivery BOM (BBOM), Assurance BOM (SBOM), and Operations BOM (OBOM) can be converted sequentially, but not in reverse. After data conversion, all data in the BOM data conversion module is in a checkout state. It requires approval through the BOM conversion process before being changed to check-in and published. The BOM data conversion module records conversion logs, including function operation codes (FunOperationCode), relationship model change information (OMRelationChangeInfo), and variable... The BOM data conversion module needs to collect the following information: the parent node object information before the change (PrimaryParentObject), the target node object information before the change (PrimaryTargetObject), the relationship data identifier (PrimaryLinkID), the parent node object information after the change (CurrentParentObject), the target node object information after the change (CurrentTargetObject), and the relationship data identifier (CurrentLinkID). In addition, for imported data that encounters anomalies during the conversion process, the BOM data conversion module also needs to collect the abnormal object data identifier (ObjectID), the abnormal data object type identifier (OMTypeID), the abnormal reason code (ExceptionReasonCode), the abnormal duration (ExceptionDuringTime), and the abnormal alarm identifier (ExceptionFlag).

[0107] The BOM data traceability module can obtain relevant data from the data storage module, including historical data of the object model, relationship change data in various views, historical operation data of various processes, and log data of various data operations, and assemble and display this data. Since the data has gone through the entire product lifecycle, it is necessary to optimize the model at each stage. By comparing the historical versions of the object model data, the frequency of attribute changes and attribute validation rules can be analyzed to optimize the object model. By analyzing the instance anomaly information and the health of steps in the historical operation data of each process, the process structure can be optimized. By analyzing the relationship change data in various views, the operation mode of relationship transformation can be extracted, and a trusted space model and an untrusted space model can be established. Establishing a trusted space model involves extracting similar data from the normally operating transformation data, designing a reasonable relationship model, and merging them. Establishing an untrusted space model involves extracting similar data from the abnormally operating transformation data and designing a reasonable relationship model.

[0108] The BOM data traceability module provides functions including BOM view traceability analysis, BOM object historical version traceability analysis, and BOM object usage traceability analysis. The BOM view traceability analysis function traces the relationship structure of selected object data across different BOM views. Based on the conversion log information recorded by the BOM data conversion module, it displays the changes of the selected object in different views, using a network structure diagram for traceability. The BOM object historical version viewing function displays the information of each revision version of the selected object based on the completed revision process records, including the attribute information contained in each version, the BOM structure information of multiple views with this object as the root, the usage information of this object version, and the reason for the version change. The BOM object usage traceability function displays the usage of the selected object in various BOM views. The selected object is traced upwards from its BOM view, expanding layer by layer until the top-level node. The BOM data traceability module can intuitively query the changes of object data, generate multiple BOM tables, maximize the reuse value of object model data, trace the development and change process of BOM data, and use the comparison display between different versions of data to more effectively control BOM data and trace the reasons and processes of changes.

[0109] Figure 3 This diagram illustrates the overall implementation flowchart of a relationship modeling and management method based on a product BOM structure according to an embodiment of the present disclosure. Figure 3 As shown, the method includes the following steps:

[0110] Data import and model definition: The BOM data import module processes the product design data generated by the product design tool, extracting the type information of each component and the relationship information between them. Based on the type information of each component, it defines the relevant information of multiple object models and the relationship model information between them. This information is then imported into the BOM data storage module. The BOM object modeling module uses the object model information in the BOM data storage module to define the object models. The relevant information of the definable object models includes the object type, derivation relationship, basic attributes, custom attributes, lifecycle, version rules, and validation rules. After the object model information is defined, an entity storage structure, such as a database table, can be created based on the defined object model.

[0111] The BOM relational modeling module calls the relational model information in the BOM data storage module and the predefined object models in the BOM object modeling module to define the BOM relational model between multiple object models. The definable relational information includes the basic information of the relational model, the attributes contained in the relation, the start and end points of the relation, the cardinality of the relation, the revision rules of the object, and the cloning rules of the object.

[0112] The BOM page modeling module uses pre-created BOM object models and BOM relationship models. It employs a visual, WYSIWYG page modeling tool to create page models that display business data generated based on the BOM object models and BOM relationship models.

[0113] Maintenance and management of object business data: Business data information is imported from the BOM data storage module. Based on the object and relational models defined above, it is parsed and stored in the BOM data storage module. Then, the BOM data storage module is called to retrieve the business data stored in the data storage medium and load and display it according to the page model defined above. The BOM object management module is responsible for monitoring the lifecycle status of the object model business data and performing user operations such as check-in, check-out, addition, modification, revision, and creation of change baselines. If the user needs to revise the selected business data or create a change baseline, the corresponding approval process needs to be initiated by calling the BOM process management module. The process can be monitored using the BOM process management module, and intervention operations can be performed on process instances. BOM data is transferred and integrated throughout the product process: the BOM relationship view management module is responsible for managing the addition and removal of relationships between business data of object models under multiple stage views, controlling the consistency of business data. The BOM relationship view management module calls the BOM data storage module to add and remove relationship data, and calls the BOM data transformation module to transform business data and relationship data under different views, so that data between views is continuous and transferable. The BOM data storage module is called to store the transformation log data, making the transformation process safe, controllable and traceable.

[0114] BOM Data Traceability Analysis: The BOM data traceability module can retrieve relevant data from the data storage module, including historical data of the object model, relationship change data in various views, historical operation data of various processes, and log data of various data operations. This data is then assembled and presented. Since the data has spanned the entire product lifecycle, the models at each stage need optimization. By comparing historical versions of the object model data, the frequency of attribute changes and attribute validation rules can be analyzed to optimize the object model. Analysis of instance anomalies and the health of steps in the historical operation data of each process is used to optimize the process structure. Analysis of relationship change data in various views extracts the operational patterns of relationship transformations, establishing trusted and untrusted space models. Establishing a trusted space model involves extracting similar data from normally functioning transformation data, designing and merging reasonable relationship models. Establishing an untrusted space model involves extracting similar data from abnormally functioning transformation data and designing reasonable relationship models.

[0115] The following are embodiments of the apparatus disclosed herein, which can be used to execute embodiments of the method disclosed herein.

[0116] According to an embodiment of the present disclosure, a relational modeling and management device based on a product BOM structure can be implemented as part or all of an electronic device through software, hardware, or a combination of both. The relational modeling and management device based on a product BOM structure includes:

[0117] The import module is configured to import product design data generated from the product design tool and extract the type information of each component in the product design and the relationship information between each component from the imported product design data.

[0118] The first definition module is configured to define relevant information of multiple object models based on the type information of each component in the product design. This is used to structurally represent the types of each component in the product, the attributes they contain, the life cycle of each component type and its life cycle status. Based on the relevant information of the object models, an entity storage structure is defined for the structured storage of product data.

[0119] The second definition module is configured to define the relevant information of the relationship model between the multiple object models based on the relationship information of each component in the product design and the relevant information of the multiple object models;

[0120] A creation module is configured to create a page model using a visual, WYSIWYG page modeling tool based on information related to the object model and information related to the relationship model. The page model is used to display information related to the business data generated by the object model and the relationship model.

[0121] The relationship modeling and management device based on the product BOM structure in this embodiment corresponds to the relationship modeling and management method based on the product BOM structure described above. For specific details, please refer to the description of the relationship modeling and management method based on the product BOM structure described above, which will not be repeated here.

[0122] Figure 4 This is a schematic diagram of the structure of an electronic device suitable for implementing a relational modeling and management method based on a product BOM structure according to an embodiment of the present disclosure.

[0123] like Figure 4As shown, the electronic device 400 includes a processing unit 401, which can be implemented as a CPU, GPU, FPGA, NPU, or other processing unit. The processing unit 401 can execute various processes according to any of the methods described above in this disclosure, based on a program stored in the read-only memory (ROM) 402 or a program loaded from the storage portion 408 into the random access memory (RAM) 403. The RAM 403 also stores various programs and data required for the operation of the electronic device 400. The processing unit 401, ROM 402, and RAM 403 are interconnected via a bus 404. An input / output (I / O) interface 405 is also connected to the bus 404.

[0124] The following components are connected to I / O interface 405: an input section 406 including a keyboard, mouse, etc.; an output section 407 including a cathode ray tube (CRT), liquid crystal display (LCD), etc., and speakers, etc.; a storage section 408 including a hard disk, etc.; and a communication section 409 including a network interface card such as a LAN card, modem, etc. The communication section 409 performs communication processing via a network such as the Internet. A drive 410 is also connected to I / O interface 405 as needed. A removable medium 411, such as a disk, optical disk, magneto-optical disk, semiconductor memory, etc., is installed on drive 410 as needed so that computer programs read from it can be installed into storage section 408 as needed.

[0125] In particular, according to embodiments of this disclosure, any of the methods described above in the embodiments of this disclosure can be implemented as a computer software program. For example, embodiments of this disclosure include a computer program product comprising a computer program tangibly embodied on a machine-readable medium, the computer program containing program code for performing any of the methods in the embodiments of this disclosure. In such an embodiment, the computer program can be downloaded and installed from a network via communication section 409, and / or installed from removable medium 411.

[0126] The flowcharts and block diagrams in the accompanying drawings illustrate the architecture, functionality, and operation of possible implementations of systems, methods, and computer program products according to various embodiments of this disclosure. In this regard, each block in a flowchart or block diagram may represent a module, segment, or portion of code containing one or more executable instructions for implementing a specified logical function. It should also be noted that in some alternative implementations, the functions indicated in the blocks may occur in a different order than those indicated in the drawings. For example, two consecutively indicated blocks may actually be executed substantially in parallel, and they may sometimes be executed in reverse order, depending on the functions involved. It should also be noted that each block in the block diagrams and / or flowcharts, and combinations of blocks in the block diagrams and / or flowcharts, can be implemented using a dedicated hardware-based system that performs the specified function or operation, or using a combination of dedicated hardware and computer instructions.

[0127] The units or modules described in the embodiments of this disclosure can be implemented in software or hardware. The described units or modules can also be located in a processor, and the names of these units or modules do not necessarily constitute a limitation on the unit or module itself.

[0128] In another aspect, this disclosure also provides a computer-readable storage medium, which may be a computer-readable storage medium included in the apparatus described in the above embodiments; or it may be a standalone computer-readable storage medium not assembled into a device. The computer-readable storage medium stores one or more programs that are used by one or more processors to perform the methods described in this disclosure.

[0129] The above description is merely a preferred embodiment of this disclosure and an explanation of the technical principles employed. Those skilled in the art should understand that the scope of the invention involved in this disclosure is not limited to technical solutions formed by specific combinations of the above-described technical features, but should also cover other technical solutions formed by arbitrary combinations of the above-described technical features or their equivalents without departing from the inventive concept. For example, technical solutions formed by substituting the above-described features with (but not limited to) technical features disclosed in this disclosure that have similar functions.

Claims

1. A relationship modeling and management method based on product BOM structure, characterized in that, include: Import product design data generated by the product design tool, and extract the type information of each component in the product design and the relationship information between each component from the imported product design data; Based on the type information of each component in the product design, define the relevant information of multiple object models to structurally represent the types of each component, the attributes they contain, the life cycle of each component type and its life cycle status, and define an entity storage structure based on the relevant information of the object models for the structured storage of product data. Based on the relationship information of each component in the product design and the relevant information of the multiple object models, define the relevant information of the relationship model between the multiple object models; Based on the relevant information of the object model and the relevant information of the relationship model, a page model is created using a visual WYSIWYG page modeling tool. The page model is used to display the relevant information of the business data generated by the object model and the relationship model. The method further includes: Retrieve stored business data; the business data includes object data and relationship data; Add, edit, and remove object data; The acquired object data is parsed according to the type and attribute information defined in the corresponding object model, and the object data is split into basic object attribute data and dynamic object attribute data, and finally stored in the entity storage structure corresponding to the object model. Adding and removing relational data; The acquired relational data is parsed according to the corresponding relational model, and then parsed into relational association data and relational attribute data, and finally stored in the entity storage structure corresponding to the relational model; The business data is loaded and displayed using the page model. Monitor the lifecycle status of the business data and perform corresponding operations on the business data based on the lifecycle status; wherein, changes in the lifecycle status are approved by calling the corresponding approval process configured when defining the lifecycle; user revision operations on business data or creation of change baselines are approved by calling the corresponding approval process, and the status of the process instance is monitored by starting the corresponding task, and intervention operations are performed on the process instance.

2. The method according to claim 1, characterized in that, The method further includes: Manage the addition and removal of relationship data between object data corresponding to the object model under multiple stages of BOM relationship view, as well as the conversion of BOM relationship view at different stages, and control the consistency of object data; Transform relational data under different relational views to make business data between different views continuous and transferable; Log data generated by transforming business data and relational data.

3. The method according to claim 1, characterized in that, The method further includes: Relevant data is obtained from the BOM data storage module to trace the flow of the entire product lifecycle. The relevant data includes historical data of various versions of the object model, relationship change data when different BOM views are converted, historical running data of various processes, and log data of various business data operations. The relevant data is then assembled and displayed.

4. A relationship modeling and management device based on product BOM structure, characterized in that, include: The import module is configured to import product design data generated from the product design tool and extract the type information of each component in the product design and the relationship information between each component from the imported product design data. The first definition module is configured to define relevant information of multiple object models based on the type information of each component in the product design. This is used to structurally represent the types of each component in the product, the attributes they contain, the life cycle of each component type and its life cycle status. Based on the relevant information of the object models, an entity storage structure is defined for the structured storage of product data. The second definition module is configured to define the relevant information of the relationship model between the multiple object models based on the relationship information of each component in the product design and the relevant information of the multiple object models; A creation module is configured to create a page model using a visual, WYSIWYG page modeling tool based on information related to the object model and information related to the relationship model. The page model is used to display information related to the business data generated by the object model and the relationship model. The device further includes a module implemented as follows: Retrieve stored business data; the business data includes object data and relationship data; Add, edit, and remove object data; The acquired object data is parsed according to the type and attribute information defined in the corresponding object model, and the object data is split into basic object attribute data and dynamic object attribute data, and finally stored in the entity storage structure corresponding to the object model. Adding and removing relational data; The acquired relational data is parsed according to the corresponding relational model, and then parsed into relational association data and relational attribute data, and finally stored in the entity storage structure corresponding to the relational model; The business data is loaded and displayed using the page model. Monitor the lifecycle status of the business data and perform corresponding operations on the business data based on the lifecycle status; wherein, changes in the lifecycle status are approved by calling the corresponding approval process configured when defining the lifecycle; user revision operations on business data or creation of change baselines are approved by calling the corresponding approval process, and the status of the process instance is monitored by starting the corresponding task, and intervention operations are performed on the process instance.

5. A relational modeling and management system based on product BOM structure, characterized in that, include: BOM object modeling, BOM management, and data processing; The BOM object modeling part includes: a BOM object modeling module, a BOM relationship modeling module, and a BOM page modeling module; the BOM management part includes a BOM object management module, a BOM process management module, and a BOM relationship view management module; the data processing part includes: a BOM data storage module, a BOM data import module, a BOM data conversion module, and a BOM data traceability module. The BOM object modeling module defines relevant information about the BOM object model based on the type information of each component in the product design extracted from the product design data. The relevant information about the BOM object model includes the object type, derivation relationship, basic attributes, custom attributes, object lifecycle, version rules, and validation rules. The BOM relationship modeling module defines relevant information about the BOM relationship model based on the relationships between various components in the product design extracted from the product design data. This information includes basic information about the relationship model, the attributes contained in the relationship, the start and end points of the relationship, the cardinality of the relationship, object revision rules, and object cloning rules. The basic information about the relationship model includes name, icon, and description. The BOM page modeling module provides a visual configuration for the predefined BOM object model and BOM relationship model, and generates the corresponding page model. The page model is used to display the business data generated based on the BOM object model and BOM relationship model. The BOM object management module manages business data for BOM object models. It calls different page models for different object types within different BOM object models to add and modify corresponding object type data. The module provides checkout, check-in, revision, and baseline functions. It also offers lifecycle management functionality; different object types in the BOM modeling module have different lifecycles and lifecycle stages defined according to business needs. Object data is in the first stage of its lifecycle upon creation, and any stage change requires approval from the relevant approver before the stage status is changed. The module further provides revision functionality for different object types in... The BOM modeling module defines different lifecycles based on business needs, and each lifecycle is bound to a different revision process. During revision, different revision processes are activated based on the object type of the object being revised. When important attributes of an object change, the revision process is initiated. The entire revision process can be tracked and managed. After the revision process is completed, the version of the business data will be upgraded, and the original version becomes a historical version. The BOM object management module provides a baseline function to create an initial baseline and add BOM objects to this baseline. The product baseline is used to solidify the technical state of a product at a certain stage, ensuring that this state is permanently saved. Under this baseline, the product structure tree is solidified, and all its component and design document versions will no longer change with later modifications. The BOM process management module manages the running status of all approval processes related to the BOM object model, as well as process instances in non-running states. It manages process initiation and closure, process operation, process approval, and template usage through approval methods. During the operation of a business process instance, it detects whether the business process instance is blocked at the current step by probing the range of the BPMstepTime value of the currently running business process instance. If a blockage is confirmed, the BOM process management module pauses the business process instance and promptly notifies the process approval person to conduct a detailed check on the running status of the business process instance. The BOM relationship view management module adopts a multi-view approach to manage different needs at each stage of product design, process, and manufacturing. Each view is associated with a predefined BOM relationship model, allowing for the addition of relationship instances between BOM object models and the maintenance of relationship attributes. Multiple views can be converted between different views based on the BOM relationship model. The BOM data storage module receives business data from the already edited and generated object model and imported data from the BOM data import, stores the imported data, and displays the current data storage status. The BOM data import module extracts and imports the BOM information of each component from the product data designed in the product design tool. The BOM information includes model data, business data, and relational data. The extracted model data includes object type information, object attribute information, object version information, object lifecycle status information, role / department information, and role / permission information. The extracted business data includes object reference information, object representation reference information, object instance information, and object form instance information. The extracted relational data includes aggregation relationships, instance ownership information, and pointing relationships. The BOM data conversion module converts different views based on the BOM relationship model. It records a conversion log, which includes function operation codes, relationship model change information, parent node object information before the change, target node object information before the change, relationship data identifiers before the change, parent node object information after the change, target node object information after the change, and relationship data identifiers after the change. The BOM data conversion module also collects the identifiers of abnormal objects, the type identifiers of abnormal objects, the cause codes of the abnormalities, the duration of the abnormalities, and the alarm identifiers for abnormalities. The BOM data traceability module provides functions including BOM view traceability analysis, BOM object historical version traceability analysis, and BOM object usage traceability analysis. Among them, the BOM view traceability analysis function traces the relationship structure of the selected object data in different views and displays the changes of the selected object in different views according to the conversion log recorded by the BOM data conversion module. The BOM object historical version viewing function displays the information of each revision version of the object based on the completed revision process records of the selected object. The BOM object usage traceability function displays the usage of the selected object in various views, and traces the selected object upwards from its original view, expanding layer by layer until the top-level node.

6. An electronic device, characterized in that, The invention includes a memory, a processor, and a computer program stored in the memory, characterized in that the processor executes the computer program to implement the method according to any one of claims 1-3.

7. A computer-readable storage medium storing computer instructions thereon, characterized in that, When executed by a processor, the computer instructions implement the method described in any one of claims 1-3.

8. A computer program product comprising computer instructions, characterized in that, When executed by a processor, the computer instructions implement the method described in any one of claims 1-3.

Images