AS ISO 29481.2:2018 pdf download.Building information models-Information delivery manual part 2: Interaction framework.
4 Standard principles
4.1 General
This clause is included to highlight and help explain essential concepts on which this part of ISO 29481 is based.
4.2 BIM and IDM
Building information modelling brings together the diverse sets of information used in construction into a common information environment. For this to happen, there should be a common understanding of the building processes and the information that is needed for and from their execution. ISO 29481 is a standard that sets out a method for the development of an Information Delivery Manual. The IDM methodology given in ISO 29481-1 shall be used for all references to development and use ofIDM.
4.3 Components of IDM
The methodology and components of IDM are described in ISO 29481-1. In that part, an illustration is given that diagrammatically shows what the different components of IDM are and how they are related. Within IDM, there are two perspectives. These are seen as user requirements and technical solutions.
Within the two perspectives, there are a number of zones that characterize the various components of IDM (see Figure 1).
4.4 Basic principles of business communication
Once a client or customer has asked to deliver a product or provide a service, there will be a chain of activities in operation, whose combined effect is to provide the product or service. Such a chain of activities is called a business process. More specifically, we speak here of a primary business process
because it is initiated externally. Part of the business process is the communication between the involved parties. This part of ISO 29481 concentrates on the communication that relates to the delivery of an outcome (performative communication). The initiation and execution of a request is through communicative actions. In a communicative action, two parties are always involved: the person who performed the action and the person to whom the action is directed. The handling of a request appears to occur in a particular pattern called the transaction.
In Figure 2, the simplest form of this transaction pattern is presented. It shows that bringing about of a new production result (for example, the ‘desired result’ is the delivery of a document) starts with requesting of this result by someone in the role of customer from someone in the role of producer. This brings the process to the state “result requested”. The producer responds to the request by promising to produce the desired result, which brings the process to the state “result promised”. This presents a to-do item for the producer: he has to comply with the promise by actually preparing the document and deciding to deliver the document. In the act of handing over the document to the customer, he states that he has complied with his promise. The customer responds to this state by accepting the result as produced. This act completes the transaction.
In the execution of the business process, often many actors are involved. Their behaviour is dependent on their role in the process. Roles/actors do business with other roles/actors by executing transactions. A useful representation of the interaction between roles/actors is called the interaction map.
4.5 Interaction map
An interaction map shall identify the relevant role types and transaction types for a certain process. 1DM draws a distinction between a role that makes a request, the initiator, and the role that gives effect to that request, the executor. A transaction shall have only one initiating role and only one executing role. Figure 3 shows the components of the interaction map.
NOTE The notation of the interaction map is based on the construction model as described in the publication of Prof. Jan L.G. Dietz. This notation differs from BPMN and is used to prepare maps that are as simple as possible. Also, it provides the concept of ‘transaction’, which is not available in BPMN.AS ISO 29481.2 pdf download.