Introduction to the Line Control module

The Nexeed Line Control module includes the following functions:

Part data

The function provides a view and search of parts data in the Nexeed Line Control User Interface (UI). The function offers the possibility to create part data and update part data through the production line interface (a connection is currently only possible via the Module Nexeed Direct Data Link).

The following part data can be displayed in the Line Control UI:

Additional Data

Includes the ability to view additional data for a product record in the Nexeed Line Control UI. The stations of a production line can read and create, update and delete additional data via a corresponding configuration in Module Nexeed Direct Data Link, which must be created by the Customer. Additional data can be stored as name-value pairs. Additional data can be scalar values of the data types integer, float, string or boolean. Additional data can be arrays, structs and struct arrays based on the simple data types integer, float, string and Boolean. The production line stations can read, save and overwrite Character Large Objects (CLOB) and Binary Large Objects (BLOB) for a parts data record in the Nexeed Line Control module by configuring the Nexeed Direct Data Link module accordingly, which must be created by the customer.

Editor for route lists

Route lists can be created, displayed, updated and deleted. Route lists can be imported and exported, the format is JSON and can be changed by the manufacturer at any time. The sequence of production steps for a product can be determined with the help of the route lists. The route lists are stored in the Nexeed Line Control database and are used to monitor the product data records.

Factory central storage for route lists

The route lists are stored and managed centrally. Once a route list has been created, it can only be explicitly deleted manually. The production line services (assembly line service) receive a copy of the centrally stored route lists with every change (create, change and delete) of the route list.

Interface for the production line (assembly line API)

The function includes the following interface functions to establish connectivity with a production line using the Module Nexeed Direct Data Link:

Specific information on the individual functions can be found in the Developer Manual. To implement connectivity, the Module Nexeed Direct Data Link is also required.

Supermarket

Allows product records to be moved from the production line to a supermarket database using the command “MovePartToStock”. To do this, the Customer must create a corresponding configuration in the Module Nexeed Direct Data Link. The product data records can be retrieved from the supermarket database and used further by the stations of downstream production lines using the "MovePartFromStock" command. To do this, a corresponding configura-tion must again be created in Module Nexeed Direct Data Link by the Customer for the production line. In addi-tion, the corresponding configuration must be uploaded in the Module Nexeed Line Control. Further information can be found in the Operations Manual.

Enforce blocking of products and product groups on the production line

To be able to use this function, the Nexeed Block Management module is also required. If a product block or a block of a group part is created in Nexeed Block Management, this block data is entered in all Line Control databases. With the help of this block information, Line Control can refuse to release a product when requested by the stations of a production line. If there is a block for a corresponding product identifier, the release for further production is not given.

Enforce material blocks on the production line

To be able to use this function, the Nexeed Block Management module is also required. If the material release check is to be carried out as part of the process release check, the material identifiers must also be transmitted to Line Control in the request from the production facility. This requires a corresponding configuration in the Nexeed Direct Data Link module, which must be created accordingly by the customer. If there is a block in the Line Control database for a corresponding material identifier, the information "Material blocked" is returned to the requesting production facility.

Enforce tool blocks on the production line

To be able to use this function, the Nexeed Block Management module is also required. If the tool release check is to be carried out as part of the process release check, the tool identifiers must also be transmitted to Line Control in the request from the production facility. This requires a corresponding configuration in the Nexeed Direct Data Link module, which must be created accordingly by the customer. If there is a block in the Line Control database for a corresponding tool identifier, the information "Tool blocked" is returned to the requesting production facility.

Enforce production facility blocks on the production line

In order to use this function, the Nexeed Block Management module is also required. If the production facility release check is to be carried out as part of the process release check, the production facility identifier (location identifier) must also be transmitted to Line Control in the request from the production facility. This requires a corresponding configuration in the Nexeed Direct Data Link module, which must be created accordingly by the customer. If there is a block in the Line Control database for a corresponding production facility identifier, the information "Production facility blocked" is returned to the requesting production facility.

Enforce process blocks on the production line

To be able to use this function, the Nexeed Block Management module is also required. If the process release check is to be carried out as part of the process release check, the process number must also be transmitted to Line Control in the request from the production facility. This requires a corresponding configuration in the Nexeed Direct Data Link module, which must be created accordingly by the customer. If there is a block in the Line Control database for a corresponding process number, the information "Process blocked" is returned to the requesting production facility.

Monitoring time dependencies between production processes

To be able to use this function, the Nexeed IAS Setup Specs module is also required to be able to create corresponding timer definitions. Once timer definitions for a product type have been created in Setup Specs and marked as released, these definitions are synchronised to Line Control and saved in the Line Control database. If the head-end station now creates a product data record for the corresponding product type, a timer is created for this product data record. The timer is started when it passes the correspondingly configured start process and it is ended when it passes the correspondingly configured end process. Triggers for starting and stopping a timer can be the request for production process release or the confirmation of the result of the production process. The timer is always checked when it is stopped. If the condition of the timer is not fulfilled, the timer can block the product data record, mark the product data record as scrap or write the product data record to a rework station (next NOK destination in the route list), depending on the configured action.

Monitoring the maximum number of repetitions of production processes

To be able to use this function, the Nexeed IAS Setup Specs module is also required to be able to create corresponding counter definitions. Once counter definitions for a product type have been created in Setup Specs and marked as released, these definitions are synchronised to Line Control and saved in the Line Control database. If the head-end station now creates a product data record for the corresponding product type, a counter is created for this product data record. The counter is always incremented when it passes the correspondingly configured production process or the configured production facility. The trigger for incrementing the counter can be the request for production process release or the confirmation of the result of the production process. The counter is always checked after it has been incremented. If the current counter value exceeds the configured threshold value, the counter can block the product data record, mark the product data record as scrap or write the product data record to a rework station (next NOK destination in the route list), depending on the configured action.

Configuration

Line Control supports so called scopes, with scopes the customer is able to operate assembly lines on different database schemas to maximize the ability of scaling of Line Control. Within the scopes the customer is also able to prive scope dependent configuration of Line Control.
Under Configuration the customer is able to:

Block Migration Tool

With the Block migration tool the customer is able to migrate MES blocks towards IAS.

All modules of the Nexeed Industrial Application System are based on permissions. Depending on the permissions, different functions are available in a module.
To enable functions, the user is assigned a role based on the desired permission. Permissions are managed in the Multitenant Access Control module.

The standard configuration of the module includes the following roles: