Skip to content
WIREHARNESSSTUDIO

Help center / 01

Help center

Practical guidance for taking a harness from source data to a reviewed manufacturing release.

Start with the project model. Every guide assumes that the schematic, formboard, wires, parts, and BOM stay connected.

Read the engineering blog

Start with a project

Move from source data to an inspectable harness without losing the engineering context behind each connection.

Getting started

Create your first harness project

A short path from an empty workspace to a connected schematic, formboard, and release view.

  1. Open the Studio and choose a project name that matches the assembly or vehicle program.
  2. Create devices, pins, signals, and project standards, or import a CSV or TSV connection sheet.
  3. Review unresolved fields before accepting the imported objects into the project model.
  4. Switch between Schematic, Formboard, and release views to confirm that each object keeps its identity.
Source data

Import a spreadsheet without making it the source of truth

Map columns once, resolve ambiguity, and turn rows into addressable engineering objects.

  1. Prepare a CSV or TSV with stable headers for devices, pins, signals, part numbers, and any known wire attributes.
  2. Map each column to a project field and check the preview for missing or conflicting values.
  3. Resolve ambiguous fields with explicit edits or a copilot proposal that stays pending until reviewed.
  4. Import the validated objects, then continue editing the project model instead of maintaining a second spreadsheet state.

Design and review

Keep electrical intent, physical routing, and engineering review in the same addressable workspace.

Core workflow

Move from schematic to formboard

Use the logical view to verify connectivity, then shape the physical route with real branch and length context.

  1. Verify devices, cavities, pins, signals, and wire identities in Schematic before routing.
  2. Open Formboard to place connectors, branch points, bundles, and route geometry at physical scale.
  3. Edit authored geometry directly; measured lengths and route labels update from the same model.
  4. Use fit view and selection to inspect endpoints, component labels, and branch junctions before release.
Copilot

Use the copilot with review-before-apply

Delegate repetitive harness work while keeping the engineer in control of every project mutation.

  1. Describe the outcome in project language: parts, connections, wire attributes, routing, or release checks.
  2. Read the proposed changes, affected objects, and unresolved assumptions in the review panel.
  3. Approve only the validated proposal you want to apply; pending proposals do not change the live project.
  4. Recheck the resulting schematic, formboard, and release outputs after the change is applied.

Release and collaborate

Prepare manufacturing data from the same model and give every teammate the right level of access.

Release

Prepare manufacturing outputs

Issue wire details, cut lengths, parts, and BOM data only after the project passes its release checks.

  1. Confirm wire colors, gauges, coverings, terminations, bundle membership, and calculated lengths.
  2. Check the formboard for missing endpoints, discontinuous routes, or labels that need engineering attention.
  3. Review the wire table and BOM against the current project revision, not an older exported file.
  4. Export the release package when the model and review notes agree on the build definition.
Collaboration

Invite reviewers and shop-floor viewers

Keep editing authority narrow while making the current harness legible to everyone who needs to build or review it.

  1. Use editor access for people who need to change the project model or approve proposals.
  2. Share reviewer or shop-floor access with teammates who need to inspect the current release.
  3. Keep revision history and project standards with the paid Studio workspace when the team needs private collaboration.
  4. Revoke access or publish a new revision when the build definition changes.

Frequently asked questions

Short answers to the product questions that shape a safe harness workflow.

What can I import into Wire Harness Studio?

You can import structured CSV or TSV connection data, map its columns to project fields, and review unresolved values before creating addressable devices, pins, wires, and terminations.

Does the copilot change my project automatically?

No. The copilot prepares typed, reviewable proposals. An engineer must approve a validated proposal before it changes the project model.

Are schematic and formboard separate projects?

No. Schematic, Formboard, wire data, parts, and BOM outputs are views of one addressable harness model, so a reviewed change can carry through the release workflow.

Can reviewers and shop-floor viewers edit the harness?

Reviewer and shop-floor access is designed for inspection and build context. Editing authority stays with project editors.

Continue in context

Open a complete harness project.

Use the Studio to inspect the model behind these workflows, then bring your own source data into the same release path.

Open the studio