As Builts

Explaining the priority scores:

This is a new field on the Project Stage Step object that helps prioritize the queue based on White Glove Treatment status, the number of days since contract execution, and the number of days since the stage became available.

Explanation of what is determined on what is a As-built:

An as-built design is determined once the installation has been confirmed as complete. The Post-Install QA (PIQA) team is responsible for reviewing the completed installation, including auditing site photos and verifying that the required work has been completed.

Once the PIQA team confirms completion, they will enter the Solar Work Complete and Electrical Work Complete dates. After both dates are entered, the Installation Completion Date will automatically populate. This date is what determines that the project is ready for the as-built process if a Change Order (CO) was opened during the installation or identified during the PIQA audit, Compliance will review and process the CO. They will determine whether any rework, plan resubmittals, or financier requirements are needed and will open the appropriate rework items as necessary.

ION Solar: As-Built Training Guide

1. Introduction & Triggers

The As-Built process ensures that our final system designs accurately reflect what was actually installed in the field. This step is crucial for compliance, correct system monitoring, and future service needs.

According to the new As-Built Step framework, an As-Built design rework is triggered when one of the following happens:

Design rework is explicitly requested, and the PA step is As Built step .
Installation complete is marked complete and there is a processed CO.

1.2 Sending it back to the OG designers.

If the revision is determined that it needs to go back to the OG designer then we will do the following
- Consult your team lead or supervisor before sending it back
- Create a new CO stating the reason why it needs to go back to and say that the design PA step need to rejected and reprocessed.
- And in the dropdown of the PA step, select the step as unnecessary.

2. Handling Install Deviations

When an install crew is on-site and cannot build the system as originally designed, they will contact Field Support and follow the Install Deviation SOP:

Layout Deviations

Access Aurora: Pull up the customer’s account and refer to the Installation CD to review the original designer's notes.
Duplicate the Design: If one wasn't made during the field call then duplicate the Final Design model in Aurora and rename it DC@I.
Evaluate the Change:
- Soft Layout Changes (No Manager Approval): Installer preference (easier installation) or shifts within the same roof section.
- Hard Layout Changes (Manager Approval Required - Joe, Ethan, Cam, Sam, or James): Production drops > 5% or increases > 10%, or moving/adding panels to a different roof section.
DXF: Download the dxf file from aurora and import it into the auto-cad file.
- Make sure that new model is properly scaled and meets all the highline requirements.

Electrical Deviations

Review Photos: Pull up installation electrical photos and review them along side the planset/install CD
Update plans as necessary: Make the necessary changes to the excel doc, auto-cad and re-datalink the sheet.
PDF Print: PDF print the plans

3. Completing the As-Built Rework

Once the redesign requested has been processed

SLA Expectation: 1.5 hours from the time of claiming the job (subject to change).
Addressing Redesign request: Read the revision notes carefully. Make the necessary change, double check the installation photos to make sure plans match the install, REV CLOUD all changes (unless the design tool says otherwise) (Name the cloud AB1) and PDF print the updated plan.
Document Naming: Save the a deliverables using the standardized suffix. Start with AB_Revision_1 and increment for subsequent revisions (e.g., [Project name]-AB_Revision_1_[Date])(no special characters).
Archiving: Archive old versions of the design documents in the designated location.
System Updates: Ensure all relevant Salesforce inputs (special equipment, scope of work, etc.) are updated to reflect the revision, and complete the AB PA step.

4. Modeling & Electrical Accuracy

When updating the DC@I or As-Built model, ensure you are adhering to strict modeling and electrical standards:

Aurora Modeling Adjustments

Refer to AURORA BASICS to ensure the final representation is accurate to the real-world build:

Obstructions & Setbacks: Ensure any new vents or obstructions discovered by the crew are modeled accurately. Make sure that we are follow the FSB's
Pitch & Azimuth: Verify the surveyed pitch matches the built array. If there is a discrepancy then match install.
Shade Report: Once all change have been complete then reprint the shade report following the same style of naming conventions.
No changes: If no changes have been made then move on to the next steps.

Electrical Input Updates

If the electrical scope changed on-site, the Design Tool Electrical Inputs in Salesforce must be updated to match the As-Built reality. Ensure accuracy for:

Equipment: Modules and Inverters (if substituted).
Distances: Furthest Array to Combiner Box (ft) and Combiner Box to POI.
Service & Ratings: Existing Main Bus Rating, Main Disconnect Rating, PV Breaker sizes, and any Tandem Breakers required.
Interconnection Method: Ensure the final interconnection method (e.g., Load Side, Supply Side Tap) is correctly documented.

5. Completion and documentation

Once completed and everything is correctly changed, rev clouded, notated and documented. Then we are going to leave the following notes
- AB Criteria

Financing Source: --

Signed Production Estimate: --

Design Change at Install?: --

New Production Estimate: --

Percentage Change: --

One line change?: --

Reason for change: --

Structural Change at Install: --

Reason for Change: --

Redesign request fulfilled? --

Page updated

Report abuse