A07_W91CRB18R0002_Attachment_J-8_ASABS_GBS-SA_Integration_Datasheet.pdf

UNCLASSIFIED

DISTRIBUTION A. Approved for public release: distribution unlimited.

Advanced Small Arms Ballistic System (ASABS) Government Ballistic Software – Small Arms (GBS-SA)

Integration Datasheet Product overview

The Fire Control Systems & Technology Directorate (FCSTD) of the US Army Armament Research, Development and Engineering Center (ARDEC) is pleased to announce the availability of a new Government developed ballistic software package (the GBS-SA) which supports the squad, precision, and crew served fire control missions. GBS-SA is software which provides three main features: a modified point mass trajectory algorithm based ballistic solver implemented by the US Army's Small Arms Ballistics Kernel (SABK), the inclusion of high accuracy ballistics data for US Army weapons and cartridges, and a weapon sight model which converts the ballistic solution results to weapon sight holds.

The GBS-SA software package has been developed using rigorous software development methods based on ARDEC's CMMI level 5 process. CMMI Maturity Level 5 is the highest level of software process improvement excellence that an organization can attain. It focuses on optimizing process performance through incremental and innovative technological improvements. The CMMI for Development at Maturity Level 5 consists of over 400 best practices in the disciplines of systems and software engineering that the ARDEC Armament Software Engineering Center (ASEC) has implemented in the development and delivery of products and services to the Warfighter.

Version 1.0 of the GBS-SA software package is currently delivered and under formal configuration management by the ARDEC ASEC's Configuration Management and Library Systems Facility.

Integration overview

The purpose of this datasheet is to provide prospective system developers with the integration information they require to evaluate the feasibility and scope of integrating GBS-SA into their fire control systems.

The sequence of events for integrating GBS-SA is:

A Government Agency or Contractor requests access to the GBS-SA. Upon approval, FCSTD delivers the GBS-SA Interface Control Document (ICD) / Interface Design Description (IDD) and Software User Manual which enables the Customer to begin GBS-SA integration planning and development. GBS-SA and associated documentation are Distribution D.

FCSTD configures the GBS-SA code-base to support the Customer required weapon + cartridge combinations, compiles the GBS-SA code-base into a binary format compatible with the Customer's hardware, and performs a pre-delivery Formal Qualification Test (FQT) on Customer representative test hardware (e.g. an agreed upon reference board).

FCSTD delivers the binary GBS-SA files (typically a static library and associated C header file) and the FQT Test Report to the Customer.

UNCLASSIFIED Government Ballistic Software – Small Arms (GBS-SA) Datasheet

UNCLASSIFIED

DISTRIBUTION A. Approved for public release: distribution unlimited.

Technical requirements of integration

Customer deployment hardware and software development environment must:

o Support an 8 byte floating point "double" data type (either in hardware or software emulated) o Support integration of static binary libraries with a C language interfaces

Customer representative test hardware and software development environment must:

o Have the same processor as the deployment hardware o Have the ability to build C code (with no external dependencies beyond the C runtime) into a static library that is compatible with both the test hardware and the deployment hardware.

o Have an external serial communications interface (RS-232 is preferred, UART is acceptable) which can be used by FCSTD's PC based automated test tool to communicate with an embedded test driver which runs on the representative test hardware.

The GBS-SA does not require:

o An operating system – GBS-SA has been written to be compatible with the smallest of embedded systems – it is written in pure C with no external dependencies outside of the C runtime.

o On-disk storage – the GBS-SA does not use external storage for logging or loading/saving of data files – ballistics data is compiled into the library.

Representative deliverable sizing and performance

The following are the results of a GBS-SA build conducted by FCSTD which can be used to support Customer integration planning.

Reference board: Microchip p/n 320007 (200Mhz PIC32 MZ2048EFH144 processor; 2MB of program space; 512KB of RAM)

Reference board test interface: RS-232 serial port

Development environment: MPLAB X IDE v3.10; XC32 v1.40 C compiler

Weapons + cartridges supported: 29 unique weapon + cartridge pairings supported

GBS-SA footprint: Based on this test application, it is recommended that the integrator allocate the following minimum amount of storage for GBS-SA integration:

RAM: 50Kb Program space: 200Kb

Measured performance: Representative time to compute a solution vs range.

100m shot: < 1ms 500m shot: 2ms 1000m shot: 5ms 1500m shot: 6ms

Point of Contact

To begin the process of acquiring the GBS-SA ballistic solver, please contact:

Mr. James L. Willis

(973) 724-7204 james.l.willis58.civ@mail.mil

Mr. Darren L. Ward

(973) 724-2748 darren.l.ward.civ@mail.mil

Stephen A. Graham

(410) 278-5172 stephen.a.graham8.civ@mail.mil mailto:james.l.willis58.civ@mail.mil mailto:darren.l.ward.civ@mail.mil mailto:stephen.a.graham8.civ@mail.mil