Select a Case Study Below

REDUCING BATTLEFIELD RESPONSE TIME
PRECISION ENGAGEMENT FOR HIGH-VALUE TARGETS

CLIENT:
PM High Mobility Artillery Rocket Systems (PM HIMARS).

CHALLENGE:
Significantly improving engagement response time once a high-value target is detected. It was taking too long for the Army's Multiple Launch Rocket System (MLRS) to respond to suitable high value targets detected by sensors on the battlefield. This delay in response was due to cumbersome target processing parameters. These parameters required targeting data to be successively filtered through intermediate command and control fire support elements (Corps, Division and Brigade), before being sent to fire direction centers, and finally to the launcher.

SOLUTION:
Three separate demonstrations, conducted between August 2003 and December 2004, proved Techrizon effectively designed a way to correct the target detection to engagement response time. Techrizon's solution was to develop HIMARS C2, an automated command and control system mounted on-board the MLRS firing platform.

This system made it possible to transmit fire mission data for high value, fleeting targets directly from the sensor to the launcher - without degrading command and control at intermediate levels. The first phase of development ended with a successful technology demonstration at Fort Sill, Oklahoma. Subsequently, Techrizon began developing the HIMARS Enhanced C2 System. We capitalized on the software developed for the previous technology demonstration and built in significant enhancements to include an interface with high frequency radios. This allowed us to increase the range for sensor to shooter transmissions.

Further enhancements allowed us to seamlessly support traditional fire support networks, while maintaining the sensor to shooter link. We also enhanced the target pairing functions. This made it possible to command one or more firing platforms to point at a predetermined target area. When sensors located targets in that area, the firing platforms could be rapidly commanded to engage that target. This significantly increased the likelihood of rapid, successful attacks on fleeting targets.

 [top]

FORMAL QUALIFICATION TESTS (FQT)
DESIGNED, DEVELOPED AND CONDUCTED FOR AUTOMATED BATTLEFIELD SYSTEMS

CLIENT:
The United States Army's Fire Support Software Engineering Center (FSSEC). A Capability Maturity Model Integrated (CMMI) Level 5 organization, the center oversees Fire Support Systems Software Engineering for the Army.

CHALLENGE:
To test six complex and diverse battlefield systems relating to Command and Control, Effects, Intelligence, Surveillance, Reconnaissance, and Meteorological Measurement. Prior to release of Software Version 7.01, for use throughout the Army, that branch of the military required rigorous FQT, which included:

• Extensive system level testing
• Message-oriented interface testing with both internal and
  external systems
• Mission-oriented interoperability tests in a Command Post Exercise
  configuration, and
• A comprehensive test of the Joint Variable Message Format
  messaging capability.

The Client also required Central Technical Support Facility (CTSF) Certification and Interface testing. As a result, Techrizon personnel at Fort Sill, Oklahoma, had to operate each system's test equipment as a remote facility interconnected to CTSF at Fort Hood, Texas.

SOLUTION:
The FQT results for software version 7.01 were far superior to those of the three earlier software versions used by the Army. And the improved results were accomplished despite the environment being far more complex and having more rigorous and demanding FQT requirements in place than when the previous versions were developed.

Further, the remote CTSF activity was configured and staffed by Techrizon's Systems Test Staff. This event marked a precedent-setting technological partnership among three major Army Commands.

Implementing an Incremental Software Development (ISD) approach was key to our solution. Under ISD, software is built in incremental phases throughout the development cycle. By following the ISD mandate to conduct testing for each phase, we ensured proper requirements were implemented. More importantly, testing at each phase of software development provided an opportunity for Techrizon Test Personnel to correct most anomalies prior to the start of FQT. As an added plus, it allowed them to simultaneously fine-tune their system skills.