Analysis Demand Profile

Purpose
This tab contains general information about the workbook

The definition of each column in the workbook.
Coded use cases
Data readiness of each use case aligned to systems
General Guiding Principles
Revision History
Initial Revision
Name Page Number
1. General Information 1
2. Column Dictionary 2
3. Analytics Demand Profile 3
4. Data Readiness Profile 4
Version Person Date

1.00
TAB Analtyics Demand Profile Column Column Heading Column Definition
Analytics Approach each use case
A Portfolio falls under
B Use Case Number Use Case Specific Number
C Analytics Capabilities - Future Demand Name of use case

Business Unit designation of use
D Priority case priority
Holistic assessment of data
E Data Readiness readiness to enable use case
Unstructured notes around
F Notes specific use case
Description / Overview of Analytics
G Use Case Description of use case
Description / Overview of Analytics
H Use Case Description of use case
I High-level Overview of Project Overview of the project
Group of value drivers related to
[CLIENT]'s strategic values - as
J Strategic Value Drivers defined by [CLIENT]
K Control Rates Strategic Value Driver
L Make Productive Investments Strategic Value Driver
M Earn reasonable returns Strategic Value Driver
Build a culture of safety and
N engagement Strategic Value Driver
O Grow the business Strategic Value Driver
Modernizing and Transformative
P Projects Strategic Value Driver
Q Innovative Products and Services Strategic Value Driver
R Customer Facing Strategic Value Driver
Creates a More Robust and
S Modernized Grid Strategic Value Driver
Regulatory Support for effective
T recovery Strategic Value Driver
Component of impact score,

weighted to reflect the importance
U Weighted Sub-Total of strategic value drivers
V Divider Space
Group of value drivers related to
[CLIENT]'s business values - as
W Business Value Drivers defined by [CLIENT]
X O&M reduction Business Value Driver
Y Revenue/margin growth Business Value Driver
Z Environmental Business Value Driver
AA Safety Business Value Driver
AB Physical and Cyber Security Business Value Driver
Operational Improvement (customer
engagement, SAIDI, SAIFI, MAIFI,
AC MTBF, etc.) Business Value Driver
AD Customer Service Excellence Business Value Driver
AE Smart Spending Business Value Driver
AF Regulatory Relationships Business Value Driver
AG Employee Engagement Business Value Driver

AH Weighted Sub-Total of business value drivers
AI Divider Space
Group of business units impacted

by use case enablement - as
AJ Business Unit Impact defined by [CLIENT]
AK Nuclear Business Unit
Fossil, Fossil Environmental Special
AL View Business Unit
Utility Operations - Integrated Energy
AM Management Business Unit
AN Utility Operations - Gas Business Unit
AO Infrastructure Business Unit
AP Energy Wholesale Commodities (EWC) Business Unit

AQ IT, Test BU Business Unit
AR Energy Market Ops / SPO Business Unit
AS Transmission Business Unit
AT Utility Operations - Distribution Business Unit
Utility Operations - Customer Systems
AU , BS Apps Business Unit
Customer Systems (Respond to

Consumer Requests, Outage
AV Reports, Operate Telephony Systems) Business Unit
AW Legal / Regulatory Business Unit
AX Audit Business Unit
AY HR Business Unit
AZ Safety and Security Business Unit
BA Supply Chain Business Unit
BB Finance/Accounting Business Unit
BC Commercial Analytics Business Unit
of use case impact on business
BD Weighted Sub-Total unit
BE Divider Space
BF Quality Architectural component
BG Timeliness / Latency Architectural component
BH Self-Service Architectural component
BI Agile & Elastic Architectural component
BJ Backup / Recovery Architectural component
BK Volume Architectural component
BL Security Architectural component
BM Integration Architectural component
BN Availability Architectural component
BO Asset Master Domain Characteristics
BP Power Asset Master Domain Characteristics
BQ Common Master Domain Characteristics
BR Customer Master Domain Characteristics
BS Measurement Master Domain Characteristics
BT Metering Master Domain Characteristics
BU Outage Master Domain Characteristics
BV System Network Master Domain Characteristics
BW Weather Master Domain Characteristics
BX Work Master Domain Characteristics
BY IoT Data Source Characteristics
BZ Social Data Source Characteristics
CA Weather Data Source Characteristics
CB Structured Data Source Characteristics
CC Unstructured Data Source Characteristics
CD Internal Data Source Characteristics
CE External Data Source Characteristics External
CF [PROJECT] Data Source Characteristics

CG [PROJECT] In Flight Initiatives Characteristics
[PROJECT]
[PROJECT][PROJECT]
CH [PROJECT] In Flight Initiatives Characteristics
CI [PROJECT] In Flight Initiatives Characteristics
CJ [PROJECT] In Flight Initiatives Characteristics
CK [PROJECT] In Flight Initiatives Characteristics
CL [PROJECT] In Flight Initiatives Characteristics
CM [PROJECT] In Flight Initiatives Characteristics
CN Empty Space
CO Management Consumers Impact
CP Customers Consumers Impact
CQ Field Consumers Impact
CR Regulatory Consumers Impact
CS
CT
CU
All the information captured are

Data Readiness Profile
Data Source Assets

