Department of the Navy, Naval Sea Systems Command, 2531 Jefferson Davis Highway, Arlington, VA 22242-5160

A -- ADVANCED DEVELOPMENT SOL N00024-99-R-5107 POC John Murray, (703) 602-7903, Ext. 514 BROAD AGENCY ANNOUNCEMENT FOR SHORT TERM CONCEPT STUDIES RELATING TO AN AREA AIR DEFENSE COMMANDER (AADC) CAPABILITY The Navy has embarked on a program to develop and deploy an advanced command and control system to provide real time battle management to enable the execution of the Theater Ballistic Missile Defense (TBMD) and overall theater air defense missions. As part of the total Navy effort, the Area Air Defense Commander (AADC) capability is a command and control system element for execution of the Area and Navy Theater Wide TBMD and Joint Warfare programs. Studies have suggested that improved real time battle management within the constructs of network centric warfare is necessary to optimize weapon system performance and operator decision making. Using current state of the market display and computer program technology, the command and control system that will be developed for the AADC will provide automated Force Planner and Tactical Operations capabilities to extend the commander's ability toplan, monitor, and execute assigned warfighting functions. The AADC effort is currently in the concept development phase of the acquisition process, and the Naval Sea Systems Command is soliciting proposals for short term concept studies for an AADC capability. The objectives of these studies are to obtain the following: 1. A conceptual design approach for an AADC capability which meets the operational requirements specified in the draft Operational Requirements document (ORD); 2. A software engineering approach for the conceptual AADC design that: -- Identifies the source and effort required to develop the computer programs to satisfy each functional requirement in the System-Subsystem Specification (SSS). The approach should also address programming, documentation, quality assurance, configuration management standards, and the process, procedures, and tools to be employed. The approach shall identify, for each functional requirement, the extent of new development that will be necessary. For reuse, it should also identify the source (e.g. Defense Information Infrastructure -- Common Operating Environment (DII-COE) segment name, mission segment name), extent (e.g. design, code), and description and estimate for any re-engineering, modification, enhancement or additional documentation required. The software engineering approach should make maximum use of commercial industry standards and COTS tools. -- Assesses the scope of effort required for DII-COE compliance at Level 6 for the AADC conceptual design. In conducting the assessment, identify any impediments to DII-COE compliance at level 6 and higher, and need for any engineering change proposals to DII-COE to meet AADC requirements. -- Assesses the DII registered mission segments and other sources of existing and emerging DII-COE compliant application software (e.g. Theater Battle Management Core Systems (TBMCS), Global Command and Control Systems (GCCS)) for applicability to AADC requirements. -- Assesses emerging advanced computing technology projects (e.g. Advanced Information Technology Services (AITS), Leading Edge Services (LES), and COSTS advanced computing technologies (e.g. CORBA, Open GL, and JAVA) and other non-vendor-specific standards, programs and tools for applicability to AADC requirements. -- Analyzes the AADC requirements in the ORD and SSS relative to existing and planned capabilities of the DII-COE and DII-LES. -- Assesses any design concepts, software algorithms, interfaces, software or lessons learned from existing or developing programs that might be applicable to a production AADC system. This may include the AADC Prototype (to be discussed). 3. An analysis of the critical characteristics and capabilities of an AADC capability based on the AADC ORD and SSS; 4. An assessment of the cost, performance and schedule risk posed by the technologies critical for the conceptual design approach; 5. A general approach to testing the conceptual AADC design including computer programs, hardware, DII-COE, and interoperability; 6. A concept for developing a Total Ownership Cost (TOC) methodology that includes all costs associated with the research, development, procurement, operation, logistical support, ship impact (e.g. space preparation and installation), and disposal of the AADC system. This should include common support items and costs that are incurred because of the introduction of AADC, as well as the total supporting infrastructure that plans, manages and executes AADC over its full life. The TOC methodology should include identification of the primary TOC cost drivers. Proposed approaches for reducing those costs should include Cost as an Independent Variable (CAIV). 7. A metrics plan for computer program and equipment development, program progress, and interface requirements. 8. Cost of the proposed AADC conceptual design with supporting rationale. The deliverables under this effort shall be delivered not later than six (6) months from date of award and shall include: 1. AADC conceptual design. 2. Software engineering approach, including DII-COE compliance assessment, and risk management approach. 3. Critical characteristics and capabilities analysis. 4. Critical design technologies assessment. 5. General approach to testing. 6. Methodology for assessing and minimizing Total Ownership Cost (TOC). 7. Proposed Metrics. 8. AADC conceptual design cost estimate. The offerors are requested to submit a technical proposal that: 1. Outlines their approach for developing an AADC conceptual design. 2. Describes how the conceptual design approach will ensure that the AADC capability will meet the requirements of the ORD and SSS. 3. Outlines their software engineering approach, to include: The development process, design, and documentation standards, and evidence that these standards have been implemented and result in a disciplined software development. A demonstration of a full understanding of industry and open, object oriented, distributed system interface standards which are consistent with the JTA and DII-COE and incorporation of evolutionary technologies. A demonstration of an understanding of capabilities and limitations of applicable DII-COE compliant mission segments, LES/AITS segments, and emergent open system, object oriented, software technology and standards. A demonstration of an understanding of an approach to interfacing the conceptual AADC design with other systems, (e.g. AEGIS Command and Decision, TBMCS, other potential Joint host command and control systems, and GCCS-M). The process and metrics by which the software engineering approach will support management's ability to track and predict development progress and program quality. An overall approach to ensure the software development process meets end system performance objectives. 4. Outlines their approach for developing the Total Ownership Cost methodology for the conceptual design. 5. Addresses past performance with evolving programs based on COTS, DII-COE, advanced computing systems, and advanced display systems. As a minimum, the past performance should address programs developed which include: DII-COE. Distributed object-oriented developments which were/are not specific to a particular system (e.g. CORBA), development and performance testing of computationally intensive computer programs in a parallel processing environment using POSIX threads. High performance 2-D and 3-D graphics within an open system environment. Software segmentation. Software documentation. Past performance and experience in integrating similar systems into Joint command and control systems. Past performance and experience in Joint, Naval, and Combined Air Defense operations. Metrics used to measure the success and progress of similar programs in which the offeror has been involved. The offerors shall submit a price proposal that accurately reflects the proposed technical effort. TECHNICAL APPROACH CRITERIA Proposals will be evaluated and selected based on: (1) System and software development capabilities and past performance in hardware and software development and integration; (2) Technical merit of the proposed AADC conceptual design approach; (3) Merit of the Total Ownership Cost approach for the conceptual design; (4) Past performance and experience in Joint, Naval, and Combined Air Defense operations; (5) Merit of the metrics proposed. PRICE CRITERIA The Government may consider funds availability, price realism, and reasonableness as appropriate. The Government considers the technical approach to be significantly more important than price; and within the technical approach criteria, of the 5 subfactors, 1 and 2 are of equal weight and 3, 4, and 5 are of equal weight, though significantly less important than 1 and 2. The technical proposal (exclusive of proposal cover pages, tables of contents, glossaries of abbreviations, tabbed dividers, resumes, and title pages) shall be no more than sixty (60) pages and will be evaluated only on sixty pages. The narrative material in the proposal shall be one and one-half spaced, typed or printed in New Times Roman font with type no smaller than 12-point font. Paper shall be 8-1/2 X 11 inches (standard size) with a minimum margin of 1 inch around the page. Any typed narrative included on graphics pages may not be smaller than 12-point font. The proposal shall be bound in three-ring binders to permit removal of sections. Offeror shall provide an original and five (5) copies of the proposal. Foldouts are not permitted. Proposals shall be UNCLASSIFIED. The technical proposal may be incorporated by reference into any resultant contract, and may serve as the basis for the work to be accomplished. Each task description shall be written to facilitate evaluation and acceptance without the need for major rewrites if incorporated into the resultant contract. The technical proposal shall include a program milestone chart that includes a detailed list of tasks and sub-tasks and the duration of the same. The Government seeks unlimited rights in all technical data and computer software delivered under any contracts awarded pursuant to this BAA. The offerors must provide a list of technical data and computer software it will deliver with less than unlimited rights in accordance with DFARS 252.227-7017. The Government will consider offers from other government activities. The Government intends to use one (1) or more contractors to assist in reviewing offeror proposals, the names of which will be provided to all companies attending the Industry Day briefing. Offerors will be required to permit the Government's assisting contractors to view their proposals. The Government's assisting contractors will all sign non-disclosure agreements. The price proposal shall be separately bound in a three-ring binder to permit removal of sections. Offerors shall provide an original and five (5) copies of the price proposal. An Industry Day briefing will be conducted for all interested offerors on Tuesday 1 December 1998, at 0900, at TECHMATICS, 12450 Fair Lakes Circle, Suite 800, Fairfax, Va.. Attendance will be limited to four (4) representatives from each company. ForwardSECRET clearances to: TECHMATICS Three Crystal Park 2231 Crystal Drive, Suite 1000 Arlington, Va. 22202-3742 Telephone: 703-521-3818 Fax: 703-521-0175 Security Point of Contact: Ms. Kim Johnson Meeting Point of Contact: Mr. Jon Fantin As a risk reduction activity, the Government has rapidly prototyped a partial AADC capability as a Proof of Concept at the Johns Hopkins University, Applied Physics Laboratory (JHU/APL). To further the prototyping process, a segment of the JHU/APL prototype is planned for installation onboard an AEGIS Cruiser in FY 99. The prototype effort was not developed with the system engineering rigor or ORD compliance required for a production system. To assist with understanding the AADC concept, interested offerors will be permitted to schedule an information visit to JHU/APL on 2 December 1998 to view a demonstration of the AADC prototype. The demonstration is scheduled from 0900-1100. The following procedures have been established for interested offerors to visit JHU/APL: a. The Point of Contact (POC) for the visit is Mr. Greg Miller; Tel: (240-228-6803). b. Offerors shall check in with the POC. c. Visits shall be by appointment only, scheduled no later than 1 December 1998 at the Industry Day briefing. d. Visits are to be limited to one visit per offeror with a maximum of three (3) persons. Proof of security clearance for all visitors must be provided in advance of the visit to the POC. All visitors must be U.S. citizens and possess a SECRET or higher security clearance. Security clearance and visit request(s) stating the specific visit date, visitors names and levels of clearance must be sent to: John Hopkins University/Applied Physics Laboratory (JHU/APL) Johns Hopkins Road Laurel, Maryland 20123-6099 FAX: 301-953-5910 A reading room will be established with procedures for access and use provided at the Industry Day briefing. The AADC Acquisition Web Site at http://www.navy-aadc.org includes the Navy's DRAFT ORD and SSS. The AADC web site also provides links to other web sites with information potentially useful for this effort, including the DII-COE and DII-LES. Access to the AADC Acquisition web site will be made available following the Industry Day. The Government intends to award up to four contracts based on proposals submitted in response to this Announcement, within a total budget of $4,000,000. The contract type will be Firm Fixed Price (FFP). No contract will exceed $1,000,000. Under no circumstances will a contractor be entitled to more than the Firm Fixed Price it proposed for performance of the contract. A delivery schedule for the deliverables will be negotiated with the successful offerors. There will be no formal Request for Proposal (RFP) or other solicitation request for this BAA. Only one (1) proposal from each offeror (or offeror team) will be accepted. All responsible sources may submit an offer which will be considered, but must do so on or before 2:00 PM Eastern Standard Time on 20 January 1999 to be considered. Proposals shall be delivered to: Commander, Naval Sea Systems Command Department of the Navy National Center Building #3 Room 5E40, Code SEA 0291 2531 Jefferson Davis Highway Arlington, VA 22242-5160 and shall be marked: RFP N00024-99-R-5107 Attn: Mr. John M. Murray, SEA 02513 DO NOT OPEN IN MAIL ROOM The Government expects to award contracts under this BAA during the 2nd quarter of FY99. The period of performance is anticipated to be six (6) months from date of award. Technical and contracting questions regarding this announcement should be directed in writing, to Naval Sea Systems Command, Attn: Mr. John M. Murray (SEA 02513), 2531 Jefferson Davis Hwy, Arlington, VA 22242-5160.***** Posted 11/17/98 (W-SN272194). (0321)

Loren Data Corp. http://www.ld.com (SYN# 0003 19981119\A-0003.SOL)