Combined with examples, interpret the HUAWEI CLOUD digital factory information model configurator

Abstract: Combined with the related business data objects involved in an actual "production execution management" scenario, the system introduces the usage method of the "information model" configurator of Huawei Cloud Digital Factory Platform to realize the data modeling of related business objects.

This article is shared from the HUAWEI CLOUD community " Digital Factory in-depth and Simple Series (2): Introduction to Using the Information Model Configurator ", author: Yunqi MAE.

The HUAWEI CLOUD digital factory platform adopts the industry's advanced metadata-driven architecture, deconstructs application functions into four core building elements: data information, logical process, data analysis, and front-end view, and provides corresponding metadata configurators and operating engines: users According to actual business needs, use the metadata configurator provided by the platform to quickly and graphically complete the metadata modeling of the corresponding business objects, and then the metadata model will dynamically generate running instances of the corresponding business application functions through the metadata model running engine of the platform .

The HUAWEI CLOUD digital factory platform abstracts and encapsulates business objects involved in manufacturing scenarios into nine types of business models, and a business model (Business Model) is instantiated into an application function component:

Among them, "information model" is used for data modeling of business objects involved in business functions, and it is the data basis for developing any type of business functions. The HUAWEI CLOUD digital factory platform provides a graphical information model configurator, which enables business personnel who do not understand technology to define data models on their own, realizing true business-driven digital application development. The information model can automatically generate data views of various common types (list/card/calendar/Gantt chart, etc.), and the generated views can be used on PC web and H5 mobile terminals.

After the user configures the information model, click the "Release" button to realize one-click release without deployment.

This issue introduces in detail how to use the "Information Model" configurator of the HUAWEI CLOUD Digital Factory Platform based on a simplified "production execution management" scenario case.

(1) Case Scenario Description

In the "production execution management" case scenario, application functions need to be built to meet the following two requirements:

  • Carry out information data modeling for business objects related to production execution to manage related business data. Related business objects mainly include the following activities: production orders, process task orders, production material demand orders, etc.; and configure related transaction documents Business coding rules to realize automatic generation of tracking numbers;
  • Match the actual production execution business activity process to realize the automatic flow of information data between related business objects, such as the production order automatically generates the corresponding process order according to the product's production process route, and automatically generates the corresponding according to the product's manufacturing BOM list Material requirements information, etc.

This issue introduces how to implement the first requirement of this case scenario on the HUAWEI CLOUD Digital Factory Platform.

(2) Formal construction steps

1. Relevant master data preparation:

In the production execution management scenario, the master data of manufacturing resources (products, materials and bills of materials, etc.) and the master data of manufacturing processes (standard procedures, process routes, etc.) need to be maintained in advance.

Under the "Data Workbench>Manufacturing Resources and Process" function path of the HUAWEI CLOUD Digital Factory Platform, users can complete the required master data maintenance by operating the following functions:

  • Material master data:
  • Product and bill of materials (manufacturing BOM) master data:
  • Standard process master data:
  • Routing master data:

2. Data modeling of business objects related to production execution:

In this production execution management scenario case, the business objects involved mainly include the following activities: production order, process task order, and material demand order. Users use business activity transaction functions on the "Collaborative Workbench" of the HUAWEI CLOUD Digital Factory Platform. The "Collaborative Workbench" organizes the layout according to the "business domain" and "business scenario" to which the business activity transaction belongs when modeling The functional usage path of a business activity transaction.

In the "Modeling Workbench" of the HUAWEI CLOUD Digital Factory Platform, the user uses the "Transaction" model builder to first complete the data modeling of the relevant business activity transaction objects:

  • Production Order Modeling

In the "Transaction" model builder, select the "Production" domain tab, then create or use the existing business scenario "Production Management", create a new transaction model "Production Order" in the business scenario, and click the edit icon on the right side of the information model , open the information model configurator, and configure the information fields required by "production order":

Here is an expanded introduction to how to use the "Information Configurator":

(1) Field component library description:

(2) Description of field attribute configuration:

(3) Example of field configuration of associated model type:

Use the "Production Order" model to configure the "Product" and "Processing Route" fields as an example to illustrate the configuration method of the field of the associated model type:

  • In the "Product" field, we need to select the required processing product from the product master data when creating a production order:

The first step is to select the target model: In the "Field Attribute Configuration" window on the right, click the "Configure" button of the associated model, and the configuration associated model window will pop up for the following configuration:

a. Select the target model from the model type to which the associated model belongs, for example, select the target model "product" from the "product" class model;

b. Select the main model (such as product information) or sub-model (such as BOM under the product) that needs to be associated from the target model.

The second step is to configure the view content of the "Data Selection" window of the associated model and the linkage processing with other fields after the associated model field is entered when entering the value of the "Associated Model" field:

a. Check the form fields that need to be displayed to the user in the data selection window when the product master data needs to be selected;

b. After selecting a product master data, the "data title" field value of the product master data will be brought to the front-end user interface by default. Here, it is supported to check other field contents that need to be brought to the front-end user interface. For example, the "specification" of the product needs to be ", "Model" and other fields are brought to the front-end interface;

c. After selecting a product master data, you need to bring the value of the product's "Unit of Measure" field to the "Production Unit" field of "Production Order" by default, and add a mapping relationship of "Assignment" under "Target Field Mapping". Select the Unit of Measure field of the Production Order and drag the Unit of Measure field of the product on the left.

  • In the "Processing route" field, we need to filter the optional "Processing route" master data according to a certain "Product" master data selected by the user when creating a production order, and limit the data status of the routing to "Valid":

