REMINDERCheck in on the

COLLABORATE mobile app

Los Angeles MetroMeasure R Public Dashboard

Prepared by:Julie Owen (LA Metro) and Rudy Ising (DRMcNatty and Associates)

Updating General Public with Project Status Updates

Session ID#: 15449

Agenda

■ Background▪ LA Metro Measure R and PMIS

■ Problem Statement▪ Needs Assessment

■ Solution■ Architecture

▪ How it Works■ Dashboard Demo■ Lessons Learned■ Conclusions■ Future

PMIS Background

This is a subtitle or bulleted list

Background

■ LA Metro

• 3rd largest public transportation system in US■ Measure R

▪ $40B in transportation upgrades▪ 30 year program, 550,000 new jobs▪ Increased oversight and accountability▪ Potential aggressive / accelerated schedule▪ Maxes out Metro resources

Enter—Project Management Information System (“PMIS”)

PMIS

■ Centralized repository■ Improved data accuracy■ Automated financial data ■ Proactive / Timely project status■ Enhance communication by removing silos■ Provide project and program performance, current status, and

forecast trends■ Data available via web for stakeholders

Problem Statement

■ PMIS focused on internal project management.■ Need to provide general public accurate project status.■ Reduce manual efforts to accurately describe progress.■ Provide an auditable means of presenting information to

public.

Needs Assessment

■ Dashboard considerations:■ Cost to deploy and maintain

■ Ease of use for end users

■ Portability/browser neutrality

■ Administration of publication

■ Security

Hosted Solution

■ Dashboard design hosted in same environment as primary PMIS software tools.

■ Facilitates security, data transfers

Dashboard Solution

This is a subtitle or bulleted list

Dashboard Solution

■ Custom Dashboard■ Use of pre-built elements

■ Modular for ease of design configuration

■ Platform/Browser neutral

■ Ability to conform to Metro design standards

■ Automated data retrieval using web services■ Custom Administration component

■ Audit

■ Publication Controls/Reviews

■ Maintain publication history

■ Data security

System Architecture

Data Sources queried as scheduled services via secure and automated processes

Review and Publication performed securely on Dashboard Server

Public only has access to current published dataset

System Architecture

■ Dashboard design uses the following data sources:▪ Primavera P6

— This includes primary schedule information as well as other general updated information (such as scope and status updates).

▪ Ecosys— FIS (financial) data is included in the Ecosys data so no need to pull

directly from FIS.

— Change information recorded in Primavera Contract Management (PCM) is also brought into Ecosys so this is included in the Ecosys data.

System Architecture

■ Architecture▪ Kettle is used to extract and import data into Mongo database

containing all Dashboard data.▪ A custom Dashboard Administration function is built into this

site, to perform review and publication tasks.▪ Hicharts and other javascript web components are used to

display the dashboard content.▪ All of the site is contained within secured systems.

■ Accessibility▪ Dashboard is browser neutral, requires no java or other

applications to run.▪ iPad, mobile accessible.▪ Compatible with Metro.net accessibility requirements.

How it Works

■ Data extraction from PMIS systems automated.■ Dashboard administration handled through security built into

dashboard.▪ Complete audit trail of review/publication process.▪ Complete control over content that is made public to assure

accuracy and quality control of data.

Begin Review

Financials Close; 

Begin Review

How it Works

■ Monthly, Metro staff reviews datasets for publication.▪ Roles include reviewer, administrator and publisher.

■ All transactions (review/publication) include email notifications to participants.

■ Data extraction performed nightly so any corrections noted can be made and next day’s dataset can be used with corrections.▪ Only Publisher role has rights to make the dataset public.

Begin Review

Financials Close; 

Begin Review

Review Content

How it Works

■ Only current published dataset is accessible to public.▪ Publication is tied to official Metro financial closing, so process is

integrated to the normal project management processes.■ Historical or rejected datasets are accessible to Dashboard

administrator role but not accessible to public.

Begin Review

Financials Close; 

Begin Review

Review Content Publish Archiving

Dashboard Administration Workflow

Begin Review

Financials Close; 

Begin Review

Review Content Publish Archiving

Measure R Dashboard

This is a subtitle or bulleted list

Measure R Rail Dashboard

Multiple Graph Options

Project Color Coding to Match Metro.net Standards

Project Scope View

Project Scope and Map

Links to other resources

Project Status View

Status updated in P6 

Notebooks

Project Photos

Project Cost View

Costs by Phase

Context Help Throughout

Context Help for Public

Project Schedule View

Mouse over for Dates

Schedule Milestones

Key Milestones include Baseline Dates and Forecast/Actual

Lessons Learned

■ Develop data requirements early on to avoid re-programming.■ Engage management input for level of data to publish■ Keep Project Management input and data review

requirements simple to facilitate buy in.

Conclusions

■ Dashboard design has simplified the publication of project status to the general public.▪ Previously, work effort to publish project information on

Metro.net pages required project managers to be less productive.

▪ Dashboard design provides archival (historical) view of what was conveyed to public in each update—previously difficult and time-consuming for staff.

Future Plans

■ Public Facing Dashboard Additions:▪ Measure R Highway Projects▪ Other Metro Project Portfolios

■ Internal Use Dashboard▪ Management/Project Management Use

Please complete the session evaluationWe appreciate your feedback and insight

You may complete the session evaluation either on paper or online via the mobile app