Professional Documents
Culture Documents
Integration Application
1. Highlights.................................................................................................................................................. 3
2. Capabilities............................................................................................................................................... 5
3. Industry Standards................................................................................................................................. 5
4. Library of Pre-Built Integration Templates ..................................................................................... 6
5. Components ........................................................................................................................................... 7
6. Benefits .................................................................................................................................................. 8
6.1. The Ability to Traverse a Business’ Varying Security Models ................................... 8
6.2. Multiple-Enterprise and Supply-Chain Application Integration ................................ 8
6.3. Scalability ................................................................................................................ 8
6.4. Built-In Administration Tools .................................................................................. 9
6.5. Integrated Real-Time Event Engine .......................................................................... 9
6.6. Powerful Orchestration Environment ...................................................................... 9
6.7. Transform and Map Schemas for Subsequent Re-Use ............................................ 10
6.8. The ArchestrA Architecture’s Real-Time Application Integration Platform for
Services ................................................................................................................. 11
6.9. Synchronized Information Flow Coupled with Independent, Continuous Plant
Operations ............................................................................................................. 11
6.10. Managing Master Data for Manufacturing Operations ........................................... 12
6.11. The Ability to Locally Dispatch Production Work Orders ..................................... 12
6.12. Application Assembly, Not Programming .............................................................. 13
7. Centralized Topology.......................................................................................................................... 13
8. Mapping between Business and Manufacturing Systems ........................................................ 15
9. Ensuring Successful Implementation through Qualified System Integrators ..................... 16
10. Enterprise Partnerships....................................................................................................................... 18
11. Summary ................................................................................................................................................ 19
In essence, the Wonderware Enterprise Integration Application addresses the current need
for transactional business integration in manufacturing automation systems.
2. Capabilities
3. Industry Standards
Following Wonderware’s tradition for building solutions that employ robust, market-
leading technologies and industry standards, the Wonderware Enterprise Integration
Application leverages:
These pre-built integration templates are under constant development, so this list will
continue to grow.
5. Components
• Manufacturing module
This is the module that resides within the manufacturing automation system, either
apart from the system (when Wonderware’s Industrial Application Server is already
installed) or on top of the existing automation system. The manufacturing module
acts as a real-time event engine and integrates with existing plant system(s)
through the SuiteLink protocol, DDE, OPC or SQL as a result of ArchestrA
technology. This module will be independent of the business orchestration module.
It includes a production database in Microsoft SQL Server that uses an ISA-95
database schema for all the different sections of the standard, such as the
“planned” and “actual” data. This module also enables the downloading of
schedules that can be stored in the ERP until required for use in the manufacturing
system.
6. Benefits
6.3. Scalability
To address an enterprise’s future integration needs, the most logical approach is to
start with a pilot and then scale up. The Wonderware Enterprise Integration
Application provides the ability to scale the number of:
• Real-time plant connections;
• Workflows and transformations; and
• Application connections being integrated.
With its flexible architecture (see the Centralized Topology section for details), the
Wonderware Enterprise Integration Application provides the ability to evolve
architectures to meet physical distribution requirements and fit existing IT
structures. Examples include:
7. High-Availability Topology
As an example, SAP’s drive for implementing versions of its ERP central component (ECC)
SAP 4.7 and SAP NetWeaver™ technology, this type of application architecture will
become even more common, as NetWeaver provides a powerful transformation and
business-flow environment for transforming incoming and outgoing messages to the
appropriate calls within the R3 system. Especially in the manufacturing environment, where
companies are striving for standard messages between different sites, many companies
base their messages on ISA-95 (B2MML) standards.
Having determined a common message structure at the business end, the proposed
architecture places the Enterprise Integration Application at each site so that it can collect
incoming messages and transform them into the required calls needed in that particular
site. Usually, each manufacturing site will require its own transformation of standard
messages.
1. The ERP system sends a schedule, which is transformed by the ERP middleware
(let’s say SAP NetWeaver XI) to the ISA-95 (B2MML) production-schedule message,
and places it on the message bus.
2. The messaging system delivers the message to the correct manufacturing site.
3. The Enterprise Integration Application’s business orchestration module collects the
message at the manufacturing site and transforms it through workflows into the
ISA-95 production database. This enables a production schedule to be stored
locally. In case the SAP connection is lost, manufacturing will continue. This
architecture facilitates the customization of workflows and mappings, as well as a
manual entry system that enables schedules to be entered via a local terminal.
4. The Enterprise Integration Application’s manufacturing module pulls the scheduled
orders and makes the required calls to the batching/manufacturing execution
system (MES) to start executing the orders. It also monitors all production events,
collects the required data and transforms it to the ISA-95 production database,
which is ready for uploading to the business system.
5. In the event of a particular process-update event or business-system request, the
business orchestration module queries the ISA-95 production database, builds the
required ISA-95 production-performance message and places it on the message
bus.
6. The message system sends the message to the business system.
7. The business system’s middleware collects the message and transforms it to the
required calls in the business system.
This approach is found in companies that have only one manufacturing site or where the
business system is local to each site -- effectively, these companies run each site as its own
business. This topology is also appropriate for companies with business systems that
cannot be wrapped in standard middleware.
While each company must be analyzed on a case-by-case basis, companies with multiple
physically distributed manufacturing sites that plan to switch to a central business system
should seriously consider the standard-messaging approach and architecture proposed in
the first topology.
The focus of the business system is different from that of the manufacturing or MES
system – and they should be in order to optimize the performance of their required tasks
within the organization. Due to their different areas of specialization, different
terminologies and groupings are applied, requiring resolution for optimal integration and
interoperability. The ISA-95 standard (parts 1 and 2) provide a basis for these messages,
but they do not provide all the structure. The World Batch Forum developed the B2MML
message structure.
Having implemented a number of ISA-95 integrations, Wonderware has found that these
two standards (ISA-95 and B2MML) provide a solid basis for standard messaging --
providing approximately 80% of the structure. However, as would be expected, there
should be room for customization according to the different sites.
Leading end-users have often discussed applying these standards, particularly when
mapping ISA-95 process segments to a structure in the SAP recipe and MES plant model
(e.g., S-88 and ISA-95 part 3).
Fig. 6 is a good example of a mapping topology in which numerous sites are mapped.
(Note: this will vary by site and organization.) However, end-users with a common business
system will strive to pass common messages between the business and manufacturing
systems. Therefore, a standard set of mapping rules across the entire organization will be
required.
Wonderware has found from its business use cases that, typically, defining these mapping
rules is the most challenging part of any implementation, especially the first project. In
order to help with this problem, Wonderware offers consulting expertise to end-users as
well as system integrators (SIs).
Due to the complex nature of system integration, integrators who implement successful
business system-to-manufacturing systems must possess knowledge of both business and
manufacturing systems. To verify this level of knowledge, Wonderware provides a
qualification program for system integrators who would like to implement Wonderware
Enterprise Integration Applications. The objectives of this program are to:
This program complements the overall Wonderware System Integrator Program. (Learn
more about this program at www.wonderware.com/solution_providers/SI/). In order to
deploy the Wonderware Enterprise Integration Application, system integrators should be
ArchestrA Certified SIs, or at least have the required skills and expertise to achieve this
level of certification. Qualified SIs have been trained on how to successfully implement a
Wonderware Enterprise Integration Application. They understand how to capture the right
kind of information from the customer and determine the most appropriate
implementation approach. They also possess knowledge pertaining to business rules and
workflows, enabling them to link the business system to the manufacturing system. (The
best approach can vary widely from organization to organization.)
SAP
This is only the initial step in Wonderware’s drive to enhance business system alignment
with manufacturing operations, working with SAP on their adaptive manufacturing
initiative.
iWay Software
iWay's proven products, partners, and professional services are key to quickly and
efficiently transforming business processes by integrating existing data, applications and
environments with new systems and applications, including:
• Popular ERP, CRM and SCM application packages;
• Messaging technologies such as MQSeries;
• Application technologies like Java/J2EE/JCA and XML; and
• Internet technologies such as Web Services and .NET.
11. Summary
Using the Wonderware Enterprise Integration Application, customers can reap the rewards
of enterprise integration solutions that complement their existing systems, including
traditional MES functionality, and grow with their business. In addition, Wonderware
enterprise solutions can be painlessly combined with powerful Wonderware production
and performance management solutions.
Wonderware • 26561 Rancho Parkway South, Lake Forest, CA 92630 • Tel: (949) 727-3200 •
Fax: (949) 727-3270 • www.wonderware.com
© 2005, 2006 by Invensys Systems, Inc. All rights reserved. No part of this document may be
reproduced, stored in or introduced into a retrieval system, or transmitted in any form or by any
means (electronic, mechanical, photocopying, recording or otherwise), or for any purpose, without
the express written permission of Invensys Systems, Inc.