Concept explanation – Groups, categories, control schemas and activities
CONTEXT #
This article shows an overview table of the central concepts in the system module (AjourInspect & QA) for building groups, categories, control schemas and activities. The table describes the purpose of each concept, which synonyms exist in the system language, and how the concepts relate to each other in practice.
RELEVANCE #
You need this explanation when you are building or maintaining a control structure in the system – for example, when you are creating templates for several projects, or when you need to understand how groups, categories, control schemas and activities fit together. Knowing the concepts makes it easier to navigate the system and place new data correctly.
PREREQUISITES AND REQUIREMENTS #
- Access to the system with permissions to create or edit groups, categories and control schemas
- Basic knowledge of how the system is structured
Concept explanation #
| Step | Concept | Explanation | Synonyms | Relation | Action |
| Step 1 | Schema Headers | Schema headers are used as the basis for designing the column headings of a control schema. | Columns, column headings | Activities, acceptance criteria, control time, control method, documentation requirements, control scope, control result | Identify which headings the columns in your control schema must have. |
| Step 2 | System Groups | System groups are templates and are used to group one or more categories and/or control schemas. They work as templates in the system and can be imported to projects. | Templates, standards, paradigms | Construction management, handover, 1-5 year review, work environment, supervision, DS1140 – self-inspection, DS1140 – independent inspection, trade contract – self-inspection | Choose a system group if the structure is to be reused across projects. |
| Step 3 | Project Groups | Project groups are project-specific and are used to group one or more categories and/or control schemas. They can be linked to registrations on projects. | Control plans, tender control plans | Construction management, handover, 1-5 year review, work environment, supervision, DS1140 – self-inspection, DS1140 – independent inspection, trade contract – self-inspection | Choose a project group if the structure is to apply to one specific project only. Remember that at least one project group must always be linked to the registration type. |
| Step 4 | Categories | Categories are created under groups and are used to categorise one or more categories or control schemas. They can be linked to registrations on projects. | Control plans, tender control plans | Receiving inspection, process control, final inspection (can optionally be divided by trade group, building part, material or product) | Create categories under your chosen group. |
| Step 5 | Control Schemas | Control schemas are created under groups or categories and are used to list one or more activities. They can be linked to registrations on projects. | Checklists, control plans, tender control plans | Receiving inspection, process control, final inspection (can optionally be divided by trade group, building part, material or product) | Create the control schema under the group or category. |
| Step 6 | Activities | Activities are created under control schemas and are used to specify which conditions the user must carry out or document. | Checkpoint, control point, work, task, effort | – | Add the specific activities under the control schema. |
| Step 7 | Linking to project | When the entire structure (group, category, control schema, activities) has been created, it can be put into use. | – | – | Link the structure to registrations created on the relevant project. |
NEXT STEPS #
- Create your first control schema with the relevant schema headers
- Review the existing system groups to see whether a template already covers your needs
- Link the finished structure to a registration on a project to test the flow