based on the information from
APPRA that is mainly derived from
'Asset' tab columns 'K' and 'DH'.
A
Master Domain The master data domain matched to
B the IBM Utility Data Model
Other Data Domain Classification of all data domain that
are listed in APPRA (i.e. derived from
'Asset' tab columns 'K' and 'DH)' and
also based on information that
captured during interview with
SMEs/Stake Holders.
C
Data Location Classification of the data source
being internal or external, observed
based on the information from APPRA
that is derived from 'Asset' tab
columns 'K' and 'DH'.
D
Data Structure Classification of the data structure
(i.e. structured or un-structured),
observed based on the information
from APPRA that is derived from
E
Traditional Data Classification of the traditional data
source type (i.e. Third-party,
Transactional, System of Record)
listed on 'IBM Analytics reference
architecture: Capabilities', observed
columns 'K' and 'DH'
F
Integration Classification of the data source (i.e.
Batch/Real Time/ Near Real Time),
'Asset' tab columns 'K' and 'DH'
G
New Data Classification of the new data source
(such as Machine & sensor, Image &
video, Content Services,...) listed on
'IBM Analytics reference architecture:
Capabilities', observed based on the
information from APPRA that is
derived from 'Asset' tab columns 'K'
and 'DH'
H
Quality of Data quality of data (i.e. good, poor,
incomplete) observed based on the
and 'DH'
I
Technology List of technologies that are observed
J columns 'K' and 'DH'
Data Security Classification of the data source from
security aspect (i.e. risk, in place),
purely observed based on the
and 'DH'
K
System Scalability Classification of the data source
based on system scalability, purely
L
Data Acquisition Assets All the information captured are
M
Data Transformation Rule? Classification of the data rule
existence, observed based on the
and 'DH'
N
Transformation Tool Use Classification of the data
transformation (such as ETL tool,
manual) observed based on the
and 'DH'
O
Rules Repository Classification of the data rule
repository existence, observed based
on the information from APPRA that is
and 'DH'
P
Frequency Classification of the data
transformation frequency observed
Q
Standardizing Data? Classification of the data
standardization existence, observed
R
Shelf Life of Data Stored Classification of data how long data
resides in this layer, observed based
and 'DH'
S
Enriching Data? Classification of the data enrichment
at this layer, observed based on the
and 'DH'
T
Transformation Rule Quality Classification of the transformation of
data rule quality, observed based on
the information from APPRA that is
and 'DH'
U
Integration Method Observed based on the information
V 'Asset' tab columns 'K' and 'DH'
Technology/Tool Observed based on the information
W 'Asset' tab columns 'K' and 'DH'
Data Consumption Assets All the information captured are
X
Information Presented Classification of how information is
presented (such as KPI, Reports,…)
Y
Frequency Classification of the frequency of data
consumption (such as weekly, daily,
…) observed based the frequency
Z
Data Model Classification of the data model
customization of data consumption
(such as weekly, daily,…) observed
based the data model customization
AA
Data Model Customization Classification of the data model
customization of data consumption
(such as weekly, daily,…) observed
based the information from APPRA
AB
Archival strategy Classification of existence of the
archival strategy, observed based on
and 'DH'
AC
Data Quality Classification of the data quality (i.e.
incomplete, complete), observed
AD
Data Stored Classification of the kind of data
stored, observed based on the
and 'DH'
AE
Technology Classification of the technology that
are used of the data consumption,
AF
Information Management & All the information captured are
Governance Assets based on the information from
AG
Apply Data Standard? Classification of the existence of data
standard, observed based on the
and 'DH'
AH
Data Polices Classification of the existence of data
policy, observed based on the
and 'DH'
AI
Data Quality Process Classification of the existence of data
quality processes, observed based on
and 'DH'
AJ
Business Metadata Classification of the existence of
capturing business metadata,
AK
Technical Metadata Classification of the existence of
capturing technical metadata,
AL
Operational Metadata Classification of the existence of
capturing operational metadata,
AM
Model Management Classification of the existence data
model management, observed based
and 'DH'
AN
Standard Tool Used Classification of the standard tools
that are used for management of
data, observed based on the
and 'DH'
AO
Data Issue Management Classification of resolving the data
management issue, observed based
and 'DH'
AP
Business Rule Management Classification of the existence of
business rule management, observed
AQ
Data Requirement Given Classification of the existence of data
requirement management, observed
AR
Technology/Tool Classification of the technology that
are used of the data governance,
AS
Customer Systems (Respond to Consumer Requests, Outage Reports, Operate Telephony Systems)
Operatonal Improvement (customer engagement, SAIDI, SAIFI, MAIFI, MTBF, etc.)
Utlity Operatons - Integrated Energy Management
Utlity Operatons - Customer Systems , BS Apps

[CLIENT] Analytics Demand Profile
Creates a More Robust and Modernized Grid

Data Source Characteristcs In Flight Initatve Dependencies Consumers
Modernizing and Transformatve Projects

Build a culture of safety and engagement
Fossil, Fossil Environmental Special View

Regulatory Support for efectve recovery
Architectural Characteristcs Master Domain Characteristcs (1-3 Impact Score, 1=low / (1-3 Impact Score, 1=low / (1-3 Impact Score,
External
Energy Wholesale Commodites (EWC)
Alignment to Business Capabilities (1-5 impact score) Alignment to Key Business Capabilities (1-3 impact score) (1-3 Impact Score, 1=low / 3=high) (1-3 Impact Score, 1=low / 3=high) 3=high) 3=high) 1=low / 3=high)
Innovatve Products and Services
Utlity Operatons - Distributon

This tab is used to capture analytc demand profile
Make Productve Investments
Customer Service Excellence

Descripton: and alignment to business capabilites
Strategic Value Drivers
Business Value Drivers
Physical and Cyber Security
Business Unit Impact
Energy Market Ops / SPO

Regulatory Relatonships
Revenue/margin growth
Earn reasonable returns
Utlity Operatons - Gas

Employee Engagement
Commercial Analytcs
[PROJECT][PROJECT]
Timeliness / Latency
Finance/Accountng
Weighted Sub-Total
Weighted Sub-Total
Weighted Sub-Total
Safety and Security
Grow the business
Backup / Recovery
Legal / Regulatory
Guidance: Breadth of informaton is more valuable than depth of informaton
Customer Facing
Smart Spending
System Network
O&M reducton
Agile & Elastic

Environmental
Measurement
Infrastructure
Management
Supply Chain
Control Rates
Unstructured
Transmission
Power Asset
Self-Service
Availability
Regulatory
Integraton
Structured
Customers
[PROJECT]
[PROJECT]
[PROJECT]
IT, Test BU
[PROJECT]
[PROJECT]
[PROJECT]
[PROJECT]
[PROJECT]
[PROJECT]
Customer
Common
Metering
Weather
Weather
Security
External
Nuclear
Volume
Internal
Quality
Outage
Social
Safety
Audit
Work
Asset
Field
Contributors:
IoT
Total
HR
Portfolio Business Unit Use Case Number Analytics Capabilities - Future DemandPriority Data Readiness Notes Description / Overview of Analytics Use Case High-level Overview of Project ANALYTICAL SORT COLUMN
Can we design a better way to model revenue

incorporatng relevant customer and market
intelligence, and, in turn, improve financial
Corporate Commercial performance for all four stakeholders (owners,
Cognitve Analytcs Analytcs UC-001 N/A Market & Economy Forecasts Picked up by Sales, Load and Revenue Femployees, customers, communites) 3 3 3 1 3 20 3 2 3 3 2 17 3 3 3 3 3 3 22 58 3 2 3 3 3 3 3 3 3 3 2 3 3 2 3 3 3 3
How might we proactvely identfy and respond to
disruptve technologies and end-use trends in the
Corporate Commercial markets we serve and depend on for our four
Cognitve Analytcs Analytcs UC-002 N/A External Force Predictons Picked up by DER use case How might we provide alternatve pricing
stakeholders 3 3 3 3 18 2 2 3 1 10 1 2 1 2 3 2 3 3 20 48.8 3 3 3 2 2 3 2 2 2 2 2 3 1 3 3 3 3
mechanisms / rate structures and influence/afect
Corporate Commercial customer behavior to reduce total system cost (fuel,
Cognitve Analytcs Analytcs UC-003 N/A Rates Picked up by Rates AMI use case O&M, purchased power) 3 3 2 2 3 20 3 3 2 2 2 2 3 22 3 3 3 3 3 3 2 24 65.6 3 2 3 2 3 3 3 3 3 2 2 2 1 3 3 2 3 1 2 3 3 3 3 3 3
How might we collect, organize, and analyze market
Corporate Commercial X and commodity data to better understand and
Cognitve Analytcs Analytcs UC-004 Markets & Commodites Forecasts Medium predict industry trends and impact on our customers 3 3 3 1 3 1 3 1 27 3 3 1 3 2 3 1 21 3 3 3 3 3 3 22 69.4 3 3 2 3 3 3 1 3 1 3
Corporate Commercial reduce costs
How might we collect, validate andand increase reliability
use data
Predictve Analytcs Analytcs UC-005 N/A Asset Efficiency Picked up by Distributon/STI for planningcommodity,
(customer, and operatons industrial, market, financial) 3 3 3 2 2 2 3 3 32 3 3 1 1 1 3 3 3 1 1 26 3 3 2 3 3 17 74.3 3 1 2 1 3 3 3 3 3 3 1 3 3 3 1 3 2 3 3 2 3 3 3 3
to better understand individual customer segments
for enhanced customer experience (reliability, ETR
Corporate Commercial A portfolio ofETR
interacton, weather normalizaton
communicaton, models
informing
Data Lake / Data Mart Analytcs UC-006 Customer and Product Medium (including
customers,by billingof
control cycle,
energy total system sales, rate
usage) 1 2 2 3 3 3 2 24 2 3 2 3 2 2 18 3 3 2 3 3 17 59 3 3 2 3 3 3 3 3 3 3 3 3 3 2 3 1 3 3 3 3 3 3 3 2
classes, demographic and regional models) which
appropriately estmate weather impacts separate
from energy efficiency, to build confidence around
X and explain weather normalized sales results to
Revenue, Sales and Load Improve
investors,accuracy
for use in and transparency
rate cases/regulatory of thefilings,
forecastand
Stochastc Optmizaton Forecastng UC-007 Weather Normalizaton of Sales High UDW, SAP & Weather - High by using more
to improve inputgranular
to sales data (e.g., see examples)and
forecasts 3 2 2 2 3 18 2 3 6.5 1 3 3 3 3 3 3 23 47.3 3 2 1 3 3 3 3 3 3 3 3 3 3 3 3 2 3 2 3
to explain the forecast/trends, to minimize risk, to
improve overall decision making, to respond to
X SAP, Energy efficiency data is the questons/requests, to inform future products and
Revenue, Sales and Load Load Forecastng Using More Granular challenge, Solar data, AMI in future - services, to help build a foundaton for using granular
Predictve Analytcs Forecastng UC-008 Data Medium Medium data prior
Access to getting
to more AMIDER (including energy
granular 3 3 3 3 18 2 2 3 2 12 3 3 3 3 3 1 1 3 3 28 57.3 3 3 3 3 3 3 3 3 2
efficiency) savings projectons, usage, spending data
Revenue, Sales and Load in order to explicitly measure how much DER is
Data Lake / Data Mart Forecastng UC-009 DER Modeling Medium Need EE data, more coordinaton acros reducing / impactng sales and load 2 2 2 2 2 1 2 3 24 2 2 2 7.8 3 3 3 3 2 3 2 2 2 28 59.4 3 2 3 3 3 2 3 3 2 3 2 3 3 3 3 2 2 3 2 3
A short-term forecastng process that is more robust
so that decisions can be made about sales trajectory
Revenue, Sales and Load based Management
Audit on near-term can eventseasilysuch as weather,
compare department
Predictve Analytcs Forecastng UC-010 Near Term Sales Forecastng Model industrial customers'
performance objectvelyscheduled
to key KPIs maintenance
and KRIs to 3 3 2 3 17 3 3.9 2 2 3 8.4 28.8 3 1 1 2 2 3 3 3 3 3 3 3 3 3 3 2 3 3
Descriptive iteratvely drive the audit plan, increasing high risk
Analytics X area coverage by 25% and decrease cycle tme by
(Prescrptive?) Audit UC-011 Audit Planning and Ongoing Prioritzaton Low High number of systems - low readiness50%An auditor can systematcally and proactvely identfy 3 3 9 1 1 1 1 1 3 1 1 1 1 16 1 1 1 1 1 1 3 2 2 2 2 1 22 46.2 3 1 2 2 3 3 3 3 3 3 3 3 3 2 3 3 3 3 3 3 3 3 3 1 3 3 3
fraudulent patterns (red flags) to reduce
X investgatons by 10% and increase financial recovery
Predictve Analytcs Audit UC-012 Fraud Detecton High IKW, Asset suites - Achievable. Closer toby 25% 3 3 9 3 3 3 3 16 1 1 1 1 1 1 1 1 1 1 3 2 2 2 2 1 26 51 3 1 3 1 3 3 2 2 2 2 2 2 2 3 3 3 2 3 3 2
Anomaly detecton for physical and digital access
logs, to identfy and ultmately predict suspicious
behavior indicatve of fraud, theft, ethics violatons,
Predictve Analytcs Audit UC-013 Log Analysis Medium Might need to int with Splunk An auditor canissues,
management predict andtrends in various
upcoming HR violatons
retrement 3 3 9 2 1 3 1 9.1 1 3 3 1 1 1 1 1 1 3 2 2 1 2 1 29 46.9 3 1 3 1 3 3 2 2 2 2 2 2 2 3 3 2 3 2 3 3 2
(ethics cases, short term disability trends,
absenteeism, ethics cases, OHSA incidents,
retrement/succession planning) to more quickly
Predictve Analytcs Audit UC-014 HR / Proactve Behavior Analysis Medium Pull in ethics line stuf develop mitgaton plans and take correctve acton 3 2 7.5 2 1 1 3 3 13 3 3 3 3 1 1 1 1 1 1 3 3 1 1 2 1 35 55.3 3 1 3 3 3 2 3 3 2 3 3 3 3 2 3 3 2
Automated anomaly detecton during SOX
Predictve Analytcs Audit UC-015 SOX Automated Anomaly Detecton Anomaly
compliance detecton
processon customer service rep actons
executon 3 3 2 12 3 3 7.8 3 1 1 1 1 1 1 3 1 1 1 1 1 20 40.2 3 1 3 3 3 3 3 3 3 3 3 3 3
to identfy and prevent situatons in which customers
have been ofered exceptons, refunds, cancel/rebills
Descriptve Analytcs Audit UC-016 Revenue [CLIENT] business unit customers (contract
against policy 3 3 9 3 3 7.8 2 1 3 3 1 12 28.8 3 3 3 2 3 3 3 3 3 1 3 2 3 3 3 3 3 1 3
managers, executves, and buyers), can access a 360
degree view of enterprise-wide suppliers (including
analytcs based performance scorecards, upstream
X impact, risk (litgaton, safety, financial),
cybersecurity) to decrease enterprise wide supply
cost by 1/2 - 1X, decrease cycle tme by 30%, and
Data Lake / Data Mart Supply Chain UC-017 Supplier Optmizaton Low Difficult - too many systems to touch - [CLIENT]
decreasebusiness
supplier unitcompliance
customers issueshavebyautomated
50% or more 2 3 3 2 15 3 2 3 3 3 3 2 25 3 3 3 3 3 1 1 1 1 1 1 1 1 2 3 2 1 37 76.9 3 3 3 2 2 3 2 3 3 3 2 2 3 3 3 3 3 3 3 2 2 3 3
and optmized inventory levels to reduce overhead
Descriptive and cycle tme, improve project completon tme,
Analytics Inventory Optmizaton and Predictve X IKW, Asset suites - Validate data and increase ability to purchase inventory at optmal
(Prescrptive?) Supply Chain UC-018 Ordering Medium availability - Medium prices through market trend analysis 2 3 2 2 14 3 3 1 3 3 17 2 2 2 2 1 1 1 1 1 1 1 1 1 3 2 2 29 59.2 3 3 3 3 3 3 3 3 2 2 2 3 2 3 3 3 3 1 2 2 3 3 3 2 3
Business units can optmize warehouse operatons
Leverage
and a consolidated
prevent / integrated project
inventory obsolescence, minimizing
Descriptve Analytcs Supply Chain UC-019 Obsolescence Avoidance management
overhead, operatons, and inventory cost project
system to more easily predict 3 3 3 3 16 3 3 3 2 3 3 3 3 2 2 2 3 2 3 3 3 2 2 3 3 3 3 3
1 3 6 3 3 7.2 28.8
supply needs, to prescribe optmal sourcing
methods, and to identfy underperforming projects,
resources, and processes, in order to optmize bids,
manage costs, reduce scheduling delays and
Stochastc Optmizaton Supply Chain UC-020 Project Management Low Loads of data to pull in maximize
Credit andresource
Collectons utlizaton
can analyze customer behavior 1 3 1 1 3 14 3 2 3 3 14 2 2 2 2 1 1 1 1 1 1 1 1 1 3 1 1 26 54.2 3 3 3 3 3 3 3 3 2 1 2 3 3 3 3 1 1 1 1 1 3 3
to predict delinquency to reduce revenue losses.
Predictons identfy both for customers mostly likely
X to pay to avoid delinquency, and customers most
Predictve Analytcs Credit & Collectons and MUC-021 Revenue at Risk - Payment Delinquency High SAP Customer data - Close to ready likely to pay to exit delinquency 3 3 3 14 3 3 3 3 16 1 1 1 1 1 1 7.2 36.3 3 1 2 2 3 3 3 2 3 1 3 2 3 1 3 3 2 3 2 3
Credit and Collectons can analyze customer
payment behavior to predict and ofer the
Revenue at Risk - Personalized Payment X personalized payment plans that will reduce revenue
Predictve Analytcs Credit & Collectons and MUC-022 Arrangement High SAP Customer data - Close to ready. CheckCredit anddebt
loss / bad Collectons can analyze customers' usage, 3 3 3 14 3 3 3 3 16 1 1 1 1 1 1 7.2 36.3 3 3 1 3 3 1 3 3 1 3 1 3 2 3 3 3 2 3 3 3
Descriptive Business
payment services
history, andhas 360
externaldegree viewtoofoptmize
factors meters
Analytics X (including [PROJECT]
deposit amounts and regulatory
(within accurate outage constraints) to
(Prescrptive?) Credit & Collectons and MUC-023 Revenue at Risk - Deposit Coverage Medium SAP, outside systems to be tapped. Me informaton)
reduce revenue thatloss
allows
/ badcross-validaton
debt to reduce 3 3 3 14 3 3 3 3 16 1 1 1 1 1 1 7.2 36.3 3 2 2 3 3 3 1 3 2 3 3 3 2 3 3
estmatons, improve rate analysis and work order
accuracy, reduce field trips (enhance meter
Data Lake / Data Mart Credit & Collectons and MUC-024 Meter 360 - [PROJECT]/geospatal operatons) in advance of AMI deployment 1 3 2 1 11 2 2 2 2 1 12 1 2 2 2 2 11 33 3 2 3 2 2 3 3 3 2 3 3 2 3 3 3 3 3 3 1 3
Identficaton of incorrect meter status records,
MRO can identfy
integrated and resolve
with outage incorrecttoand/or
management, decrease
missing
the numbercontact informaton
of truck rolls forfor customers
replacing withthat
meters
Predictve Analytcs Credit & Collectons and MUC-025 Meter 360 - Outage difficult-to-access
are not providing reads meters forinaadvance
known reasonof AMI to 1 3 1 1 9 2 2 2 2 1 12 1 1 1 3.6 24.3 3 3 1 3 3 3 3 3 3 3 3 2 3 3 2 2 3
decrease the number of failed AMI installatons and
AMI Readiness - Customer Contact X Data not immediately available. Low incorporate access challenges into deployment
Data Quality & Curaton Credit & Collectons and MUC-026 Informaton and Access Challenges Medium data quality. Low readiness planning 3 3 3 3 18 3 3 3 3 16 3 3 7.2 40.8 3 3 3 2 3 3 2
Descriptive MRO needs a way to understand 'pick-a-date'
Analytics X
AMI Readiness - Pick a Bill Date and customers so that we can reroute (if needed) before
(Prescrptive?) Credit & Collectons and MUC-027 Reroutng High SAP - Close to readiness AMI 1 3 1 3 12 2 1 2 3 10 1 3 2 7.2 29.6 3 3 3 3 3 3 3 3 3 3 2 2
No use/low use meters are identfied and replaced in
advance of AMI deployment to level-set customer
expectatons around billing and to optmize truck
Descriptive X rolls to no use/low use locatons in the interim
Analytics AMI Readiness - no use/low use anomaly Data exists, medium because need
(Prescrptive?) Credit & Collectons and MUC-028 detecton Medium more granular weather data 1 3 1 3 12 2 2 2 2 10 1 3 3 8.4 30.8 3 3 3 3 3 3 3 3 3 3 3 2 2
Descriptive
MRO needs a way to map out meter reading actvity
Analytics AMI Readiness - Prioritzaton of Credit & X Depends on AMI Deployment plan by cycle so that a plan can be developed ahead of
(Prescrptive?) Credit & Collectons and MUC-029 Collectons Work Low plus the billing cycle - low Business rule optmizaton to detect reading 3 3 3 14 3 3 2 3 3 18 1 1 1 1 1 1 7.2 38.9 3 3 3 3 3 3 3 3 2 2
AMI helping
Excepton
exceptons levelize
identficaton
and thewithin
to minimize work thethroughout
manually
number of the
badmonth
created bills
as minimize
to AMI is that
readings deployed
the
arenumberto maximize
released offor the benefits
badbilling,
readings thatfrom
are
consequently
Descriptve Analytcs Credit & Collectons and MUC-030 Cancel/Rebill - Residental deployment
released
improvingfor billing, consequently
customer satsfacton improving 2 3 2 3 13 3 3 2 3 3 3 3 3 3 3 3
1 3 1 3 12 3 3 3 11 35.8
customer satsfacton. Identficaton of opportunites
to develop an accrual process that enables
Descriptve Analytcs Credit & Collectons and MUC-031 Cancel/Rebill - CG&I Accrual Optmizaton estmaton
Fleet of current
workforce month revenue
management can use safety data, 1 3 1 1 3 14 2 3 2 3 2 16 3 3 3 11 39.9 3 3 3 3 3 3 3 2
telemetry data, hours tracking data, job
Identficaton and
classificaton, of incorrect multpliers scorecard
other productvity for CG&I
X customers in order to ensure accurate recording of
inputs to better
Identficaton of identfy
transformerand recognize
rated meterstop that are
Descriptve Analytcs Credit & Collectons and MUC-032 Revenue
RevenueAssurance
Assurance--CG&I
Transformer Rated Medium Need granular weather data - Medium revenue
performers, and to identfy
incorrectly recording consumptonand interfere in
to ensure 1 3 1 3 12 3 3 7.8 3 3 3 11 30.6 3 3 2 3 3 3 3 3 3 3 3 3 3 3
Descriptve Analytcs Credit & Collectons and MUC-033 Meters X Medium Need granular weather data - Medium situatons where employees
accurate recording of revenue are demonstratng 1 3 1 3 1 14 3 3 3 12 2 3 3 3 13 38.4 3 3 2 3 3 3 3 3 3 3 3 3 3 3
unsafe or costly behaviors (e.g., unsafe driving,
illegitmate vehicle requests, extreme vehicle idle
Predictve Analytcs Fleet Management UC-034 Fleet Workforce Productvity and Safety tme, managers
Fleet etc.) can access vehicle data (including 1 1 3 1 9 3 1 3 3 3 17 1 3 4.8 30.7 3 3 3 3 3 3 3 2 3 2 3 3 2 3 3 3 3 3 2 3 3 2 3
leasing history, maintenance history, vehicle type
Maintenance records, drug testng standards)
Fleet and driver
managers data (including
can identfy which fleet drug testng
assets are
X history - Challenge - High number of top
history, licensing,
candidates forperformance
replacementhistory)based on to usage,
improve
DOT Regulatory Compliance / 360 systems - missing data - Low compliance
mileage, andand prepare
historical andforprojected
potental repair
Department
cost of
Data Lake / Data Mart Fleet Management UC-035 Vehicle View / 360 Driver View Low readiness Transportaton
data. Fleet managersaudit can also leverage that data to 2 1 3 9 2 2 3 3 13 3 3 7.2 29.2 3 3 3 3 3 3 3 2 3 2 3 3 2 3 3 3 3 3 2 3 3 2 3
make informed purchasing decisions around "fit for
purpose" assets (buy and upfit vs. buy as-needed)
Asset Replacement / Purchase X and asset fuel type (diesel vs. gasoline vs. natural
Predictve Analytcs Fleet Management UC-036 Optmizaton Medium Medium gas) 1 3 2 1 1 12 3 1 2 3 3 16 1 3 3 8.4 36 3 3 3 3 3 2 2 3 3 3 3 3 3 2 3 3 2 3
Fleet Management can access historical leasing data,
current leasing contracts, and interest rate trends to
inform future lease negotatons and current lease
X renegotatons, minimizing cost and maximizing
opportunites to meet "green fleet" environmental
Predictve Analytcs Fleet Management UC-037 Vehicle Leasing Trends / Optmizaton Low Missing data - Low readiness goals
Optmizaton of vehicle driving tme, idle tme, down 1 3 2 1 1 12 3 1 3 3 3 17 1 3 3 8.4 37.3 3 3 3 3 3 2 2 3 3 3 3 3 3 3 2 3 3 2 3
Fleet
tme forManagement
maintenance, canandleverage
service data on miles
center locaton
driven,
Improved
selecton hours
IVR
to utlized,
root cause
minimize anddetecton
costs, maintenance
maximize history
andvalue
predictve to
of fleet
X predict and increase
messaging. proactvely
Customer resolve
Service potental
Representatves
assets, and fleet productvity at tmescan of
Descriptve Analytcs Fleet Management UC-038 Vehicle Utlizaton Optmizaton Medium Low readiness maintenance
easily understand
high demand issues thebefore they happen,
root cause to catch
of a customer call 1 1 3 3 1 3 3 13 3 3.6 19.6 3 3 3 3 3 2 2 3 3 3 3 3 3 2 3 3 2
repeat
and knowmaintenance
the "next best orders on the
ofer" for same fleet assets,
that individual
Predictve / Preventatve Fleet and to prioritze
customer fleet repairs
by accessing a robust to repository
decrease of
Predictve Analytcs Fleet Management UC-039 Maintenance maintenance
customer datacost and down
including tme
history ofof vehicles and
outbound 1 3 1 1 9 3 1 2 3 3 16 1 3 4.8 29.4 3 3 3 3 3 2 2 3 3 3 3 3 3 2 3 3 2
inbound communicaton, geographic / jurisdicton
X data, external data (weather, economic, etc.),
Predictve Analytcs Customer 360 Omnichannel View + Call frequent caller identficaton, call keyword analysis,
(Prescrptve?) Customer Operatons UC-040 Root Cause Analysis Low CDI - Low readiness Customer
and other Operatons
customer data leadership
points. can forecast call 1 2 2 1 3 14 3 2 3 3 14 3 3 1 8.4 36.2 3 3 3 2 3 3 2 3 3 3 2 3 3 3 3 3 3 3 2 3 3 3
volumes and associated operatng costs based on
changes in variables including new product and
service oferings, outbound marketng campaigns,
X weather (specifically abnormal temperature
fluctuaton and outages), and individual outbound
Call Volume Forecastng + "What-If Cost messaging to respond to ad-hoc requests from
Predictve Analytcs Customer Operatons UC-041 Analysis" Medium CDI Medium readiness senior leadership, optmize hiring, and reduce costs 1 2 3 9 3 1 3 3 13 3 3 2 9.6 31.6 3 3 3 2 3 3 2 3 3 3 2 3 3 3 3 3 3 3 2 2 3 3 3
Tracking of agent performance, including correct
transactons and resolutons, errors, productvity,
and text recording analysis, to identfy and train low
Customer Service Agent Performance - performing agents, and to identfy and reward high
Descriptve Analytcs Customer Operatons UC-042 Rewards and Discipline performing agents 1 1 3 1 3 14 2 1 3 3 3 16 3 3 3 1 12 41.1 3 3 3 2 3 3 2 3 3 3 3
More granular insight and recommendatons on how

Customer Ops Outsource Spending / More accurate
to optmize calland more
center tmely ETR
outsource values to
spending produced
Stochastc Optmizaton Customer Operatons UC-043 Vendor Management Optmizaton and communicated
maximize productvity to customers following
while minimizing an outage
costs 1 3 1 2 11 3 1 3 3 13 1 3 2 7.2 30.7 3 1 2 2 3 2 2 3 3 2
so that call volume around unmet expectatons is
Predictive Analytics ETR Estmaton and Communicaton X High reduced. Machine learning functon that improves
(Prescrptive?) Customer Operatons UC-044 Improvement Data exists, High ETR estmaton calculaton over tme 1 3 6 2 1 2 3 10 3 3 7.2 23.6 3 3 1 2 3 3 2 3 2 3 3 3 3 3 3 3 3 3 3 2 3 3 3
More granular insight and recommendatons on how

to optmize internal call center spending to maximize
Stochastc Optmizaton Customer Operatons UC-045 Customer Ops ESI Charges Database productvity while minimizing costs 1 3 6 3 1 3 3 13 1 3 2 7.2 26.2 3 1 2 2 3 2 2 3 3 2
Transmission develops a score for major assets based
Predictve Analytcs Transmission UC-046 Asset Health/Risk Scores Correlate
on risk to costs to asset
customer health
(Scope scores; by
is covered useSTI
costs to
project) 3 3 3 14 2 3 3 1 3 16 3 1 1 6 35.1 3 3 3 2 2 3 3 2 3 3 3 3 3 3 3 3
Descriptive inform repair/replace decisions and maintenance
Analytics Integratng Financial Data with X prioritzaton by connectng toLightning Locaton
Automates
TARP ratngsFaultwithAnalysis and
levels ofdata
confidence for amount of
(Prescrptive?) Transmission UC-047 Transmission Asset Management Medium Tied to STI - Medium engineering/operatonal
System 1 3 3 11 3 3 3 3 16 3 1 4.8 30.9 3 3 3 2 2 3 3 2 3 3 3 3 3 3 3 3
current (FALLS) analyses to
that Transmission pinpoint
lines locatons
can carry. of
There
outages andbedecrease
ratngs will based onresponse
ambienttmes; predictng
temperature and
Predictve Analytcs Transmission UC-048 Predictve TARP Ratngs outages
sun (wind through mapping historical outages and
is too variable) 0 0 0 0 3 3 3 1 3 3 2 3 3 3 3 3 3 3 3 3 3
preventng outages hardening/replacing especially
X susceptble assets; lightning strike and line fault
Predictve Analytcs Transmission UC-049 Transmission Outage Response Medium Multple systems - medium analysis 3 3 3 14 2 3 3 3 14 3 3 3 11 38.6 3 2 2 1 3 3 2 3 3 3 3 3 3 2 3 3 1 1 3 3
Updatng the algorithm that uses storm data to
predict the equipment damages (ex. Number of
poles down) during a storm event to better prepare
Predictve Analytcs Transmission UC-050 Transmission Storm Readiness for response 3 3 3 14 2 3 3 3 14 3 3 3 11 38.6 3 2 2 1 3 3 2 3 3 3 3 3 3 3 3 1 1 2
Transmission has moved from tme-scheduled
Transmission Conditon-Based maintenance to conditon-based maintenance for
Predictve Analytcs Transmission UC-051 Maintenance some asset classes (Scope is covered by STI project) 3 3 3 14 2 3 3 1 3 16 3 1 1 6 35.1
Use analytcs to predict needs of high cost
transmission assets and shorten lead tmes on
Predictve Analytcs Transmission UC-052 Transmission Inventory Optmizaton Medium Follow up on coding delivery 2 3 2 2 14 3 3 1 3 3 17 1 3 1 1 1 1 1 1 1 3 2 2 22 52 3 3 3 2 3 3 3 2 3 1
Attriton of baseload contractors to EPC
subcontractors; optmizaton of mix of in-house and
Distributon [PROJECT]can
contract workers for variousidentfy internal
functons; reducton in
challenges
response tmesand areas
basedofongreatest
manpoweropportunity
in an area;(i.e.
Stochastc Optmizaton Transmission UC-053 Transmission Workforce Optmizaton [PROJECT]) with sufficiently reliable operatons data
increased productvity 3 1 3 11 3 2 3 2 3 17 3 3 7.2 34.6 3 2 3 3 3 2 3 2 3 2
to make acan
[CLIENT] cost and benefit
predict potentalbusiness case outages
near-term for securing
Distributon Data Maintenance X fundingonfor
based strategic
machine and technical
learning improvement
of system data, historical
Data Lake / Data Mart Distributon / [PROJECT]/ UC-054 Foundaton and Strategic Valuaton Low Data quality issues - low projects,informaton,
outage and to reduce overallpatterns,
weather businessetc.
unittorisk 3 3 3 3 18 3 3 1 3 13 3 1 1 1 7.2 38.2 3 3 2 2 2 3 3 2 3 3 3 2 2 3 3 3 3 3 3 3 3
improve ETR, improve customer satsfacton, and
decrease restoraton costs. This use case will be
Distributon Outage and Restoraton enhanced by AMI meter "last gasp" signals when the
Predictve Analytcs Distributon / [PROJECT]/ UC-055 Forecastng (Proactve) data becomes available 3 3 3 14 2 3 3 3 14 3 3 3 11 38.6 3 3 2 2 2 3 3 2 3 3 3 3 2 3 3 3 3 3 3 3 3
[CLIENT] can analyze the extent, duraton, and
X sources of grid outages along with crew placement
Distributon Outage and Restoraton to optmize the customer restoraton process in near
Stochastc Optmizaton Distributon / [PROJECT]/ UC-056 Situatonal Intelligence (Reactve) Low Multple systems - Low Distributon
real-tme and[PROJECT]can
minimize ETRproactvely manage load 3 3 3 14 2 3 3 3 14 3 3 3 11 38.6 3 3 2 2 2 3 3 2 3 3 3 3 2 3 3 3 3 3 3 3 3
and minimize outage risk via real tme analysis of
System Planning for Load Management environmental factors, equipment factors, and load
Predictve Analytcs Distributon / [PROJECT]/ UC-057 and Circuit Model profiles 1 3 3 11 2 3 3 3 3 18 3 3 3 11 39.5 3 3 2 2 2 3 3 2 3 3 3 3 2 3 3 3 3 3 3 3 3
As part of its grid modernizaton eforts, [CLIENT] can
identfy and proactvely address critcal areas to
Stochastc Optmizaton Distributon / [PROJECT]/ UC-058 Switching Routne Analytcs Damage
minimizePreventon
switching riskscan proactvely identfy 0 0 0 0 3 3 2 2 2 3 3 2 3 3 3 2 3 3 3 3 3 3 3
distributon assets at risk from dig actvity and
X Dependencies on AMI & Grid Mod - Distributon
increase accuracy[PROJECT]can
of locaton predict and proactvely
to minimize uncertainty
Predictve Analytcs Distributon / [PROJECT]/ UC-059 Damage Preventon Optmizaton Low Data quality issues - low address
of areas asset
at riskmaintenance
and to minimize issues to reduce
number cost,rolls
of truck 3 3 3 14 2 3 3 1 3 16 3 1 1 6 35.1 3 3 2 2 2 3 3 2 3 3 3 2 3 3 3 3 3 3 3
Distributon Asset Predictve including by leveraging asset attribute data
Maintenance and Field Data Collecton / X Maintenance data ted to asset collected / validated by field operatons, lightening
Predictve Analytcs Distributon / [PROJECT]/ UC-060 Enablement Low attributes - Medium/Low Distributon
strike analysis can leverage
data, etc. enhanced inventory 3 3 3 14 2 3 3 1 3 16 3 1 1 6 35.1 3 3 2 2 2 3 3 2 3 3 3 3 2 3 3 3 3 3 3 3 3
tracking and situatonal
Customer Experience canawareness
integrate to minimize
financial data
Inventory Optmizaton and Predictve Vegetaton
inventory Management
overhead can
costtoand forecast
tme vegetaton
tobusiness
fulfill, and to
with
risks customer
to assets insights
leveraging capitalize
data on current and revenue
Descriptve Analytcs Distributon / [PROJECT]/ UC-061 Ordering improveand
growth work order
cost / project
saving completon
opportunites. tmefuture
Customer 2 3 2 2 14 3 3 1 3 3 17 1 1 1 3 1 1 1 1 1 1 3 2 2 23 53.2 3 3 3 2 3 3 2 3 3 3 2 3 3 3 3 3
environmental conditons, tree mortality / health,
Vegetaton Management - Trimming X Additonal data required from USGS - Experience
tree density,can andimprove
speciesreliability
to optmize of demographic
trimming cycles
Cognitve Analytcs Distributon / [PROJECT]/ UC-062 Forecastng and Optmizaton Medium Medium and
and operatonal
minimize cost data to increase reliability of inputs 2 3 3 3 14 3 2 3 3 3 2 3 3 3 3 3 3 2 3 3 2 3 3 3 3 3 3 3
3 3 3 14 3 3 3 11 38.6
Vegetaton Management - to propensity
Vegetaton models, predict
Management product adopton
can segment routes andand
Vendor/Contractor Optmizaton and X Additonal data required from USGS - increase
trimmingROI. cyclesCustomer
in orderExperience
to optmizecan predict
vendor and
selecton
Predictve Analytcs Distributon / [PROJECT]/ UC-063 Management Medium Medium track impacts
and truck typeofinprogram
a way that changes and new
minimizes cost products 3 3 3 14 2 3 3 10 3 2 6 29.9 3 2 3 3 2 3 3 3 3 3 3 3 3 3 3 3
Tradeof Analysis - Customer Value on brand image and overall satsfacton with
Mapping to Resource Usage, Marketng X [CLIENT] so that [CLIENT] can make informed
Cognitve Analytcs Customer Experience UC-064 Efectveness, and Program Design Medium CDI Medium readiness decisions 3 3 3 3 3 2 26 3 3 3 3 3 1 21 3 3 1 8.4 54.7 3 2 3 3 3 2 3 3 3 3 3 3 3 3
Customer Experience can create a complete profile
of their customers through the integraton and
analysis of data to satsfy the needs of the greatest
X number of customers. Customer Experience can
track and analyze customer segmentaton strategies
Customer 360 Omnichannel View and and efectveness over tme to optmize customer
Descriptve Analytcs Customer Experience UC-065 Customer Segmentaton Medium CDI Medium readiness segments for the greatest impact. 3 3 3 3 3 3 2 30 3 3 3 3 16 3 3 7.2 52.8 3 2 3 3 3 2 3 3 3 3 3 3 3 3
Customer Experience can track and analyze payment
behaviors vs. credit / Dunning policy in order to
make recommendatons to improve Dunning so that
Predictve Analytcs Customer Experience UC-066 Credit & Collectons Dunning Medium Stored in SAP; functon of CDI project it incorporates global business impact 3 3 3 3 3 2 26 3 3 3 3 3 20 3 3 7.2 52.2 3 2 3 3 3 2 3 3 3 3 3 3 3 3
Customer Experience can prevent communicatons
overload/saturaton and optmize outbound
Customer Experience
communicatons will customer
to meet be a hub for all customer
expectatons,
data to ensure
improve open and consistency
conversion andrates,
to streamline
and maximize
Data Lake / Data Mart Customer Experience UC-067 Customer Data Management processes
ROI of marketng investment. Customer Experience 1 3 6 2 3 3 10 3 3 7.2 23.6 3 2 3 3 3 2 3 3 3 3 3 3 3 3
can accurately track customer calls and maintain up-
to-date contact informaton in order to ensure that
Inbound Call Management and DCI requires change management for they reach customers how and when they would like
Data Quality & Curaton Customer Experience UC-068 Outbound Communicatons Optmizaton Low customer comms with adopton to be reached. 3 3 3 3 2 21 3 3 3 3 3 20 3 3 7.2 47.7 3 2 3 3 3 2 3 3 3 3 3 3 3 3
Ability to access employee PII, work history,
Identfy
performancesuccess and failure
history, reportng of individual
structure,leaders
job role,by
Compensaton / Human analyzing leadership
training history, practces, organizatonal
compensaton, etc. to more easily health
Resources / Talent surveys, exit interviews,
and efectvely respond to attriton data,
requests, and tme and
saving
Data Lake / Data Mart Management UC-069 Employee/Department 360 Low Multple systems performance
improving data review data (including both content
accuracy 3 3 9 3 3 3 3 16 1 1 1 1 1 1 1 3 1 1 1 1 17 41.4 3 3 3 3 3 3 3 3 3 3 3 3 3 3
Compensaton / Human Tied to [PROJECT] - Mulitple systems - and sign-of process) in order to intervene and
Resources / Talent Supervisor 360 and Leadership X unstructured data, no governance - Proactvely
mitgate attritonmonitor caused by poorly
and identfy performing
risk areas in
Predictve Analytcs Management UC-070 Efectveness Low low mangers employee role categories. Identfy and
diferent 3 3 1 11 2 1 3 7.8 2 2 2 2 2 1 1 1 1 1 1 1 3 1 1 1 1 29 47.1 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
mitgate risk around hard to fill and “key roles”
Compensaton / Human (those requiring
Identfy candidates significant knowledge
at high risk of leavingtransfer and
[CLIENT]
Resources / Talent on the
and thejob training),
expected then revise
tmeline recruitment
for separaton, and
partcularly
Descriptve Analytcs Management UC-071 Workforce Planning Medium Dependant on [PROJECT] retenton
for retrementstrategy accordingly
eligible employees and subject matter 3 4.5 3 3 3 12 3 3 3 3 3 1 1 1 1 1 1 1 3 1 1 1 1 35 51 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
experts seen as a “single point of failure” should they
Compensaton / Human leave the company, in order to proactvely intervene
Resources / Talent X Already a model in place for the first Establish
and craft an enterprise-wide
efectve definitonand
retenton packages of “top
strategies
Predictve Analytcs Management UC-072 Predictve Attriton and Retenton Medium part (retrement piece). Low performer,”
based on market then data
leverage analytcs
to prevent to mine and
separaton 3 4.5 3 3 3 12 3 3 3 3 3 1 1 1 1 1 1 1 3 1 1 1 1 35 51 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
identfy top performing employees who meet the
established criteria but have not been otherwise
acknowledged, in order to improve succession
Compensaton / Human X Data is already in success factors. planning, employee engagement, and employee
Resources / Talent Getting data out of it is difficult. We development, and to decrease enterprise risk of top
Descriptve Analytcs Management UC-073 High Performer Identficaton Medium have to define top performer - Low performer attriton 3 3 9 3 3 3 12 3 3 3 3 3 1 1 1 1 1 1 1 3 1 1 1 1 35 55.5 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
Leverage employee work history, skills inventory,
succession planning, and historical success of
Compensaton / Human internal individuals filling the same job role to
Resources / Talent Internal Candidate Matching for Open identfy and evaluate top internal candidates when
Descriptve Analytcs Management UC-074 Positons Medium Dependant on [PROJECT] positons
Ability become
to better availableequity, base pay and
antcipate 3 3 9 3 3 3 3 16 3 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 25 49.8 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
Compensaton / Human short-term incentve needs to forecast
Resources / Talent Compensaton Rato Distributon & X Data already exists. Dependent on comprehensive
Optmize costs and
the tradeof impacts
between acrossattriton
possible the and
Predictve Analytcs Management UC-075 Forecastng High [PROJECT] but stll high organizaton
ability to fill the positon when crafting 1 3 3 3 2 3 23 2 3 3 3 14 3 3 3 3 3 1 1 1 1 1 2 1 3 1 1 2 1 37 74 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
Compensaton / Human compensaton and benefits packages, especially in
Resources / Talent hard-to-fill
More positons
efectvely utlizeand when employee
existng consideringsurveyhiring
Descriptve Analytcs Management UC-076 Recruitment and Retenton Optmizaton Medium former to
results employees as contractors
gauge sentment and craft strategies to 3 3 9 3 3 3 12 3 3 3 3 3 1 1 1 1 1 1 1 3 1 1 1 1 35 55.5 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
Compensaton / Human increase engagement; mine social media informaton
Resources / Talent Looking at loads of diferent data; to monitor
Use analytcs [CLIENT]’s
to forecastexternal reputaton
quarterly among to
claims spending
Cognitve Analytcs Management UC-077 Employee Engagement Low unaccessible current
avoid and potental
unexpected costsfuture employees
at year-end due to 3 3 9 3 3 7.8 3 3 3 3 3 1 1 1 1 1 1 1 3 1 1 1 1 35 51.6 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
emergency events; ability to provide guidance to
Compensaton / Human employees on how to optmize benefits selectons
Resources / Talent based on personal demographics to increase savings
Predictve Analytcs Management UC-078 Benefits Optmizaton Low Multple systems; HIPA challenges for both [CLIENT] and employees 1 3 1 7.5 3 3 3 1 3 17 1 1 1 1 1 1 1 3 1 1 2 1 18 42.4 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
Compensaton / Human X Ability to pull together multple sources of employee

Resources / Talent Data already exists. Dependent on data to identfy drivers of internal movement in
Descriptve Analytcs Management UC-079 Internal Churn Predicton Medium [PROJECT] but stll high order to better
Optmize designfor
the process employee programs
identfying large variances 3 4.5 3 3 3 12 3 1 1 1 1 1 1 1 1 1 1 1 3 1 1 1 1 25 41.4 3 2 3 3 3 3 3 3 3 3 3 2 3 3 3
in usage and/or customer not being billed, alert
Automate Anomaly Detecton for Large billing to explain variance in order to increase tme
Descriptve Analytcs Accountng UC-080 C&I savings for [CLIENT] 1 2 2 7.5 2 1 3.9 1 1 2.4 13.8 2 3 2 3 3 3 3 3
Remove large C&I customers from unbilled accrual
Large C&I Accrual Estmaton X group and accrue at the bill level to increase
Descriptve Analytcs Accountng UC-081 Improvement High Billing exists - High accuracy of unbilled accrual 1 2 2 7.5 2 2 1 6.5 1 1 2.4 16.4 3 2 3 3 3 3 3
Calculate savings from MISO based on heat rate,
admin cost, and other factors internally to reduce
Descriptve Analytcs Accountng UC-082 Calculate MISO Savings Internally cost analytcs to determine a rule-based optmizaton
Use 1 1 2 6 3 2 6.5 1 2 3.6 16.1 3 3 2 3 3 3 3
process to determine percentage of gas bought
Descriptve Analytcs Energy Market X Load forecast - PRT, Tesla, Dispatch month ahead versus day ahead, optmizing
(Prescrptve?) Operatons / SPO UC-083 Gas Purchase Optmizaton High model - High regulatory prudence 1 3 3 1 3 17 3 2 3 3 14 3 3 3 2 1 1 16 46.4 3 3 3 3 2 3 3 3 3 3
Automated internal model that enables predicton
Energy Market Very Short-Term to Short-Term Load X Data exists. Challenge is automaton - from one hour out, 24 hours out, balance of month
Predictve Analytcs Operatons / SPO UC-084 Forecast High High out, reducing risk and redundant modelling 2 3 2 1 3 17 3 2 3 10 3 3 3 3 3 3 3 3 3 32 59.3 3 3 3 3 2 3 3 3 3 3
Determine how factors such as weather impact
Energy Market declared plant parameters versus actual
Predictve Analytcs Operatons / SPO UC-085 Declared Plant Parameters Versus Actuals performance, improving predictve models 2 1 1 1 7.5 2 1 2 6.5 2 2 2 2 2 3 16 29.6 2 3 2 2 2
Identfy and protect crown jewels and develop
X security rings / zones to control access, optmizing
Cyber Security Cybersecurity UC-086 Data classificaton High High (Waitng on RFP) storage investments 1 1 3 1 3 2 7.8 1 2 3.6 14.4 3 3 3 3 3 3 3 3 3 3
Refine the business rules using analytcs to balance
X false positves against full and complete detecton of
Cognitve Analytcs Cybersecurity UC-087 Alert Optmizaton High Data in Splunk - High attacks, reducing risk 3 4.5 1 3 1 1 7.8 2 2.4 14.7 2 3 3 3 3 3 3
Optmize and prioritzaton baseline profiles of
actvity so anomaly detecton can be determined,
Predictve Analytcs Cybersecurity UC-088 User Behavioral Analytcs - Insider Threats reducing
Root causerisk
analysis to reveal how many employees 2 3 3 1 1 6.5 2 2 4.8 14.3 2 3 3 3 3 3 3
are susceptble to phishing attacks, helping to guide
change management actvites and reduce the risk of
Predictve Analytcs Cybersecurity UC-089 Internal Weakness Assessment cybersecurity attacks 2 3 3 2 6.5 2 2 2 7.2 16.7 2 3 3 3 3 3 3
Descriptve Analytcs Cybersecurity UC-090 External Vulnerability Assessment Match vulnerability against critcality 2 3 3 1 5.2 2 2.4 10.6 2 3 3 3 3 3 3 3
Develop tools to assist with capacity planning, to
assess
Identfyhow
key various
themesretenton
that drivepolicies
serviceimpact capacity
now tckets,
Stochastc Optmizaton Cybersecurity UC-091 Productvity Analytcs - Capacity Planning in order tohow
assessing make better
many investment
could have been decisions
completed by 2 3 2 1 1 1 6.5 1 2 1 4.8 14.3 2 1 2 3 3 3 3
self-service tools already in place vs identfying new
self-service opportunites in order to optmize
Descriptve Analytcs Cybersecurity UC-092 Productvity Analytcs - ServiceNow resource costs 1 1.5 2 1 1 5.2 1 2 1 4.8 11.5 2 1 2 3 3 3 3
Improve access management through actvity-based

assessment, to reduce unnecessary access to
Descriptve Analytcs Cybersecurity UC-093 Access Management systems and reduce risk of breaches 3 4.5 3 3.9 1 1 2 2 7.2 15.6 3 2 2 3 3 3 3
Improve pattern recogniton tool for plant startup
across all plants to reduce false negatves and false
Power Generaton - Fossil UC-094 Smart Signaling Pattern Recogniton positves, reducing risk 1 3 1 1 9 3 2 6.5 3 3 3 3 3 18 33.5 3 3 3 3 3 3 3 3
X Accurately project hour by hour output based on

Power Generaton - Fossil UC-095 Weather Adjusted Megawatts ambient conditons to mitgate supply/demand risk 1 3 1 2 3 15 1 1 1 1 5.2 1 3 1 1 1 1 3 1 1 1 17 37 1 3 2 3 3 2 3 3 2 1 3 1
Automate maintenance system to improve

Power Generaton - Fossil UC-096 Workforce Productvity maintenance process and reduce resource spend 2 1 2 7.5 2 1 1 1 1 7.8 1 1 1 1 1 1 1 1 9.6 24.9 3 2 3 3 3 2 2 2 2
X Attach financial data to assets in order to improve

Power Generaton - Fossil UC-097 360 Asset View spend decisions
Monitor
Quantfy vibratons and createtax
the costs (including alerts
and on variatons in
earnings 3 1 1 7.5 2 1 3.9 1 1 1 1 1 1 1 1 9.6 21 1 3 3 2 2 3 3 2 3 3
amplitude, frequency
implicatons and velocity
across [CLIENT]) to detect
of retring assets at a
problems
certain tmeearlier
versusandhistorical
increaseprojectons
safety and of what
Power Generaton - Fossil UC-098 Vibraton analysis preventatve
should maintenance
have been retred inatorder
powerto plants
optmize when 3 3 1 11 2 2 2 7.8 2 2 2 2 2 12 30.3 3 3 2 3 3 2 3 3 2 1 3
and which assets to retre based on financial
justficatons
Accountng UC-099 Asset depreciaton retrement 2 3 2 2 5.2 1 1 1 3.6 11.8 1 2 2 3 3 3 2 3 3
Optmize closings throughout the year with
predictve analytcs, accountng for surge of inputs at
year-end to ensure targets are met
Accountng UC-100 Rate case closings [CLIENT] can improve revenue recovery as DER 2 2 6 1 1.3 2 2.4 9.7 2 2 2 2 3 2 2 3
expands in prevalence. Note: AMI is needed for rates
Iterated Outside to truly transform. A rate roadmap project is also in
Descriptve Analytcs Workshops UC-101 Rate Design / Rate Optmizaton Low Dependent on reg roadmap progress 3 3 3 3 3 3 3 32 3 3 3 12 3 3 3 3 3 1 1 3 2 26 69.6 3 3 2 3 3 2 3 3 3 3 3 3 3 3 3
AIRSWEB data available - detect and prevent
[CLIENT] can proactvely identfy,potentally
target, and
Iterated Outside Unstructured . Tied to telemetry data incentvize
hazardous situatons
customersand withtake
highactons
usage to mitgate
during peak
Predictve Analytcs Workshops UC-102 Safety Analytcs Medium & tme and labor - Medium [CLIENT]
demand can
andanalyze
accidentstmes injuries interval
to improveresultngconsumpton
load from the
relief. Networkdata to
situaton 3 1 6 2 3 2 1 1 12 3 3 3 3 3 1 1 1 1 1 1 2 2 3 1 1 1 37 54.9 3 3 3 3 2 3 3 3 2 3 3
identfy
operators start
canorretroactvely
stop of consumer devices
determine the such as aof
amount
refrigerator, air isconditoner,
load relief that available atpool pumplocatons
network or TV to and
Iterated Outside distnguish
price points,between
if the loaddiscretonary and
reducton actually occurred,
Predictve Analytcs Workshops UC-103 AMI - Demand Response Analysis Low nondiscretonary
and by which customers energy usage and consequently 1 3 3 3 3 3 3 29 2 3 3 3 3 18 3 3 3 3 1 16 62.3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
develop better commodity management functon
Iterated Outside AMI - Device Fingerprintng - Load and a more efectve use of load as a resource in
Predictve Analytcs Workshops UC-104 Disaggregaton [CLIENT]
distributoncannetwork
proactvely monitor meter temperature
operaton 2 3 3 3 3 21 2 1 3 7.8 3 3 3 1 12 40.8 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
to identfy and deploy alerts both during and in
Iterated Outside AMI - Meter Temperature Monitoring - [CLIENT]
advance of can"hot
identfy andscenarios,
socket" track highdecreasing
risk candidates
risk
Predictve Analytcs Workshops UC-105 temp forecastng (monitoring is covered) for
andenergy theftsafety
improving by using risk scoring and confidence 3 3 3 3 18 3 3 3 12 3 3 3 11 40.5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
levels, track investgaton case status, and estmate
Iterated Outside AMI - Theft Detecton (part of AMI power and revenue losses to increase revenue and
Predictve Analytcs Workshops UC-106 project) Develop
decreaseariskportfolio of targeted messaging using 1 3 2 3 3 18 3 3 3 12 3 3 3 3 14 44.1 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
customer segmentaton with counterfactual analysis
(baseline analysis) to engage and inform customers
so that they have increased awareness of their usage
Iterated Outside which will ultmately lead to them adjustng their
Workshops UC-107 Consumpton reducton Low AMI is handling Develop
consumpton a series of targeted
throughout themessaging
year using 1 2 1 1 6.5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
1 2 1 6 2 12.5
customer segmentaton that will be deployed during
a peak period with counterfactual analysis (baseline
Iterated Outside estmaton) to encourage customers to adjust their
Workshops UC-109 Behavioral Demand response program Low AMI is handling usage during a few peak hours 1 2 1 6 1 2 1 1 6.5 2 12.5 3 3 3 3 3 3 3 3 3 3 3 3 3 3 3
[CLIENT] can use monthly meter data to alert
customers that their bill will be high due to increased
Iterated Outside usage in order to reduce call center calls and improve
Workshops UC-110 High Bill Alert High CSAT score 3 4.5 3 3 7.8 1 3 12.3 3 2 3 3 3 2 3 3 1 3
Using voice-to-text transcripton tools and text
analytcs, mining customer calls for insights on
Iterated Outside satsfacton and other key metrics to improve CSAT
Workshops UC-111 Call Audio Analysis High scores 1 2 4.5 3 3.9 2 8.4 3 3 3 3 2 3 3 2 3
Area Total
(insert row if needed)

Total 23 29 24 10 3 11 11 13 2 9 203 29 23 1 9 8 34 16 31 7 4 211 0 112 18 17 19 16 9 5 11 8 9 14 12 14 16 24 13 12 22 26 9 329 19 12 16 24 30 22 45 11 8 0
Analytics Capabilities - Existing Projects

Total 23 29 24 10 112 18 9 14 12 14 16 24 13 22 26 9 126 40 140 153 173 157 335 105 41 0
[CLIENT]
Descripton:
Guidance:
Contributors:
UC-002
UC-003
UC-004
UC-005
UC-006
UC-007
UC-008
UC-009
UC-010
UC-011
UC-012
UC-013
UC-014
UC-015
UC-016
UC-017
UC-018
UC-019
UC-020
UC-021
UC-022
UC-023
UC-024
UC-025
UC-026
UC-027
UC-028
UC-029
UC-030
UC-031
UC-032
UC-033
UC-034
UC-035
UC-036
UC-037
UC-038
UC-039
UC-040
UC-041
UC-042
UC-043
UC-044
UC-045
UC-046
UC-047
UC-048
UC-049
UC-050
UC-051
UC-052
UC-053
UC-054
UC-055
UC-056
UC-057
UC-058
UC-059
UC-060
UC-061
UC-062
UC-063
UC-064
UC-065
UC-066
UC-067
UC-068
UC-069
UC-070
UC-071
UC-072
UC-073
UC-074
UC-075
UC-076
UC-077
UC-078
UC-079
UC-080
UC-081
UC-082
UC-083
UC-084
UC-085
UC-086
UC-087
UC-088
UC-089
UC-090
UC-091
UC-092
UC-093
UC-094
UC-103
UC-104
UC-105
UC-106
UC-107
UC-109
Err:509
0
0
Data Source Assets SK SK
Alignment to Analytics Capabilities (1-0 impact score)
Total
TPPS The Third Party Payment System (TPPS) is a system for recording the payments received from customers. All payments 1 1 1 1 1 1 1 1 1 1 1 1
go through RTPS or TPPS. Only diference between RTPS is that payments between 7:15 am and 7:15 pm are
considered real-tme. Payments between 7:15pm and 7:15 am via batch loads are carried out through TPPS. There are
a lot of feeds from external vendors to RTPS for payments from diferent sources. RTPS interfaces with CCS for postng
of those payments.
Sabrix Tax SABRIX is a Tax engine primarily used for calculatng [CLIENT]'s Sales and Use Tax. It is used to determine tax for 1 1 1 1 1 1 1 1 1 1 1 1 1 1
vendor payments only. It is not used for calculatng the Tax components on the customer statement/ bills. This
applicaton is a customized package but is supported in-house. It is interfaced with Accounts Payable or external Tax
Vendors. SABRIX was implemented in 2006.
This applicaton extended the standard tax features available in PeopleSoft. It uses the applicaton broker & integraton
protocol to provide Tax Data to PeopleSoft users transparently. The PeopleSoft Component calls the broker which
communicates with SABRIX through XML process. Multple automatc updates occur every month. In case there is a
conflict between the Tax amount calculated by the PeopleSoft AP system and SABRIX, it results in partal payments to
the vendor untl the issue is resolved. [CLIENT] uses this functonality only to determine the Sales and Use Tax and it
does not leverage other functonalites of this applicaton like calculatng the VAT, excise and indirect taxes and fees.
Workflow: When certain items are purchased, tax payable on them is accrued based on the assessment carried out by
Sabrix. The accrual is booked in PeopleSoft. The Tax Compliance group queries a report, validates the amount and
authorizes the tax payment through ATPR. Certain cases are not routed through Sabrix such as some specific BU
related cases, certain vendors related, certain invoices related and certain contracts related. Within Sabrix, there is an
in-built business logic which takes into account the Tax rates, jurisdictons and other factors which impact tax liability.
It is a highly stable system. Whenever there is a change in the tax component, an automatc update is sent by the
SABRIX to [CLIENT] to implement the same. The desired changes are then incorporated into the system. The updates
PeopleSoft Fin occur
Employeeon an immediate
info, notce
specifically and employee
[CLIENT] there is nofinancial
notceable
infotme
usedlag. It is aLMS
to keep web-based finance applicaton that sits on
up-to-date 1 1
PeopleSoft HR Employee info, specifically [CLIENT] employee demographic info used to keep LMS up-to-date 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
PeopleSoft T&LAM "PeopleSoft Time and Labor is the tme-keeping system of the company. It is the main source of informaton of an 1 1 1 1 1 1
employeeÆs tme. It replaced ESTER which was a home-grown applicaton. The project took four years and went live
in 2012.
The system captures what tme is being billed by allocatng code blocks. Code blocks are set up in the system by
employees. The applicaton keeps track of the in-tme and out-tme of the employees when the employee punches
his/her card. The Time details are entered and managed in Timesheets. Once the employee enters the tme, it is
available for the supervisor to review and approve. It also has an Absence Management Module. . Every Monday,
Absence Calc. and TA (Time Administraton) are run and, if required, data is cleaned or processed for excepton
approval. Mass approval happens before the load if the data is clean. It is then uploaded for further processing. The
applicaton is also used for allocatng costs and is capable of handling work shifts. The system efectvely captures the
data if an employee is assigned to one shift or multple shifts.
It interfaces with PeopleSoft HRMS, Work Management System from Transmission, as well as PeopleSoft HRMS-
Payroll system to calculate the compensaton for the employees against the tme spent at work. The work schedules
are set up by the business.
Currently, there is no way to verify the number of hours put in by the employees in the Time Sheet. The Company has
to rely on the Time sheet details only for processing of the Payroll to calculate pay for the number of hours of work
put in by the employees. The tme sheet has to be approved by the immediate manager of the employee.
Issues Faced: They are related to the high volume of data and growing pains related to the applicaton being relatvely
new in the company and users stll getting familiar with it."
VEA (AIXPROD) The Vehicle Entry Applicaton (VEA) is a home grown, web-based tool that is used to allocate vehicle costs 1 1 1 1 1 1
appropriately to Capital and O&M based on the work the vehicles support.
This applicaton allocates the usage of the vehicles û cars, trucks, trailers, etc. û owned by [CLIENT]. There are
allocaton methods and rules for each type of vehicle. The costs pertain to depreciaton, mileage, maintenance and
upkeep of the vehicle over the duraton of the project. There are diferent ways of assigning the costs: Code Block;
PeopleSoft Time and Labor, Payroll. Further there are diferent allocaton methods depending upon whether it is a
Capital project or for O&M.
VEA interfaces with PeopleSoft modules Time and Labor, Payroll, and GL; and with Fleet. It is a web based tool with
Oracle at the back end.
ARCOS Call out and scheduling system 1 1

Bill Matrix Bill Matrix is an external payment service. This service allows an online customer to pay with other tender besides 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
draw draft
RoD Resources on-Demand (RoD) is a web-enabled system used to manage resource (people and equipment) requests 1 1 1
and track personnel movement during emergency outages. In the event of an outage emergency, a power company
needs a tool to facilitate resource request and assignments. RoD captures resource requests and available resources
and provides historical informaton on the movement of resource teams. Within RoD, all personnel movement is
tracked historically within an event and maintained for historical reportng. It is only used during storm recoveries,
payment and justficaton of storm invoices.
RoD tracks hotel reservatons, workers, assigned jobs, equipment and any other movements during storm restoraton.
It also tracks meals for work crews by entering vendors and expected delivery.
RoD is installed on two internal [CLIENT] web servers with F5 load balancers. The load balancers were added after
experience in 2012 storm recovery, but the system is having session persistence issues. IT is currently working with
the vendor to resolve. RoD could contain privacy informaton if a medical conditon occurs during restoraton. It has a
placeholder for medical conditons.
SQL agent jobs in database run nightly to take snapshots of tables.
Interfaces:
None
Functonality not available: We would like limited contractor access to ROD to allow them to input data into ROD
during storm. It could be a spreadsheet contractor can upload into a repository with in ROD.
Report: Standard set of report available with in ROD. Ad-hoc query is being maintained by Alan to run whenever
required.
One Source Not found 1 1
UI Planner (P2R) Nuclear Capital Planning System will support the Capital budget planning and tracking for Nuclear. The existng system 1 1
carries out the Budgetng and Tracking for O&M. A separate system needs to be created for the Capital Planning and
tracking in Nuclear.
FileNet FileNet is an image document management system used for storing invoice images. It is managed and used by the 1 1 1 1
Accounts Payable team. The image management capability of FileNet is interfaced with Accounts Payable for faster
processing of paper based invoices through automated image capture, optcal recogniton technology and
configurable business process workflow. The soluton eliminates physical paper handling and related costs associated
with manual invoice processing. Accelerated invoice processing is achieved by managing each invoice as an image
within the FileNet repository known as FileNet Content Engine and automatng data processing in FileNet Process
Engine. All the vouchers created in PeopleSoft require a document ID or the image of the actual invoice as a
supportng document. These images are stored in FileNet. In case of multple documents, metadata is used to link
them. The current version of FileNet Capture in use at [CLIENT] is version 5.2.1.The invoices come from various
sources that are interfaced with FileNet. It has an authentcated (User Id and Password) web interface, which can be
invoked to view content from various applicatons like Asset Suite and PeopleSoft. For Nuclear sites, the files are Ftp'd
locally and then an import program loads the files into FileNet. These import programs are run for batch processing of
the invoice images.
The applicaton is also interfaced with various external devices, such as RightFax and an email interface through
Mavro, which is used to email the pdf documents in the form of image, in additon to manual scan and upload
features for the import and export of the invoice images. Once the vouchers are created from these invoice images
and the payments are processed, the data is archived and sent to FileNet Record Manager. The FileNet applicaton is
integrated with SharePoint.
New versions for this applicaton are available; however, the vendor has announced that the applicaton will be at end
of life in early 2015. Presently, [CLIENT] does not use the workflow features of FileNet. Instead, the business uses
FIDO, a homegrown workflow tool.
AMFM DFM DFM (Distributon Facilites Management system) is an [PROJECT]System to track distributon assets such transformers, 1 1 1 1
regulators and capacitors. Capacitors have been added to DFM over tme; distributon is now adding switches due to
government requirements related to SS6 gas. It also tracks equipment that contains oil and has regulatory
requirements. DFM is focused on Distributon Line planning ($40-50M capex), improving customer reliability and
addressing aging infrastructure issues. DFM enables data driven planning to ensure best spending is achieved. DFM
replaced a mainframe tracking system.
DFM is broad term for non-graphical part of AM/FM. It includes customer account table and meter table. AM/FM
owns the DLOC / premise relatonship and sends back to CCS. When the meter is set at an existng pole, the work
order associates the premise to a meter or next-to meter. This associaton is used to determine the DLOC and updates
within AM/FM and CCS. If new locaton, data maintenance ensures that the DLOC is updated once the pole is set.
Tracking implies lifecycle monitoring from cradle to grave. It starts from procurement and contnues through
deployment, repair, and retrement. If equipment is in service, it also appears in AM/FM [PROJECT]. If not in service
(being repaired / reserved), it is maintained in DFM but is not in [PROJECT]. Transformers, capacitors, regulators and
reclosers are the primary tracked equipment. Supply Chain enters into DFM after procurement. Once reconciled
through the work management and design process, the field crew selects equipment from their stores and writes
informaton on a paper change order. Based on equipment number and details, the asset is actvated in DFM by the
data maintenance team. All changes to distributon data are maintained by the data maintenance team.
Distributon does not have a comprehensive view of [PROJECT] Equipment not in DFM is tracked offline in databases
and spreadsheets (e.g. poles, avian outages, and outage trending and data analysis). There is very limited knowledge
of how old equipment is in Distributon. [PROJECT]should become increasingly important as the system contnues to
age. [CLIENT] will want to make intelligent capital investments. Also, distributon currently manages work in large
financial buckets. For example, all charges related to outages are charged to one charge code, with no insight into the
cost of an individual outage. It is expected that it will become more important to understand data and costs moving
forward. Customers want to know more informaton about issues and resolutons, and increased knowledge about
assets and economic linkage to assets. Accuracy becomes more important as data is exposed to customers (e.g.
red/green lines on outage map).
Requirements to perform annual inspecton on reclosers, capacitors and regulators are assigned through DFM. IT
developed an automated batch job to generate work orders to perform inspecton (regulatory requirement in some
states). Based on inspecton, the field may also need to perform repairs and/or replace the equipment. Work orders
are created through DFM to generate in DIS and then push to Service Suite. DFM also provides load analysis at
transformer / customer level.
DFM has limited reportng capabilites around equipment. Some reports are broken and not heavily utlized (e.g. ratng
equipment analysis to determine under-rated devices). Capability of trending around assets is not fully developed.
Users cannot easily run a query of what is broken so that work can be planned for fixing. Instead, the business must
perform manual processes such as capturing in Service Suite, writng down the informaton and sending back to a
geographical region. It is also not easy to track what was actually repaired. The necessary data actually resides in
DFM, but it is not possible to look at the changes.
Engineers serve as maintenance program owners and use DFM to develop the preventve maintenance plans (10-14
annual programs). Example programs may include outage tactcs and targeted circuits. A work plan is developed
around program criteria to select best funding across all jurisdictons.
Tactcs is a good example of automated program selecton in DFM. An algorithm automatcally selects the projects.
AMFM EA EA( Engineering Analysis) is an analysis software to perform load flow and short circuit studies on distributon feeders. 1 1 1
EA creates an extract for Synergee. EA is part of AM/FM which sits on top of AM/FM [PROJECT]. EA is used to calculate
the peak load in summer and winter. The load study is performed at transformer level. EA contains load studies
performed semi-annually based on usage informaton from CCS/CIS. This is performed by IT support.
Users perform extracts from EA and also use the mapping functonality to view assets. It has other functonalites (e.g.
cable editor, wire editor) which are not being used.
Users :
Planners, Fault locaton detecton also benefit from EA. 45 planners for all the Jurisdicton. We are using the same
guidelines and tools even though we are spread across the geography.
Interface:
DFM - usage informaton
[PROJECT] - extract of transformers
Synergee - EA extracts informaton
SQRT - used to create extract for Synergee
Technologies:
GE Smallworld
CustomTool :
Weather normalizaton process spreadsheet: This helps in scales up or scales down the load forecast normalizaton.
Uses last 10 to 15 years of actual data for modeling. This is built in excel spreadsheet.
Issue/pain points:
Distributon planning is tme consuming with lot of manual steps. Lots of tme is spent to get to the point where
planners can do the analysis. Engineer need to have knowledge of various technologies to do the analysis (STP ,
Microsoft Access , need to understand the tables, etc.).
Distributon planning would be more efectve if building the load model was automated. Building a substaton is very
expensive, and it would be beneficial to have good analysis to forecast, plan, and build the load model through
automaton.
Additonal Functonality: None . It supports and does a good job. It transforms the data to the format in which analysis
can be done.
AMFM Gas AM/FM Gas is a [PROJECT] based system used by [CLIENT]Æs Gas Distributon organizaton in New Orleans and Baton 1 1 1
Rouge. The system stores the spatal and locatonal informaton related to major assets for gas distributon, such as
mains and services. The key functonality is identficaton of the physical locaton of the gas piping network in the
ground.
The informaton resides in a specific Gas Database in the GE SmallWorld [PROJECT] system, which was purchased in
2004. [CLIENT] has built the gas network using the gas network data model provided by GE. The network data model
has undergone minimal customizatons and [CLIENT] has tried to minimize customizatons as much as possible.
The land base related to Gas network is conflated and GPS accurate. [CLIENT] uses the land base provided by the cites
of New Orleans and Baton Rouge. The system also holds around 34 miles of gas transmission mains. GDO (Graphical
Design Object) is used to draw these mains in [PROJECT].
Functonality:
Pipeline Constructon Process - Pipes (Mains & Services) are typically designed in DIS and then sent to field for
constructon. After the constructon is complete, field users provide ôWork Slips,ö and these ôwork slipsö are linked to
Documentum, which is [CLIENT]Æs document management system. The linkage of work slips to Documentum is done
in the back office.
Gas Pipeline Leakage Survey û Leak survey technicians use printed maps and manually prepare a route to perform
Leak Surveys. The printed maps contain the gas network (including mains, services and other facilites) of the area
where the leak survey is intended. When a pipeline leak is identfied during the survey, the leak details (e.g. grade,
locaton, etc.) are manually captured on the printed map. A GFIX tcket is then created in DIS for leak repairs.
Potental improvements
1. Automate the entre Leak Survey process, including electronic recording of the leaks.
2. Currently the leak informaton is not available to the DIMP software for risk analysis. Future asks is to automatcally
transmit the leak data to DIMP.
3. Regulator Staton inspectons are handled by a diferent department and are currently managed in Microsoft Access
Database. This data is not connected electronically to the work management systems. Future asks is to handle
Regulator Staton inspectons in a Work Management System, rather tracking the inspecton in [PROJECT] (manually)
as is the current scenario.
4. Cathodic Protecton data is available in [PROJECT]. Cathodic Protecton technicians use this informaton to perform
CP surveys and capture the results manually in [PROJECT]. However [PROJECT] is capable to store only the latest CP
readings, overwritng the historical data. The historical readings are available only in a paper format. There is scope to
automate some of the processes in Cathodic Protecton.
From a technology point of view the applicaton uses Oracle database and GE SmallWorld and Magik modules for
programming the customizatons.. The total user base for this system is around 40 to 50 users.
AMFM OM Interfaces:
"Outage Management (OM) is built on top of AM/FM [PROJECT]. It collects customer outage informaton from phone 1 1 1 1 1 1
calls from customers, text messages or through the IVR system and predicts outages. OM tracks the lifecycle of
outages and records outage informaton for historical purposes. AM/FM [PROJECT] stores the network informaton
from substaton to service point. Service point is the end point in [PROJECT] and is connected to the customer's
informaton such as meter or premise. The customer informaton is maintained in an Oracle database, and both
network and customer model is present in AM/FM DFM. AM/FM DFM serves as the data model for Outage
management. Emergency calls are handled in SAISO, and SAISO generates the outage trouble tckets. The tcket from
SAISO is sent to OM, and OM predicts the outage on device based on the grouping of calls. The predicton logic helps
to locate the outage in [PROJECT] and generate the estmated tme of restoraton (ETR). ETR is communicated back to
SAISO. A high level ETR is communicated to the customer. Dispatch / crew executon is done through Service Suite.
Switching management for outage is performed by backend MAGIK process inside [PROJECT]. Outages after
restoratons are archived and moved to history in DFM.
Outage from SCADA û Alarms from SCADA comes into AM/FM along with Breaker status, feeder ID and Substaton ID.
RDR is applicaton which scans every 4 seconds the alarms from SCADA for outages and updates in oracle DB.
OM is highly scalable and used even in Storm management.Call processor talks to 2 AIS/2 SAISO databases, polls 5 per
second. This interface has been in service since 1997 and is developed in ôPro Cö.
GCR Interface pushes outage informaton by neighborhood to regulators.
Architecture is similar to that of AM/FM as OM is subset built on top of AM/FM.
Current business processes includes outage restoraton, monitoring through SCADA, trouble management, trouble
dispatching, ETR calculaton, and switching management.
OM has basically two operatons: Predicts by phone calls and confirm breaker operaton by SCADA. OM predicts by
phone calls unless it is a breaker outage, in which case it depends on SCADA to send informaton that overrides
breaker status. OM has capability to reconfigure the system. There is a panel in system called ôReconfiguraton
Manualö which helps in modeling the system on the fly. This is also used as simulaton mode where manual actons
are performed that would be really done in the field. This helps in providing customer count of all customers from
breaker to the feeder. [CLIENT] would like to have logic built to know what the positon of reclosure is when the
breaker is operated. Past the breaker there are devices which operate based on certain conditon which helps in
reconfiguring the system like de-energizing and energizing customers. These devices have SCADA interfaces but those
are not used as of today to know the positons. Right now the system predicts what devices can be operated but
there is no way to know the current positon of the devices
Key metrics like SAIDI and CAIFI are measured and reported. These are standard reports that go into corporate
scorecards and are compared with other jurisdictons.
[CLIENT] would like to have AMI integrated to outage management as this will avoid dependency on to customer calls.
This will help to come up with immediate acton plan before customer calls in and to know quickly what the problem
causing outage.
Interface :
IVR --> SAISO to capture Outage calls
GTI Viewer GTI Viewer provides geospatal viewing and analysis capabilites for the office and field users. GTI Viewer has replaced 1 1 1 1 1
the field paper maps and is used for locatng and viewing [CLIENT]'s facilites, queries, scoutng, redline and markups.
It is an intricate part of daily field operatons and is used for outages, where you will have to run queries and trace
back to feeds. GTI Viewer has the capability to identfy the electric and/or gas facility supportng a locaton.
GTI Viewer is used as a field soluton for street light assessments. Constructon crews can load GTI Viewer to view
facilites. Crews can perform redlining, email the GTI Viewer file and request the data maintenance group to update
AM/FM [PROJECT].
GTI Viewer extracts AM/FM data to proprietary database and compressed to manageable file size. The file is pushed
out to mobile devices and allows field user to view in disconnected mode. Data is refreshed on monthly basis and
available in read only mode. GTI Viewer has GPS tracking capability, but all users do not have a GPS Dongle. Service
crews have wireless connectvity and modems. In Service Suite one could create a file and import the file in GTI Viewer
to display all the userÆs work graphically and create a route.
Distributon is currently trying to use GTI Viewer to capture the damage informaton of [CLIENT]Æs facilites during
post storm assessment. Field users can use on their hand device and report the damage informaton back. Currently
[CLIENT] is looking at GE Damage Assessment tools, but the strategy is not decided as it depends on the ESRI and
Service Suite roadmaps within [CLIENT]. GTI is popular with field crews due its ability to provide spatal view.
Modificatons (Phase 1 completed - not rolled out to all users, Phase 2 - changes identfied) are underway to assist
damages during Major outages by collectng attributes.
GT Web - Smart phone based. Damage Preventon & locate groups as it enables fast access to informaton (Gas &
Elect.)
Known issues:
1. GTI Viewer data file is diferent for each state. In case of STORM scenario, download the specific GTV file and
have to be connected to the server, this is tme taking process.
2. Monthly extract (so data is old): The data could be inaccurate as its not live data and it's based on the extract
which is done once a month. Routne extract which runs once a month.
3. Data size is increasing (gig +), could be the reason for users not updatng the data periodically.
4. Coordinatng with multple vendors: Software is supported by vendor GTI and data extract is performed by
another vendor.
5. One need to connect through flash drive not automated sync process.
6. Potental Safety issue.
Future (good to have): Follow through' on enhancements. Better download process. Plotting functonality needs to be
enhanced.
Out of the box: [CLIENT] specific Configuraton (styles, displays, labels, query menus etc.).
User: Service suite users are big users. They are the main users (approximately 1200+ users). Service man uses it for
locatng outages.
Interface:
QuestLine Extract from [PROJECT] to get the data, not direct interface. 1 1 1 1 1 1
Questline is an external vendor responsible for delivery of marketng-based emails. These emails include the welcome
and newsletter emails.
No internal integraton – info extracted out of UDW to develop target lists , then sent to Questline
Service Suite (MDT) Service Suite is a work management transactonal system. Its architecture includes an applicaton server, operatons 1 1 1 1 1 1 1 1
database server, historical database server, and street level routng server. DIS delivers Work in/out of Service Suite
to/from the host systems (CIS, CSS, FLEET, DFM - Reliability, and AMFM). Service Suite is primarily used for
distributon non-design work, which includes customer-driven work orders (e.g. turn ons and turn ofs), maintenance
inspecton, emergency work, outages, and meter changes.
[CLIENT] deployed Ventyx Service Suite in 2008 and upgraded to current version Service Suite 8.0 R2 in 2010. There is
a currently a planned upgrade to version 8.1.2 in the near future (next few months). The latest version of Ventyx
Service Suite software available in market in 9.x. An approved decision is pending to perform this upgrade 2013-14.
Couple of technical reasons for upgrade to 8.1.2: The existng version does not work with Windows 7 PC and two of
the applicatons connect to Oracle through individual user accounts, which has been identfied as non ûcompliant in
the security audit. The implementaton of Ventyx has moved the soluton into more automated and optmized work
management. Before, work was assigned to a person by simple assignment but now optmizes based on shift. Street
level routng did not reduce truck rolls because individual workloads increased. Street level routng does dispatch
trucks in most efficient manner. Before Service Suite, technicians were average 6-10 orders per day. After, technicians
were averaging 35-40 orders per day (completng backlogs). Now, the field keeps no backlogs and averages 16-18
orders per person per day.
There are two data bases: ODB (Operatonal Database) and HDB (Historical Database). ODB and HDB are kept in sync
using Oracle stream. ODB has orders limited to past 7 days only, thereby maintaining a much smaller database size
compared to HDB. Currently there is no archival strategy; all the data is retained in HDB. HDB is currently 1+ TB. The
future upgrade to version 8.1.2 will address the issue as it provides capability to archive data. Historical database
(HDB) is used for order completon trends, average travel tme, available man hours vs. idle tme, etc. For example,
used to track success of work order consolidaton (move in / move out) project and was able to justfy reducing
contractor pay based on more accurate depicton of work.
Service Suite has Cognos tools for reportng û ADS/ KPI. In order to create reports, complex database joins are
required. Reports out of HDB are very slow due to the database size. Cognos extracts some data to UDW. Cognos
needs to be more user-friendly to field resources. The users would find it helpful if Cognos was built of live data; the
data delay causes many reruns of reports. Users have had some glitches with system retrieving data, and IT is in
process of moving to a diferent architecture to try to improve performance. Currently there are 9 reportng
enhancements pending for business. The field is not running reports because IT infrastructure is not there (e.g.
reports may tme out based on unavailable resources).
Service Suite is highly configurable. Customizatons were done to the field mobile module creatng 10 new forms for
data capture; apart from that there are no other customizatons in Service Suite. On top of HDB there is an ecosystem
of data exchange, with multple enterprise wide systems utlizing the data for example; Meter Testng Data.
Timekeeping is captured in [CLIENT] Fleet Systems, the capabilites / features ofered by Service Suite are not used.
Currently there is a no disaster recovery mechanism laid out for Service Suite. High availability is ensured through a
failover to HDB in case of ODB going down. In the event of a failover the systems access is restricted to limited users.
Mobile Display Terminals (MDT) Panasonic Tough Books and Dell 80G are used by filed technicians and regular
Desktops are used by Dispatchers. Technicians to use the street level routng more consistently. Some stll go their own
way. If a technician is dispatched toward an emergency, he can click to re-sequence his remaining work in the most
efficient manner. Today, it is a manual process, but would like to have automated.
Approximate order volumes are 20,000 work orders per day transacted in Service Suite. The work optmizaton
Operatonal Database (ODB) There are two data bases: ODB (Operatonal Database) and HDB (Historical Database). ODB and HDB are kept in sync 1 1
using Oracle stream. ODB has orders limited to past 7 days only, thereby maintaining a much smaller database size
compared to HDB.
Call Center Informaton Not Found 1 1 1 1 1 1 1
MAO (My Account Online) E- My Account Online allows [CLIENT] customers (both in CCS and CIS) to access to their account informaton and pay 1 1 1 1 1
Plus their bills. Customers can report outages, perform service initaton, and request payment extensions. MAO provides
a bill analyzer that displays reasons that the bill may be higher than expected. It also allows customers to opt-in to
email and text message notficatons.
Currently, over 1,000,000 accounts have re[PROJECT]tered through MAO.

Since the applicaton is customer-facing, authentcaton is done through SQL Authentcator on top of the Oracle
database instead of through ActveDirectory.
[CLIENT].com Web Analytcs/Tracking - Coremetrics is used to provide the web analytcs capabilites for [CLIENT].com. Currently, 1 1
there are no customer-level tracking features in place
Large Power Billing Informaton Not Found 1 1

system (LPBS)
Trade TRADE is a front-end entry tool for transformer rated meter data sheets. This informaton was originally entered and 1 1
tracked on paper. There is no place to store this data in CCS, and the project was initally started as part of a DR plan
Calvin (Cut Actvity Logging home grown applicaton - for logging processes, For Sarbanes-Oxley reportng (SOX), the business can investgate what 1 1 1 1 1
and Validaton of Internal happened with a partcular cut of data.
Networking)
DMIT DMIT is used to track and complete dead meter investgaton codes entered by meter readers. The system 1 1 1 1
automatcally completes some records based of meter reading history and business rules. The remainder of records
are presented to back office (MCAS) for verificaton.
Implausible Automaton This program automatcally releases targeted implausible meter readings. The WINBATCH Implausible Meter Reading 1 1 1 1
program runs a check on the records and looks for implausibles within the readings. An implausible is similar to an
outsort. It a meter reading that CCS considers invalid and will not bill.
MAVEN MAVEN automatcally verifies the more simplistc MAB accounts. It processes around 1200 accounts per month. 1 1
MAVEN stores independent account details (rate, riders, lights, etc) in its own database and automatcally interfaces
with CCS, BEX and Excel workbooks to gather data
MAB (Major Accounts Billing ) 1 1
ATW (Allowance Tracking his product is used to keep track of environmental allowances provided by the government and any purchased or sold. 1 1
Workstaton) Allowances tracked are SO2 and NO2.
Fossil records all transactons and financial informaton. Emissions are manually inputted. Produces reports for EPA.
ABTS (Asbestos Tracking Interfaces to ESTER to record user name and supervisor for updatng record. Uses standard Fossil interface to ESTER 1 1
System) (batch job runs and updates a middle-ter table).
Not used by all plants.
One purpose of the applicaton was to provide employees informaton. However, they call the contractor or just look
for the blue bands. The app does not seem to be adding value.
AIMM(Automated Integrated AIMM implements processes for maintenance management. manages component facility data, work requests, 1 1 1 1 1 1 1 1 1 1 1 1
Maintenance Management) preventve maint tasks, schedules, materials orders and contractor work.
All contracts and purchase reqs are initated and approved. Has outage cost tracking capability. Extensive reportng
capability in reportng tool. Track correctve work vs. preventve maintenance.
Only app for Fossil with SLA. 99.6% availability with Saturday night outage window.
Interfaces: Powerplant for projects, financials for data, budget system, Passport for contracts, Passport for materials,
account validaton module, tagging system, technical drawings, reportng tool, Outlook for notficatons.
ATS(Automated Tagging supports the Fossil Operatons Tagging Procedures. ATS manages standard clearance templates, clearances, and tag 1 1
System) printng.
Documentum - Supply Chain This applicaton is a cabinet in Documentum (SCMS Cabinet) used by the Supply Chain organizaton as a document 1 1 1 1 1 1 1 1 1 1 1 1 1
repository. It contains any documents created during vendor engagements, RFPs, purchase orders, certficates of
insurance. On average, 10 supportng documents are created per contract. For compettve bid contracts, up to 25-30
documents may be stored. Each sourcing group has their own folder within the cabinet and may store additonal
documentaton based on their own internal processes or business unit standards. This cabinet does not contain any
WebTop customizatons.
Although the system is functonal today, users have recorded one outstanding feature request. They have asked for
the capability to save documents directly into the store from within their document creaton applicatons.
Documentum - [CLIENT] [CLIENT] Enterprise Content Management system (Shared Documentum) - used to store current project informaton 1 1 1
Enterprise Content and project artfacts
Management
PCI: Energy Accountng Energy Accountng: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Energy companies must account for all the megawatt-hours in their systems and PCIÆs Energy Accountng Soluton
simplifies that process by calculatng and tracking any type of energy asset data. PCI supports actual, calculated and
virtual meter data and can import that data from other systems.
Imports eter data from internal and external data sources such as MV90, SCADA
PCI: Generaton Supply Solutons: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Management System (GSMS) Originally founded as a generaton optmizaton software company, PCI has organically grown and expanded our
solutons suite to encompass all mission-critcal functons including bidding, scheduling, settlement, deal
management, asset operatons, data warehousing, energy accountng and business intelligence.
To allow our customers to optmize their generaton asset portfolios, all PCI delivered solutons involve robust analytcs
that accommodate the physical constraints of generaton assets. Our products are built on a common platform that
enables seamless integraton across all parts of your enterprise ù from daily operatons and trading to mid-term
portfolio management and financial forecastng, and even long term planning and analytcs.
PCI: GenPortal PCI GenPortal« is our web-based Business Process Management (BPM) and automaton soluton designed for 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
managing generaton assets. It is the functonal platform for all of PCIÆs software applicatons, and enables seamless,
enterprise-level integraton, allowing managers and traders to optmize and ofer their generaton portfolio(s) in a near
real-tme mode.
GenPortal« is a highly configurable system that spreads knowledge across your organizaton by integratng diverse
pieces of data to optmize decision-making. It reveals hidden operatonal and workflow savings while maximizing
return on investment (ROI). More than any other energy [PROJECT]tool, PCI GenPortal« combines complete control
and a scalable service-oriented architecture (SOA) to provide a turnkey BPM soluton.
PCI: GenManager PCI: GenManager pulls in data for settlements from MISO. The meter data comes in from the ISO statements and 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
GEMS. Exports data to PCI: Reportng (DART) or export to [CLIENT]'s internal reportng (not in PCI: GenPortal).
The issue with PCI: GenManager is that it can only pull in 3 days at a tme, there are no help files or documentaton,
and there is a volume issue.
PCI: GenManager cannot perform analysis, cannot perform scenerios, cannot forecast, cannot perform analysis on
historical data.
PCI GenManager« is a powerful software package designed to help market partcipants automate their bid
management process and maximize profits in an LMP, two-settlement market operaton. The soluton incorporates
locatonal marginal prices (LMP) and supports analysis modes for day-ahead and real-tme bidding. Its modular web
services architecture provides flexibility to respond quickly to varying market conditons and to interface with other
systems and data sources. The primary components of PCI GenManager« are described below.
PCI: GenTrader 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Operatons Planning Weather [CLIENT] uses OPWAQ to obtain historical weather data for use in its forecastng actvites. It will contnue to do so for 1 1 1 1 1 1 1 1 1 1
and Query (OPWAQ) the foreseeable future.
Additonal weather staton feeds will be required to improve the quality of its forecasts for Arkansas as well as the
wider MISO market area.
OPWAQ is a windows forms applicaton written in VB6 that queries actual weather data from the weather database in
OPPROD oracle instance on wo2oraproda.
The database gathers loads and temperatures for the 6 company regions or load zones.
PCI: Asset Operatons Asset Operatons: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Asset Operatons Soluton is an integrated collecton of applicatons designed to streamline work processes and
improve communicatons between plant and operatons personnel. It allows generaton owners and operators to
comprehensively manage asset declaratons within their company and report to an ISOs scheduling entty for
coordinaton and approval.
CCS Bill Print File Transfer Hub This system has a high architecture risk and seems to be overly complicated with a custom soluton. For much of this 1 1
functonality, other tools, such as EAI, exist in the enterprise. This system should be re-evaluated by ratonalizing
against standard communicaton tools and methods within the enterprise.
he CCS Bill Print File Transfer Hub was implemented as part of the BPO project. CCS sends files to the transfer hub,
which in turn forwards to bill print vendor. File internals are not manipulated; files are simply compressed and sent
through a VPN tunnel.
The system provides a web-based GUI view of the status of file transfers. An internal database records file processing
status.
For disconnect notces, the hub also send a file daily of available Quick Pay Statons.
Address files are sent to Bowne for standardizaton.

The bill print vendor returns around 40 files after processing, including insert reports, EDI files, MAO and CheckFree
files, quality control files, etc. Bill images are also returned and then run through a compatbility routne and loaded
into Mobius. A series of Mobius reports are generated and emailed to business users.
Some bills are specially routed when returned from the vendor, such as MAB accounts and accounts flagged by back
office (MCAS) (e.g. review, special conditon).
As the BPO project contnues to stabilize and rollout, the Hub should be monitored to ensure that its scope is
controlled. The intent is that the Hub will only monitor files, not interrogate or change the contents of the files. Need
to contnue to monitor file transfer speeds.
Basic privacy informaton is not included within the applicaton database, but is included in temporary files and bill
images
CCS Special Forms (Refund CCS Special forms handles the printng of items consistng of refund checks, credit letters, payment agreements and 1 1
Checks, DPA Letters) Texas deposit letters. Under normal operatons, around 1000 checks are printed per day. When events such as
deposit credit refunds happen, as many as 20,000 checks may be printed. This applicaton also sends log files that are
used for balancing, auditng and reconciliaton. Triggers with in both CIS and CCS automatcally initate the printng of
the required item. CCS FTP's a file of records to the mainframe where the documents are generated. The resultng
documents are printed and mailed internally at the Hammond facility.
Checkfree IBPP Genesis Vendor porton of IBPP - See Internet Billing Presentment & Payment that is, This applicaton provides an online 1 1 1
System viewable version of inserts for customer bills. Internet Billing customers are able to view the same insert informaton
as a paper bill customer. This functonality was transitoned to RR Donnelly as part of the BPO project for CCS
customers. Only CIS customers currently use this system.
Corporate Communicatons originally maintained an Excel spreadsheet; IT now maintains. Around 50 parameters can
be set to point customers to diferent inserts. Corporate Communicatons places the actual insert on the web server.
CIS Cancel Rebill Tracking CRB is a data store of historic CIS Cancel/Rebill summary reports. The report lists cancel / rebill accounts and the 1 1 1 1
reason for their status which is used for metrics. The report files are created each month after cycle 21 and than
manually loaded into an MS Access DB from their source on the mainframe. The Access database is used to generate
metric reports in Excel which, after being FTP'd to another server, are picked up by users. The applicaton is supported
by a SAIC ofshore resource who handles the importaton of the mainframe report files and the generaton of resultng
Excel reports. This applicaton is associated with both METNE and JDCDBETSP007.
SAP/ISU-CCS Some of the difficulty in supportng the system includes data validatons. SAP is so flexible that users can do many 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
things to cause data issues and problems. These data problems can lead to batch failures or billing errors. The
problem could be a data integrity issue or a failed business rule. Sometmes it is difficult to trace the root problem
because of diferent ways to perform the same transacton. Instead of fixing the root cause, IT has to simply repair the
data. IT must go back to subject matter experts for an understanding of how rates should work; sometmes IT must
confirm how the rate works in CIS. The implementaton is overly complex (e.g. naming standards are not consistent
between jurisdictons).
CTS (Contract Tracking CTS is used to process contractor invoicing. The system is ted to DIS to compare vendor invoices to projected work 1 1
System) and approve invoices. It is only used by distributon. Reconciliaton is completely manual between invoice and work
order.
Work orders are created in DIS that may be performed by external workers. Work is dispatched through DIS; the
invoice is expected from the vendor. CTS acts as an archive for received invoices and correlates against the work
performed in DIS. CTS can also create a dummy record if work wasn't created in DIS.
Users log the invoice in CTS. When a contracted work order is created in DIS, a record is sent to CTS. The DIS record
will contain a vendor code that reconciles with Passport. CTS serves as "middleware" to te together contract
informaton in Passport and work informaton in DIS by using a translaton table in CTS.
CTS exports invoices to pay to Passport. Invoice paid informaton comes back from Passport. CTS has multple levels (2
or more) of approval. CTS contains hierarchy chart for dollar amount approvals. It also has the ability to look at the
contract from Passport for specifically assigned approvals. Hierarchy informaton is completely user maintained by
[CLIENT] IT instead of being automatcally pulled from HR systems.
The system has been audited and has some issues around controls. It must mimic what is done in PeopleSoft AP. Wish
List: Users would like to access images of invoices and te to a record.
Users: Distributon organizaton ( Operaton , Engineering )
Technologies: PowerBuilder 9, Oracle 10g
Interfaces: DIS ,Asset Suite ,PeopleSoft AP (read only), code block validaton
Tools: Some adhoc reports are being created out of Access Database Dump.
Functonal gap: It contains reports but unaware if users are leveraging. Diferent reportng optons are required.
ACSSI Not found 1 1

ACS "The Agent Care System (ACS) was built in 2006 as a front-end for CSR agents. CCS had not been live for many years, 1 1 1 1 1 1 1 1
and agents were having trouble adjustng to the standard GUI from the AIS legacy GUI. CCS did not give agents the
amount of informaton that they needed as easily and quickly as possible. Originally, the scope was a read-only inquiry
system. Scope was expanded to issue work orders, update address and customer informaton, and issue ICLE requests.
Scope also includes preliminary high-bill analyzer.
ACS 1.5 is a portal-based applicaton, but is accessed within CCS. Agents navigate to CIC0 and access through the SAP
HTML control. (Note: SAP recommends not to use the HTML control in the manner ACS was implemented, i.e.
performing session handling and complex applicatons)
ACS is limited in that it is difficult to grant access to people outside of the call center. The security setup is such that
only partcular CCS roles and AD groups can access. The user must CSC agent profile in CCS. As individual people
request ACS, it requires several security groups and users to grant access.
ACS' technical architecture was also limited by the design decision to embed in CCS. Standard web functonality, such
as launching popups and certain controls.
The first ACS release created the portal infrastructure with EAI connectons to CCS through SAP adapters; it provided
read-only informaton with no CCS updates. This release communicated with the WebMethods EAI layer through JMS
technology (i.e. no web services on ALSB). The functonality in this release stll leverages this same technology. The
next release introduced CCS update capabilites and a more simplistc architecture approach. All additonal
functonality accesses CCS through ALSB to EAI. Adding ALSB also exposed services to a broader audience.
ACS 1.5 found a severe architecture limitaton when update functonality was introduced. The system must perform a
""user switch"" when updatng data in CCS. The CSR user id (retrieved through single sign-on of Windows ID) is sent as
a parameter to the service call. The EAI SAP adapter then uses a generic connecton pool with one user id. For some
RFCs within SAP, the update user id is changed directly on the table after SAP is updated to reflect the CSR that
initated the change. For other updates, it remains the generic ID.
CMS - Call Management Avaya Call Management System (CMS) is an integrated analysis and reportng soluton. The Avaya PBX sends events of 1 1 1 1 1 1 1 1
System call routng and switching of the ~23,000 calls each day to the switch protocol interface service of CMS. These events
are used to construct records of individual call details such as buttons pressed, length, Vector Directory Number
(VDN), number of segments (holds, transfers, and other legs of a call) and any other detail that may be important to
understand what is happening during call center operatons. CMS also has metadata that defines targets such as,
answer within 30 seconds, and it records whether calls achieve those goals. Call data is summarized at 30 minute
increments and every 2 hours the data is transfered into the CCO repository data mart and cleared from the database.
The current implementaton includes two CMS servers in a high-available configuraton with both servers receiving
parallel data feeds from the PBX. These servers, CMS-NO (r3entla) and CMS-LR (r3entar), are not currently recorded in
the server database. The collected data and resultng reports are essental to enable monitoring of the overall call
center operatons. Bobby Gant is the current Technical and Operatons Product Manager and Jef Heeter s the
Engineering and Backup Product Manager.
Customer Informaton The Customer Informaton System is a mainframe applicaton that provides a variety of functons for external 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
System (CIS) customers, including account setup and maintenance, service orders, meter reading, billing and payments. The
system began to be replaced by CCS around 2002. However, due to the changing utlity environment around
deregulaton, one jurisdicton ([CLIENT] Texas) was never converted.
Over they years, the decision to convert the remainder of CIS has been delayed. CIS was put into a "sunset" state,
where changes were extremely limited to only those absolutely necessary. However, as other systems evolved, such
as My Account Online, CIS changes were made to provide additonal functonality to Texas customers.
The number of resources available to support the CIS mainframe systems are extremely limited.
Customer Invoicing "Customer Invoicing Management System (CIMS) is a web-based work management system that allows the business 1 1 1
Management System to manage and distribute tasks associated with back office, including unbilled account errors. CIMS utlizes inputs
provided by external systems to streamline the management of both new and returned tasks. CIMS retains and tracks
inputs and updates to allow reportng on individual performance, CCS system trends and the overall status of specific
tasks.
There is a semi-manual process to query CCS for unbilled accounts. The results of that query are copied and then
pasted into a staging table for CIMS. The CIMS applicaton then parses out groups of records appropriate to the
number of hours that an agent plans to work that day. Un-processed records are returned to the database, and then
re-assigned to another agent.
CIMS has very limited functonality in assistng with the correcton of records, and it is not integrated with CCS itself.
This sometmes causes false records to be dispatched to users, and the data to become stale throughout the day."
CICIS Revenue Reportng This is an two part interface between CIS and Peoplesoft G/L. A job on the mainframe exports data from CIS and than 1 1
a job in the Peoplesoft system reformats the data and imports it into the general ledger system. The data that is
exported from CIS is based of table or file changes. For example, if a new town code is created a CIS user must enter
a new line in the VCM file on the mainframe. When the mainframe job runs, it will collect this and other changes and
export it for the Peoplesoft to handle. The job on the mainframe runs once a month but must be called in to be
manually submitted. Informatonal reports also exist to provide details on what should go into Peoplesoft in order to
confirm the transfers.
Support issues currently exist on this interface. Although the individuals are very supportve, knowledge is not
widespread. This can cause issues with resolving issues or questons and has become a concern within the business.
The code can no longer be compiled on the mainframe which limits the methods of resoluton for identfied bug fixes.
Often workarounds must be accomplished utlizing other tools outside of this interface.
Change Request Informaton 1 1

System
Contnuous Emissions This applicaton stores and reports on historical environmental data. 1 1
Monitor Reportng
No longer used for current informaton, but stll actve for historical archived informaton. Replaced by an actve
monitoring system (CEMS) which automatcally gathers informaton. Fossil sends informaton to EPA quarterly. Users
can get informaton directly from EPA.
NOTE: No business survey completed because business stated no longer in use. Recommend retring.
Contnuous Emissions Use StackVision (vendor ESC) to automatcally monitor emissions from plant operatons to be submitted to the EPA for 1 1
Monitor System (CEMS) compliance. Interfaces to data logger that converts data from analyzers in the stacks. Used by all plants; each locaton
has a separate server.
Vendor support agreement; SAIC supports the server.
PI system interfaces to StackVision to gather emissions data.
Must capture 90% of data per federal regulaton. No alarms if data is missing. Vendor has a system to monitor, but
cost prohibitve.
PI (Plant Informaton System) Plant Data archiving tool. 1 1

PI Server Monitor Monitors tags in specified PI servers to ensure that the system is functonal. Visually alerts any issues, and allows 1 1
acknowledgment.
Used primarily by Steve Winsett and Byran Hennesy.
PI Universal Data Service Captures and historizes plant and/or unit control data. Backbone of the entre PI system. Provides the data 1 1
warehouse for PI and becomes the source for all PI interfaces.
PI Interface Bufer Interface into PI from the DCS / DAS systems. Has a built-in bufer. If the PI Server becomes unavailable, the Interface 1 1
Bufer will retain data untl it returns online. If the server is unavailable for such a tme period that the bufer
becomes full (2GB), data begins to overwrite; could be around one week.
Although not used to control the plants, has to be on the DCS network.
Harrison County actually writes data that comes from PPG back into the DCS.
Runs on a PC at each plant. Operatng system depends on version necessary to support the DCS. Upgrades are not
made unless the DCS is changed. PI Interface Bufer is the most critcal part of the PI Architecture and is running on a
PC. Consider, as opportunites allow, hardening the infrastructure and migratng to a more enterprise environment.
PowerHouse Reservaton Epitome Property Management is a product from Hotel Informaton Systems (HIS). The system, which is designed for 1 1
System (PHRS) large hotel propertes, is being used to manage reservatons for guests at the PowerHouse in Jackson, MS. The
PowerHouse is used for management meetngs and conferences and has several rooms available for overnight stays.
Last year, the PowerHouse served 13,000 meetng partcipants, 421 meetngs, 4,600 overnight room stays, and 26,000
meals. PowerHouse rooms are usually booked between 40-48%. The numbers for reports are kept manually offline.
Front Desk and Back Office personnel will use the system to create reservatons and manage check-in and check-out.
Beverly Newton puts the meetng and room requests directly into Epitome and maintains any changes. Beverly also
keeps a paper list of all meetng partcipants and gives the lists to the front desk every Wednesday. The front desk
then enters in the details. Staf performs a nightly audit through Epitome to see if guests are actually staying in a room
or if anything was left behind.
Employees can schedule a stay at the PowerHouse through the travel center even if the meetng is not at the
PowerHouse. Travel center emails Beverly directly. Beverly manages the room wait list on an Excel calendar. There
were discussions to put the availability online for employees to see, but it was not done due to it being too frequent
in changes.
The major issue with the system is that it does not count rooms correctly. When a reservaton is placed, it will show
that the PowerHouse is overbooked (e.g. -3 rooms). Next day, the system resets itself and new reservatons can be
added. Since the system is untrustworthy, manual records are diligently kept offline.
The system also crashes 3-4 tmes per year. Usually it requires a server reboot. The servers resides at Echelon (test
server and producton server). HIS dials into the system and performs any work.
Asset Suite (Ventyx) Transmission uses Asset Suite to approve the payments and contracts. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Asset Suite is one of the most critcal Enterprise applicatons at [CLIENT]. It provides a variety of functonality that
supports various processes in the Nuclear unit. The system is a three-tered applicaton running on an Oracle / Unix
platform. It includes custom COBOL (panel code and data access modules), but the support team feels that it is
straightforward to maintain due to its maturity and stability. Asset Suite uses proprietary technology to distribute load
at the applicaton layer. An F5 router distributes load at the user interface layer, allowing expansion to be easily
performed.
The following modules are currently being used in the Nuclear unit :
Work Management - Asset Suite is used to plan and execute the work necessary to maintain the nuclear plants. Users
create work orders that are then worked within the plant. A group of planners at each site model work orders, reserve
the materials for work, then engage the purchasing modules to get the material to the plant. Planners plan both
short-term and long-term jobs, including outages, preventatve maintenance and electve maintenance. Another
applicaton called Primavera ûinterfaces with Asset Suite and is used to build the maintenance and outage schedules.
Work orders are created in Asset Suite, scheduled in Primavera, and the work order dates are populated back. The
work management module also interfaces with the procurement and inventory management modules to create
demand, reserve / commit material or generate a reorder notce.
Engineering û ûAsset Suite is used to maintain informaton about major components installed in nuclear plants. A bill
of materials includes the subparts that make up components. Each subpart includes a CAT ID which interfaces to the
inventory management module. Design changes are handled through the engineering change process, which updates
both the component database and the bill of materials. This informaton is used for maintaining stocking levels and
taking procurement acton. Each plant has its own procurement and engineering functons, in additon to the fleet-
wide groups.
Acton Tracking û Asset Suite has the ability to create and route acton items. Nuclear uses this functonality to track
acton items such as making code changes and screen enhancements. Also, when an item is sent back to inventory, an
acton is created to track the item untl it returns to inventory. This functonality serves as an interface between the
work management and inventory management modules.
Procurement -- Once a request for materials (i.e. a requisiton) is created and approved, it is sent to the buyer for the
facility. The buyer can then create a purchase order / RFQ within Asset Suite. An alert is sent to the requester statng
that the PO has been issued and can be viewed. Asset Suite populates the purchase order and sends to the vendor
based on the preferred communicaton method (e.g. EDI, fax, or other). Once the material is shipped and received,
the process contnues within the inventory management module. Role security is used to make sure the right people
have the right access to the right transacton. The transmittal process will change with the implementaton of EIPP.
With EIPP, buyers will interact with vendors through Areva.
Contracts û Asset Suite is used to write contracts for services with suppliers. Within the contract, informaton is
captured concerning the scope of work, contract number, dollars, and account codes. This module interfaces with the
NERC NERC Workbooks are spreadsheets providing NERC documentaton calculatons and Operatons data based on the 1 1 1
most current versions of relay settings files in Webtop. There is one to several NERC Workbook spreadsheets for every
substaton in [CLIENT]Æs system. Thousands of NERC Workbooks are stored in Webtop by grid, substaton, and kV
level.
Example:
Arkansas
Dell Substaton
500kV
(folder of NERC Workbooks)
What does it not do?

It is not an automated report based on a relatonal database of relay settings informaton.
Any issues?
Yes. Using large numbers of spreadsheets dispersed throughout file trees instead of using a relatonal database poses
many problems.
Version control is difficult to non-existent. It is practcally impossible to propagate changes to NERC Workbooks
throughout the thousands of spreadsheets on Webtop. Instead, there are at least 17 diferent versions of NERC
Workbooks on Webtop.
There is no link between NERC Workbook data and relay settings files. NERC Workbooks are manually populated with
copy & pastes from relay settings files. These processes are prone to human error and laborious to keep syncÆd.
Workflow to keep NERC Workbook data and relay settings files in sync involves multple tools that donÆt talk, emails,
and manual tracking with more spreadsheets.
Other processes that need synched data output from NERC Workbooks involve emails, manual parsing of data, and
manual copying & pastng. Those processes are prone to human error.
Are there any processes or interfaces that come into or out of the system?
Relay settings engineers design relay settings, transmit relay settings with Remedy (soon to be Service Now), and those
files are stored in Webtop. Another group retrieves relay settings files from Webtop to construct thousands NERC
Workbooks (spreadsheets). After NERC Workbooks are constructed, emails go out to Configuraton Management
personnel who manually read the NERC Workbooks and copy & paste certain data into Facility Ratng Workbooks
(more spreadsheets).
NERC Voltage Reading The OIS Team (Kim Caraway) developed the soluton 1 1 1
Fossil and SoC Business Units seeks to implement a 3rd party software that can be used for PI alarm functonality in
the control room and for Fossil and SPO to get their voltage readings from the same locaton.
Currently, the Fossil plants pull voltage readings from a RTU (Remote Transformer Unit, an instrument that pulls
readings from control systems and converts to digital value) and the SOC pulls the voltage readings from a diferent
RTU. The voltage readings in SCADA are pulled from the SOC RTU. Since all plants do not have access to switch yard
voltages in their control systems the most likely source for accurate voltage readings is the SOC SCADA system. All of
the SOC SCADA voltages are present in the central PI server. The plants currently have the ability to monitor the SOC
voltages via PI but there are no alarming features.
The Alarm Management soluton will pull the voltage readings from PI so that Fossil & SPO will get the same readings.
It will also visible and auditable alarm in the respectve plant control rooms when their voltage reading is out of
tolerance whether high or low.
Exele, 3rd party soluton, will be used for PI alarm functonality in the control rooms. Exele will provide the ability of
alarm detecton, auditable alarms and notficatons, bi directon email & SMS communicaton, remote access and
acknowledgement and mobile web applicaton.
Evaluated 3rd party solutons that can be used for PI alarm funcionality in the control rooms. The proposed solutons
were Alarm Results, Exele and Transpara.
CVM CVM is used as an online vendor re[PROJECT]traton portal, customized to fit [CLIENT]'s requirements, to support two 1 1 1 1 1 1 1 1 1 1 1 1
diferent eforts. The first of these eforts, Supplier Diversity, is supported by collectng spending informaton from
re[PROJECT]tered Prime and Tier2 ($500k spend per year identfied via SART) vendors. Prime contractors are required
to report all of the diverse subcontractors they utlize. This is required per the General Services Agreement with the
Federal Government. CVM supports the safety efort by collectng safety metrics and documents from
re[PROJECT]tered vendors as well. The portal allows contractors to input data points such as REI number, the number
of deaths, ERI rates, etc. Depending on the class of work, they also may need to go through an audit prior to approval.
There is an override capability if the contractor is critcal to a business functon but it requires internal approval.
Overall, the portal works by having contract analysts invite contractors into the system. These contractors will enter
the required informaton into the system and CVM will verify and perform whatever calculatons that are required. If
the level of risk associated with a contractor is low, they will automatcally be approved. Contractors with high risk
require safety analysts to review the data and perform audits as required. Procurement analysts also monitor the data
within CVM and use it to support Tier2 reportng. Tier2
The system is managed by Javier Riascos and he is responsible for confirming the contractors that are invited are
correct. Recent enhancements include dashboards on supplier metrics, allowing management to perform approvals,
and a query package to allow ad-hoc reportng. A new nightly batch dump will allow [CLIENT] to create additonal
reports internally. Overall, the applicaton is meetng the needs of Supply Chain, however, there are a few additons
that have been identfied. Supply Chain would like to have a consolidated vendor re[PROJECT]traton portal and have
CVM integrated with PeopleSoft. CVM has recently been acquired by Altegrity but the implicatons of the purchase
DIS Distributon Informaton System (DIS) is a big and complex system. DIS manages all customer and reliability driven 1 1 1 1 1 1 1 1 1 1 1 1
work that is performed by distributon operatons. The system is tghtly integrated with both Customer Informaton
System (CIS) in TX and CCS in the other states. Work that is requested from the customer flows to DIS and then routed
to the appropriate system and/or resource. In the event of meter related work DIS manages the routng to the proper
work group and Service Suite system handles the assignment and tracking in the field.
Presently DIS has no vendor support but [CLIENT] stll maintains the system efficiently through the original source
code and a good understanding of system. DIS is more than 10 years old, and the last major upgrade happened in
2008. DIS was purchased in mid 1990 from Logica. Logica no longer supports the soluton installed at [CLIENT].
DIS has the following source systems from which it receives the informaton: AM/FM ( Automated mapping and
Facilites management), GDT ( Graphical design Tool), DFM ( Distributon facilites Management), CIS ( Customer
Informaton System), and CCS ( SAP\CCS). The target system is Service Suite where it sends the work orders.
Currently some Design (includes Estmaton Functon) process is stll done in DIS and some in GDT. In March 2013 GDT
got rolled out which has the estmaton capability. However the estmaton process is transitoning to GDT and in
future it will be moved completely in GDT. Presently GDT gets material, labor and overhead rates form DIS.
The majority of work requests are generated from CIS/CCS, with many additonal planned work requrests generated
directly within DIS using spreadsheets. In the future (most 2014 projects) planned work will be automated and directly
entered using GDT. Non-design related work and line area work generates some work requests in DIS as well.
DIS has scheduling capability. Work can be scheduled in either in DIS or DSS (Distributon Scheduling System), with
most scheduling now transitoned to DSS.
DIS is the system of record for all design and non-design related work. The opinion among IT support is that it would
be hard to replace DIS due to all the interfaces to other systems. Some thought has been given to DSS being replaced
with Service Suite for long cycle work. In this case, DIS would stll remain as the data repository and controller of
interactons between diferent applicatons.
Most work which requires less than one dayis not scheduled and is handled manually. 30% of design work is handled
in DIS and 70% in GDT. The non-design works goes to Service Suite. Designs are checked as per regulatory guidelines.
After design is approved it is goes into constructon phase and the crew updates as built in DIS. DIS has the capability
for designers to copy old cancelled jobs and reuse them for design purposes.
Issues/Challenges :
1. DIS is an older system and is not user friendly. Sometme user needs to use the keyboard and mouse and get stuck.
The user interface makes tasks tedious and difficult for constructon people during the as-built process.
2. DIS needs improvements in reportng. Reports are very old and need to modify the reports as per todays need to
reflect the current state of organizaton.
3. A large number of custom reports have been built using Access and DIS Prodquery (e.g. all jobs whose commit
dates expires in next seven days, designer backlog reports, design work in GDT vs DIS, etc).
4. DART reports were built to satsfy internal auditng around design policies. These reports are broken. Leidos is
looking into this. These needs to be fixed.
5. There are not enough resources to support IT.
Technology:
Initally it was bought from Logica. It has been customized heavily over period of tme. Logica is no longer supportng
it. However source code is with [CLIENT] and it is being supported by [CLIENT]. The applicaton has been quite stable.
Database: Oracle 10g
AIRSWEB SIMR 3rd party product 1 1 1 1 1 1 1 1 1 1 1 1 1 1
AIRSWEB safety informaton management and reportng applicaton to Utlity Operatons and Energy Delivery
personnel. The AIRSWEB applicaton will be the data repository and reportng mechanism for all safety events
excluding coaching cards. Additonally, this applicaton will include employee data only. Contractor data will be
incorporated in Phase III.
3rd-party Safety Management applicaton purchased from the vendor Safety Software, Ltd (SSL). In conjuncton with
adoptng a single safety management process, this soluton ofers a consistent process / applicaton to track and
report key safety metrics across the company. This allows a proper and consistent channel to report accidents which
will reduce the multple data sources that are currently being leveraged to produce safety performance results.
Resultng in improved accuracy and tming of data, and reduce the number of individuals tasked today to collect,
enter, track and report this safety informaton.
TCOS TCOS is an outage system used by the TOC to track transmission related outages. TCOS will stay for substaton and line 1 1 1 1 1 1 1 1 1 1 1
type outages after ITC, but outages will be entered by transmission. If there is outage and one secton is stll out, this
informaton will go to the transmission line, substaton and relay group. They will do the investgaton and find out
what caused the outage and enter the root cause into TCOS. The same group will fix the problem and restore it. A
tcket is created in TCOS for every event. It gets number and name from SWMS and similarly it gets line number from
LWMS.
TCOS has its own database and is used by the business to create transmission outages. It has the ability to run reports
and track root cause, etc.
AM/FM distributon outage informaton is pulled into TCOS and associated with the transmission outage, if within a
specified window from the event, through a stored procedure executed every five minutes. TCOS sends back to
AM/FM the initatng major cause.
Interface:
AM/FM
LMS
SWMS
PowerBuilder 12.5
SQL Server 2008
Reports: Canned reports are available inside the applicaton. No reports are outside the applicaton. Paul B is working
on some report. Not sure if these has been completed. The applicaton has capability to exports into excel and you can
create your own report out of it.
Issue/Challenge:
1. In a broad perspectve TOC has also TAORS.AOR is more for planning actvites. If any secton of transmission line is
out, tcket is created in TCOS and then we update AOR to reflect the same. So double entry of informaton is
happening. AOR is for planned outage. ITC is looking at merging the functonality of both TAOR and TCOS. Similar
merger of functonality is desired on [CLIENT] side.
2. Printng of report. At tmes it prints five pages. ItÆs not a big issue.
3. Transacton stability issue: If they build a new secton it will not be there in the system TCOS and we have to call
them to get it added before we can create a tcket in TCOS.
4. There is no user guide to train new resource.
5. Only one resource is supportng it and we have five TOC. At tmes response tme is high , it depends on what type of
request is.
TCOS is an outage system used by the TOC to track transmission related outages. This applicaton will be no longer
ECOS The [CLIENT] Call-Out System (ECOS) is used by dispatchers and other personnel (e.g. supervisors and clerks) to 1 1
determine who are the on-call employees for the various job positons and duty types in [CLIENT]. It is used to create
on-call schedules for the various call-out positons and to track which employees are on the schedule along with their
contact numbers and call-out order. ECOS then tracks the call history for each employee showing various statstcs
about how often they were called, how often they responded, and other pertnent informaton. It is also used to track
the crew performance on call-out. It is a stands alone system.
ECOS is used by all 4 states. The actve user count is around 300. There could be more in the system considering
people retred and moved to other departments.
Schedulers create the schedules and determine the order in which individuals should be called. ECOS tracks the
history of changes to the schedules. It is used in union shops to determine how many tmes call had been turned
down, which may afect raises and discipline. In some cases, it used for legal purposes also. The scheduler is
responsible for understanding any rules on the order of call-out.
The DOC accesses the system to understand who is on call and then tracks the response and tme spent on the job. It
is only used in distributon. ECOS pulls phone informaton from MyIdentty and pulls basic employee data (company,
job code, supervisor, home address) from HRIS on a weekly basis.
Future needs û
1. ECOS to interface with phones.
2. ECOS is heavily manual, lot of data entry and does not automatcally call people. There are lot of manual
interventon which sometme lead to order mismatch and click incorrect number. It gets difficult when trying to make
more than 10 callouts.
3. Field folks have to maintain the schedule and it is not user friendly.
Technology:
Visual Basic 6, SQL Server 2008.
[CLIENT] Call-Out System (ECOS) is a standalone system .[CLIENT] does not have an automatc callout management
system. Business users spend lots of tme in manual data entry. Manual actons lead to order mismatch and incorrect
calls. [CLIENT] needs to bring automaton into the process to avoid such incidents and manual dependencies. The
applicaton is built with old technology, has no data management strategy and no applicaton monitoring system.
DCOS TCOS is an outage system used by the TOC to track transmission related outages. It will stay for substaton outages 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
after ITC.
TCOS has its own database and is used by the business to create transmission outages. It has the ability to run reports
and track root cause, etc.
AM/FM distributon outage informaton is pulled into TCOS and associated with the transmission outage, if within a
specified window from the event. A stored procedure runs against AM/FM every five minutes. TCOS sends back to
AM/FM the initatng major cause.
DCOS is a website that allows users to enter major distributon outages. Records are entered into the TCOS database.
TCOS is also used to manage the users for DCOS, as well as distributon lists for outage notficaton emails. Through
this project, no business owner nor technical owner could be identfied for this website, nor anyone who knew of it
being used.
ITRON "Itron Field Collecton System(FCS) is a meter reading soluton to obtain customer usage from 3.3 million gas and 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
electric metering points each month for billing. The soluton consists of handheld units (model FC300) and FCS
communicaton software. Data is uploaded from FCS to CCS / CIS for whole routes (not for individual meters). AMI
meters are handled outside of FCS. Each night FCS creates an export file for all completed route and the interface
posts to CCS.
Weather related input is used to adjust the expected reading for CCS while validatng the consumpton. CIS works little
bit diferently on the expected consumpton calculaton. The meter reading accuracy is very important. The tool is
working pretty well from estmaton point of view.
Users: Meter readers (contractors), Specialists and supervisors.
Interface:
FCS <-> CCS ( FCS uploads Meter reading into CCS and CCS send routng to FCS)
Issues/Challenges:
1. Recent upgrade of FCS: It had some issues with OS on handheld device which iTron has delayed to install. Team has
a scheduled meetng with iTron to address it.
2. AMR meters: We are looking for some drive by device which can capture more reading than by going and collectng
the reading on foot.
Opportunites:
1. OMR meters: Resoluton of last choice.
2. New FCS handhelds: Capability to take picture and store the meter reading pictures.
3. Save truck rolls on RRHB: If we can access the pictures of the meter reading this can save truck rolls. The current
handheld does have capability to capture the image but does not have capability to store it.
4: GPS co-ordinates on handheld device will help in becoming more productve.
5: Tempering flag counter on OMS meter: The current system does not have any way of capturing the informaton.
Handheld captures it but CCS does not send anything related to past informaton on tempering flag. Some
opportunity is there to integrate with CCS."
TRON has had some issues with the operatng system on handheld devices which iTron has delayed to install. The
current system does not have a good way of capturing the tampering informaton, since CCS does not send anything
related to past informaton on the tampering flag. GPS coordinates on the handheld device would help productvity.
The current handheld has the capability to capture an image of the metering reading but does not have capability to
RT2000 store it.
Distributon Reportng (RT2000) is a PowerBuilder reportng system with a Report Hierarchy Viewer. It serves as the 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
reportng base for Operatons Management, MDT, Distributon, Lamp Street Light and [PROJECT](AM/FM DFM). Most
reportng, however, is being migrated to web based in-house reports and Cognos.
LAMP specific canned reports are getting generated out of RT2000; however, more reports are required to manage the
business process. There are currently 24 canned reports, and business believes they would need another 10 reports
out of RT2000.
AM/FM DFM reports have moved to in-house web based reports.
Technology: SQL Server 2008 (Not Sure) , Power builder 5.
RT2000 does not house any data; it connects to the individual applicaton database to create the reports.
Interface: It does not have interface to other applicatons for data, however it connects to individual databases to pull
informaton for reportng using PowerBuilder database connecton.
Users: Though database has 2000 users, not all of these are actve users. Probably 300 to 500 are real users.
Issue/Challenges:
1. The platform is not standardized for UDW ( Utlity Data Warehouse).
2. The reports are out of date compared to the needs.
Outside of the team there is no Power builder 5 expertze.
AMI-ITRON Considered Smart meters, provide remote meter reading capability as well as communicatons to energy efficiency 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
related devices. Cellular based used in LA for targeted deployement
AMI-ELSTER Considered Smart meters, provide remote meter reading capability as well as communicatons to energy efficiency 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
related devices. Used in Baton Rouge and ARK for irrigaton load control
Store Catalog System is not being used but needs to be decomissioned. No business or tech interview necessary. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
IHD Commonly employed in associaton with AMI/Smart Meter installatons.á They are dedicated to providing customers 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
informaton about their consumpton and billing.á They communicate from utlity internal systems through a metering
infrastructure to the device located with customer homes.
HAN Devices Used as part of a Smart meter/AMI implementaton.á Includes but not limited to PCTs, IHDs, and switches used to 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
manage customer consumpton.
ENOI DOE AMI Pilot [CLIENT] New Orleans, Department of Energy funded pilot utlizing AMI Meters and HAN Devices. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Material Tracker This system helps determine what material was recently ordered and when that material will arrive. The system 1 1 1 1 1 1 1 1 1 1 1 1
reports the "need date" and the "expedited date" for material orders. The system interrogates tables in Indus Asset
Suite for purchase orders, category ID, work orders, jurisdictons and checks which material has been ordered for a
partcular work order. The report provides details about the purchased items for a work order. The informaton is
available in Asset Suite by accessing multple screens. However, it was determined that an outside system would be
more efficient.
For engineering project managers, this system provides a simple tracking mechanism to monitor materials ordered for
specific work orders associated with specific projects. Project Managers look at the report to confirm that all the
material identfied was ordered, that the dates confirmed by vendor match the latest project schedule, and allows
them to monitor materials that are expected to arrive for their job. This informaton is also used to ensure that
contractors are lined up to work at the tme specific materials for the job arrived. At the end of the job, a report will
be generated in Excel that will print a copy of the order with an additonal "material returned" field. This report is
emailed to storekeepers who print the report, who will keep it on file. When storekeeper receives unused materials,
he will place those items back in inventory via a "return" transacton in Asset Suite which then credits the job for
which it was ordered. This system is also used by employees in the project controls group to monitor costs. In
partcular, they monitor long lead tme materials such as breakers and transformers (typically lead tme is measure in
weeks and costs are hundreds of thousands of dollars). The project cost controls team is monitoring estmated and
actual costs for these larger items.
IKW Reporrtng This IKW

The system is in theTool
Reportng midst of a re-write
consists as it is deemed
of two separate very inefficient
executables, and lacks
IKW Summary and certain functonality.
IKW Report Tool. IKWThe system runs
Summary runs 1 1 1 1 1 1 1 1 1 1 1 1
20-30 queries nightly for a set user list. These queries include, contracts expiring in 90 days, requisitons open, etc.
The data collected from each IKW query is deposited into an Access database. The set runs around 1AM under
Kamie's user account on her desktop via task scheduler. She was forced to use her own account to run the summary
reports because she has not been able to get a generic ID for it to run under. The password for her account is stored
in a password protected Access database. The password value itself is encrypted using third-party encrypton utlity
with an unknown algorithm.
The Access database holds employee informaton (hierarchy), reports definitons, and user list. Its located on a shared
drive:
metnc\ebs_procure\sctt\ikwtool\database (Access database)
..\SQL (SQL queries used to get IKW data)
Installaton:
\\metnc\ebs_procure\ikw_reportng_tool\setup.exe
The IKW Reportng tool is a dashboard that has two modes. Normal employee will only see their specific metrics.
Managers and directors will see hierarchy of their direct reports. The inital view is summary metrics but the
applicaton allows you to drill-down into the specifics by double-clicking on each indicator. This applicaton is installed
locally on desktops via an standard Visual Studio installaton package that is not distributed with ESM. No SAIC or
other IT support is available for the installaton package. Detail reports (drill-downs) are executed using the end user's
IKW IDs. These detail reports are displayed in a grid form which can then be exported to Microsoft Excel, if required.
The applicaton is available to all Sourcing and Supply Chain personnel to releave work from Marketng Analysts. It is
primarily used as a productvity tool to assist users in managing their work load.
After the implementaton of Asset Suite, several business processes were under supported. Due to resource
constraints and budget issues, both within the business and IT, the business developed small, "one-of" reportng and
tracking systems. Some of these systems were developed because although the informaton could be extracted from
Asset Suite, it was deemed complicated relatve to creatng an additonal system to provide the same informaton
quicker. Although Indus Knowledge Warehouse contains a robust set of informaton regarding inventory, purchases,
AIMM AIMM implements processes for maintenance management. manages component facility data, work requests, 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
preventve maint tasks, schedules, materials orders and contractor work.
All contracts and purchase reqs are initated and approved. Has outage cost tracking capability. Extensive reportng
capability in reportng tool. Track correctve work vs. preventve maintenance.
Only app for Fossil with SLA. 99.6% availability with Saturday night outage window.
Interfaces: Powerplant for projects, financials for data, budget system, Passport for contracts, Passport for materials,
account validaton module, tagging system, technical drawings, reportng tool, Outlook for notficatons.
AIMM is fossil's primary system to support its day-to-day operatons. AIMM is a very old, mature, and highly
customized soluton that is well integrated into most employee processes. The primary strategy for AIMM should be
to: 1) perform housekeeping tasks on the system as some have indicated performance/stability problems, 2) expand
AIMM's use both in terms of leveraging capabilites already inherent in the applicaton as well as integratng additonal
functonality currently served by a number of "one of" applicatons developed outside of AIMM. This expansion of
AIMM should be performed by carefully examining the capability in each "one of" applicaton and determining the
best method for integratng the capability into AIMM and 3) ultmately, [CLIENT] will likely achieve long term benefits
by leveraging an integrated, enterprise-wide, [PROJECT]soluton. The case for such an acton should be re-evaluated in
3-5 years.
Need to identfy business champion.
Given that the proposed future state of Fossil's environment will be centered on an asset work management suite
(Ventyx), decisions to modify AIMM should keep that end goal in mind (i.e. changes should be made in a way that will
facilitate / improve migraton).
Windows 7 - PB versions. Fundamental change to architecture and support skills.
GSCADA Telvent system used to monitor and control in real tme the Gas distributon system in both New Olreans and Baton 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Rouge. True SCADA system swith communcaton to the field gas substatons that monitor gas flows, pressures, etc.
-----------------------------------------------
Gas contol in New Orleans and Barton Routes
-----------------------------------------------
There are no changes planned for future.
There are no system outside of the system . Reports are coming out everyday. On a daily basis data from reports put
on to a spreadsheet and is being sent to everybody. Nominatons are made based on these reports.
More informaton from RTUs through SCADA is required. This will help us in making more efectve decision.
SCADA system is a robust system.
MODBUS protocol is used for communicatng with RTUs
Any other system on top of SCADA ? No
Patch afects the SCADA configuraton earlier now has been smoothed out.
Running out of sapce issues some tmes.
No functonal issue , it does how it's supposed to use.
SCADA The SCADA Alarms database tracks the SCADA alarm on basis of priority 1, priority 2, or priority 3. Priority is defined 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
based on the type of alarm. Priority of alarm decides the completon tmeline of the work. The DOC sends the alarm
informaton to the substaton and supervisor through emails on daily basis. The substaton crew will take the decision
on alarms and when to attend the problem. When the crew fixes the issue they inform the DOC, and the DOC updates
the status of SCADA alarm Data base.
This system is currently only used by Mississippi. How other jurisdictons are handling is not known.
Supervisory Control and Data Acquisiton (SCADA) is the control system that is used to detect outages at sub-statons
in real-tme.
User Group: DOC
Reports: It has in built reports. Reports are based on priority. Report on diferent area north, south or central. Report
on alarm that has been corrected /not corrected.
Issues/ Challenges: Normal access DB challenges.
Interface: None.
The SCADA Alarms database tracks SCADA alarms on the basis of defined priorites which decide the completon
tmeline of the work. This applicaton is built on Access technology and is marked as high database risk. The
applicaton can be ratonalized over tme to the DMS program. DMS has the capabilites to categorize and prioritze
alarms and notfy alarm details automatcally to the concerned groups.
SwitchMan Switchman captures switching and clearance certficaton for [PROJECT]grid employees and contractors that perform 1 1 1 1 1 1 1
switching or clearances. The system is used to identfy a switchman for outages and to make sure their certficatons
are current.
Switchman is a web-based applicaton. Supervisors enter and maintain certficatons. Anyone can view informaton,
but only supervisors can add/edit. The system contains name, address, phone, certficaton, valid dates, etc. A job
runs weekly to bring in valid employee informaton, which is used for lookup dropdowns.
Certficatons can be for distributon or transmission.
When an outage is upcoming, users lookup who is available and is certfied to make a list of candidates. Switchmen
are assigned to substatons. The system provides basic reportng to apply criteria and find switchmen.
A job used to run nightly to email supervisors of expired certficatons; however, it was disabled in March 2013. (The
support owner was unsure of reason). Users can manually send an email through the webpage of expiring
certficatons.
A business case was presented in 2012 to replace with Vision. However, it was not approved due to lack of support
and other critcal initatves.
Interfaces:
PeopleSoft HR (user id, part of SSN)
SWMS - substaton informaton
Technologies:
ASP
SQL Server 2008 (including stored procedure batch jobs)
Switchman Database is implemented with retred technology. In 2012, a business case was presented to replace with
Vision. However, it was not approved due to lack of support and other critcal initatves. As the users have already
shown interest to replace this applicaton and as a work management system provides capabilites to store all the
details and certficaton of users and monitor them to alert as a standard practce, Switchman Database can be
ratonalized to the work management program.
Logility IPS is a COTS applicaton that optmizes the planning and forecastng of T&D material inventory levels to reduce the 1 1 1 1 1 1 1 1 1 1 1 1
cost of inventory on the books. It also ensures inventory is available on seasonal and periodic needs. IPS is used by
~12 users in Brian Duckett's group.
The applicaton consists of 4 modules. Demand Planning contains 36 months of historic demand informaton that is
extracted out of AS by CatID. There are ~47,000 cat IDs in the big 10 facilites. The output of this module is a 12
month forward looking forecast. This is determined by looking backwards to determine how well previous forecasts
performed versus the actual usage. Seasonality, growing or declining trends in demand, etc are all used as models. It
also supports a manual override if specific or expected conditons are known.
The second module, Inventory Planning, uses the forecast to develop specific orderings for the materials. CatIDs are
categorized into A/B/C with A being the highest demand and turnover. The goal is to develop a plan for each CatID
based on the forecast and prioritze by their ratng.
The third module, Replenishment Planning, pulls in on-hand inventory from AS. This module determines how much
to buy which is then pushed back to AS.
The final module, Performance Management (Control Tower), provides a reportng and performance indicator
capability. It is not currently used because it required additonal programming and consultng tme to get
implemented. Its redundant to what Frank Burgess has already done with the IOT Access database and schema
mappings.
The version deployed at [CLIENT] is a thick client versus the newest version which is 100% web based. Our current
version is difficult to navigate but in Q4 2012 version 8 (web-based) is scheduled to be implemented which should
resolve those issues.
Configuraton and customizatons are complicated and difficult to work with and there are a lot of batch jobs
necessary. Most current issues are around the interfaces between IPS and Asset Suite.
IPS provides important capabilites to the Supply Chain organizaton by optmizing inventory management. As such,
FALLS this applicaton
This applicaton should be data
takes the sustained in EZNav
used in order for
andit plots
to contnue to support
lightning this process.
strokes using In thetools.
spatal query mid-term,
This isan upgrade
used to is 1 1 1 1 1 1 1 1 1 1 1
determine if the lightning strokes are within [CLIENT]Æs design parameters. FALLS Server is used by the user to track
and analyze lightning strikes in the [CLIENT] areas. Six month ago it was using an applicaton called EZham but is now
using a version of [PROJECT].
Users: Transmission line groups, Distributon organizaton uses it.
Custom built Tools: No
Issues, pain points: None
Enhancement: Moving to a newer version of platform coming from vendor.
Critcality for distributon and transmission: There is a diferent level of critcality but it is not very useful for
distributon. It is because of the special nature of lightning.
[CLIENT] has to pay for $100,000 per year for lightning map. Distributon would probably move to a lower level of the
lightning data that would cost lower. This would provide less accurate level of lightning data.
FALLS is used to determine and analyze lightning strikes. This system is used only for transmission lines. FALLS is not a
very useful applicaton for distributon because of the special nature of lightning. Every year [CLIENT] has to pay for
lightning maps. After ITC spin of distributon will not need this applicaton, so at that tme it can be reclaimed.
PEN Pen Manager is a home grown SQL database. Pen helps IT manage associated Panasonic and hardware components. It 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
provides functonality needed to track failure and placement history of all Panasonic assets used in distributon and
transmission. It also allows IT to enter and track user to Panasonic to air card assignments and reassignmentsIt
maintains the ownership of the computer service tag, the air card serial number and the person assigned.
Pen provides details that PC Asset Manager (PCAM) does not allow.. However, the exact limitatons of PCAM are not
remembered at this tme.
Issue: None
Interface: Standalone
Technology :
Data Base: SQL database
UI - Classic ASP
18 months old.
Pen Manager has the capability to track failure and placement history of all Panasonic assets used in distributon and
transmission. This system is built on less than optmal architecture, such as Classic ASP. The technology is marked as
the retrement directon. There is no strategy in place to maintain database state of health and applicaton monitoring.
Pen Manager does not have any DR strategy. This applicaton needs to be ratonalized to avoid these risks.
The system need to partcipate in a larger inventory management program. [CLIENT] requires a system that would
provide an optmized way of doing things through a controlled approach in [PROJECT] This applicaton can be
ratonalized to an enterprise soluton which will help in better tracking of these assets. Due to specific nature of this
type of devices, [CLIENT] needs to look at if this could fit in distributon [PROJECT]or consolidated with other PC
[PROJECT]
SQRT "This applicaton allows asset planning engineers to accurately track and maintain metered demand and equipment 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
informaton for substatons, substaton transformers, and feeder circuit breakers. SQRT is the primary tool that
planning uses to develop load forecast And is the data source for several pieces of critcal informaton to build the
model. It helps in growth forecast, weather normalizaton, and power factor input. SQRT is official store house for the
under frequency / under voltage load shed and black start maintenance programs.
SQRT contains informaton about substatons. EA (Engineering Analysis) accesses informaton in SQRT about breaker
relays and source impedence to create its extracts for Synergee.
Users : Planners, [PROJECT]for programs such as load shed program, ALT ( Automatc load transfer), capacity,
Transmission planning uses it based on distributon planning or load forecast.
Interfaces:
EA (Engineering Analysis) pulls info from SQRT
SQRT accesses STP( Substaton Transformer Profile)data
SQRT gets informaton from AM/FM (Customer Count)
Technology: VB 6
Vendor applicaton is built on top of SQL Server database.
COTS
SQL Server 2008R2
Issues/Pain Points:
It's a manual pull of feeder data from Pegasus to forecast load. It would be beneficial, if this can be automated. SQRT
holds all critcal informaton. This is kind of brain to engineering analysis for load forecastng.
Impendence data - manual feed into SQRT from Transmission planning ASPEN Model. This needs to be automated.
Pulls customer count informaton from AM/FM. There is a lot of opportunity to get data from other system and
provide data to other systems/groups.
Customizaton Tool :
1.Weather Normalizaton spreadsheet( Weather normalizaton and growth rates based on historical load informaton)
2.Feeder peak capture spreadsheet : Planners use it for finding the peak by comparing or extrapolatng other phases
load.
Adequacy of IT support : Break fix is excellent but IT does not have overall understanding or big picture or business
use of tool. It could be because it's an engineering tool and it needs deep understanding of the tool."
Substaton Querying and Reportng Tool (SQRT) allows asset planning engineers to accurately track and maintain
substatons and equipment. SQRT is the primary tool that planning uses to develop load forecasts. The system can be
ratonalized to a DMS program where all engineering analysis can be performed in one system.
Tactcs Tactcs Query Extract Tables is similar to the Outage Query applicaton. The functonality of Tactcs is reportng. In 1 1 1 1 1 1 1
Tactcs, reports are created on historical outage data. It is used to run Arkansas Outage reports (Summary Outage
Report, Detail Outage report by Region, Networks, Types of outages, Roughly 20 reports). It copies certain tables from
the AM/FM Oracle servers and copies to flat files on an Arkansas server. Data is copied only on Wednesday at noon.
There is no front-end as part of this system.
Users: All Arkansas Distributon Supervisors, Directors and region managers. The reports are used by Arkansas only. It
was created about 10 years ago. This tool was originally created by Don West. After Don Left the company user id and
password is missing. So we do not have access to the source code.
Technology: Front End: Web tool, SQL Server 2008, stored procedures. When new tables or fields are added to
AM/FM, must make changes to Tactcs.
Interface: AM/FM
------------------------------Work Mgmt. Reportng System ------------------------------------------------------------
Work Management Reportng System: This is a reportng system for the entre jurisdicton. The reports are based on
all the design work for four jurisdictons. This captures the schedules and puts out reports. The intent of work
management reportng system is to find out if network needs more resource i.e. for work load balance. Based on the
reports planning and preplanning actvites are carried out.
User Groups: The typical users are Network Supervisor and Distributon work mgmt. Employees.
Technology: Front end - Web Tool, Backend: Access Database
Interface: Work Mgmt. reportng Tool <-- Prod Query Table (DIS)
Issues/ Difficultes: It is run manually. Scheduling reports in the tool are inaccurate. However backlog reports are
accurate. Presently there is no performance issue. There is no need to adding any more reports into the tool.
------------------------------Scheduling Reportng System ------------------------------------------------------------
Scheduling reportng Tool: This tool runs scheduling efficiency reports. It finds out what was planned for two weeks
period and how much has been executed. This is only for Arkansas and other jurisdicton does not have it. Scheduling
reportng comes out biweekly basis. This tool was created in the beginning of January 2012 but currently [CLIENT] do
not have source code and we are not able to run it now after October 2012.
Users Group: Network Supervisor, Distributon work mgmt.
Technology: PDF report comes out of access database. Database is same as work management reportng tool.
Interface: Work Mgmt. reportng tool database
The functonality of Tactcs Query Extract Tables applicaton is to create outage reports from outage historical data
ISON The ISONE Database is a MS Access database which is used to assemble the ISONE Settlement informaton with an 1 1
end result of the ISONE Reconciliaton spreadsheet. The ISONE Settlement daily files are placed onto the ISONE FTP
Server which the user manually pulls the daily files down onto the [CLIENT] Server. Once the daily files have been
placed onto the [CLIENT] Server, the user opens the ISONE Database and uses this MS Access database to import the
daily files into the database. The ISONE Database will assemble the daily files that were imported into a single
calendar month file. Once the calendar month file has been created then the file will be exported into the ISONE
Reconciliaton spreadsheet. This spreadsheet is used for the use of the ISONE Settlements. There are User desknotes
for the documentaton on the ISO NE Database.
AIS 1 1
SAISO SAISO is an outage reportng system for CCS customers. All customer data is sent via EAI from CCS and stored as a 1 1 1 1 1 1 1 1 1 1 1 1 1
copy in the SAISO database. Used by call center agents, but also by DOC to generate emergency requests and as a
backup to AM/FM.
SAISO was created from the AIS outage code. However, it is maintained as a separate applicaton. Two databases,
similar to AIS architecture, are replicated and load-balanced via an INI file.
Agents also use SAISO for quick searches when they cannot find the data in CCS.
In 2012, outage communicatons were enhanced to provide proactve alerts to customers based on real-tme
informaton. Existng interfaces were enhanced and became more complex.
In 2013, SAISO was enhanced to send re[PROJECT]traton of customer for text from the applicaton to Notfi.
SAISO will soon be moving to a later version of PowerBuilder.
SAISO is an outage reportng system for CCS customers. This system is built on less than optmal architecture, such as
Power Builder 7, and scores high in architecture risks. Once the CIS conversion eliminates the need for AIS, this system
will become very costly, as the AIS infrastructure will be necessary for only SAISO. At the same tme, additonal
functonality gained through the SAP upgrade should provide a means to ratonalize the system.
This applicaton has to be ratonalized to avoid these risks. This system should contnue to be maintained in its current
design, but it is recommended that this system can be ratonalized with a Work Management program for reportng
outages.
LodeStar Client Server Lodestar is a COTS package used for manipulatng interval data. The system gathers interval data and 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
performs analysis for cost of service, rate cases, and system agreements. Client Server Lodestar is used by Customer
Load Informaton for performing analysis of tme series data (Interval Data). The C/S Lodestar database also holds the
billing data for Major Accounts Billing.
Data points may be massaged in BEX and returned to Lodestar. Logs are monitored to identfy errors and users
receive manually generated emails notfying of data issues that require correcton.
Users can perform ratos, aggregaton, and sample analysis within Lodestar. Requests are received for domain analysts
analyze rate classes by revenue codes within rate categories.
Loaded data goes through a validaton process. Parameters can be set to determine the quality of data. Data not
meetng set parameters will load as invalid data sets. Correctons are then made in MV90 and the data reloaded. The
COTS contains around ten customizatons. Most exist within the batch loading system.
The Load Research System feeds data into Lodestar.
Interval data processing systems are currently built around Oracle's BillingExpert and Lodestar systems. The version is
becoming antquated, and Oracle is restructuring licensing such that it is more costly. A number of systems have also
been developed internally to extend the functonality ofered by the Oracle tools.
It is believed that the functonality of these systems can be provided by SAP's Energy Data Management (EDM) and
other modules. It is also believed that the functonality provided by the current interval data processing systems will
be very similar to that needed for AMI; however, the current system infrastructure cannot support the volume that
even the AMI pilots have introduced. A new platform should be chosen that can address current and future needs.
It is recommended that, once SAP is upgraded to ECC 6.0, a ratonalizaton study be conducted to determine whether
MV90 SAP's
The MV90AMI and interval
system data
is used to soluton, along
collect and with other
prepare applicatons
interval in data
usage meter the standard architecture
for residental, patterngovernmental,
commercial, (such as UDW 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
industrial and wholesale customers across all [CLIENT] jurisdictons. The interval data is used for large power billing as
well as load research analysis. It receives the monthly consumpton data from meters and loads the informaton to
Lodestar.
MV90 has a capability to read the meter format. MV90 is an Itron product which receives informaton from the meter
and sends to Lodestar. It collects interval usage meter data every 15 min of interval.
Presently MV90 is more than 10 years old and has a problem of searching informaton. IT Support took over support
from the business three years ago. The database archival process is stll being handled by business team. Itron has
recommended certain changes/upgrades to be made, but it has as not been implemented yet. There is no data
management strategy in place.
There is no way to build business logic to do validatons in MV90. The business has to do many manual validatons on
meter data but presently does not have the capability to do the validaton at customer account level.
Itron AMI meters are present in every jurisdicton for large power billing. Right now metering is not in this conditon
to handle a full AMI implementaton for the organizaton. MV90 cannot handle the volume of data; it was built for
weekly (not daily) data.
Version:
Presently [CLIENT] is using MV-90 XI version 2.0 SP1 and vendor support is available.
Database:
Database used is called æPervasive - Version v9.5. The latest version available now is 12 or 13.MV 90 has Disaster
Recovery in place.
Recent Changes:
Six months back [CLIENT] internal team conducted a security audit and as per the audit recommendaton few changes
have been made. No performance degradaton observed after the security changes.
Report: Reportng capability is not good in MV90. Business access data through SQL query.
Interfaces:
Itron FCS û Receives meter data directly from meter.
Itron Smart Link - Collects the consumer load informaton and monthly consumpton data.
Loadstar û Receives meter data from MV90.
CCS û MV90 pulls customer informaton from CCS through nightly batch process.
CIS - MV90 pulls customer informaton from CIS through nightly batch process.
No interface to outage management
Issues:
1. Out of date on pervasive database.
2. The current version of MV 90 is 4 and presently we are using version 2.
3. MV 90 has a large amount of manual process for users (data operaton point of view).
4. MV90 is system of records, but some of this informaton is fed manually into other systems which cause error.
5. MV90 does not run on windows 7.
6. Troubles with meters on phone line, we are facing lot of communicaton issues. Sometme for the resoluton of
problem MV 90 needs a manual interventon.
Smart Meter: We have total 700 smart meters.
Functonality wanted:
Servm No Informaton found 1 1
Streets & Trips Streets & Trips is only usedby meter services to help them route tmeter reading. It provides another means to route 1 1
on a graphical mode. This is user friendly compared to Garmin GPS. Garmin GPS routng is complicated.
Users: Meter Services and Data maintenance
Interface: Stand alone
Issues / Pain points: Address associated with customer is not accurate.
--IT support---------------------
Nobody is maintaining the license pool. We are discouraging users to do it. IT does not advise to install it.
Microsoft Streets & Trips is a standalone applicaton and plays a functonal support role in Meter Services. Presently
the system is having an issue that addresses associated with customers are not accurate. It is recommended that this
applicaton be ratonalized to a standard [PROJECT] program and then reclaimed.
TMS Transacton Management System is an applicaton for remittance processing. It is the payment hub for all payments 1 1
received and helps in cutting down the total expenses for processing the customersÆ payments. The applicaton is
supported by the Finance Business Unit. It is a meter to cash process. It is a vendor applicaton (Trans Centra) provided
as a customized package but primarily in-house supported.
The applicaton accepts customerÆs payments primarily in the form of checks received via mail. This is managed by
resouces who open and process the mail. It allows the users to process (recognize) the checks used for the payments.
After the checks are processed, payments are posted to customer accounts. Occasionally, some discrepancies are
found with bills not matching with amounts, etc. TPPS pulls informaton from the CIS and CCS systems and sends to
TMS.
The TMS system sits on Archive Database, ECS Database and CMI Database. It also updates TPPS and CMI. There is a
standard daily backup and a fully tested applicaton recovery strategy in place for the applicaton database.
CMI is used to figure out what BU the Utlity account is associated with. It creates files and sends them to Cash
Operatons to facilitate movement in the PeopleSoft systems. Also, it pulls reports from the auto debit banking
accounts. It has additonal tools: TMS Enquiry and TMS Netquery to pull up copies of checks. They are being updated
as of now.
The number of users using this applicaton varies during the day and night. There are 3-4 users for this applicaton in
the day and 1-2 users at night. There are a total of 4 checks processing machines within this applicaton. The scope of
this applicaton is primarily around the mail-in payments. The applicaton gives the operators/ users the chance to
manually review and correct the errors that the machine cannot recognize. The TMS applicaton has been in place for
the last 4-5 years.
FLEET This critcal
FLEET applicaton
Inventory is serving
Reportng createsthe business
Excel needs as
spreadsheet originally
reports fromplanned and isdata.
the Cyndrus undergoing enhancements
The reports already.
are generated and It 1 1 1 1 1 1 1 1 1 1 1 1
automatcally emailed monthly.
FLEET Inventory Reportng creates Excel spreadsheet reports from the Cyndrus data. The reports are generated and
automatcally emailed monthly. Business leaders have shown concerns around the in-house built applicatons around
Cyndrus. There is no formal DR strategy plan for this system. The technology ASP is marked as the retrement
directon, and this applicaton scores high in database and operatonal risks. It is recommended that this applicaton
can be ratonalized in into the new Fleet [PROJECT]system.
PERFMGR None 1 1
IVR The IVR is an in-house, customized package used to provide menus and optons to customers during calls. The goal of 1 1 1 1 1 1 1 1
the IVR is to contain and answer as many calls as possible. The IVR includes functons such as account lookup, balance
inquiry, automated outage reportng, and other simple tasks. Currently, calls to CCS are performed via a mixture of
RFC and web service calls.
Overall, the IVR should be sustained as part of the integrated call center soluton. However, the data interfaces to SAP
should be re-architected to use standard connectors and services after the upgrade to ECC 6.0.
OSMOSE None 1 1 1
Plateau Used by all of Nuclear as the repository of all nuclear training. Replaced On-track. There is a Analytcs component that 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
runs from the same Web server as the Plateau applicaton. The Analytcs component uses the PLATDWPD database.
Used to manage project manager training and qualificatons

ò [CLIENT] uses several training platforms (Nantel, Plateau, Webtap) to manage personnel training and qualificatons.
The portfolio soluton should leverage these systems for project managers to rapidly be able to determine training and
qualificaton status for all personnel assigned to the project team as well as the CFAM to manage PM Dept training
and qualificatons.
Pegasus - PDC Pegasus is used to track what is going to fail soon to plan and perform maintenance work. All of the Pegasus 1 1 1 1 1 1 1 1 1 1 1 1 1 1
informaton is obtained from the EMS system (SCADA). This informaton is then interfaced to SWMS via the
DSS_SWMS interface from Pegasus.
Pegasus Data Collector (PDC) is a critcal subsystem of the Pegasus RDS Platform which executes, in real tme, on
Enabled and Standby EMS hosts (Critcal Cyber Assets). PDC runs under Habitat and transfers data to Pegasus Data
Servers using pdMarshal and pdRecon. PDC maps SCADA database objects (Analogs, Limits, Points and Accumulators)
to Pegasus Invariant Keys and collects/bufers, in real-tme, all SCADA Numerical and Event data.
Subsystem that collects and bufers SCADA and Event data on EMS Hosts.
Pegasus - Explorer Desktop Client that provides scriptable access to historical SCADA data sets from the Pegasus RDS Platform. The 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Pegasus Exporter enables users to execute large, load-balanced æbackgroundÆ data requests for thousands of SCADA
Objects spanning weeks, months or years with defined resultant data sets easily imported into Excel, Access or SQL
Server.
Pegasus - Smart Client Desktop Client that enables Exploratory Data Analysis of 360,000+ SCADA Objects and Alarms stored and managed by 1 1 1 1 1 1 1 1 1 1 1 1 1 1
the Pegasus RDS Platform. The Pegasus Smart Client also enables High Integrity Audit Trails of SCADA DB histories,
EMS Node Failovers, and myriads of actonable reports based on Alarm Actvity.
Provide client access to near real-tme and historical SCADA and Event data. Customers are primarily outside to
operatng arenas.
Plot Log None 1 1

ENGINES None 1 1
DriveCam "A combinaton of cameras and managed services are provided by DriveCam to record driving behavior. A porton of 1 1 1 1 1 1 1 1
Distributon and Transmission vehicles have a DriveCam camera mounted on the windshield. In the event of a hard
braking, quick acceleraton, accident, or other events, the camera records forward looking and the inside of the cab of
the vehicle. The data is transferred to the DriveCam service center after hours via a cellular connecton. [CLIENT] then
pays DriveCam monthly fees to review the events, provide images, recommendatons and metrics. Safety is the #1
focus of this system. Cameras are part of the packaged service provided by vendor. Data is [CLIENT] owned but stored
on vendorÆs server.
There is 100% vehicle coverage for meter services. For other departments, [CLIENT] rotates the cameras from truck to
truck based on supervisorÆs discreton. All costs are paid from the business budget.
Technology: Front end: n tred Architecture. ItÆs built in ASP. Backend: SQL
It's a cloud based applicaton (SAAS). The informaton is updated to cloud. Individual drivers and managers can access
the informaton from cloud.
Lot of Analytcs available.
Issues / Challenges - None
Reports: No additonal reports as of now.
Important Point: We have some old camera Wi-Fi and hot connected cameras. Since business is not using old
infrastructure and is using cellular network we have to take old infrastructure out."
This applicaton helps [CLIENT] to maintain the safety of their employees by monitoring the driving behavior. It uses
cloud based technology and has ample analytcs available. It is recommended to sustain this applicaton.
GADRS The GADRS applicaton provides a means to collect generaton and unit outage data primarily for reportng to NERC. 1 1
Many additonal reports are available within the applicaton to analyze performance levels from the system level down
to the unit via IEEE statstcs.
Interfaces: Exchange/SMTP (notficatons)

Note: Failure Analysis is a process embedded inside GADRS for each event. Two types of failure analysis.
Boiler tube failure report (BTFR) based on design from EPRI manual to capture root cause analysis. Originally a word
template; fit into GADRS to leverage event capabilites. Also has follow-up actons. Plants can elect not to use this
functonality. Could replace trending and analysis intended in AWARE.
Other type is a failure mode analysis; for component and piece part allows certain generic failure modes to be tested
against evidence collected. Failure mode tables built from common failure modes from INPO. Also allows attachment
for large analyses, such as vendor involvement or cause mapping.
It is expected that within the next year NERC will mandate requirements around GADS systems. Due to standardized
informaton and reportng, GADRS would require significant enhancements. This opportunity should be taken to
investgate implementng a standard COTS tool, thereby transferring the risk of changing compliance requirements to
the vendor.
SuccessFactor None 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
SharePoint - SPO SharePoint is used for, but not limited to, sharing informaton, creatng training plans, and storing records. 1 1
SharePoint - SubstatonAM None 1 1
SharePoint - Line This database is really a spreadsheet within Sharepoint. It is TransmissionÆs single source for transmission line 1 1
Impedance Database impedance data. It also contains some additonal informaton for transmission lines. And frequency informaton stored
in the PLC database is being merged into the Sharepoint Line Impedance Database.
Any issues?
This database is fairly new. We are stll working out some process issues with regards to when, or how far ahead of
tme, new transmission lines are added to this database. Presently, there are people who needs records for future
transmission lines in this database at a tme when the keeper of the database isnÆt ready to put the line in there.
Are there any processes or interfaces that come into or out of the system?
Freq.pl needs to be modified to read this database.
Relay settings people use data in this database to generate Aspen models of the system. Planning is also a heavy user
of this database.
SharePoint Develop an integrated document and project collaboraton soluton with archives for closed or cancelled projects. 1 1
WebTARRS An in-house applicaton developed to calculate Temperature Adjusted Ratngs based on the Temperature in the next 1 1
Hour and Day.
There is a manual process to get the Facility Ratng Workbook ratngs and input those ratngs into the WebTARR
Program.
UI Internatonal (Project1) The UII applicaton used by [CLIENT] is a Financial Forecast module of UII. It is a Java based desktop applicaton with a 1 1 1 1 1 1 1 1 1
SQL database. It generates excel reports. A new module, æBudget and Regulatory moduleÆ, could get added next
year. The company is also considering IBM TM1. The company is striving towards having a single source of data to
overcome issues related to diferent people seeing diferent versions of the same data and be able to drill down to the
lowest level of detail.
The applicaton is used for financial planning.The financial planning process starts with gathering financial data from
all over the company for historical analysis and reportng and making financial projectons for the next 5 years on a
rolling basis. It is used by the Tax department for Tax forecastng, Regulatory group for Regulatory filing, Treasury for
Cash Forecastng, Investor Relatons to report to Wall Street.
It is considered a one-stop shop for a lot of people. It pulls the Financial Statements Actuals and produces forecasts for
the year as well as subsequent years. It enables high level budget and targets setting which can be broken down to
lower levels. It allows the tying up of the top down and the bottoms up approach for budget and financial planning.
It pulls a fairly summarized report from Cognos. Lots of other data is loaded via spreadsheets. There are no automated
interfaces as most data is pulled in forms of text files. The data pertains to projectons of Sales, Growth, Profitability,
etc. over the next 5 years. The annual financial planning process begins in April and goes on tll December to lock the
following yearÆs financial plan. Simultaneously, multple what-if scenarios are run on various corporate finance
contngencies such as depreciaton scenarios, capital allocatons, etc ..
Issues
ò Presently, drilling down can be done only at a high level and there is no ability to drill down below the monthly
levels.
ò Issue with accurate ability to forecast capital allocaton
ò Issues with accumulated deferred income tax. There seems to be inadequate informaton available on that.
PowerPlant The EWC [PROJECT]group performs two functons within PowerPlant: 1) approves the Accountng group to set up the 1 1 1 1
new capital account within the system; and 2) the Supply Chain group issues the work order to perform the inventory
audit at the Plant then the [PROJECT]group receives the report of the Plant inventory to approve that there are no
changes within the system.
PowerPlant is an asset/project tracking applicaton. [CLIENT]Æs current platform includes four û Power Property Tax ,
Power Lease, Power Provision and Power Tax. It is managed by the Property Accountng Group, which tracks all assets
and the depreciaton associated with them. The team tracks Storm Accountng, Capital Expenditure, Overhead
Accountng, Lease Tracking, ARO, etc. The data present in the applicaton is also used to support Tax informaton and
Regulatory requirements.
It is a vendor provided client-server applicaton. The applicaton is mainly supported in-house with vendor support
provided at the tme of enhancements. The system has many Interfaces: PeopleSoft General Ledger, PeopleSoft EPM
DW, PeopleSoft Accounts Payable, Cost Reportng and Analysis, DIS and Projects, among others . Earlier PeopleSoft
was being used for Asset Tracking and Accountng. As there were multple issues faced with PeopleSoft, [CLIENT]
implemented the PowerPlant system in 2004.
PowerPlant is used for creatng projects such as constructon of power plants, transmission lines, distributon
substatons and distributon lines, etc. The informaton is then fed to PeopleSoft Projects after which the cost is
allocated to diferent units. After the allocaton is approved, it is sent to PeopleSoft GL for accountng purpose.
PeopleSoft Project s only receives the high level informaton on project Ids, assets, status, company etc. from
PowerPlant and is used only for validaton purpose; no real processing occurs there. Various cost buckets in the
PowerPlant system û tax,transportaton etc. û are allocated to the project based on certain pre-defined criteria. Data
is also made available in the EPM for reportng purpose.
Workflow: The materials supplied from Contnuing Property Records (CPR) go into PeopleSoft Projects . The estmates
are created in the Project module and Assets are created from those estmates. After that, the system creates asset
records in CPR. CPR has an Asset ID associated with it. It also has various features like the Property Group, Quantty,
Costs, Depreciaton Group, etc. which tell how to depreciate the assets. Class Code is an additonal feature in this
system. These Codes are limitless. Special Tax Break is present for the class. There are 72 bucket creatons possible in
the PowerPlany applicaton. Asset locatons have other attributes associated with it in its own table. Approximately 50
Focus None 1 1
WebTap WebTAP is a web-based tool for the administraton and tracking of training course partcipaton and compliance 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
acknowledgement. It originated in the Fossil business unit and became an enterprise wide applicaton. There are two
main capabilites delivered via this applicaton. One focus is to deliver online training (CBT based) and the other is to
track class room training through re[PROJECT]traton. Each side has the ability to track training credits for courses that
have been taken.
The online training capability hosts and delivers compiled CBT courses. In the past CBTs were developed by outside
vendors. Over the past few years [CLIENT] has purchased software to allow us to do it internally. CBT courseware
development is beyond the scope of WebTAP support and is BU specific. As of today, Transmission is the only
business unit that has a dedicated group to do the CBT courses for WebTAP. BUs make the decision to develop CBTs
internally or rely on outside vendors. [CLIENT] does have standard guidelines that they must follow regardless of how
they create their CBTs. All developed courseware must be SCORM (Sharable Content Object Reference Model) version
1.2 compliant. However, no standards are in place to address the themes or look and feel of each course. The
applicaton maintains course completon records for each CBT automatcally.
The classroom re[PROJECT]traton capability provides the ability for BU administrators to configure courses via the
administraton interface. Unlike the CBT capability, administrators have to enter classroom training completons
manually. The lists of required courses are managed both automatcally and manually with most BUs having
automated this process to some extent. Fossil is entrely manual while other BUs have at least some process (e.g. 1 or
2 automatc plus additonal manual). Yearly courses have been the inital target for automaton among the BUs. BU
admins are required to make sure [CLIENT] get everyone trained for each requirement. When manual processes are
used to re[PROJECT]ter individuals, the potental does exist to miss people. When this occurs it is up to business
administrators to resolve. The cost of each course is billed back to the corresponding employee department. Each
partcpant is required to enter charge codes for each course. Employees will enter almost anything if they don't know
what their department's charge codes are. The system now requires valid code types via format checking but it does
not validate whether a code is valid for a partcular person. Employee Development would like to have data
prepopulated from PeopleSoft to reduce errors. This is because they do not realize bad codes were entered untl they
actually go to charge back the department. The finance system rejects the charge due to its own validaton violatons
and Employee Development then needs investgate the reason and determine the proper codes for the individual.
WebTap also includes a reportng functon. The primary report in this module shows how many requirements each
employee has completed. Once or twice a year requests are received for specific one-of data reports. To fulfill these
requests, HR runs SQL queries against the database and exports the data into Excel spreadsheets.
An important aspect of WebTAP is that it is not a true Learning Management System (LMS). It is limited in overal
functonality and was never intended to do what its being used for today. The system has a limited reportng
Cptrack This system is used to track distributon capital projects from the concept phase to approval. It is integrated with DIS 1 1
for cost estmaton purposes. Once the project is approved the project is handled by engineering team. Constructon is
completed through DIS. CPTrack has all capital projects that the distributon planning team initates. Scheduling of the
work is handled through DIS. This applicaton has been in use for more than 10 years and recently has been enhanced.
The business is exploring the possibilites to further enhance the capabilites. Project scoring is done offline (through
Excel) and put into CPTrack (import capability). It takes input of around 20 parameters, including regulatory and
politcal aspects.
Currently the applicaton is supported by the external contractor Round Table. CPTrack is integrated with DIS to pull
work request data for cost estmatng purposes.
Interface:
CPTrack <- DIS CPTrack Pulls the informaton from PROD Query, Nightly batch of Work request Data. NO flow back to
DIS.
Issues: Not aware.
Performance: Not aware.
Technology: Microsoft Visual basic 6.0 and SQL server 2008
CPTrack is an old (more than 10 years) system used to track distributon capital projects from the concept phase to
approval but after approval the tracking of work is not performed within this applicaton. It is integrated with DIS for
cost estmaton purposes to get the work request data. It does not have inbuilt capability for project scoring. It is done
offline through excel and imported into CPTrack.
There are a lot of manual project management actvites going on which should be automated. After ITC spin of level
of co-ordinaton actvites between diferent partcipants will add more complexity. For e.g, Today we have one team
to execute a substaton installaton, now it would be two teams i.e. one for transmission and one for substaton. Co-
ordinaton between two teams is going to be difficult and big challenge which does not exist today. Moreover
limitaton of tools will make it more difficult to execute. There is no centralized place where [CLIENT] can look for
Geo Tab lessons
None learnt, check list, things to do for the project management etc. for similar projects. Oracle Unifier got selected 1 1
SmallWorld The SmallWorld Internet Applicaton Server (SIAS) provides access to [PROJECT] data using a web browser. It shows all 1 1
the [PROJECT] data available inside AM/FM. This provides a read only view and has also been customized to support
customer searches. LAMP applicaton also leverages SIAS. There is also a ôgo-toö feature from DFM to provide an
engineered model and a switched model view.
User Groups: Lightng group, Constructon group.
Technology:
ò Front End: HTML Client
ò Backend: SmallWorld proprietary database from GE.
Interfaces:
ò No real interface.
ò DIS makes web service call to backend SIAS to get MDT (service suite) boundary informaton.
Known issues:
ò ItÆs slow and not as user friendly as GTI Viewer. It's difficult to figure out the navigaton features.
ò There is plan to decommission this version of SIAS and upgrade it to 4.1.1/replace the current version with GSS 4.2
(Geo spatal server).
The SmallWorld Internet Applicaton Server (SIAS) provides access to [PROJECT] data using a web browser. There are
known issues such as its slow performance and difficult navigaton features. Business users have shown interest in
decommissioning this version of SIAS to replace with the current version of GSS 4.2 (Geo spatal server). This
applicaton can be ratonalized into a standardized [PROJECT] program in the near future.
TMS Transacton Management System is an applicaton for remittance processing. It is the payment hub for all payments 1 1 1 1 1 1 1 1 1 1 1 1
received and helps in cutting down the total expenses for processing the customersÆ payments. The applicaton is
supported by the Finance Business Unit. It is a meter to cash process. It is a vendor applicaton (Trans Centra) provided
as a customized package but primarily in-house supported.
The applicaton accepts customerÆs payments primarily in the form of checks received via mail. This is managed by
resouces who open and process the mail. It allows the users to process (recognize) the checks used for the payments.
After the checks are processed, payments are posted to customer accounts. Occasionally, some discrepancies are
found with bills not matching with amounts, etc. TPPS pulls informaton from the CIS and CCS systems and sends to
TMS.
The TMS system sits on Archive Database, ECS Database and CMI Database. It also updates TPPS and CMI. There is a
standard daily backup and a fully tested applicaton recovery strategy in place for the applicaton database.
CMI is used to figure out what BU the Utlity account is associated with. It creates files and sends them to Cash
Operatons to facilitate movement in the PeopleSoft systems. Also, it pulls reports from the auto debit banking
accounts. It has additonal tools: TMS Enquiry and TMS Netquery to pull up copies of checks. They are being updated
as of now.
The number of users using this applicaton varies during the day and night. There are 3-4 users for this applicaton in
the day and 1-2 users at night. There are a total of 4 checks processing machines within this applicaton. The scope of
this applicaton is primarily around the mail-in payments. The applicaton gives the operators/ users the chance to
manually review and correct the errors that the machine cannot recognize. The TMS applicaton has been in place for
the last 4-5 years.
TMS This critcal
Used applicaton
to control is serving
Inventory the business
in Toolroom at EN-S needs asSites.
Nuclear originally
Usedplanned andand
to check-in is undergoing
check-out enhancements already.
tools and keep track of It 1 1
that informaton
TMS Placeholder for creaton of tme tcket management system 1 1
Create tme tcket management system
Meridian Meridian document management system is used by T&D. Distributon engineering is using a diferent tool. Meridian is 1 1
a document management system for AutoCAD designs. AutoCAD has been customized per [CLIENT] standards to be
integrated into Meridian. Using a wizard the user can check in / check out the document from AutoCAD. A Documents
include asset drawings, standard drawings and transmission designs.Number of Users: 120 power users + 450 view
only web users
Transacton stability is good and applicaton functonality meetng the requirements is high.
Functonality - High
Server got upgraded recently - 2012, Web server upgraded on April 2013. And after the upgrade users are happy and
are not complaining any more.
Server response tme is 3 to 5 minutes to less than 30 seconds. It was more to do with hardware than software.
It is customized more towards transmission.
Meridian document management is used by T&D for AutoCAD designs. Meridian carries a high operatonal risk and
contains confidental informaton. There is no formal DR strategy for this applicaton, and [CLIENT] has limited support
expertse.
Other business units like Nuclear are also using Meridian. It is recommended that Meridian should be ratonalized
over the period of tme with the enterprise document management program.
TAORS Transmission Automated Outage Request System (TAORS) is used to manage all planned substaton equipment and 1 1 1 1 1 1 1 1 1 1 1
transmission line outages. This applicaton is used by the Transmission Operatons Center (TOC), System Operatons
Center (SOC), Independent Coordinator of Transmission (ICT), Distributon Operatons Center (DOC),
Planners/Schedulers, Constructon, [PROJECT] Major Accounts, Wholesale Accounts, Distributon and Operatonal
Planning to facilitate outage planning and scheduling. TAORS is the key focal point in the outage coordinaton process
which allows a balance between constructon/maintenance outages and transmission service availability. Outages in
TAORS are used to drive AFC calculatons, outage postngs, and nuclear notficatons. It implements the business
processes from planning to approval where operators input planned outages and other groups use the system to
approve outages. Approvers vary based on outage type (e.g. an outage may require DOC approval depending on
distributon field switching requirements). Approvers receive an email to notfy that approval is necessary. A new
functonality was added to integrate with Keystone and transfer outages to MISO for approval. For every unplanned
outage an entry is made in TAORS.
The main functon is to coordinate future plan outages with TOC, regional switching centers, major account
representatves if those outages impact whole sale or large customers , distributon operatng centers as it relates to
switching and reliability coordinator. TAORS also feeds outages into a NERC study process to perform impact analysis
to system bottlenecks. It is also used as a historical database for the past actons on the transmission system. After the
ITC split, distributon will no longer have access to TAORS. A manual process will be in place to gain distributon
approval for transmission outages through phone calls and emails.
Transmission uses TAORS to feed external systems such as reliability coordinator SDX ( System Data Exchange) to share
outage informaton with the eastern interconnect. It also uploads informaton to OASIS (Open Access Same Time
Informaton System) so all utlity members can see the informaton at same tme. It is also used to track when outage
is started and stopped explicitly.
Transmission handles 69KV voltage level and above outages (69KV to 500KV). Any outage below 69KV is handle by
distributon except for those devices that are owned by transmission at lower voltage level such as tertary winding
reactor that is energized at 13.8 KV which is at distributon level voltage yet it is a transmission asset that sits on a
transmission transformer.
Distributon may need to create its own version of TAORS after the ITC split. Even though TAORS was developed
specifically for transmission, distributon began using it after a few years. However, the business rules were specific to
transmission. For example, a P3 level outage request should be schedule not less than 4 weeks in advance for
transmission, but this not rule does not apply to distributon. Distributon will have their own set of new business
rules for their business requirements. The second challenge distributon will have to implement these rules in
software is the applicaton is very old (roughly 9 to 10 years old) and code is not maintained properly. A change in one
module will have impact on other modules, and distributon does not have the experience and level of understanding
with the tool to know where the code changes need to be done and what others module will be impacted.
Would like to have following features :
1. connectvity model build in SWMS and LWMS which presently has the equipment informaton. The connectvity
model will help TAORS in efectvely manage outages.
2. To have code transfer to .Net which is presently in .ASP .
3. Merging of COS and TAORS as it will reduce the amount of work.
Reportng:
KPIÆs SAIDI and SAIFI are measure and reported from COS (Consolidated outage system) but not from TAORS. TAORS
Keystone An in-house applicaton developed to interface with MISO CROW (Control Room Operatons Window) (MISO's outage 1 1 1 1 1 1 1 1 1 1 1 1
tool) to TAORS.
There are issues with Keystone which is that it is constantly having issues whereas have 1 employee dedicated to keep
up with the errors. To get rid of Keystone by hiring 6 people to work on shift.
SWMS SWMS provides [PROJECT] substaton assets. SWMS tracks work requests and the documentaton of work for all 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
substaton assetsthrough seven elements of the work management business process:
1. Nameplate data- attributes for the asset that describe its makeup
2. Pending Work (Conditon & Time Based Maintenance) û SWMS look at Pegasus and other data for using complex
algorithms to automatcally generate work for the operaton and tme based maintenance work.
3. Work History - Reports can be run to show work that has been done on assets. It is use to identfied the trend
and no data is archived out of the database itÆs kept in history tables.
4. Failure History - SWMS keeps inspecton data for each asset and has the capability to show that fault which have
occurred.
5. Operatons û SWNS keeps counter of breakers that have tripped open or closed with other reading detail.
6. Test Data(over 100,000 assets within 2,000 substatons)- Its enter in results of tests that have been performed
7. Interfaced with T&L to upload field crews work hours
SWMS is used by distributon and transmission to handleswork, tme and inventory. It records operatonal data about
equipment based on real-tme from Pegasus. SWMS has algorithms to automatcally generate new work requests
(sent through TES to the field). TES can operate in a disconnected mode. While uploading the batch, all completon
informaton is sent back to SWMS. TES does not have the ability to optmize work distributon. SWMS has an ability to
attach external documents through TES and SWMS to work requests. SWMS serves as a document management
system for some types of informaton. It has the capability to access the test result for proof and auditng. TES sends
back completon informaton. SWMS adds code block informaton and then sends to PeopleSoft Time &Labor. Project
code informaton is entered directly into SWMS.
SWMS is the hub for many other applicatons in the organizaton. It is the system of record for documentaton. It has a
capability for contnual enhancements (e.g. collect new types of data). Many enhancements are mandated because of
environmental and other laws (e.g. SF6 gas tracking). SWMS includes only substaton equipment (not line assets).
Some facilites will no longer be in SWMS after the ITC split. It creates PMs, IMs, DMs automatcally. CMs can be
created on the host or through TES. TES is the field version of SWMS. The planned schedule is created in SWMS and
transmitted to TES machines. Data is collected from other applicatons when transferring work requests from SWMS
to TES through a nightly job process.
The configuraton management group puts the asset in SWMS, and maintenance is applied by schedulers / supervisors
to the assets. Assets will have diferent maintenance cycles, each carrying diferent work requests.
SWMS fully supports SERC audits - test results and other data sets needed are available in SWMS.
User groups - Scheduler, Supervisors, Mechanic / Technicians, Planning, Config. Mgmt. group. Data is used by several
other departments in the organizaton.
*** SFIS renamed to Time Entry System (TES) - allows tme entry, creaton of work and inspecton data. Checklists for
SERC purposes. ***
Interface: Interfaces with multple applicatons
SWMS gets code block and employee informaton from T&L through EAI and uploads tme sheet.
SWMS reads informaton from LMS.
SWMS reads informaton from COS.
Technology
LWMS LWMS is an [PROJECT]system for transmission similar to DFM for distributon. It has transmission lines only and it is 1 1 1 1 1 1 1 1 1 1 1
not used for distributon lines. It does not have scheduling capability. LWMS collects and updates field inventory data,
electrical connectvity, item inspectons and observed problems.
All attributes of lines are captured in LWMS. However it does not have the capability to generate preventve
maintenance (PM) requests. Based on Crystal reports PMs are created. Better reportng capability is required for
maintenance programs.
LWMS is about 20 years old. The data has not been maintained as it should have and is unreliable at tmes.
Tool/system use for Pole inspecton ûThe purpose of spread sheet is for causal inspecton of pole. Business uses
spreadsheet based tool for scheduling inspectons as the tool does not have scheduling capability. The informaton is
being exported to a crystal report and then sent to the field. All field crews are contractors. Only one crew is internal.
There is lot of functonal gaps between LFIS and LWMS. Most of the LFIS users are contractors, they have universal
login for LFIS. After they capture informaton on LFIS, it updates back the informaton to LWMS server.
No tme entry capability is there and it's also not required as the users are contractors and they send their invoice.
Interface:
LFIS < - > LWMS.
LWMS -> SWMS (SWMS accesses for line informaton), LWMS database is called TMS.
LWMS -> COS
Technology : PowerBuilder 7 , SQL Server 2008
For Transmission, LWMS is a software applicaton that provides primary support of the Work Management Process
(AM-PC-AD-001) for Transmission Lines. LWMS is used to store informaton on line component asset definitons,
identfy damages found during inspectons, and track maintenance actvites. LWMS does not provide a scheduling
functon at this tme.
LWMS is about 20 years old. It is used only for transmission lines. The technology PowerBuilder 7 is marked as the
retrement directon, and the applicaton scores high in architecture risk. There is no strategy in place to maintain
database state of health. The applicaton does not have a scheduling capability. LWMS is not for distributon use, and
it does not have any tme entry capability. After the ITC spin of, this system will not be required, and the system can
be reclaimed.
WebFG WebFG Replicated Data Servers (RDS) provides read-only access to EMS displays.áWebFG RDS server data is replicated 1 1
from the EMS systems. Project Development uses WebFG RDS to look at configuratons.
PWP PowerPlant Property Tax Module is primarily used for Reportng purpose by the Property Tax group and is managed by 1 1
about 10 people. These reports are basically the listng of assets. It also contains privacy informaton which has to be
in compliance with the Property Tax rules. These reports, after including the tax regulatons, tax rates, etc. are then
forwarded to the Tax Authorites for further acton.
This applicaton is also used for negotatng values from other companies . Diferent types of approaches are used for
negotatons like Cost Approach value, Income Approach Value, etc. As the assets are allocated across various
geographies, it also contains the descriptons and categorizaton of assets as per state Laws.
This applicaton is integrated with the GL system where the journal entries are created. It is also integrated with
Budget. The ATPR system is used to pay the bills.
PWP is a critcal applicaton primarily used for reportng purpose by the Property Tax group. It is aso used for tracking,
analysis, reconciliaton, reportng and filing of property tax informaton.
The applicaton should be sustained.
PowerSafe None 1 1
PassPort (Indus) Indus PassPort. [PROJECT]tool used by all [CLIENT] BU's except [CLIENT] Nuclear Northeast (ENNE). Also PassPort is the 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Work Management tool used by [CLIENT] Nuclear South (EN-S).
Passport (Legal Claim) With the implementaton of the DatacertÆs Passport applicaton, [CLIENT] will decommission the STARS, AIMS, and 1 1
Collect (part of Phase II) applicatons. The project implementaton strategy is to implement in two phases: Phase 1
will replace the existng STARS and AIMS functonality. Phase 2 will replace the existng Collect functonality.
The system allows the Legal department to track and manage spend for outside legal assistance. Contractual
informaton can be entered into the system and will alert the Legal team when invoices fall outside of the contract
agreement. The system allows for an outside firm to enter invoices themselves and get payment status updates. The
new system interfaces with PeopleSoft Accounts Payable, Gould and Lamb (ExamWorks Clinical Solutons, ECS), CorVel,
CCS, Peoplesoft EPM and PeopleSoft HRMS via VDS. The new system provides reportng capabilites for Claims and
Legal.
The list shown below identfies the current integratons with Passport. Integratons with external vendorÆs and
systems are denoted in parenthesis.
ò Integraton 1: Code Block Validaton

