(TeleManagement Forum & NGOSS Program Overview) · (TeleManagement Forum & NGOSS Program Overview)...

(TeleManagement Forum & NGOSS (TeleManagement Forum & NGOSS Program Overview)Program Overview)

Tony RichardsonTMF Director – Strategic LiaisonsChair – Industry Group Advisory BoardJune 2003

Convergence of Telecoms and Enterprise Management

AgendaAgendaWhat is the TeleManagement Forum ?

Motivation for NGOSSNGOSS BasicsNGOSS eTOM: Business ProcessesNGOSS SID: Shared Information Data ModelNGOSS TNA: Technology Neutral ArchitectureNGOSS: Now and the Future

Industry Group LiaisonConvergence Telecoms / Enterprise Management

What is TM Forum?What is TM Forum?Non-profit global consortium focused on Operations Support Systems (OSS) and management issues for the communications industry

Service providers, software and hardware suppliers, systems integrators

Source of leadership, knowledge, technical solutions and market awareness for the industry 340+ members in 36 countriesProvides a collaborative environment in which companies can address service provider’s most critical business and technical requirementsProvides an on-line knowledgebase featuring industry information and potential solutions

The voice of the OSS industry

Create a portal which is a resource center which the industry can use as first port of call for OSS/BSS info

Communicate

Develop proof of concept solutions to real industry problems that can subsequently be productised andsold

Demonstrate

Create a collaborative work environment within which competitor can solve problems of mutual interest

Collaborate

Draw direction and requirements in a market-centric fashion from key industry players

Market Focus

Provide the premier global OSS/BSS environment within which members can conduct business

A Place to Do Business’

Key Work ProgramsKey Work ProgramsTechnical TeamsBusiness, System & ImplementationArchitecture

Market Centers• Mobile• Value Chain• Service Provider

interst group

TMF CentralWebsite

Catalyst Showcase

TeleManagement World

What does TM Forum do?What does TM Forum do?Provides strategic leadership and guidance on:

Business Process Modeling and AutomationManaging Next Generation Network TechnologiesSystems Integration and ImplementationService ManagementWeb-Based Customer Care (E-Care) and Customer Relationship Management (CRM)Managing E-Commerce

New Generation Operations Systems and Software (NGOSS)

Enables collaborative, business-driven solutions based on commercially available software and industry standards

NGOSS AgendaNGOSS Agenda

Motivation for NGOSS

NGOSS Basics

NGOSS eTOM: Business Processes

NGOSS SID: Shared Information Data Model

NGOSS TNA: Technology Neutral Architecture

NGOSS: Now and the Future

TheThe Operational Challenges Are Growing…Operational Challenges Are Growing…The market demands that next generation systems provide….Rapid service development

Real-time flow-through service delivery

Proactive, real-time, content based,location based billing

Web-based, customer self service

Service level guarantees across multi-service, multi-technology, multi-provider infrastructures

Flexible and responsive technology base

…But Yesterday’s Systems Can’t Cope…But Yesterday’s Systems Can’t Cope OSSs Have Become a Roadblock to Innovation

- Not a Business Tool for Competitive Success

Systems development/integration can take too long, and is too expensive and riskyBusiness Processes and Systems are:

Slow to evolve - unable to support new servicesCan’t meet rapid time to market requirementsCan’t deliver superior customer service that determines market winners

Affecting companies’ bottom line

A Traditional OSS/BSS EnvironmentA Traditional OSS/BSS EnvironmentExternal data flow

Internal data flow

Pending data flow

System appears twiceNAME

Planned systems

Key:

JOBMOBE

TMM

NI

DFGPVI

CID/SAM

LOC

INPLANS

ISIS

ASOS

Mech Eng

TESS

CCP

TOPS

NRSS

Billstar 3

Billstar 1PCDB

EC

RIMSPRECISEPay by

Phone

DOMSCustomizer800

Custom800 DB

RCRMS

BOSSCOR

OSMOPLIDB

E911

NAA

LMOS

Exch Plus

APTOS

PREMIS

MIStarwriter

CMS(CCRS)

SABR

LFACS

FWS

PICS/DPCR

TNDS/TK

LEIS

WM

COSMOS

SOAC

PAWS

LOMS

FIRST

ORGIS

GIRBAIF

IRSSSDID

SDDL-POFSOCSPDR

TOR

AOG

SORD

CRMS

EARSMAPS

CESAR

CABS

Data Svc

PR

JOUR

GL

RAP

3rd Pty

Bill Print

MP USAGE

RM REVEBill Format

Bill Day

Billing

DirectoryDelivery

Corp Books

MI

CL CONFEM EXCH

Listing Svc

C/CA

SOFE

LSD&C

Data

WarehseFIMS

PARIS

CARTS

COR

SUMMIT 4.0

SBIR

MRDB

Sales Agency

ORBITSAthena

AA PBCC

SMS

DRSDCN

CPNI Sales CompPB Awards

APTOS

PaSS

COIN

AP

PBVS

CSFT

IP

SPACE

MARCH

CSTAR

Separation

ConnectVu

CLONES

TNM NMA-F

DCOS-2000

NetPilot

SEAS

EADAS NDS-TIDE

AMOSNSDB

TIRKS

IPMS

MOPICS PMM

CMTSFTDM

SARTS

PVS | PMI

REACT2001

TSANTAS

MTASLATIS

CRASCIAS

ANS

LMOS

MLT

SORD

SOAC

PBOD

Service

Manager

Electronic

Bonding

ALRU

PDS-ERA

PDS

CustomerProfile

AIM

POS-R

POS

BRIS

REMS

ESS

EmFiSys

TAPS

AUTS

TRAINS

WTS

IFSTWIST

ATR

NSDM

MTR

TCMS

Tech PDP

PMIS

PagingCNR

PBITS

MP/F

FLEXCOM

COSMOS

WFA/C

OPAS/Loopview

OPS/INE

Predictor

INATransport

SSI PBRIMS IPMSCCSN TANCCPL MP/F

ComnLang Taskmate

SCSFEPS

CUR/CAR

TAGS

FDOC

Network

AT&T

Network

DSCNOR AT&T

Network

NOR

STPSCPISCP

EDIIS

PB1

Network

AT&T

NOR

IS

ERMIS

Common Interface Layer

ATC

CIDB

Advantage

TIRKS

AgendaAgendaMotivation for NGOSS

NGOSS Basics





What is NGOSS?What is NGOSS?NGOSS is a comprehensive, integrated framework for developing, procuring and deploying operational and business support systems

Industry-agreed, business & systems framework to guide the implementation of process automation :

Defines methodologies for evolving OSS and BSS infrastructure into a lean operations approachSpecifies the key characteristics of OSS/BSS (business processes, data models and integration architectures) that allow high degrees of process integration and automationDeveloped by major operators and suppliers worldwideDriven and managed by TM ForumImplemented as a set of programs and maps

Architecture MigrationArchitecture Migration

Emerging Emerging --•open•distributed•components•soft workflow•shared data•policy enabled

Legacy Legacy ––•poor integration•stovepipe •very inflexible

Today Today --•loose integration

(pair-wise service)•proprietary•multiple databases•multiple user interfaces•inflexible

EAI

NGOSS PedigreeNGOSS PedigreeBellcore (now Telcordia) OSCA & INA ArchitecturesANSA ProjectTINA-C ArchitectureISO / RM-ODPITU-T / TMNTM Forum TOM (and eTOM)OMG MDA & UMLHP ISMDMTF CIMEC FORM Project

Some of the Lead Players in Some of the Lead Players in NGOSS DevelopmentNGOSS Development

Hitchhiker’s Guide to NGOSSHitchhiker’s Guide to NGOSSFramework

Supports multiple viewpointsArchitecture

Technology-neutral frameworkTechnology-specific implementations defined

MethodologyCombination of policy and process managementShared information and data models

InteroperabilityContract and component-based

CommunicationDistributed networking and computing services

ComplianceTestable and provable

NGOSS – New Generation OSS

Conforman

ce

Testin

g &

Deploym

ent

Conforman

ce

Conforman

ce

Testin

g &

Testin

g &

Deploym

ent

Deploym

ent

NGOSSNGOSSSupportingSupporting

ToolsTools

Business

Process Analysis

& Design

Business

Business

Process Analysis

Process Analysis

& Design

& Design

System

s

Analysis

&Des

