Company: Functions
Enter the functions of your reporting company that are supported by ICT third-party services — these records must exist before you can assign contracts to functions.
Fields covered on this page:
Function ID
A sequential number that Copla Registry combines with the prefix "F" to generate a unique function identifier for this record.
What to enter
Enter a sequential number — 1, 2, 3, and so on.
The same function operated under two different licensed activities requires two separate function records with two separate IDs.
NOTE:
-
The function identifier is a key value in the register. It must be unique and used consistently across all records that reference this function.
If you're having issues, see My function identifier is invalid.
Select reporting company's function
The licensed activity of the reporting company that this function supports.
What to enter
Select the licensed activity from the list that corresponds to this function.
If the function is not linked to any licensed activity — for example, an IT support or HR function that enables core activities — select Support function.
Function's name
The internal name used by the reporting company to refer to this function.
What to enter
Enter the function name as it is defined in your entity's internal organisation.
There is no prescribed list of function names — use whatever terminology your entity applies consistently.
Importance assessment
Whether this function has been assessed as critical or important, and the outcome of that assessment.
What to enter
Select Yes if the function has been assessed as critical or important.
Select No if it has been assessed and determined not to be critical or important. Select Assessment not performed if no assessment has been carried out.
NOTE:
-
The importance assessment is the entity's own determination based on its internal assessment and applicable sectoral regulations.
-
There is no prescribed list of functions that must be classified as critical or important.
If you're having issues, see Criticality, RTO, RPO, and special values issues.
Reasons for criticality
A brief explanation of why this function has been assessed as critical or important.
What to enter
Enter a plain-text explanation of up to 300 characters.
Focus on the operational or regulatory reason — for example, the function's role in delivering a core service, its regulatory classification, or the impact its disruption would have.
NOTE:
-
This field is required only when the importance assessment is
Yes.
Does external function support time-critical operations?
Whether the outsourced function is essential for time-sensitive operations of the reporting company.
What to enter
Select Yes if disruption to this function would affect operations that are time-critical — for example, payment processing or real-time trading.
Select No otherwise.
Last importance assessment date
The date on which the reporting company last assessed or reviewed the criticality or importance of this function.
What to enter
Enter the date in YYYY-MM-DD format.
If no assessment has been performed, enter 9999-12-31.
If you're having issues, see Criticality, RTO, RPO, and special values issues.
Function's recovery time limit
The maximum time in hours that this function can be unavailable before it seriously affects the reporting company's operations.
What to enter
Enter a whole number of hours.
If the recovery time objective is less than one hour, enter 1. If the RTO has not been defined, enter 0.
NOTE:
-
When the same ICT service supports several functions, the RTO for the service must comply with the shortest RTO across all functions it supports.
-
Enter each function's own RTO independently — do not average across functions.
If you're having issues, see Criticality, RTO, RPO, and special values issues.
Function's recovery data loss limit
The maximum amount of data loss in hours that the reporting company can accept after an outage affecting this function.
What to enter
Enter a whole number of hours.
If the recovery point objective is less than one hour, enter 1. If the RPO has not been defined, enter 0.
If you're having issues, see Criticality, RTO, RPO, and special values issues.
Impact if function stops
The assessed impact level on the reporting company if this function is discontinued or significantly disrupted.
What to enter
Select Low, Medium, or High based on the entity's own assessment.
Select Assessment not performed if no assessment has been carried out.
If you're having issues, see Criticality, RTO, RPO, and special values issues.
Impact if outsourced function stops
A description of the operational impact on the reporting company if the outsourced part of this function stops.
What to enter
Enter a plain-text description of the impact.
Describe what would happen to the entity's operations if the ICT third-party service supporting this function became unavailable.