XML Working Group Meeting WBF European Conference 14 November 2006

gabonesedestructionΛογισμικό & κατασκευή λογ/κού

17 Φεβ 2014 (πριν από 3 χρόνια και 7 μήνες)

108 εμφανίσεις

Copyright
© 2006 WBF. All rights reserved.

XML Working Group Meeting

WBF European Conference

14 November 2006

Copyright
© 2006 WBF. All rights reserved.

Agenda


Introductions


Working Group Update


BatchML


B2MML


V04 proposal


OAGIS & MIG WG


UN/CEFACT

Copyright
© 2006 WBF. All rights reserved.

Working Group Update


Logos


New WBF management company


Web enhancements


Yahoo Groups


WBF.org site


B2MML.org & BatchML.org sites


Sharepoint site


Role of XML WG with respect to ISA’s SP88 and
SP95 committees


Is a more formal structure, procedures, needed?

Copyright
© 2006 WBF. All rights reserved.

BatchML


V02


Current release


New/Enhanced schemas for


ISA
-
88 Part 3


General & Site Recipes


Not started


ISA
-
88 Part 4


Batch Production Record


Started, on hold pending B2MML v04


Questions


ISA
-
95/B2MML style transactions?


Support for Core Components?


Defer to B2MML discussion


ISA
-
88 Part 1 Update


Impact on BatchML?


Make BatchML a reference implementation in as ISA
-
88 Part 1
annex?

Copyright
© 2006 WBF. All rights reserved.

B2MML


V0301 released June 2006


Minor bug fix from v03 released August 2005


ISA
-
95 Status


B2M Query Language


Collaboration with other interoperability groups


UN/CEFact Core Components


V04 schemas


ISA
-
95 Part 5 Transactions


B2MML Roadmap


Copyright
© 2006 WBF. All rights reserved.

ISA
-
95

U.S. Standard

International
Standard

Title

ANSI/ISA
-
95.00.01
-
2000

IEC/ISO

62264
-
1:2003

Enterprise
-

Control System Integration
-

Part 1:
Models and Terminology

ANSI/ISA
-
95.00.02
-
2001

IEC/ISO

62264
-
2:2004

Enterprise
-

Control System Integration
-

Part 2:
Object Model Attributes

ANSI.ISA
-

95.00.03


IEC/ISO

62264
-
3:2005

Enterprise
-

Control System Integration
-

Part 3:

Activity Models of Manufacturing Operations
Management

ISA draft
95.00.04

Draft

Enterprise
-

Control System Integration
-

Part 4:

Object Models and Attributes of Manufacturing
Operations Management

ISA 95.00.05

IEC/ISOJWG 15
Work Item

Enterprise
-

Control System Integration
-

Part 5:

Business to Manufacturing Transactions

Copyright
© 2006 WBF. All rights reserved.

B2M Query Language


Developed at the University of Nancy by Herve
Panetto


Data base design (SQL) that implements B2MML
objects


Can be used to provide persistence to B2MML data.




Herve Panetto is willing to make B2MQL publicly
available


License terms pending

Copyright
© 2006 WBF. All rights reserved.

Collaboration with Other

Interoperability Groups


OpenO&M


Open Operations & Maintenance


Open Applications Group (OAG)


OAGIS


ARC


Customer Interoperability End User Council


MIG WG


Manufacturing Interoperability Guideline Working Group


Copyright
© 2006 WBF. All rights reserved.

Open Operations & Maintenance


Collaboration of standards organizations to develop a
comprehensive, open information architecture for
Operations & Maintenance (O&M) information that enable:


Condition Based Operations (CBO)


Collaborative Asset Lifecycle Management (CALM)


OpenO&M™ leverages a combination of
existing

standards that will continuously improve over time


The standards are vendor, platform and application neutral
and they are applicable to manufacturing, fleet and
facilities O&M applications integration


OpenO&M™ for Manufacturing

Copyright
© 2006 WBF. All rights reserved.

Life
-
cycle

MGT

NIBS

OpenO&M


Facilities JWG

NIBS FMOC

OpenO&M


Military JWG

OpenO&M™ Initiative


Participating Standards Organizational Model

OpenO&M


MFG JWG

ISA 95 ISA 99


WBF


F O U N D A T I O N

OpenO&M Initiative Joint
Working Groups

Copyright
© 2006 WBF. All rights reserved.

OpenO&M Relationships

MIMOSA

B2MML

ISA
-
95

ISA
-
88

BatchML

OPC

Make2Pack

ISA

Standards

ISA
-
88


Batch Control System
Standard

ISA
-
95



Enterprise/Control System
Interface Standard, Parts 3 & 4
define MES Functions

WBF

BatchML



XML Schemas based on
ISA
-
88

