Guidance for Developing a Freight Transportation Data Architecture (2010) / Chapter Skim
Currently Skimming:
Pages 17-48
The Chapter Skim interface presents what we've algorithmically identified as the most significant single chunk of text within every page in the chapter.
Select key terms on the right to highlight them within pages of the chapter.
From page 17... ...
As the realworld examples in Chapter 1 showed, supporting such a wide spectrum of decisionmaking needs requires using a wide range of data sources. The literature review in this chapter includes a general description of available data sources as well as a detailed discussion of several systems and architectures that were of particular interest because of the processes that led to their development, which could be used as lessons learned while developing a national freight data architecture.
|
From page 18... ...
x x x x x Economic Census U.S. Census Bureau x x x x x x Energy Information Administration Data Services Energy Information Administration x x x x x Fatality Analysis Reporting System FARS NHTSA x x Freight Analysis Framework FAF2 FHWA x x x x x x Hazardous Materials Information System HMIS PHMSA x x x x x x x Highway Performance Monitoring System HPMS FHWA x x x Motor Carrier Financial and Operating Data FMCSA x x x Motor Carrier Management Information System MCMIS FMCSA x x x Motor Carrier Safety Status Measurement System SafeStat FMCSA x x National Automotive Sampling System NASS NHTSA x x National Hazardous Material Route Registry NHMRR FMCSA x x National Pipeline Mapping System NPMS PHMSA x x x National Transportation Atlas Database NTAD BTS x x x x x x Navigation Data Center Waterborne Commerce Data U.S.
|
From page 19... ...
System and Architecture Review The following systems and architectures in Table 1 were of particular interest because of the processes that led to their development: • Automated Commercial Environment/International Trade Data System, • Carload Waybill Sample, • Commodity Flow Survey, • Electronic Data Interchange Standards, • Freight Analysis Framework, • Highway Performance Monitoring System, • National Income and Product Accounts, • National ITS Architecture, • National Spatial Data Infrastructure, and • National Transportation Atlas Database. Lessons learned from the development and implementation of these systems and architectures can provide invaluable information for, and help to minimize the costs of, the development
|
From page 20... ...
The analysis covered several topics, including the following: • Purpose and intended benefits; • Content; • Institutional arrangements used for developing and maintaining the system or architecture; • Challenges and issues faced in creating and maintaining the architecture or system; • Strategies and methods for dealing with data integration issues, such as data quality, timeliness, and proprietary and privacy concerns; • Adaptability to serve evolving purposes and data sources; and • Assessment of how well the system or architecture works in the form of lessons learned. In reality, institutional arrangements, issues faced during development, implemented strategies, and adaptability are interrelated.
|
From page 21... ...
. From the 10,000 data elements that PGAs identified, ACE/ITDS staff reduced the number of required data elements by 96 percent to a standard dataset of 400 data elements.
|
From page 22... ...
The sample is one of the main sources of information for the development of trip generation estimates and is often used by regulators, planners, nongovernmental agencies, and other stakeholders. The sampling rate for carload waybill samples is a function of the number of carloads per waybill and the method the railroad uses to submit the documentation (i.e., manually or using a computerized system)
|
From page 23... ...
Lessons Learned Lessons learned in connection with the development, evolution, and maintenance of the Carload Waybill Sample follow: • Provide clear, uniform guidance. The regulations clearly identify which freight railroads are required to submit a Carload Waybill Sample.
|
From page 24... ...
For example, CFS data are used to build truck O-D trip tables, for traffic simulation analyses, to benchmark the Carload Waybill Sample (37) , and as input to the Freight Analysis Framework.
|
From page 25... ...
in a wide range of areas such as materials, warehousing, product services, and transportation. Many EDI transaction sets are related to freight and cover topics such as rate proposals, freight details and invoices, trailer manifests, shipment information, shipment status inquiries and status messages, and tariff information.
|
From page 26... ...
To address some of the limitations associated with traditional EDI transaction sets (including proprietary software implementations, cryptic format, and implementation com26 No. Description 104 Air Shipment Information 109 Vessel Content Details 110 Air Freight Details and Invoice 210 Motor Carrier Freight Details and Invoice 211 Motor Carrier Bill of Lading 214 Transportation Carrier Shipment Status Message 215 Motor Carrier Pick-up Manifest 216 Motor Carrier Shipment Pick-up Notification 217 Motor Carrier Loading and Route Guide 218 Motor Carrier Tariff Information 309 Customs Manifest 310 Freight Receipt and Invoice (Ocean)
|
From page 27... ...
For motor carrier shipments, ANSI ASC X12 Transaction Set 211 describes commodity items using national motor freight classification (NMFC) codes.
|
From page 28... ...
Many EDI transactions sets are related to freight and cover topics such as rate proposals, freight details and invoices, trailer manifests, shipment information, shipment status inquiries and status messages, and tariff information. Traditional EDI implementations use direct modem-tomodem connections.
|
From page 29... ...
However, FAF1's shortcomings, including its reliance on proprietary data and little use of CFS data, resulted in inconsistencies between FAF1 and CFS and the inability to publish estimates of commodity flows for areas smaller than states (64)
|
From page 30... ...
The process included matching route assignments to HPMS truck volume estimates, which revealed quality problems with HPMS data. • Temporal resolution.
|
From page 31... ...
highways, which Congress uses to establish authorization and appropriation legislation that affects the scope and size of the federal-aid highway program; • Assessing changes in highway system performance and for apportioning federal-aid highway funds to individual states; • Assembling freight corridors and determining freight movement performance; • Special policy and planning studies; • Travel and congestion monitoring, public road usage, and fatality rate calculations; • Investment needs and planning at the state level; and • Air quality conformance and planning. Various agencies use HPMS data, including federal, state, and local agencies, as well as research agencies.
|
From page 32... ...
Operations 95 Peak Capacity 38-46 Highway Surveillance Systems 96 Volume/Service Flow Ratio 47 Sample Identifier 97 Future AADT 48 Donut Area Sample Expansion Factor 98 Year of Future AADT Table 4. HPMS data items (67)
|
From page 33... ...
Data collection costs influence the number of collected data items, transportation system scope, and data quality requirements. FHWA is responsible for maintaining HPMS data provided by state DOTs.
|
From page 34... ...
; – Evaluate data aggregation levels; – Evaluate if the data should be collected for all sections or for a sample of sections; – Evaluate whether the data collected met HPMS mission and objectives and constituted an improvement over the current system, including an evaluation of implementation costs versus savings, potential impacts when data elements are analyzed as a group, and process and timing requirements; and – Gather public input and obtain final FHWA internal review and adoption. In addition to identifying core data items and processes to reduce the data collection burden on state DOTs, the 1999 reassessment identified a number of needed system enhancements, including the following: – Improve the quality of HPMS data; – Increase the use of new technology to collect HPMS data; – Improve training to states and other data collection agencies; – Develop better integration, linkages, and coordination among state, regional, and local databases; – Allow access to raw or disaggregated HPMS data for local use; – Design HPMS to be statistically significant at the local level; and – Include additional pavement condition data.
|
From page 35... ...
shifted to a current-cost basis 1985 Quality-adjusted price indexes for computers and peripheral equipment introduced 1991 National production measure changed from GNP to GDP 1993 NIPA improvements started following the System of National Accounts 1993 framework 1996 Methods for estimating changes in real GDP and for CFC calculation improved Government expenditures for equipment and structures recognized as fixed investment 1999 Several key definitions improved New method introduced for calculating real value of non-priced bank services Consumer price indexes revised back to 1978 2003 More advanced measures of insurance services and banking services adopted New treatment of government activity adopted National income definition expanded to follow international guidelines New tables including two new summary accounts added 2009 New treatments of disasters and insurance services provided by government enterprises introduced Transactions between the federal government and U.S. territories and commonwealths reclassified New classification system for personal consumption expenditures added 2002 benchmark I-O accounts incorporated Statistical measure for estimating persona proprietors' income improved l consumption expenditures, wages and salaries, and Table 5.
|
From page 36... ...
, traffic signal systems, and tolling operations. The National ITS Architecture includes user services, a logical architecture, a physical architecture, and standards, as summarized below.
|
From page 37... ...
The logical architecture defines processes, data flows among processes, terminators (i.e., entry and exit points such as sensors, computers, and human operators) , and data stores required to satisfy the functional requirements of the 33 user services (88)
|
From page 38... ...
Although the National ITS Architecture is generic, it can be tailored to meet unique local or regional transportation needs. In the architecture, functions, subsystems, and data flows have precise definitions and associated data elements, which facilitates data exchange within and among jurisdictions at several levels.
|
From page 39... ...
Developing a national IVHS architecture would ensure compatibility among different IVHS hardware and software technologies and accelerate the implementation of IVHS by reducing the risks to privateand public-sector stakeholders. Without the assurance of compatibility, stakeholders would be reluctant to invest in IVHS infrastructure.
|
From page 40... ...
The first phase involved four contractors (Hughes Aircraft, Loral, Rockwell International, and Westinghouse) to develop candidate IVHS architectures (97)
|
From page 41... ...
As with other user services, which represent what a system would do from the perspective of the user, ADUS provides tools and describes processes related to ITS data archiving. Although all ITS deployments use and/or produce data, ADUS is not mandatory.
|
From page 42... ...
National Spatial Data Infrastructure Purpose and Content NSDI is a dissemination effort to "acquire, process, store, distribute, and improve utilization of geospatial data throughout all levels of government, the private and non-profit sectors, and academia" (106)
|
From page 43... ...
Interaction with other agencies also takes place through a variety of initiatives, including the following: – Fifty State Initiative, which focuses on assisting states in developing strategic and business plans to facilitate programs, policies, and technologies to support NSDI; – NSDI Cooperative Agreements Program, which focuses on assisting the geospatial data community through funding and other resources in implementing NSDI components; and – Geospatial Line of Business (LoB) , which is a presidential initiative that focuses on fostering collaboration, reducing redundancies, and improving accountability and transparency across the federal government.
|
From page 44... ...
Reasons mentioned include the following: • Lack of up-to-date strategic plans with specific measures for identifying and reducing redundancies, • Many federal geospatial datasets not being compliant with FGDC standards or published outside NSDI clearinghouse procedures, and • Lack of effectiveness in OMB's oversight of federal geospatial activities. A recent National States Geographic Information Council report concluded that there was a need to refocus national efforts to complete the development of NSDI and to devise appropriate data maintenance methods (118)
|
From page 45... ...
Census Bureau Fixed-Guideway Transit Facilities Polyline FTA Freight Analysis Framework Polyline FHWA Hazardous Material Routes Polyline FMCSA Highway Performance Monitoring System Polyline FHWA Hydrographic Features Polygon BTS Hydrographic Features Polyline BTS Intermodal Terminal Facilities Point BTS Metropolitan Planning Organizations Polygon BTS and FHWA National Bridge Inventory Point FHWA National Highway Planning Network Point FHWA National Highway Planning Network Polyline FHWA National Park System Boundary Dataset Polygon National Park Service National Populated Places Point U.S. Census Bureau Navigable Waterway Network Polyline USACE Non Attainment Areas Polygon EPA Ports Point USACE Railroad Grade Crossings Point FRA Railway Network Point FRA Railway Network Polyline FRA U.S.
|
From page 46... ...
includes a detailed description of each data source, system, or architecture. Although not comprehensive, the review provides a sample of the typical data sources, systems, and architectures that could be included in a national freight data architecture, as well as any potential implementations that could derive from that data architecture.
|
From page 47... ...
The sample of systems and architectures selected for the detailed historical analysis covered a wide spectrum of topics related to freight transportation and included the following: • ACE/ITDS, • Carload Waybill Sample, • CFS, • EDI standards, • FAF, • HPMS, • NIPAs, • National ITS Architecture, • NSDI, and • NTAD. For this sample of systems and architectures, the analysis covered several topics, including the following: • Purpose and intended benefits; • Content; • Institutional arrangements used for developing and maintaining the system or architecture; • Challenges and issues faced in creating and maintaining the architecture or system; • Strategies and methods for dealing with data integration issues, such as data quality, timeliness, and proprietary and privacy concerns; • Adaptability to serve evolving purposes and data sources; and • Assessment of how well the system or architecture works in the form of lessons learned.
|
From page 48... ...
Census Bureau for the use of survey instruments (CFS) ; • Emphasize data access, quality, reliability, confidentiality, and integrity (Carload Waybill Sample, FAF, NIPAs)
|
Key Terms
This material may be derived from roughly machine-read images, and so is provided only to facilitate research.
More
information on Chapter Skim is available.