Exhibit C - CDRL A007 Interface Control Document Example - NGT II - 12Jun2025.pdf

Controlled Unclassified Information (CUI)

CUI

INTERFACE CONTROL DOCUMENT (ICD)

Between

Product Lead Logistics Information Systems (PL LIS) Radio Frequency In-Transit Visibility (RF-ITV)

And

TBD

Next Generation Transponder (NGT-II) Vendor

Version 0.0

DATE TBD

Controlled by: PL LIS CUI Category: Controlled Technical Information (CTI)

Limited Distribution Control: TBD

POC: TBD

ICD - RF-ITV & TBD CUI DD MM YYYY

Summary of Changes

Version Number Date Major Changes Party Responsible for Change

Table of Contents

1.0 Scope

1.1 Interface Identification

1.1.1 VENDOR Description

1.1.2 RF-ITV System Description

2.0 System Communication Details

3.0 Detailed Interface Requirement

4.0 Approvals

Appendix A – Acronyms and Abbreviations Appendix B – References

List of Figures

Figure 1 – Next Generation Transponder II (NGT-II) Interface to RF-ITV Systems Figure 2 – Design view of the NGT-II message schema Figure 3 – Example Registration message (used for initial registration or for updating the model number or owner) Figure 4 – Example Position message Figure 5 – Example Position Message with additional optional elements (ProximityDevices) Figure 6 – Example Response Message (Success) Figure 7 – Example Response Message (Failure – DeviceID too short) Figure 8 – NGT Schema (NGT.xsd) Figure 9 – NGT Schema Types (NGTBase1.0.xsd)

1. PURPOSE

The purpose of this Interface Control Document (ICD) is to describe the external interface requirements and design between Product Lead Logistics Information Systems’ (PL LIS) Radio Frequency In-Transit Visibility (RF-ITV) Server and Vendor’s Next Generation Transponder II (NGT-II) System.

Additionally, the purpose of this ICD is to provide a signed agreement defining the terms, conditions, and responsibilities for the working relationship between the Product Lead Logistics Information Systems (PL LIS) and Vendor.

2. SCOPE

The RF-ITV and Vendor have one interface, NGT messages, as shown in Figure 1 below. The Vendor’s System shall provide a Simple Object Access Protocol (SOAP) payload in Extensible Markup Language (XML) format, as specified in section TBD, that the RF-ITV Server will pull.

This document provides the specification of requirements needed to support the exchange of XML data elements. It will define the interface between the RF-ITV system and NGT-II on NIPRNet as shown in Figure 1.

Figure 1 – Next Generation Transponder (NGT-II) Interface to RF-ITV Systems.

3. SYSTEM IDENTIFICATION

a. Vendor’s

b. RF-ITV System Description

The RF-ITV system uses transponders with Radio Frequency, Cellular, and Satellite technologies to provide In-Transit Visibility (ITV) information required by the DoD, North Atlantic Treaty Organization (NATO) Allies, and Coalition Partners of the United States. The RF-ITV system traces the identity, status, and location of cargo from origin (depot or vendor) to destination. Data from transponders are combined, processed, and delivered to numerous systems to provide global logistics support to the Joint Warfighter. Users can also access ITV data directly through the ITV Management Portal which includes web-based maps and tracking reports.

4. SECURITY REQUIREMENTS

The security requirements for this ICD are listed below:

a. The transfer of data shall comply with DoDI 8500.2 IA control requirements

b. RF-ITV server shall authenticate with account credentials.

c. Cybersecurity

Security readiness information can be found in the DoD Information Technology Portfolio Repository (DITPR), Enterprise Mission Assurance Support Service, or upon request. Both system owners agree to maintain the security posture of their systems in accordance with the Office of Management and Budget (OMB) Circular A-130 Appendix III, Federal Information Processing Standards (FIPS) 199 Standards for Security Categorization of Federal Information and Information Systems, and FIPS 200, Minimum Security Requirements for Federal Information and Information Systems. Both system owners agree to comply with the Department of Defense Directive (DoDD) 8500.01, Cybersecurity, and Department of Defense Instruction (DoDI) 8510.01, Risk Management Framework (RMF) for DoD Information Technology. Both systems shall be certified and accredited in accordance with DoDI 8510.01.

Additionally, both offices agree to comply with established DoD connection rules and approval processes. If a security incident occurs, audit trail documentation will be provided to all concerned parties upon request.

5. INTERFACE COMMUNICATION DETAILS

a. Message Type

The RF-ITV Server will establish a secure connection and retrieve NGT Data Message(s) from the Vendor’s End Point Server using a SOAP webservice.

The web service receives the message, validates it against the NGT schema, and saves it to a queue for processing. If successfully invoked, the call returns an HTTP status code of “HTTP/1.1 200 OK” and returns a response message. If not successfully invoked, the call returns a status code, such as “HTTP/1.1 401 Unauthorized” if, for example, the credentials are incorrect. If the HTTP status code is 200, the response code contained in the response message should be checked for “SUCCESS” (see Figure 6 below). This indicates that the submitted message is valid against the NGT schema and the message will be processed into the RF-ITV server. If the response code is “FAIL” then the message is invalid against the NGT schema and the message will NOT be processed into the RF-ITV server.

b. Data Elements

The following table outlines the minimum required NGT-II data elements and their descriptions.

Table 1 – Data Elements and Descriptions

Element Element Description ReceiptDateTime This is the timestamp when the Contractor's Server received the device's location report.

EventDateTime This is the timestamp when the device captured the GPS location.

DeviceID This is the unique 14-digit identifier assigned by the Government to identify the NGT-II device.

Manufacturer This is identifying the device’s manufacturer, which must match a value in the RF-ITV system's reference table to be recognized; otherwise, it will be displayed as "Unknown".

BatteryCapacity This is a numeric value (0-100) representing the device's remaining battery life as a percentage.

Latitude This is the Decimal Latitude; the latitude of a point on the Earth's surface, expressed as a decimal number, ranging from -90.000 (South Pole) to 0.000 (Equator) to 90.000 (North Pole).

Longitude This is the Decimal Longitude; the longitude of a point on the Earth's surface, expressed as a decimal number, ranging from -180.000 (West) to 0.000 (Prime Meridian) to

180.000 (East).

ModeOfTransmission This single character ('S' or 'C') indicates whether a device's position was transmitted via Satellite (S) or Cellular (C) network

c. Example Messages

The NGT message is embedded within the NGTTransmission element. An NGTTransmission includes a transmissionID and a transmissionDTG. The transmissionID should be a unique positive integer number. The transmissionDTG should be set to the current date and time (GMT) when the upload occurs. These elements assist troubleshooting by uniquely identifying a particular upload.

Figure 2 – Example Registration message

<soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:ngt="http://www.usarmyLIS.army.mil/XMLSchemas/NGT" xmlns:int="https://www.usarmylis.army.mil/XMLSchemas/Interface_Base.xsd">

<soapenv:Header/> <soapenv:Body>

<ngt:sendNGTData> <ngt:NGTTransmission> <int:transmissionID>99990</int:transmissionID> <int:transmissionDTG>2018-11-01T11:50:01</int:transmissionDTG>

<ngt:NGT> <ngt:NGTMessage>

<ngt:ReceiptDateTime>2018-11-01T11:31:05Z </ngt:ReceiptDateTime> <ngt:EventDateTime>2018-11-01T11:31:05Z</ngt:EventDateTime> <ngt:DeviceInfo>

<ngt:DeviceID>19829864005632</ngt:DeviceID> <ngt:Manufacturer>VENDOR</ngt:Manufacturer> <ngt:BatteryCapacity>74</ngt:BatteryCapacity> <ngt:RegistrationInfo>

<ngt:ModelNumber>GT-1100</ngt:ModelNumber> <ngt:Owner>DLA</ngt:Owner>

</ngt:RegistrationInfo> </ngt:DeviceInfo>

</ngt:NGTMessage> </ngt:NGT>

</ngt:NGTTransmission> </ngt:sendNGTData>

</soapenv:Body> </soapenv:Envelope> http://schemas.xmlsoap.org/soap/envelope/ http://www.usarmyamis.army.mil/XMLSchemas/NGT http://www.usarmyamis.army.mil/XMLSchemas/Interface_Base.xsd

Figure 3 – Example Position message <soapenv:Envelope xmlns:soapenv=http://schemas.xmlsoap.org/soap/envelope/ xmlns:ngt="http://www.usarmyLIS.army.mil/XMLSchemas/NGT" xmlns:int="https://www.usarmylis.army.mil/XMLSchemas/Interface_Base.xsd">

<soapenv:Header/> <soapenv:Body>

<ngt:sendNGTData> <ngt:NGTTransmission> <int:transmissionID>99991</int:transmissionID> <int:transmissionDTG>2018-11-06T08:44:01</int:transmissionDTG>

<ngt:NGT> <ngt:NGTMessage>

<ngt:ReceiptDateTime>2018-11-06T08:29:04Z </ngt:ReceiptDateTime> <ngt:EventDateTime>2018-11-06T08:29:04Z</ngt:EventDateTime> <ngt:DeviceInfo>

<ngt:DeviceID>19829864005632</ngt:DeviceID> <ngt:Manufacturer>VENDOR</ngt:Manufacturer> <ngt:BatteryCapacity>73</ngt:BatteryCapacity>

</ngt:DeviceInfo> <ngt:PositionInfo>

<ngt:Latitude>39.383</ngt:Latitude> <ngt:Longitude>-74.493</ngt:Longitude> <ngt:ModeOfTransmission>C</ngt:ModeOfTransmission>

</ngt:PositionInfo> </ngt:NGTMessage>

</ngt:NGT> </ngt:NGTTransmission>

</ngt:sendNGTData> </soapenv:Body>

</soapenv:Envelope>

Figure 4 – Example Position Message with additional optional elements (ProximityDevices) <soapenv:Envelope xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/" xmlns:ngt="http://www.usarmylis.army.mil/XMLSchemas/NGT" xmlns:int="https://www.usarmylis.army.mil/XMLSchemas/Interface_Base.xsd">

<soapenv:Header/> <soapenv:Body>

<ngt:sendNGTData> <ngt:NGTTransmission> <int:transmissionID>99992</int:transmissionID> <int:transmissionDTG>2018-11-06T14:41:01</int:transmissionDTG>

<ngt:NGT> <ngt:NGTMessage>

<ngt:ReceiptDateTime>2018-11-06T14:29:04Z</ngt:ReceiptDateTime> <ngt:EventDateTime>2018-11-06T14:29:04Z</ngt:EventDateTime> <ngt:DeviceInfo>

<ngt:DeviceID>86506702459616</ngt:DeviceID> <ngt:Manufacturer>SaviTechnologies</ngt:Manufacturer> <ngt:BatteryCapacity>72</ngt:BatteryCapacity>

</ngt:DeviceInfo> <ngt:PositionInfo>

<ngt:Latitude>39.383</ngt:Latitude> <ngt:Longitude>-74.493</ngt:Longitude> <ngt:ModeOfTransmission>C</ngt:ModeOfTransmission> <ngt:ProximityDevices>

<ngt:ProximityDeviceID>18710548976182</ngt:ProximityDeviceID> <ngt:ProximityDeviceID>18710546884413</ngt:ProximityDeviceID>

</ngt:ProximityDevices> </ngt:PositionInfo>

</ngt:NGTMessage> </ngt:NGT>

</ngt:NGTTransmission> </ngt:sendNGTData>

</soapenv:Body> </soapenv:Envelope> http://schemas.xmlsoap.org/soap/envelope/ https://armyeitaas.sharepoint-mil.us/teams/AIT-7/Shared%20Documents/General/NGT-II/NGT-II%20Pre%20ACQ%20Package/PWS/Attachments/%22http:/www.usarmyLIS.army.mil/XMLSchemas/NGT%22 https://armyeitaas.sharepoint-mil.us/teams/AIT-7/Shared%20Documents/General/NGT-II/NGT-II%20Pre%20ACQ%20Package/PWS/Attachments/%22https:/www.usarmylis.army.mil/XMLSchemas/Interface_Base.xsd%22 http://schemas.xmlsoap.org/soap/envelope/ http://www.usarmyamis.army.mil/XMLSchemas/Interface_Base.xsd

Figure 5 – Example Response Message (Success)

Figure 6 – Example Response Message (Failure – DeviceID too short)

Figure 7 – NGT Schema (NGT.xsd)

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Header/> <S:Body>

<ns2:sendNGTDataResponse xmlns="https://www.usarmylis.army.mil/XMLSchemas/Interface_Base.xsd" xmlns:ns2="http://www.usarmylis.army.mil/XMLSchemas/NGT">

<ns2:response> <responseCode>SUCCESS</responseCode> <message>SUCCESS</message>

</ns2:response> </ns2:sendNGTDataResponse>

</S:Body> </S:Envelope>

<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/"> <S:Header/> <S:Body>

<ns2:sendNGTDataResponse xmlns="https://www.usarmylis.army.mil/XMLSchemas/Interface_Base.xsd" xmlns:ns2="http://www.usarmylis.army.mil/XMLSchemas/NGT">

<ns2:response> <responseCode>FAIL</responseCode> <message>cvc-length-valid: Value '2244668800120' with length = '13' is not facet-valid with respect to length '14' for type 'TrackingDeviceIdentifierISO'.</message> </ns2:response>

</ns2:sendNGTDataResponse> </S:Body>

</S:Envelope>

<?xml version="1.0" encoding="UTF-8"?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.usarmylis.army.mil/XMLSchemas/NGT" targetNamespace="http://www.usarmylis.army.mil/XMLSchemas/NGT" elementFormDefault="qualified" attributeFormDefault="unqualified">

<xs:include schemaLocation="NGTBase1.0.xsd"/> <xs:element name="NGT" type="NGT"/> <xs:complexType name="NGT"> <xs:annotation> <xs:documentation>The collection of messages containing information about Next-

Generation Transponder (NGT) devices.</xs:documentation> </xs:annotation> <xs:sequence> <xs:element name="NGTMessage" maxOccurs="unbounded"> <xs:annotation> <xs:documentation>Information about a satellite tag and the location of and events that have occurred to an object to which a satellite tag has been affixed.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="ReceiptDateTime" type="DateTime"> <xs:annotation> <xs:documentation>The date and time that a message transmitted by a tracking device is received at the vendor's ground station.</xs:documentation> </xs:annotation>

</xs:element> <xs:element name="EventDateTime" type="DateTime" minOccurs="1"> <xs:annotation> http://schemas.xmlsoap.org/soap/envelope/ http://www.usarmyamis.army.mil/XMLSchemas/Interface_Base.xsd http://www.usarmyamis.army.mil/XMLSchemas/NGT http://schemas.xmlsoap.org/soap/envelope/ http://www.usarmyamis.army.mil/XMLSchemas/Interface_Base.xsd http://www.usarmyamis.army.mil/XMLSchemas/NGT http://www.w3.org/2001/XMLSchema

<xs:documentation> The date and time that an event (Position Report, Sensor Alert, etc.) occurs. Additional datetimes for individual sensor reports may be included in the same message under specific Sensor elements.</xs:documentation>

</xs:annotation> </xs:element> <xs:element name="DeviceInfo"> <xs:annotation> <xs:documentation>Information about a particular tracking device; its identifying information, battery status, etc.</xs:documentation> </xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="DeviceID" type="TrackingDeviceIdentifierISO"/> <xs:element name="Manufacturer" type="OrganizationName"> <xs:annotation> <xs:documentation> The organization that manufactured the tracking device.</xs:documentation> </xs:annotation>

</xs:element> <xs:element name="BatteryCapacity" type="BatteryCapacity" minOccurs="1"/> <xs:element name="RegistrationInfo" minOccurs="0"> <xs:annotation> <xs:documentation>Device model number and device owner (e.g. 21TSC) to register a new tracking device. This information only needs to be provided once in order to "register" the device with the RF-ITV system.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="ModelNumber" type="ManufacturerPartNumber" minOccurs="1"/> <xs:element name="Owner" type="OrganizationName" minOccurs="0"> <xs:annotation> <xs:documentation>The organization that owns the tracking device.</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:complexType>

</xs:element> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="PositionInfo" type="PositionData" minOccurs="0"/> <xs:element name="Sensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of sensors - devices that record values of environmental parameters of the tagged object. The tagged object may not be included in the message but can be inferred from externally available commissioning data.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="TemperatureSensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of the temperature sensor.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="TemperatureEventDateTime" type="DateTime"/> <xs:choice> <xs:element name="TemperatureActivatedStatus" type="SensorActivatedStatus" default="1"/> <xs:sequence> <xs:element name="Temperature" type="Temperature"/>

<xs:element name="TemperatureSensorAlarm" type="TemperatureSensorAlarm" default="0">

<xs:annotation> <xs:documentation>0=temperature is within limits 1=temperature is outside Limits</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:choice> </xs:sequence> </xs:complexType </xs:element> <xs:element name="HumiditySensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of the humidity sensor.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="HumidityEventDateTime" type="DateTime"/> <xs:choice> <xs:element name="HumidityActivatedStatus" type="SensorActivatedStatus" default="1"/> <xs:sequence> <xs:element name="Humidity type="Humidity”/> <xs:element name="HumiditySensorAlarm" type="HumiditySensorAlarm” default="0"> <xs:annotation> <xs:documentation>0=humidity is within limits 1=humidity is outside limits</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:choice> </xs:sequence> </xs:complexType </xs:element> <xs:element name="GForceSensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of the GForce sensor.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="GForceEventDateTime" type="DateTime"/> <xs:choice> <xs:element name="GForceActivatedStatus" type="SensorActivatedStatus default="1"/> <xs:sequence> <xs:element name="GForce"> <xs:complexType> <xs:simpleContent> <xs:restriction base="GForce"> <xs:attribute name="GForceUOM" type="GForceUOM" use="required"/> </xs:restriction> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="GForceSensorAlarm" type="GForceSensorAlarm" default="0"> <xs:annotation> <xs:documentation>0=GForce is within limits 1=GForce is outside limits</xs:documentation> </xs:annotation>

Page 8 of 14 <

/xs:element> </xs:sequence> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="LightSensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of the light sensor.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="LightEventDateTime" type="DateTime"/> <xs:choice> <xs:element name="LightActivatedStatus" type="SensorActivatedStatus" default="1"/> <xs:sequence> <xs:element name="Light"> <xs:complexType> <xs:simpleContent> <xs:restriction base="Light"> <xs:attribute name="LightUOM" type="LightUOM" use="required"/> </xs:restriction> </xs:simpleContent> </xs:complexType> </xs:element> <xs:element name="LightSensorAlarm" type="LightSensorAlarm" default="0"> <xs:annotation> <xs:documentation>0=the interior illuminance is within limits 1=the interior illuminance is outside limits</xs:documentation> </xs:annotation> </xs:element> </xs:sequence> </xs:choice> </xs:sequence> </xs:complexType </xs:element> <xs:element name="MotionSensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of the motion sensor.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence> <xs:element name="MotionEventDateTime" type="DateTime"/> <xs:choice> <xs:element name="MotionActivatedStatus" type="SensorActivatedStatus" default="1"/> <xs:element name="MotionSensorAlarm" type="MotionSensorAlarm" default="0"> <xs:annotation> <xs:documentation>0=the object is not in motion 1=the object is in motion</xs:documentation> </xs:annotation> </xs:element> </xs:choice> </xs:sequence> </xs:complexType> </xs:element> <xs:element name="DoorSensor" minOccurs="0"> <xs:annotation> <xs:documentation>Data describing the active status, value or alarm report date/time and the actual analog value and/or alarm state of the door sensor.</xs:documentation>

Figure 9 – NGT Schema Types (NGTBase1.0.xsd) <?xml version="1.0" encoding="UTF-8" ?> <xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" xmlns="http://www.usarmylis.army.mil/XMLSchemas/NGT" targetNamespace="http://www.usarmylis.army.mil/XMLSchemas/NGT" elementFormDefault="qualified" attributeFormDefault="unqualified" version="1.0">

<xs:simpleType name="BatteryCapacity"> <xs:annotation> <xs:documentation>The ratio of the actual power to the total potential power

(expressed as a percentage) of an electrical storage device.</xs:documentation> </xs:annotation> <xs:restriction base="xs:nonNegativeInteger">

<xs:minInclusive value="0" /> <xs:maxInclusive value="100" />

</xs:restriction> </xs:simpleType> <xs:complexType name="PositionData"> <xs:annotation> <xs:documentation>The angular measurements identifying the intersection of the surface of the World Geodetic System-84 *WGX-84) ellipsoid representing the earth's surface with a ray originating from the center of that ellipsoid.</xs:documentation>

</xs:annotation> <xs:sequence> <xs:element name="Latitude" type="Latitude"/> <xs:element name="Longitude" type="Longitude"/> <xs:element name="ModeOfTransmission" type="TransmissionMode" minOccurs="0"> <xs:annotation> <xs:documentation>Communication medium by which the device data was received.</xs:documentation> </xs:annotation>

</xs:element> <xs:element name="ProximityDevices" minOccurs="0"> <xs:annotation> <xs:documentation>Nearby tracking devices (usually RFID tags) "seen" by this device at this position. The position of the parent device is added to the position history of these nearby devices.</xs:documentation>

