Building Envelope Website vs Project and Commissioning Software: What Should Own What?

Overview

A building-envelope consultancy can use the same project name in several systems.

That is not a problem when each system has a clear responsibility.

The public website/front office should answer:

The technical project stack should answer:

• Who is the prospective client?
• Which building/project?
• Which service do they need?
• What is the proposal deadline?
• What should a consultant review next?
• Which drawings and specifications are current?
• Which field observation belongs to which location?
• Which test was performed?
• Which measurement or image is authoritative?
• Which issue is open?
• Which commissioning requirement applies?
• Which report was approved?
• Which closeout item remains?

What the public website should own

Usually:

Current OneStudio features fit this front-office layer.

• service pages;
• buyer/building pages;
• public project case studies;
• proposal/RFP request;
• ordinary client/contact history;
• genuine consultation booking;
• marketing analytics.

What AEC/project software should own

Usually:

• accepted project;
• project number;
• drawings/specifications;
• revisions;
• submittals;
• RFIs;
• site observations;
• issue logs;
• contract-administration records;
• closeout.

What building-envelope testing/inspection software should own

Depending on the firm's tools:

Atlas Inspections is a current example of why envelope survey evidence benefits from a specialist project record rather than ordinary CRM notes.

• survey area/location;
• photo/thermal imagery;
• annotations;
• measurements;
• weather/test conditions;
• test point;
• finding;
• severity;
• field notes;
• report.

What commissioning software should own

A BECx workflow can include:

Keep that lifecycle in the commissioning/project system.

• commissioning plan;
• design reviews;
• submittal reviews;
• mockups;
• preconstruction meetings;
• observations;
• testing;
• issues;
• responsibilities;
• due dates;
• verification;
• closeout.

Keep the prospect and project separate

One institutional owner can have:

The CRM records the owner relationship.

The project system records each engagement.

• roof portfolio work;
• a new BECx project;
• a facade leak investigation;
• several campuses.

Keep the customer problem statement separate from the finding

Customer:

Water appears at the window head during wind-driven rain.

Technical record:

Preserve both.

• assembly/location;
• observation;
• test setup;
• measurement;
• finding;
• interpretation;
• recommendation.

Keep project intake dates separate from field schedules

The public proposal form may collect:

Those are commercial planning dates.

The accepted project may have:

Use the project system for the operational schedule.

• proposal due date;
• estimated start;
• estimated completion.
• design review deadlines;
• mockup date;
• site-observation dates;
• test dates;
• closeout dates.

Keep drawings controlled

Building-envelope work depends on details and interfaces.

The technical system should own:

Do not use the sales CRM as the authoritative document register.

• drawing revision;
• specification revision;
• submittal;
• reviewed document;
• markups.

Keep field observations structured

An observation may need:

Keep it with the project.

• building/area;
• assembly;
• location;
• photo;
• description;
• responsible party;
• disposition.

Keep test evidence linked to conditions

Envelope testing can depend on:

Do not reduce that evidence to a generic note.

• test method;
• assembly;
• location;
• pressure or water conditions;
• weather;
• instrument;
• image;
• result.

Keep commissioning issues linked to verification

A commissioning issue should preserve:

That is not a marketing task.

• originating review/test/observation;
• responsible party;
• due date;
• response;
• verification;
• closure.

Keep final reports authoritative

Technical deliverables can include:

Use one technical source of truth.

The public CRM can know a deliverable was completed without storing an editable competing copy.

• peer-review letters;
• field reports;
• test reports;
• forensic reports;
• repair design documents;
• commissioning reports;
• closeout documents.

Current specialist products show the boundary

Atlas Inspections currently combines radiometric envelope imagery, measurements, annotations, mobile field capture and branded PDF reports.

General AEC project platforms support controlled project documents, issue tracking and construction workflows.

Commissioning platforms support checklists, verification, issues and closeout.

These systems solve technical delivery problems.

OneStudio solves the public acquisition and ordinary relationship problem.

Use one explicit handoff

Choose:

Building-envelope project accepted into technical delivery

Before handoff:

After handoff:

• website;
• proposal/RFP request;
• ordinary client/contact;
• consultation;
• marketing source.
• technical project;
• documents;
• field observations;
• tests;
• commissioning;
• reports;
• closeout.

Use a source-of-truth matrix

A 30-point buyer test

1. Website and technical systems have explicit roles.
2. Proposal request and accepted project are separate.
3. Client organization and project are separate.
4. Handoff has one explicit trigger.
5. Project number has one owner.
6. Technical scope has one owner.
7. Drawing revision has one owner.
8. Specification revision has one owner.
9. Submittal has one owner.
10. RFI has one owner.
11. Field observation has one owner.
12. Field photo evidence has one owner.
13. Test method has one owner.
14. Test location has one owner.
15. Test measurement has one owner.
16. Test result has one owner.
17. Commissioning plan has one owner.
18. Commissioning issue has one owner.
19. Responsible-party workflow has one owner.
20. Verification/closure has one owner.
21. Contract-administration record has one owner.
22. Final report has one owner.
23. Closeout package has one owner.
24. Public CRM excludes technical measurements.
25. Public CRM excludes controlled drawing revisions.
26. Public reminders are not commissioning due-date control.
27. Booking is not confused with field scheduling.
28. Website URLs can survive project-software changes.
29. Marketing analytics exclude sensitive technical/legal data.
30. Staff can explain the architecture in one sentence.

Give the website the relationship and the project system the professional record

The public layer should make the consultancy easy to evaluate and engage.

The technical layer should make every drawing, observation, test and report traceable.

Explore OneStudio features, compare plans, or review the turnkey website service.

Questions businesses ask