Stop Splitting Designs Across Pages in E3.series: Use Fields to Group Data on a Single Sheet

Engineers often split a design across extra sheets just to keep functional areas separate. That creates more documents to manage, more places for data to drift, and more room for errors during reviews and manufacturing. In E3.series you can keep related but distinct areas on the same page and stay consistent by using Fields.

Who this helps

• Electrical engineers who need to document to systems or areas on one page
• Harness and panel teams who want clean separation without extra sheets
• Reviewers who need a single source of truth with accurate inheritance

The core problem

Without a formal way to group on one sheet, teams use free text and manual notes. Devices pick up the wrong context, title blocks get out of sync, and reports do not reflect intent. Rework shows up late during build prep.

What are Fields in E3.series

A Field is a defined region on a sheet that carries its own context. Devices placed inside the region inherit the Field’s high level assignment and location. Devices placed outside inherit the sheet’s assignment and location. The result is two or more clean groups on the same drawing with correct inheritance.

When to use sheet assignment vs Field regions vs device scope

• Project properties set global information that everything should inherit
• Sheet assignment sets the default context for that page
• Field regions define exceptions on that page for a second group
• Device or object properties are for genuine one off requirements

Step by step: single sheet, two clean groups

1. Set the sheet assignment. Give the page its default high level assignment, for example LCH.
2. Place a device. Confirm it inherits the sheet assignment in the device tree.
3. Insert a Field region. Draw the region and name it to reflect intent.
4. Assign the Field. Set the Field’s high level assignment, for example ENG.
5. Place devices inside the Field. Verify they now belong to ENG while the rest of the page remains LCH.
6. Apply placement rules. Use the placement behavior so symbols belong to the correct group when moved or copied.

Why this approach works

• Consistency. Inheritance flows from project to sheet to Field to device
• Fewer sheets. Reduce pagination while keeping groups logically separate
• Cleaner outputs. Reports, PDFs, and downstream consumers see the right context by design

Common pitfalls and how to avoid them

• Free text labels. Replace stray text with properties that flow to reports and title blocks
• Renaming at symbol level. Rename the device in the device tree or device properties so every view stays aligned
• Fields without assignment. Always set the Field’s high level assignment or you will not get the separation you expect

Quick FAQ

Can I mix more than two groups on a page
Yes. Use multiple Field regions, each with its assignment. Keep regions visually clear and non overlapping.

Do title blocks update from Fields
Title blocks pull from project and sheet scope. Use Fields for device grouping and use sheet properties for title block data.

Will reports and PDFs respect Fields
Yes. Devices inherit from the Field or sheet, which drives filters and grouping in reports and makes PDF navigation clearer.

Watch the chapter video

This chapter walks through sheet setup, creating a Field, assigning the Field, placing devices inside it, and the placement rules that control behavior.