Alaska s Transportation Asset Management Information System (TAMIS) Proof of Concept
|
|
- Marion Ward
- 5 years ago
- Views:
Transcription
1 Alaska s Transportation Asset Management Information System (TAMIS) Proof of Concept presented to 2016 GIS-T Symposium - Raleigh, North Carolina presented by Bruce D. Spear, Ph.D. Cambridge Systematics Anita Vandervalk, P.E. Cambridge Systematics April 6, 2016
2 What is a Transportation Asset Management Information System? A collection of hardware, software, data, and processes that support asset management business processes Used to:» Collect, process, store, and analyze information about assets» Develop sound maintenance and rehabilitation strategies» Schedule, track and manage work Included Information:» Technical - asset characteristics, condition, & performance» Financial - current asset value & resources needed to maintain» Planning - recommended or scheduled work on assets» Historical - work accomplished 2
3 Alaska s TAMIS Vision Goal A TAMIS that meets the needs of stakeholders by integrating data and establishing institutional methods to ensure that integration results in improved decision making for TAM Objective Transformation of data into information to fulfill the needs of TAM in Alaska. Business processes and tools will be recommended for transforming asset data into information needed for asset management Start Simple, Grow Smart, Show Continuous Improvement 3
4 TAMIS Desired Outcomes Create a system that all DOT&PF employees can easily use and for the State of Alaska to maintain Strengthen the ability of data programs to support core business functions of the agency Improve data quality throughout the organization Protect data as an asset of the agency Limit risks associated with loss of data and information 4
5 Functional Components of TAMIS Asset inventory - Maps, images, photographs, video, construction plans Treatment selection and life cycle management Resource allocation Asset condition, performance, utilization tracking Prediction of condition and performance Work planning and tracking support 5
6 Technical Components of TAMIS Database - Support for multiple database types - Links to geospatial features Application software - Upload, export, view, edit data, run analyses, perform queries, produce reports Interfaces - Enterprise Resource Planning (ERP) systems Field Data Collection System (mobile access) 6
7 7 TAMIS Framework
8 TAMIS - Project Objectives Document and analyze relevant research and requirements for TAMIS Conduct an assessment of existing business practices and information/data systems/tools related to TAMIS Develop a framework for TAMIS, including a common vision Conduct a gap analysis (as an overall risk management/ assessment program) Develop recommendations in the form of a work plan Develop a TAMIS Proof-of-Concept 8
9 Task 1 Task 2 Task 3 Task 4 Task 5 Task 6 Task 7 Project Management and Work Plan Document and Assess all Federal Requirements and Associated Research Research Other State Best Practices Stakeholder Coordination Evaluate Current Systems and Extent of Integration (Existing Condition) Develop ADOT&PF TAMIS Framework (Desired Condition) TAMIS Gap Analysis TAMIS Project Tasks Task 8 Research TAMIS System Model Alternatives Task 9 Task 10 Task 11 Research Recommendations for TAMIS Develop and Conduct a Project Communication Plan Data Business Plan for TAMIS 9 Task 12 TAMIS Proof-of-Concept Application
10 TAMIS Proof-of-Concept Objective: Demonstrate the potential functionality of TAMIS through development of a web-based application to support project prioritization and analysis across different program areas Application Examples 1. Support for project prioritization and development 2. Integration of high priority data for ad hoc reporting
11 11 TAMIS POC Demo
12 12
13 13
14 14
15 15
16 16
17 17
18 18
19 19
20 20
21 21
22 22
23 23
24 24
25 25
26 26
27 Lessons Learned TAMIS Data 1. The ability of TAMIS to answer specific questions is only as good as the data that it can access 2. Summary measures must be created for most asset databases 3. Storing asset data in a centralized data warehouse improves system performance and reliability 27
28 Lessons Learned TAMIS Viewer Application 1. On the fly computations can significantly impede system performance and responsiveness 2. Increased analysis flexibility adds more complexity to the user interface 3. Users require the ability to select and download subsets of TAMIS data for further analysis 28
29 Recommendations Implement TAMIS incrementally TAMIS System Architecture» 2 distinct but interdependent components TAMIS Data Warehouse TAMIS Data Viewer Create and maintain a TAMIS data warehouse Build or procure a web-based TAMIS viewer application 29
30 30 TAMIS System Architecture
31 Basic TAMIS Viewer Capabilities Dropdown list of pre-defined asset management questions Users can select subsets of asset records by Geography Simple structured query tool Users can summarize results via tables, charts, maps, and reports Users can export a selected subset of records in common data formats System administrators can add new asset databases, change dropdown menus, add new report templates, or add new questions without major software reprogramming 31
32 Questions? Anita Vandervalk Bruce Spear 32