Page tree
Skip to end of metadata
Go to start of metadata

* indicates that this field is required

Project Name*Open API Program
IPR Mode*

RAND

Explanations of each mode is available at http://www.tmforum.org/IPRPolicy/11525/home.html

Project Start Date*January 2018
Project End Date*December 2018
Type of Project*Development Project
Strategic ProgramAgile Business & IT
Previous Project CharterOpen API Program Charter (R17.5) - A Core Project Area Charter
Project Workspace LinkAPI Project Home
Project Sponsor*
Project Team Lead*
TM Forum Staff Support

 

1. Table of Contents

2. Project Overview


Developing best practices and standards in certain fields greatly benefits from frequent joint work or exchange of live collaboration materials with other TM Forum projects. To facilitate low-friction collaboration between such projects, this RAND Project Charter is a member of a larger “Core Project Area” which holds the RAND Project Charters;  Frameworx, Zero-touch Orchestration, Operations & Management (ZOOM), APIs & Open Digital Architecture (ODA)

The Core Project Area Project Charter may be seen here; Core Project Area Charter (R18.0) 


 

One of the most important parts that the Forum provides is a set of standard interfaces that enable rapid, repeatable, and flexible integration among operations and management systems.

  • Reduce full lifecycle costs of networks and services through use of well documented, consistent interfaces
  • Integrate management systems with each other while minimizing cost and risk
  • Reduce cycle time for putting new network equipment in service with shorter management system integration and test cycles
  • Reduce cycle time for getting new services to market with repeatable management systems integration
  • Reduce development costs for adding new management capabilities with developer kits and reusable designs and code
  • Easily share management information across departments, subsidiaries or with partners 

 

The work of the Open API Project is to provide APIs that allow simple and coherent management of any given service and provide developers key design patterns to enable rapid implementation across both the members of the Forum as well as the larger digital ecosystems outside of TM Forum.

Migration of machine readable artifacts to Apache 2.0 license mode in R18.0

It is the TM Forum’s intent to re-issue the existing TM Forum Open APIs under Apache 2.0. Per the Bylaws, we have created a new project and ask all software contributors to existing APIs to join this area with the knowledge that the resulting APIs will be published with Apache 2.0 license. The APIs will be up versions and new notice and licensing statements added.

The human readable artifacts (Open API Specifications, Conformance Profiles and SID mapping documents) will continue to be published under the RAND license mode from work carried out under this charter.

Computer readable artifacts (Swagger files, Postman files, RI/CTKs) will henceforth be published under the Apache 2.0 license mode under a related but different charter, see: API Apache 2.0 Project (R18.0)

Both sets of artifacts will be consumable from one place, in the Open API portal, here: Open API Table

3. 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...
As a..TMF member
I need to...have a standard means to monitor performance, bill and settle accounts, on-board new partners, order and provision services, and so on
So that I can...move quickly in the market and work with the broadest set of vendors, partners and channels
To do this I need...a complete set of easily adoptable APIs that are common across both the TMF community and the broader IT ecosystem

  

As a..OTT developer
I need to...extend my solutions into a number of TM Forum members
So that I can...bring existing and new products and services to a broad market 
To do this I need...a rich set of APIs that provide a standard and reasonable means to integrate the various business systems

  

As a..TMF member
I need to...be able to work with all the APIs provided by TM Forum in a consistent and expected manner
So that I can...contain costs and deliver solutions in the shortest time possible
To do this I need...the APIs from TM Forum to be consistent and follow common patterns that are generally adopted across the wider developer community

 

4. Dependencies

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

