TFD Group/Systems Exchange

Download our ACA datasheet: Sign In

The answer for software release…

ACA™ provides a systems approach to capture software versions and compatibility for aca
a build release.

Gain immediate visibility of software for system builds and insure hardware/software compatibility of the final load with a single software utility. ACA™ is built to exacting standards and can work for any system in which complex rules for compatibility of software and hardware releases must be observed.

Manage loadable
data files.

ACA is used in the post software development process and beyond. Software builds may be made up of one or several executables across different subsystems on a loadable platform. ACA insures compatibility in each software or system build between hardware, firmware and software. Compatibility assurance is also extended to the latest versions of courseware, operating manuals and technical data for operation and maintenance activities.
Compatibility of software and hardware configurations is critical to a total systems approach to maintenance, operation and technology insertion. Support equipment and/or portable maintenance aids (PMAs), which interface to the aircraft or vehicle, must be the right version to operate properly. ACA allows for building or importing hardware/software compatibility tables to be used in documentation and maintenance information systems. ACA supports a process, building upon compatibility business rules, from receipt of new software releases or inception of a build request through the entire software release cycle to the factory or field.

ACA Functions

Capture system-level approach to software/ system builds
Plan and execute software/system builds
Manage content of software/ system builds
Relate metadata for tech data, and courseware versions/releases
Create or import hardware/software compatibility tables
Secure maintenance of executables and data files in a relational database
Link data files, documentation and executables
Import/export capability
Editable headings on forms
Create custom reports

Who uses ACA?

Software Build Planners
Software Build Technical Leads
Software/System Build Execution and Release
Configuration Management
System Engineers
System Integration & Test
Management Team and Team Leads
Computer technicians in the field
Various users in read only mode

Build Execution and Release
ACA allows a software technical lead to plan a software build and build links to other software components, data files and documentation. ACA allows a software technical lead to capture all versions or “recipes” of the software in a build or
system level release. ACA uses a top-level software ID, or part number and a build request number for each release.

Common database for software, data files, related metadata, and documentation.

Compatible support elements are related to the build in ACA, tightly coupling the build with such elements as pilot flight manual versions, courseware versions, technical publication (IETM) versions, and any other software elements subject to change that might be found in specialized support equipment or training systems. The ACA tool can store the actual software executables, data file templates, loadable data files, and all types of related documentation.
The focus of ACA is configuration management of software and related products after development. The entire plan, build, and software release process can be managed and simplified by this integrated solution. aca2
Data File Management.

Keeping track of software builds and the make up of the build is valuable in and of itself, but the system approach of ACA introduces significant new capabilities. ACA is able to track, store, and relate data files that are used in conjunction with the software and are normally installed under a maintenance action. These data files may be weight and center of gravity data, boresight, flight test aids, or any other data that might be loaded to the platform in the form of a computer data file. ACA links the required format and schema of the data file with the software release to ensure compatibility. Both the actual software build and specific data files loaded to a system can be identified with the system’s serial or tail number.
ACA can be used in the operating and support phase of a system’s life, as well as in the production phase.

Import/Export and Accessibility
ACA can import from a variety of file types and formats, including XML, Excel®, database formats and others. The import routines can be customized to accept data from other sources. The export of data can be formatted for support of software reviews, presentations, status meetings etc. The software, data files, and documentation are accessible and can be downloaded for use in laboratories, factory, engineering test and evaluation and in the field.

System Administration and Security aca3
ACA has a full range of administrative capabilities. The administrator can set up any combination of user capabilities to mirror the process and organization of your managerial methods. There are four functional user distinctions:

System administration
Planning and execution of software builds
System upload of software build
End-user data review

These can be mixed, matched and modified to reflect your approach to software/hardware compatibility. ACA can be web-based or delivered over either wide area or local area networks. ACA runs in both the UNIX and PC environments.
ACA operates in classified or restricted data environments. Tandem systems can be installed, one running in an open environment and another in a sealed or classified data system. Place holders in the two systems preserve the total build structures, but allow isolation of sensitive data from the rest of the system. This method of deployment serves both ITAR and security requirements.