Ngoss

Problem i mogue rjeenje
NGOSS NGOSS
ne postoji takav napredak u tehnikama razvoja programske podrke kao to se vidi napredak u razvoju mrea (NGN) apetit klijenata za novim, sofisticiranim uslugama raste konkurencija prisiljava ICSPs da:
svoje sisteme i procese projektiraju u skladu s potrebama klijenata
TMF NGOSS program
minimiziraju vrijeme potrebno za uvoenje nove usluge
do sada ICSPs OSS/BSS sisteme izgrauju vlastitim snagama po principu silosa (upravljaki otoci); teko ih je povezivati unutar tvrtke, a praktiki nemogue sa sistemima drugih ICSPs; suvremene usluge upravo zahtijevaju intenzivnu interakciju izmeu niza ICSPs. TeleManagement Forum nudi rjeenje u New Generation Operations Systems and Software, NGOSS otvorenom standardu koji prua podrku i smjernice za:
analiziranje i modeliranje poslovnih procesa ICSPs razvoj NGOSS usklaenih aplikacija nabavku NGOSS komponenata na otvorenom tritu
2/156
Sadraj
NGOSS
to je TeleManagement Forum?
NGOSS
NGOSS program
eTOM SID TNA arhitektura NGOSS Lifecycle & Methodology OSS/J inicijativa
www.tmforum.org udruga koja krajem 2007. godine broji 600 lanova tvrtke iz IC industrije (ICSPs, mreni operatori, proizvoai programske podrke i mrene opreme, sistem integratori) vizija Foruma koji je osnovan 1988. bila je postizanje interoperabilnosti OSS/BSS proizvoda danas je Forum u sklopu NGOSS Programa (New Generation Operations Systems and Software Program) usmjeren prema definiranju radnog okvira za modeliranje telekom. poslovnih procesa i razvoj otvorenih i automatiziranih OSS/BSS sistema
3/156
4/156
Motivacija za NGOSS
NGOSS
Trend - broj poslovnih subjekata u lancu se poveava

NGOSS
Rastui izazovi upravljanja i operativnog voenja:

zahtjevi trita za suvremenim uslugama nakon ideje, usluga se mora razviti i ponuditi tritu u najkraem moguem roku usluge koje su superiorne na tritu esto su sloene i oslanjaju se na niz resursa u vlasnitvu razliitih poslovnih subjekata mogunost klijenta da upravlja postavkama usluge preko Web suelja proaktivno naplaivanje u realnom vremenu temeljeno na sadraju i/ili lokaciji nuno je garantirati kvalitetu usluge koja se moe realizirati na mreama razliitih tehnologija i u vlasnitvu razliitih pruatelja i operatera OSS sistemi moraju se moi prilagoavati brzo kako bi pratili potrebe nestalnih poslovnih procesa trend - broj poslovnih subjekata u dohodovnom lancu se poveava
Fragmentiranje u dohodovnom lancu (fragmentiranje trita) glavni je problem u racionaliziranju infrastrukture. to ima vie poslovnih subjekata u lancu, novi pristup razvoju OSS sistema (NGOSS) postaje vaniji.
Klasini pristupi razvoju OSS-a ne mogu zadovoljiti navedene zahtjeve. Razvoj je spor, integracija sloena i skupa, rizik je prevelik, implementirana rjeenja su nedovoljno efikasna.
5/156 6/156
to je NGOSS ? (Arhitekture)
NGOSS
to je NGOSS ? (ivotni ciklus i metodologija razvoja)

NGOSS
NGOSS = Architectures + Lifecycle & Methodology

Temelj NGOSS-a predstavljaju tri arhitekture kojima se propisuje ugradnja procesa, informacija i interakcija u OSS/BSS sisteme.
ivotni ciklus NGOSS sistema promatra se kroz 4 karakteristina pogleda:

Business view System view Implementation view Deployment view
Business View
System View
Deployment View
Implementation View
SID
eTOM
Metodologija razvoja NGOSS sistema:

Information Architecture Process Architecture
poluformalne upute iterative, business process centric, model-based
Interaction Architecture
TNA
perspektiva - (polu)automatsko preslikavanje specifikacija iz pogleda u pogled (MDA) implementacija predvia upotrebu tehnologija iroko prihvaenih od IT industrije te komercijalnih off-the-shelf komponenata, COTS
7/156 8/156
NGOSS Frameworks
NGOSS
NGOSS Frameworks (nastavak)

NGOSS
NGOSS radni okviri predstavljaju bazu specifikacija/znanja koje se koristi tijekom razvoja NGOSS usklaenih sistema :
Enhanced Telecom Operations Map, eTOM (Business Process Map) - skup kategoriziranih specifikacija poslovnih procesa tipinog ICSP Shared Information/Data Model, SID - opsene standardizirane i kategorizirane definicije informacija (usklaene s eTOM kategorijama procesa) Technology Neutral Architecture, TNA tehnoloki neutralna specifikacija arhitekture NGOSS sistema. Telecom Application Map, TAM referentna mapa koja sadri popis kategoriziranih NGOSS aplikacija (usklaeno s eTOM kategorijama procesa).
Upotreba NGOSS frameworks-a tijekom:

sveobuhvatnog razvoja NGOSS sistema realizacije parcijalnih projekata: npr. analiza i optimiranje poslovnih procesa, odabir NGOSS komponenata na tritu, uvoenje SID usklaenog modela u postojee OSS sisteme i dr.
Business Process Framework (Enhanced Telecom Operations Map, eTOM)
sveobuhvatni razvoj ili parcijalni projekti
Information Framework (Shared Information and Data Model, SID)
Applications Framework (Telecom Applications Map, TAM)
System Integration Framework (Technology Neutral Architecture, TNA)
9/156
10/156
NGOSS Domains
NGOSS
Architectural Concepts (rjeenja usklaena s NGOSS)

NGOSS
Rjeenja/sistemi usklaeni sa NGOSS:

temelje se na zajednikom, dijeljenom informacijskom modelu sadre suvremenu kom. infrastrukturu omoguavaju fleksibilno kontroliranje djelovanje primjenom politika omoguavaju djelovanje usmjeravano logikom procesa sadre barem servise za osiguravanje transparentnosti raspodijeljenosti NGOSS domene - temeljna podruja interesa NGOSS programa. Prema njima su definirana eTOM podruja i grupe te SID domene: 11/156 sadre NGOSS aplikacijske komponente
Namjera TMF-a je da se dovri definiranje Compliance and Conformance Criteria - niz uputa i testova kojima se omoguava provjera usklaenosti rjeenja sa NGOSS
12/156
OSS/J nudi rjeenje ...

NGOSS
NGOSS pedigr
NGOSS
OSS through Java (OSS/J) inicijativa spojila se sa TMF-om 2006. OSS/J je zajednica proizvoaa programske podrke koja se bavi razvojem specifikacija API-a ija implementacija je predviena za J2EE okolinu. Komponente (EJB) koje implementiraju OSS/J API-e + J2EE infrastruktura predstavlja NGOSS usklaeni (pod)sistem.
Bellcore (now Telcordia) OSCA & INA Architectures ANSA Project TINA-C Architecture ISO / RM-ODP ITU-T / TMN TM Forum / TOM OMG / MDA & UML DMTF / CIM, DEN EC FORM Project
13/156
14/156
NGOSS specifikacije Release 6.0

NGOSS
Napomena - (ne)preciznost NGOSS specifikacija

NGOSS
NGOSS specifikacije vezane uz arhitekture i ivotni ciklus izraene su polu-formalno (BPM, UML, OCL) i neformalno (prirodnim jezikom, tabele, dijagrami). Djelomina nepreciznost u tome - to predstavlja standard i kako ga treba koristiti - utjee na njegovo sporije prihvaanje od strane telekom. industrije. Pri TMF-u djeluju Catalysts projekti u kojima se na praktian i eksperimentalan nain testira proizvodni ciklus i otkrivaju neprecizna mjesta u NGOSS specifikacijama. U perspektivi se nedostatak planira rijeiti definiranjem niza formalnih meta-modela kojih e predstavljati temelj za razvoj alata. Alati bi korisnika trebali voditi u primjeni NGOSS metodologije uz precizno definirane artefakte (specifikacije) koji se tijekom razvoja moraju u odreenih fazama generirati. Postojanje takvih alata e developer-ima omoguiti bre upoznavanje sa standardom i njegovo bolje razumijevanje.
15/156
16/156
Tko koristi NGOSS i kako ?

NGOSS NGOSS
redizajniranje i optimiranje postojeih te osmiljavanje novih poslovnih procesa (ICSPs) traenje, ugovaranje i nabavka NGOSS komponenata na tritu (ICSPs) razvoj NGOSS aplikacija i testova za testiranje usklaenosti (SVs, ICSPs) integracija sistema (SIs, ICSPs) Temelj za kvalitetnu komunikacija izmeu ICSPs, klijenata, SVs, SIs.
17/156
18/156
Sadraj
NGOSS
to je Enhanced Telecom Operations Map (eTOM)?

NGOSS
NGOSS program
eTOM
SID TNA arhitektura NGOSS Lifecycle & Methodology OSS/J inicijativa
dio TMF-ovog NGOSS programa industrijski standard za imenovanje, opis i sistematizaciju (kategorizaciju) poslovnih procesa suvremenih ICSPs okvir za hijerarhijsku dekompoziciju procesa okvir za sintezu procesa od elemenata procesa prua smjernice za modeliranje dinamikih aspekata eTOM procesa eTOM-om se nastoji obuhvatiti cjelokupni prostor (borba protiv silosa) poslovnih aktivnosti (Strategy, Operations & Enterprise) tipinog ICSP identificiranje novih elemenata procesa i proirenje eTOM-a je stalno u tijeku eTOM specifikacije procesa su generike, neovisne o organizaciji tvrtke ICSP-a, tehnologiji i konkretnim uslugama koje ICSP prua eTOM je i ITU-T standard (M.3050). eTOM nije model poslovanja ICSP-a (koje e elemente procesa specificiranih u eTOM-u i na koji nain ICSP koristiti ovisi o poslovnoj strategiji ICSP, a ne o eTOM-u)
19/156 20/156
Od TMN preko TOM do eTOM

