Communities

1
ACC-821 8 DEC 2004The Evolution of Enterprise
Systems - II

• Communities
• Independent view
• Collaboration space
• ebXML open-edi
• Ecological Fit

2
Collaboration Space
Value Exchange
Buyer
Seller
Third Party
Japan expert contribution to 15944-4, 9 May 2002,
Seoul Korea
3
Electronic Collaboration WHY??Michael Hammer
-- The Agenda

• Extend Your Enterprise
• See your business not as a self-contained company
  but as part of an extended enterprise of
  companies that work together to create customer
  value.
• Identify and strengthen the key processes at
  which you excel outsource everything else to
  someone better equipped to do it.
• Be prepared to rethink your companys identity
  and strategy in fundamental ways.

4
Electronic Collaboration WHY??Michael Hammer
-- The Agenda

• Knock Down Your Outer Walls
• Streamline the connections between your processes
  and those of your customers and suppliers
• Relocate work between companies so that it is
  done by whoever can do it best
• Coordinate through open sharing of data between
  companies (independent view of transactions?)
• Exploit the opportunity of collaborating with
  co-customers and co-suppliers

5
Collaboration Perspective Trading Partner vs.
Independent
Dotted arrows represent flow of goods, services,
and cash between different companies solid
arrows represent flows within companies
Japan expert contribution to 15944-4, 22 Oct
2001, Victoria BC ,
6

• Perspective-Dependent Collaboration Descriptions
• Inside agent outside agent
• Vendor Customer
• Inflow Outflow
• Sale Purchase
• Cash Receipt Cash Disbursement

7

• Perspective-Independent Collaboration
  Descriptions
• Initiating agent Responding agent
• Flow
• Shipment
• Payment
• Buyer Seller ??

8
Event-Type
Economic Event
typification
quantity applied
duality
Shipment
Payment

9
Economic Event
Economic Agent
accountability
Economic Agent Type
typification
10
Electronic Collaboration Old (bottom-up) and
New (top-down)

• OLD technology is EDI (electronic data
  interchange)
• EDI has standard documents or transaction sets _at_
  to X12 (American) or EDIFACT (everywhere else)
• Industry RosettaNet
• Cross Industry -- OAG
• NEW technology is XML
• Bottom-up ? UBL
• Top-down ? ebXML or BP emphasis

11
ebXML -- 101
12
Business Semantics of ebXML

• ebXML uses a concept of shared business objects
  to keep a partners processes aligned with
  another partners processes
• When partners in a collaboration agree on the
  same value (or state) of a shared business
  object, then each of their business processes
  should be synchronized, and the partners are said
  to be in state alignment
• ebXML calls a shared business object a Business
  Entity (BE)
• Examples of Business Entities A purchase order,
  a shipping container
• An instance example of a BE PO AB1234, SEAU
  6547347
• A BE has 2 important points
• a state value (the business object is in a
  condition)
• a lifecycle (the phases a business object goes
  through from start to finish)
• Understanding the behavior and lifecycle of BE is
  critical to modeling
• There will be a Library of Business Entities

Source ebXML COOL presentation by R. Haugen
J. Yunker)
13
Business State Alignment

• Means both trading partners must agree on the
  state of each Business Object at the end of each
  Business Event.
• For example, the Order is not accepted until both
  partners agree explicitly that it is accepted.
• The Business Transaction protocol must insure
  that both partners transition to the new Business
  State - or neither does.
• Think electronic handshake.

Source ebXML BCPMC Bob Haugen
14
Economic Resource Type
governs
Agreement
typifies
establish
specifies
specifies
Business Role
involves
Economic Commitment
Economic Event Type
specifies
qualifies
fulfills
reserves
typifies
Economic Event
Economic Resource
stockflow
Economic Agent
from
to
constrains
duality
Partner
requires
Bilateral Collaboration
Mediated Collaboration
participates
ISO Open-edi Ontology Collaboration Model
15
An Example Business Transaction with Business
Events Grouped in Phases
16
EconomicResourceType
ltltBusinessEventgtgt publishCatalog
ltltBusinessEventgtgt sendCatalogRequest
ltltBusinessEventgtgt
acceptAvailabilityAndPriceRequest
ltltBusinessEventgtgt sendOffer
ltltBusinessEventgtgt acceptOffer
ltltBusinessEventgtgt shipAcceptableSubstitute
State Machine Diagram for Economic Resource Type
17
Sample States for Business Objects
18
negotiation pending ? negotiation
in-service ? negotiation complete
Sample Business Objects with State Life Cycles
19
ebXML vision

