CIGRE Working Group D2.33
Operation & Maintenance of Telecom
networks and associated information systems
in the Electrical Power Utility
Paris, 14-15 June, 2012
Membership
- -P2
Thomas LEROY
BE
Elia
Fernando CASTRO
ES
ZIV
Jaume DARNE
ES
Pullnet
Mehrdad MESBAH (Conv.)
FR
Alstom
Pascal PARISOT
FR
RTE
Paul RENSHALL
GB
MottMac
Jan PIOTROWSKI
PO
Eltel Networks
Jorge FONSECA
PT
REN
Rui FRANCISCO
PT
EDP
Ion NEDELCU
RO
Eltel Networks
Valentin PEPTENARU
RO
Teletrans
Corresponding Membership
- -P3
Rubén GOMEZ
AR
EPEN
Michael SCOTT
AU
AusGrid
Rohan FERNANDEZ
AU
Electranet
Miguel Angel ALVAREZ CABANES
ES
ZIV
Julio ALVAREZ
ES
REE
Sampo YLIRAASAKKA
FI
Nokia Siemens Nets
Kazuto IWASAKI
JP
Kiushu Electric Power Co
John CRISP
NZ
Transpower
Pedro FONSECA
PT
EDP
Andrei BORDUF
RO
Teletrans
Danilo LALOVIC
RS
EPS
Jovanka GAJIKA
RS
Pupin Institute
Matjaz BLOKAR
SI
Specinova
Ziyaad GYDIEN
ZA
Eskom
Parkash DARYANI
US
Aurigacorp
AGENDA
• Thursday 14 June
09H00
09H30
Reception of participants and coffee
Opening of the meeting
• Member Presentations
• Admin. Issues
13H00
14H30
17H30
20H30
O&M Discussions
Lunch
TB Scope & Structure Definition
Meeting break Day 1
Dinner in Paris
• Friday 15 June
09H30
12H30
- -P4
TB Scope & Structure Definition
Work Allocations & Next Meeting
Close meeting – Lunch
Advisory Group D2 .03
Mapping WG to Issues of Concern
WGD2-26
D2-461 (2011)
Service Architecture, Provisioning/Delivery Model,
Management & Support
WGD2-34
Service Continuity
& Disaster Recovery
Communication
Services
Smart Grid
Services
UTelco Services
WG D2-13 (2008)
WGD2-30 Protection Communications
(2012)
35-192 (2001)
WGD2-28 Operational IP Services
(2012)
O&M
(Future WGD2-xx)
Mobile Data Services
Core Services
SC B5
Customer Premises Access
Substation IP Access
WGD2-29 (2012)
Access Network
Backbone
Network
Communication
Networks
WG D2-07
Multi-service IP Networks
Operational VPN
Scalable Core
Networks
WGD2-33
NG SDH
Optical Fibre & WDM
WGD2-35
Local Access Technologies
DSL, Wireless Mesh, etc.
-
- -P5
WGD2-32
Wide Area Ethernet
Passive Optical Networks
D2-245 (2003)
Telecom
Technologies
Private Mobile Radio
Wireless Broadband Data
Power Line Carrier
D2-241 (2002)
Fibre Deployment
& Maintenance
D2-460 (2011)
Broadband Power Line
WGD2-27
D2-302 (2006)
WG D2-19 (2008)
New WGD2.33
Operation & Maintenance of Telecom and IT systems
•
Different organizations and responsibility approaches
− separate Telecom & IT or merged ?
− In-house or external
•
Perimeter of the organization
− Operational, Corporate Enterprise,
− Local Networks and Wide Area Transport
•
Management tools (Operation Support Systems, Inventory systems, etc.)
•
ICT for enhanced Power System Asset maintenance –
−
−
−
−
Communications for workforce management,
Dedicated mobile/nomadic data applications (survey, inventory data, work orders, …)
Wireless in the Substation (WiFi, etc.)
Tele-maintenance communication infrastructure
•
•
•
•
- -P6
Organization, Process, Tools
Operation Support Systems
Field Worker Communications
Telecom for Asset Maintenance
Remote real-time monitoring, visualization and diagnostics of assets
Remote access of external contractors and on-duty staff to infrastructure
Access of external contractors to EPU premises
Access of contractors in EPU premises to their remote support base
O&M of Telecom networks and associated IS
•
Kick-off : June 2012
•
Term of Delivery : June 2014
•
8 meetings (+1 or 2 in Cigre session/colloquium) :
1.
2.
3.
4.
5.
6.
7.
8.
9.
- -P7
June 2012 (Massy)
[Aug 2012 (Paris Cigre Session) – Wed 29.08 (afternoon)]
Oct 2012
Jan 2013
Apr 2013
June 2013
Oct 2013
Jan 2014
Apr 2014
WGD2.33 - Work Plan
Meeting
Date
Venue
1
June 2012
Paris
2
Aug 2012
Wed 29.08 PM
Paris (Cigre)
3
Nov 2012
week 45 (8-9)
Barcelona
4
Jan 2013
Warsaw
to be confirmed
5
Apr 2013
London
6
June 2013
7
Oct 2013
8
Jan 2014
9
Apr 2014
June 2014
Other venues : Brussels, Lisbon/Coimbra, Vienna, Prague, Padua
- -P8
Kick-off, Define TB Scope & Structure
Discuss TB scope & structure with Corr members (Half day
meeting)
Contributions on allocated work
TB structure finalized
Full Draft
Final draft submitted
WG D2.33 (O&M) and D2.34 (Disaster Recovery)
•
Comments from Advisory Group meeting:
•
These groups deal with 2 different faces of the same task
•
O&M process, organization and tools deal with normal, day-to-day operation of the network
•
Disaster Management (disaster-resistance, -preparedness, and –recovery) deals with avoiding disastrous situations and O&M
process when extraordinary situations do happen
•
O&M targets at optimized operation, DR aims at essential services survival
•
DR means employing extra people, extra assets, extra tools, and special process in addition to those required for normal O&M
•
How and when (decision criteria and source) do we switch from normal incident management to extra-ordinary disaster
recovery?
•
A common WG33/34 questionnaire on what exists in Utilities is desirable
•
WG34 should also consider Power Utilities Defense Plan
- -P9
Manage “disastrous” incidents for service continuity using special
processes, extra people & extra tools
WGD2.34
Disaster Recovery for ICT
Manage incidents for optimal cost/performance using
ordinary processes, tools and workforce
WGD2.33
O&M of Power System Telecom Networks
Telecom for O&M of Power Systems
Process Automation
(when & why?)
Op. Telecom OSS
Field Worker Comms
Remote Monitoring of assets
WGD2.26
Service Provisioning Model
Telecom Asset Ownership
Telecom Management Process
(Management Tools)
- - P 10
Maintaining & Managing
Smart Grids
(New WG D2 to be set)
Tentative Structure
•
•
•
•
- - P 11
Introduction
− Business case for our work, What? Why? How?
Telecom O&M – Organization & Process (use TB461 and extend)
− Impact of Telecom service delivery model on O&M
− Size and scope of organization (operation vs enterprise, local area vs wide area)
− Formal/informal processes and interactions
− Process automation (when & why), cost of automation vs cost of manual treatment
Telecom Operation Support System
− Network infrastructure management
− Communication service management
− Incident management, service desk
− Network & service inventory
− O&M communications
ICT for Power System Asset Maintenance
− Current practices & process evolution
− Field worker communications
− Tele-maintenance
Management
Tools
Management
Scope
Management
Management
Organization
Process
TB461 Fig 10.1
- - P 12
Power Corporation
EPU
Telecom
Service
Operations Corporate
Provider
Activities
EPU
A
C
Operations
Corporate
Activities
Telecom
B
Operations
EPU
D
Telecom
Services
EPU
Corporate
Activities
Corporate
Activities
Operations
Telecom
Service
Contractor
Telecom
Assets
E
EPU
Operations
TB461 Fig 8.4
Corporate
Activities
Telecom
Service
Provider
A: Telecom is part of the operational activity. Corporate entity provisions telecom services separately.
B: Common Telecom (& IT) Services for both Corporate and Operational Applications.
C: TSP is a sister company to the EPU, providing services exclusively (or in priority) for the Power System
- - P 13
D: EPU procures its telecom assets but operates them using an external Service Contractor
E: Telecom services are procured under SLA by a TSP providing services to many customers.
Maturity Model for Telecom Service Delivery
Providing Service to External Customers & U-Telco Business Involvement
Operational
Services
only
Internal
Multi-User
Services
External
Managed
Services
External
Leasing of
Facilities
External
Non-IP
Wholesale
External
IP Service
Wholesale
External
Retail
Services
External Contractor & Service Provider Involvement
Supplier
Helpdesks &
Warranties only
Field
Maintenance
Contracts
Full Service
Delivery
Contracts
Service costs
estimated but
not recovered
Service costs
recovered at
no profit
Service price
established as
Service Catalog
Relationship
can get formal if
problems arise
Formal SLA
No systematic
measurement
Liable to SLA
Must constantly
produce formal
proof
Support
Contracts for
sub-systems
Procure
Telecom
Services
Cost Recovery from Service Users
Overall telecom
budget without
repartition
Resource
repartition per
contributing
entity
Telecom Liability to Service Users
Implicit,
User
application
serves to
define the QoS
Required QoS
is defined &
agreed upon
TB461 Fig 10.2
- - P 14
Deploy &
Adjust
Business Development
Service Portfolio Evolution
Service Migration Planning
Upstream
Management
Build Service Offer
Build Capability
Strategy &
Planning
Build Strategy
Customer / User
Operations
Customer / User Relationship
Service Management
Resource Management
Provider / Contractor Relationship
Security, BCP, Safety, Skill Mgt
Provider / Contractor
Enterprise
Processes
Initialize
Deliver
Provide Support
- - P 15
TB461 Fig 10.7
Get Paid
User Order
Handling
User Service
Enquiry Desk
Set up User SLA
Monitor User SLA
SLA Management
Notification
Contingency
User Problem
Handling
User Change
Management
User
Dashboards
Service
Configuration
& Activation
User Invoicing
& Settlement
Service
Continuity
Service Quality
Management
Capture
cost of
service
Change Request
Site Access
Service Policing
& Usage Metering
Service
Configuration
Management
Service
Capacity &
Performance
Management
Disaster
Recovery
Network
Configuration
Management
Bandwidth &
Capacity
Provisioning
Service
Impact
Network Fault
Management
Network
Performance
Management
- - P 16
Incident
Management
Problem
Management
Field Maintenance
Asset Lifecycle
Management
Spare Management
Service
Change Mgt
Network
Change Mgt
Work Allocation
Who
When
All
Questions for the questionnaire
Mid-July
All
Present O&M organization & practice
Mid-July
Paul
ITIL processes
Mid-July
Pascal
Safety Monitoring
NOC and manaagement organization
Mid-July
AMI maintenance & Monitoring
Mobile & radio maintenance
Mid-July
Integrated management tools, Service Impact
Mid-July
Jan
Mehrdad
Thomas, Jorge, Jaume
- - P 17
What
Data core network monitoring
Rui
Distribution domain management of O&M
and associated telecoms
All
Send presentations to all
End of June
Mehrdad
Send WG26 report to members not having
the report
Send draft 33 to members
End of June
Paul, Ion
Power system domain O&M requirements in
terms of communications