NGOSS
Temelji TOM-a
NGOSS
inspiracija za
TOM
Doseg TOM-a: procesi operativnog voenja (Operations)
TMN
Business Mgmt. Service Mgmt. Netw. Mgmt. Elem. Mgmt.
se proirenje u
eTOM
Da bi se osigurala integracija svih vitalnih sistema za podrku unutar Telco. tvrtke, a i prema van, bitno je uniformno tretirati sve procese relevantne za tvrtku (posebno koje dotiu klijente, dobavljae i druge ICSPs)
21/156 22/156
eTOM dokumenti
NGOSS
Pojmovi i principi - element procesa, tok procesa, podruje procesa i grupiranje procesa
NGOSS
A main document (GB921) that provides an overview of the eTOM Business Process Framework, from both Intra-Enterprise and Inter-Enterprise viewpoints, and describes the main structural elements and approach An Addendum (GB921D) describing the Service Provider enterprise processes and sub-processes in a form that is top down, customer-centric, and end-to-end focused. Process decompositions are provided for all processes from the highest conceptual view of the eTOM framework to the level of detail agreed for use by the industry. An Addendum (GB921F) describing selected process flows at several levels of view and detail that provides end-to-end insight into the application of eTOM. An Addendum (GB921B) describing the implications and impact of e-business for service providers and their business relationships, and how eTOM supports them, including a description of handling of business-to-business Interactions by eTOM. Associated with this is a separate Application Note (GB921C) describing a Business Operations Map for processes involved in business-to-business interaction An Addendum (GB921P) providing an eTOM Primer to assist new users of eTOM A separate Application Note (GB921V) that shows how eTOM can be used to model the ITIL processes (this supersedes the previous GB912L) A separate Application Note (GB921T) that shows how eTOM processes relate to the functional view provided by the ITU-T M.3400 Recommendation (this work was developed in conjunction with ITU-T within the joint Telecom Management Collaboration Focus Group) A separate Application Note (GB921N) describing selected NGOSS Contracts at the Business View that show how eTOM processes can be used as part of the NGOSS Methodology and Lifecycle. ITU-T standard M.3050 serija preporuka
23/156
Poslovne aktivnosti su u eTOM-u definirane uz pomo komponenata/podprocesa od kojih su sastavljeni sveobuhvatni, end-toend E2E poslovni procesi. Te se komponente nazivaju elementi procesa (Process Elements). Svaki se proces ili element procesa moe dekomponirati kako bi se predstavili novi detalji. Elementi procesa se povezuju kako bi sudjelovali u interakcijama ime se stvaraju tokovi procesa (Process Flows). Podruje procesa (Process Area) i grupiranje procesa (Process Grouping) u eTOM-u predstavljaju mehanizme za kategorizaciju elemenata procesa. eTOM pravi razliku izmeu grupiranja E2E procesa i grupiranja funkcijski povezanih procesa.
24/156
Hijerarhijska dekompozicija procesa

NGOSS
Hijerarhijska dekompozicija procesa (nastavak)

NGOSS
najbolji nain za strukturiranje velike koliine sadraja i detalja je strukturiranje sadraja na vei broj razina - hijerarhijska dekompozicija hijerarhijska dekompozicija procesa (Hierarchical Process Decomposition) je sistematian pristup modeliranju procesa i iznad razine koja je pogodna za modeliranje tokova procesa (dinamike) cilj dekompozicije je analiza procesa dekompozicija se moe nastaviti na onoliko (pod)razina koliko je to potrebno (ovisi o sloenosti procesa kojeg dekomponiramo) dekompozicija predstavlja statiki pogled na procese jer ne namee nikakve odnose u smislu slijeda izvoenja elemenata procesa dekompozicija omoguava modularniju implementaciju procesa (dekompozicija sugerira sistemsko rjeenje!)
proces X (npr. baratanje narudbama klijenata) dekomponiran je u tri elementa nie razine podprocesi se mogu dalje dekomponirati svaka grana ne mora nuno zavravati listom na istoj razini dekomponiranja (list je zadnji element procesa koji se dalje ne dekomponira) process element UML Use Case Diagram ili UML Activity Diagram
Level 0 Level 1 X1 X3 Level 2 X
X2
Level 3
25/156
26/156
Primjer hijerarhijske dekompozicije (eTOM)

NGOSS
eTOM principi specifikacije

NGOSS
Level 1
specifikacije obuhvaaju:
dekompoziciju procesa (statiki odnosi - struktura) smjernice za modeliranje tokova procesa (dinamiki odnosi)
Level 2
prema eTOM standardu sistematizacija poslovnih procesa poinje na vrnoj razini - razini tvrtke Level 0 (top-down princip) Level 0 identificira tri globalna podruja procesa i okolinu tvrtke (klijente, dobavljae/partenere, dioniare, zaposlenike, i sve ostale zainteresirane stranke) sljedea nia razina Level 1 sadri grupe procesa koje su ugraene u spomenuta podruja od Level 1 razine kree hijerarhijska dekompozicija elemenata procesa za svaki proces specificiraju se sljedei osnovni elementi:
identifikator procesa naziv procesa saeti i proireni opis procesa
27/156 28/156
Level 3
eTOM Konceptualna razina (Level 0)

NGOSS
Operations area (Level 1)

NGOSS
Customer
Strategy, Infrastructure & Product Operations
FAB predstavlja jezgru Operations podruja Operations Support & Readiness grupa je odvojena od FAB Operations podruje takoer obuhvaa horizontalna grupiranja procesa
Operations
Operations Support & Readiness
Market, Product and Customer
Fulfillment Assurance
Billing
Service
Customer Relationship Management
Resource
(Application, Computing and Network)
Service Management & Operations
Supplier/Partner
Resource Management & Operations

Suppliers/Partners
Supplier/Partner Relationship Management
Enterprise Management
Shareholders Employees Other Stakeholders
29/156
30/156
Service Lifecycle Process (FAB)

NGOSS
Strategy, Infrastructure & Product area (Level 1)

NGOSS
service delivery
service assurance
service usage
create/modify provision
manage
bill analyze
SIP podruje obuhvaa procese vezane uz strateko odluivanje i podrku ivotnim ciklusima infrastrukture i proizvoda. Obuhvaa grupe: Strategy & Commit Infrastructure Lifecycle Management Product Lifecycle Management
Strategy, Infrastructure & Product

Strategy & Commit Infrastructure Lifecycle Management Product Lifecycle Management
Marketing & Offer Management
Service Development & Management
modify services quickly activate and deliver services rapidly
manage SLAs ensure service availability monitor quality
bill based on usage capture usage data for billing, capacity planning, and marketing analyze subscriber behavior
31/156
SIP takoer obuhvaa horizontalna grupiranja koja odgovaraju onima u Operations podruju.
Resource Development & Management

Supply Chain Development & Management
32/156
E2E (okomito) vs funkcijsko (horizontalno) grupiranje (Level 1)

NGOSS
Enterprise Management area (Level 1)

NGOSS
7 okomitih grupa - predstavljaju E2E procese za podrku klijentima i upravljanje poslovanjem 8 horizontalnih grupa - predstavljaju funkcijski povezane procese
Brand Brand Management, Management, Market Market Research Research & Advertising & Advertising Stakeholder & Stakeholder & External External Relations Relations Management Management Disaster Disaster Recovery, Recovery, Security & Security & Fraud Fraud Management Management
Enterprise Quality Enterprise Quality Management, Management, Process & IT Process & IT Planning & Planning & Architecture Architecture
Strategic & Strategic & Enterprise Enterprise Planning Planning
Financial & Financial & Asset Asset Management Management
Human Human Resources Resources Management Management
Research & Research & Development, Development, Technology Technology Acquisition Acquisition
33/156
34/156
eTOM Level 0 & 1

NGOSS
Operations area (Level 2)

NGOSS
Customer
Operations
Fulfillment Assurance Billing
Operations Support & Readiness Customer Relationship Management
CRM Operations Support & Process Management CRM Operations Readiness
Operations
Operations Support & Readiness
Fulfillment
Assurance
Customer Interface Management
Billing
Selling Marketing Fulfillment Response Order Handling Problem Handling Customer QoS / SLA Management Billing & Collections Management
Sales & Channel Management
Retention & Loyalty

Resource Development & Management (Application, Computing and Network) Resource Management & Operations (Application, Computing and Network)
SM&O Support & Process Management Service Management & Operations Readiness Service Configuration & Activation Service Problem Management Service Quality Analysis, Action & Reporting Service & Specific Instance Rating

Supply Chain Development & Management Supplier/Partner Relationship Management
RM&O Support & Process Management Resource Management & Operations Readiness Resource Provisioning & Allocation to Service Instance
Resource Problem Management
Resource Quality Analysis, Action & Reporting Resource Data Collection, Analysis & Control
Strategic & Enterprise Planning Financial & Asset Management
Brand Management, Market Research & Advertising Human Resources Management
Stakeholder & External Relations Management Research & Development, Technology Acquisition
Disaster Recovery, Security & Fraud Management Enterprise Quality Management, Process & IT Planning & Architecture

S/PRM Operations Support & Process Management S/P Relationship Management Operations Readiness S/P Buying S/P Purchase Order Management S/P Problem Reporting & Management S/P Performance Management S/P Settlements & Billing Management
Supplier/Partner Interface Management
35/156
36/156
Elementi procesa ukljueni u vie E2E grupa

NGOSS
The SIP area (Level 2)

NGOSS
kad je potrebno osigurati konzistentnost preko nekoliko E2E procesa proces koji je ukljueni u vie grupa moe:
pruati istu funkcionalnost svim tim grupama E2E procesa, svakoj grupi moe pruati razliitu, specijaliziranu funkcionalnost.


Market Strategy & Policy Product & Offer Business Planning & Commitment Product & Offer Portfolio Capability Delivery CRM Capability Delivery Marketing Capability Delivery Product Development & Retirement Marketing Communications & Promotion Product, Marketing & Customer Performance Assessment
Primjer: Customer Interface Management proces sudjeluje u F, A i B s razliitim sadrajem i interakcijama, ali suelje mora imati usklaeni izgled (look & feel).
Product & Offer Portfolio Strategy, Policy & Planning
Sales & Channel Development

