The ADES Delivery System
Defined scope. Structured review. Clear handoff.
Every ADES assignment moves through a documented workflow, from agreed requirements to a reviewed, versioned release. You receive the deliverable, and visibility into the review behind it.
- Agreed scope and deliverables
- Client BIM requirements and standards
- Drawings, models and point-cloud data
- Software, coordinates and project setup
- Requirements and model setup
- Production and coordination
- Independent quality review
- Controlled release and handoff
- Reviewed project model
- Documented issues and resolutions
- Completed quality-control record
- Versioned delivery package
Requirements first
Requirements first, production second.
Four groups of inputs are reviewed before any modeling begins.
Modeling · Coordination · Documentation
Model structure · submission requirements
Point clouds · equipment information
Coordinates · linked models · project templates
Anything missing is logged in the requirements register, never assumed.
The workflow
Six stages. Six records.
Select a stage to see its checks and the record it produces.
Requirements
Scope, standards and inputs are agreed and anything missing is logged before production.
Checks
- Scope confirmed
- Standards identified
- Missing information logged
Record produced
Requirements register
Model Setup
The project environment is configured and verified so the model starts on the right footing.
Checks
- Coordinates verified
- Links validated
- Project environment configured
Record produced
Setup checks
Production
The model is developed to the agreed standards and self-checked by the modeler.
Checks
- Model developed
- Standards followed
- Self-check performed
Record produced
Production review
Coordination
Interferences and clearances are reviewed and every issue is documented.
Checks
- Interferences reviewed
- Clearances checked
- Issues documented
Record produced
Issue register
Independent QC
A separate reviewer checks the model against the requirements and confirms corrections.
Checks
- Model reviewed
- Requirements verified
- Corrections confirmed
Record produced
QC record
The modeler may perform the first check. Final release requires a separate review.
Release
Open items and the version are recorded, and the package is approved for handoff.
Checks
- Open items recorded
- Version documented
- Package approved
Record produced
Release record
What you receive
The deliverable, and the review behind it.
Reviewed Model
Current coordinated model package, prepared against the agreed project requirements.
Issue Record
Open issues, closed issues and approved exceptions.
QC Record
Checks performed, reviewer identified and status documented.
Versioned Delivery
Package ID, revision, submission date and release status.
QA/QC system
Structured checks. Documented review. Repeatable quality.
Every review combines your project-specific requirements with ADES baseline quality checks. Select an area to see what is checked.
Review methods
Review status
Pass: requirement satisfied. Fail: correction required. Open: pending action or information. N/A: not applicable. Exception: reviewed deviation.
| Category | Check | Method | Status |
|---|---|---|---|
| Setup | Shared coordinates verified | Visual | Pass |
| Mechanical | Equipment access verified | Technical | Pass |
| Electrical | Panel working clearance checked | Technical | Pass |
| Plumbing | Required pipe slopes verified | Technical | Pass |
| Coordination | Major hard clashes reviewed | Coordination | Open |
| Documentation | View naming meets standard | Visual | Pass |
Automated validation
Automate the deterministic. Review what requires judgment.
Rule-based Revit and Dynamo workflows support repetitive QA/QC checks, so technical reviewers can focus on decisions that need professional judgment.
What can be rule-based
- Naming, parameters and potential duplicates
- Model structure, defined geometry and required data
What remains human-reviewed
- Constructability and equipment serviceability
- Routing practicality, design intent and accepted exceptions
Issue control and release
Identify. Resolve. Verify. Release.
Coordination and quality issues are recorded, assigned, reviewed through closure, and reflected in the deliverable's release status.
Identified
QA/QC, validation or review
Classified
Type, priority and action
Assigned
Owner, reference, review point
Corrected
Model or information updated
Rechecked
Correction verified
Closed
Closure or accepted exception
Items that fail the recheck return to Corrected. Further action is required before they can close.
Corrected does not mean closed.
Release conditions
- No unresolved critical issue
- Required QC completed
- Outstanding major items assessed and documented
- Accepted exceptions recorded
- Current package and revision identified
- Reviewer approval recorded
| Field | Record |
|---|---|
| Project / package | — |
| Package ID / revision | — |
| Submission date | — |
| QC review | To be recorded |
| Open items / exceptions | To be recorded |
| Prepared by / reviewed by | — |
| ID | Discipline | Issue | Priority | Owner | Status |
|---|---|---|---|---|---|
| CI-021 | Mechanical | Duct / beam conflict | Major | ADES | Closed |
| CI-022 | Plumbing | Drain slope conflict | Major | ADES | Recheck |
| CI-023 | Electrical | Panel clearance | Major | Client / GC | Open |
| CI-024 | Mechanical | Access-zone review | Minor | ADES | Closed |
| CI-025 | Coordination | Penetration pending | Major | Design team | Open |
| CI-026 | Model | View naming | Minor | ADES | Exception |
Get started
Start small. Prove the fit. Then scale.
Begin with one equipment room model or one coordination review cycle, scoped and priced up front.