The Business Process and Information model defines how to describe the basic information elements used in business messages and to describe business processes.
A Business Process is something that a business does, such as buying computer parts or selling a professional service. It involves the exchange of information between two or more Trading Partners in some predictable way.
The specification for business process definition enables an organization to express its business processes so that they are understandable by other organizations. This enables the integration of business processes within a company, or between companies.
The ebXML Business Process Specification Schema (BPSS) provides the definition of an XML document that describes how an organization conducts its business. An ebXML BPSS is a declaration of the partners, roles, collaborations, choreography and business document exchanges that make up a business process.
Following diagram gives a conceptual view of Business Process.
A Business Collaboration is a choreographed set of Business Transaction Activities, in which two Trading Partners exchange documents.
The most common one is a Binary Collaboration, in which two partners exchange documents. A Multiparty Collaboration takes place when information is exchanged between more than two parties.
Multiparty Collaborations are actually choreographed Binary Collaborations.
At its lowest level, a Business Collaboration can be broken down into Business Transactions.
A Business Transaction is the atomic level of work in a Business Process. It either succeeds or fails completely.
Business Transactions are transactions in which Trading Partners actually transfer Business Documents.
Business Document flows:
A business transaction is realized as Business Document flows between the requesting and responding
roles. There is always a requesting Business Document, and optionally a responding Business Document,
depending on the desired transaction semantics, e.g. one-way notification vs. two-way conversation.
Actual document definition is achieved using the ebXML core component specifications, or by some methodology external to ebXML but resulting in a DTD or Schema that an ebXML Business Process Specification can point to.
The choreography is expressed in terms of states and the transitions between them. A Business Activity is known as an abstract state, with Business Collaborations and Business Transaction Activities known as concrete states. The choreography is described in the ebXML Business Process Specification Schema using activity diagram concepts such as start state, completion state etc.
The Business Documents are composed of Business Information Objects, or smaller chunks of information that have previously been identified.
These chunks, or components, don't carry any information, of course. They are merely structures, such as an XML Schema or a DTD, that define information and how it must be presented. The end result is a predictable structure into which information is placed, so that the receiver of the final document can interpret it to extract the information.
Business Process Specification Example:
A partial example of Business Process Specification is given below:
<BusinessTransaction name="Create Order">
<DocumentEnvelope BusinessDocument="Purchase Order"/ >
A Business Process Specification:
- Describes collaboration between two partners
- Defines roles, relationships and responsibilities
- Defines choreography of business documents.
- Expressed in platform and vendor neutral format.
- Can be modeled with UMM (UN/CEFACT Modeling Methodology).
- Formally described by Business Process Specification Schema (BPSS).
- Referenced by CPP and CPA.
- Refers to Business Document Definitions.