Service Strategy & Policy Service Planning & Commitment Service & Operations Capability Delivery Service Development & Retirement Service Performance Assessment

Resource & Technology Strategy & Policy Resource & Technology Plan & Commitment Resource & Operations Capability Delivery Resource Development Resource Performance Assessment

Supply Chain Strategy & Policy Supply Chain Planning & Commitment Supply Chain Capability Availability Supply Chain Development & Change Management Supply Chain Performance Assessment
37/156
38/156
Enterprise Management Hierarchy (Level 2)

Strategy & Commit
Operations
Product Lifecycle Management Operations Support & Readiness Fulfillment Assurance Billing
NGOSS
Market Market Strategy & Strategy & Policy Policy Product & Product & Offer Offer Business Business Planning & Planning & Commitment Commitment
Infrastructure Lifecycle Mgmt.
NGOSS
Customer Interface Management Customer Interface Management Selling Selling Marketing Marketing Fulfillment Fulfillment Response Response Order Order Handling Handling Problem Handling Problem Handling Customer QoS / /SLA Customer QoS SLA Management Management

Product & Product & Offer Offer Portfolio Portfolio Capability Capability Delivery Delivery CRM CRM Capability Capability Delivery Delivery Marketing Marketing Capability Capability Delivery Delivery Product Product Development Development & & Retirement Retirement Marketing Marketing CommuCommunications nications & & Promotion Promotion Product, Product, Marketing Marketing & Customer & Customer Performance Performance Assessment Assessment

CRM Operations CRM Operations Support & Process Support & Process Management Management CRM Operations CRM Operations Readiness Readiness Sales & Channel Sales & Channel Management Management
Billing & Billing & Collections Collections Management Management
Product & Offer Product & Offer Portfolio Strategy, Portfolio Strategy, Policy & Planning Policy & Planning
Sales & Sales & Channel Channel Development Development
Retention & Loyalty Retention & Loyalty

Service Service Development Development & & Retirement Retirement Service Service Performance Performance Assessment Assessment SM&O Support & Process SM&O Support & Process Management Management Service Management & Service Management & Operations Readiness Operations Readiness Service Service Configuration Configuration & Activation & Activation Service Problem Management Service Problem Management Service & Service & Specific Specific Instance Instance Rating Rating
Strategic & Enterprise Planning
Financial & Asset Management
Brand Management, Market Research & Advertising
Human Resources Management
Stakeholder & External Relations Management
Research & Development, Technology Acquisition
Enterprise Quality Management, Process & IT Planning & Architecture
Disaster Recovery, Security & Fraud Management
Service Service Strategy & Strategy & Policy Policy
Service Service Planning & Planning & Commitment Commitment
Service & Service & Operations Operations Capability Capability Delivery Delivery
Service Quality Analysis, Service Quality Analysis, Action & Reporting Action & Reporting

Resource & Resource & Technology Technology Strategy & Strategy & Policy Policy Resource & Resource & Technology Technology Plan & Plan & Commitment Commitment Resource & Resource & Operations Operations Capability Capability Delivery Delivery Resource Resource Development Development Resource Resource Performance Performance Assessment Assessment

RM&O Support & Process RM&O Support & Process Management Management Resource Management Resource Management & Operations Readiness & Operations Readiness Resource Provisioning & Allocation to Service Instance
Resource Problem Management Resource Problem Management Resource Quality Analysis, Resource Quality Analysis, Action & Reporting Action & Reporting Resource Data Collection, Analysis & Control Resource Data Collection, Analysis & Control
Strategic & Business Planning
Financial Management
Brand Management
HR Policies & Practices
PR & Community Relations Management
Research & Development
Process Architecture Management & Support Information Systems Strategy & Planning Enterprise Quality Management
Disaster Recovery & Contingency Planning Security Management

Supply Supply Chain Chain Strategy & Strategy & Policy Policy Supply Supply Chain Chain Planning & Planning & Commitment Commitment Supply Supply Chain Chain Capability Capability Availability Availability Supply Chain Supply Chain Development Development & Change & Change Management Management Supply Supply Chain Chain Performance Performance Assessment Assessment

S/PRM Operations Support & S/PRM Operations Support & Process Management Process Management S/P Relationship Management S/P Relationship Management Operations Readiness Operations Readiness S/P S/P Buying Buying S/P Purchase S/P Purchase Order Order Management Management S/P Problem S/P Problem Reporting & Reporting & Management Management S/P S/P Performance Performance Management Management S/PRM S/PRM Settlements Settlements & Billing & Billing Management Management
Business Development
Procurement Management
Market Research & Analysis
Workforce Strategy
Shareholder Relations Management Regulatory Management
Technology Acquisition
Supplier/Partner Interface Management Supplier/Partner Interface Management
Enterprise Architecture Planning Group Enterprise Management
Real Estate Management
Advertising
Workforce Development
Fraud Management
Strategic & Enterprise Planning Brand Management, Market Research & Advertising
Enterprise Enterprise Architecture Architecture Planning Planning Group Group Enterprise Enterprise Management Management Brand Brand Management Management Market Research Market Research &&Analysis Analysis Advertising Advertising

Knowledge Knowledge Management Management Enterprise Quality Enterprise Quality Management Management Information Information Systems Strategy Systems Strategy &&Planning Planning
Employee & Labor Relations Management TeleManagement Forum
Legal Management
Knowledge Management
Business Business Development Development
Strategic && Strategic Business Business Planning Planning
Process Process Architecture Architecture Management && Management Support Support
Research & Development Technology Acquisition

Research && Research Development Development Technology Technology Acquisition Acquisition

Financial Financial Management Management Real Estate Real Estate Management Management Procuremant Procuremant Management Management

Regulatory Regulatory Management Management Legal Legal Management Management PR &&Community PR Community Relations Relations Management Management Shareholder Shareholder Relations Relations Management Management

HR Policies HR Policies &&Practices Practices Workforce Workforce Strategy Strategy Workforce Workforce Development Development Employee &&Labor Employee Labor Relations Relations Management Management

Security Security Management Management Fraud Fraud Management Management Disaster Recovery Disaster Recovery &&Contingency Contingency Planning Planning
39/156
40/156

Strategy & Commit Infrastructure Lifecycle Mgmt. Product Lifecycle Management
Operations
Operations Support & Readiness Fulfillment Assurance Billing
eTOM Level 3 : Billing & Collections

NGOSS
Customer Interface Management Customer Interface Management Selling Selling Marketing Marketing Fulfillment Fulfillment Response Response Order Order Handling Handling Problem Handling Problem Handling Customer QoS / /SLA Customer QoS SLA Management Management
NGOSS

Market Market Strategy & Strategy & Policy Policy Product & Product & Offer Offer Business Business Planning & Planning & Commitment Commitment Product & Product & Offer Offer Portfolio Portfolio Capability Capability Delivery Delivery CRM CRM Capability Capability Delivery Delivery Marketing Marketing Capability Capability Delivery Delivery Product Product Development Development & & Retirement Retirement Marketing Marketing CommuCommunications nications & & Promotion Promotion Product, Product, Marketing Marketing & Customer & Customer Performance Performance Assessment Assessment

CRM Operations CRM Operations Support & Process Support & Process Management Management CRM Operations CRM Operations Readiness Readiness Sales & Channel Sales & Channel Management Management
Billing & Billing & Collections Collections Management Management
Product & Offer Product & Offer Portfolio Strategy, Portfolio Strategy, Policy & Planning Policy & Planning
Sales & Sales & Channel Channel Development Development
Retention & Loyalty Retention & Loyalty

Service Service Strategy & Strategy & Policy Policy Service Service Planning & Planning & Commitment Commitment Service & Service & Operations Operations Capability Capability Delivery Delivery Service Service Development Development & & Retirement Retirement Service Service Performance Performance Assessment Assessment

SM&O Support & Process SM&O Support & Process Management Management Service Management & Service Management & Operations Readiness Operations Readiness Service Service Configuration Configuration & Activation & Activation Service Problem Management Service Problem Management Service & Service & Specific Specific Instance Instance Rating Rating
Service Quality Analysis, Service Quality Analysis, Action & Reporting Action & Reporting

Resource & Resource & Technology Technology Strategy & Strategy & Policy Policy Resource & Resource & Technology Technology Plan & Plan & Commitment Commitment Resource & Resource & Operations Operations Capability Capability Delivery Delivery Resource Resource Development Development Resource Resource Performance Performance Assessment Assessment

RM&O Support & Process RM&O Support & Process Management Management Resource Management Resource Management & Operations Readiness & Operations Readiness Resource Provisioning & Allocation to Service Instance
Resource Problem Management Resource Problem Management Resource Quality Analysis, Resource Quality Analysis, Action & Reporting Action & Reporting Resource Data Collection, Analysis & Control Resource Data Collection, Analysis & Control

Supply Supply Chain Chain Strategy & Strategy & Policy Policy Supply Supply Chain Chain Planning & Planning & Commitment Commitment Supply Supply Chain Chain Capability Capability Availability Availability Supply Chain Supply Chain Development Development & Change & Change Management Management Supply Supply Chain Chain Performance Performance Assessment Assessment

S/PRM Operations Support & S/PRM Operations Support & Process Management Process Management S/P Relationship Management S/P Relationship Management Operations Readiness Operations Readiness S/P S/P Buying Buying S/P Purchase S/P Purchase Order Order Management Management S/P Problem S/P Problem Reporting & Reporting & Management Management S/P S/P Performance Performance Management Management S/PRM S/PRM Settlements Settlements & Billing & Billing Management Management
Supplier/Partner Interface Management Supplier/Partner Interface Management
Strategic & Enterprise Planning
Business Business Development Development Strategic && Strategic Business Business Planning Planning Enterprise Enterprise Architecture Architecture Planning Planning Group Group Enterprise Enterprise Management Management
Brand Management, Market Research & Advertising

Brand Brand Management Management Market Research Market Research &&Analysis Analysis Advertising Advertising

Knowledge Knowledge Management Management Enterprise Quality Enterprise Quality Management Management Information Information Systems Strategy Systems Strategy &&Planning Planning
Process Process Architecture Architecture Management && Management Support Support
Research & Development Technology Acquisition

Research && Research Development Development Technology Technology Acquisition Acquisition

Financial Financial Management Management Real Estate Real Estate Management Management Procuremant Procuremant Management Management

Regulatory Regulatory Management Management Legal Legal Management Management PR &&Community PR Community Relations Relations Management Management Shareholder Shareholder Relations Relations Management Management

HR Policies HR Policies &&Practices Practices Workforce Workforce Strategy Strategy Workforce Workforce Development Development Employee &&Labor Employee Labor Relations Relations Management Management

Security Security Management Management Fraud Fraud Management Management Disaster Recovery Disaster Recovery &&Contingency Contingency Planning Planning
41/156
42/156
Identifikatori grupa procesa i procesa (Level 1, 2, 3 IDs)

NGOSS
Primjeri ID grupa procesa (Level 1)

NGOSS
grupama procesa i procesima dodijeljeni su identifikatori (ID) prema sljedeem formatu:
Customer
Strategy, Infrastructure & Product Operations
Operations Support & Readiness O Strategy & Commit Infrastructure Lifecycle I Management Product P Lifecycle Management
aaaaaa.b.XXXX.c.d.e
aaaaaa : (broj) identifikator tvrtke ICSP; koristi se ako ICSP proiruje ili mijenja proces (precizni format ovog polja nije definiran i ne koristi se u eTOM standardu). b : (broj) identificiranje organizacije/tvrtke koja je izvorno definirala proces. Ako je proces TMF-ov koristi se 1; za sve ostale sluajeve 2. XXXX : (znakovi) do 4 znaka se koristi za identificiranje Level 1 okomitih grupiranja:
S - Strategy & Commit, I - Infrastructure Life-Cycle Management, P - Product LifeCycle Management, O - Operations Support & Readiness, F - Fulfillment, A Assurance, B - Billing, E - Enterprise Management.
Fulfillment Assurance
Billing
A OFAB.1
SIP.1
CRM ID = 1.OFAB.1
TMF-ova spec.
SIP.2
Resource Development & Management (Application, Computing and Network) Resource Management & Operations (Application, Computing and Network)
OFAB.2
SIP.3
OFAB.3 OFAB.4
SIP.4
c : (broj) identifikator procesa na Level 1 razini d : (broj) identifikator procesa na Level 2 razini e : (broj) identifikator procesa na Level 3 razini
43/156
Strategic & Enterprise Planning E.1 Financial & Asset Management Brand Management, Market Research & Advertising E.2 Human Resources Management Stakeholder & External Relations Management Research & Development, Technology Acquisition
E.3
E.4 E.8
E.5
E.6
E.7
44/156
Primjeri ID procesa (Level 2 i 3)

NGOSS
Opis procesa Level 2 i 3 (GB921 D)

Proces Name Proces ID Brief Description Customer Interface Management 1.FAB.1.2 Upravljanje svim sueljima izmeu tvrtke i potencijalnih odnosno postojeih klijenata. Procesi odgovorni za kontakt s klijentima, procjenu svrhe kontakta, preusmjeravanje klijenta na odgovarajui proces, terminiranje kontakta, upravljanje iznimkama (neregularnosti i sl.), analiza i izvjetavanje o rezultatima kontakta. Kontakt se moe odnositi na jedan ili vie procesa vezanih uz usluge (Fulfillment, Assurance (upravljanje kvalitetom usluge te upravljanje kvarovima i problemima) , Buling) ovisno o klijentovom traenju. NGOSS
1.FAB.1.2 1.F.1.4 1.F.1.3 1.F.1.5 1.A.1.7
Extended Description
Level 1
1.A.1.6
1.B.1.8
1.FAB.1.9
Level 2
Level 3
Proces Name Proces ID Manage Request (Including SelfService) 1.FAB.1.2.2 Upravljanje svim zahtjevima upuenim od strane potencijalnih i postojeih klijenata. Svrha procesa je
1.FAB.1.2.1
1.FAB.1.2.2
1.FAB.1.2.3
1.FAB.1.2.4
Level 3 procesi
45/156
Brief Description Extended Description
46/156
Specifikacije postoje i do Level 4

NGOSS
Se llin g
Level
Dinamiki aspekti
NGOSS
2
Customer Data Acquisition Cross / Up Selling
eTOM daje smjernice za modeliranje dinamikih aspekata:

predvia se modeliranje tokova procesa i interakcija izmeu procesa uz upotrebu: elemenata SID modela za specificiranje informacija koje se razmjenjuju i sljedeih dijagrama:
Process Flow Diagrams (uz varijante Process Interaction Flow Diagrams i Process Dynamics Flow Diagrams) Activity Diagrams (UML) Use Case Diagrams (UML) State Chart Diagrams (UML) Sequence Diagrams (UML)
Prospect M anagement
Customer Qualification and Education
Sales Negotiation
Prospect Needs Analysis
Understand Customer Need
Solution Determination With the Customer Sales Proposal Development
Customer Identity Capture
Up & Cross Sale Opportunities Identifica Up & Cross Sale Packages Application
Potential Solutions Identification
Qualify Customer
Relationship Establishment
Track and Report Prospect Result
Develop Solution Alternatives
Solution Details Negotiation
Customer Profile Capture and Record Customer Preferences Capture and Record
zato nema referentnog modela tokova procesa?

svaki ICSP e implementirati odreeni proces koristei vlastitu kombinaciju elemenata procesa i njihovog povezivanja u skladu s poslovnom vizijom, misijom i ciljanom tritu!
48/156
C u stomize Solutions to Customer Requirem Confirm Solution Availability
Sales Closure
Product Development Inquiry
47/156
Pristup modeliranju toka procesa (GB921F)

NGOSS
Primjer eTOM: General Interaction Diagram

NGOSS
to predstavlja model toka procesa?

veze i interakcije izmeu elemenata procesa u kontekstu nekog procesa vie razine analizira se samo jedan (tipini, glavni) scenarij (dakle model predstavlja samo djelomini pogled na cjelokupno ponaanje)
kako modelirati tokove procesa u skladu s eTOM radnim okvirom?

1. Identificiranje cross-functional procesa (CFP) i elemenata procesa od kojih je sastavljen 2. specificiranje General Interaction Diagram-a (identificiranje veza meu elementima procesa) 3. specificiranje Process Interaction Flow (no sequences) ili Process Dynamics Flow diagrama (sequences). specifikacije treba raditi za odabranu razinu detalja (ako elimo manju koliinu detalja vezanu za tok procesa koristimo eTOM elemente procesa vie razine i obratno)
veze izmeu procesa, ali bez ikakvih detalja vezanih za ponaanje
49/156
50/156
Primjer eTOM: Level 2 Proces Interaction Flow Diagram

NGOSS
Primjer eTOM: Level 2 Proces Dynamics Flow Diagram

NGOSS
Cu stomer Cu stomer Contacts Re tailer Cu s t o me r Interf ace Management Cu stomer Re la tionship Ma n a gement Cu stomer Interf ace Ma n a gement Re trieve Cu stomer Prof ile Of f er Cu stomer S o lution A lternatives S ales Pr oposal of f er to Cu stomer Re tention & Loyalty Pr eOrder to Order Ha n dling Up d a te Customer Co ntact History Cu stomer places order Cu stomer Places Order
Cu stomer Interf ace Ma n a gement
S ales enquiry r o uted to Selling group Ma r keting Fu lf illment Response S e lling
O r d er Handling
S e lling
Cu s t o me
Pre Order result Service Ma n a gement & Operations De s ign&Technology S e lection Request S e rvice Conf iguration & A ctivation
Resource Ma n a gement & Operations
O ptional F low
Resource Re servation Re quest
Co nf irm Resource Re servation
Re s ource Provisioning & A llocation to Sv Ch e ck External S u p p lier Solution S u pplier/ Pa rtner Re la tionship Ma n a gement En terprise S u p p lier/Partner B uying
staze u dijagramu odgovaraju funkcijskom grupiranju iz eTOM modela; svaki element se pojavljuje samo jednom tako da dinamika toka interakcija nije eksplicitno prikazana 51/156
52/156
Level 3 Decomposed Process Flows

NGOSS
Order Handling
Pre-Order to Order Handling
Process Dynamics Flow Diagram (slijed eksplicitno oznaen)

NGOSS
PreOrder Feasibility Determination
Pre-Order result
Send PreOrder Feasibility request

Customer Order to Order Handling
Get preOrder resullts Order Issuance

Internal Work Order
Credit Authorization
Coordination of Supplier/partner components
Order Tracking and Status
Design and Technology selection Request
Detailed Design
Design of solution
Request Detailed Confirmation by Engineering
Customer accepts Design
Order Tracking and Status

Service Details for Billing
End-to-end Service Test completed
Order Completion
Service Details for Assurance
Order Completion advice
Level 4 processes
53/156
54/156
UML dijagrami kojima se moe specificirati dinamika eTOM procesa

NGOSS
Specifikacije koje predvia eTOM

NGOSS
Activity diagram
Start CRM
Design Solution
Sales
Service Activator Track Service Order
SM&O
Receive PO & Issue Order
Create Service Order
Close Service Order
Track Order & Manage Jeopardy
Allocate Specific Resources to Services
Use Case diagram

Start Created Canceled
Track & manage Work Order
Implement & Configure Service
In Execution Delayed
Test Service E2E Complete Order
Closed End
End
Activate Service
Statechart diagram
55/156
56/156
Odnosi izmeu pruatelja usluga, uloge i veze meu procesima

NGOSS
Kako se eTOM moe koristiti?

NGOSS
Specifikacije sistematiziranih eTOM procesa predstavljaju tehniki i tehnoloki neutralnu referentnu toku prema kojoj ICSP moe:
usporeivati i analizirati vlastite procese i odnose meu njima, donositi odluke o njihovom unapreenju (redizajn, optimiranje, atomatizacija) te o osmiljavanju i uvoenju novih procesa procijeniti potrebe te definirati suradnju i sporazume s okolinom potencijalnim klijentima, drugim ICSP i dobavljaima (outsourcing, outtasking), SI i ostalim zainteresiranim strankama pregovarati s dobavljaima oko nabavke COTS komponenata na tritu za automatiziranje postojeih i planiranih procesa procjenjivati cijenu implementacije te performanse buduih procesa.
Tijekom razvoja NGOSS rjeenja, proizvoaima PP, SI i samim ICSPs, specifikacije temeljene na eTOM-u predstavljaju poetne, referentne artefakte na kojima se temelji izrada svih ostalih specifikacija.
57/156
58/156
eTOM se neprestano razvija

