SIT ForProcess FunctionalOverview
SIT ForProcess FunctionalOverview
for Process
Functional Overview
www.siemens.com
June 2013
SIMATIC IT Industry Libraries Hybrid for Process issued by: Siemens. © Siemens AG 2013. All rights reserved.
Functional Overview | SIMATIC IT Industry Libraries Hybrid for Process | June 2013 2
Contents
1 Introduction ................................................................................ 4
5.1 What’s New in Industry Libraries Hybrid for Process v 3.3 ........ 17
1 Introduction
Under the pressure of new business-driving forces that have been emerging in recent decades, Manufacturing
Plants continue to play a major role. The globalization of both companies and production processes makes it
necessary to create new models. Manufacturing is not a process that can be completed by a single self-enclosed
entity, but extends beyond the bounds of the Plant, the Country and the Enterprise.
Therefore, MES cannot act simply as an interface between Business and Process layers, but requires a substan-
tial number of functions that are crucial to a Company’s success. Rather than remaining distinct from one an-
other, connected solely by a data exchange layer, these functions need to be coordinated, in adherence to the
Business and Production strategy.
ISA-95 documents point this out very clearly, describing the MES process in terms of both data and interaction
between functions (e.g. Order Dispatching, Resource Management).
The result is a new approach to MES, based on an architecture that allows describing Business Processes that
orchestrate functionalities provided by a set of specialized and affordable Components.
At the same time, this orchestration must also involve the Automation and Control level, thereby making both
MES and Control part of the same Collaborative Production Management system.
ISA-95 is acknowledged as the most authoritative standard for MES applications. Not only Market Analysts such
as AMR (www.amrresearch.com) and ARC (www.arcweb.com) confirm this, but also several major vendors
adopt this standard. In addition to Siemens, we can find, for example, SAP and Microsoft.
Siemens works in close conjunction with ISA and was the very first MES vendor to offer a comprehensive prod-
uct implementing the ISA-95 standard. This translates into standardized terminology, concepts and models for
integrating manufacturing operations functions with enterprise functions. Such standardization is achieved
with ISA-95, which defines the functional view of an enterprise, allowing a simple generic model of work activi-
ties to be applied to the main areas of manufacturing. As a member of the ISA-95 Committee, Siemens actively
contributes to the further development of this standard.
Complying with ISA-95 makes it possible to reap some important benefits: in particular, for what concerns de-
fining the hierarchical model of the MES solution, which simplifies developing solutions that are both standard
yet flexible, while still satisfying customer requirements in full.
On a daily basis, a variety of figures in charge of different activities face problems that involve manufactur-
ing systems. Implementing MES and deploying the right production model can provide a solution to many
of these issues. In broad outline, the problems encountered concern: S
Business
Production
IT
Is your system able to react quickly to new conditions and new market requirements?
In today’s world of manufacturing, the ability to adapt to new operational requirements (i.e. changes in
product specifications, quality procedures…) and environmental conditions (i.e. introduction of new
standards…) is paramount to success. If your system is ready to meet these challenges, the reward may be
a significant increase in your competitiveness, as well as impressive savings in terms of costs.
Do you need to increase visibility of your production process? Is your system able to provide Produc-
tion-related KPIs and advanced reporting?
To fully comprehend how your plant is performing, you need a system that can generate production re-
porting correlating process-control specific data with production-related data (i.e. order number, lots,
personnel, materials…) to facilitate troubleshooting and analyzing performance problems. MES can
heighten visibility in the production process, creating the right conditions to promote improvement and
increase your manufacturing system’s efficiency.
Do you need to raise your level of quality? Are you able to pinpoint contaminated lots or out-of-spec
finished-goods lots? Are you able to backtrack your production with accuracy?
If not, you might be unable to address specific issues regarding the quality of your product. You may also
be unable to respond to customer complaints appropriately or organize product recalls promptly. An effi-
cient MES system can provide complete genealogy, being able to track materials throughout the entire
production process. It also follows all material transformations with precision until the final product is
produced and delivered to the final customer.
Does your system react efficiently to production problems? Do you re-schedule your plant activities
properly?
What if something goes wrong on the shop floor? Efficient management of failures and downtimes is a
must. Often, several systems need to be involved in order to solve the problem (maintenance must be
informed, rescheduling is necessary, certain people must be notified as soon as possible…). Poor coordina-
tion leads to using resources in an ineffective manner, ultimately raising your production costs.
Is your ERP System working with the Manufacturing Operations System efficiently?
To optimize Supply Chain efficiency, the Business Logistic System must be informed in real-time as to what
is happening on the Shop Floor, especially in terms of Production Performance. This is especially useful in
terms of planning, as well as both material and warehouse management.
2.3 IT issues
Is your System properly integrated and synchronized? Are there so many links between applications
that communication is difficult? Are your IT maintenance costs too high?
A myriad of links between your Software Packages greatly increases the complexity of the manufacturing
system. In turn, costs for IT maintenance and program modification become staggering. This is mainly due
to the lack of coordination and flexibility of the majority of manufacturing applications. The modeling
approach can effectively simplify integration and actively coordinate the interaction and the flow of infor-
mation between different applications on site.
Is implementation too expensive? Do you frequently assess projects as falling in the "high-risk" cate-
gory?
Being able to employ reusable solutions creates the conditions for streamlining and speeding up project
implementations. Total ownership costs can be cut dramatically, thanks to efficient software reusability.
Does sharing your know-how represent an obstacle? Would you like to re-use your expertise and
your software effortlessly?
Efficient reusability of software is key to effective cost saving. Being able to "code" the expertise permits
the rapid transfer of know-how between users, which is usually not feasible with standard applications.
Without a modeling environment to help you define business procedures, focusing on the production pro-
cess rather than specific IT issues, the understanding of complex manufacturing applications is rather
difficult, making it virtually impossible to modify or reutilize code.
Is it difficult for you to maintain your team’s technological skills at top level? Are the costs to train
your staff in line with state-of-the-art technology excessive?
Applications are very often numerous and customized to satisfy specific needs. As a result, frequently, the
person with the most know-how is used to develop and maintain these applications. Such competence is
very difficult to maintain, as well as very expensive. By adopting SIMATIC IT, which covers all functionali-
ties in an integrated and homogenous environment, complex manufacturing systems can be implemented
with ease, making the tasks involved viable even for those users who possess normal skills.
In order to rationalize/ speed up processes, the product design / ideation data, need to be seamlessly trans-
ferred to the actual R&D environments, where formulation and formulation testing is typically being exe-
cuted
The R&D process is the critical link between Product ideation and manufacturing. It’s where ideas become
industrialized reality… true speed comes than when also these data, are seamlessly transferred to the
manufacturing floor for the actual execution of the production. Real-time capabilities and supply chain
efficiency, come from interoperability with the financial/ administration software, managing customer
orders and transferring these back to manufacturing or R&D environments
In parallel, also the production floor needs to be ideally equipped and organized, in order to be able to
produce in an efficient way, avoiding unforeseen problems with equipment capacity, energy use, etc.
Therefore, our digital factory / Plant lifecycle management part of the portfolio enables virtual testing and
commissioning of plants and their equipment, up front delivering the needed configurations for the auto-
mation layer, which in turn communicates with the manufacturing execution level.
All these interactions, managed by the Siemens Industrial Software portfolio, enable integration of the
product and production lifecycles – resulting in faster time-to market.
In order to increase the efficiency of the manufacturing plants in a way that is
• Fully integrated with the ERP
• Compatible with new products introduced from R&D
• Integrated with legacy Manual, DCS, PLC and Batch Managed Processes
• Compliant with legal Quality requirements
• Complete with the reporting and analysis tools required to support operations staff
Siemens has organized its Process Portfolio for Manufacturing Execution into a plug-and-play Factory-in-a-
box that can be rolled out and maintained with a very low TCO.
Fortunately each vertical market in the process sector share common characteristics that enable Siemens
to address them with a single solution and value proposition:
The Factory-in-a-Box is highly modular and scalable and can be deployed with a stepwise approach. Fur-
thermore, the Factory-in-a-box solution is structured in main sub-niches:
• Primary – called Primary-in-a-box – to support the primary production
• Secondary – called Secondary-in-a-box - – to support secondary processes (filling, packaging, palletiz-
ing)
• Integrated Quality to support the quality management
• Logistics to support the in-bound logistic
They can be used in tight combination for moving wall-to-wall inside a customer or only in specific area
depending on the customer requirements.
Each sub-niche can be enriched and completed with the Data Concentrator/Coordinator – called DCC/DCO -
to support a standardized and reliable message-based communication interface between the MES and the
Automation Layer with dedicated components for Primary and Secondary
• SIMATIC IT Production Suite allows manufacturers to model their own business to be much more cus-
tomer-oriented and ready to satisfy any on-the-fly requirements from the market.
• SIMATIC IT Production Suite has also been designed to facilitate application roll-out to several plants,
thus being extremely cost-effective in multi-site contexts.
• SIMATIC IT Production Suite effectively helps users to comply with existing regulations.
3.4 IT Benefits
The basic approach of SIMATIC IT makes it possible to model business rules in a graphical way so as to
represent the interactions and the expected flow of information among different software components
(including those that are not part of SIMATIC IT Production Suite). SIMATIC IT Libraries, classes and inher-
itance mechanisms create the conditions for an effortless rollout and reutilization of SIMATIC IT Production
Suite applications.
SIMATIC IT Production Suite permits users to focus on process issues, rather than IT issues.
In SIMATIC IT Production Suite, technological aspects are transparent to the user, who, as a result, requires
fewer skills than what is normally required to develop standard MES implementations.
Costs for maintenance and application modification are pared to the bone.
Siemens partners can create their own SIMATIC IT Libraries, coding their own expertise and making it easi-
ly reusable, thus dramatically reducing the average development time for MES projects.
• Tank Farm Management Library (ILH-TFM) manages the movements of materials between tanks in a
plant and allows external applications (e.g. other libraries) to search for material within the tanks or
for tanks where they can place material.
• Communication Management Library (ILH-CMM) allows messages to be exchanged between external
systems and Manufacturing Execution System (MES) applications. A typical example of an external
system which needs to send/receive messages to/from MES is the Control Layer. Examples of MES ap-
plications which send/receive messages using CMM are Industry Libraries such as the Production Order
Handling library (ILH-POH), and the Process Management library (ILH-PRO).
• Logging Management Library (FRM-LOG) provides useful instruments for logging information from the
rules running in the Production Modeler on to a database.
• Compliance Management Library (FRM-CPM) can be used in any kind of industry which may need to
enforce compliance to a given set of Regulatory Code Rules. Two are the features that the library pro-
vides:
o Electronic Signature (ES) intended as the authentication of a specific user. If associated to an
action, for the action to be terminated the user must perform an authentication by inserting
the proper username and password.
o Audit Trail (AT), intended as a log operation.
• Configuration Library (FRM-CNF) which provides a set of functionalities to configure the libraries in-
cluded in the collection such as configuring web keys, manager attributes, enabling and disabling user
exits and so on.
• Process Management Library (ILH-PRO) handles each sub-step of production, from the order initializa-
tion to the completion. The library focuses on the runtime phase of a production step, managing activ-
ities such as order dispatch, material declaration and consumption, download of parameters to Control
Level, and so on.
• Pallet Management Library (ILH-PAL) permits creating pallets and movable containers, that are typical-
ly reusable pallets (that can be empty or with one or more lots inside) and are used to move amounts
of material at the end of Secondary Production. Pallets are also called Logistic Unit – LU – stage.
• Labeling Management Library (ILH-LBL) provides the basic functionalities to create label data and to
configure label templates, tailored for Secondary Phase and in particular labeling of CU (Consumer
Units, e.g. a single bottle), SKU (Stock Keeping Units, e.g. a carton of 6 bottles), and LU (Logistic Units,
e.g. a pallet).
• Line Management Library (ILH-LMG) allows the creation and maintenance of virtual lines.
• Recipe Management Library (ILH-RCM) handles recipe management for production plants.
• Lot Information Library (FRM-LIN) allows the user to view Material Lots and their Genealogy Links.
• Material Management Library (FRM-MTL) handles the materials in a production system.
• Corrective Action Management Library (CIL-CAM) allows managing Corrective Actions (CA) which are
actions that can be performed during run time plant functioning to recover, for instance, to critical
situations.
• Electronic Work Instruction Library (CIL-EWI) allows the operator to manage Electronic Work Instruc-
tions which are forms containing a list of instructions that must be read to understand an operation
that has to be done and has to be filled by the operator to check important production variables.
• Tank Farm Management Library (ILH-TFM) manages the movements of materials between tanks in a
plant and allows external applications (e.g. other libraries) to search for material within the tanks or
for tanks where they can place material.
• Communication Management Library (ILH-CMM) allows messages to be exchanged between external
systems and Manufacturing Execution System (MES) applications. A typical example of an external
system which needs to send/receive messages to/from MES is the Control Layer. Examples of MES ap-
plications which send/receive messages using CMM are Industry Libraries such as the Production Order
Handling library (ILH-POH), and the Process Management library (ILH-PRO).
• Logging Management Library (FRM-LOG) provides useful instruments for logging information from the
rules running in the Production Modeler on to a database.
• Compliance Management Library (FRM-CPM) can be used in any kind of industry which may need to
enforce compliance to a given set of Regulatory Code Rules. Two are the features that the library pro-
vides:
o Electronic Signature (ES) intended as the authentication of a specific user. If associated to an
action, for the action to be terminated the user must perform an authentication by inserting
the proper username and password.
o Audit Trail (AT), intended as a log operation.
• Configuration Library (FRM-CNF) which provides a set of functionalities to configure the libraries in-
cluded in the collection such as configuring web keys, manager attributes, enabling and disabling user
exits and so on.
• Reporting Framework - Secondary which provides the collection data model for reporting.
4.4 Logistics
The Logistics is a collection of several Hybrid-Industry Libraries (ILH) and Basic-Framework Libraries (FRM).
These have been brought together and partially pre-configured in order to cover the most common func-
tional requirements of the Load In and Load Out phases and the Warehouse Management.
Here is a complete list of the included libraries:
• Warehouse Management Library (ILH-WHM), which handles the storage of materials within a physical
area named Warehouse.
• Load-In/Load-Out Library (ILH-LOA), which manages the Load-In / Load-Out operation, for example the
arrival or departure of a carrier, lot and pallet registration linked to the purchase order, and so on.
• Communication Management Library (ILH-CMM) allows messages to be exchanged between external
systems and Manufacturing Execution System (MES) applications. A typical example of an external
system which needs to send/receive messages to/from MES is the Control Layer.
• Logging Management Library (FRM-LOG) provides useful instruments for logging information from the
rules running in the Production Modeler on to a database.
The aim of the Data Concentrator (DCC) is to build a standardized and reliable message-based communica-
tion interface between the MES and the Automation Layer. The communication technology used herein is
compliant with the SIMATIC IT ILH-CMM Process Library.
DCC buffers events (from automation to MES) and orders (from MES to automation), assuring that no data
is lost.
The Data Coordinator (DCO) is a “Process-Runtime-Area” located in the Automation Layer, which is capable
of handling processes operating at the Unit level and it is fully compliant with the S88 standards.
The goal is to provide a general solution usable in different scenarios. For example:
• Connection to Siemens and non Siemens PLC hardware with old programming
• Replacement of ProCX without touching the Automation Layer
• Complete newly deployed automation systems based on S88
The solution is a generic shell that hides the Plant-specific process modeled on the Unit Level. The process
to be managed is plant specific, but the shell is always the same.
It wraps the basic functions and goes close together with the Data Concentrator and the MES Library func-
tions for the Production Orders handling.
DCO primary delivers predefined functionality for primary processes in combination with the SIMATIC IT
primary library collection.
DCO secondary delivers predefined functionality for primary processes in combination with the SIMATIC IT
secondary library collection.
In case MES is temporary disconnected from the plant, DCC/DCO allows to operate the production process
in “degradated mode”. A set of WinCC pages are available for directly operating the DCC/DCO from the
Scada screen.
• New functionalities
In detail:
• Orders page selection using equipment as filter: Add filters to selects Orders that contains opera-
tions running/scheduled on a set of equipments
• Order pages refresh only on events: A order page is refreshed only at the status change event of its
operations
• HLWF UI Customization: Allows the HLWF UI customization allowing to modify configuration files
• Management of CMM unprocessed messages: Add a page to list the CMM unprocessed messages to
allow their selection and eventually re-processing them manually
• Process global context mechanism support: Set Operator parameters at the beginning of the work-
ing time and show all pages filtered using these parameters
• Orders page selection using equipment as filter: Add filters to selects Orders that contains opera-
tions running/scheduled on a set of equipments
• Order pages refresh only on events: A order page is refreshed only at the status change event of its
operations
• Manage the commands Abort, Hold; Complete at order level: The capability has been extended
also to the Order Level (not only at operations level)
• Set a default routing for a Virtual Line: Allow to set a default routing among the possible alterna-
tives and use it at the order creation
• At the restart of an order or an operation change the equipment where to execute it. It allows
to modify and select a new equipment at the restart of an order or an operation
• Align the operations list when DCC-DCO create new operations for a running order. Add the
capability to receive messages from DCC-DCO
• Configuration and execution of a recipe containing manual operations ( EWI) mixed with au-
tomatic production Operations (DCC-DCO): Add the capability to configure and execute a recipe
where automated process operations need to be controlled and synchronized with manual opera-
tions. It creates a secondary order with automatic entries as a workflow and manage the download to
DCC-DCO
• Run command at order level integrated with DCC-DCO: Add the capability to send Run command at
order level
• Configuration of Virtual Lines taking into consideration the physical connections: Add the capa-
bility to support the virtual line configuration selecting an equipment and automatically provide the
routing depending on the physical lay-out.
• Alignment of workflow orders executed at DCC-DCO level in degraded mode: Add the capability
to receive message from DCC-DCO and update orders as soon as the communication is re-established.
After the re-alignment, the pending operation of the order must be handled manually
• Management of CMM unprocessed messages: Add a page to list the CMM unprocessed messages to
allow their selection and eventually re-processing them manually
• HLWF UI Customization: Allows the HLWF UI customization allowing to modify configuration files
relevant for the UI lay-out
• Manage set of parameters relevant for a set of equipment and depending from the recipe. Dur-
ing the recipe configuration, add the capability to define and manage properties relevant for the
set of selected equipment
• Association of virtual lines to Recipe: Per each recipe, the user can select one o more virtual lines to
associate to it , eventually according to the material specification. The association is propagated to
segments of the recipe linking the proper equipment.
• Process global context mechanism support: Set Operator parameters at the beginning of the work-
ing time and show all pages filtered using these parameters
• Form Web Editor from SIT Portal. Add the capability to define forms from a web page to improve the
form configuration (avoid to use dedicated tool)
• SPC: pre-configuration of the Pareto Chart. Add the capability to pre-configure Pareto Chart (pre-
configured list of characteristics) to reduce mis-configuration problems
• SPC: Show Control Limits values in the chart details’ panel. Show the control limits values per
each points in the chart details panel at each subgroup selection
• Simplify the IQ engineering editing. Effort to change/edit the quality tasks configuration has been
reduced in terms clicks and steps
• Search and Display executed Quality tasks. Add the capability to search for quality tasks based on
test results, time and context (Order, shift, products, etc) . For failed Quality task, the operator will be
able to drill down into the failed parameters
• Centralized Limit s Configuration. Add the possibility to have one single repository to define all
measures’ limits contextualized by products and/or equipment
• Allow “amend” operation on already executed manual data acquisition. Provide to authorized
personnel the capability to change/modify data wrongly entered.
• Set context data at Correcttive Action rule start. When a task violation occurs, provide context
ualized data to the corrective action rule
• Show SPC results in WFM. Add the capability to show SPC results (SPC task values) from WFM pages
• SPC save limits in run-time to simplify data consistency check. Add the capability to save the con-
trol limits together with the subgroup values.
• Allow to skip the Corrective Action execution. Add the capability to add and execute customer
specific logic to decide if a Corrective Action has to be executed or not (user Exit and relevant context
data)
• Associate to a workflow more than one event inside one IQ Plan. Add the capability to replicate
the same workflow in a PLAN for each event that can trigger it.
• Associate to a workflow more than one equipment on which the test has to be executed. Add the
capability to link a set of equipment (site, area, cell, unit) to a workflow in configuration phase and
actualize the triggering unit at run time.
• Show EWI results in WFM. Add the capability to show EWI results (EWI task values) from WFM pages
• Show ALT limits violations in WFM. Add the capability to show ALT results (ALT limits violations)
from WFM approval pages
• Process global context mechanism support. Set Operator parameters at the beginning of the work-
ing time and show all pages filtered using these parameters
• Hand Held move procedure. From an Hand held device, extend the capability to move material trac-
ing information on the system database
• Historical information about materials movements duration. Add capability to track the start time
and end time of movements
• Process global context mechanism support. Set Operator parameters at the beginning of the work-
ing time and show all pages filtered using these parameters
• Manage the commands at order level. Add the capability to set commands not only at operations
level but also at order level
• Add new operation in a order already in execution. Order workflow is up and running but it needs
to be modified on “the fly”. Allow the creation of a new operation associated to an already running
order at MES and then download to the DCC-DCO.
• At the restart of an order or an operation, change the equipment where to execute it. It allows
to modify and select a new equipment at the restart of an order or an operation on the MES and then
downloaded to DCC-DCO
• Extend the management of parameters associated to material and operations. All the parameters
associated to an entry/operation must be managed at Operation level, Material Level, Equipment level.
• Add string type parameters. The type “ string” has been added to the parameter types list
• Extend the equipment dictionary to map MES equipment parameters. Add the capability to trans-
late parameters into/from the low-level and MES format.
• Workflow orders execution interfacing DCC-DCO. Add the capability to receive orders and com-
mands from MES also when the order scheduling is managed by workflow.
DCC-DCO is slave of the MES workflow
• L-COM Integration. Add the capability to read/write from another PLC (Restricted to Siemens Family)
on the same LLA network
• HMI functionality in Degraded Mode (Copy Operation). Extend the DCC-DCO HMI to add the capa-
bility to copy locally an operation already available and to let the operator adjust the related order in
degraded mode
www.siemens.com Siemens AG
© Siemens AG 2013