Home' RTCA Documents for Review : DO-230H FRAC Contents 126
© 2017, RTCA, Inc.
Figure 5-1: Typical PIDS Progression
A PIDS system can only achieve these functional capabilities by blending three principle elements - Staff
(organization), Process (programs such as ASP and SOPs), and Technology (hardware, software,
infrastructure, integration) – all working in concert.
These include, but are not limited to staff from airside, landside and waterside operations, aviation security,
public safety, facilities management, communications, and external agencies.
The implementation of a PIDS will require (possibly new) clear and common processes, practices, and
procedures that will drive effective and efficient operations through the control, management, and
dissemination of timely and accurate data and information. Policies supporting new and legacy PIDS-driven
SOPs must be drafted, vetted and adopted by PIDS stakeholders.
Finally, the technology of the PIDS should ensure effective and efficient security operations that will be
deployed and integrated to enhance security operations, communications, information access, knowledge
capture, system performance, and infrastructure and process automation. It should be built to allow for ease
in selection and upgrading of components. In addition, the system should allow for the incorporation of
legacy (existing) systems, be based on open architecture standards (no proprietary systems), and be scalable
to allow for future system expansion.
Risk and Needs Assessment
Since the terrorist attacks of September 11, 2001, the type and number of security technology products
available to airports have increased substantially. As a result, there is a tendency to start the process of
defining a PIDS by looking first at technology and working back from there. This approach often results in
a system that is substantially more expensive than planned, not risk appropriate, and/or ineffective. One of
the most important lessons learned is to clearly define the problem and capability needs before defining
system/security requirements that will eventually lead to an implemented solution. The reader should refer
to Section 1: Introduction for a discussion on threat, vulnerability, and risk assessment for airport security.
Through the process of risk assessment, airport operators can define their capability needs and determine if
a PIDS is appropriate.
The Code of Federal Regulations Title 49, § 1542.201(b) (l) (2) states in part that “[e]ach airport operator
who is required to establish a secured area within the airport must prevent and detect the unauthorized entry,
presence, and movement of individuals and ground vehicles into and within the secured area by doing the
following: 1) Establish and carry out measures for controlling entry to secured areas of the airport in
accordance with § 1542.207. 2) Provide for detection of, and response to, each unauthorized presence or
movement in, or attempted entry to, the secured area by an individual whose access is not authorized in
accordance with its security program.” Section 1542.201 also requires the airport operator to post signs at
secured access points and on the perimeter that warn against unauthorized access.
Links Archive Navigation Previous Page Next Page