B2MML



XML Schemas based on
ISA
-
95

OPC



DCOM and XML interfaces.
New Web Services Unified
Architecture (UA) under development

MIMOSA



Maintenance and Asset Mgt
Interfaces

Make2Pack



Developer of PackML to
standardize packaging machinery
interfaces

OpenO&M



Joint work by MIMOSA,
OPC & ISA
-
95 to integrate
maintenance and operations data

Potential Relationship

OpenO&M Relationship

Relationship

OpenO&M

OAG

Copyright
© 2006 WBF. All rights reserved.

OpenO&M Manufacturing Whitepapers


Condition Based Manufacturing


Collaborative Operations & Maintenance

Using MIMOSA’s OSA
-
EAI and ISA
-
95/B2MML

Copyright
© 2006 WBF. All rights reserved.

ERP System

Supply Chain Mgmt.

Supply Chain Mgmt.

Production Forecasting & Scheduling / MES System

Asset Capability Forecasting &

Asset Optimization DSS

Enterprise
Asset
Management
(EAM)
System

Asset Registry

Maintenance

Work & Parts Mgmt.

Asset Health
DSS

Condition
Based
Maintenance
Advisories

Control &
SCADA
Systems and
Data
Historians

Condition
Based
Operational
Advisories

Asset Measurements & Inspections

O&M Event
Monitoring

I&C Device
Monitoring

Portable
Device
Monitoring

Online
Surveillance
Monitors

Online
Protection
Monitors

Online
Transient
Monitor

Sample
Monitoring


F O U N D A T I O N


F O U N D A T I O N

Condition Based Operation (CBO)

Copyright
© 2006 WBF. All rights reserved.

OSA
-
EAI Assets map to

ISA
-
95/B2MML Equipment

Dependency 1

ISA
-
95/B2MML

Equipment Hierarchy

OSA
-
EAI

Segment Hierarchy

OSA
-
EAI

Assets

OSA
-
EAI

Segments

OSA
-
EAI

Networks

Production Unit
Turbine A

Production Unit
Turbine B

Dependency 2

Production Unit
Reliability
Network

XYZ Company

ISA
-
95/B2MML

Enterprise

Stony Point

ISA
-
95/B2MML

Site

Power Plant

ISA
-
95/B2MML

Area

Turbines

ISA
-
95/B2MML

Production Unit

Generate
Power

ISA
-
95/B2MML

Process Segments

Stony Point

OSA
-
EAI

Site

XYZ Company

OSA
-
EAI

Enterprise

Turbine A

ISA
-
95/B2MML

Unit

OSA
-
EAI

Equipment & Site

OSA
-
EAI Enterprise & Site map to
ISA
-
95/B2MML Equipment

OSA
-
EAI
Networks

map to

ISA
-
95/B2MML

Process Segment

ISA
-
95/B2MML


MIMOSA EAI
-
OSA Mapping

Copyright
© 2006 WBF. All rights reserved.

OAGIS

Manufacturing

Operations & Maintenance

Enterprise

Inter
-
Enterprise

Machine

OPC DA, HDA, A&E, OMAC

Discrete

Process

OAGIS

MIMOSA

MIMOSA

OPC UA

ISA
-
95

B2MML

OAGIS


F O U N D A T I O N

OpenO&M
TM
and the MIMOSA logo are marks of MIMOSA.

All other marks are the property of their respective owners.

OpenO&M


Manufacturing


Domain Mapping

Copyright
© 2006 WBF. All rights reserved.

What is OAGIS
®

?


OAGIS
®

is a business process
-
based data
exchange model for enterprise functions.


The OAGIS
®

standard is built as a horizontal
business language, enabling it to be used in
many industries worldwide.

Copyright
© 2006 WBF. All rights reserved.

OAGi Genesis


Founded in November, 1994


Originally by ERP Vendors


Focused on how they can integrate together
better


Identified common content as biggest
missing piece

Copyright
© 2006 WBF. All rights reserved.

By the Membership and

for the Membership


OAGi is owned by its members


Open Membership


Anyone can join


Must be a member to join or form a
Workgroup


OAGIS work is supported by membership
fees

Copyright
© 2006 WBF. All rights reserved.

OAGi Work Groups


Core Components


CRM XML


Logistics XML


Discrete Manufacturing


Modeling


Architecture

Copyright
© 2006 WBF. All rights reserved.

OAGi Activities


Technical Activities


Standards Development


Standards Governance


Interoperability Activities


NIST Test Bed


Semantic Integration


Out Reach Activities


Working with Industry


Services and Training


OAGIS Help to Users



Copyright
© 2006 WBF. All rights reserved.

OAG
-

The Fully Integrated Enterprise

Outside the
Enterprise

