Home' RTCA Documents for Review : DO-230H FRAC Contents 83
©2017 RTCA, Inc.
Comply with the requirements for an access control and proprietary alarm monitoring system as
specified in UL 294, Standard for Access Control Systems, and UL 1076, Proprietary Burglar-
Alarm Units and Systems, as applicable
Enable the system to meet all of the operational requirements defined by the PACS owner.
The system manufacturer should offer a documented Software Developer Kit (SDK) to facilitate
or to support secure connectivity and integration to third party databases using industry standard
data exchange protocols. SDK lifecycle management is a critical component to consider during
Data Base Connectivity compliant, ODBC (Open Data Base Connectivity), XML, Transactional,
SOAP/SAML, SPML, SQL, etc.
Available commercially “off-the-shelf” with little or no necessity to modify its codes; additional
functionality or modifications should be done in a modular, add-on fashion to ensure that the code
modules remain “off the shelf”; basic PACS software should require no modifications or
customizations to operate at an airport environment; and all modifications should be fully under
configuration management controls, documented, and provided to the PACS owner prior to
acceptance of the system Allow adjustments to databases, data tables, parameters, system
configurations, alarms, access door control, reports and other system data and information by non-
programmer staff through user-friendly screens and appropriate system maintenance software
Be fully supported by a vendor or developer throughout the useful lifespan of the system
Be warranted by the system provider to perform the functions for which it was purchased, for an
agreed upon period of time
Software training should be provided to both the PACS administrator and operational personnel
prior to the system acceptance test
Be easily operated by personnel with minimal technical training and provide a user-friendly
interface, such as map displays and graphical annunciation of alarms
The PACS should deny access for expired, terminated, lost, or deactivated access, or
administratively deleted ID badges. [Refer: Credentials Section 2)
The PACS should provide for the reporting of security events.
The PACS should provide an audit trail and event log recording, and system malfunction reporting.
The PACS should support compliance with regulatory requirements.
The PACS should be highly reliable, and easy to maintain/repair.
The PACS should be adaptable, expandable, and upgradeable.
The PACS should have high throughput and fast transaction speed to allow for access validation as
specified by the PACS owner (typical transaction speed is between 0.5 – 1 second.)
PACS Server Hardware
PACS architectures use the host server and associated client workstations as administrative tools, and are
commonly used to store the PACS application software and database. When required, the PACS server
database is often an integration point to other components
Performance, functionality and effectiveness of the entire system depend on the server. Therefore, care
must be taken in selecting host computers for any size PACS. A rule of thumb is to select the fastest
commercial processor speed and largest memory (RAM) size available at the time due to the rapid
developments in hardware and software technologies. A system should be selected that can function for a
minimum of 5 years without major upgrade or replacement.
Links Archive Navigation Previous Page Next Page