Business Agreements - Management

1
Business Agreements - Management Registry
Proof of Concept Proposal
May 2005 David RR Webber david_at_drrw.net
2
Project Overview
Introduction

• Problem Statement
• Proposed Solution
• Approach

Planning

• Solution Architecture
• Solution Process
• Deployment Plan
• Participants

Supplemental Details

• Technology Components

3
Problem Statement

• Need to formulize and manage partner agreements
  both inside and outside enterprise
• Speed-up ability to integrate with partners by
  providing intuitive business-centric tools
• Provide common point of reference for partners to
  ensure consistent operational practices
• Facilitate re-use across enterprise by providing
  templates of proven solutions
• Provide open standards-based approach that can be
  accessed by implementation systems

4
1. Memorandum of Understanding - MoU
Proposed Solution Triad

• Business Managers
• Meeting of the Minds
• Business Goals
• Define Scope
• Rough Timeline
• Creation / Best Practice Wizard

3. On-line Registry

• Systems Administrators
• Manage operational use
• Provide automation access

2. Collaboration Protocol Agreements

• Operations Managers
• Precise Choreography
• Automated
• Messaging Parameters
• ebMS transport
• WSDL web services

5
Approach

• Needs
• The Business Mission Area needs a new type of
  Collaboration Agreement especially designed to
  address net-centric data sharing activities
• The Business Mission Area also needs
  state-of-the-art techniques for creating and
  maintaining net-centric data sharing agreements
  between data producers and consumers
• Road Map
• Review components of existing data sharing
  agreement formats
• Identify candidate data sharing agreement formats
  to be used
• Identify techniques for creating and maintaining
  these agreements

6
COLLABORATION AGREEMENT SUMMARY Impact to
Business Mission Area
7
Solution Planning

• Solution Architecture
• Solution Process
• Deployment Plan
• Participants

8
netCentric Solution Architecture
Wizard runtime
CPA Designer runtime extensions ebMS and WSDL
3
1
2
MoU Guide
Partner Interface Agreement builder review /
support / completion workflow
Reuse rationale maps
4
design time
supports ebMS exchanges and Web services WSDL
CPA with MoU Linking
6
Library Object templates/Components
XML
Management Configuration Reports
5
Facets Questions / Data
Registry and digital bag store
9
Solution Process

1. Select domain and category of MoU from available
   template options
2. Interact with Wizard Guide and create new MoU
3. Proceed to CPA step uses components from MoU
4. Complete one or more CPA entries using screens
   dialogue with runtime transport for ebMS / WSDL
5. Store to secure Registry catalogue (each
   enterprise has its own distinct domain and
   private entries)
6. Enterprise support staff review new submissions
   for accuracy and acceptance

10
Deployment Plan

• GUIDE product - MoU Wizard builder
• HTML-based CPA entry forms
• xslt CPA template models
• ebXML OMAR Registry

GUIDE MoU
HTML CPA
Templates CPA / WSDL
Developer Team
XML
ebXML Registry
Hosted via Internet
database
11
Participants

• Domain Participants
• Navy
• DOD / DFAS
• Consulting services
• eProcess Solutions (MoU design, CPA design,
  Webservices)
• ebXML Registry
• Navy supporting contractors (domain use cases,
  testing)

12
Technology Details

• Components Overview

13
MoU Builder Wizard

• Every MoU instance is a unique combination of
  common parts
• Allow users to assemble MoU from pre-built
  components
• Simplify and formulize MoU process under
  configuration control
• Dynamically configurable to match business domain
  and terminology
• Use intuitive HTML web-based interfaces

Conceptual Components
Who Stakeholders
Scope
1. Scope This Memorandum of Understanding
entered into between and . 2. Objective
The purpose of this MOU is to facilitate the
exchange of data 3. Responsibilities of
Parties 3.1 Both parties agree 3.1.1
3.1.2 3.1.4 to semantically align business
concepts (preferred term, aliases and XML tag) by
target date _2005-07-22__. Reference Appendix
A Concept Definitions Template (.xls) 3.1.5 to
technical exchange considerations by target date
__2005-08-04___ .
Reference Appendix B
Interface Specification
Why / What
When
14
MoU Builder Wizard (continued)
Focus on the business pick, choose, reuse from
libraries to build MoU wizards
15
MoU Builder Wizard (continued)
Guide Users step-by-step
16
Logical Information Lexicon
Business MoU Compendium
Where
When
Who
What
How
Why?
17
Memorandum of Understanding MOU
(continued)
18
Memorandum of Understanding MOU
(continued)
Semantic Alignment
http//FinMan.info/terms
19
CPA Structure Overview
http//www.oasis-open.org/committees/download.php/
253/cpa-example-2_0b.xml
20
Collaboration Agreement Build Steps
BPSS (OV-6C-based)
2
Query By CAGE CODE
CPP
Query By Company Name
CAGE System
Messaging Preferences
1
3
Via Web Service
Via EDI
WSDL support
4
Message Exchange Details
CPA
21
ebXML CPA Functions

• ebXML CPA provides
• Service name and parameters
• Endpoint for invocation
• Role of an organization in the context of a
  service
• Organization demographic information
• Failure scenarios
• Business process scenario and business
  transaction activity step
• Link to partner responsibilities
• Transaction Messages being exchanged
• Transport level QOS parameters
• Certificate and Encryption configuration
• Business status of agreement

22
Controlling Versioning via CPA ID

• Using Receiver CPA id value to manage versioning
• Partner can publish to public registry a generic
  CPA that contains a reference CPA id value and
  outbound service / actions.
• Value of CPA id corresponds to specific version
  of system e.g. NIHxCHG-eCGAP-010105-01
• Can be used to switch between inbound routing to
  test and production environments.
• This also allows explicit sub-versioning within
  the delivery handling, transaction validation and
  routing.
• Allows partners to automatically configure their
  delivery systems by looking up CPA details from
  registry via CPA id value.

23
What is a MOA / MOU?

• A formal agreement which can be used to
  characterize any relationship between two
  entities
• What are the components of a Memorandum of
  Agreement/Understanding
• Scope
• Objectives
• Responsibilities
• Interface Definition
• Data Transfer Frequency and Period
• Technical Infrastructure and Methodology
• Volumetrics
• Exception Processing
• Security Considerations
• Backup and Recovery Procedures
• Signature and Date
• Attachments (File layouts, data dictionary,
  sample files, etc.)

24
What is a Trading Partner / Service Level
Agreement?

• A formal agreement which prescribes the general
  procedures and policies to be followed by parties
  when using electronic data interchange techniques
  for transmitting and receiving information
• Used extensively throughout the public and
  private sectors today to document EDI data
  sharing agreements
• What are the components of a Trading Partner
  Agreement
• Purpose
• Objective
• Scope
• Terms and Conditions
• Limitations
• Dispute Resolution
• Termination Process
• Certification and Effective Date

25
What is a Data Sharing Agreement

• A formal agreement which sets forth the terms and
  conditions governing the exchange of data between
  two or more parties
• What are the components of a Data Sharing
  Agreement
• Requestor (Agency Name, Address, POC Name, POC
  Phone Number)
• Data Provider (Agency Name, Address, POC Name,
  POC Phone Number)
• Purpose
• Period of Agreement
• Justification for Access
• Description of Data
• Method of Access of Transfer
• Location of Data and Custodial Responsibility
• Disposition of Data
• Confidentiality
• Signatures and Effective Dates