Transcript Open Applications Group Project Definition

©
Open Standards that Open Markets™
Open Applications Group Project Definition
Name:
B2B Network Collaboration –
Setup and Messaging
January 17, 2014
© Open Applications Group, 2014 All Rights Reserved
Open Standards that Open Markets™
Agenda
•
•
•
•
•
•
Proposed scope and deliverables
Proposed approach
Assumptions, dependencies and issues
Outside resources
Questions
Next steps
© Open Applications Group, 2014 All Rights Reserved
2
Open Standards that Open Markets™
B2B Collaboration
Single OAGIS web service
pipeline
•Partner on-boarding Service
•Message Delivery Service
B2B Service Provider
(e.g. E2OPEN)
PROCUREMENT
FINANCIALS
CRM - ORDER
CAPTURE
SUPPLY CHAIN
MANAGEMENT
Oracle Supplier
Network
On-Premise B2B
(Legacy)
Access to partners
on other B2B
networks or VANs
Other B2B Networks
Trading Partner
Trading Partner
Trading Partner
Trading Partner
Trading Partner
Trading Partner
Trading Partner
Application is a
tenant on a B2B
Service Provider
Network
© Open Applications Group, 2014 All Rights Reserved
Web
Services,
HTTP,
FTP, SMTP
X12,
EDIFACT,
RosettaNet,
OAGIS
3
Open Standards that Open Markets™
Proposed scope and deliverables
• Specification for Trading Partners to setup
messaging interactions and exchange
messages through a B2B service provider
– Interactions initiated by “Tenants” on the Service Provider network
– Messages delivered to “Trading Partners” who are setup on the network
– “Tenants” interact with the Service Provider network using proposed new
OAGIS messages
– Service Provider transforms and delivers messages to Trading Partners in
their supported message format
– Service Provider receives messages from Trading Partners in their
supported message format, transforms to OAGIS and delivers to tenant
© Open Applications Group, 2014 All Rights Reserved
4
Open Standards that Open Markets™
Proposed scope and deliverables
• Why do we need something new
– ebXML has a comprehensive message definition for CPP
(Collaboration Partner Profile) and CPA (Collaboration Partner
Agreement)
– CPP/ CPA is intended for facilitating direct interaction between
trading partners, and requires every message sender to support the
messaging standards and protocols of the message recipient
– Service Provider model is simpler – sender is unaware of
capabilities or setup of recipient, and relies on service provider to
handle recipient requirements
– Service provider needs a single, consistent approach to deal with
their tenants, and also to interact with other service providers
© Open Applications Group, 2014 All Rights Reserved
5
Open Standards that Open Markets™
B2B Collaboration Discovery and Setup
•
•
•
•
•
Query for Trading Partner on
Service Provider Network - Get/
Show Collaboration Partner
Request Service Provider to onboard Trading Partner with support
for a set of messages - Process
Collaboration Partner/
Acknowledge Collaboration
Partner
Service Provider update on
Partner setup status – Notify
Collaboration Partner
Request Service Provider to
update Partner setup – Cancel
Collaboration Partner
Collaboration Messaging Setup
Service with above operations
© Open Applications Group, 2014 All Rights Reserved
6
Open Standards that Open Markets™
B2B Collaboration Messaging
•
•
•
Exchange messages with Service
Provider (messages intended for
Trading Partner) – Process
Collaboration Message/
Acknowledge Collaboration
Message
Confirmation of Message
Processing – Confirm BOD
Collaboration Messaging Service
with above operations
© Open Applications Group, 2014 All Rights Reserved
7
Open Standards that Open Markets™
Proposed Approach
• Collaboration Messaging Setup service
–
Operations to discover or setup a Trading Partner on the Service Provider network
• Collaboration Messaging Service
–
–
–
–
Operations to send messages, acknowledge message receipt and confirm message
processing
Single operation and payload type for processing all messages – Process Collaboration
Message
Process Collaboration Message payload is a standard OAGIS BOD identified using
instance type substitution
Set of BODs that are used in the Collaboration Message exchange declared in a
business process specific file that is referenced by the service
• e.g. all messages used for implementing the Procure to Pay process (Process
Purchase Order, Change Purchase Order, Notify Shipment etc) are in a single
Procure to Pay schema file that is generated from a set of profiled standalone BODs
© Open Applications Group, 2014 All Rights Reserved
8
Open Standards that Open Markets™
Advantages
• Ease of setup and management for both
tenants and the service provider
– Single service endpoint for a business process
– Flexibility to add support for new messages without changing the service
signature – only need to add additional types and the back end
implementation
– Standard OAGIS BODs used for messaging
– Single, profiled, standalone schema for a set of OAGIS BODs (set could be
business process specific, or span multiple business processes)
– Service implementation is not business process specific – business process
identified by the associated schema
© Open Applications Group, 2014 All Rights Reserved
9
Open Standards that Open Markets™
Nouns and Verbs to be added
• Verbs
–
None
• Nouns
–
Collaboration Partner
• Business Process Document
–
Business Process specific set of Nouns generated from the OAGIS library of BODs
• Services
– Collaboration Messaging Setup Service
– Collaboration Messaging Service
© Open Applications Group, 2014 All Rights Reserved
10
Open Standards that Open Markets™
Deliverables
•
•
•
•
Scenarios
Nouns
Procure To Pay Business Process Document
Services
© Open Applications Group, 2014 All Rights Reserved
11
Open Standards that Open Markets™
Workgroup Members
•
•
•
•
•
•
Ian Hedges, E2open – co-Chair
Mike Rowell, Oracle – co-Chair
Serm Kulvatunyou, NIST
Ralph Hertlein, Hertlein Group and OAGi VP
Satish Ramanathan, Oracle
Jim Wilson (will need a signature for
AgGateway)
© Open Applications Group, 2014 All Rights Reserved
12
Open Standards that Open Markets™
Planned Schedule
• Collaboration Partner – March 2014
• Process Collaboration Message – April 2014
• WG Review and Vote - May 2014
© Open Applications Group, 2014 All Rights Reserved
13
Open Standards that Open Markets™
Assumptions, Dependencies and Issues
• Assumptions
– Sufficient staffing
• Dependencies
– None at this time
• Issues
– None at this time
© Open Applications Group, 2014 All Rights Reserved
14
Open Standards that Open Markets™
Outside Resources Required
• Not expected at this time
© Open Applications Group, 2014 All Rights Reserved
15
Open Standards that Open Markets™
Next Steps
• Decision on Work Group by Architecture Council and
Policy Board
– Approved/not Approved?
– Issuance of Work Group IP signoff form
• Set up Google Drive
• Call for participation
• Set schedule for meetings
© Open Applications Group, 2014 All Rights Reserved
16
Open Standards that Open Markets™
OAGi Project Definition
Name: B2B Network Collaboration – Setup and Messaging
Signature Page
•
•
•
•
By signing this Project Definition you are agreeing to make a contribution to this Working Group
The scope of the contribution to the Working Group is constrained to the scope definition in this Project
Definition
The complete definition of a contribution and the terms under which the contribution are made is described in
the OAGi Intellectual Property Policy, which is available on the OAGi website at www.oagi.org
This page can be scanned and emailed to [email protected] or faxed to OAGi staff at +1 (770) 234-6036
Authorized Signature
Name Printed
Organization Name
Date
© Open Applications Group, 2014 All Rights Reserved