​​​​​​D3.1​: Functional Program of Requirements for planning and cost​

Summary

​​This deliverable describes the requirements in the context of cost and planning software. The requirements find their origin in different KPI’s and different use cases, an important source for this was D1.1 Best practices and existing shortcomings. Since use cases are not available during the development of this report the test cases are used as basis instead. This deliverable will be updated after the use cases become available. All requirements are collected and clustered. To create the software for INSITER the “to be developed functionalities” first have to be defined. There are two possible directions from where those features will be defined: on one hand there are the named functionalities given in the Description of Action (DoA) which highlight some relevant features. And on the other hand there are required functionalities coming from the Use Cases (respectively from the Test Cases since the Use Cases are not finally defined yet). After creating a list of all relevant functionalities an additional list of requirements for the software will be derived. Comparing this list of the functionalities from already available software in the market will reveal the gaps, which have to be closed by the “to be developed software” in the INSITER project. The review of state-of-the-art software and widely accepted open standards shows what is currently available in the market as well as what can be expected in the near future. Based on this review we check what requirements are fulfilled directly by existing solutions or solutions that are expected to come to market very soon and what requirements are not fulfilled by state-of-the-art software at this moment. This deliverable identifies the gaps between requirements and (soon to be) available solutions and secondly it identifies the gaps needed to full fill the requirements. When identifying the gaps between requirements and available solutions the following basic principles are kept in mind: 

• When possible existing software should be used, INSITER is not to reinvent the wheel or re-develop software solutions that already exist;
  
• When possible the focus will be on use of widely accepted open standards; 
  
• The main central component is the BIM server based on open standards; 
  
• Markets are changing rapidly , therefore when solutions are not available yet, but could be expected soon they will be included as feasible option; 
  
• Developments to be done within D3.2 have to be feasible within the scope of available time/resources within task 3.1. 
  

The final conclusion is that an integrated view of cost, planning and design available ‘anywhere’ is missing in the current field of applications. This is also something that can be developed as a plug-in of the Open Source BIM server. A complex part of making this visualization is already solved and available in this solution that can be used as the basic starting point. Within the standardization area important improvements are made in the area of scheduling/planning the latest release of IFC (ISO 16739:2013). Also for cost calculation, which is heavily depending on Quantity Take-Off relevant developments are found like QTie. However in this area INSITER can bring important improvements to standardization area by adding quality/trust of given quantities.​

Download​​​