Configuration management
SFIA 3: Definition
The systematic management of information relating to the documentation, software, hardware and firmware assets of an organisation. This will involve identification and appropriate specification of all configuration items (CIs). Required information will relate to storage, access, problem reporting and change control of CIs. Application of status accounting and auditing, often in line with acknowledged external criteria such as ISO 9000, throughout all stages of the CI life history.
Proposed for SFIA 4.0:
The lifecycle planning, control and management of the information relating to the documentation, software, hardware and firmware assets, their dependencies and relationships of an organisation, system and/or service(s). This will involve identification, classification and appropriate specification of all configuration items (CIs) and the interfaces to other processes and data through techniques such as federation. Required information will relate to storage, access, service relationships, versions, problem reporting and change control of CIs. Application of status accounting and auditing, often in line with acknowledged external criteria such as ISO 9000 and ISO 20000, throughout all stages of the CI lifecycle.
The skills level summary should be accurate
Posted by
bpscotty
at
2008-08-03 10:56 AM
The way the skills summaries are currently written to me inflates the roles, but when reading further into the SFIA the additional attributes for each level read true - So level 3 should read level 2 etc. Particularly within SFIAPlus level 3 detail is good but some of it could be seperated to create a level 2
- so it is basically only that a level 2 should be created and a new summary for level 6 is created.
An example for Level 6 – should be “manages the organisation CMS and champions the business value and company policies for the CMS. Key participant in the business Service Knowledge Management System. Manages the research and development of tools, processes and techniques.
- so it is basically only that a level 2 should be created and a new summary for level 6 is created.
An example for Level 6 – should be “manages the organisation CMS and champions the business value and company policies for the CMS. Key participant in the business Service Knowledge Management System. Manages the research and development of tools, processes and techniques.
Forgot your password?
New user?
CI planning and lifecycle management should also be mentioned.
Key area is the relationships and dependencies of CI’s and the service models built on them.
Needs to be brought in line with ITILV3 but also continue to cover traditional version control.
The lifecycle planning, control and management of the information relating to the documentation, software, hardware and firmware assets, their dependencies and relationships of an organisation, system and/or service(s). This will involve identification and appropriate specification of all configuration items (CIs) and the interfaces to other processes and data through techniques such as federation. Required information will relate to storage, access, service relationships, versions, problem reporting and change control of CIs. Application of status accounting and auditing, often in line with acknowledged external criteria such as ISO 9000 and ISO 20000, throughout all stages of the CI lifecycle.