Integrated Air Surveillance Concept of Operations - Joint Planning ...
Integrated Air Surveillance Concept of Operations - Joint Planning ...
Integrated Air Surveillance Concept of Operations - Joint Planning ...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
<strong>Integrated</strong> <strong>Air</strong> <strong>Surveillance</strong> <strong>Concept</strong> <strong>of</strong> <strong>Operations</strong><br />
integrity, confidentiality, and availability as needed within the domain, as described in NIST 800-<br />
53, Recommended Security Controls for Federal Information Systems and Organizations, and<br />
equivalent Federal guidance pertinent to the security level <strong>of</strong> the domain. 19 Controls used in<br />
different domains must be interoperable and harmonized at the appropriate points to allow the<br />
necessary sharing <strong>of</strong> information end-to-end. Access to information must be based on<br />
appropriate processes, such as attribute-based access controls (ABAC) and proper identification<br />
authentication, providing the proper information to the authorized user.<br />
4.2.8 Quality <strong>of</strong> Shared Information<br />
Requirements concerning the quality <strong>of</strong> data used for the integrated air surveillance mission will<br />
depend on purposes for which the data is being used. For example, data used in providing<br />
safety-<strong>of</strong>-life critical services, such as air traffic operations and weapons targeting, will have<br />
stringent requirements for availability and timeliness. The components <strong>of</strong> the agile informationsharing<br />
infrastructure must be designed, tested, and operated in order to provide the necessary<br />
performance and availability to meet these requirements where needed.<br />
The information sharing infrastructure will also provide support for higher-level requirements<br />
related to information quality, such as:<br />
Provenance - An information receiver may need to be able to determine and authenticate<br />
the original data source and chain <strong>of</strong> custody <strong>of</strong> subsequent processing <strong>of</strong> the data;<br />
Consistency - Algorithms for processing and analyzing data may need to meet standards<br />
for consistency among mission partners (e.g., tracker, coordinate system, adaptation) to<br />
allow for shared situational awareness and collaborative decision making;<br />
Accuracy - Systems may have requirements for the maximum allowable error between<br />
the data values and the actual value <strong>of</strong> the quantity being measured; and<br />
Data update rate - Systems may impose requirements on the maximum time interval<br />
between new information updates.<br />
4.2.9 Geo-Coordinated Data<br />
<strong>Surveillance</strong> data distributed for shared use at different operations centers will be positionreferenced<br />
using a common global coordinate system. Data may be converted to a local position<br />
reference system if operationally necessary.<br />
4.3 Sensor Network<br />
An information-sharing environment will deliver appropriately secured sensor data to facilities<br />
for subsequent automated processing. This network will have applicable class-<strong>of</strong>-service<br />
attributes, quality-<strong>of</strong>-service attributes, and communications protocols for delivery <strong>of</strong> near real<br />
19 National Institute <strong>of</strong> Standards and Technology (NIST) Special Publication 800-53, Recommended Security<br />
Controls for Federal Information Systems and Organizations, 2009.<br />
November 2011 34