Project NameINPUT FROM / OUTPUT TO / JOINT WITHCOMMENTS (describe nature of Input / Output / Joint)API ContactOther Project Contact
API-Apache 2.0OAPI specifications team approved and published to the API-Apache 2.0 project where the Swagger, Postman, RI and CTKs will be constructed  
API-Apache 2.0IOnce the API-Apache files have been uploaded or edited in the tmforum-apis GitHub organization and been "promoted" to a public copy, this is then ready for review.  
Customer Centricityx   
Data Analyticsx   
IOE & Digital Ecosystemsx   
DMMx   
Explore AIx   
Explore Blockchainx - nothing in R18.0Blockchain lab? - Is there scope for complementary work? - Future work 
FrameworxJointAPI / SID mapping.
Open Digital ArchJointONAP product suiteLudovic Robert 
Smart CityI & OMerging Open Digital APIs with FiWARE APIs - API specification workPierre Gauthier 
ZoomJointNaaS product suite

 

5. 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.

* indicates that this is a required field or role.

RoleName*Company* Confluence “@” mentionComments
Project Co-Team LeadAndreas PolzInfonova 
MentorPierre GauthierTM Forum 
Sponsor*Laurent LeboucherOrange 
Subject Matter ExpertPierre GauthierTM Forum 
StaffJoann O'BrienTM Forum 

 

Role Descriptions & Responsibilities given in section 11

 

6. Project Workstreams and Deliverables

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

6.01: API Design Guidelines

Workstream Leader: Pierre GauthierStephen Harrop

How do we create industry leading and technologically leading APIs that ensure capability, connectivity and exposure consistency across the ecosystem?
Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.01.1API Design Guidelines 4.0TMF630

DG4.0 - support for messaging & streaming

      
6.01.2  New swagger template      
6.01.3  Tie in the Tosca service definition with our catalogue management APIs      
6.01.4  Simplification and Consummability of DG - create a version of the Design Guidelines - discuss and resolve how to address and what format such a deliverable should take     

 

6.02: API Processes & Governance

Workstream Leader: Stephen Harrop

How do we manage the wide spread of demands, priorities and resource challenges to optimise the delivery and maintenance of the TM Forum Open APIs?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.02.1  Need to tie up the technical architecture with stronger governance - all deliverables - 25% have no postman - clear plan & priority to complete existing and clarity of requirements for new ones.      

 

6.03: Road mapped APIs

Workstream Leader: Andreas Polz

How do we ensure that the TM Forum Open APIs, planned to be developed in the API roadmap, are brought to full implementation; spec, CP, SID mapping, swagger, postman, RI & CTK?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.03.1  Priority APIs from API roadmap - Clear plans & delivery of all the each step & product ownership to execute on full deliverable set      
6.03.2Trouble TicketTMF621 - stretchProvides a standardized client interface to Trouble Ticket Management Systems for creating, tracking and managing trouble tickets among partners as a result of an issue or problem identified by a customer or another system. Examples of Trouble Ticket API clients include CRM applications, network management or fault management systems, or other trouble ticket management systems (e.g. B2B).     L: Jacob
C: Luis
C: Ludovic
M: yanivgi@amdocs.com
6.03.3Customer ManagementTMF629 - stretchProvides a standardized mechanism for customer and customer account management, such as creation, update, retrieval, deletion and notification of events.     L: mariano.belaunde@orange.com
M: patricia@szita@accenture.com
6.03.4Party ManagementTMF632 - stretchProvides standardized mechanism for party management such as creation, update, retrieval, deletion and notification of events.
 Party can be an individual or an organization that has any kind of relation with the enterprise.
     L: sophie.bouleau@orange.com
