Single GPS Vendor Migration Project Update

Date: February 5, 2015

1

Agenda

2

Key briefing items: Project Overview Primary System Design Installations / Migration System Integrations Secondary System Design Leveraging Information into Actions Best Practice Review & Enhancements

Project Overview

3

Primary System Design

Installations / Migrations

Systems Integration

Secondary System Design

Turning InfoInto Action

BestPractice

Core Team

Fleet Team

I. T. Team

End User Team

..Feb - Apr

……….Feb - Jul

………….…….Feb - Mar

………..……….…….Apr - Jul

……..…..……….….Oct – On-Going

…………….…..……….…….Dec – On-Going

Primary System Design / Build

4

Structure for System Built - follows accounting structure

Ease of Linking to Other Company Systems Reports Available at Each Level of Structure

System Attributes Established Vehicles Loaded with Consistent Naming Conventions User Names / Passwords Created Access / Security Set for Users Landmarks / Hotspots Recreated Automated Reports Rebuilt

Portable Units On-Site Script Approved Developing Process & Procedure

Primary System Design

Installations / Migration

5

Installations

Schedule• Mass East Started 1/19 – 2/28• Mass West Start 2/23 – 2/28• Connecticut Start 3/2 – 4/11• PSNH / Mass Gas - TBD

Weekly Metrics – % Attainment - Target 250 Per Week

Migration to New Enterprise Massachusetts East -Week Ending 2/7 - Old Enterprise Archived,

New Enterprise Activated• Limited Access/Use by Users• Users Login After the Migration as Usual, but will be Pointed to

New Enterprise.

Installations / Migrations

System Integrations

6

Internal Outage Maps (Conn. & Western Mass.) & New

Enterprise Connectivity Live Data Feed Configured & In-Place (Test Environment)

• Vehicle location• PTO Usage• Driver Identification – (future functionality)

New Fleet System Company A New Enterprise Built with Future Connectivity Ability –

single point of entry• Push information from vehicle (vin, make, model, trouble codes,

etc.)• Pull information to system (create, reassign, etc.)

Systems Integration

Secondary System Design

7

“Get the right data to the right people at the right time”Reporting – (business rules, recipients, formatting &

delivery) System Canned Reports & Custom Designed Reports Additional Reporting Requirements

Training Outlines, Audiences, & Attendees

Coin FOB Type & Method to Deploy, Process & Procedure

Portable Devices Ownership, Storage Location, Process & Procedure

Post Implementation System Ownership, Roles & Responsibilities Additional Assets Requiring Devices

Secondary System Design

Turning Information Into Action

8

“Taking ownership by integrating new information into daily operations” Incorporating Information Into

Daily Interactions & Communications Weekly & Monthly Meetings

Accessing Live System Desktop, Laptop, Tablets & Phones

Leveraging DatafeedsOutage Management SystemFleet Maintenance Application

Turning InfoInto Action

Best Practice Review & Enhancements

9

“Identifying additional ways to strengthen our return on investment”

Perform Critical Review of System with Internal Subject Matter Experts: System Use (storm / non-storm) Functionality Reporting

Leverage Company A’s Experience with Other Customers System Use Case Studies / Success Stories

Hold Best Practice Meetings with: Other Utilities Similar Industries

BestPractice

10

Appendix

Custom Report Examples Driver Safety Non-Productive Idle Tracking Crew Field Data (depart / arrive) Supervisor Colocation

Driver Identification Hardware Oversight Committee / Core Team Members End User & Fleet Team Members

11

ReportingDriver Safety Non-Productive Idle Tracking• Speeding• Hard Braking• Hard Acceleration

• Non-Productive Idle Time• Non-Productive Idle Cost $$• Non-Productive Idle Alerts

12

ReportingCrew Field Data Supervisory Field Data• Time Stopped “In-Field”• Time at Service Center• Travel Time

• First Job Site Arrival Time• Total Co-Location Time• Last Area Work Center Arrival Time

Driver Identification - Hardware

13

Driver Identification –

• Installed during GPS Upgrade process (for cost savings), but NOT ACTIVE• Labor Having Discussions with Locals

Coin Reader – Installed into the dashboard of vehicles (near ignition)

Coin FOB / “Dallas Key”

Exec. Oversight Committee / Core Team

14

Core Team ORG.Mass. Elec.Mass. Elec.

Operations ServicesOperations Services

Conn. Elec. I.T.

Company ACompany A

Core Team Key ActivitiesContract Negotiation / ApprovalProject AuthorizationMaterial AcquisitionLabor NotificationsIdentification of Driver Identification OptionIdentification of Resource NeedsCreation of Detailed Project ScheduleEstablish Data-feed to DispatchSystem Build Hierarchy – Views of System I.D. & Create Landmarks / Points of Interest Create vehicles, users, drivers, devices, etc..Reporting Build / Test / Approval /DeploymentReport Delivery Methods – Frequency Push / PulledTraining RequirementsTraining DeliverySystem Maintenance – On-going

Project Sponsor ORG.Operations Services

Oversight Comm.

ORG.

Mass. Elec.Mass. Elec.Conn. Elec.NH Electric

GasSup. Chain / Env. /

Property Mgmt

End User & Fleet Team Members

15

Fleet Team ORG.Mass Elec.

NH OpsConn. Elec. & Gas

End User Team ORG.Mass. Elec.Mass. Elec.Mass. Elec.

NH OpsGas OpsGas Ops

Conn. Elec.Conn. Elec.

Customer CareEnvironmentalSupply Chain

Key Activities End User TeamIdentify Training NeedsAid with System Build RequirementsAid with System Naming ConventionsI.D. Needed Hot Spot / Points of InterestsIdentification of Alerts to be Built / RebuiltIdentification of How to Distribute Coin FOB’sIdentification of Business Rules: Start / Stop Times Take Home Vehicles Paid / Unpaid LunchesReporting Build / Test / Approval /Deployment

Key Activities Fleet TeamIdentify Training NeedsAid with System Build RequirementsIdentify Consistent Vehicle Naming ConventionsIdentification of Key Facility Contact PersonnelIdentification of Each Locations Hrs of OperationAccess to : Facilities, Vehicles, Keys