BS ISO/IEC 15944-1:2011
$215.11
Information technology. Business operational view – Operational aspects of Open-edi for implementation
Published By | Publication Date | Number of Pages |
BSI | 2011 | 318 |
The Open-edi Reference Model (ISO/IEC 14662:2010, Clause 4) states:
“The intention is that the sending, by an Open-edi Party, of information from a scenario, conforming to Open-edi standards, shall allow the acceptance and processing of that information in the context of that scenario by one or more Open-edi Parties by reference to the scenario and without the need for agreement. However, the legal requirements and/or liabilities resulting from the engagement of an organization in any Open-edi transaction may be conditioned by the competent legal environment(s) or the formation of a legal interchange agreement between the participating organizations. Open-edi Parties need to observe rule-based behaviour and possess the ability to make commitments in Open-edi (e.g., business, operational, technical, legal, and/or audit perspectives).”
This part of ISO/IEC 15944 addresses the fundamental requirements of the commercial and legal frameworks and their environments on business transactions, and also integrates the requirements of the information technology and telecommunications environments.
In addition to the existing strategic directions of “portability” and “interoperability”, the added strategic direction of ISO/IEC JTC 1 of “cultural adaptability” is supported in this part of ISO/IEC 15944. It also supports requirements arising from the public policy/consumer environment, cross-sectorial requirements and the need to address horizontal issues.12) It integrates these different sets of requirements. See Figure 3.
This part of ISO/IEC 15944 allows constraints [which include legal requirements, commercial and/or international trade and contract terms, public policy (e.g. privacy/data protection, product or service labelling, consumer protection), laws and regulations] to be defined and clearly integrated into Open-edi through the BOV. This means that terms and definitions in this part of ISO/IEC 15944 serve as a common bridge between these different sets of business operational requirements, allowing the integration of code sets and rules defining these requirements to be integrated into business processes electronically.
This part of ISO/IEC 15944 contains a methodology and tool for specifying common business practices as parts of common business transactions in the form of scenarios, scenario attributes, roles, Information Bundles and Semantic Components. It achieves this by 1) developing standard computer processable specifications of common business rules and practices as scenarios and scenario components; and thus 2) maximizing the re-use of these components in business transactions.
PDF Catalog
PDF Pages | PDF Title |
---|---|
15 | Purpose and overview |
17 | Requirements on the business operational view aspects of Ope |
19 | Business operational view (BOV), Open-edi and e-commerce, e- |
20 | Use of “Person”, “person”, and “party” in the context of bus |
21 | Organization and description of the document Registration aspects of Open-edi scenarios, scenario attribu |
23 | Scope |
24 | Normative references Terms and definitions�) |
34 | Symbols and abbreviated terms Characteristics of Open-edi |
35 | Actions based on following clear, predefined rules Commitment of the parties involved Communications among parties are automated Parties control and maintain their states |
36 | Parties act autonomously Multiple simultaneous transactions can be supported Components of a business transaction�) Introduction Overview |
37 | Standard based on rules and guidelines |
38 | Business transaction: commitment exchange added to informati |
42 | Business transaction: unambiguous identification of entities�) |
45 | Business transaction model: key components Business transaction model: classes of constraints |
48 | Rules governing the Person component�) Introduction Person, personae, identification and Person signature�) |
53 | Person – identity and authentication |
56 | Person and roles: buyer and seller |
57 | Person and delegation to “agent” and/or “third party” |
58 | Person and external constraints: the “regulator” Person and external constraints: individual, organization, a |
62 | Person and external constraints: consumer and vendor |
63 | Rules governing the process component�) Introduction |
64 | Planning |
65 | Identification Negotiation |
66 | Actualization�) Post-actualization |
67 | Rules governing the data component�) Recorded information |
69 | Predefined and structured data elements |
72 | Business requirements on the FSV (Business demands on Open-Edi Support Infrastructure)�) Introduction |
73 | Internal constraints (self-imposed) |
74 | External constraints |
75 | BOV requirements on the FSV for security methods and techniq Liability of repositories�) |
76 | Primitive classification and identification of Open-edi scenarios�) Introduction Classification of Open-edi scenarios Requirements for classification of Open-edi scenarios |
77 | Market type on business boundary Settlement type in business process Roles in business transactions: primitive or complex |
78 | Trade models based on three classification factors Trade models by market type: defined and undefined |
79 | Trade models by settlement type: immediate and separate |
80 | Trade models by participation type: bilateral and mediated Classification and scenario types of Open-edi scenarios Classification on Open-edi scenarios |
81 | Scenario types Basic primitive trade scenario: (a) |
82 | Basic complex trade scenario: (b) Defined primitive trade scenario: (i) Defined complex trade scenario: (j) |
83 | Primitive agreement scenario: (c) Defined primitive agreement scenario: (k) Complex agreement scenario: (g) |
84 | Defined complex agreement scenario: (m) Separate delivery scenario: (d) Separate payment scenario: (e) Authentication scenario: (f) |
85 | Defined authentication scenario: (l) Remarks on scenario classification Continuous transaction: Services transaction: Auction transaction: Bidding transaction: Credit payment transaction: Regulatory constraints: |
86 | Guidelines for scoping Open-edi scenarios Introduction and basic principles�) |
87 | Rules for scoping Open-edi scenarios |
89 | Template for specifying scope of an Open-edi scenario Introduction to template |
90 | Template�) |
93 | Rules for specification of Open-edi scenarios and their comp Introduction and basic principles |
96 | OES demands on interoperability |
97 | Rules for specification of Open-edi scenarios and scenario a Open-edi scenario rules Open-edi scenario (OeS) attributes and associated rules |
98 | Scenario attribute: OeS identifier Scenario attribute: OeS name(s) |
99 | Scenario attribute: OeS purpose Scenario attribute: OeS set of roles Scenario attribute: OeS set of Information Bundles Scenario attribute: OeS set of requirements on Open-edi Part |
100 | Scenario attribute: OeS set of external constraints on busin Scenario attribute: OeS inheritance identifier(s) and cross- Scenario attribute: OeS security service requirements |
101 | Scenario attribute: OeS communication – quality of service r Scenario attribute: OeS role requirements and constraints Scenario attribute: OeS dependency among roles in a scenario Scenario attribute: OeS dependency among Information Bundles Scenario attribute: OeS dependency among Semantic Components Scenario attribute: OeS demands on Open-edi Parties |
102 | Scenario attribute: OeS demands on Open-edi infrastructure Rules for specification of Open-edi roles and role attribute Rules governing roles |
103 | Role attributes and associated rules |
104 | Role attribute: role identifier (ID) Role attribute: role name(s) Role attribute: role purpose |
105 | Role attribute: role business goal(s) Role attribute: role business rules and constraints Role attribute: role inheritance identifiers and cross-refer |
106 | Role attribute: role external constraints on business requir Role attribute: role security service requirements |
107 | Role attribute: role communications and quality of service r Role attribute: Role demands on Open-edi Support Infrastruct Role demands on Open-edi Parties |
108 | Interoperability demands among roles Role states Role transitions |
109 | Role events |
110 | Role actions Role internal function Role demand on Open-edi Support Infrastructure (OeSI) |
111 | Rules for specification of Open-edi Information Bundles (IBs Rules governing Information Bundles (IBs) |
112 | Information Bundle (IB) attributes and associated rules Information Bundle attribute: IB identifier Information Bundle attribute: IB name(s) |
113 | Information Bundle attribute: IB purpose Information Bundle attribute: business rules controlling con Information Bundle attribute: IB external constraints on bus Information Bundle attribute: IB contents Information Bundle attribute: IB security service requiremen |
114 | Information Bundle attribute: IB recorded information retent Information Bundle attribute: IB time validity characteristi |
115 | IB information for interoperability IB demands on Open-edi Support Infrastructure (OeSI) Rules for the specification of Semantic Components and Seman Rules governing Semantic Components |
117 | Rules governing Semantic Component attributes Semantic Component attribute: SC identifier Semantic Component attribute: SC name(s) Semantic Component attribute: SC definition |
118 | Semantic Component attribute: SC security service requiremen Business requirements on FSV (business demands on Open-edi S |
119 | Primitive Open-edi scenario template Purpose Template structure�) and content |
120 | IT-interface needs perspective�) Human interface needs perspective�) Consolidated template of attributes of Open-edi scenarios, r |
123 | Requirements on Open-edi description techniques General requirements on Open-edi description techniques |
124 | Requirements on OeDTs for roles |
125 | Requirements on OeDTs for Information Bundles |
126 | References |