Understand the reasons a BIMIT order may be delayed and how they are resolved.
BIMIT orders can be delayed for a range of reasons. When an order is delayed, our team works to clear the blocker and keep your order moving. Some delays move your order into a Paused state until the issue is resolved.
Below are the current delay reasons, grouped by category.
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D101 | Incomplete input data | The order can't proceed because required input data is missing or incomplete. | Missing scan files or reference materials; incomplete metadata or scope; partial upload at submission. | We contact you for the missing inputs and resume once all are received. |
| D102 | Input data quality limitations | Scan data didn't meet the minimum quality for the requested scope or level of detail. | Low scan resolution or density; occlusions in key areas; insufficient coverage. | We assess feasibility, apply corrections where possible, or request updated data. |
| D103 | Input data inconsistencies | Inconsistencies across the datasets need validation before modeling. | Conflicting reference files; scan vs. supporting-material misalignment; unclear project info. | We validate inputs and request clarification or corrections before proceeding. |
| D104 | Input data reprocessing required | Scan data needed extra processing before BIM production could start. | Registration or alignment issues; format or data-optimization needs. | We prepare the data and resume production once the dataset is ready. |
| D105 | Delayed or phased data delivery | Input data arrived in stages, affecting the planned production sequence. | Incremental uploads; late delivery of specific areas or references. | We adjust the production plan and continue as data arrives. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D201 | Scope clarification required | We needed to confirm modeling scope, inclusions, or exclusions. | Ambiguous scope; discipline boundaries not clearly specified. | We coordinate with you to clarify and proceed once confirmed. |
| D202 | Scope complexity higher than anticipated | Actual project complexity exceeded what the provided information indicated. | Dense MEPF; irregular geometry or complex layouts; high element repetition with variations. | We reassess timelines and adjust production planning. |
| D203 | Scope change after production start | Scope changes or additions were introduced after production began. | Added scopes; expanded modeling requirements; revised deliverables. | We evaluate the impact and update delivery timelines as needed. |
| D204 | Multi-discipline coordination impact | Combined scopes needed extra coordination and sequencing across disciplines. | Architecture, MEPF, and Site interdependencies; shared references or background models. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D301 | Limited visual references | Supporting visual references were missing or insufficient for efficient modeling. | Missing virtual tours; limited photo documentation. | We proceed with conservative assumptions or request more references. |
| D302 | Ambiguity in existing conditions | Existing conditions couldn't be fully confirmed from the available inputs. | Occluded or unclear areas; conflicting visual information. | We validate assumptions internally or request clarification before proceeding. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D401 | Technical processing constraints | Extra technical effort was needed to prepare project data for production. | Large or complex datasets; performance-optimization needs. | We complete the processing and continue once resolved. |
| D402 | System or tool limitations | Software or infrastructure limits affected production timelines. | Performance constraints; temporary service interruptions. | We mitigate the issue and resume once systems are fully operational. |
| D403 | Rework due to technical validation | Internal validation/QAQC surfaced issues that needed corrective modeling. | Detected inconsistencies; non-compliance with internal standards. | We address the issues and revalidate deliverables before release. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D501 | Extended internal QAQC | Extra quality-control cycles were needed to meet delivery standards. | Complex scopes; high-accuracy requirements. | We complete QAQC and proceed with delivery once approved. |
| D502 | Internal clarification or review dependency | Production needed an internal review or expert validation first. | Complex modeling decisions; discipline-specific validation. | We complete the reviews and continue production. |
| D503 | Issue resolution during validation | Inconsistencies needed resolving before final delivery. | Conflicting interpretations; model-consistency adjustments. | We resolve the issues and finalize the deliverables. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D601 | Production capacity constraints | Order volume or resource availability temporarily affected timelines. | High order volume; resource constraints (e.g., holidays). | We rebalance workload and proceed as capacity allows. |
| D602 | Resource allocation adjustments | Scheduling was adjusted for prioritization or workload balancing. | Parallel critical projects; scheduling optimization. | We update timelines and continue production accordingly. |
| D603 | Dependency on specialized resources | Delivery depended on the availability of specialized expertise. | Complex MEP or Site requirements; advanced coordination needs. | We allocate specialized resources as soon as available. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D701 | Third-party dependency | Progress depended on inputs or actions from external parties. | External data providers; upstream services. | We follow up with the relevant parties and resume once resolved. |
| D702 | Client response delay | We're awaiting clarification, confirmation, or input from you. | Open questions; pending approvals. | We proceed as soon as we receive your response. |
| D703 | Upstream data dependency | Production depended on data generated by another workflow or stage. | Scan-processing stages; prior deliverables. | We continue once the upstream data is finalized. |
| Code | Reason | What it means | Common causes | What happens next |
|---|---|---|---|---|
| D801 | Unforeseen project conditions | Unexpected conditions appeared that couldn't be anticipated at the start. | Unusual building conditions; data anomalies. | We assess the impact and adjust production plans accordingly. |
| D802 | Data interpretation limitations | Some elements needed conservative interpretation to ensure model reliability. | Limited visibility; ambiguous elements. | We apply standard assumptions and document decisions as needed. |
| D803 | Risk mitigation measures applied | Extra measures were taken to ensure accuracy or consistency of deliverables. | High-risk areas; critical coordination elements. | We complete the mitigation steps and proceed with delivery. |
If your order is delayed, you can always reach our Support Team at support@integratedprojects.co for a status update.
| We coordinate internally to ensure consistency before delivery. |