Sie sind auf Seite 1von 18
Inventory evolution

Inventory evolution

Upgrade Services

Upgrade Services

Upgrade Services

Why upgrade

Why upgrade › Better usability and new GUI/Thin client › New Task Manager/orchestration tool › New

Better usability and new GUI/Thin client New Task Manager/orchestration tool New architecture more fit for purpose Out of the box models New SDK/extension kit available for end user organization Virtualization Improvements in the D&R module (usability & performances) Enhancements and defects logged in the previous version have been addressed in this release of EAI Current release already end of support

Example Workshop Agenda
Example Workshop Agenda

Example Workshop Agenda

Architectural Overview

Architectural Overview

›Introductions:

– Scope

– Aims and Objectives

– Strengths/Weaknesses of Current deployment

›“As Is” Landscape:

– Overview of Existing deployment and modules in use

– Role (Provisioning, assurance, asset management)

– Supported Technologies (Mobile, MMBB, Enterprise)

– Overview of Interfaces

– Level of Automation

– Data Volumes & Quality – are there known deficiencies/gaps/problems

– Infrastructure (HA, DR etc)

Modelling

 
Modelling  

› Core Models (Sites, Equipment, Cables, Segments):

 

– Extensions (associations, attributes, validation rules, name generation) – Templates (number and complexity)

Service Modelling:

Mapping of existing models (path/network/AMO) to Connection Orientated, Connectionless, Wireless models Extensions (associations, attributes, validation rules, name generation) Bandwidth Table

Model Extensions:

 

AMO, UDC -> Mapping to NGO or to pre-defined models (E.g. WOSS to EAI Wireless Model)

Other Items:

 

IPAM, Works, Auto-routing, Reports

Automation & Integration

 

Automations, Plug-ins and Integration Points:

Ownership and Development History

Module Use (Assign & Design, Granite Automator)

Custom Code (mechanism (Java, WS))

Volumes

Known Issues

Discovery & Reconciliation:

Number of adapters (Ownership and development history)

Supported devices/services (physical only or logical/service discovery)

Transaction Volumes

Known Issues

discovery) – Transaction Volumes – Known Issues Ericsson Expert Analytics | © Ericsson AB 2016
Example Analysis
Example Analysis

Example Analysis

Recommended Upgrade Approach

Recommended Upgrade Approach › Upgrade to EAI 16.1 with EDR 9.3.2 – Utilize EAI 16.1 standard

Upgrade to EAI 16.1 with EDR 9.3.2

Utilize EAI 16.1 standard Start to use the evolved Thin Client GUI Introduce new technologies direct in the new models using EAI NGO (next generation object) model Takes advantage of new improved features (e.g. connectionless model) Granite Classic Models and EDR Models will be migrate and evolved to the new EAI Models after upgrade Replace CNUM by EAI Identifier Management New integration between EAI and ENE

EVOLVED

REPLACED

EVOLVED

REPLACED

Solution - Proposed Architecture Interface s Order EMS NMS TTM Fault Mgt Mgt
Solution - Proposed Architecture
Interface
s
Order
EMS
NMS
TTM
Fault Mgt
Mgt
Number Portability (TS Solution)
Number
Portability
(TS Solution)

Inventory Upgrade

EAI 16.1

(non BCM)

Identifier

Mgt

EDR 9.3.2

DDS

Upgrade EAI 16.1 (non BCM) Identifier Mgt EDR 9.3.2 DDS Adapter s Data Sync Product Integratio

Adapter

s

Data

Sync

Product
Product
Product
Product

Product

Product
Product
Product
Product

Integratio

ENE

R 16.x

XML GW

CNUM

IPAM

EII

R 2.3

Activation (TS Solution Thru GI DB)
Activation
(TS Solution
Thru GI DB)

Ericsson Expert Analytics | © Ericsson AB 2016

n

Upgrade facts

 
Upgrade facts  

Maintain critical support to OSS inventory solution

   

Enhancements from previous versions

 

Upgrading now will ensure that TS can move to future releases of EAI (i.e. 16.x, 17.x, 18.x) with less risk

Use the new Thin Client User (GUI) which is more friendly and simple to work

SDK toolkit which makes agility, flexibility and extensibility when developing

A robust ID management to support any communications identifier, and flexible enough to extend to future identifier types with limited to no customization replacing also CNUM capabilities

 

Using Automation Value Pack the Unified Inventory Engine (UIE) and Network Designer (ND) work together to select the most appropriate network elements and paths using available resources represented in any database

Simple integration because in the new architecture Inventory objects are defined using an XML-based Object Model

 

