Over deze norm
The CEN WS/BII3 Workshop has recognised that to facilitate a high level of interoperability, there is a need to provide the capability to run business processes between disparate organisations using one or more transactions. This is achieved by defining the core set of information elements for each transaction in a defined business process, which are useful and understandable in all business scenarios in scope. Generally, the term core has a very broad meaning and exists for different types of objects (from semantic models to fruits). However in CEN WS/BII3, a single Core Information Requirement Model defines the business information considered to be: necessary to reach the business goals which are in scope. - rich enough to represent a typical business transaction - simple to implement without too much preparation and system adaptions - fully understood by the receiver - possible to reuse, extend and customize for more specific use cases. Therefore there is no single Core for all transactions but a Core for each transaction that have elements in common. This is because one transaction may effectively imply a request for information and the response will provide the update. The key exercise is to define and agree on the scope and business goals to ensure the transaction is produced from a methodology to ensure it is Core. The business goals can be translated into the business functions supported by the transaction. The considerations about implementation simplicity should be a leading principle. The number of goals for the Core Model will be a consequence of the stakeholders and their ambitions... A large group with diverging goals will jeopardize the principle of simplicity. It is therefore important that the members of the group have a common understanding of the principles of core and are willing to compromise. A methodology to extend (customize) the transactions is also necessary to be in place. If the methodology is too complex to use or understand, the risk is that the stakeholders prefer to add all their specific requirements to the transaction, and by this approach risking the simplicity, instead of considering to add them to an extension at a later stage. Defining BII Core Models has been a fundamental part of BII deliverables for the past six years and the Workshop has developed various models for transactions in both Post and Pre-Award scenarios3. This guide describes the methodology by which Core Information Requirement models (Core Models) are produced and therefore ensuring the resulting transactions are also Core.
|Engelse titel||Business Interoperability Interfaces for Public Procurement in Europe - Architecture - Part 109: Guideline on the Concept of Core|