CP112 General Data Model
Learn about the foundation of CP112
The CP112 data model is based on informational entities and on the relations between the informational entities. Once the informational entities are defined, each of it can have a specific and customisable profile that allows the entity life cycle monitoring. On top of these, the informational entities can be placed on customised workflows that will add even more flexibility to the monitoring activities.
CP112 use the following informational entities:
For DESIGN stage:
Within the DESIGN stage the CP112 data model operates with a number of informational entities in order provide two main capabilities: requirements traceability and impact analysis. These informational entities are organised in 4 hierarchical levels.
| No. | Level | Entity Name | Entity Description |
|---|---|---|---|
| 1 | 1 | Requirement | Simple requirement/design specification/recommendation that shall be implemented |
| 2 | 2 | Component | Logical grouping of requirements |
| 3 | Component Specific Objective | A specific objective/expected result that shall be achieved by the implementation of a component | |
| 4 | Component Main Objective | Main objective of a component | |
| 5 | 3 | Functional Area | Logical grouping of components having as result a well defined functionality of the system |
| 6 | Functional Area Specific Objective | A specific objective/expected result that has to be achieved through the implementation of a certain functional area | |
| 7 | Functional Area Main Objective | The main objective that shall be met by the implementation of a certain functional area | |
| 8 | 4 | System Specific Objective | A specific objective that shall be met by the implementation of the whole system |
| 9 | System Main Objective | The main objective that shall be met by the implementation of the whole system |
The informational entities are connected as shown below in order to reflect the logical hierarchy and provide the capabilities.
For IMPLEMENTATION stage:
Within the IMPLEMENTATION stage the CP112 data model operates with a number of informational entities in order to provide the capability of monitoring the implementation. These informational entities are organised on 4 hierarchical levels.
| No. | Level | Entity Name | Entity Description |
|---|---|---|---|
| 1 | 1 | Task | A specific activity to be executed during the implementation |
| 2 | 2 | Project | Collection of tasks |
| 3 | 3 | Programme | Collection of projects |
| 4 | 4 | Main Programme | The collection of all programmes from the implementation |
The informational entities are connected as shown below in order to reflect the logical hierarchy and provide the implementation monitoring capability.
For OPERATION stage:
Within the OPERATION stage the CP112 data model operates with a single informational entity, namely the assets. Assets are the results of the IMPLEMENTATION stage and are consumed/used/operated by the organisation.
CP112 data model ensures the transitions between the three stages of the system life cycle. The main concept of CP112 (following the system design, the implementation of 112 and of each of its components produces assets that are used (consumed) by the 112 organisation during operations) is implemented by the transitions mechanism.
The common denominator of all stages of the life cycle is the organisational structure. The members of the organisational structure (departments, persons) are responsible for the design, shall perform implementation and operates the assets resulted from the implementation. CP112 data model allows the definition of the organisational structure that can be further used for providing the capabilities of the platform throughout the whole life cycle of the system.