Full integration support with WebServices, EJBs

 

New capabilities of EAI available to use:

 

Wireless RAN Model

 

Connection Services

Connectionless Services

ND

UEI

Thin Client

SDK

Ericsson Expert Analytics | © Ericsson AB 2016

 

ID Management

Upgrade Strategy

Upgrade Strategy › Modeling Assessment → Analysis to determine how the existing data models can be

Modeling Assessment → Analysis to determine how the existing data models can be best supported in EAI

Data Model and Administration → Remodel the granite classic objects and administration features to new EAI capabilities according with the Modeling Assessment

Interfaces, Custom adaptation and Validations plugins → Redevelop to fit the new EAI architecture and Data model

IPAM and CNUM to Identifier Management → Remodel and reconfigure IPAM and CNUM in the new EAI Identifier Management

EDR Adapters and DDS Modules → Redevelop the adapters and DDS Modules to the EAI Architecture and Models using the Modeling Assessment result

XML Gateway to Data Sync → The use of XML GW will evolve to use Data Sync to fit the new EAI architecture and Data Models

Data Migration → Completely Data Migration from Granite Classic objects to the new EAI Solution deployed

EII to New Interface → A new integration between EAI and ENE replacing EII will be developed

 

User Documentation → Update user documentation to reflect the new EAI Deployment and way of working

User Training → Training in EAI + EDR products

 
 

Ericsson Expert Analytics | © Ericsson AB 2016

 

Conclusion Consideration

Conclusion Consideration

Ericsson recommends to upgrade Granite 8.1 and EDR 8.1 to EAI 16.1 Standard and EDR 9.3.2

• Least risk to this upgrade since the new Architecture will be deployed completely separated from the existing production system

• Optimal upgrade approach

• New Architecture Models and capabilities

• Architecture and Data Migration to the new NGO Architecture

• Easiest move to future releases of EAI (i.e. 16.x, 17.x, 18.x) with less risk

• All benefits, issues and product enhancement

• Continue support guarantee without impact in the TS business

• Ericsson does not recommend perform the upgrade without Ericsson's support due the complexity changes to the new architecture

Data Migration Tool
Data Migration Tool

Data Migration Tool

OVERVIEW

OVERVIEW › The Sincera DMT tool is a standalone application that runs in Windows through command

The Sincera DMT tool is a standalone application that runs in Windows through command line or in a UNIX environment.

Object export files will be created from a source system and data import will run on the Target system.

This tool will migrate existing Granite Inventory Data into the new 16.x data structure Ericsson Adaptive Inventory (EAI.)

Objects Migrated with DMT

 

Object Being Migrated with DMT

Any Exceptions or Additional Details

Site Object

Archived objects will not be migrated

AMOs will not be migrated

Floor Plan will not be migrated

Container/Shelves

Archived objects will not be migrated

AMOs will not be migrated

Point Codes will not be migrated

Equipment will not bring over data on template binding since there is no equivalent reference in EAI 16.1

Customers

Archived objects will not be migrated

AMOs will not be migrated

Cloud detail will not be migrated

Slot/Card

Archived objects will not be migrated

AMOs will not be migrated

Ports

Archived objects will not be migrated

AMOs will not be migrated

Specific Cases exist around Port Mapping – all will be brought over but in a new format for the new EAI model

Cables

Archived objects will not be migrated

AMOs will not be migrated

Cable Pairs

AMOs will not be migrated

Cable Strands

AMOs will not be migrated

Paths and Networks

Represented as a trail

Revisions: Will bring over multiple revisions to trails (1 of 1, Live/Pending, etc.)

Archived objects will not be migrated

AMOs will not be migrated

Path Relationships data will not be brought over. Tool will indicate what the paths were and the relationship.

Circuit Path links will all be represented as trail elements in the original path (trail) migrated

Path Legs will be migrated over and a separate trail object will be created

Trunk Group detail will not be migrated

Aggregate Paths will be skipped. Migration Tool will log that these aggregates were skipped.

Segments

Represented as a trail

Archived objects will not be migrated

 

Ericsson Expert Analytics | © Ericsson AB 2016

AMOs will not be migrated

objects will not be migrated   Ericsson Expert Analytics | © Ericsson AB 2016 ∙ AMOs

Migration Requirements

Migration Requirements › Source System – The source system must be an EAI 16.0 or 16.1
Migration Requirements › Source System – The source system must be an EAI 16.0 or 16.1

Source System

The source system must be an EAI 16.0 or 16.1 environment (BCM).

Target System

The target system will be an EAI 16.1 environment.

Ericsson Expert Analytics | © Ericsson AB 2016