ASTM_E_2259_-_03a_2011.pdf

Designation:E225903a(Reapproved 2011)Standard Guide forArchiving and Retrieving Intelligent Transportation Systems-Generated Data1This standard is issued under the fixed designation E2259;the number immediately following the designation indicates the year oforiginal adoption or,in the case of revision,the year of last revision.A number in parentheses indicates the year of last reapproval.Asuperscript epsilon()indicates an editorial change since the last revision or reapproval.INTRODUCTIONThis guide has been developed within the framework of developing standards of ASTMInternational and thus the format,structure,as well as the review,balloting,and approval processesconform to those specified by ASTM International.These processes may differ in their particularsfrom those used by other standards development organizations associated with developing ITSstandards.However,their general intent is the samethat of having a representative group of interestedand knowledgeable stakeholders develop standards that can be used by a wide variety of public andprivate organizations in developingArchived Data Management Systems(ADMS),which can be usedto facilitate data sharing and interoperability among systems.This guide has been prepared with various ITS data stakeholder groups in mind,that is,data users,ADMS policy makers,ADMS developers,andADMS administrators.To data users andADMS policymakers,it can provide a general understanding about technical approaches to archiving and retrievingITS-generated data.For the ADMS developer group,which includes data application softwaredevelopers,this guide can be a bench-marking reference against which existing ADMS could befurther refined or improved with broader perspective.Further,it is also intended to bring greaterawareness and consistency in the use and understanding of concepts and use of terminology by theADMS developers.Finally,the ADMS administrators,whose main function includes collecting,archiving,managing,and distributing ITS data,can find practical guidance and approaches from thisguide for effectively operating their ADMS.It should be noted that there is a subtle distinction in the use of the acronym ADMS throughout thisguide.When it is being used in the context of the National ITS Architecture the S stands for asubsystem of the National ITS Architecture.When the acronym ADMS is being used in the contextof an Archived Data Management System in general,or a particular deployment of one,then the Sstands for System.It is also noted that Appendix X1 to this guide presents relationships of the guideto several other activities and standards.This guide follows the intent of all guides prepared within the ASTM International framework.Inparticular,it suggests approaches,offers an organized collection of information,or proposes series ofoptions or instructions that give direction without recommending a specific course of action.Guidesare also intended to increase awareness of potential users of the standards of the available techniquesin the subject area,while at the same time providing information from which subsequent practices canbe derived.This document,however,cannot replace a broad-based education or pertinent experienceand should be used in conjunction with professional judgment.Not all aspects of this guide may beapplicable in all circumstances.This guide is not intended to represent or replace the standard of careby which one judges the adequacy of a given professional service,nor should this document be appliedwithout consideration of the many unique aspects of a project.The word Standard in the title of thisdocument means only that the document has been approved through the ASTM Internationalconsensus process.Copyright ASTM International,100 Barr Harbor Drive,PO Box C700,West Conshohocken,PA 19428-2959.United States1 1.Scope1.1 This guide covers desired approaches to be consideredand followed in planning,developing,and operating specificADMS for the archiving and retrieval of Intelligent Transpor-tation Systems-generated data.The scope of this guide antici-pates incremental or modular implementation of an ADMS,which over time and with a series of investment of resourceswill approach or exceed desired practice.However,it isrecognized that programmatic constraints of time and budgetresources do not always allow practitioners to follow a moredesirable course of action and that during interim periods theability to implement a particular fully functioning system maybe less than desired.1.2 The desired approaches described in this guide arefoundational and are not intended to be all-inclusive.Users ofthis guide are allowed,and indeed encouraged,to exceed thedesired practices in one or more of several ways.An exampleof one way is that to address and satisfy the particular needsand requirements of some of the intended users and stakehold-ers for a particular implementation may necessitate exceedingthe desired practice.Another example is that some implemen-tations may want to fos