ignSystem

s

System

s

Analysis

&

Analysis

&Des

ign

Design

SolutionDesign &

Integration

Solution

SolutionDesign &

Design &

Integration

Integration

Business

Process Map

(eTOM)

Shar

ed

Info

rmat

ion

&

Data

Mod

el

(SID

)

Contract Interface &

Technology

Neutral Architecture

Com

plia

nce

Test

s


NGOSS Basics






Conforman

ce

Testin

g &

Deploym

ent

Conforman

ce

Conforman

ce

Testin

g &

Testin

g &

Deploym

ent

Deploym

ent


ToolsTools

Business

Process Analysis

& Design

Business

Business

Process Analysis

Process Analysis

& Design

& Design

System

s

Analysis

&Des

ignSystem

s

System

s

Analysis

&

Analysis

&Des

ign

Design

SolutionDesign &

Integration

Solution

SolutionDesign &

Design &

Integration

Integration

Business

Process Map

(eTOM)

Shar

ed

Info

rmat

ion

&

Data

Mod

el

(SID

)


Technology


Com

plia

nce

Test

s

A Brief History of eTOMA Brief History of eTOM1995 – 1998: development of TOM (Telecom Operations Map)

1999: stabilization of TOM

2000 – 2001: evolution of TOM towards eTOM

May 2001: eTOM v1.0 for TMF Members Evaluation

Oct 2001: eTOM v2.0 for TMF Members Evaluation

Jan 2002: eTOM v2.5 for Public Evaluation

May 2002: eTOM v3.0 is TMF Approved

July 2002: Addendum to core eTOM released to Members

Dec 2002: Status update on work in progress to Members

June 2003: release of eTOM v3.5 (extends v3.0 with further process decompositions and selected flows) for TMF Member Evaluation

“e” for enhanced

NGOSS Business MapNGOSS Business MapOperations

Fulfillment Assurance BillingOperationsSupport &Readiness

Customer Relationship Management

Service Management & Operations

Resource Management & Operations

Supplier/Partner Relationship Management

(Application, Computing and Network)

Enterprise Management

Strategic &EnterprisePlanning

Financial & AssetManagement

Enterprise QualityManagement, Process & ITPlanning & Architecture

Stakeholder & ExternalRelations Management

Brand Management,Market Research &Advertising

Human ResourcesManagement

Disaster Recovery,Security & FraudManagement

Research &Development,TechnologyAcquisition

Strategy, Infrastructure & ProductProductLifecycleManagement

InfrastructureLifecycleManagement

Strategy &Commit

Marketing & Offer Management

Service Development & Management

Resource Development & Management

Supply Chain Development & Management


Customer

OperationsFulfillment Assurance BillingOperations Support

& ReadinessCustomer Relationship Management




The Operations areaThe Operations area

ServiceConfiguration & Activation

ServiceProblem

Management

Service QualityManagement

Service &Specific Instance

Rating

SM&OSupport &Readiness

Supplier/Partner Interface Management

S/P Buying

S/P PurchaseOrder

Management

S/P ProblemReporting &

Management

S/PPerformanceManagement

S/P Settlements& Billing

ManagementS/PRM

Support &Readiness

ResourceProvisioning

ResourceTrouble

Management

Retention & Loyalty

Customer Interface Management

Billing & Collections

Management

CustomerQoS / SLA

ManagementProblemHandling

Selling

OrderHandling

MarketingFulfillmentResponse

CRMSupport &Readiness

Resource Data Collection & Processing

ResourcePerformance ManagementRM&O

Support &Readiness

Process DecompositionsProcess DecompositionsOrder Handling

CreditA uthorization

Order Issuance Order Trackingand Status

PreorderFeasibilityDetermination

Order Completion

Receive Pre-OrderFeas ibility Request

Order PlanDevelopment

Order Creation Confirm OrderCompletion w ithCustomer

Report unmetcommitments orcapabilities

Status Report

CustomerJeopardyNotif ication

Committed DateRe-negotiatio w /Customer

Validate info forAssurance andBilling

CustomerSatisfactionValidation

Conf irm CustomerValue delivery

Billing SatisfactionValidation

Test solution anddemonstrate tocust

Order Cancellation

Order Amendment

Obtain AppropriateApprovals

Advise andNegotiateA cceptable Terms

Order RequestValidation

Issue Pre-OrderFeasibility Study

CreditInvestigationDetermination

CreditInvestigation

StatusEs tablishment andManagement

Manage Customerchanges toA greement Con

Train the customer

Follow up onoptimal CustomerUtilisation

© Te leManageme nt Forum e TOM April 200 1

TEA M DRAFT

Level 2

Level 3

Level 4

eTOM eTOM -- The Level 2 ProcessesThe Level 2 ProcessesLevel 1 Vertical Grouping

Level 1 Horizontal Grouping

Customer


Enterprise Quality Mgmt, Process & IT Planning & Arch.Process Arch.Management

& Support

Info SystemsStrategy &Planning

KnowledgeManagement

Stakeholder & External Relations ManagementPR & Comm.

RelationsManagement

RegulatoryManagement

ShareholderRelations

Management

LegalManagement

Human Resources ManagementEmployee& Labor

Relations

WorkforceStrategy

WorkforceDevelopment

HR Policies& Practices

Disaster Recovery, Security & Fraud ManagementFraud

Management

Disaster Recovery & Contingency

PlanningSecurity

Management

Financial & Asset ManagementFinancial

ManagementProcurementManagement

Real EstateManagement

Strategic & Enterprise Planning Strategic &Business Planning

BusinessDevelopment

EnterpriseArchitecture

Planning

GroupEnterprise

ManagementResearch &

DevelopmentTechnologyAcquisition

Research & Development & Technology Acquisition

Brand Management, Market Research & AdvertisingMarket

Research &Analysis

BrandManagement

Advertising

Level 2 Process ElementExternal Entity

EnterpriseQuality

Management





Infrastructure Lifecycle Management

Product Lifecycle Management

Strategy & Commit

Strategy, Infrastructure & Product

Supply Chain Strategy & Policy

Supply Chain Planning

& Commitment

Supply Chain Development & Change

Management

Supply Chain CapabilityAvailability

Service Planning & Commitment

Service Strategy &

Policy

Service &OperationsCapabilityDelivery

Service Development &

Retirement

Resource &Operations CapabilityDelivery

Resource &Technology

Strategy & Policy

Resource &Technology

Plan & Commitment

Resource Development

Product Development & Retirement

Product & OfferPortfolio

CapabilityDelivery

Product & OfferPortfolio Strategy,Policy & Planning

MarketingCapabilityDelivery

Product & OfferBusiness

Planning &Commitment

CRMCapabilityDelivery

MarketStrategy &

Policy

Sales & ChannelDevelopment

Marketing Communications

& Promotion


& ReadinessCustomer RelationshipManagement





ServiceProblem

Management


Service & Specific Instance

Rating

SM&OSupport & Readiness


S/P Buying

S/P Purchase Order

Management

S/P Problem Reporting &Management

S/P PerformanceManagement

S/P Settlements & Billing

ManagementS/PRM

Support &Readiness


ResourceTrouble

Management

Retention & Loyalty



Management

CustomerQoS / SLA


Selling

Order Handling


CRMSupport & Readiness


ResourcePerformanceManagementRM&O

Support & Readiness

Example Ordering (Fulfillment) FlowExample Ordering (Fulfillment) Flow






Selling

CustomerRequestreceived

CustomerOrderconfirmed

Order HandlingCustomer OrderInitiated

DesignConfirmation byCustomerEngineeringRequested

DesignAccepted byCustomer

CompletionAdvised toCustomer

Retention & Loyalty

Pr iorityRequested

Pr iorityAdvised

Service Configuration & Activation

InternalServiceOrderInitiated

ServiceActivated

Service OrderStatus Update

DesignCompleted

DesignRequested

Resource Provisioning & Allocation to Service Instance

InternalWork OrderInit iatied

CapacityRequested

ResourceActivationRequestedCapacity

Reserved

InternalResourceProvisioningCompleted

ResourceActivated

S/P Buying

Ex ternal SupplierSelection Required

S/P Purchase Order ManagementEx ternal Component Requested

Ex ternalResourceActivated

Cus tomer requests SPoffering

Billing &CollectionsManagement

CustomerQoS/SLAManagement

Service Detailsf or Billing