ò Integraton 2: Pre AP Post Validaton
ò Integraton 3: AP Post
ò Integraton 4: Vendor Sync
ò Integraton 5: HR Employee Data
ò Integraton 6: CCS Matter Sync
ò Integraton 7: CorVel Matter Post (external integraton with CorVel)
ò Integraton 8: CorVel Invoice Sync (external integraton with CorVel)
ò Integraton 9: ECS Claim Eligibility Post (external integraton with ECS)
ò Integraton 10: ECS Claim Status Sync (external integraton with ECS)
ò Integraton 11: ECS Claim Result Sync (external integraton with ECS)
ò Integraton 12: ECS Claim Input Post (external integraton with ECS)
ò Integraton 13: ECS Claim Response Sync (external integraton with ECS)
ò Integraton 14: ECS TIN Reference Response Sync
ò Integraton 15: AP Reconciliaton
ò Integraton 16: Workgroup Locaton
ò Integraton 17: SSO with SAML
See System Understanding Document for Legal, Claims, Matter and Spend Management System or ITAM for more
informaton.
WebTab None 1 1
Underground Fault None 1 1
LAMPS None 1 1
DIMP Distributon Integrity Management Program (DIMP) is a regulatory required applicaton built on top of AM/FM Gas 1 1
and is used to track and prioritzed risks in gas system. It uses Opvantek for DIMP reports. It consolidates the gas asset
informaton in AM/FM and provides multple applicatons for diferent use. The GE SmallWorld standard gas model
ôGas Distributon Officeö (GDO) was used to creatng the Gas Data Model 10 years ago. DIMP provides analysis on
pipes of highest risk and, depending on budget availability, and performs PRPs, leak surveys and helps in developing
mitgatng acton. Leak informaton comes from field in the format of work slips and is entered in Documentum. The
leak object is created in Documentum and is linked to [PROJECT] to provide the source for all history leaks.
Following are data contained within DIMP:
ò Assets: Pipes, Valves and Leak history,
ò Consequences: Populaton density, Paving, pressure
ò Risk - Opvantek (plugin to SmallWorld).
Reportng:
Build a set of tables for reportng. A set of templates are provided by Opvantek for regulatory filing.
Future initatves:
1. Build an interface to pressure analysis.
2. Store CFR rules.
3. Help in Rate Case justficaton.
4. From future system integraton perspectve - te to other database such as Locate Requests, Leak survey, Pressure
Modeling (GREGG Engineering, Houston).
5. Develop additonal tools that will connect Excel spreadsheet to Oracle database.
This applicaton is critcal to track and prioritze risks in gas system. DIMP should be sustained in order to support
analysis on pipes of highest risk, perform PRPs, perform leak surveys and help in developing mitgatng acton. There is
a need to build an interface for pressure analysis and to other databases such as Locate Requests, Leak Survey, and
Pressure Modeling. [CLIENT] would like to have a system in place for new assets in ground that are automatcally
barcoded and linked into records programs in near real-tme. There are opportunites with this applicaton to find
opportunites for system improvement investments with enhanced reliability / safety.
The system does not require any significant change over the next few years and should be sustained in its current
design.
NJUNS None 1 1
CIR None 1 1
COS None 1 1
ROWT None 1 1
First Advantage None 1 1
DSS DSS is the Distributon Scheduling System, a frontend to Distributon Informaton System (DIS), simplifying work for 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
design groups. DSS does not manage non-design work and it is handled through MDT. MDT is used for short cycle
work and DSS is used for large projects designs. MDT is not as user friendly as DSS; Hence DSS is stll maintained and
designs are mainly created through it. DSS is used for scheduling work for both [CLIENT] employees and contractors.
Two weeks of schedule are maintained for contractors. Actual work executon is through paper work for both
employees and contractors. After work is completed, the As-built is updated in DIS and status is updated in DSS
through an interface.
Distributon Scheduling System is for paper work and Service Suite (MDT) is for automated work. Distributon
Informaton System (DIS) determines if the specific work order follows the paper or Service Suite route. Work orders
going to Service Suite do not need any scheduling in DSS.
There are no electronic attachments or drawings present in DSS which can be used for reference or help. All is hard
copy used by crews. Operator qualificaton is not captured in DSS and there is no certficaton informaton available for
qualificaton/skillset of crews. 35,000 design jobs per year are created in DSS.
An interface exists with CTS through DIS for contractor work for invoicing purpose.
Process wise there are no issues with DSS. If DSS is not available then [CLIENT] uses DIS to schedule the work. DSS
has some reportng capability, but these are not being used.
Interfaces:
ItÆs a front end to the DIS database.
Interface with CTS through DIS for contractor work for invoicing purpose.
Technologies:
Custom applicaton Built on PowerBuilder 7 (Old) and database Oracle 10g
The applicaton was built around 1999 or 2000.
This applicaton works on top of the DIS database. The technology directon is marked for retrement. There is a
strong desire from business leaders to bring in more automaton in scheduling to better address customer
commitment dates, resultng in increased customer satsfacton and less truck rolls. This automated scheduling needs
to be addressed as part of a new unified work management system across distributon.
PQWeb None 1 1
Contractors None 1 1
ARCOS None 1 1
WoW None 1 1
Auto manager None 1 1
RoD "Resources on-Demand (RoD) is a web-enabled system used to manage resource (people and equipment) requests 1 1
and track personnel movement during emergency outages. In the event of an outage emergency, a power company
needs a tool to facilitate resource request and assignments. RoD captures resource requests and available resources
and provides historical informaton on the movement of resource teams. Within RoD, all personnel movement is
tracked historically within an event and maintained for historical reportng. It is only used during storm recoveries,
payment and justficaton of storm invoices.
RoD tracks hotel reservatons, workers, assigned jobs, equipment and any other movements during storm restoraton.
It also tracks meals for work crews by entering vendors and expected delivery.
RoD is installed on two internal [CLIENT] web servers with F5 load balancers. The load balancers were added after
experience in 2012 storm recovery, but the system is having session persistence issues. IT is currently working with
the vendor to resolve. RoD could contain privacy informaton if a medical conditon occurs during restoraton. It has a
placeholder for medical conditons.
SQL agent jobs in database run nightly to take snapshots of tables.
Interfaces:
None
Functonality not available: We would like limited contractor access to ROD to allow them to input data into ROD
during storm. It could be a spreadsheet contractor can upload into a repository with in ROD.
Report: Standard set of report available with in ROD. Adhoc query is being maintained by Alan to run whenever
required.
Macrosoft is also supportng this applicaton along with IT as per the maintenance contract."
This applicaton is critcal to track personnel movement during emergency outages. Presently the system is having
session persistence issues, and [CLIENT] is currently working with the vendor to resolve. There is a need for limited
contractor access to ROD to allow them to input data during a storm. The system does not require any significant
change over the next few years, so it should be sustained as required.
MDUS Meter Management system built by SAIC to track AMI meters 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
PCRS Paperless conditon reportng system (PCRS) is an in-house developed applicaton used to log/report any conditons 1 1 1 1 1 1 1 1 1
(safety related etc.) in the plant .The conditons can be reported by anybody including visitors or guests. The
applicaton is then used to maintain the conditon reports and correctve actons and track them to closure. PCRS also
tracks procedure revisions, etc. Thus it is now being used as generic tracking system. Also, there are some plans to use
PCRS to trigger work request in to asset suite. The applicaton is also being used by Fossil and Transmission business
units.
It also contains sub-modules/configuratons, Procedure Processing, Correctve Actons, Assessment/Benchmarking,
Vendor Correctve Actons, Outage Critque/Learning, Licensing Acton Requests and Work Tasks.
The applicaton is tghtly integrated with many other important applicatons (Asset Suite, P6, etc.) used at the Nuclear
business unit.
This is one of the critcal applicatons being used in the Nuclear business unit which also helps in regulatory
compliance .The applicaton should be replaced with a more robust and flexible product in the long term. This being a
generic functonality used across the industry, there are many industry standard, vendor based products which would
be good fit as a long term soluton. The Asset Suite û Acton tracking module, Devonway ActonWay (Cooper plant has
replaced PCRS with ActonWay), SAP EHS module etc. Maybe some of the suitable optons which can be evaluated.
There is a risk around the support for the applicaton. The Business Process Owner, who was handling any adjustments
or changes in modules, is planned to retre in May 2014. Therefore in the future, IT will need to take care of the
requests for the changes, for which ramp up of the business process knowledge would be necessary. This risk will
PCRS - SPO Enterprise tool utlized to document compliance related concerns (Conditons) and to track all required actons 1 1 1 1 1
(Correctve Actons) utlized to address the current Conditon and to proactvely prevent the future occurrence of
similar events. PCRS has the ability to add keywords or trend codes to run reports from.
PCRS - EWC Compliance database which tracks issues, icludes resolutons of the issues. The applicaton is limited in its ability to 1 1 1 1 1
attach other file types other then .doc and .pdf.
PCRS - Transmission Maintenance and Tracking of Transmission and Fossil Conditon Reports 1 1 1 1 1
Fossil currently evaluatng where to take PCRS long-term. Currently put FERC and NERC alerts and NERC compliance
correctve actons into PCRS. Used by NERC compliance and each plant's NERC champion.
Craig Maxim is administrator for corporate compliance.
Will expand to include relay mis-operatons.
PCRS, although not heavily used by fossil today, should be considered for broader use across the department. PCRS's
simple even capture, monitoring, and acton tracking capabiltes can serve multple purposes within Fossil as it relates
to identfying events and risks and then tracking each item from its identficaton through its closure. Today, fossil has
multple solutons that serve this same purpose.
PCRS - Report This is an old in-house developed reportng tool for the PCRS applicaton .The applicaton allows the users to easily 1 1 1 1 1
create ad-hoc reports on the PCRS data. The applicaton has a lot of issues/bugs and every tme it is opened to fix,
more bugs get introduced. The business has therefore decided not to do any break fixes again on the applicaton. Also,
there are no changes or investments on the applicaton for many years .If there are any issues, somehow re-installing
the applicaton helps to resolve the issues. The only reason the applicaton stll exists is because it provides the only
interface for general users to perform ad-hoc reportng. The advanced users have the opton to go through the read
only interface to the PCRS database. Also, the business has changed the general processes which have impacted the
usefulness of some of the reports contained. As the applicaton is not maintained any more, those reports have just
been abandoned within the system.
This is very old applicaton with a lot of issues. It is stll exists because it is the only way for the general users to get ad-
hoc reports. Also, the applicaton is based on old VB6 technology. This applicaton needs to be ratonalized within the
enterprise BI initatve.
EB (Enterprise Bridge) Nuclear Document Management system. 1 1

