Home' RTCA Documents for Review : DO-230H FRAC Contents 230
© 2017, RTCA, Inc.
The software interfaces of such components are commonly published allowing third parties to create
integrations. They are variously known as Application Programmer’s Interface (API) or Software
Development Kit (SDK), gateways or protocols.
Look for modern architectures: In general, modern architectures that use communications
technologies like xml and web services will be easier to integrate than systems built on older
Check Vendors’ Application Programming Interfaces (APIs): APIs are the “gateway” for data to
pass in and out of systems, and the availability of an API can mean the difference between a
relatively simple integration and costly, complex, custom integration. Vendors’ approaches to APIs
vary widely; some openly publish their APIs, others charge significant sums, and some do not offer
them at all. It is important to determine, before making a commitment, if the vendor has APIs
already developed for the functions of other systems that are to be integrated to avoid the time, and
cost, of having to develop them.
Be aware that some systems have unique integration restrictions: Many organizations attempt to
integrate systems together, only to discover that a system’s vendor does not offer an API. Usually,
the only way to do this with the vendor’s approval is to pay the vendor to develop the interface,
which is usually costly. It is possible to bypass the application and integrate directly with the
underlying database without the vendor’s approval, but this can void warranties.
The consequences of attempting to integrate to a system with no available API sometimes make it more
cost effective to replace the system with one that is more amenable to integration.
Allow familiarization time for the airport staff
Don’t rush system design and installation.
Focus on core functions
Develop plans for managing system design risks.
Avoid proprietary solutions – but have plans ready for dealing with them.
Incentivize contractors to do the work properly.
Deal with legacy system upgrades as new systems to avoid unexpected consequences.
Test everything, at multiple times if possible.
Provide for operator feedback during the initial phases of operation.
Ensure adequate systems documentation.
Understand that subsequent changes to integrated systems may have impacts across the system.
Be aware that integrating systems, especially into a single GUI like PSIM, may accentuate any
deficiencies in legacy systems.
The factors affecting cost for an integrated system include:
One-way or Two-way: whether the integration is unidirectional or bidirectional affects complexity;
Functionality: To say two things are integrated is meaningless until one defines which features have
been integrated, which affects complexity;
System Size: Larger systems with more components are more complex to integrate than smaller
ones, and the cost of maintenance is also much higher;
Multi-Function Software Licensing: Cameras can be licensed based on IP address requirements.
Some multi-imager cameras are licensed by camera, i.e., if a dome configuration has four cameras
it will require four IP addresses and four licenses even if the camera outputs are stitches into a
Links Archive Navigation Previous Page Next Page