PVCAD AutoCAD PV Design Workflow: A Practical Guide

A PVCAD AutoCAD PV design workflow can produce a convincing drawing before the project is ready to issue. The array fits. Strings connect. A single-line diagram appears. Yet the roof dimensions may still be preliminary, equipment may still be a placeholder, and nobody may own the unresolved structural questions. The drawing can look finished before the engineering is finished.

Direct answer. A controlled PVCAD workflow moves through seven stages: environment check, input freeze, drawing setup, site definition, mechanical layout, electrical layout, and issue review. PVCAD can automate module placement, stringing, calculations, SLD creation, and exports inside AutoCAD. A designer must still verify source geometry, project rules, equipment, calculations, and each deliverable before release.

This guide is for the EPC manager deciding how PVCAD fits into a working design team. It follows the current PVComplete documentation, then adds the handoff controls that software instructions rarely cover. The aim is a reviewable package, not a fast screenshot.

What does the PVCAD AutoCAD PV design workflow do?

PVCAD adds solar-specific project, layout, electrical, and reporting functions to an AutoCAD drawing environment. A designer can define a site, place modules, add electrical equipment, build strings, create a single-line diagram, and produce downstream exports. The result remains a CAD workflow, with model space, drawing objects, templates, layers, and sheets that still need disciplined review.

PVComplete positions PVCAD for distributed-generation projects. Its current PVCAD product page lists rooftop, carport, and ground-mount use cases for residential and commercial projects. It also lists automated layout, stringing, single-line diagram creation, bill-of-materials output, PVSyst export, and KML export.

The key word is workflow. PVCAD does not turn a weak input pack into a reliable design. It moves selected design information through one CAD environment. That can remove repeated drafting and data entry when the drawing setup is sound. It can also spread a bad assumption across several sheets when the setup is wrong.

PVCAD object or function	What it carries	What a reviewer still checks
Project properties	Client, site, system, and sheet data	Source, revision, spelling, units, and project status
Site objects	Roofs, installation areas, setbacks, obstructions	Survey match, height, access, and jurisdiction basis
Mechanical layout	Modules, mounting, orientation, spacing, subarrays	Buildability, access, structure, and equipment status
Electrical layout	Inverters, strings, combiners, panels, conductors	Ratings, topology, protection, and project rules
SLD output	Connected electrical representation and calculations	Design basis, labels, notes, fault duties, and issue scope
Reports and exports	BOM, PVSyst scene, KML, shading, energy output	Completeness, receiving-tool settings, and revision control

Where does PVCAD fit in the solar design stack?

PVCAD sits between early site modelling and the final drawing package. Browser tools can help a team test site capacity or create an early layout. PVCAD brings that information into a CAD-controlled process. PVSyst may then receive the geometry for energy analysis, while the permit or construction package continues through technical review and sheet production.

PVComplete makes this stage distinction in its product FAQ. The vendor describes PVSketch as a browser tool for early layouts and PVCAD as an AutoCAD-based tool for later engineering and plan-set work. That is a vendor description, not an independent ranking, but it is useful for assigning each file to the right stage.

For a typical C&I rooftop, the sequence may look like this:

1. Sales or pre-design establishes a site boundary and preliminary capacity.
2. A survey, roof plan, imagery, and electrical information become the controlled input pack.
3. PVCAD receives the location, geometry, objects, equipment, and design settings.
4. The designer develops mechanical and electrical layouts in the CAD model.
5. Selected geometry moves to PVsyst for a separate energy model.
6. Reviewed drawings, calculations, schedules, and notes form the issue package.

This is why a PVCAD evaluation should not begin with a feature checklist. Begin with the handoff. Decide what enters the model, what leaves it, and who approves each output. Our solar design file formats guide explains the DWG, DXF, KML, and model-file boundaries that often cause trouble between teams.

PVCAD also does not replace every AutoCAD tool. A team with mature block libraries may keep plain drafting for some projects. A team focused on electrical schematics may compare the product against the workflows in our AutoCAD Electrical versus AutoCAD SLD guide. The best stack depends on project volume, drawing depth, and the number of handoffs.