MyeBusiness Formerly known as Managed Accounts Portal then replaced by myEbusiness. 1 1 1 1 1
The Managed Accounts Portal was implemented to support [CLIENT]'s large natonal and managed accounts (e.g.
Wal-Mart, Walgreens, Tulane University).
This portal was a precursor to MAO; its only true functonality was to provide a bill history view. Internal users may
also store content in Documentum and publish to targeted subgroups of accounts.
Managed Accounts was later loosely integrated with MAO. Instead of internal resources creatng and managing
individual user IDs, they create containers with administrator rights that allow external users to login and
re[PROJECT]ter other users for their company. Internal users also attach all sub-accounts and create the links to
SalesPage.
The portal accesses SalesPage tables to retrieve rolled up usage informaton. It then stores copies of the data in
Managed Accounts database.
Customers are not heavily using the system as-is today. Managed customers are not intended to create individual
accounts in MAO, but they do, because the MAO functonality more closely matches their needs. The going-forward
desire is to expose more MAO functons to Managed Account customers.
This portal is not being heavily used or accepted, neither by customers nor the business. Even though it is not
"allowed", managed accounts are re[PROJECT]tering their accounts with My Account Online to gain functonality.
As part of the Customer Experience strategy, it is recommended that My Account Online be enhanced to provide
approved functonality for managed accounts.
Primavera - Project Third party capital project scheduling tool used by Energy Delivery Engineering and Energy Delivery Project 1 1
Management Management & Constructon.
Scheduling tool for transmission line and substaton capital projects.
Used for Project Scheduling, Resource Planning, Cost Tracking, Change Management, and Cash Flow.
Primavera Project Management (P6) is a product from Oracle used as the Nuclear fleet scheduling soluton providing
the tools to accomplish project management. It is majorly used for scheduling actvites. The capabilites of the tool
include managing, organizing, scheduling and tracking the progress of complex projects. The current version of the
software being used at Nuclear is Version 6 .This version has gone out of support since October 2013. The version
upgrade plan (to Version 7) for the software is waitng for budget approval.
The applicaton has following Issues/Concerns:
1) The existng version (V6) has gone out of support since Oct 2013.The latest version of the product available is
version 8. Although [CLIENT] is paying the maintenance for the product, in case of any issues, the vendor will only
suggest for an upgrade and will not do any break fixes to this old version. Also, [CLIENT] will need to upgrade to
version 7, as direct upgrade to version 8 has had issues with other customers. The Business case for upgrade to
version 7 has been submitted and is awaitng budget allocaton (approximately $70,000).
2) This is one of the most critcal applicatons in the Nuclear business unit and yet there is no support SLA defined for
it. The underlying infrastructure for the applicaton is of mission critcal level but the support is defined as basic
service level.
3) The applicaton sometmes has performance related issues.
This is one of the most critcal applicatons being used in the Nuclear business unit. It has tghtly integrated to the
Asset suite applicaton for scheduling of the projects. This applicaton is one of the best industry products for project
management and scheduling. It also is very user friendly .The applicaton should be sustained with regular upgrades so
Concur as to have uninterrupted support from the vendor. Also, if the support SLA is not in place for this applicaton, it needs 1 1 1 1 1
T2R refers to the name of the project (Travel to Reimburse) that implemented the applicaton, Concur Travel and
Expense.
Targeted Deployment Date: 02/12/2016
ITAM: Concur Travel and Expense - streamlines and simplifies the [CLIENT] travel and employee expense process. This
will replace EARL and Carlson Wagonlit Travel (CWT). Vendors are Concur and American Express. Product may also be
known as Travel to Reimburse, Concur Booking
High-Level project descripton: The goal ofáthe Travel to Reimburse projectáis to streamline and simplify the [CLIENT]
travel and employee expense process.á The IT porton of the project will focus on the technical integratons that
support the development and implementaton of the larger end-to-end Travel to Reimburse process.á The Concur
Travel andáExpense modules will go live on February 12, 2016 with a 'pilot' group of employees with a subsequent
roll-out to incorporate the remaining populaton April 18, 2016.
The integratons for the CONCUR Travel and Expense modules include SSO, HR data feed, codeblock validaton,
PeopleSoft AP, modificatons to the EPM data warehouse, ápayment file to American Express, modificatons of the
Capital One ACH file, and loading receipt images into FileNet.á The scope also includes the decommissioning of
theáEARLáapplicaton.
Note: Decommissioning of EARL will occur in July 2016, plan to be submitted at a later date. Per assumptons included
the Technical Integratons SOW ôScope of project includes decommissioning of EARL. EARL data needs to be
accessible for 24 months after final group of employees are rolled-out. Support personnel need to remain available
during this tme. EARL will be decommissioned and data will no longer be available after 24 months from the final
group of employeesÆ go-live to Concur.ö
PERFMGR Note
None about support: The [CLIENT] Support Center (ESC) will field all internal employee questons about the tool. If an 1 1
AANNSTF AANNSTLF is a neural network that forecasts load for next 7 days based on weather forecast (temperature) and load. 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
The acronym stands for "Advanced Artficial Neural Network Short Term Load Forecaster"
[CLIENT] uses AANNSTLF to produce short-term load forecasts to support its Control Area (now to be two Local
Balancing Authority Areas) responsibilites and its market actvites.
A third party web applicaton from Tesla Forecastng Solutons is used to compare results.
Forecasts how much energy will be consumed in MISO.
Inputs are actual loads, actual temperatures, and forecasted load. This is needed so MISO can plan accordingly.
The applicaton is not real-tme for the next hour or for each region of [CLIENT] to see if under or over the forecast.
The processes are:
1. Loads come from LBA to AANNSTLF which loads temperatures.
2. Outputs from AANNSTLF to Load Forecastng (Access 97).
3. Outputs from AANNSTLF to LBA.
4. Outputs from AANNSTLF to PCI which is converted into demand bid.
5. Both AANNSTLF and Tesla outputs load forecasts to ???
other vendor-supplied programs have been considered in order to supplement the forecast and improve the forecast
accuracy, especially during transitonal weather periods. As a result, in 2008, [CLIENT] entered into a trial with a load
forecastng vendor called Tesla. The trial service was re-negotated into a service contract in 2013,
Planner Tools Excel Allows field personnel to view and track committed tasks, create forward looking work plans, etc. In general, it creates 1 1
Toolbar Add-in work management reports from SWMS.
Connects to SWMS DB.
Gas Platform None 1 1

