Project settings
Configuration, conventions and retention. Some of these reinterpret documents that have already been read.
Why
A change is compared against what the project currently holds and reported field by field. A submission that changes nothing is refused rather than reported as saved.
Writes are validated against the engineering rules and then refused, because no database has been configured for this environment.
Project
A convention change reinterprets what is already read
The tag grammar as it stands
What this project currently recognises as a tag.
| Asset class | Normalises to | What it matches |
|---|---|---|
| equipment | $1-$2$3 | Equipment: letter prefix, four digits, optional suffix |
| instrument | $1-$2$3 | Instrument: ISA function letters and loop number |
| valve | $1-$2$3 | Valve: function prefix and sequence |
| line | $1-$2-$3-$4-$5 | Line: unit, service, sequence, size, class |
| cable | $1-$2 | Cable: cable prefix and sequence |
| loop | $1-$2-LOOP | Instrument loop |
Retention: blank is not zero
A blank retention period means no policy has been agreed with the client. That is a different state from a policy of deleting immediately, and storing it as zero would make the two indistinguishable - at which point somebody’s drawings get deleted because a field was never filled in.
What is not configurable here
- The project code, which every issued document number carries
- Who may approve, granted per person on the team page
- Confidence ceilings, which are properties of the reading methods