Professional Documents
Culture Documents
Standard Process Diagrama
Standard Process Diagrama
Specification
For combining Processes and Clauses
To improve Efficiency for Process Auditing and Audit
Reporting, including Triennial Reviews
1.0 Introduction:
This specification has resulted as a result of a perceived change with AB views re clauses
and processes, whilst ensuring that URS remains ahead of the curve re such changes. At
the same time, produce a methodology that systemizes and automates the next level of
detail re reporting and analysis of audit programmes and to assist auditors be consistent in
their approach to reporting across the revised standards.
Cardinal
Function
Control
Functions
Activity
Input Output
Support
Functions
Input Example
Making
Tea
Materials/Information The ingredients to make the Water
output Milk
Tea
Sugar
Cardinal Example
Making
Tea
Risk Assessment RA Precautions such
Monitoring Control Audit system, KPI, to be safe
Corrective Actions Make each time
Resource Human, Energy, to correct taste
Environment, establish Audit of process
system, tools results
Environment Clean, well light Corrective
actions applied
Trained person
Etc.
4.0 Process Diagram Explained ISO 9001 and related schemes Example
Paint Shop:
Input Examples
Support Examples
Functions
Control Examples
Functions
Cardinal Examples
ER allows the clauses set at scheme level to be updated and amended to the client record.
Currently, the system does not allow what is seen at the CMS user level to be shown to the auditor
Objective 1 The auditor to see what the CMS report reviewer sees.
Likewise, the requirement that may take place in the coming months to show clauses applicable to
processes is not covered Objective 2 to link clauses and Processes seen over the 3 year
certification cycle.
Process &/or 4.1 4.2 5.1 6.1 6.2 6.3 7 8.1 8.2 9 9.1
Department
Stores x x
Paint shop x x x x x
Cutting x x x
Welding x x x x x x
Department
P A P A P A P A P A P A
Stores x x x
Paint x x x x x x x
Shop
Cutting x x x x
Welding x x x x x
2. As you can see from the above example, for a reviewer to see that all relevant clauses
have been seen across a process will make for a difficult read and to determine what has
3. Important In addition to the above table of processes to clauses, where the quote has
marked number of shifts, then for ALL fundamental processes the left hand column shall
default into subordinate rows up to 4 in total with the heading shift 1, 2, 3 and 4 but
based on the number of shifts stated in the quote.
Process
Management
Cardinal
Cardinal
Process
Process
Cardinal
Cardinal
Process Process
Process
es s
roc
lP
nta
me
da
Fun
7.0.1 Definitions:
Any process that is required to complete the process links to produce the final product or
service, without such a process the product or service cannot be produced e.g.:
Cutting
Welding
Painting
Purchasing
Stores.
Any process that that can be applied, or act on, one-or-more fundamental processes e.g.:
Calibration
Internal Audits
Corrective Action
Maintenance
RA performed
Other
Process activity that sets the performance and criteria of the Fundamental Processes and
Cardinal Processes e.g.:
KPIs/Objectives
Analysis
Review
Resource/Organization/Environment
Context/Knowledge/Scope/Information.
8.0.1 ER and Process Model Labelling for Read/Write ability and System
Storage Fundamental Processes:
A B
Fundamental Variable
(Painting)
State Shift if
applicable
(6-2.00)
Topic(s) Evidence
Fundamental Variable
(Painting)
State Shift if
applicable
(6-2.00)
Specific
Requirement:
8.0.2 ER and Process Model Labelling for Read/Write ability and System
Storage Cardinal Processes:
C D
Cardinal Variable
(Internal Audit)
Topic(s) Evidence
5.6, 5.7
8.0.3 ER and Process Model Labelling for Read/Write ability and System
Storage Management Processes:
C D
Management Variable
(Policy)
5.8
9.1, 9.2
Notes:
i) Create Table ER If table label is Fundamental Process, then system will now know this
and does count and ties-up Process name which is already a read/write field need to
change current system?
ii) We have a configuration field at scheme level to draw-up a table where clauses are
assigned to a Fundamental Process label, with Element Labels - Input, Support Function,
Control Function, Output. Therefore, for each sub-process element e.g.: Control Functions
there would be a label and that label would have a group of defined clauses attached. See
section Process Diagram and Model for other Standards.
vi) Summary Element (possibly Element Topics) and Clauses are Variable and determined
by the database administrator on scheme set-up.
If we test the model say for the example used above, such as a paint-shop, whilst we know
the model works for 9001 and related matters, the approach for H&S is different, i.e.: we
need to be assured that the process is safe for those working or come in to contact with it
i.e. hazards within the process to persons see Process Diagram Representation 18001
below.
A B
Fundamental Variable
(Paint Shop)
No lifting equipment
9.0 Ensuring the Auditor Maps Processes to the Correct Process Level:
Currently the system allows auditors to add, amend and remove processes via ER and
update CMS and vice versa.
However, the format will not allow the above structured methodology to work if we place
a new table which is broken down in to the three tier system (Fundamental, Cardinal and
Management), we could, I hope, enable the system to recognise the data and have some
form of data structure.
In other words, have a Table for the processes that has a heading Fundamental Processes,
Cardinal Processes and Management Processes this table would then be written back to
CMS and ER, but allow the pre-listed clauses and table labels to work.
However, at the scheme set-up level when clauses are created, we shall need to have an
additional option to create a clause and determine whether it falls within the Category of
Fundamental, Cardinal or Management.
Like now, the number of clauses for each standard against Category will not have a limit.
10.2 Further, when the administrator is within the above section, a drop-down, or similar
field should be presented to allow the clause to be placed within an Element (and element
topic if the Element allows the administrator to Bold Element and have sub-titles then
happy to remove the element topic to reduce complexity and table complexity it would
also allow greater space for the auditor to add his/her findings in the eventual ER template).
10.3 The above point 10.2 above, makes the assumption that when setting up the standard
on CMS, the administrator of CMS will need to be mindful to create, in effect, the
standard/scheme tables for each Process Type i.e.: Fundamental, Cardinal and
Management, as well as the Element Headings before the clauses are assigned in order to
then complete 10.2 above.
Please note that there must be the ability to amend the above table for whatever reason.
10.4 Once the process tables and clauses have been determined at scheme level, then on
the creation of the relevant ER template, such tables as R/W can then be selected in a
similar manner to existing ER table templates, providing their label is clear for the ER
creator.
10.5 Note also, the existing facility of adding and amending Processes during the completion
of an Audit Report will still exist; however, the existing system will need to allow the
identification of the Process name (Process Variable) to be linked to the Process Type i.e.:
Fundamental, Cardinal, Management to allow the write back to CMS and write to ER with
the correct data.
OR
We do away with the existing process R/W functionality and change to reflect the Process
Variable table entries.
The illustration must show the processes as described, or within the headings Fundamental,
Cardinal or Management but this labelling is not essential.
10.7 Summary Element (possibly Element Topics) and Clauses are Variable and determined
by the database administrator on scheme set-up.