MAVEN As part of the support for [CLIENT]'s largest customers, Major Accounts Billing (MAB) must individually verify that each 1 1
of its 2000 accounts is billing correctly each month. This validaton is done by recalculatng the bill, in some way,
outside of the billing systems.
MAVEN automatcally verifies the more simplistc MAB accounts. It processes around 1200 accounts per month.
MAVEN stores independent account details (rate, riders, lights, etc) in its own database and automatcally interfaces
with CCS, BEX and Excel workbooks to gather data. It then independently verifies the calculated bill amount, and
automatcally bills in CCS if it matches. MAB manages any billing or validaton exceptons within MAVEN.
When MAVEN was created, MAB was able to reduce its staf by three full-tme equivalents (FTE's).
Since a major requirement of MAVEN is performing an independent billing validaton, this system must contnue to
exist outside of SAP. Therefore, unlike other business supported applicatons, it cannot be ratonalized against SAP
functonality. However, once SAP is upgraded to ECC 6.0, the system should be re-architected to make use of web
services instead of Winbatch. At that point, support should be transitoned to an IT vendor such as SAIC.
Since MAVEN is considered one of the most critcal of the Business Services supported applicatons and also carries
one of the highest risk scores, it should be re-architected in phase one of the SAP Consolidaton program.
Recurite The PeopleSoft eRecuitring module is used to support recruitng and staffing process for company. The applicaton is 1 1 1
used to post jobs online and to recruit internal and external applicants. All applicants apply for positons with [CLIENT]
using eRecruit. The system is open to the web for all applicants. The system provides the applicant with their status
by showing them where they are in the process.
The current implementaton is not user friendly and the navigaton is clumsy. When 50 applicants apply for a positon
and the hiring manager only accepts 3, users have to individually select each of the 47 remaining applicant to reject
them. Internal hiring managers are the only ones that see the resumes associated with a given requisiton. If another
manager wants to view the resumes, they need to be copy/paste from of the system.
From an applicant perspectve feedback has been received that the system is not very user friendly partcularly in the
way resumes are handled. When they are attached, format issues arise. This can cause issues with hiring managers
but this is primary method that is used to determine if a candidate is qualified.
There is a lot of duplicaton in efort because eRecruit does not interface entrely with the core PeopleSoft HRMS
system. The eRecruit module is based on version 8.8 of PeopleSoft and the core HRMS system is on version 8.3 When
a candidate is hired not all of their data is transferred back into the core HRMS 8.3 system.
There are multple reports generated by the system including the Staffing Actvity Report (SAR) Report, the Current
Openings report and the Applicant Flow Report. These reports are shared with business leaders to expose recruitng
diversity in their organizatons. They are also used for SOX, legal purposes, affirmatve acton and Equal Employment
claims
There are opportunites to automate and improve certain processes. To obtain approval to post a positon is entrely
paper process. There are many diferent back end processes. Some of this is because management is trying to control
budgets. Many of approval processes require the hiring manager and their boss and in some cases, the boss
abov+B175e. Nuclear requires the Chief Nuclear Officer to approve some specific candidate ofers. This becomes a
PLATTS - SPO / EWC PLATTS is a data feed. It provides electricity and gas prices. 1 1
The Platts data feed is used primarily by the EMO porton of SPO, mostly for the real-tme feed of price data. We
(Planning Analysis) manage the vendor contracts for Platts. We are asking the EMO users of this applicaton for their
input. Planning Analysis is a secondary user of Platts pricing data. We access the Platts data via a series of Price
Reports which were developed and are maintained by IT. Accenture provides IT support when needed. Finally, EWC is
a user of Platts pricing data. To get an understanding of EWC needs IT should contact Devrim Albuz at EWC.
The issues with the data feed is that it occasionally contains missing data points.
There are processes or interfaces that come into or out of the systems which is the Platts FTP delivers the data. Data
from this system provides the basis for 1) providing various data requests; 2) data in various regulatory filings; 3)
responding to various RFI
There are no documentaton in regards to the use, processes, or interfaces.
Aetna Aetna manages the employee medical benefits program via an externally hosted service. Multple interfaces exist to 1 1 1 1 1 1 1 1 1
transfer data to and from PeopleSoft to manage this relatonship. The primary interface sends indicatve type data
about enrolled employees that includes benefit electons so Aetna can mail out cards and informaton in the mail.
Weekly paycheck deductons are send weekly from payroll. Indicatve data updates (e.g. address, status) are updated
via the same weekly schedule. Aetna sends a list of enrolled accounts every Friday at 5:30PM which is validated
against PeopleSoft. A report of this validaton is emailed to Andy Lopata.
All of the interface jobs are run via the PeopleSoft scheduler. Each job relies on either SFTP or a combinaton of FTP
and PGP to encrypt and transfer the data. In general, the interfaces operate consistently but occasional issues of
improper employee classificatons do occur.
For the flexible spending account (FSA) interface, Aetna provides details on employee accounts including specific
contributons, electons, and the general indicatve data. Once a year, [CLIENT] sends Aetna the enrollment and
pledge data and this file acts as the record of eligibility.
For health spending accounts (HSA), the interface is combined with that of FSA. A full list of enrollments and
contributons are sent each tme with modified records flagged. A reconciliaton report exists to validate that
deductons and the actve employee list are correct between payroll and Aetna. Special deductons are infrequently
used lump sum deductons that employees may request. Another file in this interface details which employees have
opted to utlize this feature and the amounts of their contributons.
There is an annual lump sum report that is emailed to the following individuals: Andy Lopata, Barbara Branif, and
Rhonda Pakarinen. This is via the PAYCALC interface.
Finally, as part of the medical and dental interface, a file is received from Ceridian (CobraServe provider) via FTP and
PGP. Updates to this data are incorporated into the data that is sent to Aetna. 1 1
Experian The Experian interface provides [CLIENT] with a way to check a potental customer's credit before establishing service. 1 1 1 1 1 1 1 1 1 1 1 1 1
Implemented as an RFC call from CCS initate call to the Experian Web Service (with authentcaton over SSL), data is
returned from Experian and the reformatted to store only the credit score and the result code (normal status,
deceased person, unissued SSN, etc). The score and result code are then interrogated by code within the calling
system to make business decisions, such as deposit amount, etc.
TESLA A third party web applicaton for electric power demand forecastng and analysis. Its capabilites include delivery of 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
short-term forecasts complete with automated and user-designed scenario. [CLIENT] provides load Tesla provide
Weather variables. Business uses this service in conjuncton with AANNSTLF.
MISO The MISO Portal is a website hosted by MISO and is used to access all MISO applicatons and functons (such as Day 1 1 1 1 1 1 1 1 1
Ahead bids, awards, FTRÆs, settlements, meter data, invoices, asset owner informaton, etc).
The Long-Term Analyst uses the MISO Portal to download MISO transmission model informaton for use in internal
energy planning models. The Analyst accesses the MISO Portal directly via web browser, and not use any third-party
software.
Splunk 1 1 1 1 1
ServiceNow 1 1
AMX Not sure what this is.
Aruo Not sure what this is.
Attentee File Not sure what this is.
Attentee File Not sure what this is.
Bellomy - Smart TAB Not sure what this is.
D&B Dun & Bradstreet
General Dynamics Not sure what this is.
Google Analytcs Analytcs tool set
Hibernia Bank Not sure what this is.
HIS Markit Not sure what this is.
HSD Not sure what this is.
JPMorgan
Liberty Mutual
Mellon (stock) May impact Compensaton use case
Mellon(stock) May impact Compensaton use case
MRV Not sure what this is.
MTAB Not sure what this is.
MTM Recogniton HR Vendor for Rewards and Recogniton
NOAA Weather data
NYISO.COM EWC Not sure what this is.
Oracle Fusion Cloud Oracle platform software
PAC Not sure what this is.
Panjiva Global trade data provider
Payment Processing
PIRA Power storage trends data
Power Advocate Procurement system
Riverland Credit Union
SAE File Not sure what this is.
Schneider Has many products, which one?
Simmons Bank
SNOW Not sure what this is. Could be License Manager
Sprinklr Is the Social Marketng Platform?
TALX Credit Ratng
Telvent Could be Telvent SCADA ot [PROJECT]
Trowe Price
Trustmark Bank
Vaisala
3rd Party Performance Syst Not sure what this is.
Agent Car System Utlity OpHow and where is this used? What data does this hold? What is the data source?
AIMS Not sure what this is.
Allegro Finance Not sure what this is.
APPADM/Framework DB Cognos File?
Arrora Not sure what this is.
AS Not sure what this is.
Aurora SPO used by SPO for forecastng
AutoManager Not sure what this is.
Automate Balancing SystemHow and where is this used? What data does this hold? What is the data source?
BERT Monitor Distco Not sure what this is.
Bid Screen XL EWC Not sure what this is.
Billing Expert Distco Not sure what this is.
Breaker Dispatch How and where is this used? What data does this hold? What is the data source?
Breaker TelAlert How and where is this used? What data does this hold? What is the data source?
CAMBAR Not sure what this is.
Cash Mgmt Interface Finan How and where is this used? What data does this hold? What is the data source?
CCO Repository How and where is this used? What data does this hold? What is the data source?
CEMRW Not sure what this is.
CIMS Not sure what this is.
ComputerShare Not sure what this is.
Cost Analysis Workbench F How and where is this used? What data does this hold? What is the data source?
Cost Analysis Workbench F How and where is this used? What data does this hold? What is the data source?
CRIS Not sure what this is.
Customer Contact DB FinanHow and where is this used? What data does this hold? What is the data source?
DECCER EWC Not sure what this is.
DINIS Not sure what this is.
DNA - Fusion Not sure what this is.
DSR Not sure what this is.
Electronic Data Transfer How and where is this used? What data does this hold? What is the data source?
EN Form How and where is this used? What data does this hold? What is the data source?
Endpoint Protecton EWC How and where is this used? What data does this hold? What is the data source?
[CLIENT] NET HRA Not sure what this is.
Enterprise Compliance & RiNeed more informaton
Enterprise Compliance & RiNeed more informaton
Equipment Failure TrackingNeed more informaton
EWOPIE EWC Not sure what this is.
Excepton Processing Syste Not sure what this is.
Financial Informaton Doc ONot sure what this is.
First Quarter Comp Mgmt DB used by HR?
Fleet Manager Not sure what this is.
F-O-Fleet Management Not sure what this is.
Fossil DB Not sure what this is.
Fuel Dispatch SPO Not sure what this is.
Garmin GPS system?
GeoTab Not sure what this is.
Ghost EWC Not sure what this is.
GIFTS Not sure what this is.
[PROJECT] Geogrpahic Informaton System?
HCM TL/AM Not sure what this is.
Heat Rate Test Manager SP Not sure what this is.
Intra-System Billing SPO Not sure what this is.
ISB Not sure what this is.
ISONE - Finance Not sure what this is.
ISO-NE.com EWC Not sure what this is.
Kiodex EWC Not sure what this is.
Load Forecastng SPO Load Forecstng system used by SPO. Highly likely to be MS Access or XL
MAPE Not sure what this is.
Maximo Enterprise Asset Management
MDMS Meter Data Management System?
Medical Tracking & Report Not likely to impact any use cases
MEP Access SPO Not sure what this is.
MetrixND/LT Not likely to impact any use cases
Microskyshine EWC Not likely to impact any use cases
Microsoft Streets & Tips E Not likely to impact any use cases
MictorShield EWC Not likely to impact any use cases
MISCO XML Finance Not likely to impact any use cases
Mobile Web Not sure what this is.
My Account Anywhere Not sure what this is.
My eBus Not sure what this is.
MyIdenttyIQ Access Management tool
Network Directory System Admin tool
Non-PO Expense SPO Not sure what this is.
OATI Webtrans SPO Not sure what this is.
OMS Is this homegrown Outage Management System?
Operatonal Planning Weat May be used by SPO team for forecastng
PACE Not sure what this is.
PCM Not sure what this is.
PCT Not sure what this is.
PIP Not sure what this is.
Plant Market Asset Not sure what this is.
PO Not sure what this is.
POLES Poles DB
POUTAGE Not sure what this is. Not likely to impact any use cases
Power Scheduling DW EWCShould check what data this warehouse has.
Power Scheduling EWC Should check if this is the source system for the DW.
PowerCost PCI suite of tools - used by SPO
PRFATAT Not sure what this is. Not likely to impact any use cases
Price Forecastng SPO Used by SPO
Procurement Mgmt DB
PROMOD EWC Not sure what this is. Not likely to impact any use cases
PWA Project Web App from Microsoft possibly.
RadDecay EWC Not sure what this is. Not likely to impact any use cases
Report Mailer Finance Not sure what this is. Not likely to impact any use cases
Risk EWC, SPO Not sure what this is. Not likely to impact any use cases
Risk Re[PROJECT]ter Not sure what this is. Not likely to impact any use cases
RMS Not sure what this is.
RTU Remote Terminal Unit. No direct impact on use cases
SAMS Is this Software [PROJECT]
SAS Analytcs Tool
SCAM (SideCar) Should this be HANA?
SNL EWC Not sure what this is.
SoftTAkeof EWC Not sure what this is. Not likely to impact any use cases
Stores Catalog Not likely to impact any use cases
STP Not sure what this is. Not likely to impact any use cases
Substaton Querying & RepoNot likely to impact any use cases
Sybase (HR) Used by HR - being retred
Synergee is it DNV GL's gas distributon modeling product?
T&D EAM T&D [PROJECT]?
Tampering Billing
TBET
Time Entry System Finance
Tracker
Trades SPO
Transacton Mgmt System Finance
TR-Fleet Management
TSCADA Testech SCADA
TSWMS Transmission related
UIPlanner Used for Planning, Budgetng, Forecastng, and Regulatory Filing. Used by Operatonal Accountng - We have use cases
Underground Splice
Virtual RTU
Vision We have to find out what this system does
Visual Studio EWC
Web GAD
Web Tar (TRAP)
WebFG
WebTab
WebTap
Web-Trends
WFMS We have to find out what this system does. It could be Work Force Management System
Win Pack Pro EWC
Workbooks EWC
WoW
(insert row if needed) Total