Service Detailsfor Assurance

Ex ternal OrderIssued

Modelling B2B in the context of Modelling B2B in the context of eTOMeTOM

Operations









Strategy &Commit






CustomerOperations









Strategy &Commit






CustomerOperations









Strategy &Commit






Customer

Operations









Strategy &Commit






Customer

B2B Environment

The Path Ahead: Potential eTOM ApplicationsThe Path Ahead: Potential eTOM ApplicationsThe list below shows many (although not all) the ways in which eTOM can be applied by SPs, vendors, integrators, etc.Guiding the design of new Processes, Mapping existing processes, Identifying and analyzing costs of business processes, Enterprise-level analysis of new business initiatives, Communicating Team and Individual accountabilities for projects, Analyzing and comparing project proposals for potential overlap, Framing tactical IT Architectures, Identifying gaps in existing Function Libraries, Assessing Workgroup preparedness for Solution Design, Rationalizing Workgroup roles, Evaluating proposed processes for completeness (checklist), Identifying other processes in an Enterprise, associated with a particular process (context), As an outline for documenting problem scope and requirements, Develop a consolidated view of end-to-end processes, Modeling the structure of Workgroups and Channels, Document Requirements so that they will be accurately understood by Vendors and Partners, A structure for Activity Based Costing elements, OSS development (e.g. in areas like Products, Services and Resources), OSS marketing and sales to identify areas of functionality, OSS partnership, to identify respective areas of functionalityMany companies have already provided input on their own us e of eTOM both internally and externally with Customers. Suppliers and Partners

more...

Some eTOM Users...Some eTOM Users...


NGOSS Basics






Conforman

ce

Testin

g &

Deploym

ent

Conforman

ce

Conforman

ce

Testin

g &

Testin

g &

Deploym

ent

Deploym

ent


ToolsTools

Business

Process Analysis

& Design

Business

Business

Process Analysis

Process Analysis

& Design

& Design

System

s

Analysis

&Des

ignSystem

s

System

s

Analysis

&

Analysis

&Des

ign

Design

SolutionDesign &

Integration

Solution

SolutionDesign &

Design &

Integration

Integration

Business

Process Map

(eTOM)

Shar

ed

Info

rmat

ion

&

Data

Mod

el

(SID

)


Technology


Com

plia

nce

Test

s

NGOSS ArchitectureNGOSS Architecture(SID Part)(SID Part)

Shared Information Model

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

ABE Table

SID Level 0-1

Business Entity

Contract

ABE ModelFragment

Customer

Customer ABE

Product Specification Product Offering

Product

Product Usage Statistics

Product Performance

Resource

Service Quality Service

Service Specification

Service Test

Service

Service Trouble

Service Usage

Resource Trouble

Resource Performance

Resource Specification Resource Topology

Resource

ResourceConfiguration

Customer Statistics

Strategic Product Portfolio Plans

S/P Strategy

Sales Statistics Marketing CampaignCompetitor

Contact/Lead/Prospect

Market/Sales

Market Segment

Market Strategy & Plans

Sales Channel

Resource Usage

Supplier/Partner

S/P Interaction

Supplier/Partner

S/P ProblemS/P Statistics

S/P SLAProduct

Service Capacity

Customer BillCustomer

Customer OrderCustomer Interaction

CustomerCustomer Problem

Customer SLA

S/P Product

S/P Order

S/P Bill

S/P Payment

Service Plan

Service Performance

Enterprise (under construction)

Supply Chain Strategy

Industry Compliance Workforce

Common Business Entities

Interaction Location Party

Agreement Policy

Resource Plan

SID FrameworkSID FrameworkDomains & ABEs

ABE Table

SID Level 0-1

Business Entity

Contract

ABE ModelFragment

Customer

Customer ABE

SID –Artifacts

Example of the Evolving SID FrameworkExample of the Evolving SID Framework

Resource

PhysicalResource

LogicalResource

PhysicalResource

LogicalResource

ResourceSpecification

ResourceTopology

PhysicalTopology

LogicalTopology

PhysicalConfig

LogicalConfig

ResourceConfiguration

ResourceStatistics

ResourcePerformance

ResourcePerformance

PhysicalUsage

LogicalUsage

ResourceUsage

ResourceFault

ResourceAlarm

ResourceTrouble

ResourceOutage

Resource Domain – Level 2

Network NetworkUsage

Network NetworkConfig NetworkPerformance

NetworkFault

NetworkAlarm

NetworkOutage

NetworkTopology

SID SID –– Aggregate Business Entities (ABE)Aggregate Business Entities (ABE)

Logical Business Component Name

Customer

Description The Customer ABE is the focus component for customer data and the associated data manipulation services. Customer data is the enterprise’s knowledge of the customer, their accounts and those services to which they subscribe. It also contains all customer/provider/ operator agreements and negotiations.

Business Entity Name

Customer

Contracts Create customerDelete customerSearch for customer by attributesRead customer attributesChange customer attributes

SID GB922

Party Party –– Basic ModelBasic Model

Individual ValueNetworkRole

Customer Intermediary ServiceProvider

ThirdPartyServiceProvider

Vendor

ComplementaryProvider

Employee

PartyRole0..n

0..nParty

1 0..n1 0..nhasPartyRoles

Organization

involvedPartyRoles

0..n

PartyRoleDetails

Resource OverviewResource Overview

ResourceSpecification Resource0..1 0..n0..1 0..nspecifiesResource

EntitySpecification CollectionManagedEntity0..1 0..n0..1 0..nspecifiesManagedEntity

10..n 10..n collectedEntities

LogicalResourceSpecification

PhysicalResourceSpecification

0..n 0..n0..n 0..n

lResSpecBindsToPResSpec

LogicalResource

0..n0..1 0..n0..1

specifiesLogicalResource

ReplacementSet

PhysicalResource

0..1 0..n0..1 0..n

specifiesPhysicalResource

0..n0..n 0..n0..n

pResourceSupportsLResource

0..1

0..n

0..1

0..n

replacedBy

ProductProduct--ServiceService--ResourceResource

ProductSpecification

0..n 0..10..n

involvedProductSpecs

0..1

ProductOffering0..n0..1 0..n

involvedProductOfferings

0..1

1

0..n

1

0..n

madeAvailableAs

Product1 0..n1 0..nofferedAs

Resource

ProductItem1 1..n1 1..nhasProductItems

1

0..n

1

0..n

resourceRealizedAs

CustomerFacingService

1

0..n

1

0..n

serviceRealizedAs

ResourceFacingService

0..n0..n 0..n0..n

cfRequiresRFServices

PhysicalResource

1

1..n

1

1..n

physicalResourcesHostRFS

LogicalResource

1

1..n

1

1..nlogicalResourcesForRFS

0..n0..n 0..n0..n


Service

SID Framework SID Framework –– Aligned with Aligned with eTOMeTOMStrategy, Infrastructure &Product

Operations

Enterprise

CustomerMarket/Sales Product

Service

Supplier/Partner

Enterprise Common Business Entities

Resource

Business to System:Business to System:SID Model InteractionsSID Model Interactions

Data Association

Business Process Model

Shared Information Data Model

SID Model captures business and system information

SID/eTOM MappingSID/eTOM Mapping

SID and the IndustrySID and the IndustrySID is a federation of models, not “home-grown”

Material mined from company contributions as well as DEN-ng, ITU, IETF and DMTF

SID is already being used byVendors (e.g., MetaSolv and Intelliden)Service Providers (e.g., BT and Telstra)TM Forum Catalyst ProjectsOSS/J Core Business Entity Model

SID is being considered for use inT1M1 Global Telecom Data Dictionary (GTDD)OMG Telecom Domain Task Force (DTF)


NGOSS Basics






Conforman

ce

Testin

g &

Deploym

ent

Conforman

ce

Conforman

ce

Testin

g &

Testin

g &

Deploym

ent

Deploym

ent


ToolsTools

Business

Process Analysis

& Design

Business

Business

Process Analysis

Process Analysis

& Design

& Design

System

s

Analysis

&Des

ignSystem

s

System

s

Analysis

&

Analysis

&Des

ign

Design

SolutionDesign &

Integration

Solution

SolutionDesign &

Design &

Integration

Integration

Business

Process Map

(eTOM)

Shar

ed

Info

rmat

ion

&

Data

Mod

el

(SID

)


Technology


Com

