Physical Address
304 North Cardinal St.
Dorchester Center, MA 02124
BS ISO IEC 15944 โ Information Technology Business Operational View (BOV) Standard Series
Information technology โ Business Operational View (BS ISO/IEC 15944, Open-edi and the business transaction model)
๐ BS ISO/IEC 15944 is the British Standards Institution’s adoption of ISO/IEC 15944, “Information technology โ Business Operational View” (BOV). The series provides a framework for describing how business transactions are modelled, registered, and run in the context of Open-edi (Electronic Data Interchange) and electronic commerce, so that heterogeneous systems can agree on a common semantics for “which actions, roles, and constraints constitute a business transaction”. It is maintained by Technical Committee IST/40 (Data management and interchange).
๐ก In cross-enterprise, cross-platform e-commerce, the most common problem is not “whether data can be transferred”, but “whether the two sides interpret a transaction differently”. BOV addresses exactly this semantic-consistency issue: it decomposes a business transaction into registerable scenarios and business objects.
1. Series Overview and the Business Operational View ๐
BOV is one of the three views defined by ISO/IEC 14662 (the Open-edi reference model), focused on the “business layer” โ the operations that trading parties actually carry out in commercial practice. Unlike views concerned with syntax and transport, BOV specifies the content of a business transaction, its business rules, and role responsibilities, making it the core building block of open, interoperable e-commerce. Part 1 (Operational aspects of Open-edi for implementation) is the foundational and framework document, defining the purpose, scope, and terminology of BOV and explaining its relationship to Open-edi and e-business/e-commerce.
โ ๏ธ BOV does not replace message syntax (such as XML or EDIFACT). It sits at the “semantic layer”: first it specifies which business objects and constraints constitute a business transaction, then hands the content to a syntax standard for carriage. Mistaking BOV for a transport standard is a common selection error.
2. Series Composition and Key Points ๐ง
| Part | Subject | Key Content | Readability |
|---|---|---|---|
| BS ISO/IEC 15944-1 | Operational aspects of Open-edi for implementation | Open-edi operational aspects for implementation (framework and terminology; supersedes 15944-1:2002) | Readable |
| BS ISO/IEC 15944-2 | Registration of scenarios and components as business objects | Registration of scenarios and their components as business objects (supersedes 15944-2:2006) | Readable |
| BS ISO/IEC 15944-4 | Business transaction scenario (extension) | Business transaction scenario modelling and ontology-related content (scanned, summarised from public-domain knowledge) | Scanned |
| BS ISO/IEC 15944-7 | Business transaction model (extension) | Business transaction model content (scanned, summarised from public-domain knowledge) | Scanned |
| BS ISO/IEC 15944-8 | Business transaction scenario (extension) | Personal-information and privacy-protection requirements in business transaction scenarios (scanned, summarised from public-domain knowledge) | Scanned |
| BS ISO/IEC 15944-9 | Business transaction scenario (extension) | Compliance and traceability content for business transactions (scanned, summarised from public-domain knowledge) | Scanned |
| BS ISO/IEC 15944-10 | IT-enabled coded domains as semantic components | IT-enabled coded domains as semantic components in business transactions | Readable |
| BS ISO/IEC 15944-20 | Business transaction scenario (implementation guidance) | Implementation guidance for small organisations and specific scenarios (scanned, summarised from public-domain knowledge) | Scanned |
๐จ Scanned-version note: Parts 4, 7, 8, 9, and 20 are derived from scanned originals. The descriptions in this article are written from public-domain knowledge; the official BSI published version takes precedence for the models and clauses.
3. Key Technical Requirements: Scenario Registration and Semantic Components ๐ฅ
Part 2 specifies how a “scenario” and its components (roles, business actions, business objects) are registered and version-managed as “business objects”. The registration mechanism lets different industry communities share, reuse, and trace definitions of business transactions, which is the key to the extensibility of BOV.
Part 10 (IT-enabled coded domains as semantic components) targets “coded domains” โ the code sets widely used in business transactions, such as currency codes, country codes, and units of measure. It specifies how to identify existing code standards, map them, and IT-enable them as reusable “semantic components” in the business transaction model, bringing code sets from scattered domains into a unified semantic framework. Part 1 unifies the terminology and the use of “person/party” in the context of business transactions and commitment exchange.
โ
IT-enabling coded domains is a lever for lowering e-commerce integration cost: once the currency, country, and unit codes in a cross-border order are standardised as semantic components, downstream systems only need to reference them rather than redefine them, significantly reducing semantic mismatch.
4. Engineering Practice ๐ ๏ธ
- ๐ Business process modelling: using the BOV method of Parts 1 and 2, model procurement, ordering, invoicing, and other business transactions as scenarios and business objects, and register them for cross-enterprise reuse.
- ๐ง Semantic integration: when integrating ERP, supply-chain, and e-invoicing platforms, IT-enable coded domains per Part 10 to ensure currency, unit, and status codes are consistent.
- ๐ Compliance and traceability: consider personal-information protection and transaction-audit requirements when designing transaction flows to meet data-protection and regulatory compliance (relevant extension parts are scanned and summarised from public-domain knowledge).
- ๐ Standards governance: industry communities publish and maintain business objects through the Part 2 registration mechanism, keeping transaction semantics versioned and under controlled evolution.
5. Frequently Asked Questions โ
โ Q: What is the relationship between BOV and common XML/EDIFACT messages?
A: BOV is the semantic layer: it specifies the content and constraints of a business transaction; syntax standards such as XML and EDIFACT carry and transmit the content that BOV defines. The two divide the labour of “business meaning” and “transmission format”.
A: BOV is the semantic layer: it specifies the content and constraints of a business transaction; syntax standards such as XML and EDIFACT carry and transmit the content that BOV defines. The two divide the labour of “business meaning” and “transmission format”.
โ Q: What is the use of “registration” in Part 2?
A: Registration assigns and version-manages scenarios and their components as business objects, enabling different communities to share and reuse transaction definitions, avoid duplicate modelling, and support traceability.
A: Registration assigns and version-manages scenarios and their components as business objects, enabling different communities to share and reuse transaction definitions, avoid duplicate modelling, and support traceability.
โ Q: Why do coded domains need their own standardisation?
A: Business transactions rely heavily on codes (currency, country, unit, status). Without harmonisation, two systems may interpret the same code differently, causing data mismatch. Part 10 IT-enables coded domains into semantic components to unify semantics.
A: Business transactions rely heavily on codes (currency, country, unit, status). Without harmonisation, two systems may interpret the same code differently, causing data mismatch. Part 10 IT-enables coded domains into semantic components to unify semantics.
๐ Q: Can the scanned parts be used for design and compliance?
A: The descriptions of the scanned parts in this article are written from public-domain knowledge and marked “scanned version”. For formal design and compliance, follow the clauses in the official BSI published version.
A: The descriptions of the scanned parts in this article are written from public-domain knowledge and marked “scanned version”. For formal design and compliance, follow the clauses in the official BSI published version.