Map a design request to its site, survey, equipment, and production inputs.
Design and proposals / Design versions
Solar design version and equipment option control
Preserve what changed between design options and which technical assumptions support the version selected for a proposal.
Record
01Design request
02Design version
03Design option
04Production assumption
Current reviewCreate a design request
Configured during assessment- 01Create a design requestCurrent decision
- 02Review input evidenceNext controlled handoff
- 03Prepare or receive a design optionNext controlled handoff
- 04Complete technical and equipment reviewNext controlled handoff
Why this workflow breaks
Solar designs may change as survey evidence, equipment availability, production assumptions, and customer preferences evolve. Overwriting a file or provider response breaks the link between the technical option and the commercial proposal.
Solar1 starts by documenting the decisions and failure paths. Configuration follows only after the operating boundary is understood.
Workflow sequence
Keep the handoff visible from first review to accepted outcome.
- 01Create a design request
- 02Review input evidence
- 03Prepare or receive a design option
- 04Complete technical and equipment review
- 05Select, supersede, or revise the version
What to configure
Specific controls, qualified by implementation.
Record normalized outputs and retain a reference to the originating design artifact.
Configure technical review and equipment-mapping decisions for each version.
Lock the selected version while routing later revisions through change control.
Assessment output
A shared definition of the records, owners, and acceptance checks.
Records in scope
- Design request
- Design version
- Design option
- Production assumption
- Equipment mapping
Roles in the decision
- Solar designer
- Design manager
- Equipment reviewer
Checks before rollout
- Identify the source of each design input and output.
- Define version and supersession rules.
- Test provider failure, manual fallback, and repeated responses where applicable.
Questions to settle
Questions to settle before configuring design versions.
Can Solar1 connect to a design provider?+
A provider-specific integration can be assessed, including supported fields, error handling, version behavior, and a manual fallback.
Which design data should be retained?+
Retain the normalized assumptions and approved artifacts needed to reproduce the selected technical and commercial decision.
Can an accepted design be edited?+
Later work should create a controlled revision or change decision instead of erasing the version used for acceptance.
Next step