Table of Contents

Project Overview

The Catalyst project will demonstrate a practical implementation of a closed loop functionality, used to heal and optimize a converged network running on both traditional and virtualized infrastructures, relying on both network and services inputs. The focus will be on Agile IT contribution to the efficiency of services leveraging it even further to customer experience level. Several standards, recommendations and interfaces will be used to support the integration, including TM Forum PM & PIE and 3GPP PM /CM. The catalyst is also related to recent TM Forum & ETSI NFV work and to NGMN recommendations.

User Stories

Provide a high-level description of how an end-user might use the output of the project.

If desired, copy and paste the table below to create multiple instances of the table and complete it for each user story.

As a..

I need to...

So that I can...

To do this I need...

Dependencies

Add in other projects and Frameworx dependencies this project will have. Please enter if your project will require INPUT FROM or produce OUTPUT TO the named projects/Frameworx. In the COMMENTS column describe the nature of the input or output

Project Name

INPUT FROM or OUTPUT TO

COMMENTS (describe nature of Input/Output)

Project Contact

Participants

This section identifies the human resources and skills required by the project to successfully deliver the items listed in this charter. Unless otherwise noted, the level of commitment of all project participants is Best Effort.

At the time the charter is written, the individuals listed below are considered tentative participants. When the charter is approved, the tentative participants will be notified and they can “join” the project in the online community. From that point forward the project resources will be maintained and viewable in real time.

Provide support and guidance to a project team in your particular area of expertise

Project Workstreams and Deliverables

The project workstreams and deliverables for this project are introduced in the sections below.

If there are multiple workstreams within this project, copy and paste the table below to create multiple instances of the table and complete it for each.

Workstream 1:

Workstream Leader:

#

Deliverable Name*

Deliverable Type*

Deliverable

Description & Purpose*

DeliverableStart Date*

PlannedSubmission Date or Release Number*

Work Requests to be Implemented

Dependencies

Comments

1

2

3

Workstream n:

Workstream Leader:

#

Deliverable Name*

Deliverable Type*

Deliverable

Description & Purpose*

DeliverableStart Date*

PlannedSubmission Date or Release Number*

Work Requests to be Implemented

Dependencies

Comments

1

2

3

Member Validation and Feedback Approach

In the agile model, once a team approved draft has been created, a team should perform at least one, preferably two, member-facing validating and feedback activities. These could be online or face to face. For example, DevOps testing.

If there are multiple activities within this project, copy and paste the table below to create multiple instances of the table and complete it for each activity.

Activity Type

Activity Description & Purpose

Planned Date

Required Audience

Dependencies

Comments

Project Tooling

Indicate the tooling required for project success.

Product

Key Functions

Needed for Project?

Confluence Space

Document creation and publishing

Provided by default

JIRA Space

Agile project management

GitHub

Code repository

Trello

Project Management

Other

Liaison Relationships

Please indicate if this project has or plans to have a relationship with other External Standards Organizations (SDOs).

Legal Notice

This document and translations of it may be copied and furnished to others, and derivative works that comment on or otherwise explain it or assist in its implementation may be prepared, copied, published, and distributed, in whole or in part, without restriction of any kind, provided that the above copyright notice and this section are included on all such copies and derivative works. However, this document itself may not be modified in any way, including by removing the copyright notice or references to TM FORUM, except as needed for the purpose of developing any document or deliverable produced by a TM FORUM Collaboration Project Team (in which case the rules applicable to copyrights, as set forth in the TM FORUM IPR Policy, must be followed) or as required to translate it into languages other than English.

The limited permissions granted above are perpetual and will not be revoked by TM FORUM or its successors or assigns.

This document and the information contained herein is provided on an "AS IS" basis and TM FORUM DISCLAIMS ALL WARRANTIES, EXPRESS OR IMPLIED, INCLUDING BUT NOT LIMITED TO ANY WARRANTY THAT THE USE OF THE INFORMATION HEREIN WILL NOT INFRINGE ANY OWNERSHIP RIGHTS OR ANY IMPLIED WARRANTIES OF MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE.