Exhibit_1_AFF_ICD_-_2016.pdf

PDF 608 KB Posted

Attached to
Automated Flight Following Hardware and Subscription Service
Solicitation number
AG-024B-S-16-0019
Issued by

About this file

Exhibit 1

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Property of the United States Government This Document Contains Sensitive But Unclassified

Information Do not remove this notice

Properly destroy when no longer needed Page 1 03/16/2016

Interface Control Document (ICD)

Between

Company A

And

Automated Flight Following (AFF)

Information

Do not remove this notice Properly destroy when no longer needed

Page 2 03/16/2016

1. Overview The purpose of this connection is to allow USFS Automated Flight Following

(AFF) to poll the COMPANY A Network for tracking data from owned and/or contracted assets so they can be displayed in near real time and used for health and safety checks as well as situational awareness.

2. System Identification Information

COMPANY A

www.company.a.com

3. System-specific Contact Information

(Communications Plan) AFF Communication plan triggers

i. Incident response

1. For www.aff.gov interface problem resolution an AFF ticket is opened with the IIA Helpdesk will be routed to an on-call AFF

SME for resolution and/or escalation as necessary.

ii. Administrative oversight changes

1. For administrative oversight changes, the AFF Project Manager or Operations Manager will route the issue to the appropriate person.

iii. Technical changes

1. For administrative oversight changes, the AFF Project Manager or Operations Manager will route the issue to the appropriate person.

Table 1 – AFF IT Management Staff

Title Name/Web Email Phone

Project Manager Bob Roth rroth@fs.fed.us +1 (406) 329-3235

Deputy Project Manager Heather Matusiak hmatusiak@fs.fed.us +1 (208) 387-5619

Operations Manager Neil Flagg nflagg@fs.fed.us +1 (530) 276-8086

Help Desk https://www.aff.gov/help.aspx affadmin@firenet.gov +1 (616) 323-1667 http://www.company.a.com/ http://www.aff.gov/ mailto:rroth@fs.fed.us hmatusiak@fs.fed.us mailto:nflagg@fs.fed.us https://www.aff.gov/help.aspx mailto:affadmin@firenet.gov

Information

Do not remove this notice Properly destroy when no longer needed

Page 3 03/16/2016

COMPANY A Network Communication plan triggers

i. Incident response

1. For www.company.a.com interface problem resolution an AFF ticket is opened with the Helpdesk and will be routed to an on-call AFF SME for resolution and/or escalation as necessary.

ii. Administrative oversight changes

1. For administrative oversight changes, the Project Manager or

Operations Manager will route the issue to the appropriate person.

iii. Technical changes

1. For administrative oversight changes, the Project Manager or

Operations Manager will route the issue to the appropriate person.

Table 2 – Company A IT Management Staff

Title Name/Web E-mail Phone

Project Manager Operations Manager

Help Desk

4. Data Transfer Overview The AFF system that initiates the session:

a. Data transfer type

i. Unidirectional

b. Data transfer protocol(s): HTTP POST via FIPS-140-2 compliant SSL encryption.

c. Data transfer frequency: 15 seconds.

For COMPANY A Network:

a. URL: www.company.a.com

b. Data transfer type

i. Unidirectional

d. Data transfer protocol(s): HTTP POST via FIPS-140-2 compliant SSL encryption.

e. Authentication: HTTP Basic Authentication

f. Login user ID: <User ID>

c. Data transfer frequency: As requested

Information

Do not remove this notice Properly destroy when no longer needed

Page 4 03/16/2016

5. Data Routing Data elements received by AFF (See Appendix 1)

1. Data center name

2. Data center date and timestamp UTC

3. Equipment serial number (ESN)

4. Position acquired date and timestamp UTC

5. Latitude and longitude in decimal degrees

6. Altitude in meters from mean sea level (MSL)

7. Speed in meters per second

8. Heading from track over ground from True North reported in degrees

9. GPS fix type (3D, 2D, or invalid)

10. Position dilution of precision (PDOP)

11. Horizontal dilution of precision (HDOP)

12. Source of the data (i.e. GPS)

(Future elements such as air tanker door and helicopter bucket events will be sent. No data deemed PII will be allowed on this data feed.)

Data element ownership following transfer: USDAFS

Data security categorization for systems involved in the data exchange (CIA: High, Mod, Low) Mod

Information

Do not remove this notice Properly destroy when no longer needed

Page 5 03/16/2016

Figure 1: — High Level Diagram of COMPANY A / AFF Connectivity Primary Connectivity — AFF and COMPANY A will use HTTPS a primary data transfer protocol.

Information

Do not remove this notice Properly destroy when no longer needed

Page 6 03/16/2016

Signatory Authority

This ICD is valid for one year following the latest date of either signature below.

At the end of this period the ICD will be reviewed, updated (if appropriate), and reauthorized. Either party may terminate this agreement upon receipt of 30 days advanced notice of intent to terminate or in the event of a security incident that necessitates an immediate response.

Company A Neil Flagg

Operations Manager

USFS, Automated Flight Following

Date:__________________________ Date:_________________________

Information

Do not remove this notice Properly destroy when no longer needed

Page 7 03/16/2016

Appendix 1— Automated Flight Following (AFF) JSON Format Specification

Version 1.0 The AFF JSON position document is an extension of the:

GeoJSON Format Specification Revision 1 16 June 2008.

All AFF JSON position documents should conform to GeoJSON standard and include the "dataInfo" object in each document and a "properties" object for each "type":

"Feature".

Data Dictionary for AFF Position Reports

Key Value Description type required type FeatureCollection string y dataInfo array y affVer string y provider Hardware and Data vendor (Must be one stop shopping) string y rptTime Time system created report dateTime

ISO 8601

y sysId Name of data center providing report n features Array of geojson objects array y type Feature string y properties geojson “properties” object object y rpt pos report type string y esn hardware unique identifier -may not be lookup value string y

Information

Do not remove this notice Properly destroy when no longer needed

Page 8 03/16/2016

Key Value Description type required unitId Nickname (e.g. registration number) string n cog Course over Ground, True North integer y spd Speed. Meters per second integer y src GPS/Glonas/Gallileo/loran System used to calculate position string y fix invalid/2D/3D Position fix type string y pdop* Position dilution of precision Double y hdop** Horizontal dilution of precision

Double n vdop Vertical dilution of precision Double n tdop Time dilution of precision Double n posTime Time position was calculated. dateTime

ISO 8601

y dataCtrTime Time position reports was inserted into vendor database.

dateTime

ISO 8601

y ctrId vendor server reporting position string n geometry object y type Point string y coordinates longitude,latitude,altitude geojson “coordinates” array

Decimal degrees.

Altitude in meters msl/hae array y

* Equipment (purchased before 2016) may continue to use hdop values if no pdop available.

** Equipment purchased in 2016 and after should use pdop.

Information

Do not remove this notice Properly destroy when no longer needed

Page 9 03/16/2016

Data Dictionary for data collected by ATU

The additional ATU event fields required to be sent with the properties key are labeled with an * (see example below table).

Up to four different objects (aircraft, tank, bucket, hardware) can be included inside an “events” object.

Multiple unique key value pairs may be included inside each of the events object keys.

Key Value Definition Type atu * object firmware *version state string esn *string Imbedded identifier from the device (e.g. IMEI) state string events * object aircraft object tank object bucket object hardware object power on Aircraft power on string power off Aircraft power off string oilPress true/false Device recording start of engine based on engine oil pressure transition boolean status takeoff Aircraft takeoff for fixed wing aircraft speed change to greater than 40 knots. Only one takeoff event per flight; first transition.

transition string

Information

Do not remove this notice Properly destroy when no longer needed

Page 10 03/16/2016

Key Value Definition Type status landing Aircraft landing for fixed wing aircraft change of speed from greater than 40 knots to less than or equal to 40 knots. Only one takeoff event per flight; first transition.

transition string status inflight Fixed wing aircraft in flight where speed is greater than 40 knots.

state string wow on Weight on wheels, aircraft is landed transition string wow off Weight off wheels, aircraft is in flight transition string gear up Landing gear transition change from down to up transition string gear down Landing gear transition change from gear up to gear down transition string fill start Onloading of fire suppressant transition string fill end Stop loading fire suppressant transition string pump start Fill start when using a snorkel pump transition string pump end Fill end when using a snorkel pump transition string drop start Sensor generated start of dropping fire suppressant transition string drop end Sensor generated end of dropping fire suppressant transition string suppressant retardant Suppressant type of retardant state string suppressant foam state string suppressant water state string suppressant gel state string suppressant ukn unknown state string gallons integer Volume of suppressant in U.S.

gallons state integer

Information

Do not remove this notice Properly destroy when no longer needed

Page 11 03/16/2016

Key Value Definition Type liters integer Volume of suppressant in metric liters state integer coverageLvl Integer Coverage level selected on drop controller state integer firmwareUpdate dateTime ISO 8601 for firmware version change transition dateTime calibration dateTime ISO 8601 transition dateTime

File details come from the government source that posted it. Updated .