PV8.ai Engineering Handoff | Repowering
Package: 74c8283cf8d1e8d34afe6d3a2d4f182df686cf08081308a45f245f01ab4508ed
Status: CONCEPT_WITH_VERIFICATION_FLAGS

CONCEPT DESIGN - NOT FOR CONSTRUCTION. Functional single-line blocks; no protection coordination, fault-duty, earthing, cable sizing or utility approval is implied.

Actual format availability for this package:
- Concept electrical SLD: INCLUDED — electrical/concept-sld.dxf
- Site DXF / GIS geometry: NOT_INCLUDED — No frozen site geometry; engineering layout and route survey required
- PVsyst project and variants: INCLUDED — pvsyst/PV8_PV8_project.PRJ, pvsyst/PV8_PV8_project.VC0
- CIM16 network exchange: NOT_INCLUDED — Owner network parameters were not supplied. See electrical/cim-readiness.json before requesting network exchange.
- PowerFactory study request and runner: NOT_INCLUDED — No explicit electrical study request was supplied. A licensed PowerFactory project and reconciled object mapping are required.
- Native DWG: NOT_INCLUDED — Native DWG is not generated. Open the included DXF in a compatible CAD application and validate before conversion.
- Native PVcase design: NOT_INCLUDED — Native PVcase objects are not generated. Included site geometry is reference geometry requiring engineering conversion.
File presence is not native software acceptance, engineering approval or a certified design.

CAD: open electrical/concept-sld.dxf in AutoCAD. Each sheet is 320 mm apart in model space. Schematic millimetres; no geographic coordinates. Equipment blocks carry graphical symbols drawn after IEC 60617 (PV array, inverter, transformer, circuit breaker, disconnector, meter, busbar; the legend on the last sheet and in concept-sld-legend.svg also shows earthing, which no block asserts) on layer PV8_EQUIPMENT with their marks; feeders on PV8_FEEDERS, labels on PV8_LABELS. It remains a CONCEPT single-line diagram, not a certified drawing: symbols do not select or rate protection.
Site CAD: when present, layout/frozen-layout.dxf uses the projected metre CRS stated in coordinate-reference.json and frozen-layout.prj. Confirm project CRS before INSERT/attaching it. Never overlay the schematic DXF as site geometry.
PVcase: use site CAD as background/reference geometry in the customer's AutoCAD/PVcase project. It contains no native PVcase tables, stringing or simulation objects. Engineer conversion is required.
AutoCAD: APPLOAD importers/pv8-autocad-import.lsp, run PV8IMPORT and confirm the exact EPSG. This imports native reference layers, polylines and point blocks at metre scale and zero translation; native acceptance testing is required.
Civil 3D: import layout/frozen-layout.landxml. TIN surfaces exist only when explicit owner survey points/faces were provided; line alignments are frozen screening polylines, not surveyed cable designs. Vertical datum is preserved without height transformation.
GIS/PVcase Prospect: use GeoPackage or KML/KMZ. GeoPackage separates semantic layers and preserves geometry IDs and source/status.
QGIS/other GIS: GeoJSON is WGS84 longitude/latitude; use the PRJ only with the DXF.
PVsyst: simulation/source preserves original vendor PAN/OND/BTR/PMP and CSV bytes. Canonical energy-series CSV uses UTC interval bounds, MWh and average MW. Calculation manifest records source checksums and coverage. pvsyst/ holds a PVsyst-format project (.PRJ) and one variant per case (.VC0 as built, .VC1 repowered concept when present) written from PV8 facts: site, orientation (PVsyst azimuth, 0 = south), modules in series, strings, inverters, PAN/OND references and the losses the saved run applied. Values PV8 does not hold are left out and listed as TO_BE_CONFIRMED in pvsyst/mapping.json. Opening the files in PVsyst is an owner check (NOT_VALIDATED_IN_PVSYST). No revised financial results are generated.
PowerFactory/CIM: electrical/network-EQ.xml and network-SSH.xml appear only with explicit owner network parameters. These are a CIM16 EQ/SSH subset, not a validated CGMES dataset. Import/profile mapping and engineering validation in the customer's software remain required; see cim-readiness.json and network-design-basis.json.
Schedules: UTF-8 CSV; blank means unknown, never zero. Equipment IDs and feeder endpoints reconcile to electrical-model.json. Operating kW/kVA/current requirements are not nameplate ratings, breaker settings or cable ampacities. The BOP assembly schedule links frozen catalogue identities to topology roles and leaves procurement ratings open.
Pre-fill: inputs with status ASSET_RECORD were read from the asset record (connection voltage, PCC reference, DSO, DC/AC capacity, export limit, coordinates); evidence-register.csv names each field. Confirm them against the connection agreement and as-built documents.
Strings: schedules/strings.csv lists each documented string (digital twin stringing plan) or, without one, strings per inverter/MPPT from the asset record with an even-split flag; Voc at the design minimum and Vmp at the design maximum cell temperature use the module datasheet coefficients (V(T) = Vstc x (1 + tc/100 x (T - 25))). TO_BE_CONFIRMED marks a gap, never a zero. stringing/ holds one concept diagram per inverter configuration.
BoM: schedules/bill-of-materials.csv gives quantities, units, part numbers where known and the basis per line (RECORDED, TWIN, CATALOGUE, CONCEPT, ESTIMATE with its formula, TO_BE_CONFIRMED). It is a screening inventory, not a procurement list.
Datasheets: datasheets/ holds the PAN/OND files and equipment datasheets already stored for the asset and visible to you, checksum-verified where a checksum was stored (INCLUDED) and marked INCLUDED_UNVERIFIED otherwise; datasheets/register.csv references every candidate by document ID, included or not (size limit, checksum mismatch).
O&M: om/ holds a structured O&M scope (Markdown, PDF, XLSX) after IEC 62446-2 and the SolarPower Europe O&M Best Practices headings, with scope quantities from the asset, twin and BoM. Frequencies and response times are TEMPLATE_DEFAULT values for the O&M contract.
Yield: reports/yield-and-losses.* reorganises the saved run's yield basis, loss tree, P50/P75/P90 and uncertainty components, and names what the run did not model. Nothing is re-simulated; it is not an IE opinion.
Groups: power is equally divided across entered groups; feeder allocation needs engineering review. Data-center 2N paths each carry full duty, not double economic demand; independence and transfer are unverified.
Source: frozen-output.json is a lossless JSON reserialization, whose own checksum appears in manifest.json. source_sha256 identifies the original stored bytes. The frozen decision brief and economics remain on that source basis; handoff inputs do not rerun financial or electrical engines. A changed topology may invalidate the original economics.
Joint dispatch: study/joint-dispatch.json is included only on explicit dispatch request. It is a separate perfect-foresight operating study; frozen economics and the decision brief are unchanged. Infeasible, limited or unavailable solves contain no schedule or investment value.
Document control: archive this ZIP, edit a copy, and return revised DXF and schedules with this package ID. No files are sent to third parties; asset-record values enter only as labelled ASSET_RECORD inputs.

No frozen site geometry; engineering layout and route survey required
Datasheets: no PAN/OND or equipment datasheet is stored for this asset in your scope.
Yield and losses: the saved output holds no yield model; no report was generated.
Design temperatures are PV8 screening defaults; replace with site design temperatures before issue.
