Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Collaboration Program Process Looking to start from scratch.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Work Request Capture and Rationalisation Sub Process New work and change requests may be captured from a number of different sources using a common on-line entry point, (http://www.tmforum.org/Community/groups/collaboration_program_center/changerequest.aspx) .  These work requests are brought together into a single, consolidated list, indicating a priority level. Thes eare then filtered and assigned to an appropriate working group. By default items entered here will be of a Maturity level 0 (not set) or 1. Refer to detailed 'Work Request capture and rationalisation' sub process for complete details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Work Request Capture Work requests entered via the online form are automatically stored in a central repository. From here it is sanity checked by TM Forum staff and the appropriate Maturity level, (default 1) is set.  It is then assigned and forwarded to a CR Manager who will manage it through the remainder of its life.   A quick pre-assessment is conducted by the CR Manager to ensure straightforward items can be addressed quickly and more complex ones are sent for more detailed analysis.  Approx 10% of the requests will complete its assessment at this phase of the process. The duration of this phase should be a 1 to 2 days. Maturity level for items in this phase would typically be of a level 1 (IPR and other sanity checks having been completed). Refer to the Work Request sub-process for more details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Work Request Rationalisation sub-process Within this sub-process the more complex work requests are put forward for initial assessment by the complete CCG and from here it will get routed down the most appropriate path. This could be to be deferred, rejected or continue on for further analysis/investigation, and assigned to the appropriate investigating body.  At this point the bulk of work requests will go for further assessment. This phase should be completed by 2 weeks of request submission. Maturity level of work requests at this phase would typically be of a level 1,  Request such as Fast track items, which would have completed their assessment phase would be upgraded to maturity level 2. Refer to the Work Request Rationalisation Sub-process for complete details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Work Request analysis & Assignment sub-process Within this phase, The stakeholders, (who could be a single person or a team of people depending on complexity of the request), review the work requests and provide an assessment, (which can be a single line in the requestor tracker or a detailed report - once again, depending on complexity of request), on their findings & recommendations. These return to the CCG where they are rejected or allocated to existing projects or a proposal to start the procedure to initate a new project. Duration of this phase can take from 1 day to 3 months depending on completxity. Once work request have completed their assessment, they will have progressed to a Maturity level 2. Refer to the detailed 'Requirements Analysis and Assignment' Sub Process for complete details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Fast track request Sub Process The fast track mechanism allows for the quick turn around for work requests which are straight forward in nature and/or are of an urgent nature. Refer to the Fast Track Request sub-process for details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Call for RFP/Prospectes

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Task team creation and Assessment Work requests which are of an extreme complexity or have far yielding implications on the TM Forum standards will normally be addressed within a task team. The task team could be generated by a predefined group of people or work as an ordinary development team, putting an open call for participation and setting a Team Leader.  In either case, they should conduct minuted meetings etc. The team has the freedom to address this item as best fits the problem at hand.  HOWEVER .... The team have a timeframe of 3 months in which to complete the assessment and return their final report, which should at a minimum have broken down the issue into manageable bits and indicate the expected implementation effort, priority and urgency. Maturity Level will typically be a level 1 at this point.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Project Approval Sub-Process The Project Approval sub-process describes the activities necessary for the approval of a new project.  A new project could require a new team or a new phase of an existing team. Refer to the detailed 'Project Approval Sub-process' for complete details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Escalation Process In the event that a requestor of a CR is not satisfied with the decisions made by the CCG, an escalation process is available to them, .by submitting their request and reasons for their dissatisfaction to the Technical Committee, no later than 1 month after notification of the decision. The Technical Committee will review the request in light of all the facts and make its decision, which could be one of the following: 1. Agree with CCG 2. Reassess with new information which had not previously been available 3. Technical Committee provide an alternative interpretation of the material already provided so as to assist the CCG in the assessment of the request. (Note: It is possible that the further information may be required from the requestor, so the submission could iterate around this phase).

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Development Sub Process During this phase of the project, the project team must operate within the scope of the approved project charter and according to the TM Forum by-laws and IPR rules as defined in the Operating Guide. This section focuses on agreeing to the exact format of the deliverables, creating the deliverables and ensuring initial quality assurance is completed. Refer to the detailed 'Development Phase' sub process for complete details

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

Deliverable Approval Sub Process Once Collaboration Project artefacts are submitted for approval, this process flow outlines the steps which it must undergo in order to achieve approval and it identifies the roles & groups who are required to part take in those steps. Refer to the 'Deliverable Approval Sub Process' for details.

This process does not have any associated risks.

Process

Risk

Control Objective

Control Name

PCAOB Assertions C EO V RO PD

Financial Statement

COBiT Assertions C A V R

Key Control?

Frequency

Preventative / Detective

Manual / Automated / Spreadsheet

Ownership

Linked Resources

Test Plan

TM Forum Corporate Vote Sub-Process Detailed here is the steps which are undertaken to set-up and conduct a formal TM Forum Corporate member vote agaisnt those deliverables which have received Technical Committee approval. Deliverables which achieve a successful Member vote outcome will be given a status of 'TM Forum Approval' and upgraded to a Maturity level of 4. Refer to the TM Forum Corporate Vote Sub-Process for details.

This process does not have any associated risks.