Add a "Filter" class mapping relationship under "Target Field Mapping" in the "Configure Association Model" window, drag the "Product" field of the left routing to the "Filter Field" input box, and then select the filter condition operator "Equal to ", and select the "Product" field value of "Production Order" as the conditional value.

Add an "Advanced Filter Condition" class mapping relationship under "Target Field Mapping" in the "Configure Association Model" window, drag the "Status" field of the left routing to the "Filter Field" input box, and then select the filter condition operator "equal to", manually enter "enabled" as the condition value.

(4) Encoding rules for configuration data identification:

"Production order number" field value, usually when creating a production order, it is necessary to automatically generate coding flow according to the user's business requirements. Use the "Identification" model builder of the "Modeling Workbench" to configure the "Production Order Number" encoding serial number:

Create a new "Data Identification" model, select "Production Order" for "Data Model", and select "Production Order Number" for "Data Field":

According to the actual business needs, configure the encoding rules of the identification:

The structure of the identification code supports the following combinations of segment value types: fixed characters, system dates, system variables, model fields, serial numbers, random values, and separators.

  • Process order modeling

In the "Transaction" model builder, select the "Production" domain tab, create or use the existing business scenario "Production Management", create a new transaction model "Procedure Task Order" in the business scenario, and check "Process Process Transaction", Then associate the corresponding process operation model, indicating that the "process task order" is an activity transaction at the process operation level, and automatically preset the "process operation" associated model field after the model is created:

Click the edit icon on the right side of the "Process Order" information model to open the information model configurator, and configure the information fields required by the "Process Order":

The configuration method of the information model fields of the "Process Order" is similar to that of the "Production Order", and will not be described here.

  • Material Requisition Modeling

In the "Transaction" model builder, select the "Warehouse" field tab, and then create or use the existing business scenario "Inventory Management", and create a new transaction model "Material Requisition" in the business scenario:

(1) Configure the information model fields of "Material Requirements", the configuration method is similar to that of "Production Order", and will not be explained here.

(2) Under the "Details" tab of the "Logical Model" of the "Material Requirement", create a "Requirement Details" sub-model to carry the material requirement details line:

Among them, when "Manual Editing" is checked, it supports manual creation and editing of transaction detail data on the front-end user interface. When it is not checked, only data is allowed to be viewed on the front-end user interface (data is generated through background logic).

Configure the fields of the "Requirement Details" sub-model, the configuration method is similar to that of "Production Order", and will not be described here.

(3) "Associated Computing" configuration example:

Assuming that it is necessary to automatically summarize and count the material "Required Quantity" of the "Requirement Details" row on the "Material Requirement Document", add a field "Required Quantity Sum" in the "Material Requirement Document" information model, and then configure its default value of " "associated calculation" logic:

In the window for configuring the "Association Calculation Formula", click the "Requirement Quantity" of the sub-model "Requirement Details", and then select the "Statistics method": summary, count or average:

In the configuration "Relational Calculation Formula" window, the sub-model data that supports configuration statistics needs to meet certain conditions:

(3) Operation effect verification

1. Production order

After the "Production Order" model is released, the end business user can see and use the corresponding function instance by selecting the "Production Management" application card in the "Collaboration Workbench":

  • list view
  • Quickly create views
  • edit view

In the "Quick Create View" and "Edit View", you can verify the operation effect of the following configurations related to the "Associated Model" field:

  • The data list fields displayed in the "Data Selection View" window of associated model type fields such as "Product" and "Processing Route";
  • In the "Product" field, after the user selects a certain product master data, the values ​​of the "Model" and "Specification" fields of the product master data are automatically brought to the front page for display;
  • Optional data filtering for the "Route" field: filter optional routing master data in the "Data Selection View" window for the "Route" field based on the value of the "Product" field;
  • After the "Product" field is selected, the field value of the product master data is automatically assigned to other fields, for example, the measurement unit of the product master data is automatically assigned to the "Production Unit" field of the "Production Order".

2. Process task list

After the "Process Task Order" model is released, the end user can see and use the corresponding function instance by selecting the "Production Management" application card in the "Collaboration Workbench".

The operating effects of the "List View", "Quick Create View" and "Edit View" of the "Process Order" are similar to those of the "Production Order" and will not be explained here.

3. Material requirements list

After the "Material Requisition" model is published, the end user can see and use the corresponding function instance by selecting the "Inventory Management" application card in the "Collaborative Workbench".

The operation effect of "List View" and "Quick Create View" of "Material Requisition" is similar to that of "Production Order", so no further description is given here.

The following is the running effect of the "Edit View" of the "Material Requisition Document", which can verify the associated calculation results of the "Required Quantity Summary" field of the Material Requisition Document, and view and add the data of the "Requirement Detail Line" of the sub-model:

The above is a combination of relevant business data objects involved in an actual "production execution management" scenario. It systematically introduces how to use the information model configurator of the "transaction" model of the Huawei Cloud Digital Factory Platform to complete the modeling and use of relevant business data. In the next issue, we will systematically introduce how to use the "logic" model of the HUAWEI CLOUD digital factory platform, so that different business objects can automatically exchange data based on certain trigger conditions or actively send message notifications (such as "production orders" and "process task orders") , "Material Requisition" data flow automatically).

Add HUAWEI CLOUD IoT assistant WeChat hwc-iot, reply "Digital Factory" and apply to experience HUAWEI CLOUD Digital Factory

 

Click to follow and learn about Huawei Cloud's fresh technologies for the first time~

{{o.name}}
{{m.name}}

Guess you like

Origin my.oschina.net/u/4526289/blog/8817814