NGOSS
Sadraj
NGOSS
traje dekompozicija procesa i tokova procesa na niim, detaljnijim razinama radi se na izradi preciznijih uputa, vodia i pomagala za upotrebu eTOM neprestano se prate odzivi od industrije i prema njima se odreuju prioriteti daljnjeg razvoja na eTOM okviru radi mnotvo ICSPs, SIs te proizvoaa opreme i programske podrke. Svima je potreban referentni, industrijski standardizirani okvir za razvoj OSS komponenata mnogi ICSPs dostavljaju modele vlastitih poslovnih procesa koji prelaze granice tradicionalnih okvira i odnose se na specifina podruja poslovanja
NGOSS program eTOM
SID
TNA arhitektura NGOSS Lifecycle & Methodology OSS/J inicijativa
59/156
60/156
Postojea situacija na podruju informacijskog modeliranja

NGOSS
Razlika izmeu informacijskog modela i modela podataka

NGOSS
Klasina tehnologija (npr. SNMP SMI, CLI) ograniena:

specificiranje samo low-level tehnikih aspekata ureaja ne postoji mogunost izraavanja poslovnih pravila, politika, procesa direktna promjena konfiguracije mrenih elemenata kao odgovor na novonastale ili promijenjene zahtjeve poslovanja nije mogua.
Otvara se prostor za postojanje dva jezika:

high level informacijski jezika za specificiranje poslovnih pravila i politika low level jezika za specificiranje tehnikih aspekata IC opreme.
Informacijski model (Information model) tehnoloki neovisan model (ne ovisi o bilo kojem specifinom tipu spremita podataka, nainu upotrebe putem raunarskih programa ili pristupnom protokolu). Model podataka (Data model) - predstavlja konkretnu implementaciju informacijskog modela u obliku prilagoenom specifinom tipu spremita podataka i protokolu za pristup. Obuhvaa strukture podataka, operacije i pravila koji definiraju kako su podaci pohranjeni te kako im se pristupa i manipulira s njima.
Suvremeni jezici za informacijsko modeliranje nove generacije (DMTF CIM,TMF SID) temelje se na UML-u su dizajnirani da omoguavaju modeliranje high i low level aspekata ime se omoguava nesmetan i uniformni protok informacija na razini cijele tvrtke; upotreba standardnih jezika (CIM, SID) otvara mogunost povezivanja procesa razliitih ICSPs.
61/156 62/156
to je SID?
NGOSS
Zato dijeljeni informacijski model?

NGOSS
dio NGOSS programa. zajedniki, dijeljeni informacijski model specificira:

informacijske entitete koje su povezane s poslovnim procesima i na koje ti procesi utjeu (osobe, imovina, proizvodi i usluge high-level koncepti) odnose meu entitetima detalje koji dodatno opisuju entitete izraene atributima.
zajednike, dijeljene informacije za jednostavnu integraciju upotreba standardnog, dijeljenog modela osigurava:
uniformne specifikacije tokova informacija izmeu procesa, kako u okvirima tvrtke ICSP, tako i izmeu tvrtki i njihovih vanjskih partnera. zajedniku terminologija bez nepotrebnih varijanti. most izmeu poslovanja koje trai efikasna rjeenja i informacijske tehnologije pomou koje se rjeenja implementiraju. (specifikacije razumljive poslovnim krugovima koje su dovoljno precizne da se koriste u poetnim fazama razvoja programske podrke)
planirani razvoj SID-a:

specificiranje entiteta vezanih uz rjeenje (projektiranje i implementaciju; APIs lower-level koncepti) dijeljeni model podataka
ICSPs i ostali akteri u dohodovnom lancu imaju potrebu za dijeljenjem informacija i njihovim zajednikim razumijevanjem. SID model usmjeren je k rjeavanju te potrebu.
63/156
64/156
SID dokumenti
NGOSS
SID principi modeliranja

NGOSS
GB922 GB922 GB922 0 GB922 1A GB922 1BI GB922 1BT GB922 1C GB922 1J GB922 1L GB922 1P GB922 1POL GB922 1R GB922 1T GB922 1U GB922 2 GB922 3 GB922 4S-O GB922 4S-QoS GB922 5LR GB922 5PR GB926
Business View of the SID (covering concepts and principles) SID Business View: Concepts & Principles Primer for the SID Business View SID Agreement SID Business Interaction SID Business Entity Base Types SID Business Contract SID Project SID Location SID Party SID Policy SID Root Business Entities SID Time Related Entities Using the SID (UML models) SID Customer SID Product SID Service Overview SID Quality of Service SID Logical Resource SID Physical Resource System View of the SID
modeliraju se dvije vrste entiteta (stvari):

koje imaju identifikator (mogu se jednoznano identificirati) koje imaju samo vrijednost (slue za opis prve vrste)
model obuhvaa:
kontekst i uloga entiteta stanje i ivotni ciklus entiteta (opcionalno) odnosi meu entitetima: nasljeivanje, asocijacije, agregacije
za modeliranje se koristi se UML globalna sistematizacija/kategoriziranje entiteta:

Zachmanov okvir to Gdje Kako Tko Kada Zato
65/156
Primjer predmeta interesa po kategoriji Entitet koji je nuan u poslovanju Svojstva, zemlje, lokacije, ulice, rute kabelske mree, granice, Procesi, poslovi, planovi, strategije. Klijenti, dobavljai, zaposlenici, Trenuci ili periodi vremena Pokretai investicija, ciljevi
66/156
SID je projektiran tako da omoguava proirivanje

NGOSS
ServiceSpecification/Service Pattern
NGOSS
intenzivno se koriste obrasci za modeliranje (modeling patterns):

specificiranje uobiajenih odnosa i pojava npr. fizikih spojeva ili struktura koji se pojavljuju u realnim domenama obrasci daju modelu svojstvo proirljivosti.
propisuje razdvajanje entiteta od specifikacije entiteta.
esto koriteni obrasci:

Composite Pattern ServiceSpecification /Service pattern Role Object Pattern Entity-Entity Specification Pattern Temporal State Entity Pattern
Composite pattern
67/156 68/156
Temporal State Entity Pattern

NGOSS
Pojmovi vezani uz organiziranje informacija u modelu

NGOSS
Business Entity, BE predstavlja neto to je u fokusu interesa poslovanja (Customer, Customer Order, Customer Account). Opisano je pomou atributa i nalazi se u odnosima prema drugim BE. System Entity, SE predstavlja neto to je u fokusu interesa projektiranja sistema (Service) i/ili upravljane okoline (Physical Resource) Aggregate Business Entity, ABE dobro definirani skup povezanih informacijskih entitete (koncepte) vezanih uz poslovanje (business entities) Aggregate System Entity, ASE skup sistemskih entiteta koji se definira na temeljima ABE entiteta.
69/156
70/156
Kako su informacije u SID modelu organizirane?

NGOSS
SID Business View (Level 0)

NGOSS
SID model obuhvaa informacijske entitete koji se koriste za:

modeliranje poslovanje i poslovnih procesa (SID Business View) (GB922) specifikaciju sistema (SID System View) (GB926)
SID na osnovnoj razini Level 0 sadri 8 domena (6 se poklapa s NGOSS domenama). SID Common Business domena obuhvaa ABEs koje se koriste u ostalih 7 domena:
Root Business Entities Agreement Business Interaction Location Party Policy Management Project Time Trouble Ticket Usage Base Types Business Contract
72/156
Entiteti su organizirani po domenama (Level 0):

