Team and project roles

Who is on this project and what each of them may do. Approval rights are granted explicitly, never inherited.

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

Why

Roles and disciplines are read from the project's membership records. Granting one is validated here and enforced again by the database.

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

On this project

May approve

In the organisation, not on the project

Disciplines represented

Members

Project members
Person	Title	Discipline	Organisation	Project roles	May approve
A. Rahman	Senior Piping Engineer	PIP	member	author, viewer	No
N. Okonkwo	Lead Piping Engineer	PIP	member	checker, viewer	No
S. Lindqvist	Process Authority	PRO	member	reviewer, viewer	No
R. Haddad	Engineering Manager	PRO	member	approver, issuer, viewer	Yes
M. Silva	Instrument Engineer	INS	member	author, checker, viewer	No
T. Adeyemi	Electrical Engineer	ELE	member	author, viewer	No
J. Novak	Commissioning Engineer	COM	member	author, viewer	No
K. Mensah	Organisation Administrator	No engineering discipline	owner	project_admin, viewer	No
D. Farouk	Company Representative	PRO	member	reviewer, viewer	No
ZEMERC Support	Support (elevation required)	No engineering discipline	support	Not on this project	No

The capability matrix

What each role carries. A role is granted one at a time.

Capabilities by role
Role	What it permits	Who holds it
viewer	Read the project	A. Rahman, N. Okonkwo, S. Lindqvist, R. Haddad, M. Silva, T. Adeyemi, J. Novak, K. Mensah, D. Farouk
author	Draft a deliverable	A. Rahman, M. Silva, T. Adeyemi, J. Novak
checker	Perform the independent check	N. Okonkwo, M. Silva
reviewer	Raise and close review comments	S. Lindqvist, D. Farouk
approver	Approve a deliverable for issue	R. Haddad
issuer	Issue a controlled revision	R. Haddad
project_admin	Configure the project and its members	K. Mensah

Approval is not a side effect of membership

Adding somebody to a project grants them nothing. Approver and issuer are separate capabilities, granted by name, because approval of safety-critical content is an act of delegation somebody has to be answerable for.

Grant a role

Disciplines on this project

PROProcess
PIPPiping
ELEElectrical
INSInstrumentation and control
COMCommissioning

Authority without competence

Granting approval or checking authority to somebody with no engineering discipline recorded is refused. It is a real situation - an administrator asked to unblock a deliverable - and the answer is to grant the capability to an engineer, not to the person who happens to be available.