M: calogero.cascio@accenture.com
6.03.5Product Inventory ManagementTMF637 - stretchA standardized mechanism for product inventory management such as creation, partial or full update and retrieval of the representation of a product in the inventory. It also allows the notification of events related to the product lifecycle     L: ludovic.robert@orange.com
M:  Jonathan.Goldberg@amdocs.com
6.03.6Service Inventory ManagementTMF638 - stretchProvide a consistent/standardized mechanism to query and manipulate the Service inventory     L: nicoleta.stoica@vodafone.com
C:ludovic.robert@orange.com
M: Cecile.ludwichowski@orange.com
6.03.7Service Ordering ManagementTMF641 - stretchThe REST API for Service Order Management provides a standardized mechanism for placing a service order with all of the necessary order parameters. It allows users to create, update & retrieve Service Orders and manages related notifications.     L: ludovic.robert@orange.com
M: Cecile.ludwichowski@orange.com
6.03.8Privacy ManagementTMF644 - stretchThe Privacy Management API provides standardized mechanism for privacy profile types, privacy profiles and privacy agreements such as creation, update, retrieval, deletion and notification of events.     L: Orange?
6.03.9Service QualificationTMF645 - stretchService Qualification API is one of the Pre-Ordering Management APIs. Service Qualification API goal is to provide service availability at Customer location.     L: Ludovic Robert
L: Taka
C: luis.velardetazon@telefonica.com
M: syed_ah@infosys.com
6.03.10AppointmentTMF646 - stretchThe Appointment API is one of the Pre-Ordering Management APIs. The appointment API provides a standardized mechanism to book an appointment with all the necessary appointment characteristics. First, the API consists in searching free slots based on parameters, as for example a party. Then, the appointment is created. The appointment has characteristics such as nature of appointment, place of appointment.     L: sophie.bouleau@orange.com,
M: yanivgi@amdocs.com
6.03.11Performance Management ThresholdingTMF649 - stretchThis covers the Threshold aspects of Performance Management, also named Performance Threshold Management or PM Threshold.
Provides a standardized mechanism for performance management such as creation, partial or full update and retrieval of the resources involved in performance management (Measurement Production Job, Measurement Collection Job, and Ad hoc Collection). It allows also notification of events related to performance
     L: milind.2.bhagwat@bt.com,
C: pgauthier@tmforum.org,
C: stephen.fratini@ericsson.com
6.03.12Service Test ManagementTMF653 - stretchPlacing a service test with all of the necessary test parameters. A service test is a procedure intended to check the quality, performance, or reliability of a service.     L: haohongxia@huawei.com,
C: mariano.belaunde@orange.com
6.03.13Prepay Balance ManagementTMF654 - stretchPrepay API manages the balance, recharge (top-up) and transfer resources     L: luis.velardetazon@telefonica.com
M: Jonathan.Goldberg@amdocs.com
6.03.14Service Quality ManagementTMF657 - stretchDefines a standard interface designed to simplify the integration task of an SQM application with different partners and respective Digital Operations Centers.     L: haohongxia@huawei.com,
C: mariano.belaunde@orange.com
6.03.15Shopping CartTMF663 - stretchStandardized mechanism for the management of shopping carts. Including creation, update, retrieval, deletion and notification of event. Shopping Cart entity is used for the temporarily selection and reservation of product offerings in e-commerce and retail purchase. Shopping cart supports purchase of both tangible and intangible goods and service (e.g. handset, telecom network service). The charge includes the one-off fee such as the fee for handset and the recurring fee such as the fee of a network service.  Shopping Cart contains list of cart items, a reference to party or party role (e.g. customer) or contact medium in case of unknown customer, In addition the calculated total items price including promotions.     L: jacoba@amdocs.com,
C: Huawei
C: nicoleta.stoica@vodafone.com
C: Orange
M: Jonathan.Goldberg@amdocs.com
6.03.16Digital Service Management APITMF665 - stretchIdentifies all the relevant resources and document also addresses their lifecycle. This is not an exhaustive list and document in its final form will address in detail the specification as per DSRA, DPRA, ZOOM and other relevant initiatives at TMforum.     L: dirk.rejahl@bearingpoint.com,
C: pgauthier@tmforum.org,
C: johan.vandenberghe@nokia.com
6.03.17Partnership Type ManagementTMF668 - stretchStandardized mechanisms for creating partnership types. It is one of the APIs involved in an onboarding process. Identifies a type of a partnership between parties, including the list of role types that are permitted (i.e Buyer, Seller, Developer). Role types may refer to agreement specifications to be signed by parties playing the role. 
The API allows the retrieval, creation, update and deletion of partnership type and its owned sub-resources.
     L: Mariano
