Building information models Information delivery manual
建築資訊模型資訊傳遞手冊
Part 1:Methodology and format 第1部分:方法和格式
1 Scope 領域
This part of ISO 29481 specifies
-a methodology that links the business processes undertaken during the construction of built facilities with the specification of information that is required by these processes, and
-a way to map and describe the information processes across the life cycle of construction works.
ISO 29481的這部分規定:
它是一種方法,能夠将設施建構期間進行的業務流程與這些流程所需的資訊規範聯系起來。它也是一種映射和描述跨建築工程生命周期的資訊過程的方法。
2 Normative references 引用标準
3 Terms and definitions 術語和定義
4 Information delivery manual 資訊傳遞手冊 IDM
5 IDM Framework IDM架構
附件A
IDM development process IDM開發過程
A.1 Propose an IDM development 提出一個IDM的開發
A.2 Undertake an IDM development 實施IDM開發
附件B
Examples of simplified IDM components 簡化IDM元件的例子
B.1 Business context of the examples 示例的業務上下文
B.2 Process map 流程圖
B.3 Interaction map 互動圖
B.4 Transaction map 事務圖
B.5 Exchange requirement 互動需求
附件C (informative)
Reference life cycle stages 參考生命周期階段
C.1 Standard life cycle stages 标準生命周期階段
- inception 概念 | |
-brief 初步設想 | 1)Conception of need 需求設想 2)outline feasibility 初步可行性研究 3)Substantive feasibility 大量可行性研究 |
-design 設計 | |
-production 生産 | |
-maitenance 維護 | |
-demolition 拆除 |
C.2 Local life cycle stages 局部生命周期階段
Life cycle stages are usually defined according to local process protocols. That is, the identification of life cycle stages in one place will differ from the identification of life cycle stages in another place. For example, project development is often organized according to the RIBA Plan of Work within the UK and according to the HOAl protocol in Germany.
生命周期階段通常使用本地過程協定。也就是說,各個地方有各自的對生命周期階段的識别方式。例如,項目開發在英國是基于RIBA工作計劃,而在德國則是HOAl協定組織的。
附件D (informative)
IDM use of BPMN methods IDM使用BPMN方法
IDM recommends (but does not mandate) the use of the 22 business process modelling notation (BPMN) symbols below for the development of process maps (Figure D.1). Table D.1 lists the definitions of the recommended BPMN symbols collected from the BPMN specification by the object management group (OMG).
IDM建議(但不強制)使用下面的22個業務流程模組化符号(BPMN)來開發流程映射(圖D.1)。表D.1列出了對象管理組(OMG)從BPMN規範中收集的推薦BPMN符号的定義。
Table D.1-Definitions of the recommended subset of BPMN symbols 表d .1 BPMN符号推薦子集的定義
Element | 元素 | Defination 定義 |
Activity (Task) Sub-process Sub-Process(Expanded) Sub-Process(Collapsed) Start Event Intermediate Event End Event Start Event(Message) Intermediate Event(Message/Catching) Intermediate Event(Message/Throwing) End Event (Message) Intermediate Event(Link/Catching) Intermediate Event(Link/Throwing) Gateway Gateway (Exclusive) Gateway (Parallel) Gateway (Inclusive) Sequence Flow(Normal or uncontrolled) Message Flow Association Data Association Pool Lane Data Object Group Text Annotation | 活動(任務) 子流程 子流程(擴大) 子流程(崩潰) 開始活動 中間事件 結束事件 啟動事件(消息) 中間事件(消息/捕捉) 中間事件(消息/抛出) 結束事件(消息) 中間事件(連結/捕捉) 中間事件(連結/抛出) 網關 網關(單例) 網關(并行) 網關(分流聚攏) 序列流(正常或者非控制的) 消息流 關聯 資料關聯 池 泳道 資料對象 組 文本注釋 | |
D.1 General information 基本資訊
D.2 Specification of processes and flows 工藝和流程的規範
1)Process flow 工藝流程
2)Sequence flow connections 序列流連接配接
3)Message flow connections 資訊流連接配接
4) Association and Data Association 關聯和資料關聯
D.3 Specification of events 事件規範
D.4 Specification of data objects 資料對象的規範
D.5 Specification of exchange requirements within a process map 在流程圖中說明交換規範