Owner

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person

The Director, Catalyst Program, makes an open call to the membership to solicite proposals for new Catalyst projects.  The mechanism for the open call is to use email, News Central and any other appropriate methods.  The call will normally be made ~9 months before the target Management World Event.

Owner

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person

The member proposing to submit a project carries out an open call to invite other member companies to join the project.  Note that any member company is enttiled to join a catalyst project however, the proposing company can refuse the request if they feel that they have insufficient participation.

Owner

	Name	Description	Type
	Project Intiator	The person representing a member company that wishes to start a Catalyst project	Person

Performed By

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person
	Project Intiator	The person representing a member company that wishes to start a Catalyst project	Person

The initiating company completes Catalsyt Submission form and sends it to the Director Catalyst Programs.  The submissin form includes an outline of theproject plus a list of other member compnaies that will participate in the project.

Owner

	Name	Description	Type
	Project Intiator	The person representing a member company that wishes to start a Catalyst project	Person

Performed By

	Name	Description	Type
	Project Intiator	The person representing a member company that wishes to start a Catalyst project	Person

The submission document includes an outline of the proposed project and a list of the member companies that will participate in the project.

Owner

	Name	Description	Type
	Project Intiator	The person representing a member company that wishes to start a Catalyst project	Person

The submission document is reviewed by the selection panel.

The selection criteria that the panel use are:

1   Does the proposal support the technical strategy of the TM Forum?

2   Is there sufficient participation including a service provider sponsor?

3   Is the scope of the project doable in the proposed timeframe?

4   Is the result of the project demonstratable at a Management World?

5   Does the project align with NGOSS and other TM Forum work?

6   Is the project exciting and liable to be interesting to the membership?

7   Does the project address a new area?

8   Does the project have a reasonable chance of success?

Owner

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person

Performed By

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person
	Selection Panel	The Selection Panel decides whether a proposed project should continut to the charter pahes	Group

The technical strategy document is derived from the TM Forum strtaegy and sets out a detailed technical strategy to drive the technical work of the Collaboration Program.

The Selection Panel decides whether a proposed project should continue to the charter phase

The selection panel includes:

>   Director, Catalyst Programs (panel chair)

>   Chair of the SPLC (or their representative)

>   Chair of the TPC (or their representative)

>   Chair of the Interface Program (or their representative)

The Selection Panel will decide whether to allow a Catalyst to continue based on the selection criteria described in 'submission review'

Owner

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person

Incoming Links

	Name	Description	Link Label
	Submission review	Review the proposal for a Catalyst project

Outgoing Links

	Name	Description	Decision
	Project initiation	The project team is formed and a charter, project plan and marketing plan are produced	Accepted
	Rejected	The project intiator is informed that his submission has been rejected

The project intiator is informed that his submission has been rejected

The project team formally comes together and produces a Catalyst Project Charter, a detailed project plan and a Marketing Plan.

Owner

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person

Performed By

	Name	Description	Type
	Project Intiator	The person representing a member company that wishes to start a Catalyst project	Person
	Project Leader	The person appointed by the team to lead the project	Role

The marketin plan will include information on how the team will promote their project.  It will include the key marketing messages, the marketing channels that wil be used e.g. email, web and the timing of the marketing campaign.  It wil also include the key contact details of the person(s) who will be rsponsible for the marketing

Owner

	Name	Description	Type
	Marketin Lead	The person who will lead the marketing campaign for the project	Role

Hyperlink

	URL / File Path
	http://www.tmforum.org/pages/866/default.aspx

The project charter is produced using the template document TMF 405 and includes the scope of the project, the key milestones and the participating members

Owner

	Name	Description	Type
	Project Leader	The person appointed by the team to lead the project	Role

The Approval Committee reviews the project charter to decide whether the proposed project has sufficient backing, aligns with other TM Forum work and is desirable from a strategic point of view.

The AC takes input from the TPC when making its decision.

The TPC will in turn solicit input from the TM Forum Interface Program if the Catalyst team are planning on developing an interface specification.

Owner

	Name	Description	Type
	Approval Committee	A sub-committee apointed by the TM Forum board that is responsible for approving projects and deliverables	Group

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

Program team responsible for developing TM Forum interface specifications.

The AC may approve or reject the charter or they may refer it back to the project team for further work.  They may also approve a project subject to requested changes being agreed.

If the porject is approved, the project team is informed and the project charter is posted onto the TM Forum web site.

If the project is rejected the project team are informed and the charter is NOT posted.

Owner

	Name	Description	Type
	Approval Committee	A sub-committee apointed by the TM Forum board that is responsible for approving projects and deliverables	Group

Incoming Links

	Name	Description	Link Label
	Project Charter review	The project charter is reviewed and approved or rejected by the Approval Committee

Outgoing Links

	Name	Description	Decision
	Project Development	The project team develop their deliverables in accordance with their charter
	Rejected
	Project initiation	The project team is formed and a charter, project plan and marketing plan are produced	Referred back

The project team are informed that their charter has been rejected

During the development phase the team will develop their deliverables according to the scope and timescales set out in their charter.  The Project Leader will provide regular progress reports to the Director, Catalyst Programs

If at any time the team is considered to be diverging from the approved charter and do not take corrective action, the Director, Catalyst proigrams,  may ask the AC to revoke the charter and the project will be terminated.

Owner

	Name	Description	Type
	Project Leader	The person appointed by the team to lead the project	Role

Performed By

	Name	Description	Type
	Project Team	The team of members responsible for developing the chartered deliverables	Group

The team will demonstrate its work at the targeted Management World event and other agreed events.  Promotion of the demonstartion will be as desribed in the project marketing plan.

Owner

	Name	Description	Type
	Project Leader	The person appointed by the team to lead the project	Role

Performed By

	Name	Description	Type
	Marketin Lead	The person who will lead the marketing campaign for the project	Role
	Project Team	The team of members responsible for developing the chartered deliverables	Group

The marketin plan will include information on how the team will promote their project.  It will include the key marketing messages, the marketing channels that wil be used e.g. email, web and the timing of the marketing campaign.  It wil also include the key contact details of the person(s) who will be rsponsible for the marketing

Owner

	Name	Description	Type
	Marketin Lead	The person who will lead the marketing campaign for the project	Role

Completion of the project deliverables, as described in the project charter, may be completed eiether before the demostartion or soon afterwards.

Depending on the nature of the deliverables they may be submitted for approval using the TM Forum Deliverable Approval Process.  Devliverables that do not need approval must be submitted to the Director, Catalyst Programs, who will reveiew the deliverables and post them into the appropriate library.

Owner

	Name	Description	Type
	Project Leader	The person appointed by the team to lead the project	Role

The team must complete the project deliverables described in its project charter using the appropriate deliverable template.

Owner

	Name	Description	Type
	Project Leader	The person appointed by the team to lead the project	Role

Projects may continue to another phase of work but must follow the same process for approval of any additional work.

Owner

	Name	Description	Type
	Director, Catalyst Program	Responsible for all aspects of the Catalyst program	Person