M: mbesson@tmforum.org
6.03.18Party Role ManagementTMF669 - stretchA standardized mechanism for general party roles and includes operations such as creation, update, retrieval, deletion and notification of events. Notice that for the management of customers there is a specific Customer Management API.
Party Role management API manages the following data resources: PartyRole
     L: mariano.belaunde@orange.com,
M: cecile.ludwichowski@orange.com
6.03.19PromotionTMF671 - stretchUsed to provide the additional discount, voucher, bonus or gift to the customer who meets the pre-defined criteria. Using promotion, the enterprise is able to attract the users and encourage more consumption, especially continuous purchases. Normally Promotion is not regarded as one type of product or product offering. It is often applied when the customer buys the product offerings with the price or amount surpassing the certain limit     L: maxu@huawei.com
6.03.20User Roles & PermissionsTMF672 - stretchA user role is defined as the entity that defines a set of privileges covering various functions and/or manageable assets. When a user is assigned  a given role then it is actually allocated all the privileges defined for that role type and the corresponding permissions are created for that user     L: luis.velardetazon@telefonica.com,
C: Huawei
6.03.21Payment ManagementTMF676 - stretchThis API allows the following operations. Notify of a performed payment, retrieve a list of payments filtered by a given criteria, retrieve a single performed payment, notify of a performed refund, retrieve a list of refunds filtered by a given criteria and retrieve a single performed refund.     L: luis.velardetazon@telefonica.com
6.03.22User InteractionTMF683 - stretchA User Interaction captures information about past interactions in order to re-use it in future ones. This allows agents to serve users better by knowing the steps they went through. It also allows customers to see better the actions they have performed and how they interacted with us.     L: luis.velarde@telefonica.com
6.03.23Shipping TrackingTMF684 - stretchShipment Tracking captures information about the current status of the shipment, the past checkpoints and the estimated arrival date. Via this API, tracking information can be retrieved by providing an order Id or the shipping company’s tracking id.     L: guillermo.martinezdelcamino@telefonica.com
6.03.24Event management

TMFnnn - stretch

Event is any of the action triggered by the human or the system which requires the notification to the other system.     L: levente.janovszki@ncia.nato.int
6.03.25Experience ManagementTMFnnn - stretchExperience is the data and their impact which reflect the feeling of the user of the system. Based on the experience, the user can give judgment to the system about its usability     L: Ericsson?
C: Proximus
6.03.26Federated IdentityTMFnnn - stretchIdentity management is about the management of principals of any kind (persons, objects, …) and their access to resources in an open environment which can span across different enterprise boundaries. It relies on authentication, authorization and consent mechanisms to protect privacy with a simple and easy user experience. Different parties can provide identity services (operators, social networks, GSMA, …).     L: luis.velardetazon@telefonica.com,
C: Ericsson?
6.03.27Resource Pool ManagementTMFnnn - stretchRPM API offers the available capacity confirmation of Services / Resources and pre-reservation of them BEFORE the order     L: nakamura.takayuki@nttcom.co.jp,
C: pgauthier@tmforum.org
 DSMSee 665 aboveKeep here or separate workstream?      

 

6.04: Open API components

Workstream Leader: Pierre GauthierStephen Harrop

How do we build up TM Forum Open API suites, based on use case and requirements analysis, to support specific industry challenges?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.04.1What is a C & P for a conformance suite?

TRnnn - API Component Suite concepts & principals

TRnnn - template

TRnnn: what is an API component suite?

TRnnn: How should others document their component suites in an efficient & repeatable way?

     Pierre Gauthier
6.04.2 TRnnn: NaaS component suiteNetwork as a Service (fka End-to-End NFV Management APIs)     Johanne Mayer
6.04.3 TRnnn: IoTIoT component suite     Axel Pieuchot
6.04.4 TRnnn: Self CareSelf Care Application component suite     
6.04.5 TRnnn: MEF product suite      Ludovic Robert
6.04.6 TRnnn: ONAP product suite      Ludovic Robert

 

