WASHINGTON (Army News Service, Nov. 12, 2010) - The Army recently published its first Common Operating Environment architecture guidance aimed at leveraging a common set of computing technologies and standards.
"This lays out what we are going to enforce in the United States Army," said Army Vice Chief of Staff Gen. Peter Chiarelli.
"The COE guidance will enable more secure and interoperable applications, and faster development of apps," said Mike Krieger, acting chief information officer/G-6 (CIO/G-6).
Both the CIO/G-6 and the assistant secretary of the Army for acquisition, logistics and technology developed and approved the guidance. Computing environments affected include server, client, mobile devices, sensors and platforms. The guidance is published at http://ciog6.army.mil/ArmyEnterpriseNetworkVision/tabid/79/Default.aspx.
"We are aiming to create an open, plug-and-play architecture," said Terry Edwards, director of System of Systems Engineering, ASAALT.
"Now sensors, battle command applications, mounted vehicles and the cloud enterprise will be built upon a common set of IP standards and protocol," said Edwards. "And it will be easier for innovative technologies to merge with existing systems."
In early 2011, ASAALT will publish a complementary implementation plan that describes the steps and schedule for bringing Army systems into compliance with the guidance.
"Soon, in order to obtain funding for developing and acquiring IT devices or systems, all programs under the Army Acquisition Executive will need to comply with the COE guidance and plan," Krieger said.
The COE guidance is one of several annexes to the overarching document "Army Enterprise Network Architecture" that guides future network procurements and establishes minimum technical architecture standards for the acquisition or development of IT and National Security Systems. The architecture document and some of the annexes will be published in the near future.
The COE augments the Army Software Transformation, which is standardizing end-user environments and software development kits; establishing streamlined software processes that rely on common pre-certified, reusable software components; and developing deployment strategies that allow users direct access to new capability.