What must be ready before a PVCAD project starts?

Start with the workstation and the project evidence, not the array. PVCAD needs a supported Windows and AutoCAD environment, then a controlled set of site, equipment, and drawing inputs. If either side is uncertain, record the uncertainty before modelling. No blank field becomes an assumption by accident.

PVComplete updated its access and installation guide on June 10, 2025. It lists an x64 processor, 64-bit Windows 10 or 11, 8 GB RAM, a 1280 by 800 display, and Microsoft Excel. The same page recommends 16 GB RAM. Confirm the current requirements before purchase because supported versions can change.

The standard plug-in path requires a full AutoCAD license. PVComplete also sells a bundle with an OEM AutoCAD environment for teams without full AutoCAD or using AutoCAD LT. The vendor notes that this bundle limits other plug-ins. Check the current installer against your AutoCAD version before rollout.

AutoCAD knowledge still matters. PVComplete links users to Autodesk’s Hitchhiker’s Guide to AutoCAD Basics. A new user should understand model space, polylines, layers, units, blocks, layouts, plotting, and object selection before learning PVCAD commands.

The project input pack should contain the best available version of each item below.

Input	Preferred source	Release question
Site location	Verified coordinates and current address	Do the map pin, parcel, and project name agree?
Base geometry	Survey, measured roof plan, or controlled DWG	Which dimensions are measured and which are traced?
Roof and site objects	Plans, sections, photographs, and field notes	Are height and position known?
Design criteria	Project brief and applicable authority documents	Which criteria apply to this project and issue stage?
Equipment	Approved or clearly marked preliminary data sheets	Is each model fixed, approved equal, or placeholder?
Electrical source	Existing SLD, service data, and point-of-connection evidence	Has the tie-in information been verified?
Drawing standard	Approved DWT, title block, layer rules, and sheet list	Which revision controls the project?

Stage 1: Set the template, units, and location

Project setup controls every later output. Choose the template, drawing units, location, and project properties before placing objects. PVComplete warns that some settings cannot be changed mid-design. A late unit correction can move geometry, damage an export, or force a clean rebuild.

The official project guide, updated August 18, 2025, describes PVCAD DWT templates and linked Excel files. It also allows teams to modify templates for their drawing standard. Treat that flexibility as a controlled configuration task, not casual editing.

Use this setup order:

1. Open the approved DWT template for the project type.
2. Confirm model-space units with the AutoCAD UNITS command.
3. Set the project location by map, KML, KMZ, imagery, or controlled CAD geometry.
4. Keep the georeference near the drawing origin when the workflow requires PVSyst export.
5. Load and assign project properties to the intended title-block fields.
6. Save a clean baseline before site objects or equipment are added.

The project guide specifically warns users to match units and place the georeference close to the AutoCAD origin. It links those choices to later PVSyst export behavior. That warning deserves an early checklist item because a scale problem may remain hidden until another tool receives the geometry.

Test the title block before production. Change a non-critical project property, regenerate the linked field, and confirm the correct sheet changes. Also test the plot style, page size, revision area, and file-naming convention. A template is ready only after the full issue path works.

Stage 2: Define site objects from verified geometry

PVCAD site objects turn CAD geometry into design inputs. A roof outline, installation area, carport, ground-mount area, setback, or obstruction gains meaning only after the designer assigns its type and properties. The object definition is therefore a technical decision, not a drawing shortcut.

PVComplete’s site-object guide, updated August 18, 2025, starts with a closed polyline. The user then selects an object type, sets its properties, and defines it. Relevant properties include height and setbacks. Those values later influence layout and analysis.

Work from large geometry to small geometry. Start with the roof or site boundary. Add separate installation areas for different roof faces, mounting types, or design conditions. Then add obstructions, access areas, and exclusion zones. Do not trace every visible object before deciding whether it affects layout, shading, access, or construction.

Give each object a verification state in a layer, property, or review register:

• Verified: supported by survey, measured drawing, or approved project record.
• Project assumption: directed by the project team and visible in the issue notes.
• Image-derived: traced from current imagery but not field measured.
• Open: location or dimension remains unresolved and blocks release.