plia

nce

Test

s

NGOSS ArchitectureNGOSS ArchitectureShared Information Model

SecurityPolicy

Business ProcessOSS Applications

OSS Framework Services

Basic Framework Services

Basic Mechanisms

NGOSS Technology Neutral Architecture:NGOSS Technology Neutral Architecture:

OSS ApplicationsComponents, Services, and ContractsDistribution and Transparency ServicesMetaModelBehavior and Control – Policy ModelSecurity

NGOSS Architectural ConceptsNGOSS Architectural Concepts

Unit of Deployment andManageability

Unit of Manageability

Unit of Functionality within Service

Contains one or more

Is realized by (0 or more)

Contains two or more

Component

Service

Contract

ContractInstance

Unit of Binding

What is a Contract …What is a Contract …A description of functionality to be provided in terms of:

The metadata used to describe the interface The metadata used to describe the operations that may be invoked on the ServiceFor each operation, the set of terminations that may be returned by the Service after invocation of the operation

The behavior of the functionality, some of the behavior that may be specified are:

The pre-conditions under which an operation may be invoked (i.e., the set of conditions that must be satisfied in order to invoke the operation)The post-conditions, which define the state that the system is left in for each termination that can be returned when an operation is invoked

Contractually Defined InterfacesContractually Defined Interfaces

OperationInterface

Announcement Interrogation

AnnouncementSignature InterrogationSignature

Parameters Termination1..n1..n

1..n1..n

Interaction

OperationInteraction

Interface

OperationInterfaceSignature

1..n1..n

InterfaceSignature1

1

1

1

1..n

1

1..n

1

SignalInteraction SignalInterface StreamInterfaceFlowInteraction

SignalInterfaceSignatureStreamInterfaceSignature

The ty pe of the interaction must match the ty pe of the interf ace signature

Diagram notes:

(1) The entities with no fill color and/or black lines are not addressed by the NGOSS Architecture at this time.

NGOSS ContractNGOSS Contract

Environmental AttributesCharacteristic Attributes

SecurityAccess

Act

ivat

ion

Part

Implementation DependenciesImplementation Notes

TechnologyVendor Info, Name, Version

Impl

emen

t Pa

rt

Tec

h. S

peci

fic

Part

ExceptionsPostconditionsPreconditions

ArgumentsContract DescriptionSpecifier ReferenceContract Identifier

Des

crip

tion

Part

Tec

h. N

eutr

al

Part

Def

initi

on

Part

NGOSS Distribution and Transparency Services NGOSS Distribution and Transparency Services ModelModel

Client

Access to otherdomains

Basic Framework Services OSS Appls & Framework Svcs

Data

Distribution and Transparency ServicesDistribution and Transparency ServicesModelModel

Other NGOSSSupporting Services

(e.g. Logging, Transaction)Registration Services

UsersSpecifiers,

Designers/Devel.,& Admin.

Federated Foreign

Repository

Service LocationServices

DerivedRepository

NamingServices

Repository

Why do we need an NGOSS Metamodel?Why do we need an NGOSS Metamodel?The NGOSS Metamodel serves as the foundation to the entire series of NGOSS Technology Neutral Architecture Specifications. It provides the definitions and UML derived models of fundamental NGOSS concepts

IdentifierExtensibleElementComponentContract

InteractionInvocation Termination

NGOSSPolicy…

Extending the UML MetamodelExtending the UML Metamodel

Element

GeneralizableElementisRoot : BooleanisLeaf : BooleanisAbstract : Boolean

AttributeinitialValue : Expression

Methodbody : ProcedureExpression

Operationconcurrency : CallConcurrencyKindisRoot : BooleanisLeaf : BooleanisAbstract : Booleanspecification : Stringn

1

n

+specification1

ElementOwnershipvisibility : VisibilityKindisSpecification : Boolean

NamespaceConstraint

body : BooleanExpression

ModelElementname : Name

0..1

n

+namespace0..1

+ownedElement n

n

n

+constraintn

+constrainedElementn

{ordered}

BehavioralFeatureisQuery : Boolean

StructuralFeaturemultiplicity : Multiplicitychangeability : ChangeableKindtargetScope : ScopeKindordering : OrderingKind

ParameterdefaultValue : Expressionkind : ParameterDirectionKind

0..1

n

0..1

+parametern{ordered}

Classifier

n

1

+typedFeaturen+type

1

n

1

+typedParametern

+type1

FeatureownerScope : ScopeKindvisibility : VisibilityKind

n

0..1

+featuren{ordered}

+owner

0..1


NGOSS Basics





Business Cases:Industry Stakeholders

OSS User (Eg. Communications Service Provider)Faster Business Solutions / Time to Market, Greater Range ofBusiness Services, Less Development / More Re-Use, More Buy / Less Make of OSS SolutionsOSS Systems VendorMore Re-Use of of System Solutions / Less Customised Development, Multi-Customer Product Packaging, Reduced Product Portfolio / Maintenance CostsOSS Systems IntegratorMore Complete Business Solutions, Faster Integration, More Predictable Integration Approaches / Costs (via Framework)Network Equipment VendorIncreased up-take of network technology for new services

What Documentation is Available Now?What Documentation is Available Now?

GB 921 – eTOM v3.0

GB 922 and Addendums – SID Phase II

TMF 050 - Compliance Testing Technical Spec

TMF 055-057 – Technology Specific Application Notes (CORBA, J2EE, XML/SOAP/UDDI, J2SE and JINI) (need updating; these reflect older version of NGOSS)

TMF 083x – NGOSS Catalyst Projects

What Documentation is Available Now?What Documentation is Available Now?

TMF 053 - Technology Neutral Architecture Series (V3.0):

TMF 053: NGOSS Technology Neutral Architecture

TMF 053a: Glossary

TMF 053b: Contract Specification

TMF 053c: Behavior and Control Services

TMF 053d: NGOSS Metamodel

TMF 053s: Security Framework

What Documentation Will Be Available?What Documentation Will Be Available?(Mid(Mid--Summer)Summer)

TMF 053 - Technology Neutral Architecture Series (V3.5):

TMF 053f: Distribution and Transparency Services

TMF 053m: Process Management

TMF 053n: Naming

TMF 053p: Policy Management

TMF 053u: Use Cases

NGOSS Release 3NGOSS Release 3

Near Term Deliverables

Available Today:

Document Family:

NGOSS Element:

Updates and additions to TMF 050,050a

Additional addenda TMF 053 F, M, P

Additional GB922 addenda

Selected detailed process decompositions

TMF 050TMF 050a

TMF 052TMF 053TMF 053ATMF 053BTMF053CTMF053DTMF053S

GB914GB922 V1.0GB922A1PGB922A1LGB922A1IGB922A2GB922A3GB922A5

GB921 V3.0GB921A

TMF 050TMF 050 addendum

TMF 052TMF 053TMF 053 addenda

GB914GB922GB922 addenda

GB921GB921 addendum

Conformance -–Compliance Tests

Integration Framework --TNA, Contract Interface

Shared Data Model --SIM/SID

Business Process Map –eTOM

NGOSS – Integrated “Viewpoints”

Conforman

ce

Testin

g &

Deploym

ent

Conforman

ce

Conforman

ce

Testin

g &

Testin

g &

Deploym

ent

Deploym

ent


ToolsTools

Business

Process Analysis

& Design

Business

Business

Process Analysis

Process Analysis

& Design

& Design

System

s

Analysis

&Des

ignSystem

s

System

s

Analysis

&

Analysis

&Des

ign

Design

SolutionDesign &

Integration

Solution

SolutionDesign &

Design &

Integration

Integration

Business

Process Map

(eTOM)

Shar

ed

Info

rmat

ion

&

Data

Mod

el

(SID

)


Technology


Com

plia

nce

Test

s

TM Forum Working in TM Forum Working in Cooperation with Other Industry Cooperation with Other Industry

GroupsGroups

Industry Group Liaison – Why?

Principal focus of TM Forum work = OSS for Comms. Industry.But this has wide scope:Business Processes, Systems Framework, Info. Modelling, etc.

Increased Convergence with the work of other Industry Groups

TM Forum wants:• Cost-effective solutions that receive wide industry support• Reduced industry duplication and confusion

Hence TM Forum must:• Build upon work of other Industry Groups – where applicable• Influence the work of other Industry groups – where necessary