Inside the
Enterprise

Down the
Enterprise

E2E = B2B + A2A + A2E
TM

Everywhere to Everywhere Integration

Copyright
© 2006 WBF. All rights reserved.

Value Chain Collaboration

Applications

Enterprise

Management
Applications

Enterprise

Execution

Applications

OAGIS
®

9.0 Scope


eCommerce


e
-
Catalog


Price Lists


RFQ and Quote


Order Management


Purchasing


Invoice


Payments


Manufacturing


MES


Shop Floor


Plant Data Collection


Engineering


Warehouse Management


Enterprise Asset Mgmt.


Logistics


Orders


Shipments


Routings


CRM


Opportunities


Sales Leads


Customer


Sales Force Automation


ERP


Financials


Human Resources


Manufacturing


Credit Management


Sarbanes/Oxley & Control

Copyright
© 2006 WBF. All rights reserved.

ARC Interoperability End User Council

Copyright
© 2006 WBF. All rights reserved.

MIG WG


Manufacturing Interoperability Guideline Working
Group (MIG WG)



Copyright
© 2006 WBF. All rights reserved.

MIG WG Strategy

Guiding Principles for convergence of OAGi, ISA
-
95 and B2MML Phase 1 activities:


1)


Manufacturing IOP Standards for Level 3 and 4

manufacturing and business systems should be
formulated into ISA
-
95 documentation for both process, discrete and mix mode manufacturing models,
beginning with ISA
-
95 Part 4 Object Models. Part 1 and 2 will be updated later.

2)


ISA
-
95 standards documentation should facilitate development of software

services under

a SOA for
semantic interoperability to reduce cost and complexity of IT systems integration.

3)


A consistent and expanded set of business object models, terminology and transactions should be
developed within ISA
-
95 standards including generally accepted practices for discrete and process
industries.


These should include the optimal set of

proven and adopted

best practices using ISA
-
95
and OAGi

manufacturing standards and other related work.

4) A single

joint UML Object Model should be developed from OAGi and B2MML.

5)


A single unified set of BOD transactions should be developed without overlap.


6) The standards and messages should comply with established methodologies and practices adopted by
UN/CEFACT including Naming and

Design Rules (NDR) and proposed CCTS specifications.



7)

Acceleration of standards activities to reach a joint data schema and XML messages

is

to be supported
under the ISA
-
95 and OAGi organizational charters with available funding from the ISA and OAGi
standards bodies supplemented when necessary from customer

industry sources.



8)


The anticipated level of effort of this convergence activity should be considered and
enumerated

independent of existing resource

constraints.

First order recommendations

should be
developed

considering the

"right technical solution" to deliver the greatest

benefit to the manufacturing
software industry, customers and general public welfare.

Copyright
© 2006 WBF. All rights reserved.

Discrete Manufacturing

Integrated System



Inspection Plans



Defect Tracking



Project Planning



Production Planning



Scheduling



Inventory



Process Planning



Instruction Authoring

PDM/DM

MES

QA

CAPP

Supplier

Mgt

ERP

HR

Shop Floor Systems

Asset

Mgt

T&A

Payroll

ERP/SCM Systems

Engineering Systems

Labor Reporting Systems



Purchasing



Supplier Quality



Scheduling



Personnel



Training



Qualification



Accountability



Maintenance



Disposition



Work Order Execution


Data Collection


Labor Collection


Eng Documents


CAD Models


Drawing Images


Change Mgmt

Copyright
© 2006 WBF. All rights reserved.

MIG WG and IOpCAC Goal


One top level generic ISA
-
95/OAGi manufacturing
interoperability model is desired as much as practical.


Analysis of discrete and process manufacturing to identify
additional content needed in the model and standard.


Customer input is needed to help establish the shape of the
circles.


Process
Models
Discrete
Models
Hybrid
Models
Copyright
© 2006 WBF. All rights reserved.

UN/CEFact Core Components


Standard for defining universal XML types


Prevent XML vocabularies from splintering


e.g. DateTime, Identifier, Value, Person,…


OASIS


ISO 15000
-
5


ISO TC 154


Very important to SAP, IBM, Oracle


Simplifies ERP level integration


No uniform implementation yet


OAGi is leading in some areas


Level of support in B2MML?

Copyright
© 2006 WBF. All rights reserved.

Proliferation of XML Vocabularies

Copyright
© 2006 WBF. All rights reserved.

Structure & Semantics are Problems

Copyright
© 2006 WBF. All rights reserved.

B2MML V04


V04 RC1


No comments received on ISA
-
95 Part 5 or Core Components


Presentation by Dennis


Comments to date


SP95 comments

Copyright
© 2006 WBF. All rights reserved.

B2MML V04


