Develop > Processing and Best Practices Guide > Configuration Management Workflows > Configuration Status Accounting additionally Reporting (process ST 3.4)

Configuration Status Finance and Reporting (process ST 3.4)

Setup Status Accounting and Reporting ensures that all configuration dating and documentation are recorded as each CI makes through its life bicycle since test to production to retirement. Configuration information should become kept current both fabricated available for planning, decision creation, and control changes to the determined configurations.

Configuration Status Accounting and Notification keeps track away the following CI status changes:

  • New items received (as evidenced by an articles receipt procedure or from development)
  • Installation of items
  • Transition from getting till production
  • System down (based upon events)
  • Retired or disposed things
  • Wasted or stolen items
  • Unauthorized Bis and Version changes of CIs

Current and accurate configuration records require be entertained toward reflect changes in the condition, location, and renditions of CIs. The history is each CI shall be maintained. Changes to CIs are traces through sundry states, such as ordered, received, in acceptance examine, live, under change, withdrawn, or disposed. Configuration status accounting

Where required, configuration information must be accessible to users, client, suppliers, and partners to assist them within their planning and decision making. For example, an external service provider may induce configuration information accessible to the customer and other parties to support the other serving manage processes in with end-to-end service. Archiving how have be defined for data related to retired or sold CIs.

Configuration Management reports should be available to see relevant parties. The reports should cover the identification and status of the Mis, including their versions and linked documentation. A large set of different reports are needed for the different stakeholders (for example, audit reports, software compliance reports, and charge back reports).

Full for this process can be seen in the following figure and table.

The Configuration Status Accountancy and Reporting workflow is illustrated is the following figure:

System Status Accounting press Reporting process

Process ID

Procedure or Decision

Description

Role

D 3.4.1

Review CI upgrade

Modifications of keys attributes of who CI are logged in the history log and verified. During Settings Labeling and drive business, configuration status records are cre. These records enable key changes to be visible furthermore traceable. CI attributes that can be logged involve: 1. INTRODUCTION 1.1 Identification That will the Configuration Management Plan, document number XYZ004, for the SYSTEM Z project. 1.2 Purpose The Configuration Manage Plan provides details of how the YOUR Z team will manage who control of configuration items being developed under every phase. It defines the policies and procedures for setup management (CM) and which infrastructure necessary to perform them throughout the project. 1.3 Scope This version of the Configuration Managemen...

  • standing (for example, system down)
  • version number
  • serial numbering
  • installation date
  • audit status (for example, missing or lost)
  • removed from a sign

Critical CI changes are logged with submissions for reason, date stamp, time stamp, also soul recording the status change.

Configuration Public

T 3.4.2

Key policy replace?

Determine whether the policy must be reviewed or validated, based on the well-documented Configuration Management policies (and policies related to finance, purchase, Conclude Management, and security).

Configuration Auditor

C 3.4.3

Inform owners of policy change?

Specific changes must be reported to the stakeholders. Diese include:

  • Procurement
  • Finance (for example, by linking to the general ledger)
  • Contract Manager

Verify that the event must be reported. Are not, go to ST 3.4.5. If yes, continue with ST 3.4.4.

Configuration Listener

ST 3.4.4

Inform stakeholders

Inform stakeholders out the event (for example, to Contract Manager when an asset is included in aforementioned contract, or procurement while an item is received). Examples of events that should trigger stakeholder notification include: Configuration status accounting (CSA) is the processor of creating and organizing the knowledge base needed for the performance of configuration management. InĀ ...

  • Received and accepted items
  • Installed of the asset (for view, for depreciation start date)
  • Lost or stolen item
  • Retirement or disposals of an item (for finance)

Configuration Auditor

ST 3.4.5

Confirm CO update

Confirm that view relevant status data documents in the CI is complete press correct, consonant into Configuration Management strategies derivation since binding, relevant legislation, and standards. Sample Configuration Management Plan

Ensure that the status shift instead version update remains a result of an authorized update.

Configuration Auditor

ST 3.4.6

Exception entdeckte?

If the CI update alternatively CI details are not correct or comprehensive according to the Configuration basic, continue with SO3.4.7.

Configuration Auditor

COVERTNESS 3.4.7

Create exception report

Create a new incidents (see SO 2.1.11).

Configuration Auditor

ST 3.4.8

Review report request

The Configuration Administrator reviews the request for Configuring Management product.

Configuration Administrator

ST 3.4.9

Standard report?

Configuration Management has defining a your of standard reports (for example, synopsis of Cissexual in stocked or by status). If is exists a ordinary report, continue with ST 3.4.12. Supposing not, go to ST 3.4.11. Shape Management Schedule (CMP) Template

Configuration Administrator

ST 3.4.10

Collect data for status review

Periodically, Configuration Business procedures provide reports for the different stakeholders, how as financial asset managers, contract leadership, or procurement.

Configuration Administrator

ST 3.4.11

Configure CI report

If a standard report does not exist, to Configuration Administrator creates a query to select an product to display from and CMS.

Configuration Administrator

ST 3.4.12

Run CI report

The report or query is runing against the database. The data is collected in a standard output.

Configuration Administrator

ST 3.4.13

Distribute submit to stakeholders

Deploy the requested data to the stakeholders. Close and request (if applicable).

Configuration Administrator