Objectives achieved through Liaison Programme

TM Forum - Liaison Program

Business Relationship – Liaison Agreement

Technical Detail – Work Register

Example Liaison Areas:• Management (DMTF, T1M1)• Network Technology (MSF, OIF)• Internet (IETF, IPDR.org)• System (OSS/J, Open Group)• eBusiness (UN/CFACT – ebXML, RosettaNet)• Mobility (3GPP, OMA)• “Standards Bodies” (ITU-T, ATIS, ETSI, TTC)

Liaison Partnership in ActionExamples of co-operative work :

Input into 3GPP Releases 5&6Wireless Services Measurements - Key Performance Indicators

Involvement in Catalyst projectsInformation model input into SID, use of eTOM

Convergence of Telecoms / Enterprise ManagementConvergence of Information Models (SID / CIM)

Membership swapJoint development of SLA / QoS Handbook

Membership swapExtensions to UML MetaModelMDA / NGOSS – White paper

Telecoms / Enterprise ConvergenceWhy?

Services increasing involve integration of Telecom / Enterprisetechnologies (Eg VoIP, Multi-Media)

Increased need to manage services to customers through multipleService Level Agreements (SLAs)- SLA jeopardised equally by failure of Telecom / Networkresource (eg SDH cross-connect) as by failure of Enterprise / IT resource (eg computer)

Hence need to manage the complete Telecoms / Enterprise environment in a more integrated fashion

TMF / DMTF Information Models(CIM and SID)

Similarities:Broad-reaching, technology-neutral, object-oriented modelDescribes Service, Network, Resource, Policy (albeit differently)“Federates” information from multiple sources (ITU-T, vendors etc)

Differences:Scope

- SID = Telecoms , NGOSS / Multiple “Viewpoints”- CIM = Enterprise / IT, Comprehensive Information Model

MetaModel / Standards- SID = Full UML + extensions, ODP, Rational Rose + HTML- CIM = MoF, UML / Visio, Web (SOAP, XML etc)

Start Dates- SID = 2 years- CIM = 8 years(Different tool sets / techniques available)

Deliverables

TMF analysis of CIM from SID perspective (June 2002)(Used in potential harvesting of CIM information into SID)

TMF / DMTF Joint Industry Positioning Statement (June 2003)on Telecoms / Enterprise Management Convergence

Additional SlidesAdditional Slides

More Details:

• eTOM

• SID / UML Models

• TNA - Contract Definition etc

• NGOSS MetaModel

TMF Contact InformationTMF Contact Information

North America Office89 Headquarters Plaza NorthSuite 350Morristown, NJ 07960-6628USATel.: +1 973-292-1901Fax: +1 973-993-3131

European Office67 Corder RoadIpswich, Suffolk IP4 2XBENGLANDTel/Fax: +44-1473-288595

E-Mail: [email protected] Address: www.tmforum.org

Thanks for Listening!!Thanks for Listening!!

Questions?Questions?

eTOMeTOM: the Big Picture: the Big Picture


Strategy, Infrastructure & Product Operations

Customer

Fulfillment Assurance BillingProductLifecycleManagement


OperationsSupport andReadiness






Financial &AssetManagement

Enterprise Quality Mgt.,Process & IT Planning& Architecture


Strategy &Commit



Resource Development and Management

Supply Chain Development and Management








Operations







“FAB” remains the core of the Operations area

Operations Support & Readiness is separated from FAB

“OPS” also supports functional process groupings shown as horizontal layers

The Strategy, Infrastructure & Product areaThe Strategy, Infrastructure & Product area

“SIP” encompasses strategy and lifecycle management processes in support of operations

Strategy & CommitInfrastructure Lifecycle ManagementProduct Lifecycle Management

“SIP” also has functional groupings, aligned with those in “OPS”

Strategy, Infrastructure & Product

ProductLifecycleManagement


Strategy &Commit






The Enterprise Management areaThe Enterprise Management area



Financial &Asset

Management

Financial &Asset

Management

Brand Management,

Market Research

& Advertising

Brand Management,

Market Research

& Advertising

HumanResources

Management

HumanResources

Management

Stakeholder &External Relations

Management

Stakeholder &External Relations

Management



Enterprise Quality Management,Process & ITPlanning & Architecture

Enterprise Quality Management,Process & ITPlanning & Architecture

Disaster Recovery,Security &

FraudManagement

Disaster Recovery,Security &

FraudManagement


eTOM “Level 0 view of Level 1”eTOM “Level 0 view of Level 1”Operations


















Strategy &Commit






Customer

OPS Vertical Level 1 ProcessesOPS Vertical Level 1 Processes

Operations

Fulfillment Assurance BillingOperationsSupport andReadiness

CustomerOperations

Fulfillment Assurance BillingOperationsSupport andReadiness

CustomerOperationsAll operations processes that support the customer operations and management, as well those that enable direct customer operations with the customer. These processes include both day-to-day, and operations support and readiness processes..

Fulfillment:: provides customers with their requested products in a timely and correct mannerAssurance: executes proactive and reactive. maintenance activities to ensure service to customers Billing:: produces timely and accurate bills, processes and collects payments, and handles billing enquiries.Operations Support & Readiness: supports the "FAB" processes.. In general, the processes are concerned with activities that are less "real-time" than those in FAB, and which are typically concerned less with individual customers and services and more with groups of these..

Operations






CustomerCustomer

OPS Horizontal Level 1 ProcessesOPS Horizontal Level 1 ProcessesCustomer Relationship Management: handles customers needs.including the acquisition, enhancement and retention of a relationship with a customer.Service Management & Operations: handles services (Access, Connectivity, Content, etc.), and the provision of communications and information services required by or proposed to customers.Resource Management & Operations: handles resources (application, computing and network infrastructures), utilized to deliver and support services required by or proposed to customers.Supplier/Partner Relationship Management: supports the core operational processes through interaction with external suppliers and/or partners. These processes align closely with a supplier’s or partner’s Customer Relationship Management processes..


Operations

















ServiceProblem

Management



Rating



S/P Buying

S/P PurchaseOrder

Management


Management



ManagementS/PRM

Support &Readiness


ResourceTrouble

Management

Retention & Loyalty



Management

CustomerQoS / SLA


Selling

OrderHandling





Support &Readiness






Ref: GB921 v3.0 Operations areaRef: GB921 v3.0 Operations area


ServiceProblem

Management

Service QualityAnalysis, Action

& Reporting


Rating

SM&O Support & Process

Management

ServiceManagement &

OperationsReadiness


S/P Buying

S/P PurchaseOrder

Management


Management



ManagementS/PRM Operations

Support & Process

Management

S/P RelationshipManagementOperationsReadiness

Resource Provisioning& Allocation

to Service Instance

ResourceProblem

ManagementRM&O Support & Process

Management

ResourceManagement &

OperationsReadiness

Retention & Loyalty



Management

CustomerQoS / SLA


Selling

OrderHandling


CRM Operations Support & Process

Management

CRMOperationsReadiness

Sales & Channel

Management

Resource Data Collection, Analysis & Control

Resource QualityAnalysis, Action

& Reporting


Operations
















ServiceProblem

Management



Rating



S/P Buying

S/P PurchaseOrder

Management


Management



ManagementS/PRM

Support &Readiness


ResourceTrouble

Management

Retention & Loyalty



Management

CustomerQoS / SLA


Selling

OrderHandling





Support &Readiness

OPSOPS--FABFAB“FAB”“FAB”







ServiceProblem

Management



Rating



S/P Buying

S/P PurchaseOrder

Management


Management



ManagementS/PRM

Support &Readiness


ResourceTrouble

Management

Retention & Loyalty



Management

CustomerQoS / SLA


Selling

OrderHandling





Support &Readiness

OPSOPS--OSROSR



















Strategy &Commit






Customer

SIP Horizontal Level 1 ProcessesSIP Horizontal Level 1 Processesu

Strategy and Commit, Infrastructure and ProductLifecycle Management

Customer u

Strategy, Infrastructure and Product

Customer