This status system keeps visual precision from masquerading as evidence. A closed polyline can look exact to several decimal places even when it came from a low-resolution image. The file should tell the next reviewer how the geometry was obtained.

Check height inputs with the same care as plan dimensions. An obstruction can sit in the correct location but cast the wrong shadow because its height is wrong. A parapet can remove useful area or change row performance. A roof plane can appear continuous even though drawings show a level change.

Stage exit gate: every layout-driving object has a named source, verification state, and owner for any open dimension.

Stage 3: Build a mechanical layout that can be reviewed

Mechanical layout sets modules, mounting, orientation, spacing, and subarray behavior. PVCAD can fill an installation area automatically or let the designer place modules with click-and-drag control. Either method produces a candidate layout, not a construction decision.

The official mechanical-layout guide describes equipment selection, user-defined mounting inputs, subarrays, automated layout, and manual placement. It also lets a user add local equipment when the database lacks the required model. Verify the current data against the approved manufacturer sheet before release.

Start with one representative installation area. Set the module and mounting assumptions, then generate a small layout. Review module dimensions, orientation, spacing, azimuth, setbacks, and the interaction with nearby objects. Only then apply the approach to the full project.

An automated fill usually needs editing. Remove isolated modules that create awkward strings or access. Break large areas into subarrays when equipment, orientation, or mounting changes. Keep row and block logic visible enough that another designer can audit it without reverse engineering the model.

Use the layout review to answer four questions:

1. Does every module sit inside a verified installation area?
2. Do access and maintenance zones remain open?
3. Can the layout be grouped into sensible strings and inverter sections?
4. Which structural or field conditions still need a separate check?

The software can carry mounting and spacing inputs. It cannot know an unentered roof condition or owner constraint. It also cannot approve roof capacity. For detailed rooftop work, connect the CAD model to a defined rooftop engineering scope before anyone treats the module count as final.

Stage exit gate: the layout survives a geometry review, an access review, an equipment review, and a handoff review for the electrical designer.

Stage 4: Connect stringing, equipment, and the SLD

PVCAD’s electrical stage links the array to inverters, combiner boxes, panels, conductors, and the single-line diagram. The software supports automatic, directional, and manual stringing. A clean result depends on the electrical settings and equipment data established before the command runs.

PVComplete’s electrical-layout documentation, updated August 18, 2025, covers inverter placement, module-level power electronics, rapid-shutdown devices, combiner boxes, panels, strings, and circuit conductors. Its quick-start guide says the generated SLD includes voltage-drop and current calculations.

Use a controlled sequence:

1. Confirm inverter type, phase, equipment model, and electrical-code setting.
2. Check the project temperature assumptions and string limits outside the drawing.
3. Place inverters, combiners, AC panels, and the main panel in logical locations.
4. Create one representative string and inspect its module count and route.
5. Apply the selected stringing method to the remaining subarray.
6. Connect source, output, and AC circuits in the intended topology.
7. Generate the SLD only after the model connections have been reviewed.

Treat automatic stringing as a first pass. Direction changes, roof breaks, equipment grouping, routing, and maintenance access may require manual changes. Verify string voltage with the project’s selected module data and design temperatures. Check string sizing, conductor ampacity, and voltage drop against the governing project basis.

The generated SLD needs a drawing review. Confirm equipment identifiers, quantities, ratings, conductor notes, protection devices, grounding and bonding information, point of connection, calculation references, and revision status. The exact content depends on the project and authority. Verify requirements with the applicable AHJ, utility, and project engineer.

Stage 5: Export a package the next person can use

PVCAD can create several outputs from one project model, but each output serves a different reviewer. The BOM supports quantity review. The PVSyst export supports a separate energy model. KML supports geographic review. Shading and energy reports support design comparison. Drawing sheets support permit, construction, or internal issue stages.

The official summary and reports guide lists BOM, PVSyst, KML, energy, and shading outputs. The product page also lists design-version comparison and plan-set preparation.

Build the export register before pressing the buttons.