B2MML V04 RC01 (Release Candidate 01) includes


Support for the ANSI/ISA 95 Part 5 transactions


Uses a proper subset of the OAGiS transaction definitions


B2MML v04 XML documents will also be valid OAGiS documents


“ApplicationArea” in a B2MML transaction messages


Same as the OAGiS “ApplicationArea”


“Verb areas” are a subset of the OAGiS verb areas.


Support the use of the UN/CEFACT and ISO 11179 standards
for the base types used in the schemas


Issues remain


What is the correct level of support?


Increased support will cause bigger upward compatibility issues


Changes based on WG comments

Copyright
© 2006 WBF. All rights reserved.

Combine Material Objects


The ISA95 standard is not consistent in the way material is
handled


The Material objects in Production Capability, Process Segment
Capability, Process Segment and Product Definition models use 1
material object


Production Schedule and Production Performance models use 3
material objects (consumed, produced and consumable).


The use of 3 objects is unnecessary and limits the use of other
categories such as scrape and rework.


Submitted to SP95 Committee with Suggested Resolution:


Define a new unique Material Requirement object in the Schedule
schema to replace the 3 existing material objects, following the same
pattern than in the other models.


Do the same for Production Performance using a new object called
Material Actual


Accepted by SP95

Copyright
© 2006 WBF. All rights reserved.

Location


Part 2 defines a location attribute for segments in Process
Segment, and Production Capability but not in Schedule and
Performance.


Based on implementation experience the Location attribute is
very important for these models and should be added to all
segment objects.


Also it should be added to the Production Request and Response
objects as it would then be available at the higher and lower level
objects so it will be desirable to have it in the middle.


Submitted to SP95 Committee with Suggested Resolution:


Add the location element to the Production Request, Segment
Requirement, Production Response and Segment Response objects


Accepted by SP95

Copyright
© 2006 WBF. All rights reserved.

Add Status Attribute


Status information often must be passed as part of a production
schedule or performance message.


Establishing this as attributes of the key schedule and
performance model objects will clarify how this should be down
and enable wider and easier adoption of ISA
-
95.


As Part 5 implementations are rolled out this will become even
more important in order to convey transaction state information
as part of business transactions.


Submitted to SP95 Committee with Suggested Resolution:


Add an optional Status element to the Production Schedule,
Production Request, Segment Requirement, Production
Performance, Production Response, and Segment Response objects.


Accepted by SP95

Copyright
© 2006 WBF. All rights reserved.

Recursive Production Data


ProductionData element in Segment Response from
ProductionPerformance model is a "flat", multiple
value structure while ProductionParameter element in
SegmentRequirement from
productionSchedule

schema is recursive/structured


Passing structured data back from production is
certainly as needed as passing parameter data
(more?)


Submitted to SP95 Committee with Suggested
Resolution :


Change Production Performance model to


SP95 accepted

Copyright
© 2006 WBF. All rights reserved.

Resource Restriction

Removed


Problem:


The Resource elements (Specification/Requirement/Actual...) in segment
models in Production Capability, Process Segment, Product Definition,
Schedule and Performance do not consistently refer to Resources.


Sometimes a selector imposes to select the resource either by class or actual
resource, but not both together, while in other cases, all Resource handlers
can be specified without restriction.


Most of these Resource elements in segment models can only identify a
single class, equipment, personnel, material definition, lot, sublot


The ISA95 standard explicitly allows multiple choices for all resource
handlers

B2MML introduce restrictions with no justification


Proposal:


Make all Resource handlers optional and multiple, remove all selectors


Response:


B2MML will change and loosen the ISA
-
95 “typical” comment enforced in
B2MML and let either be used in B2MML and let the user decide to use one or
both.

Copyright
© 2006 WBF. All rights reserved.

Include Common

in Extension Schema


Request to have Extension schema include the Common schema


Proposal:


Import the common schema in the B2MML namespace


This has no impact on existing implementation, it just adds the ability to use
B2MML types.

That creates circular reference however (Common imports Extension which
imports Common). I hope that will lead to particular

issues


Response:


Rejected


In the past we've received comments to remove the duplicate include of the
common schema in the production schedule schema


the second one comes from the production performance schema


This was considered a nuisance


While import is less obtrusive and an include it would create a circular
reference


As each user can add the import and build upon the common types there is
not pressing need to change B2MML

Copyright
© 2006 WBF. All rights reserved.

B2MML Roadmap


V04


ISA
-
95 Part 5


Schema enhancements


UN/CEFact support


ISA
-
95 Part 4


Level 3
-
4 data exchanges to be rolled up with Parts 1 & 2


Generic work model


Applied to Production, Maintenance, Inventory, Quality


Drop support for the AnyType


Move to using the Extension schema


When?