Marketing & Offer Management: focuses on running and developing the Core Business for an ICSP Enterprise; including defining strategies, developing new products, managing existing products and implementing marketing and offering strategies.Service Development & Management: plans, develops and delivers services to the Operations domain; including defining strategies for service creation and design, assessing service performance, and anticipating future service demand. Resource Development & Management: plans, develops and delivers the resources needed to support services and products to the Operations domain; including defining strategies for development of network and other resources, interworking of new and existing technologies, assessing resource performance, and anticipating resource needs for future service demand. Supply Chain Development & Management: focuses on the external interactions required with the supply chain to ensure that the best suppliers and partners are chosen; including support for sourcing decisions made by the enterprise, and ensuring that contribution of suppliers and partners to the supply chain is timely and to the required performance.

SIP Vertical Level 1 ProcessesSIP Vertical Level 1 Processesu

Strategy and Commit, Infrastructure and ProductLifecycle Management



Strategy andCommit

Customer u

Strategy, Infrastructure and Product



Strategy &Commit

Customer

Strategy & Commit: generates strategies in support of the Infrastructure and Product Lifecycle processes. It is also responsible for establishing business commitment within the enterprise to support these strategies.Infrastructure Lifecycle Management: defines, plans and implements all necessary infrastructures (application, computing and network), as well as all other support infrastructures and business capabilities (operations centers, architectures, etc.).Product Lifecycle Management: defines, plans, designs and implements all products in the enterprise’s portfolio.







Strategy & Commit

Strategy, Infrastructure & ProductThe SIP areaThe SIP area

Supply ChainStrategy & Policy


& Commitment

Supply Chain Development

& Change Management



Service Strategy &

Policy


ServiceDevelopment &

Retirement

Resource &OperationsCapabilityDelivery

Resource & Technology

Strategy & Policy


Plan & Commitment


Product Development& Retirement

Product & Offer Portfolio

Capability Delivery

Product & Offer Portfolio Strategy,Policy & Planning

MarketingCapability Delivery

Product & Offer Business

Planning & Commitment


MarketStrategy &

Policy



& Promotion







Strategy & Commit

Strategy, Infrastructure & ProductRef: GB921 v3.0 SIP areaRef: GB921 v3.0 SIP area

Supply ChainStrategy & Policy


& Commitment

Supply Chain Development

& Change Management

Supply Chain Performance Assessment



Service PerformanceAssessment

Service Strategy &

Policy


ServiceDevelopment &

Retirement

Resource &OperationsCapabilityDelivery

Resource PerformanceAssessment


Strategy & Policy


Plan & Commitment


Product Development& Retirement

Product & Offer Portfolio

Capability Delivery

Product & Offer Portfolio Strategy,Policy & Planning

MarketingCapability Delivery

Product & Offer Business

Planning & Commitment

Product, Marketing & CustomerPerformanceAssessment


MarketStrategy &

Policy



& Promotion



















Strategy &Commit






Customer

The Enterprise Management HierarchyThe Enterprise Management Hierarchy

EnterpriseManagement

DisasterRecovery,Security &FraudManagement

HumanResourcesManagement

Financial &AssetManagement

Stakeholder &ExternalRelationsManagement

EnterpriseQualityManagement,Process & ITPlanning &Architecture



BrandManagement,MarketResearch &Advertising

Group EnterpriseManagement

BusinessDevelopment

EnterpriseArchitecturePlanning

Strategic &Business Planning

FinancialManagement

ProcurementManagement

Real EstateManagement

BrandManagement

Advertising

Market Research& Analysis

Workforce Strategy

Employee & LaborRelationsManagement

WorkforceDevelopment

HR Policies &Practices

PR & CommunityRelationsManagement

ShareholderRelationsManagement

RegulatoryManagement

Legal Management

Research &Development

TechnologyAcquisition

ProcessArchitectureManagement &Support

InformationSystems Strategy& Planning

KnowledgeManagement

Enterprise QualityManagement

SecurityManagement

FraudManagement

DisasterRecovery &ContingencyPlanning

eTOM in a B2B ContexteTOM in a B2B Context

Operations

Customer

Fulfillment Assurance BillingOperations Support& Readiness


InfrastructureLifecycle Mgmt

Product Lifecycle Mgmt

Strategy & Commit

Strategy, Infrastructureand Product

Stakeholder & External Relations Management

Human ResourceManagement

Disaster Recovery Security& Fraud Management

Enterprise Quality Mgmt, Process&IT Planning & Architecture


Strategic & Enterprise Planning Research & Development& Technology Acquisistion

Brand Management, MarketResearch & Advertising








Marketing and Offer Management

© TeleManagement Forum April, 2003

B2B

Env

ironm

ent

Sell Side

Buy Side

Operations

Customer

Fulfillment Assurance BillingOperations Support& Readiness


InfrastructureLifecycle Mgmt

Product Lifecycle Mgmt

Strategy & Commit

Strategy, Infrastructureand Product

Stakeholder & External Relations Management

Human ResourceManagement

Disaster Recovery Security& Fraud Management

Enterprise Quality Mgmt, Process&IT Planning & Architecture


Strategic & Enterprise Planning Research & Development& Technology Acquisistion

Brand Management, MarketResearch & Advertising








Marketing and Offer Management

© TeleManagement Forum April, 2003

B2B

Env

ironm

ent

Sell Side

Buy Side

Element Management

Network Management

BusinessManagement

ServiceManagement

Operations


















Strategy &Commit






Customer

TMN Layers correspond with TOM horizontals

TOM processes are captured in “FAB” area of eTOM Operations

eTOM maps the NGOSS Business View

Network and Systems Management Processes

Service Development and Operations Processes

Customer Care Processes

Customer

Network Element Management Processes

Information System

s Managem

ent Processes

NetworkPlanning andDevelopment

NetworkProvisioning

NetworkMaintenance &

Restoration

Network DataManagement

NetworkInventory

Management

ServicePlanning andDevelopment

ServiceProblem

Management

ServiceQuality

Management

Rating andDiscounting

ServiceConfiguration

Customer Interface Management Processes

Sales OrderHandling

Invoicingand

Collections

ProblemHandling

CustomerQoS

Management

Physical Resource and Information Technology

System

s

Analysis

&Desi

gn

System

s

System

s

Analysis

&

Analysis

&Desi

gn

Design

Shar

ed

Info

rmat

ion

&

Data

Mod

el(S

ID)

Business

Process Analysis

& Design

Business

Business

Process Analysis

Process Analysis

& Design

& Design

Business

Process Map

(eTOM)

Com

plia

nce

Test

s

Solutio

n

Confor

mance

Test

ingSolutio

n

Solutio

n

Confor

mance

Confor

mance

Test

ing

Test

ing

SolutionAnalysis &

Design

Solution

SolutionAnalysis &

Analysis &DesignDesign


Technology

Neutral ArchitectureNGOSSNGOSS

SupportingSupportingToolsTools

SID Aggregate Business EntitiesSID Aggregate Business Entities

Supplier/Partner

Supplier/Partner Performance

Supplier/Partner Payment

Supplier/Partner Bill InquirySupplier/Partner Interaction

Supplier/Partner Product

Supplier/Partner Order

Supplier/Partner Problem

Supplier/Partner Statistic

Supplier/Partner SLA

Supplier/Partner Plan

Supplier/Partner

Supplier/Partner Bill

Resource

Logical Element

Resource Order

ResourcePerformance Trend

Resource OutageCorrection

Resource TrafficTrend

Resource UsageLogical Resource

Specification

Physical ResourceSpecification

Network TopologyPhysical ResourceResource

PerformanceResource Alarm

and OutageResource Traffic

Resource PlanResource TestResource Fault Resource Traffic

ControlService

Service Specification Service Service Outage Service Quality Service Usage

Service Plan Service Order Service Trouble Service Test

Market/Sales

Market Strategy and Plan

Market Segment

Contact/Lead/ProspectMarketing Campaign

Competitor

Sales Channel

Sales Statistic

ProductStrategic Product

Portfolio PlanProduct Specification

Product Usage Statistic

Product Performance

Product Offering

Product

Common Business Entities

Business Interaction Agreement

Party Location Policy

Customer

Applied Customer BillingRate

Customer Bill Collection

Customer Bill Inquiry

Customer Interaction Customer Problem

Customer Statistic

Customer Order Customer SLA

Customer Bill

Customer

Enterprise(Still to be finalised)

Party Party –– Basic ModelBasic Model

Individual ValueNetworkRole

Customer Intermediary ServiceProvider

ThirdPartyServiceProvider

Vendor

ComplementaryProvider

Employee

PartyRole0..n

0..nParty

1 0..n1 0..nhasPartyRoles

