Security check
Please login to your personal account to use this feature.
Please login to your authorized staff account to use this feature.
Are you sure you want to empty the cart?
BS ISO/IEC 15944-1:2025 Information technology. Business operational view - Operational aspects of open-edi for implementation, 2025
- undefined
- Foreword
- Introduction
- 1 Scope
- 2 Normative references
- 3 Terms and definitions
- 4 Abbreviated terms
- 5 Characteristics of Open-edi [Go to Page]
- 5.1 General
- 5.2 Actions based on following clear, predefined rules
- 5.3 Commitment of the parties involved
- 5.4 Communications among parties are automated
- 5.5 Parties control and maintain their states
- 5.6 Parties act autonomously
- 5.7 Multiple simultaneous transactions can be supported
- 6 Components of a business transaction [Go to Page]
- 6.1 General [Go to Page]
- 6.1.1 Overview
- 6.1.2 Standard based on rules and guidelines
- 6.1.3 Business transaction: commitment exchange added to information exchange
- 6.1.4 Business transaction: unambiguous identification of entities
- 6.1.5 Business transaction model: key components
- 6.1.6 Business transaction model: classes of constraints
- 6.2 Rules governing the Person component [Go to Page]
- 6.2.1 Purpose
- 6.2.2 Person, personae, identification and Person signature
- 6.2.3 Person — Identity and authentication
- 6.2.4 Person and roles — Buyer and seller
- 6.2.5 Person and delegation to “agent” and/or “third party"
- 6.2.6 Person and external constraints — The "regulator"
- 6.2.7 Person and external constraints: individual, organization, and public administration
- 6.2.8 Person and external constraints: consumer and vendor
- 6.3 Rules governing the process component [Go to Page]
- 6.3.1 Overview
- 6.3.2 Planning
- 6.3.3 Identification
- 6.3.4 Negotiation
- 6.3.5 Actualization
- 6.3.6 Post-actualization
- 6.4 Rules governing the data component [Go to Page]
- 6.4.1 Recorded information
- 6.4.2 Predefined and structured data elements
- 6.5 Business requirements on the FSV (Business demands on Open-Edi Support Infrastructure) [Go to Page]
- 6.5.1 Overview
- 6.5.2 Internal constraints (self-imposed)
- 6.5.3 External constraints
- 6.5.4 BOV requirements on the FSV for security methods and techniques
- 6.5.5 Liability of repositories
- 7 Basic principles, rules and guidelines for scoping Open-edi scenarios [Go to Page]
- 7.1 Basic principles
- 7.2 Rules for scoping Open-edi scenarios
- 7.3 Template for specifying scope of an Open-edi scenario [Go to Page]
- 7.3.1 Introduction to template
- 7.3.2 Template for specifying the scope of an Open-edi scenario
- 8 Rules for specification of Open-edi scenarios and their components [Go to Page]
- 8.1 Basic principles
- 8.2 OES demands on interoperability
- 8.3 Rules for specification of Open-edi scenarios and scenario attributes [Go to Page]
- 8.3.1 Open-edi scenario rules
- 8.3.2 Open-edi scenario (OeS) attributes and associated rules
- 8.4 Rules for specification of Open-edi roles and role attributes [Go to Page]
- 8.4.1 Rules governing roles
- 8.4.2 Role attributes and associated rules
- 8.4.3 Role demands on Open-edi Parties
- 8.4.4 Interoperability demands among roles
- 8.4.5 Role states
- 8.4.6 Role transitions
- 8.4.7 Role events
- 8.4.8 Role actions
- 8.4.9 Role internal function
- 8.4.10 Role demand on Open-edi Support Infrastructure (OeSI)
- 8.5 Rules for specification of Open-edi Information Bundles (IBs) and IB attributes [Go to Page]
- 8.5.1 Rules governing Information Bundles (IBs)
- 8.5.2 Information Bundle (IB) attributes and associated rules
- 8.5.3 IB information for interoperability
- 8.5.4 IB demands on Open-edi Support Infrastructure (OeSI)
- 8.5.5 Rules for the specification of Semantic Components and Semantic Component attributes
- 8.6 Business requirements on FSV (business demands on Open-edi Support Infrastructure)
- 9 Primitive Open-edi scenario template [Go to Page]
- 9.1 Purpose
- 9.2 Consolidated template for specifying attributes of Oen-edi scenario, roles and Information Bundles (IBs) [Go to Page]
- 9.2.1 IT-interface needs perspective
- 9.2.2 Human Interface Equivalent (HIE) needs perspective
- 9.2.3 Consolidated template of attributes of Open-edi scenarios, roles and Information Bundles
- 10 Requirements on Open-edi description techniques [Go to Page]
- 10.1 Overview
- 10.2 General requirements on Open-edi description techniques
- 10.3 Requirements on OeDTs for roles
- 10.4 Requirements on OeDTs for Information Bundles
- Annex A (normative) Consolidated controlled vocabulary definitions and associated terms, as human interface equivalents (HIEs), English and French language equivalency in the IT standardization context
- Annex B (normative) Codes representing presence-type attributes: mandatory, conditional, mandatory subject to a conditional, optional and not applicable
- Annex C (informative) Unambiguous identification of entities in (electronic) business transactions
- Annex D (informative) Existing standards for the unambiguous identification of Persons in business transactions (organizations and individuals) and some common policy and implementation considerations
- Annex E (informative) Business transaction model: Person component
- Annex F (informative) Business transaction model — Process component
- Annex G (informative) Business transaction model: data component
- Annex H (informative) Scenario descriptions using the Open-edi scenario template: "Telecommunications Operations Map" example
- Bibliography [Go to Page]
