ascent
Thought leadership from Atos
white
paper
The
convergence
of IT and
Operational
Technology
Change Management is required to ensure that the implementation process runs smoothly
accompanied by consequent stakeholder management and open communication. In addition,
the implementation of a joint IT/OT concept has to be step-by-step to demonstrate short-term
benefits to all parties involved.
The reasons for IT services players to engage in IT/OT convergence are centered on business
impact, i.e. the commercial opportunities that IT/OT creates for industrial customers. The value
add can only be assured if challenges like pressures on production cost or a reduction in time
to market for newly developed products, for example, can be mastered. IT/OT also opens up
additional business to the mutual benefit of customers and vendors by defining and marketing
new offerings including IT/OT strategy and governance consulting - or a solution that manages
the transition of a product between R&D and operations.
The following defines a concept of what an integrated IT/OT landscape could look like.
05 13
Current Situation in IT and OT The Future Radar
Consideration of the current separated state of IT and OT
A look at a potential new area of the merger of IT and OT,
and an overview of the benefits IT/OT convergence could
specifically the application of IT concepts to the OT layer.
bring.
07 15
The IT/OT Challenge Conclusion
A summary of issues and ideas covered in the paper.
A detailed account of current challenges and trends with
regards to IT/OT convergence.
09
Implementation Strategies
Recommendations with regards to how companies can
best achieve IT/OT convergence.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
This paper defines OT as the set of devices and processes that act in real time on physical
operational systems, like electricity distribution networks, facilities or vehicle production plants.
Examples of OT elements include MES (Manufacturing Execution Systems), SCADA (Supervisory
Control and Data Acquisition), meters, valves, sensors and motors, etc.
Figure 1
For a comprehensive overview of IT and OT, Atos uses the ISA 95 model. ISA is a non-profit and
globally operating organization that sets globally accepted standards for automation.
ISA 95
ISA 951 is the international standard for the integration of enterprise (IT) and control (OT) systems.
It comprises models and terminology that can be used to determine the information to be
exchanged between commercial IT systems (e.g. finance and logistics) and systems for production,
maintenance and quality. The information is structured in unified modeling language (UML) models
which also serve as a base for the development of interfaces between IT and OT systems.
Figure 1 gives an overview of the spread of IT and OT components along the different layers.
1
Definitions deducted from A-95.com; ISA European Office 2010
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
2
IT and Operational Technology: Convergence, Alignment and Integration, Gartner 2011-02-15, G00210814
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
3
Based on material from : Smart Grid The IT-OT Convergence Help & How-To Special Issue, October 2011
4
Based on material from : The Management Implications of IT/OT Convergence, Gartner 2011-03-04, G00174016
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
Communication
Communication should be carried out to
inform, track and gather information about IT/
OT convergence projects. Communication
should target all parties involved and convince
them of the benefits of IT/OT integration. The
following communication instruments could be
employed:
``
(Virtual) IT/OT convergence hotline: problems
can be escalated and questions forwarded
to the implementation team by using an
intranet application
``
Executive talks: regular exchanges with
company management with regards to IT/OT
convergence activities and offering feedback
from employees (input for further activities)
``
Intranet page: provision of up-to-date
information about IT/OT convergence
projects;
``
Newsletter: information from everyone
touched, either in general or in particular by
(specific) IT/OT convergence projects
``
Information kit: general information package
(presentations and/or handouts) to outline
the benefits of and activities involved in IT/OT
convergence
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
As-build information is a strategic asset when it Planning and Management Detailed planning and fine tuning
comes to maintenance, repair and optimization Product Development Working Capital Management
(MRO), and therefore needs to be reliably
documented and available in both systems, Production Materials Management
which can be done via a platform provided by Service & Support Human Resources Management Seq. 04
PLM-MES integration. The accuracy of data will etc Products & Services
also be ensured by proper root-cause analysis Individual Seq. 05
Performance analysis
from MES, which includes real operational and Configuration
output data. Quality Management
Materials Management
Information Management Seq. 06
Considering this, the proper integration of Finance & Controlling
systems is vital, otherwise data would ‘manually’ Human Resource Management
Seq. 07
be passed from PLM to MES. The digital factory etc
has evolved from a theoretical idea to a real
business requirement.
Enterprise-Layer
Atos suggests a holistic approach to the
integration of PLM and MES, starting with Figure 2
clearly defining roles and interfaces. The
questions “Where does PLM end?” and “Where
does MES begin?” need to be answered. With
the landscape clearly structured, infrastructure
can be developed to harmonize information
between engineering and manufacturing.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
Figure 3
The IT industry should note that although in principle it is possible to apply IT virtues, such as
global sourcing, to the topic, a differentiation between standardized delivery models and tailored
approaches must be kept in a healthy mix.
Systematic knowledge in relation to an application needs to be separated from the business know-
how around its operation in order to safeguard the vital lifelines of a company. However, whatever
can be standardized can also be given over to global sourcing – as long as the service provider
tightly manages the global processes. Offshoring can therefore also play a role in the context of
application management for MES.
Application management for MES shouldn’t simply be a one-to-one transfer of the concepts of the
enterprise layer in order to succeed. Rather, it should be an overarching view of adjacent layers
along with an advanced understanding of the processes required. In addition, willingness for a wider
takeover of responsibility, where appropriate, should be in place.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
Application
Structure Application
Monitoring Interfaces
SLA Agreements
Knowledge
Connection
Management
Connection Software Production Sotware to
to Business Processes Process Production Processes
Figure 4
Since many MES applications are adapted to meet the needs of specific (production) processes,
a dedicated IT services provider is useful to ensure future compatibility with MES manufacturers’
developments. Often, a not insubstantial subsequent programming effort needs to be applied
which can be cost-effectively realized in offshore development centers. However, it is also important
to note that development teams need to be able to overlook underlying production-relevant
processes.
Finally, and as shown by the example of application management for MES, the success of
outsourcing also depends to no small extent on a stringent penetration at all levels of automation.
Segmentation of different IT-related components which keeps the balance between standardization
and adaptation leads to the possible optimal provision of services which use process penetration
and the necessary product know-how. The IT industry knows that currently (and perhaps also in the
near future) entire and cross-layer outsourcing is the absolute exception. Within individual modules,
consistent layer knowledge plays a crucial role - and determines results
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
© Atos, 2012, all rights reserved. The contents of this white paper is owned by Atos. You may not use or reproduce it in any type of media, unless you have been granted prior written consent thereto
by a competent person authorized to represent Atos for such purpose.
Atos, the Atos logo, Atos Consulting, Atos Worldline, Atos Sphere, Atos Cloud and Atos Worldgrid are registered trademarks of Atos SA. November 2012
atos.net © Atos, 2012. All rights reserved.