Anda di halaman 1dari 12

NGOSS Compliance

TMF Booth Presentation: A Strategy Overview TMW, Nice 2005

Compliance Program
Joining forces with LifeCycle team Developing NGOSS Compliance Strategy
Reviewing direction with TMF Technical Committee Building an NGOSS Compliance Roadmap TMF Teams contributing domain perspectives Co-ordinating work program through 2005

Focusing on high-priority areas for

Compliance assessment where NGOSS Users can see real benefits

NGOSS Compliance and Lifecycle

Iterate with SANRR

Logical View



Corporate NGOSS Knowledge Shared Knowledge Base Base

Physical View

Implementation On-going
Service Developers View

Service Providers View

Business View compliance

Business drivers
NGOSS compliance needs traceability

Prove that a solution implements a business process Prove that a process can evolve easily

ROI needs agility

Lack of formal definitions

Need transition from UML to test code Rules, models, gates Need a multi-dimension search (compliance catalog)

Information overload!

Goals of NGOSS Compliance within NGOSS The Background Picture

NGOSS Compliance: Some of the Issues Definitions !!

Technical and commercial aspects Linking with other TM Forum work Projected application scenarios (what is used where) Making it Happen Balancing different perspectives Defining the Model for NGOSS Compliance Keeping it Simple! Practical Considerations What is productive to work on? (priorities and benefits) What is feasible to deliver? (available resources) What can it be used for? (ensuring coherent suite of deliverables) What further work will be required? (future evolution) What wider commitment and buy-in is necessary? NGOSS Compliance Strategy Areas of focus Proposed work program and deliverables/milestones

NGOSS Principles Compliance

High level view only

A Model for Compliance Assessment

Lifecycle Compliance
Gates between the NGOSS phases

Methodology Compliance
Development approach, etc

NGOSS Design Compliance

eTOM & SID: Coverage, Levels of Compliance TNA: Architecture, Framework Services

Technology Specific Compliance

Implementation View, black box behavior Mappings to specific technologies (OSS/J, CORBA, etc)

Use/Application Compliance
Deployment scenarios, Use Cases, areas of eTOM and SID

An example: eTOM Compliance

eTOM provides a standard structure, terminology and
classification scheme for describing the business processes of a service provider Coverage assessment
eTOM Process Definitions are textual, not rigorous or formal Coverage assessment partly subjective Can support different levels of compliance

Use/Application Assessment

Customer Complaint

Problem Report to Customer

Assessment made against Business View Contract(s) using eTOM Strengthens precision and rigor of how eTOM is used More objective eTOM Compliance assessment Relates eTOM to a specific scenario and area of application
Mediate & Orchestrate Customer Interactions Manage Contact Manage Request Isolate Problem & Initiate Resolution Customer Relationship Management Retention & Loyalty Report Problem Track & Manage Problem Evaluate & Qualify Problem Service Management & Operations Diagnose Problem Plan & Assign Resolution Track & Manage Resolution Awaiting Resource Trouble Mgt. Awaiting Resource Trouble Mgt. Trouble Analysis Trouble Update Trouble Resolution

Manage Contact

Mediate & Orchestrate Customer Interactions

Analyze & Report on Customer

Close Problem

Retention & Loyalty

Close & Report

Awaiting Resource Trouble Mgt.

Links to the rest of the NGOSS compliance work

NGOSS Business View Contract (TMF 053B)

General Part common to all Views
Header Part, includes name, ID, version, organization Descriptive Part, includes goal, description, search criteria

Business View Contract Structure

Functional Part, including business processes (referencing eTOM processes), policies, capabilities, pre/post-conditions, result status, interaction points and roles, security aspects, context Non-Functional Part, e.g. various limitations/obligations that can affect the contract Management Part, how the contract functionality is managed and by which roles Business Model Part, includes Use Case Diagrams and Text, Interaction Diagrams, Behavioral Diagrams, SID Business Model, eTOM mapping, other business diagrams and artifacts

NGOSS Contracts are a key element in addressing NGOSS Compliance But what Contracts are available ???

Contracts end-to-end
1. Define the Business
(Leadership Team, Business Process Engineers) 1 1

2. Architect the Business Business Contract

(Enterprise IT Architects) 2

Business Contract

System Contract

Corporate Knowledge Shared Base

NGOSS Knowledge Base

Business Contract

System Contract

2 1 2

Deploymnt. Implement Contract Contract

4 3

Business Contract

System Contract Implement Contract

4. Execute the Business


3. Implement the Business

(Development Org.)

Compliance Catalog Solution Compliance Catalog

Is repository of all the
products and solutions which have been tested for NGOSS Compliance based on NGOSS principles. Provides the degree of NGOSS Compliance of products or solutions for different principles Provides Information about type of Technology Support See separate Catalog Demo at the TMF Booth !

Next Steps
NGOSS Compliance being progressed
Building framework Defining Compliance Model Setting priorities Co-ordinating across NGOSS

Need buy-in and support

Compliance is a multi-stranded area! Need input and feedback Need resource and effort to drive towards solutions

Win-win for those involved

Early insight and influence Ensures Products and Solutions benefit from developing Compliance strategy This is where the NGOSS rubber hits the road!

Get involved and contribute to where NGOSS gets real !

Thank you for your participation.

North America Office
89 Headquarters Plaza North Suite 350 Morristown, NJ 07960-6628 USA

European Office
47 Lower Brook Street Ipswich Suffolk IP4 1AQ United Kingdom Tel/Fax: +44-1473-288595

Tel.: +1 973-292-1901 Fax: +1 973-993-3131

E-Mail: Web Address: