The messaging between central control entities and Data Collection and Monitoring (DCM) devices is accomplished using the NTCIP Application Layer services to convey requests to access or modify values of DCM object definitions resident in the devices via an NTCIP network. An NTCIP message consists of a specific Application Layer service and a set of data objects.DCM devices usually record data over a period of time and transmit this data in the form of a file to a central entity. The DCM object definitions defined in Section 2 of this standard are used to configure the device. An NTCIP message using these object definitions should be compatible with the Simple Transportation Management Framework (STMF).The methodology defined in Section 3 may be used to transmit files using the AP-TFTP or AP-FTP profiles. Section 3 describes how to setup files in such a way that it allows any central system to ??parse?? and process the contents of the data files.The scope of this document is limited to the functionality related to DCMs used within a transportation environment. The limits and descriptions of the parameters are established to give the user maximum flexibility to operate devices that either exist at the time this document was authored or may exist in the future. This publication defines object definitions which are specific to DCM units and also defines standardized conformance groups (Section 4) that may be used for conformance statements.This standard includes four (4) Annexes. Annex A is normative and defines the organization of object definitions into conformance groups. Informative Annex B provides all SNMP tables defined in Section 2 as real tables to provide the user of this document with a better overview as well as with a guidance annex. Informative Annex C provides examples of configuring different types of studies as well as encoding tables using the SNMP/BER encoding. Informative Annex D provides a list of typical Communications Profiles for use with DCM equipment utilizing the object definitions and file transfer mechanism defined in this standard.In order to achieve the desired DCM functionality@ some of the object definitions described in other standards (see Normative References) such as TS 3.4 - Global Object Definitions may need to be utilized. Object definitions from other standards that are required to be used in conjunction with this standard are not re-defined in this standard@ but are referenced in conformance group definitions (Annex A) within this standard.