1. Jack Stickel Alaska Dept of Transportation & Public Facilities
Data Business Plan
for Planning
Data Management Programs
March, 2005
a.k.a. AI2
Juneau, A
Jack Stickel
Alaska Dept of Transportation &
Public Facilities

2. Data Business Plan Data Business Plan Goal
collecting the right data, distributing it to the right people, and applying it at the right time

3. Why A Data Business Plan
Quality data for decision support information:
Allocating funds across work programs and STIP
Measuring changes in transportation network
Generating condition & performance reports
Allocating funds to meet Federal reporting
Planning highway design & safety improvements
Managing personnel and assets
Providing for government, legislative & public
requests

4. Data Business Plan What is a Data Business Plan:
Understand the existing data management programs
Align data management programs with the Department’s mission and goals
Increase the return on investment (ROI) for data management programs
Provide a long-range plan for data management programs to meet future needs

5. Data Business Plan Understand the data management programs:
What data are being collected and by whom?
How is the data collected (procedures, equipment, coverage)?
What data standards & best practices are used?
What data processing steps are involved?
Where is the data stored (raw,verified, summarized ?
What record keeping procedures are used?

6. Data Business Plan Understand the data management programs :
Who uses the data and what are their business processes for decision-making?
Are there multiple sources for similar data?
Are there or should there be ownership and/or gatekeeper controls?
How is the data accessed (PC, network, workstations)?
What is the cost of data programs?

7. Data Business Plan
Align programs with the Department’s mission:
Agency - “Providing for the movement of people and goods and the delivery of state services”
Division - “Optimize the state investment in transportation and meet federal requirements through effective planning and programming”

8. Data Business Plan
Align programs with the Division’s data related core services:
“Provide federally required highway data collection and analysis to state, federal, and local agencies”
“Provide Geographic Information System (GIS) data collection and analysis, as well as cartographic and other technical services”
“Develop and administer the State Highway Safety Program”

9. Data Business Plan Increase ROA for data management programs:
Reduce data redundancy and costs
Minimize knowledge loss due to turnover and retirements through documentation
Define data management programs performance measures
Provide necessary investments in data management programs

10. Data Business Plan Provide a long-range program for future needs:
Ensure data users and providers have the same understanding of data program issues
Clarify who uses data systems and under what conditions
Describe the operational needs for data collectors, data keepers, and data users
Define new data delivery approaches
Promote data sharing & integration across organizational boundaries

11. Data Business Plan Scope of project:
Establish limits - planning data programs only
Determine stakeholders - who are the data collectors, stewards, gatekeepers, and users
Incorporate experience - determine who has experience in developing business plans (FHWA, TRB Peer Exchange)
Follows system engineering guidelines - ITS Final Rule

12. Data Business Plan Steps in project (2005 - 2007):
Concept of Operations - (Sep 2005)
Risk management - how programs are doing
Performance measures - internal metrics for program measures
Investment validation - measure value of new systems
Data program adaptability - data needs to meet new Department/FHWA requirements

13. Business Data Plan
Concept of Operations will:
Document the physical infrastructure of the data programs
Identify how data management programs fit into Department operations
Provide expectations on how future data programs will evolve

14. Business Data Plan
Concept of Operations looks at:
All interfacing systems and stakeholders in four data management areas
Existing procedures and documentation
Associated technology, business processes, and work center relationships

15. Business Data Plan Concept of Operations data management areas:
Data Systems
Legacy mainframe systems
Geographic information system (GIS)
Asset management system
Pavement Management System (PMS)
Traffic data system
Highway Safety Improvement Program (HSIP)
Bridge Management System (BMS)
511 Traveler Information System
Road Weather Information System (RWIS)
Temperature Data Probe (TDP)

16. Business Data Plan Concept of Operations data management areas:
Data Infrastructure
Data warehouses / data marts
ITS Architecture ADUS
Spatial geodatabase
Data integration, sharing, & linkage
Data access - web and internal network
Communication & networking
Anticipated technologies

17. Business Data Plan Concept of Operations data management areas:
Data stewardship
Data collection plans
Inventory processes
Data processing
Data reporting
Data Storage
Metadata
Value-added data programs
National / local best practices

18. Business Data Plan Concept of Operations data management areas:
Data standards and data partnerships
State IT Plan, State IT Standards, & web standards
ISO, IEEE, ITE, ANSDI applicable standards
Nationally recognized standards (MMUCC)
State law confidentiality rules and liability
ITS National Architecture & Final Rule
ITS regional architecture - Iways & Anchorage
511 & RWIS partnerships
DMV, Emergency Response, Epidemiology, Vital Statistics partnerships

19. Business Data Plan Future data business plan work will address:
Standards - naming conventions, data dictionaries, data exchange
Data integration - future data resource opportunities in a GIS environment
Data sharing - data formats, protocols, access
Data quality - standards, exceptions, data flags, timeliness/availability
Data models - existing and new logical/ physical architecture