Organization

involvedPartyRoles

0..n

PartyRoleDetails

LocationLocation

LocationRole

LocationSpecification

Location

0..n

1

0..n

1playedBy

0..n

0..n

0..nmadeUpOf

0..n0..n

1

0..n

1 definesManagedEntity

0..n

0..n

0..n

0..n

identifiesPlacementOf

ManagedEntityPlacement

Address GeographicArea0..n0..n 0..n0..n

liesWithinStructure LocationCoordinate

0..n0..n

0..n0..n

identifiesAddress0..n0..n 0..n0..n

identifiesGeographicArea

0..n 0..n0..n 0..n

identifiesStructure

Business InteractionBusiness Interaction

hasInteractions

NotificationAgreement ResponseRequest

InteractionRelationship

InteractionPartyRoleinteractionRole

Command

InteractionTypeinteractionTypeNameinteractionTypeDescription

PartyRole

Location

InteractioninteractionDateinteractionDescriptioninteractionDateCompleteinteractionStatusinteractionID

0..n 0..n0..n 0..n

0..n

1

+categorizedBy

0..n

1

0..n

0..n

0..n

0..n

0..n

0..n

0..n

0..n

InteractionItemquantityaction0..n

0..n

0..n

0..n

1..n1

1..n1

comprises

InteractionPlace

0..n

0..n

0..n

0..ninteractionItemLocation

hasInteractionItems

interactionLocation

participatesIn

Domain Model StatusDomain Model Status

Enhancements to existing workParty, BusinessInteraction, Location, Customer

New work in Phase IIICalendar (part of Project)Product PricePolicyLogicalResourceExtended Service Domain ABEs

ProjectProject

Product PricingProduct Pricing

Policy OverviewPolicy Overview

PolicySet

PolicyEvent

PolicyGroup

PolicyAction

PolicyCondition

Policy

PolicyStatement

0..n

0..1

0..n

containedPolicySets0..1

PolicyStatement is used by PolicyCondition and PolicyAction subclasses

PolicyEventSet

0..n1 0..n1 {filled in by eventConstraint}

hasEvents

0..n

0..1

0..n

0..1{filled in by executionConstraints}

controlsExecutionOf

PolicyRule 1..n

1..n

1..n

{ordered}

1..n

policyActionInPolicyRule

1..n 1..n1..n 1..n {ordered}

policyConditionInPolicyRule

1..n

1..n

1..n

{filled in by triggerConstraints}1..n

isTriggeredBy

ProductProduct--ServiceService--ResourceResource

ProductSpecification

0..n 0..10..n

involvedProductSpecs

0..1

ProductOffering0..n0..1 0..n

involvedProductOfferings

0..1

1

0..n

1

0..n

madeAvailableAs

Product1 0..n1 0..nofferedAs

Resource

ProductItem1 1..n1 1..nhasProductItems

1

0..n

1

0..n

resourceRealizedAs


1

0..n

1

0..n

serviceRealizedAs


0..n0..n 0..n0..n


PhysicalResource

1

1..n

1

1..n


LogicalResource

1

1..n

1


0..n0..n 0..n0..n


Service

Resource OverviewResource Overview

ResourceSpecification Resource0..1 0..n0..1 0..nspecifiesResource

EntitySpecification CollectionManagedEntity0..1 0..n0..1 0..nspecifiesManagedEntity

10..n 10..n collectedEntities

LogicalResourceSpecification

PhysicalResourceSpecification

0..n 0..n0..n 0..n

lResSpecBindsToPResSpec

LogicalResource

0..n0..1 0..n0..1

specifiesLogicalResource

ReplacementSet

PhysicalResource

0..1 0..n0..1 0..n

specifiesPhysicalResource

0..n0..n 0..n0..n


0..1

0..n

0..1

0..n

replacedBy

PhysicalResource HighlightsPhysicalResource HighlightsPhysicalResource

ManagedHardware

PhysicalDevice

PhysicalContainerPhysicalPort

Hardware

0..1 0..n0..1 0..nconsistsOf

PhysicalConnector

EquipmentEquipmentHolderAuxiliaryComponent PhysicalComponent

LogicalResource HighlightsLogicalResource Highlights

LogicalDeviceLogicalDevice RolesRoles

DeviceInterfaceRole

PhysicalResourceRole

LogicalDeviceRolePhysicalDeviceRole0..n0..n 0..n0..n

requiresHardwareSupportFor

LogicalResourceRole

CPELogicalDeviceRole

PELogicalDeviceRole

PLogicalDeviceRole

AggregationInterface

CoreInterface

EdgeInterface

RoutingRole

SwitchingRole

FirewallRole

PhysicalRouterRole

PhysicalHolderRole

PhysicalHardwareRole

PhysicalAdapterRole

PhysicalEncryptionRole

PhysicalFirewallRole

PhysicalSwitchRole

Example: Business to Network ModelExample: Business to Network Model

C ustom er P roduct1 ..n1 ..n 1 ..n1 ..n

buys

D evice1..n

1

1..n

1

uses

C o nfiguratio n1..n

1

1..n

1has

S ervice1..n

1

1..n

1

opera tes

1..n

1

defines

1..n

1

Changes to Product

Changes toConfigurationChanges toConfiguration

Changes to Service

SLA1

1

1signsUpFor

1..n

1governs

1

Changes to Service Level Agreement

Changes toConfiguration

ServiceService

Service


ResourceResourceRole1 0..n1 0..n

resourceHasRoles

PhysicalResourceRole


PhysicalResource

1

1..n

1

1..n


LogicalResource

1

1..n

1


0..n0..n 0..n0..n


LogicalResourceRole

ServicePackageServicePackage, , ServiceBundleServiceBundle, QoS, QoS

ResourceFacingServiceAtomic

ResourceFacingServiceComposite


1

0..n

1

0..n

rfsProductHasResourceFacingServices

TrafficIdentificationService

TrafficConditioningService

QoSService

0..n

0..1

0..n

hasQoSSubServices

0..1

0..1

0..n

0..1

0..n

identifiesQoSService

0..1

0..n

0..1

0..nconditionsQoSService

NetworkForwardingService

0..n

0..n

0..n

nextService0..n

1 1..n1 1..nforwardingDefinedBy

CoS1Package

CoS2Package

CoS3Package

CoS4Package

ServiceBundleServicePackage 1 0..n1 0..npackageContainsServiceBundle

CustomerFacingService0..n

0..n0..n

0..n


CustomerFacingServiceSpecAtomic

CustomerFacingServiceSpec

1 0..n1 0..n

specifiesCustomerFacingService

CustomerFacingServiceSpecComposite

1

0..n

1

0..n

hasCustomerFacingServiceSpecs

Decomposition of NGOSS ComponentDecomposition of NGOSS Component

contains one or more

functionality is definedby one or more

management isdefined by

management isdefined by

is implemented by is implemented by is implemented by

Component

ComponentMgnt. Contract

Service

ComponentMgnt. Contract

Instance

ServiceMgnt. Contract

ServiceFunctionalContract

ServiceMgnt. Contract

Instance

ServiceFunc. Contract

Instance

Component ConceptsComponent Concepts

An architectural element that represents the delivery mechanism services. A Component represents the unit of deployment in the technology-neutral architecture and offers one or more services.A unit of manageability within the technology-neutral architecture.

Service ConceptsService Concepts

A collection of functionality described by one or more contracts.A service is a unit of manageability.The functionality comprising the service is described by contracts.The functionality comprising the service is accessed through contract instances.

The NGOSS Technology Neutral Component The NGOSS Technology Neutral Component ModelModel

An implementation of functionality,Subject to 3rd party composition,Conformant to a component modelContractually specified

i.e., containers for contract instances

For high availability environments …A component instance may not have persistent state

Component CharacteristicsComponent CharacteristicsA component is an artifact. The service(s) provided by a component must be specified by NGOSS Contract(s)Must be manageable through a contract.A component must be specified and constructed in such a way as to enable it to be deployed and installed into a system without the need for the use of a trial-and-error process. A component must have all of its external (contextual) dependencies explicitly defined.

Component Characteristics (2)Component Characteristics (2)

Given the contractually defined services, and the explicitly defined external (contextual) dependencies,

a component can be combined in a system with other components to deliver a service that is then available to all other components (and client applications) within the system.

Conforms to a technology specific component model to enable a component execution environment to activate and thus make available for use, the contract implementations within a component