</xs:annotation> <xs:complexType> <xs:sequence minOccurs="1" maxOccurs="unbounded"> <xs:element name="ProximityDeviceID" type="TrackingDeviceIdentifier"/>

</xs:sequence> </xs:complexType>

</xs:element> </xs:sequence>

</xs:complexType> <xs:simpleType name="DateTime"> <xs:annotation> <xs:documentation>A measurement of time within a day fully specified in relation to the Gregorian calendar.</xs:documentation> </xs:annotation> <xs:restriction base="xs:dateTime">

<xs:pattern value=".+Z" /> </xs:restriction>

</xs:simpleType> <xs:simpleType name="DoorSensorAlarm">

<xs:annotation> <xs:documentation>An indication that the door is opened or closed.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:complexType name="GForce">

<xs:annotation> http://www.w3.org/2001/XMLSchema

<xs:documentation>The acceleration of an object relative to free fall.</xs:documentation>

</xs:annotation> <xs:simpleContent>

<xs:extension base="xs:decimal"> <xs:attribute name="GForceUOM" type="GForceUOM" use="required" />

</xs:extension> </xs:simpleContent> </xs:complexType> <xs:simpleType name="GForceSensorAlarm"> <xs:annotation> <xs:documentation>An indication that the force of gravity measured by a sensor does/does not meet a specified condition.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string"> <xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="GForceUOM"> <xs:annotation> <xs:documentation>Defined fundamental unit in which the acceleration of an object in free fall in a specified gravitational environment is expressed.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:string">

<xs:length value="3" /> <xs:enumeration value="GRF">

<xs:annotation> <xs:documentation>the average acceleration produced by gravity at the

Earth's surface (sea level)</xs:documentation> </xs:annotation>

</xs:enumeration> </xs:restriction>

</xs:simpleType> <xs:simpleType name="Humidity">

<xs:annotation> <xs:documentation>The ratio of water vapor content in the air to the amount the air can hold when saturated.</xs:documentation> </xs:annotation> <xs:restriction base="xs:nonNegativeInteger">

<xs:minInclusive value="0" /> <xs:maxInclusive value="100" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="HumiditySensorAlarm">

<xs:annotation> <xs:documentation>An indication that the humidity measured by a sensor does/does not meet a specified condition.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="Latitude">

<xs:annotation> <xs:documentation>The angular displacement relative to the equator of the

WGS-84 ellipsoid that represents the earth's surface. A positive number indicates angular displacement North of the equator; a negative number indicates displacement South of the equator.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:decimal">

<xs:maxInclusive value="90" /> <xs:minInclusive value="-90" />

<xs:fractionDigits value="11" /> </xs:restriction>

</xs:simpleType> <xs:complexType name="Light">

<xs:annotation> <xs:documentation>The measure of the intensity of incident light, weighted for the wavelength of the light.</xs:documentation> </xs:annotation> <xs:simpleContent>

<xs:extension base="xs:decimal"> <xs:attribute name="LightUOM" type="LightUOM" use="required" /> </xs:extension>

</xs:simpleContent> </xs:complexType> <xs:simpleType name="LightSensorAlarm"> <xs:annotation> <xs:documentation>An indication that the illuminance measured by a sensor does/does not meet a specified condition.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="LightUOM">

<xs:annotation> <xs:documentation>Defined fundamental unit in which the measure of the intensity of incident light, weighted for the wavelength of the light is expressed.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:string">

<xs:length value="3" /> <xs:enumeration value="FTC">

<xs:annotation> <xs:documentation>foot-candle</xs:documentation>

</xs:annotation> </xs:enumeration> <xs:enumeration value="LUX">

<xs:annotation> <xs:documentation>lux</xs:documentation>

</xs:annotation> </xs:enumeration>

</xs:restriction> </xs:simpleType> <xs:simpleType name="LiquidVolumeSensorAlarm">

<xs:annotation> <xs:documentation>An indication that the liquid volume has or has not changed.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="Longitude"> <xs:annotation> <xs:documentation>The angular displacement relative to the zero meridian of the WGS-84 ellipsoid that represents the earth's surface. A positive number indicates angular displacement East of the zero meridian; a negative number indicates displacements West of the zero meridian.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:decimal">

<xs:minInclusive value="-180" /> <xs:maxInclusive value="180" /> <xs:fractionDigits value="11" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="ManufacturerPartNumber">

