What You Are Building

Every project in GreenVee has two parallel descriptions of the work:

The work plan — the schedule of Segments and Tasks that tells the team how the work gets done.
The technical structure — the physical breakdown of the asset that tells procurement and engineering what is being built.

This section covers the technical structure side. Think of it this way:

“The work plan is the recipe. The technical structure is the dish.”

Both hang off the same Project. Neither is parent or child of the other — they are two lenses on the same endeavour.

Why it matters

Procurement needs to know which goods to order, in what quantities, and where in the plant they will be installed. Engineering needs a shared reference so that everyone means the same thing when they say “inverter cabinet on array 3”. The technical structure is that shared reference.

Without it, purchasing decisions float free — there is no way to trace a purchase order back to a specific location in the finished asset.

Linking a Technical Structure to a project

When you create a new project, the setup dialog includes an optional Technical Structure step. From that same step you can either search for and pick an existing Technical Structure to reuse, or create a brand new one on the spot — just give it a title, and GreenVee seeds it with a root Node to start building from.

This link is not locked in at creation: a project can start with no Technical Structure at all and have one attached later, once the design is ready.

What is in this section

Page	What it covers
Technical Structures	The root object — one per project — and the tree of Nodes beneath it
Nodes and Requirements	What you record on each Node: goods, materials, and spec requirements
Engineering to Procurement	How the technical structure feeds purchasing decisions and creates traceability