High availability and low operating costs with the iTAC.MES.Suite 8.51.00
The iTAC.MES.Suite portfolio has been expanded by features that enable continuous material replenishment as well as seamless machine integration based on OPC UA. More and more increasing amounts of data in the ME system can be easily managed with the new iTAC.BigData.Service and the required response times of the productive system can be guaranteed. Through a continuous replication of the productive database into a so-called "neartime" database, data-intensive evaluations (for example, the determination of all required information for a product recall) can be carried out without influencing the productive system with the aid of the neartime database.
The most important innovations at a glance:
iTAC.BigData.Service (Content Replication Service for Oracle)
The new iTAC.BigData.Service solution enables customers to improve the iTAC.MES.Suite infrastructure in high volume sites by minimizing the database content of the productive instance and by using the reporting functionality on the replication instance. After the rollout of the iTAC.BigData.Service solution the Workplace and Business Intelligence reports will no longer affect the shop floor.
iTAC.OPCUA.Service & iTAC.smart.OPCUA.Studio
New developments in the context of OPC UA: the iTAC.OPCUA.Service for coupling production systems to the iTAC.MES.Suite via the platform-independent OPC UA protocol. The integration of the service in an existing or new system prior to commissioning is supported by iTAC.smart.OPCUAStudio.
New CRP Service (Continuous Replenishment Program)
The new CRP Service ensures that there is the correct material, in the right quantity, in expected quality, in the right place at the right time! Customer benefits e.g. are the Reduction of stock level deviations due to the automatic posting of actual material usage, reduction of HR costs through automated messaging and voidance of production stoppages as well as the optimization of production resource usage through improved materials handling.
The CRP service offers the possibility to create and manage transport orders and the grouping of transport orders in conjunction with routing segments. Routing segments can in turn be grouped into routes. On this basis it is possible to realize a customer-specific logistics solution.
Additional Upload Status
Introduction of two new assembly states: "In process" and "invalid". The iTAC.MES.Suite now distinguishes between five different statuses for individualized serialized production processes. The new status "in progress" can be used in processes that confirm measurement or error data without completing the working step. With the status "invalid", working steps that were already carried out can be "reset" again; Already made bookings will be retained for later evaluations.
Failure tally card
New data object "failure tally card" for "clustering" of feedback (pass + error data) for serial numberless production.
Part images, part failures and grids
It is possible to use sample pictures of a defined failure type. Additionally a grid can be assigned to the images to identify the failure location (x/y). The images have to be uploaded to the MDA Module. The failure type definition incl. image and grid can be requested via an iMSAPI method. When uploading failure type information via iMSAPI, the grid details can be assigned.
Enhancement of trCheckSerialNumberState
The iMSAPI method has been enhanced to check also worksteps which are not feedback required.
Interface personnel deployment planning (eg for ATOSS SES)
The iTAC.MES.Suite can now be connected to any personnel deployment planning system. The necessary personnel data that is relevant to the planning process is transferred to the iTAC.MES.Suite to use it implicitly for the detailed planning in the APS service. The APS service takes into account the personnel deployment planning data in the detailed planning and calculates the production times according to the availability of the personnel groups to be deployed.
A class system has the task of describing any object by means of features and grouping similar objects according to freely definable criteria. This process is called classification. Objects can be real objects such as materials, customers, vendors, or logical objects, e.g. an order. In addition to the specific description of objects through features, a targeted search for objects with specific characteristics (attribute values) is aim of the classification.
Thus, e.g., it can be searched for specific materials during the compilation of a customer order by only displaying materials with certain characteristics. The class system for attributes works across the application, i.e. all modules of the iTAC.MES.Suite can access the functionality of the class system; this also includes the data exchange of attribute class information with a connected ERP system. The attributes, attribute classes and their characteristics (value conditions) can be freely defined, so that (almost) all company-specific requirements can be covered.
As an alternative to the iDOC format, data can now be exchanged with ERP systems (especially SAP) in the B2MML format (Business To Manufacturing Markup Language). The B2MML data are received and sent via a WebService (SOAP 1.1). This gives you a manufacturer-independent connection to B2MML-capable ERP systems.
"Active Data Guard" support
When using Active Data Guard, the iTAC.MES.Suite can be configured in such way, that reading operations are not performed on the primary database but on the standby database. This leads to a load reduction of the primary database.
The following iTAC application areas support this function:
DWH transfer process, which transfers the data from MES to QM
QM queries that are executed against the MES data
Evaluations in the TR module (BG list / BG history)
User defined tables
The iTAC.MES.Suite has become even more flexible; this release also supports so-called "dynamic master data". This is made possible because of the introduction of customer-specific data objects, which can be managed using IMSApi. Customer-specific database objects (tables, views) can be managed in a separate database schema (CUST).