Liaison Process

Process Narrative
 




Document Preferences 

Table of Contents

   1.0   Internal Liaison Request 
1.1   Start Process
1.2   Internal group
1.3   Draft Work Register
1.4   Submit Liaison Activity Request
1.5   Request for ITU Recommendation?
1.6   Prepare approval requests
1.7   Request Approval
1.8   Approval Decision
1.9   Approval Committee
1.10   Reject Request
1.11   Submit Documentation to ITU
1.12   Monitor Liaison
1.13   Existing Liaison Agreement?
1.14   Circulate request to IGAC
1.15   Final Work Register
1.16   Develop Liaision Agreement
1.17   Draft Liaison Agreement
1.18   Negotiate Liaison Agreement
1.19   End process
   2.0   External Liaison Request 
2.1   Start Process
2.2   Liaison Request Received
2.3   Circulate request to IGAC
2.4   IGAC review
2.5   Proceed with Liaison
2.6   Maps to Existing Work Group
2.7   Send Request to Team(s)
2.8   Project Team(s) Reviews Liaison
2.9   Develop Work Register
2.10   Work Register Review
2.11   Monitor Liaison
2.12   Send to TPC for Review
2.13   Maps to existing project teams(s)
2.14   Intiate new project?
2.15   Project initiation process
2.16   External industry body
2.17   Reject liaison request
2.18   End process
2.19   Raise New Requirements
2.20   CP flow - Requirements Capture & Analysis


1.0  
Internal Liaison Request  Process Narrative

Internal Liaison Request
Description This process handles liaison activity requests originating from inside the TM Forum membership
Internal Liaison Request

Purpose

This process explains how liaison requests from external bodies are processed and how the TM Forum intiaties liaison requests.

Approval List

Name Description Type
Approval Committee Group
IGAC Group

Distribution List

Name Description Type
Approval Committee Group
IGAC Group
Liaison Director Role
TPC Group


1.1   Start Process 

This process handles requests for liaison from inside the TM Forum membership. This process is in accordance to the TM Forum Operating Guide GB919.  Errors, omissions, and request for changes can be directed to Debbie Burkett dfburkett@tmforum.org.

Owner

Name Description Type
IGAC Group
Liaison Director Role


1.2   Internal group 

May consist of TM Forum project teams, program groups, councils, board committees, and staff

Owner

Name Description Type
Liaison Director Role


1.3   Draft Work Register 

Internal working teams may initiate liaison activity for a variety of reasons including, but not limited to::
- attempts to leverage existing work from an external organization
- Exchange draft documents for comments and collaborative development
- Submit completed work for accredited standards recognition

Requests are documented using the Work RegisterTemplate found in the Industry Group Liaison and Advisory Council document workspace in the Industry Group Templates folder.  http://www.tmforum.org/cws/helper_controls/download.aspx?ID=10713&team_ID=180.

Owner

Name Description Type
Project team(s) Group


1.4   Submit Liaison Activity Request 

Incoming liaison requests are logged into the Liaison Master Tracking database, the correspondence is copied to the Industry Group Liaison & Advisory Council CWS. A courtesy reply is sent to the initiator with an estimated formal response date.  

Linked Resources

Name Description Type
Liaison Request Received Circulate request to IGAC Activity

Owner

Name Description Type
Liaison Director Role


1.5   Request for ITU Recommendation? 

Additional information can be retrieved from the TM Forum Operating Guide - GB919, Reference 35, and the ITU website.  


1.6   Prepare approval requests 

All requests for ITU recommendations must be approved by the TM Forum Approval Committee.  The project team's Liaison Point of Contact (LPOC) will ensure the required ITU cover letter and complete documentation related to the requests is posted in the submitted document folder of the Techical Program Council and the requesting team's document workspace.  An Approval Committee Submission Form is prepared and forwarded to the Liaison Director to initiate the approval process.

References:   Operating Guide GB919, Ref 35.  AC Submission Form - TMF413, Version 1.0

Performed By

Name Description Type
Liaison Director Role
LPOC Liaison Point of Contact representing TM Forum for this work register Role


1.7   Request Approval 

Send request to Approval Committee

Owner

Name Description Type
Liaison Director Role


1.8   Approval Decision 

The approval committee reviews the details of the request to determine if the scope, objectives and work plan is reasonable and the work items appear to have adequate resources.  The maturity of the document being submitted weighs heavily on the decision to grant authorization to submit.  

Owner

Name Description Type
Approval Committee Group


1.9   Approval Committee 

1.10   Reject Request 

The Approval Committee coordinator will send the Approval Committee decision to reject the request, along with any comments and suggestions for improving the approval chances.


1.11   Submit Documentation to ITU 

Upon receipt of the approval to proceed, the team will submit the material to the ITU.


1.12   Monitor Liaison 

The master database is updated and progress monitoring begins.  The primary contact person will provide routine status reports to the IGAC, participate on the IGAC conference calls; and represent the views of the TM Forum on external liaison meetings.  If the liaison activity stalls or fails to make progress, the IGAC will take necessary action.

Owner

Name Description Type
IGAC Group


1.13   Existing Liaison Agreement? 

The Liaison Tracking data base is consulted to determine if an existing liaison agreement is in place with this organization.  

Owner

Name Description Type
Liaison Director Role


1.14   Circulate request to IGAC 

.An email is sent to the Industry Group Liaison & Advisory Council to describe the nature of the request, a “reply by” date, and the link to the correspondence posted on the CWS.

Owner

Name Description Type
Liaison Director Role


1.15   Final Work Register 

The terms of the work register are agreed with the affected industry groups, including detailed work plan, document exchange, and meeting frequency.


1.16   Develop Liaision Agreement 

Includes necessary steps to establish a new liaison agreement with another organization


1.17   Draft Liaison Agreement 

The Liaison Agreement is used to set the overall business context within which the parties agree to cooperate.  Liaison Agreements have a long-life which will be alternately active or passive over a period of time.  Liaison Agreements do not contain details about specific work projects (which are documented using the Work Register).  

Owner

Name Description Type
Liaison Director Role
LPOC Liaison Point of Contact representing TM Forum for this work register Role


1.18   Negotiate Liaison Agreement 

The terms and conditions of the business relationship is negotiated to satisfaction with the other organization.  In cases where the other industry group may have processes which make this difficult, but there is strong interest with both parties, all reasonable attempts should be made to develop a working relationship without compromising the TM Forum members.   After the business terms have been agreed to, the next step is to finalize the work register.  

Owner

Name Description Type
Liaison Director Role


1.19   End process