The menus

The menu bar is the whole application. Each menu opens a short list of overview pages, and the two that matter most — Dashboard and Documents — are pages themselves rather than lists.

1 Click a menu to open it; the underline shows where you are. 2 Each item is one overview page. 3 The … holds whatever does not fit on a narrow window.

Configuration — the physical ship.

Configuration — the physical ship.

What is behind each one

Read off a running document-control workspace. Your installation may carry other workspace types with other menus — see the last section.

Menu	Items	What it is
Dashboard	My open comments	what you raised that nobody has settled yet
Documents	the register	every document, with its current revision
Configuration	Zones, Spaces, Equipment, Decks	the physical ship: where things are
Definition	Cost codes, Documents	what the work is broken down into, and the register again
Management	Organisations, Disciplines, Persons, Project roles	who is involved
Communication	Transmittals, Comments	what went out, and what came back
Knowledge base	Document types, and the other lists everything else points at	the definitions
Imports	Import new nodes, relationships, files; update existing	bringing data in in bulk

Three of them group naturally, and the grouping is worth more than the list:

• Configuration is the ship — decks, areas, spaces, zones, and the equipment in them. It is what inspection reports and comments are filed against.
• Definition describes the work — the cost codes the project is broken down into, and the documents that say what is to be done.
• Management organises the people — the organisations, their roles, the persons and their disciplines.

Everything else hangs off those: Communication is the conversation about records that exist; the Dashboard is your slice of it; Imports is how a few hundred records arrive at once.

On a narrower window the last menus move behind the …. Nothing is missing; it has moved.

On a narrower window the last menus move behind the …. Nothing is missing; it has moved.

The Knowledge base is powerful and dangerous

It holds the lists the rest of the workspace is written in terms of — what a document type is, what an equipment type is. Records elsewhere point at those entries, so a change here is not a local edit: it changes what existing records say, everywhere, without any of them being touched. Read freely. Change nothing unless changing it is your job.

Two routes to the register

Documents is on the bar in its own right and under Definition. They are the same page — the register is used so often it earned a top-level spot, and the older route was kept so that instructions written for it still work.

Other workspaces, other menus

A workspace’s type decides which records exist and therefore what is on the bar. A project workspace has Systems and Cables under Configuration and Requirements under Definition; a document-control workspace has none of them and puts its weight on documents, revisions, transmittals and comments. Neither is broken. When something is genuinely not there, the useful question is which workspace you are in, not which menu you missed.