Skip to content

Concept Design for an Online Information Source for Major Surface Transportation Projects: A Discussion Paper

June 2017
Table of Contents

« PreviousNext »

4 Online Information Platform

4.1 Introduction

The information source envisioned in this discussion paper is intended to provide the end user with hard data by project phase. At the same time, it will provide other "soft" information on the prevailing context in which projects are conceived and executed, e.g., specific language of the enabling legislation, the policy framework and its evolution during a project, institutional experience and capacity to administer projects of a similar type. It will take a concerted effort to design an information source capable of answering the core research questions identified in Chapter 1 of this report. Assembling the information source would require the collection, verification, analysis and synthesis of large amounts of data on major transportation projects. This section of the discussion paper discusses the optimal platform to disseminate the information.

The organization of data in the information source is expected to be project-centric with the potential to update information (e.g., performance data) throughout the project lifecycle. It is expected that the life cycle of projects included in the information source could extend over several decades. The types of data that are expected to be included in the information source would be collated from multiple sources and points of origin as they become available over time. Incentives may be needed to encourage project sponsors to share performance information. The information could include data tables with alphanumeric information, environmental documents, project documentation, maps, and images. Users should derive significant value from the ongoing longitudinal performance information that is added to the information source over time.

There are many models for handling project information of this type. A generic or customized document management system could be used, as could a relational database or some combination of these, e.g., a document-oriented database. The project-related data that the information source is expected to include would likely lend itself to being organized in a set of well-defined data tables (also referred to as structured data). To the extent that such information is available from project sponsors and other sources, additional project artifacts such as images, video, audio, documents, and emails (also referred to as unstructured data) could be included in the information source. Many different commercial vendors offer a variety of solutions for document management, document-oriented databases and relational databases. However, given that this tool would provide information that supports analysis and comparison within project phases and across projects, a relational database structure appears to be a pragmatic and prudent approach. This type of database would need to be able to support project-specific unstructured data as well as structured data. In addition, in order to deliver information in an efficient and user-friendly manner, the information source would require a custom front-end web application to upload and retrieve project information.

4.2 High-Level System Specifications

While the specific solution and attendant details of the relational database and platform to access the information source is beyond the scope of this paper, some high-level system specifications are provided here to guide the development of such a system. This online information platform would benefit from using non-proprietary software, databases and coding practices that apply current industry-standard versions of the software platform/language, which are not more than one major revision from the latest version. It would be preferable to avoid third party add-on libraries requiring royalties/fees. The goal should be to lower the cost of maintaining the software and database system over time. However, exceptions may need to be made when developing the software needed to implement the final requirements of the information source.

The system should use responsive design for multi-device display, and be compliant with Section 508 of the Rehabilitation Act of 1973, as amended (29 U.S.C. § 794 (d)). It should support the usability/accessibility design guidelines of the Web Accessibility Initiative (WAI) to provide information to users in an intuitive manner, including those accessing online content using assistive technologies. It is anticipated that most of the data included in the information source would be alphanumeric and, therefore, accessible to visually impaired users using assistive technologies. If the information source were hosted on a federal server, any source documents residing in the information source itself - including portable document format (PDF) files would need to be Section 508 compliant. This would require converting all PDF files to hyper text markup language (HTML) or modifying their format to create web-accessible PDF documents. Either option would likely be extremely resource intensive. The need to convert such documents would be avoided if they were to reside on non-federal servers which are accessed from the information source via hyperlink. A drawback is that links would likely need to be updated frequently as the non-federal sources update their sites. There is also some likelihood that valuable time-based historical information could be lost when these non-federal sites take down "outdated" information that is no longer needed by their stakeholders.

As discussed above, the system architecture could be based on a hybrid relational database and file management platform that enables access to the database from a front-end user interface that facilitates data queries, results display, and data export. The information source should provide users with the ability to export information in convenient and commonly used formats including Excel, comma separated values (CSV) and PDF formats, at a minimum. The platform must be user-friendly and intuitive. The integrated back-end platform and front-end user interface should support the following features/functions:

  • Search Filters: Filters for generating data subsets. The filters could be organized to provide data subsets for user analysis to help address the "core questions" discussed in Chapter 1.
  • Search Results Display: A user-friendly display table could provide a synopsis of records matching user-selected criteria, to include the record identifier, which serves as a link to a detailed record display.
  • Sortable Columns: Results display table column headings could be toggled to display data in ascending and descending order.
  • Print-Friendly Pages: The results display table should support a print-friendly page display.
  • Reporting: Individual record details should be printable and templated PDF or MS Excel reports.
  • Data Upload Facility: The information platform should support population of the online information source, which would include both manual data entry for individual records, and automated data entry via a secure, data import utility using pre-defined customized data templates.
  • Data Export: The full data set and/or data subsets should be exportable in common software formats such as Microsoft Excel and CSV formats for additional analytics via other programs.
  • Online Help Menu | Tool Tips: User aids should support use of the online system and provide explanations and/or clarifications, as needed, via tool tips. YouTube instructional videos, webinar trainings, user management, and comparison functions could also prove helpful.

4.3 Data Management

The plan for populating the information source and establishing its governing structure will have a strong influence on the design of the final tool. For instance, if multiple partners handle data population, then role-based access and security will need to be built into the tool (e.g., administrator, super user, contributor, etc.). The complexity of the data management process will dictate the complexity of the underlying workflows and approvals processes. These decisions will need to be put into place prior to the actual population of the information source. Regardless of which method is used, the online system would benefit from a secure administration function that supports both system and data management. System management activities would include functionality to generate additional search filters dynamically and record mapping criteria. Data management would support record add/edit/delete functions and mapping to search criteria.

« PreviousNext »

back to top