System configuration

Hierarchy types, disciplines, deliverable types and thresholds - and the rules that are not configurable.

Demonstration project - no figure here describes a real facilityChanges are not saved

Why

The catalogues below are the ones the application actually uses. Nothing here is a placeholder list.

Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.

Disciplines

Deliverable types

Hierarchy types

Rules an administrator can weaken

Some things are deliberately not configurable

Raising the OCR confidence ceiling would not make a scan easier to read. It would make every reading from a scan look more trustworthy than it is.

Configurable

Fixed rules
Rule	Why it is fixed
Confidence ceilings per reading method	A property of the method. Raising it changes how trustworthy a reading looks, not how good it is.
The author may not approve their own work	Approval is the point at which somebody becomes answerable.
A disputed value presents no value	A number nobody can stand behind must not reach a deliverable.
Only the reviewer who raised a comment may close it	Otherwise a review is a formality.
A draft watermark cannot be removed before approval	An unapproved document that looks issued is the one most likely to be used as though it were.
Evidence cannot be edited	A reading can be superseded; rewriting one makes the audit trail fiction.

Discipline catalogue
Code	Discipline
PRO	Process
MEC	Mechanical
PIP	Piping
ELE	Electrical
INS	Instrumentation and control
CIV	Civil and structural
CON	Construction
PLN	Planning
CST	Cost
QUA	Quality
HSE	Health, safety and environment
COM	Commissioning
OPS	Operations
MNT	Maintenance
PRC	Procurement
PMG	Project management