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.
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 initiator is Field Support.
Partial Work Started is marked.
Solar Work or Electrical Work Complete is filled.
When these triggers occur, you will use the Change Order Tool and select the As-Builts option, which initially mimics the standard Create Design flow.
When an install crew is on-site and cannot build the system as originally designed, they will contact Field Support. Follow the Install Deviation SOP:
Access Aurora: Pull up the customer’s account and refer to the Installation CD to review the original designer's notes.
Duplicate the Design: Duplicate the Final Design model in Aurora and rename it DC@I.
Collect Required Photos: The crew must send photos of the issue.
Chalked Layout: If it doesn't fit, they must chalk the area.
Smaller Roof: Photos with measurements proving it won't fit.
Obstructions: If not obvious, the crew must chalk around the obstruction.
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.
Create Change Order (CO): Once finalized, create a CO for compliance and log the error.
Review Photos: Pull up site survey electrical photos and review the new photos sent by the crew (e.g., interconnection changes, incorrect subpanel details, drywall damage).
Review Proposed Solution: If the solution is reasonable, proceed. If unsure, reach out to leadership.
Create Change Order (CO): Finalize and create the CO.
Once the deviation is approved or the As-Built step is triggered, the Rework SOP dictates how the design is updated.
SLA Expectation: 1.5 hours from the time of claiming the job.
Addressing Notes: Read the revision notes carefully. Formulate a plan and REV CLOUD all required changes (unless the design tool says otherwise).
Document Naming: Save new design deliverables using the standardized suffix. Start with _REV A and increment for subsequent revisions (e.g., DocumentName_REV B).
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 mark the revision as completed in the system.
When updating the DC@I or As-Built model, ensure you are adhering to strict modeling and electrical standards:
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. Maintain a 6" clearance from obstructions and roof edges, plus necessary fire setbacks.
Pitch & Azimuth: Verify the surveyed pitch matches the built array.
Overhead Services: Ensure the design maintains a 3’ working clearance around service drops.
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.