12 12 12 11 43 2 27 29 26 28 9 4 2 12 10 3 13 8 8 14 7 7 7 23 26 2 2 24 25 31 8 7 31 3 2 11 12 13 8 10 9 5 12 4 4 11 14 8 12 12 15 22 11 33 32 31 33 3 9 8 11 1 1 0 10 7 8 3 4 6 7 7 6 5 5 6 5 5 3 2 2 6 1 29 29 176 1 7 7 19 1 0 1 177 12 7 0 28 24 23 1461
14 14 14 13 52 2.4 32 35 31 34 11 4.8 2.4 14 12 3.6 16 9.6 9.6 17 8.4 8.4 8.4 28 31 2.4 2.4 29 30 37 9.6 8.4 37 3.6 2.4 13 14 16 9.6 12 11 6 14 4.8 4.8 13 17 9.6 14 14 18 26 13 40 38 37 40 3.6 11 9.6 13 1.2 1.2 0 12 8.4 9.6 3.6 4.8 7.2 8.4 8.4 7.2 6 6 7.2 6 6 3.6 2.4 2.4 7.2 1.2 35 35 211 1.2 8.4 8.4 23 1.2 0 1.2 212 14 8.4 0 34 29 27.6 1753.2
Data Acquisition Assets
Total
FTP (PCI data Comparison Tool) The Real-tme Operatons team created a spreadsheet named PCI Data Comparison. It is 0
used for meter data validaton outside of the PCI-EA system.
Connector CIS Cancel Rebill Tracking - CRB is a data store of historic CIS Cancel/Rebill summary reports. The report lists cancel / 0
rebill accounts and the reason for their status which is used for metrics. The report files are created each month after
cycle 21 and than manually loaded into an MS Access DB from their source on the mainframe. The Access database is
used to generate metric reports in Excel which, after being FTP'd to another server, are picked up by users. The
applicaton is supported by a SAIC ofshore resource who handles the importaton of the mainframe report files and
the generaton of resultng Excel reports. This applicaton is associated with both METNE and JDCDBETSP007.
Connector (CMS - Call Management System) Avaya Call Management System (CMS) is an integrated analysis and reportng 0
soluton. The Avaya PBX sends events of call routng and switching of the ~23,000 calls each day to the switch
protocol interface service of CMS. These events are used to construct records of individual call details such as buttons
pressed, length, Vector Directory Number (VDN), number of segments (holds, transfers, and other legs of a call) and
any other detail that may be important to understand what is happening during call center operatons. CMS also has
metadata that defines targets such as, answer within 30 seconds, and it records whether calls achieve those goals.
Call data is summarized at 30 minute increments and every 2 hours the data is transfered into the CCO repository data
mart and cleared from the database. The current implementaton includes two CMS servers in a high-available
configuraton with both servers receiving parallel data feeds from the PBX. These servers, CMS-NO (r3entla) and CMS-
LR (r3entar), are not currently recorded in the server database. The collected data and resultng reports are essental
to enable monitoring of the overall call center operatons. Bobby Gant is the current Technical and Operatons
Product Manager and Jef Heeter s the Engineering and Backup Product Manager.
Connector "Customer Invoicing Management System (CIMS) is a web-based work management system that allows the business 0
to manage and distribute tasks associated with back office, including unbilled account errors. CIMS utlizes inputs
provided by external systems to streamline the management of both new and returned tasks. CIMS retains and tracks
inputs and updates to allow reportng on individual performance, CCS system trends and the overall status of specific
tasks.
There is a semi-manual process to query CCS for unbilled accounts. The results of that query are copied and then
pasted into a staging table for CIMS. The CIMS applicaton then parses out groups of records appropriate to the
number of hours that an agent plans to work that day. Un-processed records are returned to the database, and then
re-assigned to another agent.
CIMS has very limited functonality in assistng with the correcton of records, and it is not integrated with CCS itself.
This sometmes causes false records to be dispatched to users, and the data to become stale throughout the day."
Connector (CICIS Revenue Reportng) This is an two part interface between CIS and Peoplesoft G/L. A job on the mainframe 0
exports data from CIS and than a job in the Peoplesoft system reformats the data and imports it into the general
ledger system. The data that is exported from CIS is based of table or file changes. For example, if a new town code
is created a CIS user must enter a new line in the VCM file on the mainframe. When the mainframe job runs, it will
collect this and other changes and export it for the Peoplesoft to handle. The job on the mainframe runs once a
month but must be called in to be manually submitted. Informatonal reports also exist to provide details on what
should go into Peoplesoft in order to confirm the transfers.
Support issues currently exist on this interface. Although the individuals are very supportve, knowledge is not
widespread. This can cause issues with resolving issues or questons and has become a concern within the business.
The code can no longer be compiled on the mainframe which limits the methods of resoluton for identfied bug fixes.
Often workarounds must be accomplished utlizing other tools outside of this interface.
StackVision Use StackVision (vendor ESC) to automatcally monitor emissions from plant operatons to be submitted to the EPA for 0
compliance. Interfaces to data logger that converts data from analyzers in the stacks. Used by all plants; each locaton
has a separate server.
Vendor support agreement; SAIC supports the server.

