From the get go, leadership was a challenge. The vehicle developers were unaccustomed to being subcontractors and the Lead System Integrator lacked familiarity with the US Army. Also within the US Army there were challenges with coordination between the multiple programs. The manned and unmanned vehicle programs both relied heavily on the modernization of the communications program to be effective; however, the communications program did not rely as heavily on the vehicles. The acquisition office premise was that a smaller force could be effective by seeing first and acting with precision but the operational units’ experience was things do not go as planned and overwhelming force is required.
There were numerous capabilities required which exceeded the technology readiness level. As stated, situation awareness was going to rely on indirect vision, cameras, feeding video to monitors. While this technology is effectively employed in providing security to a fixed position, on a moving platform this will be very disorienting and there was concern about the reliability and defensibility of the sensors. Indirect vision was also to be a design concept for driving the vehicles. I had the opportunity to test drive a vehicle both day and night with indirect vision and while I was able to achieve all of the objectives of the test drive without the safety drivers intervention, direct vision is preferable.
To overcome some weaknesses in situation awareness, the program was integrating advanced automatic protection weapons systems. This was one of the more classified elements due to the fact that disclosure could allow weaknesses to be found and exploited by an enemy. Prototypes of these weapons systems were developed and tested early and results were promising. Some of these programs have been continued for integration on existing platforms.
I supported the development of the common crew station that would be used by all of the manned vehicles. This concept of commonality was expected to pay huge dividends in reduced complexity and logistics support. There were several other subsystems that would be common to the vehicles. At the start of the program, the vehicle subcontractors were to have shares in each subsystem. This proved to be very challenging to coordinate and it was scraped. Instead the subsystems were divided up to the vehicle subcontractors.
I continued to work on the common crew station which as one would imagine had substantial user interaction. The Human Systems Integration was very proactive in defining requirements and assessing concepts. While challenged with indirect vision, the other elements of the workstation were strongly influenced by the ergonomics to operate and maintain the vehicle and the cognitive workload to perform the tasks with a reduced number of soldiers from current force. Modeling was used very effectively to evaluate ergonomics aspects and mockups were built to simulate and evaluate.
While the FCS program was canceled, there are valuable lessons that I learned about Systems of Systems. Effecting a change in areas like leadership would be well beyond my scope but learning how the programs are structured to identify where the leadership exists and then trying to influence the leadership is possible. Leapfrogging technology is never a good idea on large scale but incremental insertion is possible. Early and continued engagement with customer not only ensures that will deliver what customer needs but also builds trust. Understanding the complexities of how humans interact with the systems is not trivial, something as trivial as alphabetizing can be misunderstood.
If anyone has an experience you would care to share or have differing opinions, contact myself or use the "Contact Us" form to the right.
By Rollie Olson
INCOSE SFBAC President
No comments:
Post a Comment