The schematic is the connectivity contract
The logical view should make every device, cavity, pin, signal, splice, and wire inspectable. It is where an engineer verifies that the right things are connected and that each connection has the attributes needed for sizing and release.
A useful schematic is addressable: selecting a pin or wire should identify the same object in the other engineering views. That identity is more valuable than a drawing that merely looks tidy.
- Devices and connector cavities have stable identities.
- Signals and wires carry attributes instead of relying on labels alone.
- Unresolved values remain visible for review instead of being silently guessed.
The formboard is the physical build definition
The formboard adds the geometry the schematic cannot express: connector orientation, branch locations, bundle paths, bend intent, measured lengths, covering, and assembly notes. It is not a decorative second canvas; it is a manufacturing view of the same harness.
When a route is edited on the formboard, the resulting length and bundle context should flow back to wire data and release checks. When a pin or wire changes in the schematic, the formboard should make the affected physical route easy to find.
One model removes reconciliation work
Separate files force teams to compare drawings, spreadsheets, and BOMs by hand. A single addressable model makes the relationship explicit: logical connectivity, physical geometry, part choices, and manufacturing outputs are different projections of one definition.
The practical test is simple. Change one wire attribute, then trace the change through the schematic, formboard, wire table, and BOM. If the team has to remember which file to update, the system is still split.
- Select an object once and locate it in every relevant view.
- Review proposed changes before they touch the live model.
- Generate release data from the current revision, not a copied export.