PI system interfaces to StackVision to gather emissions data.
Must capture 90% of data per federal regulaton. No alarms if data is missing. Vendor has a system to monitor, but
cost prohibitve.
Connector Manuallll 0
FTP ITRON FTP is a COTS product used in the backend process. It's used is to upload or download meter reading data. The 0
recent upgrade from PP4 to the new FCS format supports html. There is therefore an opportunity to upgrade the
integraton with CCS to html format which gives more flexibility to include more fields. Presently there is no issue with
the security concern of meter data. [CLIENT] is using standard protocol. Current Issue - Lost connectvity
Database û Oracle
New Initatves û currently there is no new Initatves.
Interface- ITron FTP has interface between CCS and FCS.
Additonal Tool- There is no additonal tool available with ITron FTP
ITRON FTP is used to upload/download meter data into the ITRON handheld devices. As [CLIENT] moves towards an
AMI program, this applicaton needs to be ratonalized.
Connector Distributon Reportng (RT2000) is a PowerBuilder reportng system with a Report Hierarchy Viewer. It serves as the 0
reportng base for Operatons Management, MDT, Distributon, Lamp Street Light and [PROJECT](AM/FM DFM). Most
reportng, however, is being migrated to web based in-house reports and Cognos.
LAMP specific canned reports are getting generated out of RT2000; however, more reports are required to manage the
business process. There are currently 24 canned reports, and business believes they would need another 10 reports
out of RT2000.
AM/FM DFM reports have moved to in-house web based reports.
Technology: SQL Server 2008 (Not Sure) , Power builder 5.
RT2000 does not house any data; it connects to the individual applicaton database to create the reports.
Interface: It does not have interface to other applicatons for data, however it connects to individual databases to pull
informaton for reportng using PowerBuilder database connecton.
Users: Though database has 2000 users, not all of these are actve users. Probably 300 to 500 are real users.
Issue/Challenges:
1. The platform is not standardized for UDW ( Utlity Data Warehouse).
2. The reports are out of date compared to the needs.
Outside of the team there is no Power builder 5 expertze.
Connector FLEET Inventory Reportng creates Excel spreadsheet reports from the Cyndrus data. The reports are generated and
automatcally emailed monthly.
Connector P3e to Passport Interface - take scheduling informaton associated with work orders in P3e and send back to Passport
Connector TPPS2 - It is a VB.Net based applicaton and connects to RTPS . It is only used by one user who manages the third
party vendors. It can also be used for addressing real tme data.

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Enterprise Data Assets

