(0) Not defined:

There is no awareness or evidence of a technical management plan within the organisation, or management of technical infrastructure resources that support all the repository functions and services.

(1) Initial:

There is management of technical infrastructure but this is undertaken on a reactive when needed basis. There is no evidence of documented planned management.

(2) Repeated/partial:

There are regular management tasks undertaken but these have been established through repeated practice. There is no documented technical management plan.

(3) Defined:

The organisation has in place a documented technical management and maintenance plan.

(4) Managed:

Technical management and maintenance is monitored. Issues and discrepancies from the plan are recorded.

(5) Optimised:

At regular intervals the technical management and maintenance plan is reviewed and appropriate changes are made, recorded and communicated.

(0) Not defined:

There is no evidence or awareness that the organisation has defined what is the appropriate technology or level to support all functions and services. The technology appears to be inadequate to support all functions and services.

(1) Initial:

There is evidence that the technological infrastructure is partially complete, either due to lack of resources or unable to employ qualified staff. The organisation has not defined the appropriate technological resources or level to support all repository functions and services.

(2) Repeated/partial:

There is evidence that there is likely to be an appropriate level of technical infrastructure resources to support all repository functions and services, however the organisation has not defined what this level should be.

(3) Defined:

The organisation has defined the appropriate technical infrastructure resources to support all functions and services.

(4) Managed:

Technological infrastructure resources appropriate to support functions and service needs are monitored and analysed at regular intervals. The monitoring is documented.

(5) Optimised:

At regular intervals the appropriate technological infrastructure resources are reviewed with respect to the function and service needs and the description is adjusted accordingly.

(0) Not defined:

There is no evidence of, or awareness of the need for, software migration and maintenance being performed by the organisation.

(1) Initial:

Software migration and maintenance is undertaken by staff who care for a specific service, hardware platform, or tool, on an ad hoc basis.

(2) Repeated/partial:

Software migration and maintenance is undertaken by individuals in a coordinated fashion when required to do so.

(3) Defined:

Migration and maintenance of core software is undertaken in a planned and consistent manner in accordance with appropriate policies and the management and maintenance plan and by responsible roles. A risk assessment and test installation are undertaken before migration or substantial updates are applied to core software.

(4) Managed:

Software migration and maintenance are monitored and issues and incidents are recorded.

(5) Optimised:

At regular intervals the procedures of migration and maintenance of core software are reviewed, modified where required to improve process or where required by policy change, and communicated internally.

(0) Not defined:

There is no evidence of a software evaluation procedure or requirements being defined.

(1) Initial:

New or updated software is evaluated on an ad hoc basis by various roles or staff. Software maybe installed and used to provision a function or service without a full evaluation being performed.

(2) Repeated/partial:

New or updated software is evaluated for use on a regular basis to a set of undocumented requirements but based upon the knowledge of staff. There is no systematic or comparative reporting.

(3) Defined:

A defined set of requirements (functional and nonfunctional) is created for the evaluation of core software tools or software services required safe and consistent provision of functions and services. Software or service is selected based upon best fit to the requirements. This process is documented in a policy.

(4) Managed:

The process of creating the requirements and software selection are monitored and issues recorded.

(5) Optimised:

At regular intervals the process of software and service evaluation is reviewed and alterations made if required due to changes in other policies or issues noted.