Output	Receiving task	Minimum release check	Owner
Native DWG	CAD review and sheet production	Units, references, layers, model health, revision	CAD lead
PDF plan set	Formal review or submission	Sheet list, plot scale, title blocks, legibility, issue status	Project lead
BOM spreadsheet	Procurement or estimate review	Equipment mapping, quantities, units, exclusions	Design plus procurement
PVSyst scene	Energy-model setup	Scale, orientation, object geometry, model assumptions	Energy modeller
KML	Geographic review	Coordinates, rotation, site boundary, privacy	Project lead
Shading or energy output	Design comparison	Input basis, model state, date, limitations	Energy modeller

Do not call these files a package simply because they share a folder. Add a transmittal or issue register. State the project, model revision, source revision, purpose, included files, exclusions, open items, and required next review. The receiving team should know whether a file is for feasibility, permit coordination, construction, or as-built work.

File names should carry stable identifiers. A useful pattern includes project code, discipline, document type, revision, and issue date. Avoid names such as final, final2, or latest. The revision register should decide which file controls.

At this point, a sample solar design package can help a team compare expected sheet depth and schedules. Use samples as format references, not as project criteria.

The Drawing-to-Issue Gate for PVCAD projects

The Drawing-to-Issue Gate is a six-check release method for any PVCAD package. It asks whether the drawing can be trusted outside the designer’s workstation. Each check has an owner and a visible result. A failed check returns the model to the relevant stage instead of creating a vague review comment.

1. Source check. Confirm that the location, geometry, equipment, and project criteria point to controlled source records.
2. Model check. Confirm units, origin, object types, layers, subarrays, connections, and drawing health.
3. Engineering check. Review mechanical and electrical decisions against the project basis and applicable jurisdiction.
4. Cross-output check. Compare DWG, SLD, BOM, PVSyst export, KML, and PDF data for consistency.
5. Issue check. Confirm sheet list, title blocks, revision, purpose, exclusions, and open items.
6. Handoff check. Name the recipient, next decision, required response, and controlling file set.

Use a simple red, amber, or green status for each check. Red blocks issue. Amber needs a named exception approved by the project owner. Green records the reviewer and date. The color is not the control. The evidence beside it is.

This gate also makes revisions cheaper. If a module changes, the team knows which checks return to red. Equipment data, string limits, layout fit, SLD labels, BOM quantities, and energy-model inputs may all need review. The whole package does not need a blind restart.

PVCAD versus plain AutoCAD and browser-first tools

PVCAD suits teams that want solar-specific automation without leaving a CAD-controlled drawing process. Plain AutoCAD suits teams with mature standards and custom libraries that do not need the product’s automation. Browser-first tools suit rapid concepts and sales work where full drawing control is not yet required.

Decision factor	PVCAD	Plain AutoCAD	Browser-first solar tool
Solar object automation	Built in for listed PVCAD functions	Team builds blocks, scripts, and standards	Usually built in, with less CAD control
Native CAD editing	Yes, within AutoCAD-based environment	Yes	Often export-based
Mechanical layout	Automated and manual paths	Manual or custom automation	Fast early-stage layout
Electrical workflow	Stringing, equipment, circuits, SLD functions	Manual or custom libraries	Product-dependent
Sheet standard control	Strong with managed templates	Strong with a mature CAD standard	Product-dependent
Learning requirement	AutoCAD plus PVCAD	AutoCAD and team standards	Product interface and export limits
Best fit	Later-stage solar drawings with repeatable CAD outputs	Custom workflows and lower automation needs	Feasibility, sales, and early design

Verdict. Choose PVCAD when solar-specific automation and native CAD control must coexist. Choose plain AutoCAD when your libraries and scripts already cover the work. Choose a browser-first tool for early decisions. The expensive mistake is forcing one tool to own feasibility, detailed design, energy modelling, and permit review without clear handoffs.

Our commercial solar design software guide compares the wider category. The best solar design software guide covers other project types and buying criteria.

What PVCAD cannot decide for the project team

Automation moves drafting work. It does not move accountability. PVCAD can carry a setback value, module model, wire type, or electrical setting. It cannot establish that the value applies to the current project unless the team gives it a sound basis.