6.05: API/SID mapping Task Force

Workstream Leader: Cecile LudwichowskiMichel Besson

How do we ensure that the TM Forum Open APIs, developed by a wide collaboration community and crowd sourced, have a consistent information model and data model view - with each other and with SID?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.05.1  White Paper: New overall document - the generalities of how mapped - eg 15 pages for ALL the APIs.      
6.05.2API / SID mappings in progress

TMF663A, TMF653A, TMF633A, TMF638A, TMF673A, TMF658A, TMF662A, TMF645A, TMF621A, TMF639A

 

TMF663 - Shopping Cart: Jonathan Goldberg (Amdocs), TMF653 – Service Test: Hongxia (Helen) Hao (Huawei), TMF633 - Service Catalog Management 17.5 : Cécile Ludwichowski (Orange) & Michel Besson (TMF), TMF638 – Service Inventory Management: Cécile Ludwichowski (Orange) & Michel Besson (TMF), TMF673 – Geographic Address Management - Luis Velarde (Telefonica), TMF658 - Loyalty: Narayanan Krishnamurthy (Infosys), TMF662 - Entity Catalog: Kamal Maghsoudlou (Ericsson), TMF645 - Service Qualification: Atif Syed Husain (Infosys), TMF621 – Trouble Ticket: Yaniv Gigi (Amdocs)  or maybe another colleague (Jacob Avraham), TMF639 - Resource Inventory : Jonathan Goldberg (Amdocs)

      
6.05.3API / SID assigned mappingsTMF640A, TMF654A, TMF632A, TMF666A, TMF668A, TMF669A, TMF620A, TMF641A, TMF674A, TMF675A, TMF655A, TMF680A, TMF681A, TMF657A, TMF671ATMF640 - Service / Resource configuration & Activation: Atif Syed Husain (Infosys), TMF654 – Prepaid Balance: Jonathan Goldberg (Amdocs), TMF632 – Party: Calogero Cascio (Accenture), TMF666 - Account Management: Cécile Ludwichowski (Orange), TMF668 - Partnership type (previously named Onboarding TMF650): Michel Besson (TMForum), TMF669 - Party Role: Cécile Ludwichowski (Orange), TMF620 – Product Catalog Management Kamal Maghsoudlou (Ericsson), TMF641 - Service Ordering 16.5: Cécile Ludwichowski (Orange) & Michel Besson (TMF), TMF674 – Geographic Site - Luis Velarde (Telefonica), TMF675 – Geographic Location - Luis Velarde (Telefonica), TMF655 – Change - Hongxia (Helen) Hao (Huawei), TMF680 – Recommendation (R 17.5) - Hongxia (Helen) Hao (Huawei), TMF681 – Communication (R 17.5) - Hongxia (Helen) Hao (Huawei), TMF657 – Service Quality - Hongxia (Helen) Hao (Huawei), TMF671 – Promotion - Hongxia (Helen) Hao (Huawei)      
6.05.4API / SID mappings as yet unassignedTMF651A, TMF667A, TMF652A, TMF623ATMF651 – Agreement, TMF667 – Document, TMF652 – Resource Order Management, TMF623 – SLA Management      
6.05.5Mappings that require revisionTMF637A, TMF678ATMF637 - Product Inventory: Jonathan Goldberg (Amdocs), Based on API 16.5, new release in 17.5. TMF678 – Customer Bill Management: Cécile Ludwichowski (Orange), Based on SID 17.0, new SID 17.5 changes mapping related to Account      

 

6.06: Finalize Part Completed APIs (API Spec + CP + API/SID mapping)

Workstream Leader: Pierre GauthierStephen Harrop

How do we ensure that the TM Forum Open APIs, developed by a wide collaboration community, are brought to full implementation; spec, CP, SID mapping, swagger, postman, RI & CTK? 

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.06.1  Outstanding items & priority as set by 6.02 - Complete the API table for existing APIs      

 

6.07: API Tooling and Automation Support

