Zeb, J and Froese, T (2014) Infrastructure management transaction formalism protocol specification: A process development model. Construction Innovation, 14(1), pp. 69-87. ISSN 1471-4175
Abstract
Purpose - The purpose of this paper is to develop a step-by-step procedure, referred to as transaction formalism protocol (TFP) that the transaction development personnel will use to formalise transactions (communications) in the domain of infrastructure management. The protocol is developed at two levels of abstraction: TFP specification and TFP tool. This paper presents the TFP specification in detail and introduces the TFP tool briefly. The specific focus of this paper is on the development process of the protocol specification. Design/methodology/approach - A four-step approach is used to develop the TFP; including, identify and select existing standards, benchmark standards, link and build on these standards, and develop TFP. To develop the protocol, the function modelling standard, integration definition function modelling (IDEF0) is used. The IDEF0 treats each step of the protocol as a function. Findings - The TFP specification and TFP tool are developed using the proposed methodology. The TFP specification specifies inputs, controls, mechanisms, tools/techniques, and outputs required in each step, whereas the TFP tool defines forms for each step of the protocol that the transaction development personnel will use to define transactions in the domain of infrastructure management. Practical implications - The development of the TFP would enable the transaction development personnel (including transaction analysts, transaction designers, software developers, process modellers, and industry experts) to formalise transactions effectively and efficiently for the development of ICT-based collaboration systems. Originality/value - The proposed protocol incorporates shortcomings of existing standards. In contrast to other design standards that focus on either design or design cum implementation of the work processes and communications, the proposed TFP includes transaction monitoring and improvements in addition to the design and implementation of communications. Unlike other standards, the TFP is a detailed step-by-step procedure to ease its usability and understandability.
| Item Type: | Article |
|---|---|
| Uncontrolled Keywords: | infrastructure management,message template,transaction,transaction agreement,transaction formalism protocol,transaction map |
| Index terms: | implementation, modelling, monitoring, designer, transaction map, infrastructure management, message template, methodology, integration, collaboration, usability, transaction formalism protocol, design standard, specification, transaction agreement, personnel |
| Subjects: | research methods, management, infrastructure engineering, contractual condition, networking, organizational analysis, user-centered design, business, profession, control systems, technical documentation, communication, analytical methods, contractual arrangements |
| Topics: | Roles and Professions, Procurement, Engineering Principles, Research Practice, Contract Administration, Site Management, Organizational Design, Digital Applications, Design Practice, Human Resources |
| Descriptive scope: | 3 PCT |
N.B. Descriptive scope is a count of how many of the five facets of empirical research are indicated by the words used in title, abstract and keywords. It is not intended as a judgement on the research; merely a count of the kind of word we would expect to indicate Phenomenon, Concepts, Theoretical framing, Empirical techniques, Analytical techniques. If all five are present, then a code of “5 PCTEA” will indicate this. If you feel the coding for this record is questionable, we welcome discussion around the terms we matched or the way we categorized them. The facet you would expect may not be coded, or a facet may be coded inappropriately. This can also bear on a larger question, of which facets should be treated as defining in construction management research. Please get in touch, and we will look at it. More details here