<xs:annotation> <xs:documentation>The set of characters created by the manufacturer to uniquely identify a product/part.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:maxLength value="35" /> <xs:minLength value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="MotionSensorAlarm">

<xs:annotation> <xs:documentation>An indication as to whether or not an object has moved above set thresholds.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="OrganizationName">

<xs:annotation> <xs:documentation>The distinctive designation of a specific office, activity, or unit by which that entity is commonly known.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:maxLength value="35" /> <xs:minLength value="1" /> <xs:pattern value="[A-Za-z0-9]+"/>

</xs:restriction> </xs:simpleType> <xs:simpleType name="SensorActivatedStatus">

<xs:annotation> <xs:documentation>An indication that the sensor device is turned on (is capable of sensing) or turned off (is incapable of sensing).</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:complexType name="Temperature">

<xs:annotation> <xs:documentation>The quantitative value of the measure of heat in a substance.</xs:documentation> </xs:annotation> <xs:simpleContent>

<xs:extension base="xs:decimal"> <xs:attribute name="TemperatureUOM" type="TemperatureUOM" use="required" />

</xs:extension> </xs:simpleContent> </xs:complexType> <xs:simpleType name="TemperatureUOM"> <xs:annotation> <xs:documentation>Defined fundamental unit in which the measure of heat in a substance is expressed.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:minLength value="2" /> <xs:maxLength value="3" /> <xs:enumeration value="CE">

<xs:annotation> <xs:documentation>Degree Celsius</xs:documentation>

</xs:annotation> </xs:enumeration> <xs:enumeration value="FAH"> <xs:annotation> <xs:documentation>Degree Fahrenheit</xs:documentation>

</xs:annotation> </xs:enumeration>

</xs:restriction> </xs:simpleType> <xs:simpleType name="TemperatureSensorAlarm">

<xs:annotation> <xs:documentation>An indication that the temperature measured by a sensor does/does not meet a specified condition.</xs:documentation> </xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="0" /> <xs:enumeration value="1" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="TrackingDeviceIdentifier"> <xs:annotation> <xs:documentation>The identifier of a device capable of communicating the location and status of the object to which the device is attached using radio frequency transmission via satellite communications or a ground based interrogator.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:string">

<xs:minLength value="1" /> <xs:maxLength value="32" /> <xs:pattern value="[A-Z0-9]+"/>

</xs:restriction> </xs:simpleType> <xs:simpleType name="TrackingDeviceIdentifierISO">

<xs:annotation> <xs:documentation>The ISO-standard 14-digit identifier of a device capable of communicating the location and status of the object to which the device is attached.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:string">

<xs:length value="14" /> <xs:pattern value="[0-9]+" />

</xs:restriction> </xs:simpleType> <xs:simpleType name="TransmissionMode">

<xs:annotation> <xs:documentation>A single character representing the transmission channel via which the transponder data was received - e.g. (C)ellular, (S)atellite, (W)iFi, (O)ther.</xs:documentation>

</xs:annotation> <xs:restriction base="xs:string">

<xs:length value="1" /> <xs:enumeration value="C" /> <xs:enumeration value="S" />

</xs:restriction> </xs:simpleType>

</xs:schema>

6. INTERFACE CHANGES

a. Interface Changes

All interface change requirements shall be communicated in writing to the respective system interface managers not less than 180 days prior to required implementation. Any interface changes will require discussion for potential resource requirements (i.e. funding).

b. Network Changes

Any network changes that may affect the interface, such as extended system outage, a change in Domain Name Service (DNS), IP address, or data transfer timing, shall be communicated in writing 60 days in advance and will be subject to the approval of all affected parties.

7. SERVICE DESK

a. For RF-ITV assistance, please contact the Global Army ITV/TC-AIMS II Service Desk:

Email: usarmy.belvoir.peo-enterprise.mbx.lis-global-itv-tcaims-svsdesk@army.mil and/or U.S. Toll- Free or DSN: 1-800-877-7925

b. For Vendor assistance, please contact the Help Desk:

Email: TBD and/or Phone: NNN-NNN-NNNN

8. APPROVALS

The terms of this agreement will become effective on the date of signature by the designated product managers. This ISA will be reviewed and updated annually, or as required, and shall remain in effect unless terminated in writing by program management for either the Vendor or the RF-ITV systems.

ELISSA E. ZADROZNY

Product Lead Logistics Information Systems (PL LIS)