Contract ConceptsContract ConceptsBasicsBasics

Interfacea coherent set of operations on a component that clients of that component can depend on using

Contractthe rules and constraints for interaction via the Interface associated with the Contracta Contract represents the unit of binding in the technology-neutral architecture

Contract instancea runtime manifestation of a contract-defined interface

Contract Concepts (2)Contract Concepts (2)OperationsOperations

An Operation is defined as:an interaction between a client component and a server componentTwo types of operations:

Announcement Operations (one-way)

– Invocation (client to server)– Action (server)

Interrogation Operations (two-way)

– Invocation (client to server)– Action (server)– Termination (server to client) (maybe more than one per

Operation)


Announcement Operationan interaction – the invocation – initiated by a client component instanceresulting in the conveyance of information from that client component instance to a server component instance,requesting a function to be performed by that server component instance.


Interrogation OperationAn interaction consisting of:

The initial interaction – the invocation – initiated by a client component instance

– resulting in the conveyance of information from that client component instance to a server component instance,

– requesting a function to be performed by that server component instance

A second interaction – the termination –– initiated by the server component instance– resulting in the conveyance of information from the

server component instance to the client component instance in response to the invocation

Contract Concepts (5)Contract Concepts (5)SignaturesSignatures

Interface signatures:an interface signature comprises a set of announcement and interrogation signaturesone for each operation type in the interface.

Announcement signature:A definition of the name of the invocationThe number, names and types of its parameters.

Interrogation signature: A definition of the following elements:

– The name of the invocation;– The number, names and types of the invocation

parameters– A finite, non-empty set of definitions, one for each

possible termination type of the invocation; » each definition contains the name of the termination

and the number, names and types of its parameters.

Contract Concepts (6)Contract Concepts (6)BindingBinding

Binding mechanism:an infrastructure mechanism that enables a client component to establish a binding to a server component

NGOSS PoliciesNGOSS Policies

The NGOSS Policy Sub-system is the “Supervisor of Operations”. For example, policies can be used to:

Define standard values (assures consistent values as function of defined environmental factors)Define peering relationships that must be maintainedIdentify (or change) the set of services available based on environmental factors

Proposed Policy ArchitectureProposed Policy Architecture

Policy Server

Policy DecisionPoint – Tech 1

Proxy


Policy Broker(Including Validation and Conflict Detection Logic)


Policy Enforcement Points

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

Policy Rules andAssociated Data

Policy decision local to the

device

Policy decision local to a

policy server

Global policy decisions

Policy EntryConsole

Policy EntryAPI

Policy Definition Tool

PolicyControllerCoordination

within a Policy Server

Multiple types of

PDPs for multiple

technologies

Policy Repository

Policy Server


Proxy




Policy Enforcement Points

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

��

Policy Rules andAssociated Data

Policy decision local to the

device

Policy decision local to a

policy server

Global policy decisions

Policy EntryConsole

Policy EntryAPI

Policy Definition Tool

PolicyControllerCoordination

within a Policy Server

Multiple types of

PDPs for multiple

technologies

Policy Repository

The Policy ContinuumThe Policy Continuum

Administrator View: Device- Independent, Technology-Specific OperationAdministrator View: Device- Independent, Technology-Specific Operation

System View: Device- and Technology-Independent OperationSystem View: Device- and Technology-Independent Operation

Business View: SLAs, Processes, Guidelines, and GoalsBusiness View: SLAs, Processes, Guidelines, and Goals

Device View: Device- and Technology-Specific OperationDevice View: Device- and Technology-Specific Operation

Instance View: Device-Specific MIBs, PIBs, CLI, etc. ImplementationInstance View: Device-Specific MIBs, PIBs, CLI, etc. Implementation

Configuration Management Process

ConstructConfiguration

ChangesDeploy Configuration Changes

Policy Feeds Process Which Selects PolicyPolicy Feeds Process Which Selects Policy

Policy Selects WhoPerforms Which

Tasks When

ApprovalProcess

Policy DefinesWho and How

Many ApprovalsAre NeededPer Change

InstallationProcess

Policy DefinesHow the

Changes areInstalled

ValidationProcess

Policy DefinesHow the

Changes areValidated

Business Rules

Security ContextsSecurity Contexts

Identity and AuthenticationAuthorization (access control)PrivacyIntegrityAttribution (non-repudiation)Availability

NGOSSIdentifierNGOSSIdentifier

NGOSSIdentifiertnaVersion : Stringauthority : String

Namespace GeneralizableElement


Element

NGOSSExtensibleElementNGOSSExtensibleElement

Element



Namespace

BehavioralFeatureClassifier StructuralFeaturemultiplicity : Multiplicitychangeability : ChangeableKindtargetScope : ScopeKindordering : OrderingKind

Attribute



NGOSSExtensibleElement 0..1

0..n

0..1

0..n

ngossFeatures

1

1

1

1identifies

Using NGOSSExtensibleElementUsing NGOSSExtensibleElement

Element



Namespace

BehavioralFeatureClassifier StructuralFeaturemultiplicity : Multiplicitychangeability : ChangeableKindtargetScope : ScopeKindordering : OrderingKind

Attribute




0..n

0..1

0..n

ngossFeatures

1

1

1

1identifies

SharedInformationobjectID : String

NGOSSComponent Contract

0..n0..n

0..n0..n

uses

0..n 1..n0..n 1..n

exposesFunctionalityBy

0..10..1 0..1

extends<<NGOSSExtension>>

0..1

NGOSSComponentNGOSSComponent

ModelElement

GeneralizableElementNamespace

Class

BehavioralFeature

Feature

NGOSSIdentifier NGOSSExtensibleElement

StructuralFeature

0..10..1 0..1


0..10..1

0..n

0..1

0..n

ngossFeatures

11 11

identifies

Classifier

NGOSSComponent

ContractContract

ModelElement


BehavioralFeatureClassifier

StructuralFeature

Attribute

FeatureNGOSSIdentifier


0..n

0..1

0..n

ngossFeatures

1

1

1

1

identifies0..10..1 0..1


0..1

SharedInformationNGOSSComponent Contract

0..n0..n 0..n0..nuses

0..n 1..n0..n 1..n


NGOSSInteractionNGOSSInteraction

ModelElement


Collaboration

Interrogation Announcement

NGOSSInteraction

Terminations and InvocationsTerminations and Invocations

Collaboration

Announcement

Operation

NGOSSContractTermination

Interrogation

NGOSSExtensibleElement

NGOSSContractInvocation

NGOSSInteraction

NGOSSComponent ContractSharedInformation NGOSSContractOperation

1..n

1

1..n

1

terminates

0..10..1 0..1


0..1

1

1

1

1

invokes

1..n0..n 1..n0..n


1..n1 1..n1

{opNamesare unique}

employs

0..n0..1

0..n0..1

usesSharedInfo

NGOSSPolicyNGOSSPolicy

ModelElement


Class

BehavioralFeatureClassifier StructuralFeature

Attribute

SharedInformationNGOSSComponent Contract

0..n0..n 0..n0..nuses

0..n 1..n0..n 1..n


FeatureNGOSSIdentifier

NGOSSPolicy


0..n

0..1

0..n

ngossFeatures1

1

1

1

identifies

0..10..1 0..1


0..1

0..n

0..n

0..n

0..n

governs

NGOSSPolicyApplicationRules

NGOSSPolicyClass

Using NGOSS Data TypesUsing NGOSS Data Types

UMLDataTypeUMLMetaModel

NGOSSDataTypeNGOSSMetaModel

InformationType

TechnologySpecificDataTypeNGOSSDomainSpecificDataModel

1..n1..n

TechnologySpecificEncodingNGOSSDomainSpecificEncoding

represents

1..n1..n

OMG Standards

TMF Standards

TMF Domain Neutral Info Model

TMF Domain Specific Data Model

TMF Domain Specific Implementation

TMF Working Group Standards

NGOSSDomainSpecificMetaModel NGOSSDomainDataType

NGOSSDomainSpecificInformationModel

realizes

built from

1..n1..n

encodes

implements

(TeleManagement Forum & NGOSS Program Overview) · (TeleManagement Forum & NGOSS Program Overview)...

Documents

Transcript of (TeleManagement Forum & NGOSS Program Overview) · (TeleManagement Forum & NGOSS Program Overview)...