Total
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Data Access Layer
Alignment to BI / Analytics Capabilities (1-5 impact score)
PCI DW (PCI: Data Primarily a reportng and interfacing database, the PCI Data Warehouse speeds up reportng and integraton by orders 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Warehouse) of magnitude, giving you more tme to focus on your work and your company a powerful strategic advantage. It
uncovers and exploits oftentmes hidden benefits by marrying data integraton and management with the increasingly
important areas of business analytcs and reportng.
Core 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
The tables Include master data, such as accounts, service locatons and meters. It also includes high-level billing and
meter read informaton. There were discussions around adding payments and other functonality in the past, but no
funding was available.
At first, CORE reduced ad-hoc reportng. However, there now seem to be few users (such as credit & collectons).
Some standard reports are sent to people receive on monthly basis. Other users seem to be going to IT support for
ad-hoc reports. Many business users have questons that cannot be answered by the data in CORE.
There have been discussions around putting CIS data into UDW. Small amounts of CIS data are included in UDW today,
such as lightng.
CORE was actually never moved to producton; stll running on a test server.
HDB Not found

A repository for Documentum (no other informaton found)
Access DB CIS Cancel Rebill Tracking (CRB) is a data store of historic CIS Cancel/Rebill summary reports. The report lists cancel / 1 1
rebill accounts and the reason for their status which is used for metrics. The report files are created each month after
cycle 21 and than manually loaded into an MS Access DB from their source on the mainframe. The Access database is
used to generate metric reports in Excel which, after being FTP'd to another server, are picked up by users. The
applicaton is supported by a SAIC ofshore resource who handles the importaton of the mainframe report files and
the generaton of resultng Excel reports. This applicaton is associated with both METNE and JDCDBETSP007.
Avaya Call Management System (CMS) is an integrated analysis and reportng soluton. The Avaya PBX sends events of 1 1 1 1 1 1 1
call routng and switching of the ~23,000 calls each day to the switch protocol interface service of CMS. These events
are used to construct records of individual call details such as buttons pressed, length, Vector Directory Number
(VDN), number of segments (holds, transfers, and other legs of a call) and any other detail that may be important to
understand what is happening during call center operatons. CMS also has metadata that defines targets such as,
answer within 30 seconds, and it records whether calls achieve those goals. Call data is summarized at 30 minute
increments and every 2 hours the data is transfered into the CCO repository data mart and cleared from the database.
The current implementaton includes two CMS servers in a high-available configuraton with both servers receiving
parallel data feeds from the PBX. These servers, CMS-NO (r3entla) and CMS-LR (r3entar), are not currently recorded in
the server database. The collected data and resultng reports are essental to enable monitoring of the overall call
center operatons. Bobby Gant is the current Technical and Operatons Product Manager and Jef Heeter s the
Engineering and Backup Product Manager.
Revenue DW Some of the difficulty in supportng the system includes data validatons. SAP is so flexible that users can do many 1 1 1 1 1 1 1 1 1 1
PI Historian Used for storing PMU data and additonal data associated with the Phasor project. Could be used as a data historian 1 1
for other operatons data including EMS as a replacement for Pegasus.
SIdeCar (HANA) Not found 1 1 1 1 1
COS Not found
SQL Server DB Front Desk and Back Office personnel will use the system to create reservatons and manage check-in and check-out.
Beverly Newton puts the meetng and room requests directly into Epitome and maintains any changes. Beverly also
keeps a paper list of all meetng partcipants and gives the lists to the front desk every Wednesday. The front desk
then enters in the details. Staf performs a nightly audit through Epitome to see if guests are actually staying in a room
or if anything was left behind.
Employees can schedule a stay at the PowerHouse through the travel center even if the meetng is not at the
PowerHouse. Travel center emails Beverly directly. Beverly manages the room wait list on an Excel calendar. There
were discussions to put the availability online for employees to see, but it was not done due to it being too frequent
in changes
BW (SAP Business o Has 16 users 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Warehouse) o By next year may ratonalize it away
o It ONLY contains data from CCS – used for reportng without impactng producton
o Been here for 15 years
UDW A data warehouse is [CLIENT]'s relatonal or multdimensional database that is designed for query and analysis. They 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
are not optmized for transacton processing, which is the domain of OLTP systems. UDW consolidates the historical
and transactonal data derived from multple sources. Data warehouses separate analysis workload from transacton
workload and enable an organizaton to consolidate data from several sources. UDW does not consume all the CRM
data enttes such as payments
EPM / SART (Spend Analysis Past process: any tme SC needed spend data, and need to find out what was spent before, it was a manually intensive 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Reportng Tool) process (pull from diferent systems). Diferent functons would pull diferent data and get diferent results. Did not
have one place to pull the data. Have algorythms that sift through data from various sources including AP, go through
account codes and determine what to include and exclude, automated categorizaton of spend to the point there is
some manual manipulaton. Every invoice payment comes into database, matches to category IDs, vendors,
commodity codes. Example - "Vegetaton Management, Tree Trimming". Uses COGNOS that allows reportng of spend
based on functon, categories, etc. Can compare spending to prior years. Provides drill-down capability to more and
more details.
Pro-forma tool allows to manage mappings to categories.

A lot of work to contnue to improve the accuracy of the algorythms.
Used to: negotate, prepare bids, evaluate bids. When executves want to know what our spend is by certain suppliers,
or by region, they can use SART to provide the informaton. Jurisdictons may request informaton for spend by
suppliers. May use to help determine how best to leverage suppliers.
Issue: occasionally have trouble pulling lots of data and/or handling complex queries. They will pull some data into
access. COGNOS is supposed to have a filter limit of 1,000 but at 300, running the report takes too long. Share a server
for CR&A? maybe quick win?
EPM The current system does not contain the same reportng capabilites as the legacy reportng environments, HRAR
and HRAIR. In additon, not all the data that is present in those systems is available the Cognos reportng system,
HRRA. In the short-term, HR should evaluate the informaton model that is present in EPM and re-architect it to
contain the reportng structures necessary to fulfill current and future reportng requirements. PeopleSoft Enterprise
FDW (2005 historical data) Performance
The Financial Management Data(FDW)
Data Warehouse Warehouse is the book
is a repository of records
of historical for [CLIENT]'s
financial Financial
data from 1994 -data.
2007. It is statc data used 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
for historical reportng. Finance uses Access to pull data out of there. It contains data on all transactons that would be
rolled up to create financial reportng. The data stored is at a high level from Finance perspectve i.e. an aggregate of
diferent line items and not granular enough to contain retail customer level data. The data goes back to 1994. FDW
supports ad hoc queries to support requirements for Legal, Regulatory, RFI, etc.
IT has recommended that FDW be decommissioned, as it stores statc data only, is not updated, is not used for
generatng reports and does not interface with any other applicatons. However, the business has pushed back on this
idea.
Cognos Cognos Business Intelligence Environment. Used by project managers and cost control personnel to pull a multtude of
reports related to project cost.
SalesPage SalesPage is a CRM tool used by distributon account managers. It allows access to metering, collectons, and outage 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
informaton, as well as customer specifics. SalesPage can also produce and schedule weekly actvites for the group. It
is used to track customer meetngs, visits, and important phone calls.
The EBC uses SalesPage to manage outages for managed accounts. The system produces automated reports showing
outages from each jurisdicton from 6:00AM to midnight of the previous day.
SalesPage captures additonal new load (new facility or expansion) that will be built within the system for the middle
market. Currently this informaton is only used internally; it is not reported to System Planning or used to meet with
the customers.
The component known as the Business Analytc Tool is used to produce a Growth Margin Report. SalesPage captures
AGM (revenue less fuel and certain riders such as ANO) for reports to upper management. The business then uses an
Excel spreadsheet (AGM Calculator) to calculate annual KWH and AGM by entering the load factor and estmated
demand. This informaton is entered back into SalesPage, and the Business Analytc Tool then generates reports such
as AGM Summary for the utlity president, Detailed AGM Summary for each jurisdicton president, or individual
consumpton and Actvity Reports at the organizatonal or team member level. The Business Analytc Tool also allows
users, with training, to write custom reports.
SalesPage has the potental to track informaton about contacts and partcular accounts. It has been useful when
people have moved on and new people picked up the customer. However, it stll has room for further adopton. A
recent ECI team asked for feedback; many were stll not using it. The ECI Team will explore the possibility of replacing
with other vendor systems such as SAP or salesforce.com (early 2012).
Informaton is loaded from AIS, CCS (via BW), AM/FM, SAISO, and CIS. All of these are import interfaces only. [CLIENT]
PCI Business Intelligence: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
PCIÆs Business Intelligence (BI) Analyzer suite transforms raw data into meaningful and useful informaton for
optmized decision making. PCI delivers a ôBusiness Discoveryö analytcs tool kit that redefines the BI concept and is
tailored exclusively to informaton-hungry ISO market partcipants that want to gain market and operatonal insights as
quickly and easily as possible.
PCI BI Analyzers increase your ability to make enlightened and impactful decisions. Any user can create tailored
insights that not only meet their unique needs and tmelines, but also do it in a way that more rapidly advances
objectves and enterprise-wide success.
PCIÆs Data Warehouse is the primary source for our BI Analyzer suite.
PCI Analyzers allow you to:

Visualize market and operatonal trends
Compare important data such as energy prices, volumes, fuel burns and profits across positons and through tme
Expedite analyses by quickly slicing and dicing large volumes of data, while allowing you to drill down from annual
portfolio summaries into monthly, daily, hourly and even sub-hourly positon details
Monitor Key Performance Indexes (KPIs)
Profit & Loss (P&L) Analyzer:

Often described as ôsettlements for the Front Office,ö P&L Analyzer creates a unique feedback loop for traders to
better understand the settlement impact of their bids, ofers and trades. It combines settlement data with unit cost
calculatons to quickly assess portfolio profitability in the Day-Ahead (DA) and Real-Time (RT) markets. Although the
business rules, charge codes and cost calculatons vary between ISO markets, the format and functon of P&L Analyzer
remains consistent across all ISOÆs, which makes it ideal for single and mult-market partcipants.
Since all DA and RT market data is automatcally consolidated in one place, your staf can easily identfy any ôP&L
Leakageö which occurs when Real-Time P&L drops relatve to Day-Ahead P&L. P&L Analyzer shows yearly down to sub-
hourly tme intervals (across positons) so users gain great insight into performance
trends for:
ò Units
ò Loads
ò Virtual Transactons
ò Trades
ò FTRs/TCRs/CRRs
TPPS TPPS Query provides Payment Processing Group with a reportng and/or querying tool that provides greater access to 1 1 1 1 1 1 1 1 1 1 1 1
key TPPS tables/data fields and achieves greater flexibility in data search criteria. It is Cognos based. There are no real
tme data feeds. It queries data that is already there in the data mart. It is used more from the point of view of
conductng analyses for trends and patterns.
IKW (Asset Suite) Knowledge Warehouse (IKW) is used for reportng based on Asset Suite data. Data from Asset Suite tables are copied 1 1 1 1 1 1 1 1 1 1 1 1
so that reports can be run against the Knowledge Warehouse instead of Asset Suite Producton database.
The reason to have a separate warehouse was that during the inital implementaton period, it was discouraged to
load the producton database with queries. Also, there are other applicatons which require Asset suite data. They
also get the data from the data warehouse. Many tables in the warehouse are exact replica of Asset Suite tables, while
others are normalized. Only selected data is present in the warehouse - about 1/3 of asset suite data volume.
Knowledge warehouse uses Oracle Backend, Informatca, and other Oracle tools. The thick-client is used by Admin.
Other users connect from Access via ODBC to the Knowledge Warehouse.
The frequency of updates from the Asset Suite varies from 6 tmes a day to once a day. There are some Jobs which are
also run at 6 min interval. Real tme reportng is provided by Ventyx through Real-tme performance Monitoring (RPM)
[It is not truly real tme though]
There are about 300-400 users. Access is maintained at database level. Also, there are about 100 users in the area of
Supply chain, Finance and corporate users.
Issues:
a) Instances of slower response tme for 2-3 tmes in last 9 months, since the tme the storage was moved from EMC
to Hitachi NetApp storage even though it is being used as per the specificatons. This would require a long term
soluton as it negatvely impacts SLA.
Key Planning and Indicator Reports are required 5AM each morning as they are used to confirm and plan daily plans.
Any delay in the report generaton would impact the business process.
b) Management type Dashboard report tools can be implemented. Although Crystal reports are already available, the
opportunity to Re-engineer /get a better output may also be looked into.
Suggestons:
1) Improve Batch Job Runtmes (it takes longer tme to run)
2) Standardize user access to reportng - Website, Shared files.
3) Provide a facility for Ad-hoc report generaton û Currently user's access producton data for this.
DEVONWAY Data repository for the Dashway applicaton (remote hosted). SAIC supportds the FTP and load of this data.
This applicaton was replaced by Nuclear Performance Indictor (ENOPI)
It was originally included in my list of Safety applicatons, but per Keith Gardner, it tracks performance indicators which
includes data from many apps and not Safety specific.
DashWay(Devonway) Dashway is an SAAS based applicaton from the vendor Devonway used as Nuclear performance indicator tool. It
collects and calculates the Nuclear performance indicators by using the monthly inputs provided by functonal areas
(12 units worth of data).There are a few quarterly inputs as well. This data is then used to create an index for each
functonal area (e.g. - Maintenance, Radiaton protecton etc.). The PIÆs are reviewed in the site management
meetngs held every month and also in the fleet management review meetng every trimester. An excel spreadsheet
was being used prior to Dashway for calculaton of PI. Dashway has brought consistency in calculatons and
presentaton of the PI data from each group. Some of the key attributes are also exported from Dashway to the
corporate (capability factor).
[CLIENT] submits approximately 500 performance indicators to INPO applicaton CDE (Consolidated data entry
system).INPO shares some of the performance indicators directly with NRC. There is some automaton within Dashway
for data collecton. The conditon reportng metrics are collected automatcally from CAP Performance Index. Also, the
backlog metrics are calculated automatcally for Asset Suite data (from IKW).
There is some manual overlap between the data entered into INPO's system (CDE) and Dashway. Also, the HCM
initatve is robbing existng experience on how to manage the data entry.
The ID/Password needs to be maintained internally because there is no link to UCAMS. The passwords are not synced
with Actve Directory (must be maintained by IT) which is painful. DashWay does ofer integraton but [CLIENT] will
need to implement it. The passwords are not up to true standards.
The business believes that the reportng capability should have been more robust with adhoc reportng capability.
The business had also looked at Cognos before selectng Dashway, but Dashway was selected as it is more focused
towards the Nuclear industry.
Passport IMVAL This applicaton retrieves inventory positon informaton at the end of the month for every Transmission and 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1
Distributon facility in Asset Suite. The informaton is copied and appended to another table within the database. The
database contains historical positon and price informaton. The applicaton adds nearly 260,000 records every month.
The system was created because there was a belief that informaton contained in an Indus Knowledge Warehouse
table was not being kept sufficiently current.
After the implementaton of Asset Suite, several business processes were under supported. Due to resource
constraints and budget issues, both within the business and IT, the business developed small, "one-of" reportng and
tracking systems. Some of these systems were developed because although the informaton could be extracted from
Asset Suite, it was deemed complicated relatve to creatng an additonal system to provide the same informaton
quicker. Although Indus Knowledge Warehouse contains a robust set of informaton regarding inventory, purchases,
and contracts, it acts primarily as a data source for other reportng and analytcal systems. These other systems are
managed by people throughout the organizaton, leverage a variety of access methods, and contain data that is
duplicated in producton systems. Supply Chain should consider centralizing and standardizing the technology
required to develop and use tracking reports and other analytcs. By centralizing and standardizing these access
methods, many systems can be eliminated, Supply Chain employees will be more efficient, and costs should be
reduced.
NDW (Nuclear Data "The Nuclear Data Warehouse is a repository of archived databases. It includes systems such as Maximo from each of
Warehouse) the original instances (IP2, IP3, PNP, JAF), as well as other legacy systems. These databases can be queried by
dedicated tools, Access databases, and/or Crystal reports depending on the specific database and user group.
These archived databases need to be retained for reference purpose even after the original system may have been
reclaimed."
The Nuclear Data Warehouse should be ratonalized in the Mid-term with an Enterprise Datawarehouse which can be
used to store archived data from legacy applicatons for future reference.
Query Outage The purpose of the Outage query extract is to run outage correcton reportng, customer based outage reportng, 1 1 1 1
major storm reportng and other adhoc reportng to run the business. SAIDI, CAIDI and SAIFI reports are derived out of
Cognos. Outage query extract provides all other data which Cognos does not provide related to outage.
Outage Query Extract copies certain tables from the AM/FM Oracle servers and copies to SQL Server database for
reportng. Data is copied each morning at 4:00. No front-end as part of this system. The Performance Metrics group
maintains Access databases that attached to the backend.
When new tables or fields are added to AM/FM, changes must be made to Tactcs.
Most new reports are getting created using reportng services. Old reports are in .
Interfaces: AM/FM
Users: T&D Op, [PROJECT], Asset Planning , Management ( Directors) , DOC
Critcal account informaton source of record is not known. POutage gives the customers those called but it does not
have the list of customers those are live out. Part of the informaton is in CCS but not in Distributon, so cannot have
the report generated out of Outage extract.
TPPS Query & Reportng TPPS Query provides Payment Processing Group with a reportng and/or querying tool that provides greater access to 1 1 1 1 1 1 1 1 1 1 1 1
key TPPS tables/data fields and achieves greater flexibility in data search criteria. It is Cognos based. There are no real
tme data feeds. It queries data that is already there in the data mart. It is used more from the point of view of
conductng analyses for trends and patterns.
APS/PDW No informaiton found - via discussion - it is home grown staging area that gets all kind of informaton form multple
sources based on ad-hoc requirement and create reports
SCAM
TPPSQR Query & ReportngThis the reportng DB for Third Party Payment System (TPPS)
OP-Prod Not sure what this is.
HR Sybase This extracts data from PeopleSoft and makes it available as Sybase Views for HR team run analytcs. (To be retred)
OBIA Oracle Busines Intelligence Applicaton - How and where is this used? What data does this hold? What is the data source?
Oracle Oracle Database - How and where is this used? What data does this hold? What is the data source?
Access How and where is this used? What data does this hold? What is the data source?
Sybase How and where is this used? What data does this hold? What is the data source?

5 3 2 4 6 2 4 6 4 6 0 4 0 2 3 3 6 3 3 6 8 8 8 5 5 3 3 5 6 11 7 7 11 0 0 2 2 2 1 3 3 1 2 0 0 1 1 0 0 0 1 4 0 5 4 4 5 0 1 1 2 0 0 0 6 7 6 3 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 6 6 15 0 0 0 3 0 0 0 15 4 2 0 6 4 3
7.5 4.5 3 6 9 3 6 9 6 9 0 6 0 3 4.5 4.5 9 4.5 4.5 9 12 12 12 7.5 7.5 4.5 4.5 7.5 9 17 11 11 17 0 0 3 3 3 1.5 4.5 4.5 1.5 3 0 0 1.5 1.5 0 0 0 1.5 6 0 7.5 6 6 7.5 0 1.5 1.5 3 0 0 0 9 11 9 4.5 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 9 9 22.5 0 0 0 4.5 0 0 0 23 6 3 0 9 6 4.5
Information Management &
Governance Assets
SAP/ISU-CCS Some of the difficulty in supportng the system includes data validatons. SAP is so flexible that users can do many
PI PI DataLink - Excel add-in that provides SDK that allows personnel to pull in plant historical data from the PI. consider
building standard reports
Access DB The ISONE Database is a MS Access database which is used to assemble the ISONE Settlement informaton with an
end result of the ISONE Reconciliaton spreadsheet. The ISONE Settlement daily files are placed onto the ISONE FTP
Server which the user manually pulls the daily files down onto the [CLIENT] Server. Once the daily files have been
placed onto the [CLIENT] Server, the user opens the ISONE Database and uses this MS Access database to import the
daily files into the database. The ISONE Database will assemble the daily files that were imported into a single
calendar month file. Once the calendar month file has been created then the file will be exported into the ISONE
Reconciliaton spreadsheet. This spreadsheet is used for the use of the ISONE Settlements. There are User desknotes
for the documentaton on the ISO NE Database.

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Security Assets

0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0 0
Platform Assets
Total Readiness Score 22 19 17 19 61 5.4 38 44 37 43 11 11 2.4 17 17 8.1 25 14 14 26 20 20 20 35 39 6.9 6.9 36 39 54 20 19 54 3.6 2.4 16 17 19 11 17 15 7.5 17 4.8 4.8 15 18 9.6 14 14 20 32 13 47 44 43 47 3.6 12 11 16 1.2 1.2 0 21 19 19 8.1 4.8 7.2 8.4 8.4 7.2 6 6 7.2 6 6 3.6 2.4 2.4 7.2 1.2 44 44 234 1.2 8.4 8.4 27 1.2 0 1.2 235 20 11 0 43 35 32.1

Analysis Demand Profile

Încărcat de

Informații document

Titlu original

Drepturi de autor

Formate disponibile

Partajați acest document

Partajați sau inserați document

Opțiuni de partajare

Vi se pare util acest document?

Este necorespunzător acest conținut?

Drepturi de autor:

Formate disponibile

Analysis Demand Profile

Încărcat de

Drepturi de autor:

Formate disponibile

Purpose

This tab contains general information about the workbook

General Guiding Principles

Version Person Date

C Analytics Capabilities - Future Demand Name of use case

Component of impact score,

Component of impact score,

Group of business units impacted

AP Energy Wholesale Commodities (EWC) Business Unit

Customer Systems (Respond to

CF [PROJECT] Data Source Characteristics

CI [PROJECT] In Flight Initiatives Characteristics

CJ [PROJECT] In Flight Initiatives Characteristics

CK [PROJECT] In Flight Initiatives Characteristics

CL [PROJECT] In Flight Initiatives Characteristics

CM [PROJECT] In Flight Initiatives Characteristics

All the information captured are

Data Source Assets

Utlity Operatons - Integrated Energy Management

Utlity Operatons - Customer Systems , BS Apps

Creates a More Robust and Modernized Grid

Modernizing and Transformatve Projects

Fossil, Fossil Environmental Special View

Innovatve Products and Services

Utlity Operatons - Distributon

Make Productve Investments

Customer Service Excellence

Strategic Value Drivers

Business Value Drivers

Physical and Cyber Security

Business Unit Impact

Energy Market Ops / SPO

Utlity Operatons - Gas

Agile & Elastic

Can we design a better way to model revenue

More granular insight and recommendatons on how

More granular insight and recommendatons on how

Compensaton / Human X Ability to pull together multple sources of employee

Improve access management through actvity-based

X Accurately project hour by hour output based on

Automate maintenance system to improve

X Attach financial data to assets in order to improve

(insert row if needed)

Analytics Capabilities - Existing Projects

ARCOS Call out and scheduling system 1 1

One Source Not found 1 1

Currently, over 1,000,000 accounts have re[PROJECT]tered through MAO.

Large Power Billing Informaton Not Found 1 1

PCI: Energy Accountng Energy Accountng: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

PCI: Generaton Supply Solutons: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

PCI: Asset Operatons Asset Operatons: 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1

Address files are sent to Bowne for standardizaton.

ACSSI Not found 1 1

Change Request Informaton 1 1

PI (Plant Informaton System) Plant Data archiving tool. 1 1

What does it not do?

IKW Reporrtng This IKW

Used to manage project manager training and qualificatons

Plot Log None 1 1

Interfaces: Exchange/SMTP (notficatons)

ò Integraton 1: Code Block Validaton

EB (Enterprise Bridge) Nuclear Document Management system. 1 1

Gas Platform None 1 1