A
- Access ControlRules and permissions that determine who can view, edit, approve, or share information. Access Control protects sensitive information and supports controlled collaboration in a Common Data Environment.
- Accessibility ReviewA review of spatial layouts and clearances against accessibility requirements for users and maintainers.
- Adaptive ComponentA flexible component whose geometry can respond to placement points, host conditions, or changing design context. Adaptive Component workflows are useful for complex façades, panels, and repeatable irregular…
- API Connector APIA software connector that uses an application programming interface to move information between applications.
- Application Programming Interface APIA defined way for software systems to request, send, or manipulate data and functions. Application Programming Interface connections can automate Data Exchange, dashboards, and Digital Twin integrations.
- Appointed PartyA party appointed to provide information, services, or works on a project. Appointed Party responsibilities are usually defined through the contract, Information Protocol, and delivery plans.
- Appointing PartyThe organization or person who requires information and appoints others to deliver it. The Appointing Party defines needs such as Exchange Information Requirements and acceptance criteria.
- Appointment DocumentA formal agreement or package that sets the scope, duties, information requirements, and deliverables for an appointed party.
- Approval Status CodeA code that records the review or authorization state of information, such as whether it is draft, accepted, or rejected.
- Approval WorkflowA defined sequence for reviewing, accepting, rejecting, or returning information. Approval Workflow steps help manage Status Code changes and control what information can be relied upon.
- Architectural ModelA discipline model representing architectural spaces, walls, doors, windows, finishes, and design intent. Architectural Model content coordinates with Structural Model and MEP Model information.
- Area MeasurementThe calculation or verification of areas for rooms, zones, floors, assets, or planning boundaries.
- As-Built ModelA model updated to reflect what was actually constructed, installed, or verified on site. An As-Built Model can support handover, Record Model creation, and Asset Information Model development.
- Asset Data CollectionThe process of gathering maintainable asset data from models, suppliers, commissioning teams, or site records.
- Asset Data ManagerA role responsible for defining, collecting, validating, and handing over structured asset data.
- Asset Data SetA structured package of asset information prepared for handover, operation, maintenance, or integration with FM systems.
- Asset Information Model AIMThe maintained information model used to support operation, maintenance, and asset decisions after handover. An Asset Information Model may include geometry, asset records, documents, and performance data.
- Asset Information Requirements AIRInformation requirements describing the asset data an organization needs for operation, maintenance, and long-term decisions. Asset Information Requirements guide the content of an Asset Information Model.
- Asset Information StrategyAn owner-side plan that explains what asset information is valuable, why it is needed, and how it will support operation after handover.
- Asset RegisterA structured list of assets with identifiers, attributes, locations, ownership, and maintenance information. An Asset Register can be populated from COBie, Asset Information Model, or field data.
- Asset TaggingThe assignment of unique identifiers or physical tags to assets so they can be found, tracked, and maintained. Asset Tagging may use QR Code, Barcode, or asset management…
- Audit TrailA record of who changed, approved, shared, or accessed information and when. Audit Trail data supports accountability, dispute resolution, and information governance.