The National Academies Press

Currently Skimming:

Pages 58-75

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 58... ... Freight Data Content Different stakeholders may have different interpretations of what should be the content of (i.e., what should be included in) a national freight data architecture. Read the entire page →
From page 59... ... By extension, a national data architecture that is to serve the needs of both public and private decisionmakers not just at the national level, but also at the state and local levels, has to be even more encompassing. Plenty of documents provide information about the limitations of current data collection programs, adding weight to the idea that the coverage and resolution of current freight data sources are not sufficient. Read the entire page →
From page 60... ... The amount of shipment information detail in EDI transaction sets varies according to the type of transaction set used. In general, although the transaction sets support the use of commodity codes such as NMFC or STCC, these codes are different from other codes such as SCTG or NAPCS. Read the entire page →
From page 61... ... In this case, the national freight data architecture would become the manner in which data elements are organized and integrated for all freight transportation-related applications or business processes at the national, state, regional, and local levels. For any of these implementation options, the data architecture would include the necessary set of tools that describe related functions or roles, components where those roles reside or apply, and data flows that connect roles and components. Read the entire page →
From page 62... ... In the context of a scalable national freight data architecture that might need to serve the needs of a variety of decisionmaking levels, this data architecture would need to include a number of component categories, such as the following: • Physical transportation components, • Cargo or freight, • Freight functions or roles, • Business processes, • Data sources, • Freight-related data, • Freight data models, • Freight data standards, and • User interface and supporting documentation. This list is preliminary and will need to be refined during the process of developing and implementing the data architecture. Read the entire page →
From page 63... ... Figure 10. National freight data architecture framework and components. Read the entire page →
From page 64... ... Figure 11. National freight data architecture components (focus on commodity flows at the national level) Read the entire page →
From page 65... ... Category components that pertain to commodity flows at the national level. N a t i o n a l F r e i g h t D a t a A r c h i t e c t u r e C a t e g o r y / C o m p o n e n t Commodity- Flow-Related N a t i o n a l F r e i g h t D a t a A r c h i t e c t u r e C a t e g o r y / C o m p o n e n t CommodityFlow-Related C a r g o o r F r e i g h t Travel time, speed, and dela y data Bill of ladi ng • Vehicle inve ntories Commodity • F r e i g h t D a t a M o d e l Invoice Busi ness pr ocess model • Item or product • Conc ep tual model • Purchase orde r • Data dictionary • Shipment • Logical model • Waybill • Metadata • P h y s i c a l T r a n s p o r t a t i o n Physical model • Contai ner • F r e i g h t D a t a S t a n d a r d Traffic control system • Commodity /p roduct classification: Transportation network • CPC • Vehicle HMIS • F r e i g h t F u n c t i o n o r R o l e HS • Analys t NAPC S • Carrier • NMFC • Fixed in frastructure manage r NST 2007 • Planne r • PLU • Policymaker • SCTG • Producer or manufacturer STCC • Regula to r • Industrial classification standards: Researcher ISIC Shipper or receiver • NAICS • Third-party logistics or broker • SI C • F r e i g h t - R e l a t e d D a t a SITC • Busi ness directories • Data exchange standards: Carrier used ANSI ASC X12 standard • Commodity i nvent ories FIPS PUB 161-2 • Products shi pped/received • OASIS UBL standards Distribution warehouse truck tr affi c • UN/EDIFACT standards Economic data National ITS standards Emissions data a nd esti mates FGDC-spons ored stan dards Employment by freight activit y Other standards: Freight volumes • ITDS SDS Fuel statistics METS Import and export statistics Vehicle classification standard s Licensed carrier data D a t a S o u r c e Manifests and way bills • Administrative records Mine out put data Census • Oversize/overweight routing data • Data standards • Pipeline volum es • Mandatory reporting required by laws • Railroad tonna ge data • Surveys • Safety data Other private-sector data • Shipment origins a nd de stinati ons • Other public-sector data • Shipment weigh t • U s e r i n t e r f a c e / s u p p o r t i n g d o c u m e n t a t i o n Traffic bottlenecks Outreach and traini ng material s • Traffic volumes • Web in formation clearinghous e • Transportation infrastructure inve nt ory Note: Compone nts no t marked as commodity -flow-related are not critical or may be c ons id ered optional. Read the entire page →
From page 66... ... Readers should note that the list of specifications is preliminary and might need refinement during the process of building the data architecture. The specifications described in this section are as follows: • Compare candidate data architecture implementation concepts; • Develop implementation plan for national freight data architecture components; • Develop lists of components to include in the national freight data architecture; • Develop and implement protocols for continuous stakeholder participation; • Conduct data gap analysis; • Conduct data disaggregation need analysis; • Assume a distributed approach (as opposed to a centralized approach) Read the entire page →
From page 67... ... In this case, the national freight data architecture would become the manner in which data elements are organized and integrated for a specific freight application or business process at the national level (e.g., commodity flows) Read the entire page →
From page 68... ... For each component, it will be necessary to identify the relevant data elements to include in the data architecture, using data elements already included in existing standards (e.g., EDI standards) as a reference. Read the entire page →
From page 69... ... Examples of data standards that pertain to freight information include the following: – Commodity and product classification standards CPC HMIS HS NAPCS NMFC NST 2007 PLU SCTG STCC – Industrial classification standards ISIC NAICS SIC SITC – Data exchange standards ANSI ASC X12 standards UN/EDIFACT standards OASIS UBL standards FIPS PUB 161-2 69 Read the entire page →
From page 70... ... As the previous chapter shows, which confirms the findings of several reports, freight data are scattered across many systems, jurisdictions, and business processes. Having an information clearinghouse that describes these freight data sources and how they relate to the national freight data architecture will be critical to assist in the process of understanding and developing the data architecture. Read the entire page →
From page 71... ... , could also be used for developing the national freight data architecture (140) Read the entire page →
From page 72... ... The national freight data architecture will also need to provide support to, or ensure compatibility with, applicable data standards. As previously mentioned, although the developer of the national freight data architecture will not be responsible for developing freight data standards, the data architecture developer should formulate recommendations for communication protocols with organizations responsible for developing relevant data standards and include "place holders" for data standard cross-references in the data architecture. Read the entire page →
From page 73... ... • Benefits from the implementation of the national freight data architecture might not materialize if the relationship between finer levels of data disaggregation and those 73 Read the entire page →
From page 74... ... It is important to ensure a minimum sample size to guarantee data reliability. • Not all data standards may be adequate to support key elements of the national freight data architecture. Read the entire page →
From page 75... ... • Take into consideration lessons learned from the implementation and maintenance of existing freight-related systems and architectures. Chapter 2 included a detailed review of a sample of those systems, which included topics such as purpose, content, institutional arrangements; challenges and issues faced; strategies and methods for dealing with data integration issues; and adaptability. Read the entire page →

From page 58...

... Freight Data Content Different stakeholders may have different interpretations of what should be the content of (i.e., what should be included in) a national freight data architecture.