r="0" cellspacing="0" cellpadding="0" align="center">

CP flow-V16

Ownership Document

Created:	04/07/2008
Last Modified:	07/10/2008

Table of Contents


1.0	Roles
	1.1	AC Coordinator
	1.2	CCB Admin
	1.3	CCB Chairperson
	1.4	Chief Technical Officer
	1.5	Chief Technology Officer
	1.6	Chief Technology Officer (CTO)
	1.7	CR Manager
	1.8	Document Editor
	1.9	Document Release Manager
	1.10	Document Release Manager
	1.11	Domain Expert
	1.12	Member Services Support
	1.13	Principal Representative
	1.14	Product Manager
	1.15	Product manager
	1.16	Project Champions(s)
	1.17	Project Leader
	1.18	Requestor
	1.19	Sector Heads
	1.20	Subject Matter Expert
	1.21	Team Leader
	1.22	Technical Committee Chair
	1.23	TM Forum IT support
	1.24	TM Forum Staff Support
	1.25	TMF Staff Support Person
	1.26	TPC Chair
	1.27	VP Collaboration Program

2.0	Groups
	2.1	Approval Committee
	2.2	CCB
	2.3	Change Control Board
	2.4	Community
	2.5	Industry
	2.6	Liaison Groups
	2.7	Membership
	2.8	Membership
	2.9	Project Team
	2.10	Project Team
	2.11	Public reviewers
	2.12	Sector Interest Group
	2.13	Sector Interest Group
	2.14	SPLC
	2.15	Technical Committee
	2.16	The Industry
	2.17	TM Forum Board
	2.18	TM Forum Board
	2.19	TPC
	2.20	TPC

3.0	Individuals
	3.1	Dcoument relase manager

1.0

Roles

1.1

AC Coordinator

Staff person supporting the Approval Committee and approval process

Direct Responsibilities

Name Description Type

Capture comments Comments from member and, where appropriate, public review are captured and provided to the AC to assist with their approval decision Activity

Charter distrubution The charter is distributed to the Approval committee for approval along with review end date Activity

Expert review Deliverables are reviewed by appropriate subject matter experts and groups Activity

Initial Deliverable Approval Sub Process Process Map

Member review The deliverable is reviewed by the membership Activity

Post deliverable to member only domain Deliverable is posted such that it is available to members only Activity

Post deliverable to the public domain Deliverable is posted such that it is availbale to the public. Activity

Project Approval Sub Process Project Approval sub -process Process Map

Public review The deliverable is reviewed by the public Activity

Quality Assurance Check Check that the deliverables meet the required quality levels prior to posting. Activity

Start Deliverable approval process Start Point

Start Project Approval process Start Point

TMF413 Approvals Submission form [hyperlink] TMF 413 Controlled Document

1.2

CCB Admin

Direct Responsibilities

Name Description Type

A valid Request Is the request valid Decision

Pre Assess Request Validate CR technically and assign CR Manager if appropriate. Activity

Receipt of Request Sub Process Process Map

Register Request Activity

Validate Request Activity

1.3

CCB Chairperson

Direct Responsibilities

Name Description Type

Base Artifact Request Sub Process Process Map

Determine course of action for CR Decision

Determine course of action for CR Decision

Fast-Track CR Sub Process A shorter process for CR's to follow. Process Map

Formal Vote on CR CCB review Decision

Normal CR Sub process Process Map

Pre-access CR Investigate the nature of the change request Activity

Reject Decision CCB have reviewed the CR and agreed to reject it. Activity

Start Normal CR Sub-Process Start Point

1.4	Chief Technical Officer The CTO is a member of the board who has overal responsibility for the Technical Propgram

1.5	Chief Technology Officer

1.6

Chief Technology Officer (CTO)

Direct Responsibilities

Name Description Type

For Public Review decision Is the deliverable to be submitted for public review? Decision

1.7

CR Manager

Direct Responsibilities

Name Description Type

Assess CR Activity

CR Implementation Activity

Defer Decision Unable to make a decision at this point due to various reasons. Activity

Esculation Option Activity

1.8	Document Editor Individual responsible for collating the contributions from the project team into the deliverable(s)

1.9	Document Release Manager

1.10

Document Release Manager

Responsible for processing and posting documents

Direct Responsibilities

Name Description Type

