introduction to ngoss - postechdpnm.postech.ac.kr/papers/tmw/tmw2004-longbeach/intro to ngo… ·...
Post on 18-Aug-2018
231 Views
Preview:
TRANSCRIPT
All Rights ReservedPage No. - 1Copyright 2004. All Rights ReservedPage 1 Training Plus Copyright 2004. All Rights ReservedPage 1 Training Plus Copyright 2004. All Rights ReservedPage 1 Training Plus
TM Forum Training Plus at TeleManagement WorldLong Beach, USA - 11th October 2004
Introduction to NGOSS
Joel J. Fleck, IIChief Architect, Hewlett-Packard
Cliff C. FaurerTechnical Director, NGOSS Program
Nick WebbSenior Engineer, QinetiQ
Giuseppe CovinoProject Manager, Telecom Italia Labs
All Rights ReservedPage No. - 2Copyright 2004. All Rights ReservedPage 2 Training Plus Copyright 2004. All Rights ReservedPage 2 Training Plus Copyright 2004. All Rights ReservedPage 2 Training Plus
Agenda
9.00 Welcome9.00 NGOSS Background and Basics9.30 NGOSS Lifecycle and Methodology
10.00 NGOSS eTOM Overview10.30 Break11.00 NGOSS SID Overview11.30 NGOSS Architecture Overview12.00 NGOSS Documents and Specifications12.30 Lunch
All Rights ReservedPage No. - 3Copyright 2004. All Rights ReservedPage 3 Training Plus Copyright 2004. All Rights ReservedPage 3 Training Plus Copyright 2004. All Rights ReservedPage 3 Training Plus
Housekeeping
CourtesyMobiles, Pagers, etc.
Q&ADuring Breaks, Start/End of Sessions, End of Day
FeedbackEvaluation Forms
All Rights ReservedPage No. - 4Copyright 2004. All Rights ReservedPage 4 Training Plus Copyright 2004. All Rights ReservedPage 4 Training Plus Copyright 2004. All Rights ReservedPage 4 Training Plus
TeleManagement World Training PlusLong Beach, USA - 11th October 2004
NGOSS Background and Basics
Cliff C. Faurer, TM ForumTechnical Director – NGOSS Program
NGOSS Steering CouncilNGOSS Architecture Board
NGOSS Lifecycle and Methodology TeamNGOSS SID Team
All Rights ReservedPage No. - 5Copyright 2004. All Rights ReservedPage 5 Training Plus Copyright 2004. All Rights ReservedPage 5 Training Plus Copyright 2004. All Rights ReservedPage 5 Training Plus
AgendaNGOSS Background & Basics
NGOSS Lifecycle and Methodology
NGOSS eTOM: Business Processes
NGOSS SID: Shared Information Data Model
NGOSS TNA: Technology Neutral Architecture
NGOSS: Documents and Specifications
All Rights ReservedPage No. - 6Copyright 2004. All Rights ReservedPage 6 Training Plus Copyright 2004. All Rights ReservedPage 6 Training Plus Copyright 2004. All Rights ReservedPage 6 Training Plus
What is the TM Forum?Non-profit global consortium focused on Business and Operations Support Systems (BSS/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 - 380+ members in 36 countriesProvides a collaborative environment in which companies can address service providers’ most critical business and technical requirementsProvides an on-line knowledge base featuring industry information and potential solutions.
NGOSS Lean Operator
All Rights ReservedPage No. - 7Copyright 2004. All Rights ReservedPage 7 Training Plus Copyright 2004. All Rights ReservedPage 7 Training Plus Copyright 2004. All Rights ReservedPage 7 Training Plus
What are the Challenges!Service Price – can’t drop costs fast enough to keep up!
Service TypesCommodity services – razor thin margins, demand efficiencyAdvanced services – better margins, demand flexibility 1999 2000 2001 2003 2004 2005
Uni
t cos
ts/ r
eve n
ues
Average revenue /unit
Average cost/unit
Sale
s Vo
lum
e
TornadoTornado
Main Street
Main Street
Early market
Early market
Time
Chasm
Service LifecycleEarly market Systems must be capable of being quickly turned up to meet demand or turned off without a huge investmentTornado Systems must scale & be flexible enough to handle significant volume. Market leader can set price. Many operators stumble at this pointMain street Volumes and revenue significant - need zero-touch, ultra low cost operations to maintain margins in commodity market.
Based on Geoffrey A. Moore
All Rights ReservedPage No. - 8Copyright 2004. All Rights ReservedPage 8 Training Plus Copyright 2004. All Rights ReservedPage 8 Training Plus Copyright 2004. All Rights ReservedPage 8 Training Plus
Not Just Saving Money – But Making Money!
Medium term :Reduce churn through improved customer serviceImprove ‘wallet share’through better targetingDrive more new services, with reduced time to revenueReduce opex through highly automated processes
Short-term :•Reduce opexthrough improved
• asset management• bandwidth management
Immediate :•Plug revenue leakages•Plug fraud leakages
Immediate :•Plug revenue leakages•Plug fraud leakages
Strategic = ultra low cost baseTacticalThe Death Spiral of Cutting Costs!
The Path to Profits!Declining profitability
Market share declines
Customer service and quality declines
Across the board opex and capexcuts
Declining
profitability
All Rights ReservedPage No. - 9Copyright 2004. All Rights ReservedPage 9 Training Plus Copyright 2004. All Rights ReservedPage 9 Training Plus Copyright 2004. All Rights ReservedPage 9 Training Plus
NGOSS: Becoming a Lean Operatorby
Reducing the ‘Interoperability Tax’
All Rights ReservedPage No. - 10Copyright 2004. All Rights ReservedPage 10 Training Plus Copyright 2004. All Rights ReservedPage 10 Training Plus Copyright 2004. All Rights ReservedPage 10 Training Plus
Today’s Back-office ModelM
arke
ting
Sal
es
Cus
tom
er
serv
ice
Eng
inee
ring
Pla
nnin
g
Fina
nce
No one owns the end-to-end process of delivering serviceOrganized around internal fiefdoms - not the customer.
No one owns the end-to-end process of delivering serviceOrganized around internal fiefdoms - not the customer.
High manpower costs because of a lack of automated process flow-through
Poor time-to-revenue because of rigid and inflexible business processes
Weak customer service because of poorly integrated systems with inaccurate data
Slow growth because processes and systems can’t scale
Slow new service introduction because of inflexible systems with high costs to make changes
Poor economies of scale because of fragmented acquisitions and too many suppliers.
All Rights ReservedPage No. - 11Copyright 2004. All Rights ReservedPage 11 Training Plus Copyright 2004. All Rights ReservedPage 11 Training Plus Copyright 2004. All Rights ReservedPage 11 Training Plus
Today, Around 50% of allOSS/BSS Spending is Not Productive
But up to 50% is spent on
integrating dissimilar systems
That ‘integration tax’ could be slashed if operators bought against common standards.
Around 12% CapExor around 4%of revenues isspent on OSS/BSS
All Rights ReservedPage No. - 12Copyright 2004. All Rights ReservedPage 12 Training Plus Copyright 2004. All Rights ReservedPage 12 Training Plus Copyright 2004. All Rights ReservedPage 12 Training Plus
NGOSS Lean Operator: Vision & Goals
Transform the business to deliver sustainable quality, customer service and revenues through:
Ultra low cost operationsHigh levels of automation and integrationInformation integrityCustomer self managementLow cost of changeCommercially available, off-the-shelf, solutions
Highly flexible infrastructureService development at Internet speedFast time-to-revenueRapid response to business changes and competitionReal-time flow-through service deliverySLA guarantees.
All Rights ReservedPage No. - 13Copyright 2004. All Rights ReservedPage 13 Training Plus Copyright 2004. All Rights ReservedPage 13 Training Plus Copyright 2004. All Rights ReservedPage 13 Training Plus
NGOSS – New Generation Operations Systems and Software
Industry-agreed, business and systems framework to guide the implementation of improved business behaviour (processes and policies):
Defines methodologies for evolving OSS and BSS infrastructure into a lean operations approachSpecifies the key characteristics of OSS/BSS that allow high degrees of process integration and automationDeveloped by major operators and suppliers worldwideDriven and managed by TM ForumImplemented as a set of best practices captured as information models.
All Rights ReservedPage No. - 14Copyright 2004. All Rights ReservedPage 14 Training Plus Copyright 2004. All Rights ReservedPage 14 Training Plus Copyright 2004. All Rights ReservedPage 14 Training Plus
Hitchhiker’s Guide to NGOSSLifecycle and Methodology
Supports multiple views on stakeholder concernsProcess and activity driven – captured as Use CasesIterative with Feedback
ArchitectureTechnology-neutral frameworkTechnology-specific implementations defined
FrameworkCombination of policy and process managementShared information and data modelsFederation through information models
InteroperabilityContract- and component-based
CommunicationDistributed networking and computing services
ComplianceTestable and provable.
All Rights ReservedPage No. - 15Copyright 2004. All Rights ReservedPage 15 Training Plus Copyright 2004. All Rights ReservedPage 15 Training Plus Copyright 2004. All Rights ReservedPage 15 Training Plus
NGOSS Key Concepts
Views – “focus on particular concerns within a system”Framework – “supporting or enclosing structure”Lifecycle – “traceability and consistency between all phases”Methodology – “system of principles and procedures applied to a discipline”Architecture – “style or method of design and construction.”
All Rights ReservedPage No. - 16Copyright 2004. All Rights ReservedPage 16 Training Plus Copyright 2004. All Rights ReservedPage 16 Training Plus Copyright 2004. All Rights ReservedPage 16 Training Plus
NGOSS Pedigree (Where Did It Come From?)
Bellcore (now Telcordia) NGS, OSCA, XIS and INA ArchitecturesANSA ProjectTINA-C ArchitectureISO and ITU-T RM-ODPTMForum TMNTMForum TOMOMG MDA and UMLHP INA DPE and ExtensionsHP ISMDMTF DENDEN-ngEU FORM Project.
All Rights ReservedPage No. - 17Copyright 2004. All Rights ReservedPage 17 Training Plus Copyright 2004. All Rights ReservedPage 17 Training Plus Copyright 2004. All Rights ReservedPage 17 Training Plus
Who are the Lead Players in NGOSS Development?
All Rights ReservedPage No. - 18Copyright 2004. All Rights ReservedPage 18 Training Plus Copyright 2004. All Rights ReservedPage 18 Training Plus Copyright 2004. All Rights ReservedPage 18 Training Plus
NGOSS Lean Operator: Strategy
Goal, Context, Capabilities and Constraints
A Blueprint for changeUnderstand the current behaviorsCommunicate the desired behaviorsActionable plan to implement the necessary changesContinuous monitoring and management to maintain desired course
Policies and Processes drive behavior.
All Rights ReservedPage No. - 19Copyright 2004. All Rights ReservedPage 19 Training Plus Copyright 2004. All Rights ReservedPage 19 Training Plus Copyright 2004. All Rights ReservedPage 19 Training Plus
Maturing of Problem Solving & Solution CreationSeparation of Concerns
Business Process+
Business Rules+
Functions+
Data
Business Rules+
Functions+
Data
Business Process
Functions+
Data
Business Process
Business Rules
Use C
aseP
rocessP
olicyC
ontractB
u s
I n
e s
sS
y s
t e
m s
NGOSS Method
Legacy SOA NGOSSArchitectural Style
All Rights ReservedPage No. - 20Copyright 2004. All Rights ReservedPage 20 Training Plus Copyright 2004. All Rights ReservedPage 20 Training Plus Copyright 2004. All Rights ReservedPage 20 Training Plus
A View on a Business Challenge
Soft Constraints
Derivations
Hard Constraints
Enterprise Context
CapabilitiesCapabilities
Goal
Business requires fluid adaptability at all levels:• Process and Policy: rules are “applied” to govern the expected behavior (both at
people and systems level) to achieve the desired outcome – reach the goal!
• People: effective collaboration, decision making and accountability throughout the solution lifecycle: business – system – implementation – deployment
• Technologies: require technology neutral architecture framework capable of integrating and being implemented by any technologies.
All Rights ReservedPage No. - 21Copyright 2004. All Rights ReservedPage 21 Training Plus Copyright 2004. All Rights ReservedPage 21 Training Plus Copyright 2004. All Rights ReservedPage 21 Training Plus
Beyond SoA: NGOSS System Architecture …
Problem Statement – Use CaseSolution Statement – Contract
Methodology to link and maintain traceability of stakeholder accountability and full satisfaction of concerns
Requires cultural changes in solution development process
Holistic development governed by the defined frameworkHighly iterativeInclusive of all stakeholders.
Goal
Rules
Mgmt Info
NGOSS Business Contract
NGOSS Use CaseName:Scope:Level:Audience:Primary Actor(s):Supporting Actor(s):Primary Goal(s):Stakeholder Goal(s):
Policies:Processes:Pre-conditions:Post-conditions:Triggers:Main scenario:Extension scenarios:
Process
LimitationsCapabilities
Activity
Roles
Specification
Context
Obligations
Benefits
Party Role
OAMConcepts
Mgmt Method
All Rights ReservedPage No. - 22Copyright 2004. All Rights ReservedPage 22 Training Plus Copyright 2004. All Rights ReservedPage 22 Training Plus Copyright 2004. All Rights ReservedPage 22 Training Plus
NGOSS Framework ExamplesLogical Information Framework Process Framework
e.g. Product,SLA cluster
e.g. Billing, inventorycluster
e.g. Applicationresource cluster
e.g. Service definitionService bundle cluster
policy
• Holistic information architecture
• Focus on information not data architecture
• Enable stakeholders (business, architects, developers, operations) to focus on specific solutions but with a holistic view of the overall solution interactions.
e.g. Network/Systemresource cluster
Definition- Resource Management and Operations: This horizontal functional process grouping maintains knowledge of the resources within scope …..
Do we have a quick answer of who is responsible for this? What is the KPI for service XYZ in this area?
Definition- Resource Configure & Activate: responsible for configuring and activating the resources reserved for supporting a specific service instance ……
Do we have a quick answer of who is responsible for this? Which system is used for configure/activate service XYZ using technology ABC?
All Rights ReservedPage No. - 23Copyright 2004. All Rights ReservedPage 23 Training Plus Copyright 2004. All Rights ReservedPage 23 Training Plus Copyright 2004. All Rights ReservedPage 23 Training Plus
NGOSS Lifecycle and MethodologyAddress all Stakeholder Views
No big bang project, must use tools to make knowledge visible and manageable through each solution project iteration.
Implementation
SystemBusiness
Deployment
Knowledge Base
Design Standards & Process
• System Architecture• Policy Model• Information Model• System Contract
Operational Environment
• Component Instance• Policy Instance• Data Instance• Contract Instance
Implementation Choices
• Components• Policy Spec.• Data Model• Contract Implementation
Repository of Reusable Best
Practices – process, policy, capabilities,
etc.
Business Scope, Goals, Missions
• Business Process• Business Policies• Business View Info Model• Business Contract
All Rights ReservedPage No. - 24Copyright 2004. All Rights ReservedPage 24 Training Plus Copyright 2004. All Rights ReservedPage 24 Training Plus Copyright 2004. All Rights ReservedPage 24 Training Plus
TeleManagement World Training PlusLong Beach, USA - 11th October 2004
NGOSS Lifecycle and Methodology
Joel Fleck, Hewlett-PackardNGOSS Steering Council
NGOSS Architecture BoardNGOSS Lifecycle and Methodology Team
NGOSS Contract Working Group
All Rights ReservedPage No. - 25Copyright 2004. All Rights ReservedPage 25 Training Plus Copyright 2004. All Rights ReservedPage 25 Training Plus Copyright 2004. All Rights ReservedPage 25 Training Plus
AgendaNGOSS Background & Basics
NGOSS Lifecycle and Methodology
NGOSS eTOM: Business Processes
NGOSS SID: Shared Information Data Model
NGOSS TNA: Technology Neutral Architecture
NGOSS: Documents & Specifications
All Rights ReservedPage No. - 26Copyright 2004. All Rights ReservedPage 26 Training Plus Copyright 2004. All Rights ReservedPage 26 Training Plus Copyright 2004. All Rights ReservedPage 26 Training Plus
Why an NGOSS Lifecycle?
To ensure that roles, requirements, models, implementations and deployments all contribute in a holistic manner to the solutionTo provide visibility and traceability of stakeholder responsibility and accountability throughout the lifetime of an NGOSS SolutionTo provide a documented means of extending and enhancing the NGOSS Knowledge Base.
All Rights ReservedPage No. - 27Copyright 2004. All Rights ReservedPage 27 Training Plus Copyright 2004. All Rights ReservedPage 27 Training Plus Copyright 2004. All Rights ReservedPage 27 Training Plus
Why an NGOSS Methodology?
To provide a consistent, documented manner for analyzing, modeling, defining, developing, integrating, deploying and supporting NGOSS BSS/OSS Solutions.
All Rights ReservedPage No. - 28Copyright 2004. All Rights ReservedPage 28 Training Plus Copyright 2004. All Rights ReservedPage 28 Training Plus Copyright 2004. All Rights ReservedPage 28 Training Plus
Goals of the NGOSS Lifecycle & Methodology
Develop an NGOSS Lifecycle and Methodology that:Utilizes/borrows the best parts/strengths of Zachman, RM-ODP, MDA, and USDPPromotes and strongly encourages linkage between NGOSS eTOM, NGOSS SID, and NGOSS ArchitectureEmphasizes “consumer” - “provider” relationship for each level of decompositionFacilitates the identification of “testing” points that can be used to test/monitor/manage the health of both NGOSS solutions under development and deployed NGOSS solutions.
All Rights ReservedPage No. - 29Copyright 2004. All Rights ReservedPage 29 Training Plus Copyright 2004. All Rights ReservedPage 29 Training Plus Copyright 2004. All Rights ReservedPage 29 Training Plus
What Should an NGOSS Methodology Include?
A formalized specification of the Business Model/SolutionLinkages from the Business Model/Solution to the technical/realization models (i.e. Architectural Traceability):
Traceability from the business model/solution through each level of decomposition & refinement (vertical traceability)Traceability from the process model to the data model to the policy model at each level (horizontal traceability)
Documented steps and guidelines for developing an NGOSS Solution using the NGOSS MethodologyCapability of being mapped onto major Architectural FrameworksUse Case drivenIterative.
All Rights ReservedPage No. - 30Copyright 2004. All Rights ReservedPage 30 Training Plus Copyright 2004. All Rights ReservedPage 30 Training Plus Copyright 2004. All Rights ReservedPage 30 Training Plus
What Are We Borrowing?Zachman
Emphasis on Enterprise and Business Model
MDAMeta-ModelsBusiness (CIM) - Technology Neutral (PIM) - Technology Specific (PSM) Separation of ConcernsAbility to use a model to specify architectural artifacts (as the model changes, code is updated to reflect those changes)
RM-ODPViewpoints (particularly Computational, Engineering and Technology)Strong support for modeling distributed architectures
USDPUse Case DrivenIterative Approach.
CIM – Computationally Independent Model PIM – Platform Independent Model PSM – Platform Specific Model
All Rights ReservedPage No. - 31Copyright 2004. All Rights ReservedPage 31 Training Plus Copyright 2004. All Rights ReservedPage 31 Training Plus Copyright 2004. All Rights ReservedPage 31 Training Plus
Process and Policy DefinitionsNGOSS Process – Defines a flow of linked activities through a solution scenario
NGOSS Policy – Defines a set of rules that can be used to manage and control the behavior of the activities and govern their expected outcome
Policies govern which Processes to use to access, monitor, and/or implement changes to a Managed Entity. The outcome of these Processes drive the working set of Policies that govern the system behavior.
All Rights ReservedPage No. - 32Copyright 2004. All Rights ReservedPage 32 Training Plus Copyright 2004. All Rights ReservedPage 32 Training Plus Copyright 2004. All Rights ReservedPage 32 Training Plus
NGOSS Lifecycle Views
LogicalView
PhysicalView
All Rights ReservedPage No. - 33Copyright 2004. All Rights ReservedPage 33 Training Plus Copyright 2004. All Rights ReservedPage 33 Training Plus Copyright 2004. All Rights ReservedPage 33 Training Plus
Service DevelopersView
Service Providers View
NGOSS Lifecycle Views
LogicalView
PhysicalView
All Rights ReservedPage No. - 34Copyright 2004. All Rights ReservedPage 34 Training Plus Copyright 2004. All Rights ReservedPage 34 Training Plus Copyright 2004. All Rights ReservedPage 34 Training Plus
LogicalView
PhysicalView
Service DevelopersView
Service Providers View
ImplementationDeployment
Business System
Deployment Capabilities, Constraints & Context
Implementation Capabilities, Constraints & Context
Business Capabilities, Constraints & Context
System Capabilities,Constraints & Context
NGOSS Lifecycle Views
All Rights ReservedPage No. - 35Copyright 2004. All Rights ReservedPage 35 Training Plus Copyright 2004. All Rights ReservedPage 35 Training Plus Copyright 2004. All Rights ReservedPage 35 Training Plus
NGOSS Lifecycle Knowledge Base
CorporateKnowledge
Base
NGOSSKnowledge
BaseShared
eTOM
SID
TNA
All Rights ReservedPage No. - 36Copyright 2004. All Rights ReservedPage 36 Training Plus Copyright 2004. All Rights ReservedPage 36 Training Plus Copyright 2004. All Rights ReservedPage 36 Training Plus
LogicalView
NGOSS Lifecycle
PhysicalView
Service DevelopersView
Service Providers View
ImplementationDeployment
Business System
Deployment Capabilities, Constraints & Context
Implementation Capabilities, Constraints & Context
Business Capabilities, Constraints & Context
System Capabilities,Constraints & Context
CorporateKnowledge
Base
NGOSSKnowledge
BaseShared
All Rights ReservedPage No. - 37Copyright 2004. All Rights ReservedPage 37 Training Plus Copyright 2004. All Rights ReservedPage 37 Training Plus Copyright 2004. All Rights ReservedPage 37 Training Plus
NGOSS SANRR Methodology Iterate withSANRR
Iterate withSANRR
1. SCOPE : Define Solution Boundary including Solution Mission, Goals, and High-Level Use Cases
2. ANALYZE: Document existing (legacy) and desired environments with detailed Use Cases, Process Maps, Activities and Policy Lists
3. NORMALIZE: Map current view onto common vocabulary to achieve a “single unified model” (using SID)
4. RATIONALIZE: Examine normalized model for needed changes (Gap Analysis, Replication Analysis, Conflict Analysis). Terminate when no more changes are needed.
5. RECTIFY: Modify, delete or add capabilities (Contractually Specified) to resolve needed changes identified in Step 4. Once complete, cycle to Step 3.
All Rights ReservedPage No. - 38Copyright 2004. All Rights ReservedPage 38 Training Plus Copyright 2004. All Rights ReservedPage 38 Training Plus Copyright 2004. All Rights ReservedPage 38 Training Plus
Relationship of NGOSS Artifacts
NGOSSUse Cases
Currently Conceptual - NGOSS Knowledge Base processes, extension methodologies for eTOM, SID and NGOSS Contract exploitation.Processes Used
NGOSS Design and lifecycle policies tbd (draft available in J Strassner Policy base Network Management Solutions for the Next Generation)Organisation’s internal policies
Policies Used
To capture the business goals and needs in a form that can be realized with high fidelity by Systems Implementer’s in an acceptable deployment.This methodology uses a Validation Verification AND Testing (VV&T) concept over the full NGOSS Lifecycle.
Stakeholder Goals
To capture and transform a user organisation’s business goal - based on possible existing systems and organization constraints - into a set of artefacts that express the Business Requirement in a complete form that meets the pre conditions for the Systems Phase of the NGOSS Lifecycle. Some of these artifacts may be recorded in the TMF OR the Organisation’s Own Knowledge Base
Primary Goals
TMF Members, suppliers, partners, industry analysts Tertiary Actor(s)
Stakeholders for System, Implementation and Operations TMF Team members
Secondary Actor(s)
Business Analysts and programme managers in user organizationsPrimary Actor(s)
Anyone that is involved with establishing and operating the Business Phase of the NGOSS LifecycleAudience
Very High SummaryLevel
Enterprise: The activities, constraints and artifacts (e.g. business plan) needed to perform the NGOSS Business LifecycleScope
Business Phase – NGOSS LifecycleUse Case Title
CommentaryName of Field
Currently Conceptual - NGOSS Knowledge Base processes, extension methodologies for eTOM, SID and NGOSS Contract exploitation.Processes Used
NGOSS Design and lifecycle policies tbd (draft available in J Strassner Policy base Network Management Solutions for the Next Generation)Organisation’s internal policies
Policies Used
To capture the business goals and needs in a form that can be realized with high fidelity by Systems Implementer’s in an acceptable deployment.This methodology uses a Validation Verification AND Testing (VV&T) concept over the full NGOSS Lifecycle.
Stakeholder Goals
To capture and transform a user organisation’s business goal - based on possible existing systems and organization constraints - into a set of artefacts that express the Business Requirement in a complete form that meets the pre conditions for the Systems Phase of the NGOSS Lifecycle. Some of these artifacts may be recorded in the TMF OR the Organisation’s Own Knowledge Base
Primary Goals
TMF Members, suppliers, partners, industry analysts Tertiary Actor(s)
Stakeholders for System, Implementation and Operations TMF Team members
Secondary Actor(s)
Business Analysts and programme managers in user organizationsPrimary Actor(s)
Anyone that is involved with establishing and operating the Business Phase of the NGOSS LifecycleAudience
Very High SummaryLevel
Enterprise: The activities, constraints and artifacts (e.g. business plan) needed to perform the NGOSS Business LifecycleScope
Business Phase – NGOSS LifecycleUse Case Title
CommentaryName of Field
NGOSS ProcessDescriptions
Operations
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
(Application, Computing and Network)
Customer
NGOSS Policies
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
NGOSS Activities
Order Handling
CreditAuthorization
Order Issuance Order Trackingand Status
PreorderFeasibilityDetermination
Order Completion
Receive Pre-OrderFeas ibility Request
Order PlanDevelopment
Order Creation Confirm OrderCompletion withCustomer
Report unmetcommitments orcapabilities
Status Report
CustomerJeopardyNotification
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 andNegotiateAcceptable Terms
Order RequestValidation
Issue Pre-OrderFeasibility Study
CreditInvestigationDetermination
CreditInvestigation
StatusEstablishment andManagement
Manage Customerchanges toAgreement Con
Train the customer
Followup onoptimal CustomerUtilisation
© TeleManagement Forum eTOM April 200 1
TEAM DRAFT
NGOSS Contracts
ImplementContract
SystemContract
DeploymentContract
BusinessContract
1 2
34
ImplementContract
SystemContract
DeploymentContract
BusinessContract
1 2
34
contains
references
references
adjusts
selects
controls
references
interfacesdefined by
referencesdefines
references
All Rights ReservedPage No. - 39Copyright 2004. All Rights ReservedPage 39 Training Plus Copyright 2004. All Rights ReservedPage 39 Training Plus Copyright 2004. All Rights ReservedPage 39 Training Plus
Iterate withSANRR
Iterate withSANRRNGOSS SANRR Methodology
Analyze (Document Existing and
Desired Problems)Scope
Norm
alize
Ration
alize
Rectify
DeployedNGOSS
Environment
All Rights ReservedPage No. - 40Copyright 2004. All Rights ReservedPage 40 Training Plus Copyright 2004. All Rights ReservedPage 40 Training Plus Copyright 2004. All Rights ReservedPage 40 Training Plus
LogicalView
PhysicalView
Service DevelopersView
Service Providers View
ImplementationDeployment
Business System
Deployment Capabilities, Constraints & Context
Implementation Capabilities, Constraints & Context
Business Capabilities, Constraints & Context
System Capabilities,Constraints & Context
Iterate withSANRR
Iterate withSANRR
NGOSS Lifecycle with Iteration UsingNGOSS SANNR Methodology
CorporateKnowledge
Base
NGOSSKnowledge
BaseShared
All Rights ReservedPage No. - 41Copyright 2004. All Rights ReservedPage 41 Training Plus Copyright 2004. All Rights ReservedPage 41 Training Plus Copyright 2004. All Rights ReservedPage 41 Training Plus
Roles in NGOSS LifecycleCreate Solution High Level Use Case
Business System
Implementation
Solution Manager (1)Subscriber (2)Market Analyst (2)Account Manager (2)
Customer (3)
{
Business Solution Definition Use Case
{Roles
Supporting Use Cases
Roles
Solution Designer (1)Information Modeler (1)System Architect (1)Service Architect (1)
{
System Solution Design Specification Use Case
{Supporting Use Cases
Solution Integrator (1)Service Component Builder (1)Service Implementer (1)Data Modeler (1)Network Administrator (1)
Information Modeler(2)System Architect (2)Service Architect (2)
{
Solution Implementation Use Case
{Roles
Supporting Use Cases
Service Delivery Manager (1)Subscriber (1)System Manager (1)Service Operator (1)Network Operator (1)
Data Modeler (2)
{
Solution Deployment/Operation Use Case
{Roles
Supporting Use CasesDeployment
CorporateKnowledge
Base
NGOSSKnowledge
Base
Shared
Iterate withSANRR
Iterate withSANRR Iterate with
SANRR
Iterate withSANRR
Iterate withSANRR
Iterate withSANRRIterate with
SANRR
Iterate withSANRR
Notes: - Bold Italic Roles indicate accountability- Following numbers (n) indicate Primary, Secondary or Tertiary Actors- Interactions between Accountability Roles for each View follow indicated doubled headed black arrows- Use Cases that span one or more Views are constructed as a coordinating Use Case that orchestrates the use of non-spanning Use Cases
All Rights ReservedPage No. - 42Copyright 2004. All Rights ReservedPage 42 Training Plus Copyright 2004. All Rights ReservedPage 42 Training Plus Copyright 2004. All Rights ReservedPage 42 Training Plus
Use Cases in the NGOSS LifecycleSystemBusiness
ImplementationDeployment
All Rights ReservedPage No. - 43Copyright 2004. All Rights ReservedPage 43 Training Plus Copyright 2004. All Rights ReservedPage 43 Training Plus Copyright 2004. All Rights ReservedPage 43 Training Plus
Use Cases in the NGOSS LifecycleSystemBusiness
ImplementationDeployment
NGOSS Lifecycle High Level Use Case
All Rights ReservedPage No. - 44Copyright 2004. All Rights ReservedPage 44 Training Plus Copyright 2004. All Rights ReservedPage 44 Training Plus Copyright 2004. All Rights ReservedPage 44 Training Plus
Use Cases in the NGOSS LifecycleSystemBusiness
ImplementationDeployment
Service ProviderHigh LevelUse Case
Service DeveloperHigh LevelUse Case
All Rights ReservedPage No. - 45Copyright 2004. All Rights ReservedPage 45 Training Plus Copyright 2004. All Rights ReservedPage 45 Training Plus Copyright 2004. All Rights ReservedPage 45 Training Plus
Use Cases in the NGOSS LifecycleSystemBusiness
ImplementationDeployment
Logical PlaneHigh LevelUse Case
Physical PlaneHigh LevelUse Case
All Rights ReservedPage No. - 46Copyright 2004. All Rights ReservedPage 46 Training Plus Copyright 2004. All Rights ReservedPage 46 Training Plus Copyright 2004. All Rights ReservedPage 46 Training Plus
Use Cases in the NGOSS LifecycleSystemBusiness
ImplementationDeployment QuadrantHigh Level Use Cases
All Rights ReservedPage No. - 47Copyright 2004. All Rights ReservedPage 47 Training Plus Copyright 2004. All Rights ReservedPage 47 Training Plus Copyright 2004. All Rights ReservedPage 47 Training Plus
Use Cases in the NGOSS LifecycleSystemBusiness
ImplementationDeployment QuadrantSub Use Cases
All Rights ReservedPage No. - 48Copyright 2004. All Rights ReservedPage 48 Training Plus Copyright 2004. All Rights ReservedPage 48 Training Plus Copyright 2004. All Rights ReservedPage 48 Training Plus
NGOSS LifecycleBusiness System
Deployment Implementation
BusinessScope, Goals,
& Mission
BusinessDefinitionProcess
TailoredBusiness
Processes
TailoredBus. Policies
TailoredBusiness View
Info Model
BusinessContracts
SystemDefinitionProcess
SystemProcesses
Policy Model
Info Model
SystemContracts
Company DesignStandards& Procs.
Run-TimeProcess
ContractInstances
ProcessInstances
PolicyInstances
DataInstances Deployment
Environment
ImplementationProcess
ImplementationEnvironment
ContractImpls.
PolicySpecs
Processes
Data Model
CorporateKnowledge
Base
NGOSSKnowledge
BaseShared
All Rights ReservedPage No. - 49Copyright 2004. All Rights ReservedPage 49 Training Plus Copyright 2004. All Rights ReservedPage 49 Training Plus Copyright 2004. All Rights ReservedPage 49 Training Plus
Conclusions
Artifacts are used to capture and communicate the desired interactions between entitiesOrganized using the Lifecycle Views to provide for Better OSS Knowledge Management & ReuseBetter OSS Knowledge Management improves Information Communication, leading to reduced Integration Tax and increased Interoperability and Automation.
All Rights ReservedPage No. - 50Copyright 2004. All Rights ReservedPage 50 Training Plus Copyright 2004. All Rights ReservedPage 50 Training Plus Copyright 2004. All Rights ReservedPage 50 Training Plus
TeleManagement World Training PlusLong Beach, USA - 11th October 2004
NGOSS eTOM Overview
Nick Webb, QinetiQSenior Engineer – Management Systems and Requirements
NGOSS eTOM Team
All Rights ReservedPage No. - 51Copyright 2004. All Rights ReservedPage 51 Training Plus Copyright 2004. All Rights ReservedPage 51 Training Plus Copyright 2004. All Rights ReservedPage 51 Training Plus
AgendaNGOSS Background & Basics
NGOSS Lifecycle and Methodology
NGOSS eTOM: Business Processes
NGOSS SID: Shared Information Data Model
NGOSS TNA: Technology Neutral Architecture
NGOSS: Documents & Specifications
All Rights ReservedPage No. - 52Copyright 2004. All Rights ReservedPage 52 Training Plus Copyright 2004. All Rights ReservedPage 52 Training Plus Copyright 2004. All Rights ReservedPage 52 Training Plus
eTOM: Linkage to NGOSS
The eTOM provides the process oriented view on the Business ConcernsThe eTOM process and activity descriptions are used to create business flows that diagram what needs to happen when and by whomBusiness View Use Cases drive the Business ContractsFeedback from the NGOSS development cycle is used to validate the eTOM best practices.
PhysicalView
Service DevelopersView
Service Providers View
ImplementationDeployment
Business System
DeploymentCapabilities, Constraints & Context
ImplementationCapabilities, Constraints
& Context
Business Capabilities, Constraints & Context
System Capabilities,Constraints &
ContextCorporateKnowledge
Base
NGOSSKnowledge
BaseShared
LogicalView
All Rights ReservedPage No. - 53Copyright 2004. All Rights ReservedPage 53 Training Plus Copyright 2004. All Rights ReservedPage 53 Training Plus Copyright 2004. All Rights ReservedPage 53 Training Plus
Element Management
Network Management
BusinessManagement
ServiceManagement
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
TOM horizontals correspond to TMN Layers
Operations
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
(Application, Computing and Network)
Customer
TOM processes are captured in “FAB” area of eTOM Operations
eTOM maps the NGOSS Business View Physical
View
Service DevelopersView
Service Providers View
ImplementationDeployment
Business System
Deployment Capabilities, Constraints & Context
Implementation Capabilities, Constraints & Context
BusinessCapabilities, Constraints & Context
SystemCapabilities,
Constraints & ContextCorporate
KnowledgeBase
NGOSSKnowledge
BaseShared
LogicalView
All Rights ReservedPage No. - 54Copyright 2004. All Rights ReservedPage 54 Training Plus Copyright 2004. All Rights ReservedPage 54 Training Plus Copyright 2004. All Rights ReservedPage 54 Training Plus
eTOM - Business Map
The eTOM is an organized collection of industry best practices
Business View on Concerns expressed as Process and Activity descriptions and sample Flows
Used for Identifying and Cataloging:Domain BoundariesBusiness Processes and FlowsUse Cases
Actors, Entities, ModelsContracts.
All Rights ReservedPage No. - 55Copyright 2004. All Rights ReservedPage 55 Training Plus Copyright 2004. All Rights ReservedPage 55 Training Plus Copyright 2004. All Rights ReservedPage 55 Training Plus
eTOM: the Big Picture
Enterprise Management
Strategy, Infrastructure & Product Operations
Customer
Fulfillment Assurance BillingProductLifecycleManagement
InfrastructureLifecycleManagement
OperationsSupport andReadiness
Customer Relationship Management
Service Management & Operations
Resource Management & Operations
Supplier/Partner Relationship Management
Strategic &EnterprisePlanning
Financial &AssetManagement
Enterprise Quality Mgt.,Process & IT Planning& Architecture
Stakeholder & ExternalRelations Management
Strategy &Commit
Marketing & Offer Management
Service Development & Management
Resource Development and Management
Supply Chain Development and Management
Brand Management,Market Research &Advertising
Human ResourcesManagement
(Application, Computing and Network)
Disaster Recovery,Security & FraudManagement
Research &Development,TechnologyAcquisition
(Application, Computing and Network)
Cop
yrig
ht 2
004.
All
Rig
hts
Res
erve
d
All Rights ReservedPage No. - 56Copyright 2004. All Rights ReservedPage 56 Training Plus Copyright 2004. All Rights ReservedPage 56 Training Plus Copyright 2004. All Rights ReservedPage 56 Training Plus
eTOM - The Level 2 ProcessesLevel 1 Vertical Grouping
Level 1 Horizontal Grouping
Customer
Enterprise Management
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
Service Development & Management
Resource Development & Management
Supply Chain Development & Management
Marketing & Offer 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
Operations
Fulfillment Assurance BillingOperations Support & ReadinessCustomer RelationshipManagement
Service Management & Operations
Resource Management & Operations
Supplier/Partner Relationship Management
ServiceConfiguration & Activation
ServiceProblem
Management
Service QualityManagement
Service & Specific Instance
Rating
SM&OSupport & Readiness
Supplier/Partner Interface Management
S/P Buying
S/P Purchase Order
Management
S/P Problem Reporting &Management
S/P PerformanceManagement
S/P Settlements & Billing
ManagementS/PRM
Support &Readiness
ResourceProvisioning
ResourceTrouble
Management
Retention & Loyalty
Customer Interface Management
Billing & Collections
Management
CustomerQoS / SLA
Management
ProblemHandling
Selling
Order Handling
MarketingFulfillmentResponse
CRMSupport & Readiness
Resource Data Collection & Processing
ResourcePerformanceManagementRM&O
Support & Readiness
All Rights ReservedPage No. - 57Copyright 2004. All Rights ReservedPage 57 Training Plus Copyright 2004. All Rights ReservedPage 57 Training Plus Copyright 2004. All Rights ReservedPage 57 Training Plus
Process DecompositionsOrder Handling
CreditAuthorization
Order Issuance Order Trackingand Status
PreorderFeasibilityDetermination
Order Completion
Receive Pre-OrderFeasibility Request
Order PlanDevelopment
Order Creation Confirm OrderCompletion withCustomer
Report unmetcommitments orcapabilities
Status Report
CustomerJeopardyNotification
Committed DateRe-negotiatio w/Customer
Validate info forAssurance andBilling
CustomerSatisfactionValidation
Confirm CustomerValue delivery
Billing SatisfactionValidation
Test solution anddemonstrate tocust
Order Cancellation
Order Amendment
Obtain AppropriateApprovals
Advise andNegotiateAcceptable Terms
Order RequestValidation
Issue Pre-OrderFeasibility Study
CreditInvestigationDetermination
CreditInvestigation
StatusEstablishment andManagement
Manage Customerchanges toAgreement Con
Train the customer
Followup onoptimal CustomerUtilisation
TEAM DRAFTLevel 2
Level 3
Level 4
All Rights ReservedPage No. - 58Copyright 2004. All Rights ReservedPage 58 Training Plus Copyright 2004. All Rights ReservedPage 58 Training Plus Copyright 2004. All Rights ReservedPage 58 Training Plus
Example Ordering (Fulfillment) Flow
Customer Relationship Management
Service Management & Operations
Resource Management & Operations
Supplier/Partner Relationship Management
Customer Interface Management
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
All Rights ReservedPage No. - 59Copyright 2004. All Rights ReservedPage 59 Training Plus Copyright 2004. All Rights ReservedPage 59 Training Plus Copyright 2004. All Rights ReservedPage 59 Training Plus
Where Next?
eTOM continues to prioritize business scenarios to guide the ongoing workLower-level process decompositions are developed for the selected process areasProcess flows to map the processes into the business scenarios are definedeTOM is driving the process-oriented Business View in NGOSS and linked with other elements, e.g. the SID.
All Rights ReservedPage No. - 60Copyright 2004. All Rights ReservedPage 60 Training Plus Copyright 2004. All Rights ReservedPage 60 Training Plus Copyright 2004. All Rights ReservedPage 60 Training Plus
TeleManagement World Training PlusLong Beach, USA - 11th October 2004
NGOSS SID Overview
Cliff C. Faurer, TM ForumTechnical Director – NGOSS Program
NGOSS Steering CouncilNGOSS Architecture Board
NGOSS Lifecycle and Methodology TeamNGOSS SID Team
All Rights ReservedPage No. - 61Copyright 2004. All Rights ReservedPage 61 Training Plus Copyright 2004. All Rights ReservedPage 61 Training Plus Copyright 2004. All Rights ReservedPage 61 Training Plus
AgendaNGOSS Background & Basics
NGOSS Lifecycle and Methodology
NGOSS eTOM: Business Processes
NGOSS SID: Shared Information Data Model
NGOSS TNA: Technology Neutral Architecture
NGOSS: Documents & Specifications
All Rights ReservedPage No. - 62Copyright 2004. All Rights ReservedPage 62 Training Plus Copyright 2004. All Rights ReservedPage 62 Training Plus Copyright 2004. All Rights ReservedPage 62 Training Plus
Why have an Information Model?Provides a way of visualizing informationProvides a consistent and common terminologyProvides visibility of information interactionAllows reuse of IT investment
... leading to business benefits of improvedCostQualityTimelinessAdaptabilityInteroperability!
All Rights ReservedPage No. - 63Copyright 2004. All Rights ReservedPage 63 Training Plus Copyright 2004. All Rights ReservedPage 63 Training Plus Copyright 2004. All Rights ReservedPage 63 Training Plus
What IS the SID?
Product
Customer
Resource Supplier/Partner
Common Business Entities Enterprise
Sales/Market
Service
“A Holistic De-compositional Information Model defined in UML covering each View of the NGOSS Lifecycle”
All Rights ReservedPage No. - 64Copyright 2004. All Rights ReservedPage 64 Training Plus Copyright 2004. All Rights ReservedPage 64 Training Plus Copyright 2004. All Rights ReservedPage 64 Training Plus
SID Framework – Aligned with eTOMStrategy, Infrastructure &Product
Operations
Enterprise
CustomerMarket/Sales Product
Service
Supplier/Partner
Enterprise Common Business Entities
Resource
All Rights ReservedPage No. - 65Copyright 2004. All Rights ReservedPage 65 Training Plus Copyright 2004. All Rights ReservedPage 65 Training Plus Copyright 2004. All Rights ReservedPage 65 Training Plus
Information to Answer the Six Primitive Questions
What?Where?Why?How?When?Who?
All Rights ReservedPage No. - 66Copyright 2004. All Rights ReservedPage 66 Training Plus Copyright 2004. All Rights ReservedPage 66 Training Plus Copyright 2004. All Rights ReservedPage 66 Training Plus
Contexts and Roles
How do we model something where the characteristics of interest change depending on the situation?We need to separate the intrinsic attributes from the contextual attributesSID Role Pattern.
All Rights ReservedPage No. - 67Copyright 2004. All Rights ReservedPage 67 Training Plus Copyright 2004. All Rights ReservedPage 67 Training Plus Copyright 2004. All Rights ReservedPage 67 Training Plus
States and Lifecycle
How do we model the invariant and varying characteristics of a concept or thing?
Put the invariants in a SpecificationAnd the varying into the Entity
Entity – Entity Specification PatternSeparate out those characteristics that need to have their changes tracked (past/present/future).
All Rights ReservedPage No. - 68Copyright 2004. All Rights ReservedPage 68 Training Plus Copyright 2004. All Rights ReservedPage 68 Training Plus Copyright 2004. All Rights ReservedPage 68 Training Plus
Relationships
The real world is a connected placeConcepts rarely exist in isolation
So -We need to model how things relate
Captured in UML as associations, aggregations and compositions.
All Rights ReservedPage No. - 69Copyright 2004. All Rights ReservedPage 69 Training Plus Copyright 2004. All Rights ReservedPage 69 Training Plus Copyright 2004. All Rights ReservedPage 69 Training Plus
Shared Information & Data Model
Product
Market / SalesMarket Strategy & Plan
Market Segment
Marketing Campaign
Competitor
Contact/Lead/Prospect
Sales Statistic Sales Channel
Product
Product Specification Product Offering
Strategic Product Portfolio Plan Product Performance
Product Usage Statistic
CustomerCustomer
Customer Interaction
Customer Order
Customer Statistic
Customer Problem
Customer SLA
ServiceService
Service Specification
Service Applications
Service Configuration
Service Performance
Service Usage
Resource
Supplier / PartnerSupplier/Partner
S/P Plan
S/P Interaction
S/P Product
S/P Order
S/P SLA
Enterprise Common BusinessParty
Location
Business Interaction
Policy Agreement
Applied Customer Billing Rate
Customer Bill
Customer Bill Collection
Customer Bill Inquiry
Service Strategy & Plan
Service Trouble Service Test
Resource
Resource Specification
Resource Topology
Resource Configuration
Resource Performance
Resource Usage
Resource Strategy & Plan
Resource Trouble Resource Test
S/P Problem
S/P Statistic
S/P Bill Inquiry
S/P Payment
S/P Performance S/P Bill
(Under Construction)
Product
Market / SalesMarket Strategy & Plan
Market Segment
Marketing Campaign
Competitor
Contact/Lead/Prospect
Sales Statistic Sales Channel
Product
Product Specification Product Offering
Strategic Product Portfolio Plan Product Performance
Product Usage Statistic
CustomerCustomer
Customer Interaction
Customer Order
Customer Statistic
Customer Problem
Customer SLA
ServiceService
Service Specification
Service Applications
Service Configuration
Service Performance
Service Usage
Resource
Supplier / PartnerSupplier/Partner
S/P Plan
S/P Interaction
S/P Product
S/P Order
S/P SLA
Enterprise Common BusinessParty
Location
Business Interaction
Policy Agreement
Applied Customer Billing Rate
Customer Bill
Customer Bill Collection
Customer Bill Inquiry
Service Strategy & Plan
Service Trouble Service Test
Resource
Resource Specification
Resource Topology
Resource Configuration
Resource Performance
Resource Usage
Resource Strategy & Plan
Resource Trouble Resource Test
S/P Problem
S/P Statistic
S/P Bill Inquiry
S/P Payment
S/P Performance S/P Bill
(Under Construction)
All Rights ReservedPage No. - 70Copyright 2004. All Rights ReservedPage 70 Training Plus Copyright 2004. All Rights ReservedPage 70 Training Plus Copyright 2004. All Rights ReservedPage 70 Training Plus
Example: Order Handling Business Use Case
OrderHandling
Customer
ReceiveOrderRequest
«include» ValidateOrderRequest
AnalyzeOrderFeasibility
ProcessOrder
AuthorizeCredit
IsssueOrder
TrackOrder
ManageJeopardy
CompleteOrder
AmendOrder
CancelOrder
«include»
«include»
«include»
«include»
«include»
«include» «include» «include»
OrderProcessing
CustomerInterface
Pre-Order Processing
InternalEngineering
NOC
Sales
SupplierPartner
«extend» «extend»
Courtesy PEA and mdapce
All Rights ReservedPage No. - 71Copyright 2004. All Rights ReservedPage 71 Training Plus Copyright 2004. All Rights ReservedPage 71 Training Plus Copyright 2004. All Rights ReservedPage 71 Training Plus
NGOSS SID – Product-Service-Resource
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
pResourceSupportsLResource
Service
All Rights ReservedPage No. - 72Copyright 2004. All Rights ReservedPage 72 Training Plus Copyright 2004. All Rights ReservedPage 72 Training Plus Copyright 2004. All Rights ReservedPage 72 Training Plus
NGOSS SID Contract Model
Business Contract Restriction
Policy Condition Time Period
OAM Business Philosophy Details
Mgmt Info Obtained Details Mgmt Method
Used Details
Business Benefits
Business Goal
Business Activity
Party Role
Business Context
Business Capabilities
Common OAM Business Concepts
Management Info
Management Method Entity
Role
Business Process
Policy Rule
Involved Party Roles
Party Role Delegates To
Business Contract
Specifies Business Contract
Provides
Requires
Has Business Goals
Relates To Business Activities
Defines Business Contract
Party Role Has Restricted Usage
Has Business Context
Has Business Capabilities
Has Business Limitations
Defines OAM Business Philosophy Used
Defines Mgmt Info ObtainedDefines Mgmt Method Used
Has Stakeholder Limitations
Implements Behavior
Governs Contract
Business Contract Composite
Has Business Contracts
Business Contract Atomic
EntityBusiness Contract Spec
Business Obligations
Business Contract Limitations
All Rights ReservedPage No. - 73Copyright 2004. All Rights ReservedPage 73 Training Plus Copyright 2004. All Rights ReservedPage 73 Training Plus Copyright 2004. All Rights ReservedPage 73 Training Plus
Example: Partial Contract Hierarchy for Upsell
Customer Contract
Product Contract
PhysicalResourceContract
CustomerFacingServiceContract
CustomerFacingServiceContract
ResourceFacingServiceContract
ResourceFacingServiceContract
ResourceFacingServiceContract
ResourceFacingServiceContract
ResourceFacingServiceContract
ResourceFacingServiceContract
View of the data from Market, Sales and Order points-of-view
Translated into ProductSpecs, ProductOfferings, and ProductsMay require new
device to use enhanced features Gold Service
CustomerFacingServiceContract
VoIP VPN
Route Forwarding
Device OS
Traffic Conditioning
Import Policies
Export Policies
Traffic Identification
All Rights ReservedPage No. - 74Copyright 2004. All Rights ReservedPage 74 Training Plus Copyright 2004. All Rights ReservedPage 74 Training Plus Copyright 2004. All Rights ReservedPage 74 Training Plus
SID 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, Telstra, Bell Canada)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)ITU Study Group 4.
All Rights ReservedPage No. - 75Copyright 2004. All Rights ReservedPage 75 Training Plus Copyright 2004. All Rights ReservedPage 75 Training Plus Copyright 2004. All Rights ReservedPage 75 Training Plus
TeleManagement World Training PlusLong Beach, USA - 11th October 2004
NGOSS Architecture OverviewNGOSS Documents and Specifications
Giuseppe Covino, Telecom Italia LabsNGOSS Architecture Board
NGOSS Contract Working Group
All Rights ReservedPage No. - 76Copyright 2004. All Rights ReservedPage 76 Training Plus Copyright 2004. All Rights ReservedPage 76 Training Plus Copyright 2004. All Rights ReservedPage 76 Training Plus
AgendaNGOSS Background & Basics
NGOSS Lifecycle and Methodology
NGOSS eTOM: Business Processes
NGOSS SID: Shared Information Data Model
NGOSS TNA: Technology Neutral Architecture
NGOSS: Documents & Specifications
All Rights ReservedPage No. - 77Copyright 2004. All Rights ReservedPage 77 Training Plus Copyright 2004. All Rights ReservedPage 77 Training Plus Copyright 2004. All Rights ReservedPage 77 Training Plus
NGOSS Architecture
Logical Architecture:Business View Architecture (Requirements and Specification)System View Architecture (Technology Neutral Design)
Physical Architecture:Implementation View Architecture (Technology Specific)Deployment View Architecture (Management and Operations).
All Rights ReservedPage No. - 78Copyright 2004. All Rights ReservedPage 78 Training Plus Copyright 2004. All Rights ReservedPage 78 Training Plus Copyright 2004. All Rights ReservedPage 78 Training Plus
NGOSS TNA Concepts
All (externally visible) Interfaces are defined through ContractsAll Contracts are registered and locatable via NGOSS framework servicesAn NGOSS implementation will be over a (logical) common communications infrastructure.
All Rights ReservedPage No. - 79Copyright 2004. All Rights ReservedPage 79 Training Plus Copyright 2004. All Rights ReservedPage 79 Training Plus Copyright 2004. All Rights ReservedPage 79 Training Plus
NGOSS Architecture Concepts
ContractInstanceContractServiceComponent
Contains 1or more
Contains 2or more
Instantiated by2 or more
All Rights ReservedPage No. - 80Copyright 2004. All Rights ReservedPage 80 Training Plus Copyright 2004. All Rights ReservedPage 80 Training Plus Copyright 2004. All Rights ReservedPage 80 Training Plus
NGOSS Architecture Component Model
A Component is:An implementation of functionalitySubject to 3rd party compositionUnit of manageabilityContractually specified
i.e. containers for contract instances
For high availability environments …A component instance may not have persistent state.
All Rights ReservedPage No. - 81Copyright 2004. All Rights ReservedPage 81 Training Plus Copyright 2004. All Rights ReservedPage 81 Training Plus Copyright 2004. All Rights ReservedPage 81 Training Plus
NGOSS Architecture Service Concepts
A Service is:A collection of functional capability described by one or more contractsUnit of manageabilityCapability described as contractually specified interactionsAccessible through the contract instances.
All Rights ReservedPage No. - 82Copyright 2004. All Rights ReservedPage 82 Training Plus Copyright 2004. All Rights ReservedPage 82 Training Plus Copyright 2004. All Rights ReservedPage 82 Training Plus
NGOSS Architecture ContractA Contract is:
Description of functionality to be providedMetadata used to describe the interfaceMetadata 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
Behavior of the functionality, some of the behavior that may be specified include
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)Post-conditions, which define the state that the system is left in for each termination that can be returned when an operation is invoked.
All Rights ReservedPage No. - 83Copyright 2004. All Rights ReservedPage 83 Training Plus Copyright 2004. All Rights ReservedPage 83 Training Plus Copyright 2004. All Rights ReservedPage 83 Training Plus
Decomposition 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
All Rights ReservedPage No. - 84Copyright 2004. All Rights ReservedPage 84 Training Plus Copyright 2004. All Rights ReservedPage 84 Training Plus Copyright 2004. All Rights ReservedPage 84 Training Plus
‘Morph’ the Contract1. Define the Business
(Leadership Team,Business Process Engineers)
2. Architect the Business(Enterprise IT Architects)
BusinessContract
1
4. Execute the Business(Operations)
ImplementContract
SystemContract
Deploymnt.Contract
BusinessContract
1
4
2
3
CorporateKnowledge
Base
NGOSSKnowledge
BaseShared
SystemContract
BusinessContract
1 2
ImplementContract
SystemContract
BusinessContract
1 2
3
3. Implement the Business(Development Org.)
All Rights ReservedPage No. - 85Copyright 2004. All Rights ReservedPage 85 Training Plus Copyright 2004. All Rights ReservedPage 85 Training Plus Copyright 2004. All Rights ReservedPage 85 Training Plus
Relationship of NGOSS Artifacts
NGOSSUse Cases
Currently Conceptual - NGOSS Knowledge Base processes, extension methodologies for eTOM, SID and NGOSS Contract exploitation.Processes Used
NGOSS Design and lifecycle policies tbd (draft available in J Strassner Policy base Network Management Solutions for the Next Generation)Organisation’s internal policies
Policies Used
To capture the business goals and needs in a form that can be realized with high fidelity by Systems Implementer’s in an acceptable deployment.This methodology uses a Validation Verification AND Testing (VV&T) concept over the full NGOSS Lifecycle.
Stakeholder Goals
To capture and transform a user organisation’s business goal - based on possible existing systems and organization constraints - into a set of artefacts that express the Business Requirement in a complete form that meets the pre conditions for the Systems Phase of the NGOSS Lifecycle. Some of these artifacts may be recorded in the TMF OR the Organisation’s Own Knowledge Base
Primary Goals
TMF Members, suppliers, partners, industry analysts Tertiary Actor(s)
Stakeholders for System, Implementation and Operations TMF Team members
Secondary Actor(s)
Business Analysts and programme managers in user organizationsPrimary Actor(s)
Anyone that is involved with establishing and operating the Business Phase of the NGOSS LifecycleAudience
Very High SummaryLevel
Enterprise: The activities, constraints and artifacts (e.g. business plan) needed to perform the NGOSS Business LifecycleScope
Business Phase – NGOSS LifecycleUse Case Title
CommentaryName of Field
Currently Conceptual - NGOSS Knowledge Base processes, extension methodologies for eTOM, SID and NGOSS Contract exploitation.Processes Used
NGOSS Design and lifecycle policies tbd (draft available in J Strassner Policy base Network Management Solutions for the Next Generation)Organisation’s internal policies
Policies Used
To capture the business goals and needs in a form that can be realized with high fidelity by Systems Implementer’s in an acceptable deployment.This methodology uses a Validation Verification AND Testing (VV&T) concept over the full NGOSS Lifecycle.
Stakeholder Goals
To capture and transform a user organisation’s business goal - based on possible existing systems and organization constraints - into a set of artefacts that express the Business Requirement in a complete form that meets the pre conditions for the Systems Phase of the NGOSS Lifecycle. Some of these artifacts may be recorded in the TMF OR the Organisation’s Own Knowledge Base
Primary Goals
TMF Members, suppliers, partners, industry analysts Tertiary Actor(s)
Stakeholders for System, Implementation and Operations TMF Team members
Secondary Actor(s)
Business Analysts and programme managers in user organizationsPrimary Actor(s)
Anyone that is involved with establishing and operating the Business Phase of the NGOSS LifecycleAudience
Very High SummaryLevel
Enterprise: The activities, constraints and artifacts (e.g. business plan) needed to perform the NGOSS Business LifecycleScope
Business Phase – NGOSS LifecycleUse Case Title
CommentaryName of Field
NGOSS ProcessDescriptions
Operations
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
(Application, Computing and Network)
Customer
NGOSS Policies
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
NGOSS Activities
Order Handling
CreditAuthorization
Order Issuance Order Trackingand Status
PreorderFeasibilityDetermination
Order Completion
Receive Pre-OrderFeas ibility Request
Order PlanDevelopment
Order Creation Confirm OrderCompletion withCustomer
Report unmetcommitments orcapabilities
Status Report
CustomerJeopardyNotification
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 andNegotiateAcceptable Terms
Order RequestValidation
Issue Pre-OrderFeasibility Study
CreditInvestigationDetermination
CreditInvestigation
StatusEstablishment andManagement
Manage Customerchanges toAgreement Con
Train the customer
Followup onoptimal CustomerUtilisation
© TeleManagement Forum eTOM April 200 1
TEAM DRAFT
NGOSS Contracts
ImplementContract
SystemContract
DeploymentContract
BusinessContract
1 2
34
ImplementContract
SystemContract
DeploymentContract
BusinessContract
1 2
34
contains
references
references
adjusts
selects
controls
references
interfacesdefined by
referencesdefines
references
All Rights ReservedPage No. - 86Copyright 2004. All Rights ReservedPage 86 Training Plus Copyright 2004. All Rights ReservedPage 86 Training Plus Copyright 2004. All Rights ReservedPage 86 Training Plus
NGOSS ArchitectureShared Information Model
SecurityPolicy
Business Process
OSS Applications
OSS Framework Services
Basic Framework Services
Basic Mechanisms
All Rights ReservedPage No. - 87Copyright 2004. All Rights ReservedPage 87 Training Plus Copyright 2004. All Rights ReservedPage 87 Training Plus Copyright 2004. All Rights ReservedPage 87 Training Plus
Distribution and Transparency Services Model
Other NGOSSSupporting Services
(e.g. Logging, Transaction)Registration Services
UsersSpecifiers,
Designers/Devel.,& Admin.
Federated Foreign
Repository
Contract InstanceLocation Services
DerivedRepository
NamingServices
Repository
All Rights ReservedPage No. - 88Copyright 2004. All Rights ReservedPage 88 Training Plus Copyright 2004. All Rights ReservedPage 88 Training Plus Copyright 2004. All Rights ReservedPage 88 Training Plus
Contract Instance Location ServicesA Framework Service that facilitates decoupling the “hard binding” of clients and servers by providing a dynamic “matchmaking” service during the runtime phase of the software lifecycleTo facilitate support for:
Contract Instance relocation (Contract Instance moved to new platform)Contract Instance mobility (Platform moves)Addition/deletion of duplicate Instances of Contract (for added reliability or performance)Addition of new or value-added Contract Instance
In a manner that is transparent to clients of the Contract Instances.
All Rights ReservedPage No. - 89Copyright 2004. All Rights ReservedPage 89 Training Plus Copyright 2004. All Rights ReservedPage 89 Training Plus Copyright 2004. All Rights ReservedPage 89 Training Plus
Types of Contract Instance Location Services
Pull: Contract Instance Location whereby requests for service from potential clients are matched with previously registered Contract Instance offers. Binding information is returned immediately upon matchPush: Contract Instance Location whereby requests for service from potential clients are accepted and queued. Binding information about the Contract Instance provider is returned to the potential client when the potential provider becomes availableAuctioning: Contract Instance Location whereby the potential client asks for selection of a desired service based on a auction between potential providers. Binding information is returned at either when client criteria is met or auction time expires.
All Rights ReservedPage No. - 90Copyright 2004. All Rights ReservedPage 90 Training Plus Copyright 2004. All Rights ReservedPage 90 Training Plus Copyright 2004. All Rights ReservedPage 90 Training Plus
NGOSS Federation Model
Service Level Federation: Pair-wise between two Services
NOT encouraged! Issues with scaling, performance (feature interaction problem!), and “private data model agreements”
Repository Level Federation:Recommended MOST STRONGLY!!Requires use of common information model (or those for which well defined mappings exist)Transparent to all other service (Framework or Applications).
All Rights ReservedPage No. - 91Copyright 2004. All Rights ReservedPage 91 Training Plus Copyright 2004. All Rights ReservedPage 91 Training Plus Copyright 2004. All Rights ReservedPage 91 Training Plus
Highlights of NGOSS Federated and Derived Repository Models
Derived Repositories:Cache Repository defined to add performanceUnion Repository defined to facilitate manageability, usability and scalability at enterprise level
Federated Repositories:Defined to add scalability and inter-working between Domains and EnterprisesFederation at peer level only (i.e. Cache to Cache, Union to Union, or Master to Master)Defined at a number of levels:
Intra-domain (Cache to Cache)Inter-domain, Intra-Enterprise (Cache to Cache or Master to Master)Inter-Enterprise (Cache to Cache, Master to Master or Union to Union).
All Rights ReservedPage No. - 92Copyright 2004. All Rights ReservedPage 92 Training Plus Copyright 2004. All Rights ReservedPage 92 Training Plus Copyright 2004. All Rights ReservedPage 92 Training Plus
NGOSS Federated Repository Model
Enterprise a
Domain2
BB
CCDomain
3
Enterprise b
Domain5
Domain4
D.2D.2D.1D.1
EE
UDEUDE
DDF(B,C)
UF(ABC, DE)
F(C,D)
f(C.1,D.1)Domain
1
AA
A.1A.1 A.2A.2 C.1C.1f(A.2,C.1)
UABCUABC
UABUAB
All Rights ReservedPage No. - 93Copyright 2004. All Rights ReservedPage 93 Training Plus Copyright 2004. All Rights ReservedPage 93 Training Plus Copyright 2004. All Rights ReservedPage 93 Training Plus
AgendaNGOSS Background & Basics
NGOSS Lifecycle and Methodology
NGOSS eTOM: Business Processes
NGOSS SID: Shared Information Data Model
NGOSS TNA: Technology Neutral Architecture
NGOSS: Documents & Specifications
All Rights ReservedPage No. - 94Copyright 2004. All Rights ReservedPage 94 Training Plus Copyright 2004. All Rights ReservedPage 94 Training Plus Copyright 2004. All Rights ReservedPage 94 Training Plus
Applications of NGOSSService Providers
Assess Business Process & System CapabilitiesRFP
System IntegratorsAssess Market Opportunities
Independent Software VendorsFramework for Contract/Component Development
Network Equipment ProvidersFramework for Contract-based Device Management Interfaces
Other Consortia/Standards BodiesFast-tracked as both foundation and extensions to number of major standards bodies (both telecommunications and external)
TM ForumBusiness/System Analysis & Design (WSMT, …)Experimentation & Co-operative Development (Catalyst Projects).
All Rights ReservedPage No. - 95Copyright 2004. All Rights ReservedPage 95 Training Plus Copyright 2004. All Rights ReservedPage 95 Training Plus Copyright 2004. All Rights ReservedPage 95 Training Plus
NGOSS Documentation RoadmapNGOSS Base Set
TMF 050 – Compliance SuiteTMF053 – Technology Neutral ArchitectureGB921 – eTOMGB922 – SID Business ViewGB926 – SID System ViewGB927 – Lifecycle and Methodology Process Desc. Suite
GB921B – eTOM B2B IntegrationGB921C – Business Operations MapGB921D – Process Decomposition. & DescriptionGB921F – Process Flow ExamplesGB921L – Using eTOM to model ITILGB921S – SIP Level 3 Decomposition
& Description
Info. Modeling Suite
TMF050A – Testing Rules
Compliance Suite
TNA SuiteTMF053B – Contract SpecificationTMF053C – Behavior and Control TMF053D – MetaModelTMF053F – Distribution and Framework Services.TMF053S – Security Principles
GB922 0 – SID PrimerGB922 1A – Business Entity Defs. - AgreementGB922 1BI – Bus. Entity Defs. – Business InteractionGB922 1BT – Bus. Entity Defs. – Base TypesGB922 1J – PROJECT Bus. Entity Defs. GB922 1L – Bus. Entity Defs. – LocationGB922 1P – Bus. Entity Defs. – PartyGB922 1POL – Bus. Entity Defs. – Policy GB922 1R – Root Business Entity DefinitionsGB922 1T – Bus. Entity Defs. – Time GB922 1U – Using the SIDGB922 2 – Bus. Entity Defs. – Customer GB922 3 – Bus. Entity Defs. – ProductGB922 4S – Bus. Entity Defs. – Quality of ServiceGB922 4SO – Bus. Entity Defs. – Service GB922 5LR – Bus. Entity Defs – Logical ResourceGB922 5PR – Bus. Entity Defs.- Physical Res.
All Rights ReservedPage No. - 96Copyright 2004. All Rights ReservedPage 96 Training Plus Copyright 2004. All Rights ReservedPage 96 Training Plus Copyright 2004. All Rights ReservedPage 96 Training Plus
NGOSS Lifecycle & SFT DocumentsDocument Name Version Date New/Updated for
Release 4.5
GB927 NGOSS Lifecycle & Methodology 1.2 Sep. 2004
GB927 Annex A Use Case Template 1.0 Sep. 2004
GB927 Annex B Business & System View Contract Template
1.0 Sep. 2004
GB927 Addendum 1
Executive Summary Slides 1.0 Sep. 2004
Document Name Version Date New/Updated for Release 4.5
GB924 Service Framework Guide Book 2.0 Sep. 2004
All Rights ReservedPage No. - 97Copyright 2004. All Rights ReservedPage 97 Training Plus Copyright 2004. All Rights ReservedPage 97 Training Plus Copyright 2004. All Rights ReservedPage 97 Training Plus
NGOSS eTOM DocumentsDocument Name Version Date New/Updated for
Release 4.5
GB921 eTOM Main Document 4.5 Sep. 2004
GB921B eTOM – B2B Integration 4.0 Feb. 2004
GB921C Public B2B Operations Map Application Note
4.0 Feb. 2004
GB921D Process Decompositions and Descriptions
4.5 Sep. 2004
GB921F Process Flow Examples 4.5 Sep. 2004
GB921L eTOM – ITIL Application Note 4.0 Feb. 2004
GB921P eTOM Primer 4.5 Sep. 2004
GB921T eTOM – M.3400 Mapping App Note 4.5 Sep. 2004
All Rights ReservedPage No. - 98Copyright 2004. All Rights ReservedPage 98 Training Plus Copyright 2004. All Rights ReservedPage 98 Training Plus Copyright 2004. All Rights ReservedPage 98 Training Plus
NGOSS SID DocumentsDocument Name Version Date New/Updated for
Release 4.5
GB922 SID Business View: Concepts and Principles
3.5 Sep. 2004
GB922 - 0 Primer for the SID Business View 1.0 Feb. 2004
GB922 – 1A SID Agreement 3.0 July 2003
GB922 – 1BI SID Business Interaction 3.0 July 2003
GB922 – 1BT SID Business Entity Base Types 3.0 July 2003
GB922 – 1C SID Business Contract 1.0 Sep. 2004
GB922 – 1J SID Project 1.0 July 2003
GB922 – 1L SID Location 3.0 July 2003
GB922 – 1P SID Party 3.0 July 2003
All Rights ReservedPage No. - 99Copyright 2004. All Rights ReservedPage 99 Training Plus Copyright 2004. All Rights ReservedPage 99 Training Plus Copyright 2004. All Rights ReservedPage 99 Training Plus
NGOSS SID Documents (contd.)Document Name Version Date New/Updated for
Release 4.5
GB922 – 1POL SID Policy 1.0 July 2003
GB922 – 1R SID Root Business Entities 1.3 Sep. 2004
GB922 – 1T SID Time Related Entities 1.0 July 2003
GB922 – 1U Using the SID (UML Models) 1.0 Feb. 2004
GB922 – 2 SID Customer 3.0 July 2003
GB922 – 3 SID Product 3.0 July 2003
GB922 – 4S-O SID Service Overview 2.0 July 2003
GB922 – 4S-QoS
SID Quality of Service 1.0 July 2003
All Rights ReservedPage No. - 100Copyright 2004. All Rights ReservedPage 100 Training Plus Copyright 2004. All Rights ReservedPage 100 Training Plus Copyright 2004. All Rights ReservedPage 100 Training Plus
NGOSS SID Documents (contd.)Document Name Version Date New/Updated for
Release 4.5
GB922 – 5LR SID Logical Resource 1.0 July 2003
GB922 – 1PR SID Physical Resource 3.0 July 2003
SID Business View Models – Rose mdl, XMI v2.0 & Web published
4.5 Sep. 2004
Document Name Version Date New/Updated for Release 4.5
GB926 SID System View: Concepts and Principles
1.0 Feb. 2004
All Rights ReservedPage No. - 101Copyright 2004. All Rights ReservedPage 101 Training Plus Copyright 2004. All Rights ReservedPage 101 Training Plus Copyright 2004. All Rights ReservedPage 101 Training Plus
NGOSS Architecture and Compliance DocumentsDocument Name Version Date New/Updated for
Release 4.5
TMF053 Technology Neutral Architecture 4.0 Feb. 2004
TMF053B TNA: Business and System View Contracts
4.0 Feb. 2004
TMF053C TNA: Behavior and Control Services 1.0 Feb. 2003
TMF053D TNA: NGOSS MetaModel 1.0 Feb. 2003
TMF053F TNA: Distribution Transparency Framework Services
1.0 Feb. 2004
TMF053S TNA: Security Addendum 1.0 Feb. 2004
TMF050 NGOSS Compliance Testing Strategy Technical Specification
3.3 Feb. 2004
TMF050A NGOSS Compliance Testing Information Model & Testing Rules
3.1 Feb. 2004
All Rights ReservedPage No. - 102Copyright 2004. All Rights ReservedPage 102 Training Plus Copyright 2004. All Rights ReservedPage 102 Training Plus Copyright 2004. All Rights ReservedPage 102 Training Plus
Thanks for Listening!
Questions?
All Rights ReservedPage No. - 103Copyright 2004. All Rights ReservedPage 103 Training Plus Copyright 2004. All Rights ReservedPage 103 Training Plus Copyright 2004. All Rights ReservedPage 103 Training Plus
Contacting the TM Forum
In EuropeTel:+44-1473-288595
In North AmericaTel.: +1 973-292-1901
info@tmforum.orgE-Mail:Web: www.tmforum.orgTraining Plus: education@tmforum.org
T+ @ Long Beach (2004), Intro to NGOSS
All Rights ReservedPage No. - 104Copyright 2004. All Rights ReservedPage 104 Training Plus Copyright 2004. All Rights ReservedPage 104 Training Plus Copyright 2004. All Rights ReservedPage 104 Training Plus
Next Steps
Training Plus at TeleManagement World, Nice, France, 16-19 May, 2005:
http://www.tmforum.org/browse.asp?catID=2194
TeleManagement Regional Summit, Bangalore, India, 5-6 December, 2004:
http://www.tmforum.org/browse.asp?catID=1118&linkID=29688
TM Forum “We Come to You” courses: http://www.tmforum.org/browse.asp?catID=1565
TM Forum Webinar series:http://www.tmforum.org/browse.asp?catID=2065
All About NGOSS: http://www.tmforum.org/browse.asp?catID=1639
top related