CP112 Data Model Entities

Learn about CP112 Data Model Entities


The DATA MODEL ENTITIES represents the foundation of the CP112 data model. While the data model entities describes the information that will be carried out through the processes, the relations between the data model entities describes the evolution of the information when passing through the processes. The implementation of the data model entities for 112 systems follows the main logic of the life cycle stages, DESIGN; IMPLEMENT; OPERATE. Click on the buttons below to read more about the CP112 general data and about the CP112 custom data models.

Click on the button below to read more about the relations between the data model entities.

Working with the data model entities is possible inside the dedicated sections of CP112. Click on the button below to read more about CP112 sections.

Anywhere inside CP112 sections, the data model entities can use the global data entities (organisational structure, responsibility map, commercial entities, risk entities). Click on the button below to read more about CP112 global entities.

CP112 offers both a general data model and a custom data model that further refine the general data model on the specifics of 112 systems. These models are part of the initial provision of CP112 platform but can be even further adapted, modified or extended as needed.

Entities for DESIGN stage

The data model entities for the DESIGN stage are designed in order to allow the full traceability of the information from the main objective to the requirements designed to be implemented in order to meet the objectives. These data model entities are:

  • Main Objective of the system: the main objective of the 112 system
  • Specific Objectives of the system: the specific objectives of the 112 system
  • Functional Area main objective: the main objective of a functional area
  • Functional Area specific objective: the specific objectives of a functional area
  • Component main objective: the main objective of a component
  • Component specific objective: the specific objectives of a component
  • Recommendation/Task: a recommendation/task inside a compoenent

Using these data model entities and connecting them in a logical structure (both hierarchic or non-hierarchic) CP112 provides the a complete view and understanding of the impact of any data model entity on the 112 system. Following the general data model, CP112 propose also a specific template, that further applies the general data model on the specifics of a modern 112 service under all the usual functional areas, Legal, Organisation, Public Awareness, Public Warning, ICT and Work Environment.

Entities for IMPLEMENTATION stage

After the DESIGN stage, the next one is the IMPLEMENTATION stage. Both data models offered by CP112 (the general data model and the custom data model) provides the data model entities that can be used during the implementation of a complex 112 system. These entities are:

  • 112 Programme: the main programme under which everything will be implemented
  • Functional Area Programme: the first level under the main programme, one for each functional area
  • Component Project: a project inside a functional area programme having clear scope and duration
  • Tasks: a task inside a project

Note that, by default, the general and custom data models will transform the recommendations entities from the DESIGN stage into tasks inside the projects. This will allow, on one hand, full traceability at the transition between DESIGN and IMPLEMENT stages but also automation of the process (you don't have to re-define the tasks when going to implementation). Even more, this approach allows further refinement of the recommendations/tasks into procurement requirements (for procurement process) followed by implementation actions. Assignments of responsibilities (from the organisational chart) is possible at all levels.

Entities for OPERATIONS stage

The next stage in the life cycle of the 112 system is OPERATIONS. The assets produced in the IMPLEMENTATION stage are used/consumed in the OPERATIONS stage. Both CP112 data models contains the support for defining and using the data model entities that are relevant for the OPERATIONS stage. The base data model entities is formed by the ASSETS and the BUSINESS PROCESSES. The assets are linked to the implementation projects, thus enduring the full transition from the IMPLEMENTATION stage to the OPERATIONS stage (and, through the previous DESIGN to IMPLEMENTATION transition, the full traceability from the initial recommendations to the ASSETS and BUSINESS PROCESSES).

The custom CP112 data model refines the general data model by identifying the main assets such as the 112 Public Safety Answering Points (PSAPS) or the component of the ICT platform (Computer Aided Dispatch CAD, Emergency Secure Internet Network ESINet, Public Warning System PWS and others). Further, the assets are linked to the organisational units and responsibilities map in order to provide a complete view on the responsibility matrix.

Additionally, CP112 provides the functionality for assessing the performance of the 112 service in using the assets through compliance with policies and regulatory frameworks and through embedded structure of KPIs and Quality Management features.