System architecture and interfaces
Element descriptions
| Element | Description |
|---|---|
MaterialManagement module |
The module Material Management should be deployed in its own namespace 'mat'. Currently the module and its namespace only contains the Material Management service. |
MaterialManagement UI (User Interface) |
The UI of Material Management will be executed in the browser, and delivered via the module’s service. The UI will be rendered in the Portal within IFrames. |
MaterialManagement desktop clients |
The MaterialInfoPanel and the MatClimateControl should be deployed on windows servers via the MES Installer. Updating previous versions of these clients is possible. |
IPTE Station |
The incoming goods station used by AE division of Bosch, which is usually the input for Material Management in AE plants. This station sends the information about the material(s) to Direct Data Link. |
Direct Data Link |
Provides interfaces to consumers of Material Management, which want to communicate via OpCon XML. These messages are usually sent by the stations of the factories. |
ERP Connectivity |
Provides abstraction layer between the ERP system(usually SAP) and Material Management. Used for the INTEGMA usecase. |
RabbitMQ |
Internally deployed messaging broker, which is used internally by the Material Management service instances for syncronization. |
Portal |
Hosts the UI of all modules, including Material Management |
Gateway |
An NGINX gateway, which serves as an ingress, which is also configured by the modules to redirect the respective calls to their pods |
Serves as the authentication/authorization provider for the Nexeed system |
|
Order Management |
Consumes endpoints of Material Management |
Packaging Control |
Consumes endpoints of Material Management |
Line Control |
Consumes endpoints of Material Management |
Database |
Material Management currently only supports Oracle databases. Either cluster-internal or external database can be used. |
Network connection overview
| Source | Destination | Protocol |
|---|---|---|
Material Management UI |
Material Management Service(via Gateway) |
https |
Material Management Desktop clients |
MACMA(via Gateway) |
https |
Material Management Desktop clients |
Material Management Service(via Gateway) |
https |
Material Management MatClimateControl Desktop client |
Order Management(via Gateway) |
https |
IPTE Station |
Direct Data Link |
OpCon Xml |
ERP Connectivity |
Material Management Service(via Gateway) |
https |
Material Management Service |
RabbitMQ |
AMQP 0.9.1 |
Material Management Service |
Oracle Database |
ODP.NET |
Material Management Service |
MACMA(via Gateway) |
https |
Material Management Service |
Portal(via Gateway) |
https |
Portal |
Material Management Service(via Gateway) |
https |
Order Management |
Material Management Service(via Gateway) |
https |
Material Management Service |
Order Management(via Gateway) |
https |
Packaging Control |
Material Management Service(via Gateway) |
https |
Line Control |
Material Management Service(via Gateway) |
https |
Dependencies
MACMA (Multitenant Access Control)
-
Used for authorization and authentication
-
MACMA uses the concept of roles and access control lists to allow applications authorize users / clients to access protected resources
Portal
-
Nexeed Web Portal is the integration layer of IAS in order for other modules to integrate their views (pages) in the UI (User Interface)
-
Material Management is hosting its UI in an iframe inside the portal’s frame
MES (Manufacturing Execution System) module dependencies
Material Management needs to support usecases which other products are providing in MES context to fulfill that MES usecases are also working as before. As unfortunately there are products which are not yet providing the MES usecases in IAS context.
DDL (Direct Data Link)
-
DDL is an application, which connects to various modules, including Material Management
-
It gets the messages sent by the machines and translates them to an interpretable format
-
These messages are in XML (Extensible Markup Language) format
-
It is the "interface" between the machines themselves and Material Management
Infrastructure dependencies
MES INTEGMA flow - IAS INTEGMA flow
Since version 3.11.x INTEGMA flow changes to use REST API calls instead of RabbitMQ queues. This solution simplifies the overall architecture and reduces the complexity of message handling. ERP Connectivity is now achieved through direct API calls triggered by ERP Connectivity.
Endpoints
The following endpoints are created by the changes in the INTEGMA flow. Returning all a structured common Integma Response object.
-
/warehouse/integma/easn -
/warehouse/integma/goodsreceiving -
/warehouse/integma/pairing -
/warehouse/integma/repack -
/warehouse/ifns/materials
Authentication and authorization
Endpoints requires authentication and authorization via MACMA.
MaterialManagement_Warehouse_Admin is the role required to access these endpoints which ensures that only authorized users can interact with the warehouse management functionalities.
MaterialManagement_Warehouse_Admin has execute permissions for the following resources:
-
MaterialManagement-Warehouse-Easn
-
MaterialManagement-Warehouse-GoodsReceiving
-
MaterialManagement-Warehouse-Pairing
-
MaterialManagement-Warehouse-Repack
-
MaterialManagement-IFNS-Materials
Validations
Endpoints must validate incoming requests to ensure they meet the required criteria before processing. In case of failure in validation, appropriate error responses must be returned. Request is rejected.
This includes:
-
Checking if property is required
-
Validating MIN and MAX values for numeric fields
-
Ensuring that string fields meet length requirements
-
Validate maximum size of list fields
Further detailed validation and execution logic check User Manual.