LEADER 02896oam  2200397zu 450 
001 9910219981303321
005 20240617065441.0
010   $a0-8330-8335-X
035   $a(CKB)2560000000315314
035   $a(SSID)ssj0001400561
035   $a(PQKBManifestationID)12484127
035   $a(PQKBTitleCode)TC0001400561
035   $a(PQKBWorkID)11344240
035   $a(PQKB)10128878
035   $a(EXLCZ)992560000000315314
100   $a20160829d2013      uy         0
101 0 $aeng
181   $ctxt$2rdacontent
182   $cc$2rdamedia
183   $acr$2rdacarrier
200 10$aAssessing Aegis program transition to an open-architecture model /$fPaul DeLuca
210 31$aSanta Monica, CA:$cRand,$d2013
215   $a1 online resource (xxviii, 98 pages) $ccolor illustrations
300   $aBibliographic Level Mode of Issuance: Monograph
311 0 $a0-8330-7879-8 
327   $aIntroduction The IWS business model for Aegis acquisition Aegis and the Aegis enterprise Impact of the IWS business model and implementation choices on the flee tImplications for the Aegis enterprise Risks Lessons learned from ARCI and SSDS Conclusions and recommendations
330   $aAegis is a highly integrated U.S. Navy combat system with anti-air warfare, ballistic missile defense, surface, subsurface, and strike roles that is currently operating on 84 ships. To reduce the costs of maintaining the system, and to take advantage of rapidly evolving commercial computing technology, the Navy is moving Aegis toward open-architecture software, a common source code library, and commercial, off-the-shelf processors. As it moves forward in implementing its integrated weapon system (IWS) model for the development, integration, and testing of upgrades to the Aegis weapon system, the Navy must consider the impact of this plan on Aegis facilities, personnel, and timelines. Of particular concern are the effects of new modernization and fielding rates on the technical infrastructure of the Aegis fleet. This report examines the potential benefits of the IWS model and the challenges associated with the transition from the Navy's legacy model for Aegis acquisition and development. It examines the pace of upgrades to both hardware and software and the speed with which they spread throughout the fleet. Finally, it proposes an upgrade schedule that offsets software (advanced capability builds) and hardware (technology insertions) to maximize the Navy's benefit from commercial industry's technology replacement cycle and ensure value for fixed development and testing budgets.
606   $aAEGIS (Weapons system)
615  0$aAEGIS (Weapons system)
676   $a359.8/2519
700   $aDeLuca$b Paul$01242664
801  0$bPQKB
906   $aBOOK
912   $a9910219981303321
996   $aAssessing Aegis program transition to an open-architecture model$92882650
997   $aUNINA