compliance - booth tmw nice 2005 v3
TRANSCRIPT
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
1/12
NGOSS ComplianceNGOSS ComplianceTMF Booth Presentation:
A Strategy Overview
TMW, Nice 2005
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
2/12
Compliance ProgramCompliance 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 Userscan see real benefits
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
3/12
NGOSS Compliance and LifecycleNGOSS Compliance and Lifecycle
Logical
View
PhysicalView
Service Developers
View
Service Providers
View
ImplementationDeployment
Business System
Iterate with
SANRR
CorporateKnowledge
Base
NGOSSKnowledge
Base
Shared
Done On-going
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
4/12
Business View complianceBusiness View compliance
Business drivers NGOSS compliance needs traceability
Prove that a solution implements a business process
ROI needs agility
Prove that a process can evolve easily
Challenges
Lack of formal definitions Need transition from UML to test code
Information overload! Rules, models, gates Need a multi-dimension search (compliance catalog)
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
5/12
omp ance: ome o eIssuesIssues
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
6/12
A Model for ComplianceA Model for Compliance
AssessmentAssessment NGOSS Principles Compliance
High level view only 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
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
7/12
An example: eTOM ComplianceAn example: eTOM Compliance
eTOM provides a standard structure, terminology and
classification scheme for describing the businessprocesses 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 Assessment made against Business View
Contract(s) using eTOM
Strengthens precision and rigorof how eTOM is used
More objective eTOM Compliance assessment
Relates eTOM to a specific scenario and area of application
Links to the rest of the NGOSS compliance work
Customer
ComplaintProblem Reportto Customer
Manage
Contact
Retention& Loyalty
ManageRequest
Analyze&Report on
Customer
Retention
& Loyalty
Mediate &
Orchestrate
CustomerInteractions
Isolate
Problem &Initiate
Resolution
ReportProblem
Track &
ManageProblem
Close
Problem
ManageContact
Customer
RelationshipManagement
Mediate &
OrchestrateCustomer
Interactions
Service
Management&Operations
Evaluate &
QualifyProblem
DiagnoseProblem
Awaiting Resource
Trouble Mgt.
Track &
Manage
Resolution
TroubleAnalysis
Trouble
Resolution
Awaiting Resource
Trouble Mgt.
Close &Report
Plan &Assign
Resolution
TroubleUpdate
Awaiting Resource
Trouble Mgt.
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
8/12
NGOSS Business View ContractNGOSS Business View Contract
(TMF 053B)(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 eTOMprocesses), 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 bywhich 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 ???
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
9/12
1. Define the Business(Leadership Team,
Business Process Engineers)
2. Architect the Business(Enterprise IT Architects)
3. Implement the Business(Development Org.)
4. Execute the Business(Operations)
BusinessContract
1
Contracts end-to-endContracts end-to-end
Implement
Contract
SystemContract
Deploymnt.
Contract
BusinessContract
1
4
2
3
Corporate
Knowledge
Base
NGOSS
Knowledge
Base
Shared
SystemContract
BusinessContract
1 2
ImplementContract
System
Contract
Business
Contract
1 2
3
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
10/12
Compliance Catalog SolutionCompliance Catalog Solution
Is repository of all theproducts and solutions whichhave been tested forNGOSS Compliance basedon NGOSS principles.
Provides the degree ofNGOSS Compliance of
products or solutions fordifferent principles
Provides Information abouttype of Technology Support
See separate Catalog Demo at the TMF Booth !
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
11/12
Next StepsNext 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!
-
7/31/2019 Compliance - Booth TMW Nice 2005 v3
12/12
Thank you for yourThank you for your
participation.participation.
E-Mail: [email protected]
Web Address: www.tmforum.org