Home' RTCA Documents for Review : DO-230H FRAC Contents 217
©2017 RTCA, Inc.
Don’t rush system design and installation. Regardless of design specifications, there will always
be areas where changes are required as system integration progresses and site-specific anomalies
are encountered. Be prepared to handle such changes.
Focus on core functions. Some functions will be more important than others. Identify functional
priorities, and devise the design, installation and testing schedules to allocate the necessary
resources and management attention. Treat “integration” as an objective rather than as a concept to
guide the development of operationally-significant capabilities.
Develop plans for managing system design risks. Identify system functions and areas posing the
greatest technical and management risks, and have plans in place for mitigating such risks. Phase
the work so that the most risky tasks are addressed first; if the risks are judged to be high, pursue
parallel solutions until success for one approach is reasonably assured. Avoid putting high risk
tasks in critical portions of the schedule.
Avoid proprietary solutions – but have plans ready for dealing with them. Systems based on open
standards, which are available from multiple sources, are generally advantageous for an airport
because they enhance the airport’s flexibility in selecting system elements and which can be bought
competitively using generic specifications. When sole-source equipment and/or software must be
used, requiring standards-based output from the proprietary system may provide sufficient
information to ease the burden of third-party integration. The airport should also address
limitations imposed by a vendor which may not be competent, or may not be cooperative, or may
not be in business after the system is installed. Continuously assess non-proprietary alternatives,
especially when system upgrades are being considered.
Incentivize contractors to do the work properly. Contractors who “own” the work, and must support
the installed equipment and software for years after acceptance, are more likely to do the work
properly to avoid costly repairs and replacements during the warranty period. Extended warranties
help to keep this incentive active.
Deal with legacy system upgrades as new systems to avoid unexpected consequences. Upgrading
equipment, or changing how it is installed and/or operated (often software issues) can cause
additional unplanned work. The re-routing of a fenced perimeter segment, for example, can change
video camera lines-of-sight and require additional cameras and lighting for complete coverage.
Adding new elements can have even greater consequence, as when radar sensors for perimeter
intrusion detection are replaced by fence sensors – which may also require new fencing, new
perimeter lighting (and perhaps new mains power lines and network cabling) – all of which must
be integrated. Examine all of the inter-relationships and interfaces across operational scenarios
before agreeing to what, on paper, seems to be a simple upgrade.
Test everything, at multiple times if possible. Testing hardware and software before they leave a
factory is an effective way to avoid problems in the field. It also provides an opportunity for training
airport personnel who will take responsibility for operating the system. Do operational proof testing
with actual operational staff.
Provide for operator feedback during the initial phases of operation. Despite the best efforts of
system designers, there will always be opportunities for “tuning” installed systems after airport
personnel spend time operating the systems. Means to feed back to the system designer/installer
actual operational experience, and take corrective measures from this experience, should be
provided in the management plan.
Ensure adequate systems documentation. The integrated system will require documentation that
will likely be more than that which was provided with the original systems. Equipment
compatibility and software protocols should be properly documented for maintenance and
operation going forward.
Links Archive Navigation Previous Page Next Page