BIM Asset Metadata Database Migration Assessment Brief
Plan a structured database migration and schema mapping for building information modeling assets.
Deploy this template when migrating complex BIM asset metadata into relational databases for property operations. It ensures entity integrity, IFC standard compliance, and zero data loss across construction handovers.
Role: Senior Construction Data Integration Engineer specializing in IFC/COBie metadata pipelines and relational store migrations.
Context
- Enterprise Client: {{construction_firm}}
- Legacy BIM Repository: {{source_bim_database}}
- Target Relational Engine: {{target_relational_engine}}
- Total Model Entities: {{asset_record_count}}
- Industry Data Standard: {{compliance_standard}}
- Permissible Migration Window: {{cutover_window_hours}} hours
Task
Author an architectural database migration brief defining the relational schema mapping, data validation pipeline, and cutover strategy for moving {{asset_record_count}} construction records from {{source_bim_database}} into {{target_relational_engine}}.
Method
- Analyze the entity-relationship taxonomy of building assets in {{source_bim_database}}.
- Map parametric BIM object properties to normalized tables in {{target_relational_engine}} complying with {{compliance_standard}}.
- Design surrogate key and GUID preservation strategies across parent-child asset hierarchies.
- Construct data hygiene rules to flag orphan MEP (mechanical, electrical, plumbing) components during extraction.
- Benchmark staging ingestion throughput to guarantee completion within {{cutover_window_hours}} hours.
- Formulate transaction boundary and rollback protocols for partial migration failures.
- Specify post-migration integrity verification queries matching spatial and attribute counts.
Constraints
- MUST preserve immutable IFC GUIDs across all relational entity records.
- MUST NOT permit unindexed foreign keys in the destination schema.
- Execution window must strictly fit inside {{cutover_window_hours}} hours.
- Target schema design must pass all {{compliance_standard}} validation requirements.
Output format
- Executive Summary: Target Architecture & Migration Scope (1 paragraph)
- Relational Entity Mapping Specification (table: Source Element, Target Table/Column, Type, Validation Rule)
- Ingestion Pipeline & Cutover Plan (ordered timeline with milestone timestamps)
- Verification & Rollback Protocols (4-6 step checklist)
Self-review
- Confirm all references to {{compliance_standard}} match genuine architectural naming conventions.
- Check that the cutover plan realistically fits the {{cutover_window_hours}} limit for {{asset_record_count}} records.
- Verify schema recommendations are natively compatible with {{target_relational_engine}}.
Explicit role, a named task, and discrete steps the model can follow.
Background, inputs and variables the model needs before it starts.
Hard boundaries — what the model must and must not do.
A named, field-level shape for the response.
Ordered work items that force analysis before an answer.
Length and structure that travel across frontier models.
Signal density — instruction weight without padding.
Documented variables so the scaffold adapts to new inputs.
Quality bar, assumptions and behaviour when inputs are thin.
How much real usage the template has behind it.