• A global electronic market place where
  enterprises of any size, anywhere can
• Find each other electronically
• Conduct business through the exchange of XML
  based messages
• Using standard message structures
• According to standard business process sequences
• With clear business semantics
• According to standard or mutually agreed trading
  partner agreements
• Using off the shelf purchased business
  applications
• TEAMS BP, CC, TP, security, messaging services,
  architecture, QC, etc.

20
Collaborative Process Interactions
1
Collaboration Protocol Profiles, Business
Process Models (BPSS)
XML
Business Scenarios
1
1
COMPANY A
COMPANY A
Business Profiles
Request Business Details
Request Business Details
2
2
Build Local System
Build Local System
3
Collaboration Protocol Profiles
Implementation
Implementation
ebXML
3
3
Register Implementation Details
Register Implementation Details
Registry
Register COMPANY A Profile
Register COMPANY A Profile
4
Collaboration Protocol Profiles, Business
Process Models (BPSS)
Download
Download
4
4
Query about COMPANY A profile
Query about COMPANY A profile
Agree on Business Arrangement
Agree on Business Arrangement
Scenarios and Profiles
Scenarios and Profiles
5
5
5
Collaboration Protocol Agreement
DO BUSINESS TRANSACTIONS
DO BUSINESS TRANSACTIONS
6
6
COMPANY B
COMPANY B
ebXML
compliant
system
21
CPP CPA Summary
What Parties ARE SCHEDULED to do
Collaboration Protocol Agreement (CPA)
BusinessProcess Definition
BusinessProcess Definition
intersection, negotiation
Party 1 CPP
Party 2 CPP
What Parties COULD do
22
ebXML Architecture
Core/IndustryComponents
BusinessDocuments
BusinessProcess
Design Time
Business Libraries, Trading Partner Directories,
etc
Registries/Repositories
CollaborationProtocolProfile
CollaborationProtocolProfile
CP Agreement
BusinessServiceInterface
BusinessServiceInterface
Transport
Message
Runtime
BusinessServices/Apps
BusinessServices/Apps
23
UMM metamodel
Business Domain View (BDV)
Business Area
Process Area
Business Process
Business Requirements View (BRV)
Agreement
Business Collaboration (binary or multiparty)
Partner
Economic Resources
Economic Event
Business Transaction View (BTV)
Requesting Business Activity
Authorizing Roles
Business Transaction
Responding Business Activity
Business Documents
Business Service View (BSV)
Requesting Service Transaction
Business Messages
Network Component
Responding Service Transaction
Source ebXML TMWG
24
? XBRL?
?XBRL ?

• Business Process XML (ebXML, OAG, ISO) ?

transactions, business events, value creation,
and controls
COMPANY A
COMPANY B

• General Ledger Taxonomy
• AccRec (B) xx Sales -- xx
• COGS yy Inventory yy
• Cash -- xx AccRec (B) xx

• General Ledger Taxonomy
• Purchases xx AccPay (A) xx
• AccPay (A) -- xx Cash xx

Collaboration System
Collaboration Messaging for
Planning Identification Negotiation Actualization
Post-Actualization
Traditional EDI
XML domains
25
The Semantic Web

• Beyond Enterprise Systems
• Everybody-to-everybody
• RDF ontologies
• Agent technology

26
Organizational Fit for Enterprise Systems

• Characteristics
• Speed of change
• Competition
• Complexity
• Corporate Structure
• Size

• Ecological Niches
• Ocean
• Lakes
• Desert
• Mountains
• Puddle

27
Enterprise Information Systems
Basic Accounting Systems
Counting artifacts
e-collaboration systems
Enterprise Systems classification structure is
from David, McCarthy Sommer, Communications of
the ACM, May 2003, pp. 65-9.
back
28
QUESTIONS ??
29
(No Transcript)