<BACK TO TRAINING & SOP CATEGORIES
SOP - DESIGN - REWORK
4801 N UNIVERSITY AVE SUITE 900
PROVO, UTAH 84604
888-781-7074 | IONSOLAR.COM
Date of Last Update: 8/18/2023 - Daniel Cano
PURPOSE: The purpose of this Standard Operating Procedure (SOP) is to outline the process and guidelines for handling design revisions in order to ensure consistency, accuracy, and effective communication throughout the rework process. This SOP provides a structured approach to address rework requests and maintain updated design documents.
WORK QUEUE REPORT:
DESIGN - Ready for Final Design
Order of priority:
Redesigns
Projects returning into your queue from Re-Surveys, PSR & PER
New Designs
TRAINING MATERIALS:
SLA EXPECTATIONS:
Rework: 1 business day SLA from time of assignment
CHECKLIST OF STEPS:
Submission of Rework Requests
Address Rework Notes
Document Creation of Rework
Document Name Convention
Archiving Old Versions
System Updates
Completion of Rework
PLEASE NOTE: YOU ARE ONLY REQUIRED TO COMPLETE ITEMS ASKED OF YOU AS PART OF THE REDESIGN/REVISION REQUEST. IF YOU NOTICE OTHER THINGS THAT ARE INCORRECT ALONG THE WAY PLEASE UPDATE THOSE, HOWEVER, YOU ARE NOT REQUIRED TO FULLY WHITE GLOVE EACH REDESIGN/REVISION. ANY ERRORS THAT ARE ASSIGNED TO YOU THAT WERE NOT DUE TO AN INITIAL MISTAKE YOU MADE AND WERE NOT INCLUDED AS PART OF THE REDESIGN/REVISION REQUEST ARE FULLY DISPUTABLE.
If the rework request is made more than 30 days after the last design, a new tool must be used.
DETAILED STEP BY STEP:
Step 1: Submission of Revision Requests
Design revision requests are submitted through the designated channel or platform.
All revision requests and their associated details are made accessible under the "design" section of the design tab.
Step 2: Addressing Revision Notes
Upon receiving a revision request, the assigned personnel reviews and comprehends the provided revision notes.
The design team analyzes the revision notes to understand the required changes.
The team formulates a plan to address the revision notes within the established design process.
The team will REV CLOUD all required changes unless design tool says otherwise
Step 3: Document Creation for Revisions
For each revision, the design team creates or updates the necessary deliverable documents based on the revision notes.
The team ensures that all relevant design documents, such as shade reports and engineering letters, are republished or re-uploaded.
Step 4: Document Naming Convention
New design documents are saved using the standardized naming convention.
The suffix "REV A" is added to the document name, and the revision letter is incremented for each subsequent revision (e.g., DocumentName_REV A, DocumentName_REV B).
Step 5: Archiving Old Versions
Before marking revisions as completed, the design team archives previous versions of design documents.
Archived versions are stored in a designated location for future reference and auditing purposes.
Step 6: System Updates
All relevant inputs in the Salesforce system are updated to reflect the latest revision information.
Special equipment, scope of work, and other pertinent details are updated as needed.
Step 7: Completion of Revisions
Revisions are marked as completed in the system when the "revision completed/created" date is recorded.
This signifies the conclusion of the revision process for a particular design iteration.
<BACK TO TRAINING & SOP CATEGORIES
SOP – ELECTRICAL REVIEW
When to request an Electrical Review:
Determine the scope of work (SOW) and get a second opinion from a design supervisor.
When determining the SOW for a derate/add-in or a subpanel insert, use the Main Breaker Derate/Add-in SOW Tool.
When determining the SOW for anything else, use extreme detail as to why you think an Electrical Review is required.
Once the supervisor has reviewed all the electrical photos from the site survey and any other data, approval can be given.
Project Assistance (PA)
In the Qualify Design step, mark that the account requires an Electrical Review.
Put a random name or account in as the electrical engineer until this is fixed in PA.
Complete the project note.
Go back into the Design Tab in Salesforce and delete the electrical engineer.
Save and close all your documents.
Start a new design.
Electrical Review
The account will go to the Electrical Review team who will determine the SOW.
They will create a Special Services (SPS) Object
They will complete the review through PA to ensure all fields are completed.
Designer
Once the Electrical Review is completed, read the project note and the SPS Object for the SOW.
Verify the SOW matches the information from the site survey and all AHJ/Utility requirements are met.
Apply the SOW to your design.
Add the SOW to the Electrical Notes on the design tool Cover Sheet.
If the SOW is a subpanel insert or main breaker derate/add-in, ensure the bill of materials (BOM) matches the BOM from the Electrical Review.
Select the same SOW from the Electrical Review to the Electrical Condition on the customer fd.
Required Ancillary Construction Work
The Electrical Review team will fill this out through PA.
The designer must verify this was done correctly.
Special Installation Ticket Items
The Electrical Review team will fill this out through PA.
The designer must verify this was done correctly.
Example note for the scope of work:
MAIN BREAKER DERATE REQUIRED
(EXISTING SERVICE 225A)
The main service panel cannot accommodate the backfeed of the PV system. A supply-side tap interconnection under NEC 705.11 is not an option due to existing field conditions and will not work with the configuration of the electrical system. In order to increase the allowed backfeed, the existing main breaker will need to be downsized with a new 200A main disconnect to comply with load-side interconnections and backfeed requirements under NEC 705.12. Load calculations were completed to ensure the new service size will be adequate for the existing load demand. A meter pull will be required to complete the necessary work.
MATERIALS REQUIRED: EATON CSR2200 200A/2P Main Breaker, Bolt-On, 22kAIC