Approved Project Charter Approved project chater - review after 6 months Controlled Document

Gather cast votes Corporate Members cast their vote. Activity

Invite members to vote Activity

Process deliverable to TM Forum Approved status upgrade the document status and process. Activity

Process Unapproved Document Activity

Process Votes Activity

Remain in member evaluated Start Point

Result of Vote Decision

1.11	Domain Expert

1.12	Member Services Support

1.13

Principal Representative

The Principal Representative of the member companies who have the right to vote on behalf of their company

Direct Responsibilities

Name Description Type

AC approves or rejects the charter Decision

1.14	Product Manager

1.15

Product manager

Manages the development and delivery of products

Direct Responsibilities

Name Description Type

Approved Project deliverables A suite of approved deliverables, documents model files etc, that satisfy the objectives of the project Controlled Document

Deliverable Posting Activity

Deliverable to continue for TM Forum Approval decision Decision

Development phase Sub Process Develolment of project deliverables in line with the project charter Process Map

Formal 'TM Forum Approval' Sub Process The process which is undertaken to achieve TM Forum Approval status for a deliverable. Process Map

Product plans Road map and project plans for each product / project Controlled Record

Project Requirements Requirements for exisiting or new projects projects Document

Requirement Analysis and Assignment Sub Process Review new requirements and allocate to projects Process Map

Requirements capture Collect requirements Activity

Requirements capture and rationalisation Sub Process Process Map

Requirements Rationalisation and prioritisation Requirements Team meet to assess the requirements and prioritise as appropriate Activity

Review requirements Each requirement is reviewed with a view to implementation. Activity

Submit for approval Activity

1.16	Project Champions(s) If necessary, identify a project champion for the new project(s)

1.17	Project Leader A individual from a member company designated to lead a project team

1.18

Requestor

1.19

Sector Heads

The Sector Head is a role which is perfomed by an individual person.

This role, which focuses on an individual industry sector, is to represent it in an effort to drive the TM Forum work to statisfy the needs of that particular sector.

This position is held by a TM Forum staff person.

Assigned Personnel

Name Description Type

Sector Interest Group Sector Interest Groups represent the interest of their industry sector within the Collaboration Program Group

1.20	Subject Matter Expert Individuals with detailed knowledge in a specific domain area

1.21

Team Leader

Individual responsible for managing the project team

Direct Responsibilities

Name Description Type

Define format of deliverables Conduct the ground work prior to delvierable development. Activity

Deliverable Posting Activity

Project deliverable(s) Documents, model files etc. required to meet the project deliverables Multi Document

Project deliverable(s) Documents, model files etc. required to meet the project deliverables Multi Document

Project management report Report against project plan and charter Requirement

Start Development phase Development of the project deliverables as defined in the approved project charter Start Point

Submit for approval Activity

Submit proposed charter Team submits proposed charter to the approval process Activity

Team reviews and updates Internal team and/or peer team reviews of the material Activity

TMF413 Approvals Submission form Approval Committe Submission Form Requirement

1.22	Technical Committee Chair Chairperson for the Technical Committee

1.23	TM Forum IT support

1.24	TM Forum Staff Support TM Forum staff support person allocated to the project

1.25	TMF Staff Support Person Person assigned to assist a particular team

1.26	TPC Chair Chair of the Technical Program Council

1.27

VP Collaboration Program

Direct Responsibilities

Name Description Type

CP flow-V16 End to end process flow for the Collaboration Program including project intiation and deliverable review and approval Project

Iniate new project Team Create a New team or rescurrect a previously closed team. Activity

Start CP Process Start Point

2.27

Groups

2.1

Approval Committee

The Approval Committee is the operational body that approves technical work projects and the release of technical team deliverables to the membership or the public. It is comprised of selected members of the Technical and Operations Committees of the Board of Directors, the Service Provider Leadership Council (SPLC) and TM Forum technical staff. The Approval Committee is chaired by the TM Forum President.

Direct Responsibilities

Name Description Type

AC Approval Decision AC approves or rejects the charter Decision

New charter required Decision Determine if the requirements fit within the current project scope or is tracked via CR process Decision

2.2

CCB

The Change Control Board (CCB) will provide a single body for the approval of changes to an existing product baseline. Initially the baseline will focus on documentation sets. This will be expanded to include the NGOSS models and other product types in due course.

