Already a subscriber?
MADCAD.com Free Trial
Sign up for a 3 day free trial to explore the MADCAD.com interface, PLUS access the
2009 International Building Code to see how it all works.
If you like to setup a quick demo, let us know at support@madcad.com
or +1 800.798.9296 and we will be happy to schedule a webinar for you.
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:2011 Information technology. Business operational view - Operational aspects of Open-edi for implementation, 2011
- Purpose and overview
- Requirements on the business operational view aspects of Ope
- Business operational view (BOV), Open-edi and e-commerce, e-
- Use of “Person”, “person”, and “party” in the context of bus
- Organization and description of the document
- Registration aspects of Open-edi scenarios, scenario attribu
- Scope
- Normative references
- Terms and definitions�)
- Symbols and abbreviated terms
- Characteristics of Open-edi [Go to Page]
- Actions based on following clear, predefined rules
- Commitment of the parties involved
- Communications among parties are automated
- Parties control and maintain their states
- Parties act autonomously
- Multiple simultaneous transactions can be supported
- Components of a business transaction�) [Go to Page]
- Introduction [Go to Page]
- Overview
- Standard based on rules and guidelines
- Business transaction: commitment exchange added to informati
- Business transaction: unambiguous identification of entities�)
- Business transaction model: key components
- Business transaction model: classes of constraints
- Rules governing the Person component�) [Go to Page]
- Introduction
- Person, personae, identification and Person signature�)
- Person - identity and authentication
- Person and roles: buyer and seller
- Person and delegation to “agent” and/or “third party"
- Person and external constraints: the "regulator"
- Person and external constraints: individual, organization, a
- Person and external constraints: consumer and vendor
- Rules governing the process component�) [Go to Page]
- Introduction
- Planning
- Identification
- Negotiation
- Actualization�)
- Post-actualization
- Rules governing the data component�) [Go to Page]
- Recorded information
- Predefined and structured data elements
- Business requirements on the FSV (Business demands on Open-Edi Support Infrastructure)�) [Go to Page]
- Introduction
- Internal constraints (self-imposed)
- External constraints
- BOV requirements on the FSV for security methods and techniq
- Liability of repositories�)
- Primitive classification and identification of Open-edi scenarios�) [Go to Page]
- Introduction
- Classification of Open-edi scenarios [Go to Page]
- Requirements for classification of Open-edi scenarios
- Market type on business boundary
- Settlement type in business process
- Roles in business transactions: primitive or complex
- Trade models based on three classification factors [Go to Page]
- Trade models by market type: defined and undefined
- Trade models by settlement type: immediate and separate
- Trade models by participation type: bilateral and mediated
- Classification and scenario types of Open-edi scenarios [Go to Page]
- Classification on Open-edi scenarios
- Scenario types [Go to Page]
- Basic primitive trade scenario: (a)
- Basic complex trade scenario: (b)
- Defined primitive trade scenario: (i)
- Defined complex trade scenario: (j)
- Primitive agreement scenario: (c)
- Defined primitive agreement scenario: (k)
- Complex agreement scenario: (g)
- Defined complex agreement scenario: (m)
- Separate delivery scenario: (d)
- Separate payment scenario: (e)
- Authentication scenario: (f)
- Defined authentication scenario: (l)
- Remarks on scenario classification [Go to Page]
- Continuous transaction:
- Services transaction:
- Auction transaction:
- Bidding transaction:
- Credit payment transaction:
- Regulatory constraints:
- Guidelines for scoping Open-edi scenarios [Go to Page]
- Introduction and basic principles�)
- Rules for scoping Open-edi scenarios
- Template for specifying scope of an Open-edi scenario [Go to Page]
- Introduction to template
- Template�)
- Rules for specification of Open-edi scenarios and their comp [Go to Page]
- Introduction and basic principles
- OES demands on interoperability
- Rules for specification of Open-edi scenarios and scenario a [Go to Page]
- Open-edi scenario rules
- Open-edi scenario (OeS) attributes and associated rules [Go to Page]
- Scenario attribute: OeS identifier
- Scenario attribute: OeS name(s)
- 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
- Scenario attribute: OeS set of external constraints on busin
- Scenario attribute: OeS inheritance identifier(s) and cross-
- Scenario attribute: OeS security service requirements
- 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
- Scenario attribute: OeS demands on Open-edi infrastructure
- Rules for specification of Open-edi roles and role attribute [Go to Page]
- Rules governing roles
- Role attributes and associated rules [Go to Page]
- Role attribute: role identifier (ID)
- Role attribute: role name(s)
- Role attribute: role purpose
- Role attribute: role business goal(s)
- Role attribute: role business rules and constraints
- Role attribute: role inheritance identifiers and cross-refer
- Role attribute: role external constraints on business requir
- Role attribute: role security service requirements
- Role attribute: role communications and quality of service r
- Role attribute: Role demands on Open-edi Support Infrastruct
- Role demands on Open-edi Parties
- Interoperability demands among roles
- Role states
- Role transitions
- Role events
- Role actions
- Role internal function
- Role demand on Open-edi Support Infrastructure (OeSI)
- Rules for specification of Open-edi Information Bundles (IBs [Go to Page]
- Rules governing Information Bundles (IBs)
- Information Bundle (IB) attributes and associated rules [Go to Page]
- Information Bundle attribute: IB identifier
- Information Bundle attribute: IB name(s)
- 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
-
- Information Bundle attribute: IB recorded information retent
- Information Bundle attribute: IB time validity characteristi
- IB information for interoperability
- IB demands on Open-edi Support Infrastructure (OeSI)
- Rules for the specification of Semantic Components and Seman [Go to Page]
- Rules governing Semantic Components
- Rules governing Semantic Component attributes [Go to Page]
- Semantic Component attribute: SC identifier
- Semantic Component attribute: SC name(s)
- Semantic Component attribute: SC definition
- Semantic Component attribute: SC security service requiremen
- Business requirements on FSV (business demands on Open-edi S
- Primitive Open-edi scenario template [Go to Page]
- Purpose
- Template structure�) and content [Go to Page]
- IT-interface needs perspective�)
- Human interface needs perspective�)
- Consolidated template of attributes of Open-edi scenarios, r
- Requirements on Open-edi description techniques [Go to Page]
- General requirements on Open-edi description techniques
- Requirements on OeDTs for roles
- Requirements on OeDTs for Information Bundles
- References [Go to Page]