Keep these decisions outside the software’s automatic authority:

• Whether the site geometry is accurate enough for the issue stage.
• Whether the roof or support structure can carry the proposed system.
• Which code edition and local amendments apply.
• Which fire-access, utility, zoning, and owner requirements control.
• Whether the equipment selection is approved and available.
• Whether protection, grounding, bonding, and interconnection details are complete.
• Whether the energy model uses the correct weather, loss, and operating assumptions.
• Whether a specific AHJ or utility will accept the package.

PVComplete’s overview uses broad compliance language for several standards. Treat that wording as a vendor statement about product intent. Do not convert it into a promise that a drawing complies with every jurisdiction. Code adoption, local amendments, utility rules, and project conditions vary. Verify them for each issue.

The same discipline applies to energy output. An in-app estimate can support iteration, while a separate model may support another decision. Define the purpose before comparing results. If the project needs a PVSyst study, document the export settings and rebuild checks rather than assuming identical geometry guarantees identical energy results.

How Heaven Designs supports a PVCAD handoff

Heaven Designs can take a verified project brief and develop the drawing package that follows. The useful starting point is the input and output register from this guide. It lets both teams agree on geometry, equipment status, drawing purpose, open items, and the next reviewer before production begins.

• Solar 3D Pre-Design for early site layout, shading, and proposal-stage engineering inputs.
• Solar Rooftop Detailed Engineering for detailed rooftop drawings, electrical documentation, structural coordination, and BOQ work.
• Solar Permit Design for US permit-plan-set support based on project and AHJ requirements.

The service decision comes after the gap is clear. If your team can build the model but lacks review capacity, define a review scope. If input cleanup and drafting are the bottleneck, define the full drawing scope. Use the project contact form to send the project type, location, current files, and required issue stage.

FAQ

Does PVCAD require AutoCAD?

PVCAD needs an AutoCAD-based environment. PVComplete offers a plug-in for teams with full AutoCAD and a bundle containing an OEM AutoCAD environment. The vendor directs teams with AutoCAD LT or no AutoCAD license toward the bundle. Verify current version compatibility and plug-in limits before purchase.

Can PVCAD create a single-line diagram?

Yes. PVComplete documents equipment placement, stringing, circuit connections, and single-line diagram generation. Its quick-start guide says the SLD is accompanied by current and voltage-drop calculations. The generated drawing still needs project-specific review for inputs, topology, labels, protection, grounding, connection details, and authority requirements.

Can PVCAD export a project to PVSyst?

Yes. PVComplete documents a PVSyst export for 3D project geometry and the shading scene. Check drawing units, origin, orientation, object geometry, and receiving-model settings before using the export. The handoff moves geometry. It does not validate the weather data, loss assumptions, equipment model, or energy-study purpose.

Is PVCAD suitable for ground-mount projects?

PVCAD supports ground-mount objects in its distributed-generation workflow. PVComplete recommends PVCAD Mega for larger ground-mounted work and projects needing topography analysis. Treat the product boundary as a current vendor recommendation. Compare the live documentation with project size, terrain, tracker, pier, electrical, and deliverable needs.

Does PVCAD replace an electrical or structural engineer?

No. PVCAD automates selected drawing, layout, calculation, and reporting tasks. It does not verify the site evidence or accept professional responsibility for the issued design. Qualified reviewers must check the applicable structural, electrical, fire, utility, permitting, and project requirements for the named jurisdiction and issue stage.

What should an EPC test during a PVCAD trial?

Use one representative completed project with known answers. Rebuild its template, site objects, layout, strings, SLD, BOM, and one downstream export. Record setup time, manual corrections, missing equipment, revision behavior, and review findings. A controlled replay reveals workflow fit better than a polished demo on an unfamiliar project.

What is the most common PVCAD workflow mistake?

The most damaging mistake is allowing preliminary geometry or equipment to flow into every output without a visible status. Mark each input as verified, assumed, image-derived, or open. Then apply the Drawing-to-Issue Gate before release. That makes uncertainty reviewable instead of hiding it inside precise-looking CAD objects.