Workstream Leader: Stephen HarropMariano Belaunde

How do we create a low friction and repeatable way for our collaboration community to create consistent and low effort swagger files, RI & CTK?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.07.1Update to support DG3.0 Update to support DG3.0      
6.07.2RI/CTK tooling improvements Develop the initial RI/CTK tooling      
6.07.3Micro Services Lab Micro Services Lab      

 

6.08: SDO Collaborations

Workstream Leader: Pierre Gauthier

How do we collaborate with other SDOs build up TM Forum Open API suites to support specific industry challenges?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.08.1MEF support 

Finalize Part Completed APIs (CTK)

New APIs for MEF support - eg trouble ticket

Apache version of MEF API

     Ludovic Robert
6.08.2ONAP TMF API Technical ArchitectureTRnnn

TR ONAP TMF API Technical Architecture - Technical paper exploring the technical architecture requirements to support an ONAP service enablement

     Ludovic Robert
6.08.3OSM, …        
6.08.4ETSI, …        

 

6.09: Catalog Management

Workstream Leader: Jonathan Goldberg

How do I, as service provider or vendor partner utilize enterprise catalogs to enable product offer creation in an open, efficient and easily understood manner?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.09.1 TMF620

Product Catalog API: Check if there are JIRA issues left to be processed

     Jonathan Goldberg
6.09.2 TMF633

Service Catalog API: Check if there are JIRA issues left to be processed; This API is going to be presented to ONAP. Plus new project under OPEN API Apache terms

     Ludovic Robert
6.09.3 TMF634

Resource Catalog API: JIRA Issues Expected (None identified yet)

      
6.09.4 tbd

Product Catalog API Reference Implementation: to be Completed

      
6.09.5 tbd

GB978 Interface to Interface Catalog Interface: R18.0 work not yet identified:

      
6.09.6 TMF662

Entity to Entity Catalog API: R18.0 work not yet identified:

      

 

6.10: Crowd-Sourced APIs

Workstream Leader: Stephen HarropAndreas Polz

How do we ensure that the TM Forum Open APIs, developed by a crowd sourced community, are brought to full implementation; spec, CP, SID mapping, swagger, RI & CTK?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.10.1  Clear plans & delivery of all the crowd source phases & review of each step & product ownership to execute on full deliverable set      

6.11: Open MicroServices and APIs

Workstream Leader: Pierre Gauthier

How do we create industry leading and technologically leading APIs that have design patterns that are optimized for the cloud based ecosystem?

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.11.1  Technical recommendation on how to best use Open APIs within the context of a microservices architecture - how to use the APIs to front the microservices architecture      

6.11.2

Open MicroServices

TRnnn

FAQ , Templates, Specifications and Cloud Platform based implementations on proposed MicroService and API architectures - First deliverable is a TR prior to Lisbon Pierre Gauthier, Nicoleta Stoica

 

 

 

 

 

 

 

6.12: Event Streaming & Messaging

Workstream Leader: Pierre Gauthier

Ref #

Deliverable short name

Deliverable type/numberDescriptionAudienceIntended usePlan for 1st 90 daysPlan for end of cycleSponsor / consumer supportNotes
6.12.1  Event Streaming & Messaging      

7. Member Validation and Feedback Approach

Deliverables require validation and feedback. If the development team has a broad range of Members and Service Providers, validation may be within the team, however if the range of Members and Service Providers is weak, after Team Approval, deliverables must be validated beyond the team. Teams must state their Member & Validation approach here:

Validation Activity Approach

Spec Jams

Validation Activity Description

Face-to-face meetings to resolve & clarify requirements and implementation design, as appropriate to the audience

Dependencies

 

Comments

8. 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

Contribution and feedback management

Provided by default

GitHub

Code repository (if applicable)

YES

Other

Public website API Portal

YES

9. Liaison Relationships

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

Name of Organization

Is this a New or Existing relationship?

Linkages and/or Scope of work

Contact person

Comments

MEF

existing