The Change Control Board will report to the TMF Approvals Board and is chartered with responsibility for ensuring that the change control process as documented in TECH-07, Change Control Process, is adhered to by the TMF Technical Program.

Direct Responsibilities

Name Description Type

Determine type of CR being requested Is CR a candiate for Fast Track or Normal CR Processing. Decision

2.3	Change Control Board

2.4	Community These are like minded people who come together to discuss a particular issue, e.g. web communitites.

2.5

Industry

2.6	Liaison Groups

2.7	Membership

2.8	Membership

2.9	Project Team

2.10	Project Team

2.11	Public reviewers

2.12	Sector Interest Group

2.13

Sector Interest Group

The sector Heads can initiate the creation of sector interest groups to research and address specific areas of their industry. These groups are made up from representatives from Member companies. These groups will in turn liase with other discussion forum, e.g. other project teams within the Collaboratin Program and/or other standards bodies through the Liaison process, to validate or indeed expand upon the existing requirements.

Roles/Groups

Name Description Type

Sector Heads Sector Czars are specialists in the sector that they represent and drive the participation of companies in their market sector in the TM Forum Role

2.14

SPLC

The Service Provider Leadership Council (SPLC) consists of a group of service providers from around the world who work together to create a unified voice for service providers’ needs from their OSS/BSS vendors.

The SPLC recommendations are used to drive TM Forum work, and as such drive development of industry standards for the telecom software community as a whole.

2.15

Technical Committee

The chief duties of this committee are to develop the technical strategy for the TMF collaboration program. It also provides advice and guidance to the board, participates in the review and approval of project charters and documents as well as input to the Strategic Operating Plan

Requirements

Name Description Type

Technical Strategy Detailed techical strategy derived from the Board strategy Requirement

Direct Responsibilities

Name Description Type

Technical Strategy Detailed techical strategy derived from the Board strategy Requirement

2.16	The Industry The great and vast mass which makes up the communications industry.

2.17

TM Forum Board

Direct Responsibilities

Name Description Type

Business Strategy TM Forum business strategy Requirement

Sector Heads Sector Czars are specialists in the sector that they represent and drive the participation of companies in their market sector in the TM Forum Role

Technical Committee Sub-committee of the board that provides the detailed technical strategy and guidance for technical projects Group

TM Forum Board The TM Forum board elected by the membership Group

2.18	TM Forum Board

2.19

TPC

The team leaders of all the standing technical teams are invited to join the Technical Program Steering Council. The objectives of the council are:

• To maintain an oversight of the overall progress of the technical program

• To help review project charters and technical documents prior to submission to the approvals committee

• To identify complimentary areas between programs which may help to accelerate work

• To identify possible areas where programs are creating duplication or divergent approaches from strategic TMF directions (such as NGOSS)

• To help in allocation of resources between projects where appropriate

• To help resolve conflict between teams and make recommendations to the technical committee/Approvals Committee

This team represents a broad constituency and have a good spread of technical knowledge. This team will get sight of project charters and technical documents so that comments and recommendations can be made to the approvals committee to help them in voting. The collated comments from the TPC and forward them to the Approvals Committee for their consideration

The council aims to

• meet by conference call once a month and at TAW to share progress in work and to discuss any points of conflict or overlap

have a significant impact on the direction of the TMF technical program

Direct Responsibilities

Name Description Type

Assign to existing team requirements assigned to current teams in the appropriate manner Activity

Program Management Activity

2.20

TPC

The team leaders of all the standing technical teams are invited to join the Technical Program Steering Council. The objectives of the council are:

• To maintain an oversight of the overall progress of the technical program

• To help review project charters and technical documents prior to submission to the approvals committee

• To identify complimentary areas between programs which may help to accelerate work

• To identify possible areas where programs are creating duplication or divergent approaches from strategic TMF directions (such as NGOSS)

• To help in allocation of resources between projects where appropriate

• To help resolve conflict between teams and make recommendations to the technical committee/Approvals Committee

The council aims to

• meet by conference call once a month and at TAW to share progress in work and to discuss any points of conflict or overlap

have a significant impact on the direction of the TMF technical program

3.20	Individuals

3.1

Dcoument relase manager

Title

Department

Email

Phone

Fax

Mobile

Direct Responsibilities

Name Description Type

AC approves or rejects the charter Decision