Service-Oriented Architecture for Naval Strike Force Interoperability Readiness Navy SBIR FY2006.2 Sol No.: Navy SBIR FY2006.2 Topic No.: N06-127 Topic Title: Service-Oriented Architecture for Naval Strike Force Interoperability Readiness Proposal No.: N062-127-0797 Firm: Avineon, Inc. 4825 Mark Center Drive Suite #700 Alexandria, Virginia 22311-1846 Contact: Scott Starsman Phone: (757) 232-7043 Web Site: www.avineon.com Abstract: The Afloat Master Planning System (AMPS) module of the Navy Data Environment is the authoritative data source for the Fleet Commander Command, Control, Computers, Communication, Combat systems, and Intelligence (C5I) baseline. AMPS has evolved in response to emergent requirements without planning in a larger architectural context. The resulting system contains multiple interfaces for common tasks, lack of business rule protection for key data interfaces, and entangled code that is difficult to maintain and reuse. AMPS is becoming increasingly difficult to maintain and is having difficulty responding to the increasing requirements for secure data interchanges with other data sources. Additionally, there is a growing requirement to include planning information for classified systems and provide AMPS-based analysis that includes classified information. AMPS has added a SECRET enclave to provide this capabilities, but the movement of data between unclassified and classified AMPS is a largely manual process. There is a rapidly growing need to move data between these two enclaves (and possibly more) in a much more effective manner. The objective of Phase I is to demonstrate the applicability of an SOA solution to the architectural issues present within AMPS and then to develop a plan to transition AMPS to an SOA framework. Benefits: Both the need to provide a standardized, secure, flexible interface to AMPS and the need to rapidly and securely move data between security enclaves can be addressed by migrating AMPS to a Service Oriented Architecture (SOA). The Department of Defense (DoD) Information Technology Security Certification and Accreditation Process (DITSCAP) is forcing more robust security requirements that will mandate more sophisticated security applications that can only be implemented effectively via a SOA. Transitioning existing web-based architectures to SOAs is a quickly growing requirement within both the government and commercial sectors. This work will help develop a standardized methodology for making this transition. Near-term commercialization opportunities include a large number of eCommerce sites that are on the verge of making this transition but have been unable to develop an executable plan that maintains existing service while incrementally converting to an SOA. Return