Sharing API standards

 

 

FIWAREexistingSharing API standards  
Eclipse/Papyrusexistinguse of Tooling  
Open NFVTentative   

10. Charter History

Version Date Comment
Current Version (v. 20) Aug 17, 2018 09:00 Derek Flexer
v. 19 Mar 13, 2018 09:14 Adrienne Walcott
v. 18 Mar 12, 2018 09:55 Derek Flexer
v. 17 Mar 08, 2018 06:42 Derek Flexer
v. 16 Mar 05, 2018 05:06 Derek Flexer
v. 15 Mar 01, 2018 12:32 Derek Flexer
v. 14 Mar 01, 2018 12:28 Derek Flexer
v. 13 Mar 01, 2018 06:23 Derek Flexer
v. 12 Mar 01, 2018 04:20 Derek Flexer
v. 11 Feb 28, 2018 10:08 Derek Flexer
v. 10 Feb 28, 2018 09:03 Derek Flexer
v. 9 Feb 27, 2018 10:35 Derek Flexer
v. 8 Feb 27, 2018 10:30 Derek Flexer
v. 7 Feb 27, 2018 10:28 Derek Flexer
v. 6 Jan 23, 2018 09:10 Derek Flexer
v. 5 Jan 23, 2018 06:30 Derek Flexer
v. 4 Jan 23, 2018 06:28 Derek Flexer
v. 3 Jan 23, 2018 06:25 Derek Flexer
v. 2 Jan 23, 2018 05:33 Derek Flexer
v. 1 Jan 23, 2018 05:07 Derek Flexer

11. Role Definition & Responsibilities

 Role Descriptions & Responsibilities

Project Team Lead:

  • Ensure project is developed in line with TM Forum IPR policy
  • Encourage all participants to take an active role in the project
  • Ensure participants have a clear understanding of what they need to complete and when
  • Drive the project team for on time delivery
  • Lead the design, planning and execution validation activities
  • Identify key companies required to position for industry adoption

Mentor:

  • Aid the team to maintain focus on delivery
  • Act as a source of expertise for the team
  • Join project calls to assist with blockages
  • Seek out expert resource to help as required
  • Be a guide and link to the wider Program

Sponsor:

  • Articulate the Industry User Story
  • Act as a Champion for the team
  • Review progress at six weekly intervals to ensure relevance
  • Champion final deliverables at Nice/San Jose
  • Drive Adoption in own organization by championing deliverables as beta versions of solutions to be developed

Participant:

  • Develop collaborative solutions as in accordance with the developed charter and inline with Collaboration process
  • Participate actively in team working meetings / sessions
  • Complete tasks as agreed with the team or workstream leader

Observer:

  • Choose to observe and monitor the progress of a project team
  • Use the insights gained to share observed advancements within your organization
  • Ensure planned deliveries are aligned with product roadmap in your organization to gain maximum R&D acceleration value
  • Align training and education within your organization to gain maximum value of cost & risk reduction and future proofing your organization

Reviewer:

  • All activities of observer plus…
  • Review all outputs from team and provide quality timely feedback ensuring output aligns with business and technology requirements of your organization
  • Participate in validation activities, these may be online or face to face.
  • Monitor Collaboration Events & Activities page for all latest review activities

Subject Matter Expert:

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

Workstream Lead:

  • For your agreed workstream;
  • Ensure project is developed in line with TM Forum IPR policy
  • Encourage all participants to take an active role in the project
  • Ensure participants have a clear understanding of what they need to complete and when
  • Drive the project team for on time delivery
  • Lead the design, planning and execution validation activities
  • Identify key companies required to position for industry adoption

12. Legal Notice

Copyright © TM Forum 2018. All Rights Reserved.

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.

Direct inquiries to the TM Forum office:

4 Century Drive, Suite 100
Parisppany, NJ  07054 USA
Tel No.  +1 973 944 5100
fax No.  +1 973 944 5110
TM Forum Web Page: www.tmforum.org

  • No labels