In developing the BuildUSA concepts and Prototype Initiative business plan, a number of industry recognized, as well as new words and terms were utilized. This post is a compilation of this information and provides both definitions and acronyms of some of the commonly used terms used within the Build Blog. It will be linked as a reference to all future blog posts and related documentation.
- Artificial Intelligence (AI): The simulation of human intelligence processes by machines, especially computer systems?
- Building: Spelled with a capital “B”, refers to the entire building eco-system required to create the built environment, from architecture/engineering, construction, materials, transporation…etc.
- Build Collaborative Environment Information Manager (BCE_IM): Working title for individual(s) who control and manage the implementation and operation of the BCE environment.
- Building collaborative Environment (BcE): Generic name for the BCE.
- Building Information Modelling (BIM): Industry standard reference for parametric modelling of buildings.
- BuildUSA (BUSA): Branded name that encompasses all business activities described within the Prototype Initiative.
- BuildUSA Collaborative Environment Manual (BCE_M): SharePoint website that has been developed to train and provide reference for staff and partners working within the BCE.
- BuildUSA Collaborative Environment: Branded name for the set of STW’s & software applications, that drive BuildUSA’s building process.
- Collaborative Digital Environment (CDE): Another term that is analogous to “Common Data Environment.
- Collaborative Integrated Partner Organization (CIPO): A BUSA legal framework, to organize strategic partners, including architects, engineers, manufacturers and contractors… who agree on inter company “Standard Operating Procedures” for designing, building and delivering Optimized buildings to market.
- Common Data Environment (CDE): Industry recognized term for the collaboration environment that allows individuals to share data and collaborate within the cloud environment.
- Construction Assembly Modules (CAMs): Defines multiple approaches to the creation of off-site modular components for buildings. Including; panels, racks, boxes or pods, kit of parts, groups, connections.
- Data Engine (DE): The DE is the core data creation data that defines a new building project. Typically created by architect/Engineer and closely aligned CIPO partners.
- design, Construct, Assemble, Manufacture Process (dCAMP): Industry recognized acronym for the industrialized building process.
- Director of Architecture & Architectural Systems Analysis (DoAASA): In coordination with the DoT & BUSA leadership, Individual in primary charge to ensure the architectural team maintains & continues to develop and document new STW’s within the BCE that optimize the building process.
- Director of Technology (Director of Technology): In coordination with the DoT & BUSA leadership, Individual in primary charge to ensure that the software/hardware environment required to operate the CDE and BCE are maintained, continue to be updated and monitored.
- Discipline Model (DM): Revit model linked to pCF, that is controlled by each discipline (i.e. MEP/FP).
- Discipline Model file (DMf): Actual Revit file containing discipline data, which is linked to the pCF.
- Fourth Industrial Revolution (Industry, 4.0 4IR): Industry accepted term for the evolution of software/hardware environment and data creation and sharing.
- Internally Integrated Business Conglomerates (IIBC): In the BUSA business plan the IIBC represent large international companies that compete by integrating all services internally within their corporate structure.
- Internet of Things (IoT): Industry accepted term where the physical environment will increasingly be sensored, and the data will be collected to provided better operational understanding & control.
- Material Procurement (MP): The work to aggressively integrate the material line itemization, budgeting, pricing and bidding processes, and actual procurement of materials into the BCE and Revit models.
- Modular building Model (MbM): Revit models that have been created, using digital versions of the various CAM assemblies used in Optimized building solutions. The MbM is composed of the pCF, PmF and DMf (MbM).
- Nested Hierarchies (NH): Related to both hierarchical relationships developed for data structures and modular construction solutions.
- Optimized Ambulatory Building (oAB): An Ambulatory Building designed, developed and constructed using all the attributes of Optimized building. (See Optimized Building)
- Optimized Building (oB): Optimized building is defind by 10 specific characteristics. All must be present in a fully Optimized building. (See Optimized Building)
- Placeholder File (PF): The placeholder file is a defined volume, that can be used in arranging “Optimized Building” designs. The placeholder file volume is linked to the actual components of the design suite options or CAMs that are being arranged.
- Placeholder model File (PmF): Revit file defines the specific placeholder volume for each CAM assembly within the project design.
- project Central File (pCF): Project central shared file within collaborative Revit environment.
- Project Management (PM): Industry accepted term for the management of building projects.
- Project Master Information Delivery Plan (PMIDP): Industry accepted term, that is analogous to the BCE Manual. It describes the STW’s (rules) that must be followed in order for the CDE-BCE environment to properly operate.
- Project Stakeholders (PS): Industry accepted term, for interested and impacted parties to a project.
- Proof of Concept (PoC): Industry accepted term, that defines an initial phase that proves out various initial assumptions.
- Prototype Initiative (PI): The PI is the business plan that BuildUSA is implementing. (See PI)
- Standards, Templates & Workflows (STWs): The set of data structures that underpin the BCE.
- Standards: Defined coding, classification, naming, graphic…conventions that standardize how data and work is created.
- Templates: Template files have imbedded within them established standards and workflows.
- Workflows: The defined work paths, both concurent and sequential, that establish the how, what, where, when an how data is created.