SID Business View Domains (8 domena) SID System View domains. (8+1 domena) (osam domena iz SID Business View ukljueno je i u SID System View u kojem je dodana domena Architecture).
Modeliranjem podataka na implementacijskoj Implementation View) bavi se OSS/J.
razini
(SID
71/156
SID Domene + Level 1 ABEs

NGOSS
Level 2 i Level 3 ABE

NGOSS
Market/Sales
Market Segment Sales Statistics Sales Channel Competitor
Service Service Test

Market Strategy & Plans Contact/Lead/Prospect Marketing Campaign
Service Order
Service Strategy
Service Outage Service Trouble
ABE
Service Specification Service Quality Service Level Specification Service Usage Service Service Capacity Service Performance
Level 3 ABEs identificirane u CustomerFacingService ABE
Service Domain & Level 1 ABE
Product
Strategic Product Portfolio Plans Product Specification Product Product Offering Product Performance
Product Usage Statistics
Domene
Service
CustomerFacing Service ResourceFacing Service
Applied Customer SLA Customer Statistics Customer Customer Interaction Billing Rates Customer Order Customer Bill Inquiry Customer Problem Customer Customer Bill Collections Customer Bill
Customer
Service
Service Service Specification Service Quality
Service Order
Service Strategy
Service Outage
Service Level Specification
Service Test Service Usage Service Trouble
Service Specification
ServiceSpec Enterprise (under construction)
Industry Compliance Supply Chain Strategy Workforce
Service Capacity Resource Usage
Service Performance Resource
Resource
Resource Traffic Control
Resource Performance Resource Resource Specification Network Topology Resource Test Resource Traffic Alarm and Strategic Resource Plans Logical Element Resource Fault Outage
ServiceLevel Spec ServicePackage ServiceBundle
Supplier/Partner
Supplier/Partner S/P Problem
S/P Product
S/P Strategy
S/P Interaction
S/P Bill
Common Business Entities

Party Location Interaction Policy
S/P Order S/P SLA
S/P Statistics
S/P Payment S/P Bill Inquiry
S/P Performance
Agreement
73/156
Level 2 ABEs identificirane unutar Level 1 ABEs koji pripadaju Service Domain
74/156
Business Entity Definition

NGOSS
Primjer (business view): PolicyRule Definition

NGOSS
75/156
76/156
Proirenja sistemskih specifikacija u odnosu na business specifikacije

NGOSS
SID System View (Level 0)

NGOSS
proirenje nad ve postojeim entitetom iz poslovnog modela:

dodavanje atributa koji imaju znaenja na sistemskoj razini (beznaajni na poslovnoj) dodavanje sistemskih operacija transformacija asocijacije u klasu asocijaciju (kako bi se u model ugradilo detaljnije znaenje za dotinu asocijacije) dodavanje ogranienja (via OCL) kako bi se preciznije specificirali uvjeti ili ogranienja (npr. za klase ili pred i post uvjeti nad operacijama)
SID System View = 8 SID Business View Domains + Architecture. Openito, ASEs u svakoj od SID System View domena predstavljaju proirene/prilagoene ABEs iz pripadnih SID Business View domena.
definiranje novog entiteta koji ima znaenje na sistemskoj razini:

ugradnja novih klasa u model kojima se modeliraju koncepti znaajni za sistem (npr. message bus) translatiranje jednog entiteta sa poslovne razine u jedan ili vie entiteta na sistemskoj razini (npr. to model an attribute as an object) upotreba drugaijih projektnih obrazaca (npr. Observer, Reflection, itd.) upotreba suelja i drugih tipino sistemskih koncepata.
upotreba UML-ovi mehanizama za

stereotypes tagged data constraints
77/156
78/156
Primjer proirenja (Business view -> system view)

NGOSS
Primjer proirenja (Business View -> System View) (nastavak)

NGOSS
Card business view
Card system view (varijanta 2)
Card system view (varijanta 1)

79/156 80/156
Service Domain & Level 1 ASE

NGOSS
Hijerarhija nasljeivanja
NGOSS
81/156
82/156
Veze SID domena i eTOM funkcijskih grupa

NGOSS
Veza eTOM - SID

NGOSS
83/156
84/156
Princip povezivanja SID eTOM modela

NGOSS The Customer Domain includes all data and contract operations associated with individuals or organizations that obtain products from an enterprise, such as a service provider. It represents of all types of contracts with the customer , the management of the relationship, and the administration of customer data.
Princip povezivanja SID eTOM modela (nastavak)

NGOSS
Customer ABEs
Primary Vertical eTOM Process Groupings
Primary eTOM Level 2 Processes
Secondary eTOM Level 2 Processes
Product Marketing Communications & Promotion
Customer
Is the focus for the Customer domain. Customer data is the enterprises knowledge of the customer and accounts held by a customer CRM-F
Order Handling Problem Handling
Selling
Customer QoS/SLA Management Billing & Collections Management Retention & Loyalty Customer Interface management Selling
SID ABEs se povezuju s eTOM Level 2 procesima Primary eTOM Level 2 proces je proces koji upravlja ivotnim ciklusima objekata iz pridruenog mu SID ABE; (CRUD) Secondary eTOM Level 2 procesi jesu procesi koji koriste objekte iz dotinog SID ABE.
Customer Interaction
Represents communications with customers and translation of customers requests and inquiries into appropriate events such as the creation of an customer order ... CRM-FAB
Order Handling
Customer Interface Management
Problem Handling Customer QoS/SLA Management Billing & Collections Management Retention & Loyalty
85/156
Common Business Entities (iz Common Domain) se ne preslikavaju na eTOM procese (koriste se od strane itavog niza eTOM procesa) 86/156
Postoji SID u Rational Rose formatu

NGOSS
Postoje XML scheme SID modela

NGOSS
87/156
XSD Representation of the SID Customer ABE
88/156
Sadraj
NGOSS
to je Technology Neutral Architecture (TNA) ?

NGOSS
NGOSS program eTOM SID
TNA arhitektura
NGOSS Lifecycle & Methodology OSS/J inicijativa
TNA je apstraktna arhitektura postoje konkretne implementacijske arhitekture za raspodijeljene sisteme koje su u skladu sa TNA (primjer J2EE). NGOSS razlikuje Technology Neutral Architecture, TNA (upotreba tehnoloki neutralnih koncepata) od Technology Specific Architectures, TSA (upotreba koncepata specifinih za jednu ili vie tehnologija) Osnovna zadaa TNA je osigurati meudjelovanje u NGOSS sistemima TNA arhitecture = Interaction architecture. Elementi TNA arhitekture su specificirani metamodelom.
89/156
90/156
NGOSS TNA metamodel NGOSSExtensibleElement

NGOSS
Elementi metamodela
NGOSS
Contract: temelj za interoprabilnost u NGOSS sistemu NSS GOComponent: predstavlja standardan nain za pakiranje NGOSS funkcionalnosti NGOSS Shared Information: informacije koje se razmjenjuju izmeu NGOSS komponenta NGOSS Identifier: predstavlja standardni nain za jednoznanu identifikaciju NGOSS elemenata NGOSS Policy: predstavlja standardizirani nain za kontroliranje ponaanja NGOSS komponenata i procesa NGOSS Interaction: predstavlja interakciju razliitih NGOSS elemenata i prema tome odreuje ponaanje Termination: koristi se za definiranje operacija iz NGOSS ugovora NGOSS Extensible Element apstraktni entitet od kojeg nasljeuju ostali elementi metamodela
91/156
92/156
NGOSS TNA metamodel NGOSS Contracts & Interactions

NGOSS
to je NGOSS ugovor?
NGOSS
specifikacija koja se pridruuje suelju na temelju koje se klijent povezuje sa komponentom koja implementira to suelje omoguava specificiranje oekivanog ponaanja na konzistentan nain (ciljevi i odgovornosti) omoguava upravljanje servisima te registriranje i pozivanje servisa utvruje kontekst za izvoenje servisa i omoguava klijentu odabir servisa specifikacije iz ugovora mogu se koristiti za odravanje i administriranje suelja tj. servisa koji se preko njega prua specifikacije iz ugovora mogu se koristiti kako bi se osiguralo honoriranje u sluaju neispunjavanje vanjskih obveza (SLA).
93/156
94/156
Kako se NGOSS ugovor specificira?

NGOSS
System View Contract
NGOSS
Specifikacija ugovora moe sadravati ope podatke o ugovoru te funkcijske i nefunkcijske aspekte.
funkcijski aspekti - sintaksa i semantika za upotrebu suelja. nefunkcijski aspekti - specifikacije performansi, QoS garancije i sl.
Header
Contract Id Contract Defining Organization (CDO) Description capabilities:
capability name signature (input and output parameters) pre-conditions
condition exceptions thrown in termination
Functional capability part
Specifikacija funkcijskih aspekata:

opis suelja. opis operacija koje se mogu pokrenuti: naziv operacije, skup parametara skup povratnih vrijednosti (terminations) koje se vraaju nakon pokretanja i zavretka izvoenja operacije preduvjeti postuvjeti. UML dijagrami kojima se dodatno formalizira ponaanje
terminations
termination definition post-conditions exceptions when post-condition not assured
interaction type system and/or component level use case external actors and roles that initiate the interact(s) behavioral part
models of the expected behavior of the interactions: activity, interaction, and state diagrams used entities/models
Models

structural part
Non-Functional part
management operations security Policies QoS
96/156
95/156
Comments
TNA se temelji na komponentama

NGOSS
TNA Component Model

NGOSS
97/156
98/156
Upravljanje komponentama i njihovim sadrajem

NGOSS
Transparentnost Raspodijeljenosti (Framework Services)

NGOSS
NGOSS Components
Installed and Uninstalled
NGOSS Services
Activated and De-Activated
NGOSS Contracts
Registered and Unregistered
NGOSS Contract Instances

Advertised and Withdrawn
99/156
100/156
Obvezni NGOSS servisi

NGOSS
Modeliranje upravljakih politika i PBM dio je NGOSS arhitekture

NGOSS
Distribution and Transparency Framework Services

Registration Services Naming Services Location Services Registry Services
Other Mandatory Services

Process Management Service Policy Management Service Security Management Service
U NGOSS arhitekturi sistema predviena je mogunost upotrebe politika za usmjeravanje djelovanja NGOSS sistema (policy-enabled management architecture). Upravljanje temeljeno na politikama (Policy-Based Management, PBM) predstavlja efikasnu paradigmu na podruju upravljanja mreom, uslugama i openito raspodijeljenim sistemima. Politika se definira kao perzistentna, deklarativna specifikacija odreenog pravila kojim se definira mogua varijanta u ponaanju neke komponente ili sistema. Pravilo ima klasian oblik:
if <uvjet> then <akcija>.
101/156
102/156
NGOSS TNA metamodel - Policy

NGOSS
Tipina primjena PBM

NGOSS
103/156
104/156
The Policy Continuum (Strassner, 2004)

NGOSS
Arhitektura PBM sistema (IETF)

NGOSS
105/156
106/156
TNA - sigurnosni kontekst

NGOSS
Detailed View of NGOSS TNA Architecture

NGOSS
Identity and Authentication Authorization (access control) Privacy Integrity Attribution (non-repudiation) Availability
107/156
108/156
Sadraj
NGOSS
NGOSS Lifecycle & Methodology projekt

NGOSS
NGOSS program eTOM SID TNA arhitektura
definiranje metodologije za projektiranje i razvoj rjeenja/sistema usklaenih s NGOSS etiri pogleda na NGOSS sisteme tijekom razvoja: business, system, implementation i deployment views NGOSS L&M pokuava dati ICT industriji praktine odgovore na sljedea pitanja:
kako koristiti NGOSS i implementirati NGOSS rjeenja, kako koristiti specifikacije NGOSS programa (eTOM, SID, TNA) kako organizirati i podijeliti aktivnosti oko izrade rjeenja u kontrolabilne korake. kako transformirati specifikacije iz pogleda u pogled (koje artefakte treba generirati i kada, morfiranja) kako u procesu razvoja koristiti znanje koje ICSP ve posjeduje ukljuivi tu i vlastite pristupe i metode sistemskog i programskog inenjeringa
NGOSS Lifecycle & Methodology

OSS/J inicijativa
... odnosno definirati suvisli proces razvoja koji se moe logiki pratiti i opetovano koristiti.
109/156 110/156
NGOSS Lifecycle Views

NGOSS
NGOSS Lifecycle Views (nastavak)

NGOSS
Logical Views tech. neutral
Business View (technology & technical free): specificiranje aspekata poslovanja: ciljevi, procesi, entiteti (akteri, informacije, dokumenti) i interakcije. System View (technology free but computing): projektiranje sistema koji predstavlja rjeenje: podsistemi, objekti, ponaanje, suelja i interakcije. Implementation View (concrete computing technology): implementacija rjeenja za odreenu platformu realizacija suelja razvojem ili izborom i kupovinom COTS komponenata; specifikacija modela podataka. Deployment View (run-time): odnosi se na aktivno praenje ponaanja NGOSS sistema i osiguravanje planiranog rada. Prema potrebi, izvode se odgovarajue korektivne akcije (process and policy based management), ili redefiniranje sistema.
Service Providers Views Service Developers Views
111/156 112/156
Physical Views tech. specific
NGOSS podrka ivotnom ciklusu

NGOSS
Detailed View of NGOSS Lifecycle

NGOSS
113/156
114/156
Uloga eTOM-a u ivotnom ciklusu

NGOSS
SID Morphing
NGOSS
eTOM - specifikaciju poslovnih procesa procjenu sistemskih procesa i njihove interakcije te procjenu potencijalnih granica programskih komponenata ICSP tvrtka koja pokuava implementirati NGOSS mora implementaciju procesa temeljiti na poslovnim aktivnostima koje su kategorizirane u eTOM-u tj. mora koristi iskljuivo eTOM elemente procesa. Ako postoji potreba za nekom aktivnou koja nije kategorizirana i podrana od strane nekog od eTOM procesa, tada ICSP treba pokrenuti ugradnju novog elementa u eTOM standard.
SID odnosno njegove morfirane varijante se koriste u svim fazama ivotnog ciklusa i predstavlja kontinuum u specifikacijama informacija koje su meusobno zavisne SID Business View (technology & technical free): UML class diagrams; no root element, no operations SID System View (technology free but computing) to je objektno usmjereni informacijski model (computational objects):
UML class diagrams computing system entities UML interface concept (stereotype <<interface>>) abstractions in structure (<<system>> i <<subsystem>>)
SID Implementational View (concrete computing technology) :

OSS/J je definirao tehnoloki specifinu varijantu SID-a koja se naziva Core Business Entities, CBE i koristi se za implementaciju sistema u J2EE okruenju.
SID Deployment View: run-time data objects
115/156
116/156
SID for Business, System and Implementation View

NGOSS
Contract Morphing
NGOSS
specifikacije morfiraju, ali kao podloga se koristi SID

Information model
(common/shared base)
Standard (e.g. SID Business View
NGOSS TNA predvia kontinuum NGOSS ugovora gledano obzirom na 4 pogleda.
Svaki oblik NGOSS ugovora podrava:

informacije specifine za dotini pogled, veze prema informacijama iz prethodnih faza ivotnog ciklusa, informacije i podatke koji dokumentiraju funkcionalnost, zavisnosti i okolinu.
118/156
Information model
(system design 1)
...
Information model
(system design N)
Standard (e.g. SID System View
Data Model
(platform 1)
...
Data Model
(platform M)
Vendor/platform specific implementation
117/156
Business View Contract

NGOSS
Business View Contract (nastavak)

NGOSS

119/156
Header Contract Id Contract Defining Organization (CDO) Description Scope - Organization, System or Component Level - Summary, User goal or sub-function Audience - The set of people to which this use case is intended Primary Actor(s) - The stakeholder that initiates the action and whose interests must be satisfied Supporting Actor(s) - External system, resource or person against which the system delivering a goal to the primary actor has a goal Tertiary Actor(s) - Stakeholder who is not a primary actor Primary Goals - Goals of the primary actor Stakeholder Goals - Goals of the other stakeholders (i.e., vested interests that must not be adversely affected by accomplishing the primary goal) Pre-Conditions - What must be true before the use case runs Minimal Guarantees - What must be true after the use case runs and the stakeholder interests are protected Success Guarantees - What must be true after the use case runs and the stakeholder interests are satisfied Triggers - Stimuli that causes the use case to start executing Main Scenario - The use case in which nothing goes wrong resulting in delivery of the success guarantee Extension Conditions - Conditions under which the system takes a different behavior (includes failures and exceptions) Comments
120/156
Primjer specifikacije System View Contract

NGOSS
Primjer specifikacije Implementation View Contract

NGOSS
Header Contract Id = configure_DSL_port Contract Defining Organization = TMF Description = configuration of physical layer of DSL port Functional capability part capability 1:
capability name = configure_DSL_port signature INPUT = port_coordinates (shelf/slot), DSL_profile_name, customer_ID OUTPUT = result, error code pre-conditions condition = DSL_profile_name already defined in DSL equipment exceptions thrown in termination = operation failure with error code = unknown profile terminations termination 1
termination definition = successful operation post-conditions = port configured as requested exceptions when post-condition not assured = / termination definition = failed operation post-conditions = port configuration unchanged exceptions when post-condition not assured = port configuration in an unknown state 121/156
Standardno Java suelje: interface X { /*** javadocs for preconditions and postconditions */ String configure_DSL_port(portCoordinates, DSLProfileNameCustomerID) throws UnknownProfileException; ..... }
termination 2
....
122/156
Model Driven Architecture, MDA

NGOSS
MDA osnovni pojmovi

NGOSS
A domain describes a bounded area of knowledge or interest

It can be structured into various subdomains
A metamodel is a formal representation of the concepts in that particular (sub-)domain, as well as their relationships
OMG-ov pristup razvoju sistema:

1. definira sistema pomou Platform Independent Models, PIM 2. transformacija PIM modela u Platform Specific Models, PSM 3. PSM modeli se transformiraju u programski kod.
123/156
124/156
Odnos izmeu primjeraka, modela i njihovih metamodela

NGOSS
Transformacija modela
NGOSS
metameta-model level
conforms To
Ecore conforms To ATL conforms To
conforms To meta-model level MMTimeDom
MMCompDom conforms To
conforms To Time2Comp model level TimeDomain
conforms To
CompDomain transformation
125/156
126/156
Metamodeli i pravila za transformaciju

Pojednostavljeni Statechart ModelElement metamodel
StateMachine
source outgoing NGOSS
Transformation rule
ModelElement Guard Event
trigger
Pojednostavljeni class diagram metamodel

Operation
Postoji NGOSS/MD3. To je TMF-ov team

NGOSS
Feature
generalization
NGOSS Model Driven Design and Development Tools Framework team (NGOSS/MD3-TF) Dugorona vizija:
Razvoj alata (Model-driven Tools) za potporu NGOSS Lifecycle and Methodology. Na taj nain e se NGOSS razviti od Model-Centric u pravi Model-Driven pristup!
GeneralizableElement subtype Transition

supertype
Generalization
specialization
StateNode
target incoming
Classifier State Class SimpleState ENT m2(i)[g2]/a3 m1(i)/a1 m1() m2()
Preduvjeti za razvoj alata koji e podrati Model-Driven NGOSS:

Capture NGOSS artefacts using precise metamodels Facilitate exchange of modelling content between tools (XMI) Define transformations that map technologyagnostic models onto technology-specific realisations
A m1() m2()
B m1() m2()
m2(i)
m2(i)[g1]/a2
Statechart model ENT
State Pattern
127/156
128/156
Model-Driven NGOSS Tools Environment

NGOSS
Model-Driven NGOSS Tools Environment (nastavak)

NGOSS
129/156
130/156
Sadraj
NGOSS
Uloga OSS/J inicijative i doseg specifikacija

NGOSS
NGOSS program eTOM SID TNA arhitektura NGOSS Lifecycle & Methodology
elite implementirati NGOSS usklaeni sistem u Java i Web Services tehnologijama? Specifikacije OSS through Java, OSS/J inicijative odnose se naskup APIS za implementaciju NGOSS komponenata za upravljanje poslovanjem, uslugama i mreom u okvirima J2EE standardne infrastruktura. Specifikacije su javno dostupne i obuhvaaju:
OSS/J Common APIs Specijalizirane APIs po OSS domenama Referentne implementacije
OSS/J inicijativa
OSS/J koristi Java Community Process (JCP) - formalni proces za razvoj Java specifikacija - kao instrument za standardiziranje APIs.
131/156
132/156
Doseg OSS/J specifikacija

NGOSS
Da li J2EE arhitektura zadovoljava principe apstraktne TNA?

NGOSS
J2EE osigurava:
podrku distribuiranom radu, standardnu komunikaciju (RMI-IIOP, message-driven i connector-based komunikacijski mehanizmi) upravljanje transakcijama (trenutno u sklopu NGOSS arhitekture ova funkcionalnost nije posebno razmatrana) (vano u domeni upravljanja) skalabilnost (vano u domeni upravljanja) ugradnja i rasporeivanje komponenata (J2EE module jedinica za ugradnju npr. JAR datoteka) razdvajanje poslovnih procesa od implementacije PP temeljem: Suelja definiranih ugovorom (run-time aspekti tehnoloki neutralnih NGOSS ugovora implementirani su pomou standardnih EJB komponenata; specifikacije NGOSS ugovora se na implementacijskoj razini translatiraju u Java suelja) Otkrivanje servisa tijekom izvoenja (Factory object + JNDI lookup) Rad usmjeravan politikama (J2EE ne prua zadovoljavajuu podrku baratanja s politikama kako je to opisano u NGOSS TNA). Uloge korisnika i sigurnost (J2EE prua mogunosti vezane za sigurnost; NGOSS arhitektura jo ne definira sve aspekte) dijeljenost informacija mogue; implementiro OSS/J (CBE) 134/156
133/156
Da li J2EE arhitektura zadovoljava principe apstraktne TNA? (nastavak)

NGOSS
NGOSS Contract vs. J2EE EJB Interface Metamodel

NGOSS
Principi vezani uz NGOSS arhitekturu su podrani ili direktno sa mogunostima J2EE ili preko OSS/J-ovog dizajna API-a.
Ako usporedimo System Capability Object Schema iz NGOSS TNA sa J2EE EJB Interface Metamodel moemo zakljuiti da metoda EJB odgovara SCO objektu. Dakle, preslikavanje specifikacije NGOSS System Contract u NGOSS Java Implementation Contract jest preslikavanje na deklaracije standardnih EJB/Java suelja.
135/156
136/156
Karakteristike OSS funkcija implementiranih za J2EE

NGOSS
OSS Common APIs

NGOSS
J2EE omoguava da OSS funkcije:

budu specificirane i implementirane kao EJB komponente, osiguravaju zdruivanje, skalabilnost i otpornost na kvarove (upotreba podrka J2EE aplikacijskog servera u kojem se komponente izvode) koriste Java RMI komunikaciju koja diktira direktnu povezanost (tightly coupling) (po tipovima i uz sinkronizam); takva komunikacija posebno je pogodna za aplikacije koje zahtijevaju visoke performanse (real-time procesi iz Operational eTOM area) te aplikacije osjetljive na transakcije (npr. za konfiguriranje) koriste asinkronu komunikaciju (indirektna povezanost, loosely coupling) Java dogaajima objavljenim putem JMS (npr. veliki broj mjerenja ili dogaaja vezanih uz kvarove ili promjene u performansama) koriste asinkronu komunikaciju XML porukama/dokumentima pri emu se otvara mogunost integracije temeljena na dokumentima u kontekstu odreenog toka posla (workflows) - integracija procesa i orkestraciju komponenata. koriste Web Servise za indirektnu povezanost preko razliitih transportnih protokola pogodno za integraciju u uvjetima tehnoloke raznolikosti i prostorne disperziranosti OSS aplikacija uz slabije performanse (B2B). oslanjaju se na JCA konektore radi integracije sa starim sistemima.
137/156
OSS Common API definira zajedniku bazu/podlogu Java klasa i suelja pogodnih za specifikaciju upravljakih, OSS APIs U izradi OSS Common API-a koritene su sve prednosti koje pruaju obrasci za projektiranje J2EE/EJB aplikacija. OSS Common APIs specifikacije integriran je i temeljni model podataka (osnovni koncepti proizvod, usluga, resurs, ) koji predstavljaju gornji sloj generiki dio model u OSS domeni. Model se naziva se Core Business Entities, CBE. OSS Common API koristi se za razvoj APIs specijaliziranih za potrebe odreene domene npr. Billing, QoS, Order Management itd.
138/156
CBE
NGOSS
CBE vs SID
NGOSS
Managed entities
Entity type opisuje entitet odreenog tipa koji ima neovisno postojanje. To moe biti objekt sa fizikim postojanjem ili objekt s konceptualnim postojanjem
CBE je data model (razvijen na temelju SID) projektiran tako da zadovolji informacijske (parametri, povratne vrijednosti) potrebe OSS/J APIs (javax.oss.cbo paket). CBE se prema potrebama specificiranja pojedinih OSS/J APIs proiruje. Sva proirenja su u skladu sa SID modelom (proirenje prema naprijed). Ukoliko neki entiteti nisu definirani u SID radi se proirenje SID-a (proirenje prema natrag).
SID - organizirana zbirka entiteta iz poslovne i sistemske domene specificirana kao UML model. CBE se temelji na SID-u i predstavlja model koji odgovara implementacijskom pogledu tj. deklariran je kao skup standardnih suelja (podrava paradigmu programiranja na suelje, a ne na implementaciju). Sva su suelja Java serijalizibilna to ih ini pogodnim za rad u raspodijeljenom okruenju.
<<Interface>> Party <<Interface>> PartyRole
SID (business view)
dvosmjerni proces usklaivanja specifikacija
<<Interface>> PartyPlaysRoleAssociation
<<Interface>> Address
SID ABE
CBE
139/156
Core Business Entities specifikacije
<<Interface>> NorthAmericanAddress
140/156
OSS/J Resource Inventory API proiruje CBE specifikacije

NGOSS
Proirenja OSS/J specifikacija

NGOSS
CBE Resource Inheritance Hierarchy
141/156
142/156
Integracijski profili
NGOSS
Java Integration Profile

NGOSS
OSS/J APIs moe se koristiti uz 3 integracijska profila:
Intended Use
Tight integration
Interactio n Pattern
Java Value Type Session Bean (JVT) or Java Integration Profile XML Messaging or XML Integration Profile Web Services
JVT sequence diagram
Loose integration (EAI, B2B or web browser scenarios) Loose integration (B2B Internet based scenarios)
143/156
144/156
XML Integration Profile

NGOSS
WS Integration Profile
NGOSS
pristup upravljanom objektu preko XML request/reply paradigme upravljani objekt koji prelazi suelje predstavljen je XML dokumentom ija je XLS definirana od strane OSS/J i ukljuena u OSS Common API interakcija temeljena na XML request/reply porukama podrava iste operacije kao i JVT SessionBean od ekvivalentnog entiteta
Interakcija preko WS zahtjeva. Zahtjevi se usmjeravaju prema WS endpoints. Parametri operacija definirani su WSDL specifikacijama WSDL specifikacije su ukljuene u OSS Common API
WS; loosely coupled interactions
PrimjerXML over JMS; loosely coupled, process driven interactions
145/156
146/156
Primjer: provisioning process - upotreba WS i BPM

NGOSS
OSS Common API OSS/J Building Block

NGOSS
OSS Building Block , BB (OSS/J aplikacija) je skup zdruenih komponenata i prua servise vezane uz odreenu upravljaku domenu (Trouble Ticket, Service Activation, Performance Management, Fault Management, ). BB je sastavljen od sljedeih tipinih vrsta komponenata:
EJB Session Beans, Message Driven Beans EJB Entity Beans
Managed Entities ili Business Object mogu biti predstavljeni kao EJB Entity Bean, Java Value Type Object ili kao XML dokumenti.
Source: TMFC1816
147/156
148/156
Komponente OSS/J aplikacije uklopljene u J2EE arhitekturu

NGOSS
Popis OSS/J APIs

NGOSS
Order Management API Service Activation Resource Activation Testing Product Inventory Service Inventory Resource Inventory Service Discovery Resource Discovery Trouble Ticketing Service Problem Resolution Customer SLA Management Process Quality Management
Service Quality Management Fault Monitoring Performance Monitoring Billing Billing Mediation Pricing
149/156
150/156
Odnos izmeu NGOSS i OSS/J specifikacija

NGOSS
OSS/J API Roadmap based on eTOM

NGOSS
eTOM OSS/J: OSS/J API Roadmap based on eTOM SID OSS/J: OSS/J API Info requirements mapped to SID model framework NGOSS Contract OSS/J: OSS/J APIs designed to be Javabased realizations of NGOSS contracts
151/156
152/156
OSS/J API Info requirements mapped to SID model framework

NGOSS
Alati za razvoj OSS/J APIs

NGOSS
Java/EJB integracijski profil, kao i XML i WS integracijski profili definiraju isti obim funkcionalnosti samo u vlastitoj tehnolokoj domeni. Na temelju specifikacija za Java integracijski profil (Java value-type based interfaces) mogue je automatski generirati specifikacije potrebne za XML/JMS i WS profile.
153/156
154/156
OSS/J Certification Process

NGOSS
NGOSS sutra: Policy Driven Systems & Autonomic Computing

NGOSS
Testiranje proizvoda obzirom na specifikaciju OSS/J API-a
Policy Driven run-time fleksibilnost (danas)

omoguava sistem administratorima da na vioj razini, npr. downloadanjem high-level politika, upravljaju sistemima napori da se definiraju SID, DENng i slini high-level informacijski modeli
Autonomic Computing pored policy driven mogunosti ukljuuje i aspekte samoupravljivosti na razini komponente (sutra)
155/156
156/156

Ngoss

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Ngoss

Uploaded by

Copyright:

Available Formats

Problem i mogue rjeenje

TMF NGOSS program

minimiziraju vrijeme potrebno za uvoenje nove usluge

Trend - broj poslovnih subjekata u lancu se poveava

Rastui izazovi upravljanja i operativnog voenja:

to je NGOSS ? (ivotni ciklus i metodologija razvoja)

NGOSS = Architectures + Lifecycle & Methodology

ivotni ciklus NGOSS sistema promatra se kroz 4 karakteristina pogleda:

Metodologija razvoja NGOSS sistema:

poluformalne upute iterative, business process centric, model-based

NGOSS Frameworks (nastavak)

Upotreba NGOSS frameworks-a tijekom:

Information Framework (Shared Information and Data Model, SID)

Applications Framework (Telecom Applications Map, TAM)

System Integration Framework (Technology Neutral Architecture, TNA)

Architectural Concepts (rjeenja usklaena s NGOSS)

Rjeenja/sistemi usklaeni sa NGOSS:

OSS/J nudi rjeenje ...

NGOSS specifikacije Release 6.0

Napomena - (ne)preciznost NGOSS specifikacija

Tko koristi NGOSS i kako ?

to je Enhanced Telecom Operations Map (eTOM)?

Od TMN preko TOM do eTOM

Hijerarhijska dekompozicija procesa

Hijerarhijska dekompozicija procesa (nastavak)

Primjer hijerarhijske dekompozicije (eTOM)

eTOM principi specifikacije

eTOM Konceptualna razina (Level 0)

Operations area (Level 1)

Market, Product and Customer

Customer Relationship Management

Service Management & Operations

Resource Management & Operations

Service Lifecycle Process (FAB)

Strategy, Infrastructure & Product area (Level 1)

Strategy, Infrastructure & Product

Marketing & Offer Management

Service Development & Management

modify services quickly activate and deliver services rapidly

manage SLAs ensure service availability monitor quality

Resource Development & Management

Supply Chain Development & Management

E2E (okomito) vs funkcijsko (horizontalno) grupiranje (Level 1)

Enterprise Management area (Level 1)

Strategic & Strategic & Enterprise Enterprise Planning Planning

Financial & Financial & Asset Asset Management Management

Human Human Resources Resources Management Management

eTOM Level 0 & 1

Operations area (Level 2)

Marketing & Offer Management

Customer Relationship Management

Service Development & Management

Service Management & Operations

Sales & Channel Management

Retention & Loyalty

Service Management & Operations

Resource Management & Operations

Resource Problem Management

Strategic & Enterprise Planning Financial & Asset Management

Brand Management, Market Research & Advertising Human Resources Management

Supplier/Partner Relationship Management

Supplier/Partner Interface Management

Elementi procesa ukljueni u vie E2E grupa