M

• Maintenance StrategyThe planned approach for maintaining assets, systems, and spaces to meet performance, safety, and cost objectives. Maintenance Strategy may include Preventive Maintenance and Condition Assessment.
• Master Information Delivery Plan MIDPA consolidated schedule of information deliverables for the project. The Master Information Delivery Plan brings together Task Information Delivery Plan inputs into a coordinated project-level view.
• MasterFormatA classification structure commonly used to organize construction work results and specification sections. MasterFormat can be linked to cost, procurement, and project documentation workflows.
• Material Takeoff MTOThe extraction of material quantities from drawings, models, or data for procurement, estimating, or planning.
• Mechanical ModelA discipline model representing mechanical systems such as heating, cooling, ventilation, plant, and equipment. Mechanical Model information often includes HVAC System, Ductwork, and performance data.
• MEP Model MEPA discipline model representing mechanical, electrical, and plumbing systems. MEP Model coordination is a major source of Clash Detection and installation planning.
• MetadataDescriptive information about a file, model element, asset, or dataset. Metadata can include author, status, revision, classification, location, and approval details.
• Method Statement SimulationA visual or model-based simulation of how a construction method will be executed step by step.
• Model Audit ReportA report documenting checks performed on a model, including naming, data completeness, coordinates, warnings, and standards compliance.
• Model CheckingThe process of evaluating a model against requirements, rules, or expected information quality. Model Checking can include geometry, data, classification, and deliverable compliance tests.
• Model Comparison ToolA tool that identifies differences between two model versions, such as changed objects, properties, quantities, or geometry.
• Model ConditioningThe preparation of a model for a downstream use by cleaning, simplifying, classifying, or enriching its data.
• Model CoordinationThe process of aligning discipline models, resolving conflicts, and improving design integration. Model Coordination uses Federated Model reviews, Issue Management, and Clash Detection.
• Model ElementAn individual object or item represented in a model, such as a wall, beam, pipe, space, or equipment item. Model Element reliability depends on correct geometry, parameters, classification,…
• Model EnrichmentThe addition of useful properties, classifications, quantities, or relationships to make a model more valuable for a specific use.
• Model FederationThe process of combining separate models into a coordinated environment for review and checking. Model Federation supports Clash Detection, design coordination, and project communication.
• Model GranularityThe degree to which model content is broken down into separate objects, systems, assemblies, or data records.
• Model LinkingThe process of referencing one model into another while keeping each source model separately managed.
• Model MaturityThe progression of model content from early intent to coordinated, verified, and handover-ready information.
• Model OriginThe reference origin point used by a model file to define its internal coordinate basis.
• Model Progression Specification MPSA project document that defines how model content develops across stages or milestones. It can connect Level of Development, responsibilities, and deliverable expectations.
• Model Publishing ToolA tool that prepares, packages, converts, or uploads model information for controlled sharing and review.
• Model ReliabilityThe confidence that model geometry and data are accurate enough for a stated use at a stated time.
• Model ReviewerA role that checks model content against project requirements, discipline expectations, and intended downstream uses.
• Model SimplificationThe reduction of unnecessary geometry or detail so a model performs better for coordination, analysis, or exchange.
• Model SplittingThe division of a large model into manageable files, zones, packages, or discipline segments.
• Model Status ReviewA review that checks whether a model is suitable for its stated purpose, exchange status, and next project decision.
• Model ValidationThe confirmation that a model meets defined technical, information, and delivery requirements. Model Validation can include Geometry Validation, Data Validation, and coordination checks.
• Model VersioningThe controlled tracking of model changes across revisions, issues, and deliverables. Model Versioning helps teams compare updates and understand which information is current.
• Model View Definition MVDA defined subset or exchange view of a larger schema for a specific workflow or purpose. A Model View Definition helps make IFC exchanges more predictable and testable.