18 -- MILSATCOM INTEGRATED SATELLITE CONTROL SYSTEM (MISCS) PROTOTYPE A -- OBJECTIVES. The MILSATCOM Program Office (SMC/MC) is seeking information to support the development of a plan for the streamlined acquisition of the MILSATCOM Integrated Satellite Control System (MISCS) under the "Command and Control System Consolidation (CCS-C)" program. MISCS will provide satellite control capabilities to support Air Force Space Command MILSATCOM satellite programs, including MILSTAR, DSCS III, NATO IV, SKYNET 4, Advanced Wideband Gapfiller, and Advanced EHF. The goal of this acquisition is to procure a proven, low life-cycle cost, command and control system. The system should be adapted from an existing command and control system, either one currently used to operate a commercial or military satellite system, or one that utilizes Commercial-Off-The-Shelf (COTS) hardware and software components to their best advantage. MISCS capabilities include: mission planning; telemetry processing; commanding; orbit and attitude management; resource management; space vehicle and ground system simulation; and support to satellite state-of-health operations from launch through disposal mission phases. MISCS must address the transition of legacy satellite programs as well as minimize the development for new satellite systems. MISCS software components should be not only highly reusable to lower development costs, but also integrated as part of an open underlying architecture. This architecture should form the basis of a broader component-based architecture to ensure a flexible design that will easily adapt to changing components and new satellite system needs. The current acquisition approach is to divide the program into two phases: a Prototype phase (~FY00-01) and a Development phase (~FY01-07). The Prototype phase will reduce cost and schedule uncertainty by verifying the feasibility of proposed concepts and obtaining cost and schedule data on product development. The Prototype phase is contemplated as an Other Transaction (OT) in accordance with 10 U.S.C. 2371, for the Prototype Agreement, with strong consideration being given to cost sharing. A Draft RFP for the Prototype is planned to be issued in Sep 99 and a Final RFP in Nov 99, with contract award approximately 1 Mar 2000 and a period of performance through Dec 2000. This RFI will initiate the discussion of all acquisition related activities for determining the content of the Prototype phase RFP. Notices and information for development of the Prototype phase RFP will be sent only to those companies responding to this announcement. The Development phase will be acquired through a standard FAR or FAR Part 12 contract. A full and open competition for the design, development, and deployment of the MISCS system is anticipated. A Draft RFP is planned in Aug 2000 and a Final RFP in Oct 2000, with contract award in the Jan-Apr 2001 timeframe. The MISCS development and deployment will support the launch and on-orbit operations of the Advanced Wideband Gapfiller and Advanced EHF satellites and transition of legacy satellite programs (MILSTAR, DSCS III, NATO IV, and SKYNET 4) from their current command and control systems. The overall objectives and schedule of the MISCS program are: (1) develop, deploy, and sustain a system that meets all requirements, including applicable interfaces with the Air Force Satellite Control Network (AFSCN) and with the listed MILSATCOM satellite programs; (2) complete development, test, and evaluation activities by 1 April 2003 for Advanced Wideband Gapfiller in order to support AFSPC Force Deployment Evaluation (FDE) and launch rehearsals; (3) support Advanced EHF launch rehearsal activities beginning July 2005; (4) transition legacy satellite programs from their current command and control systems, including support of FDE, by 1 October 2005 (baseline) -- there is a possibility that the schedule for transition of legacy satellite programs will be accelerated to 1 October 2003 (accelerated); (5) reduce costs of operations and sustainment from current systems (threshold requirement of no increase in operations costs and 50% reduction in sustainment costs ($TBD/year); objective goal of 30% reduction in operations costs and 75% reduction in sustainment costs ($TBD/year)); (6) minimize life-cycle cost by utilizing mature and fully integrated hardware and software; (7) minimize development to support new satellite programs and requirements; (8) effectively manage program resources to meet technical objectives on schedule and within budget; and (9) provide the Government with necessary insight into contractor activities and data for effective decision making. The specific objectives envisioned of the Prototype phase are: (1) develop specifications and preliminary design documents for the complete MISCS system, to include: (a) complete a draft MISCS System Specification and develop a draft allocated requirements document that baselines all functional and interface requirements for the Development phase; (b) develop a system operations and maintenance concept that reduces life cycle costs; (c) document a complete MISCS system architecture including descriptions of functionality and interfaces for all system components, system policies for interface management, data organization, system hardware and software, and a performance analysis methodology; (d) define a satellite and ground system simulation architecture to support system test, sustainment, and operator proficiency training; (e) design a core system that is easily expandable/extensible to support new satellite programs and requirements and changes in hardware and software; (f) define an engineering approach for interfacing with satellite developers to define and implement new requirements; (g) utilize a comprehensive approach for identifying and managing the selection, upgrade, and integration of COTS and Non-Developmental Item (NDI) hardware and software and the code necessary to integrate the selected products; and (h) define a system test approach that ensures requirements will be verified against validated baselines; (2) reduce risk and uncertainty by developing a prototype satellite control system for one DSCS III satellite and a portion of a MILSTAR satellite, to include: (a) document a detailed design for the prototype system and provide evidence of its compliance with the overall MISCS architecture; (b) develop selected MILSTAR vehicle-specific functions; (c) implement vehicle models from existing satellite documentation, mission-unique software, and/or databases to support maneuver planning during the demonstration; (d) build flight-qualified satellite telemetry databases (full DSCS III satellite and partial MILSTAR satellite); (e) identify and implement correct command sequences/constraints (full DSCS III satellite and partial MILSTAR satellite); (f) provide orbit analysis software that meets key accuracy/performance requirements; (g) provide attitude determination software to accommodate existing satellite attitude modes and sensor types; (h) interface with the AFSCN Remote Ground Facility; and (i) assess Command, Control, Communications, Computers, Intelligence, Surveillance, and Reconnaissance (C4ISR) Architecture Framework Version 2.0, Joint Technical Architecture (JTA), and Defense Information Infrastructure (DII) Common Operating Environment (COE) compliance; (3) demonstrate key performance requirements within the developed functional areas using a live satellite, or a satellite simulator, and the AFSCN Remote Ground Facility; and (4) develop a life-cycle cost estimate for the Development phase. The specific objectives envisioned of the Development phase are: (1) complete the development of the MISCS system including end-to-end system testing: (a) revise (as needed) the complete MISCS specifications and architecture documentation; (b) provide a complete detailed design with evidence of compliance to the MISCS architecture, including any product-line strategies; (c) complete satellite database and MUS development for Advanced Wideband Gapfiller, Advanced EHF, and legacy satellites; (d) provide satellite operations activity scheduling capability to meet requirements; (e) provide an engineering analysis capability to support satellite anomaly resolution; (f) develop a ground system simulation capability; (g) develop an integrated satellite system simulation capability that interfaces with GFE satellite simulators; (h) provide an integrated equipment monitoring capability; (i) implement current satellite support plans into the database for legacy satellite programs; (j) implement mission-unique equipment interfaces per current baselined interface specifications; (k) develop and provide logistics support assets and required documentation for operations, maintenance, and sustainment; and (l) support Advanced Wideband Gapfiller and Advanced EHF launch rehearsal commencement dates; (2) transition from current MILSATCOM command and control systems to MISCS without interruption in ongoing operational activity; (3) correct all latent deficiencies identified by the Government during Force Development Evaluation (FDE) and subsequent updates to the system through System Turnover to Air Force Space Command; and (4) implement system transition to sustainment, with either standard Air Force or Contractor Logistics Support. Details of the MISCS capabilities needed will be available in a draft Technical Requirements Document (TRD). B -- INDUSTRY DAY BRIEFING. An Industry Day briefing will be held on 13 August 1999, 0800-1200 hours PDT, at Building A1, Room 1062, The Aerospace Corporation, 2350 East El Segundo Blvd, El Segundo, CA. 90245-4691. The briefing will cover an overview of the MISCS program and the information being requested in this RFI. Interested parties who wish to attend are requested to submit the names of attendees to the POC via e-mail no later than 0900 hours PDT, 12 August 1999. No Facility Visit Requests are required. C -- SUBMISSION INSTRUCTIONS. Interested parties are requested to submit white papers of not more than twenty pages total (8.5 x 11 inches maximum each page, double-sided, Microsoft Word 97 format), via e-mail no later than COB 8 September 1999, with a backup submission on 3.5-inch floppy diskette to arrive no later than COB 9 September 1999. White papers should include the following information: (1) System Description. Provide a description of your satellite command and control system that would meet the objectives stated in Paragraph A. This should include the following: a system architecture diagram and associated text describing all major functional components of the system; a list of all COTS/NDI hardware and software used in the system; and a description of all custom development required to tailor the COTS/NDI hardware and software for a particular satellite and for the AFSCN Remote Ground Facility. (2) Customer Base. Provide a list of all commercial and government customers who are using your system for satellite command and control. For each customer, describe which of your components are being used and where the customer has developed custom hardware and/or software or purchased other vendor products to provide a full system capability. (3) Operations Concept. Provide a high-level operations and sustainment concept that illustrates how system life-cycle costs would be reduced. Include a discussion of numbers of personnel, skill levels, Air Force versus contractor personnel, and Air Force Integrated Logistics Support versus Contractor Logistics Support. (4) Program Objectives. Provide comments on the Prototype and Development (baseline and accelerated) objectives stated in Paragraph A for the MISCS system. (5) Component-Based Architectures. Provide comments on any ongoing corporate efforts related to component-based architectures and product lines for satellite command and control systems. For any currently viable product lines, discuss the number and types of customers, strategic plans, and references to any available documentation. In the architecture description provided in response to item C.1 above, provide a description of how products (either yours or another vendor's) can plug into such an architecture. (6) Standards and Architecture Compliance. Identify which JTA standards and DII COE components would be used in development of your satellite command and control system, and the planned level of DII COE compliance. (7) Any data that is proprietary or confidential should be marked accordingly. Relevant documents are available on the Web as follows: JTA Home Page: http://www-jta.itsi.disa.mil/ (contains relevant JTA documents); DII COE Home Page: http://spider.dii.osfl.disa.mil/dii/ and DII COE Engineering Home Page: http://coeeng.ncr.disa.mil/ (contain relevant DII COE documents). (7) Cost Information. Provide high-level information on the cost of the MISCS Prototype and Development phases (both baseline and accelerated), based on the Draft Technical Requirements Document. Costs should include COTS hardware purchase and installation, COTS software licenses, hardware/software development for the MISCS capabilities stated in Paragraph A, development for any satellite-specific software, and development of a flight-qualified database for one DSCS III satellite.D -- OTHER REQUIREMENTS. Foreign owned firms are advised that they will not be allowed to participate at the prime contractor level. To participate in this RFI, the contractor will require access to Militarily Critical Technical Data and classified data whose export is restricted by U.S. export control laws and regulations. Only contractors who are registered and certified with the Defense Logistics Information Service (DLIS) will be allowed to participate (in order to register with DLIS, registration with Dun and Bradstreet is required first (1-800-333-0505)). Contact DLIS, 74 North Washington, Battle Creek, Michigan 49016-4312 (800-352-3572) to register. A copy of DD Form 2345 will be required to attend the Industry Day conference and receive documents associated with this RFI. For information on registration, contact the CCR Assistance Center at 1-888-227-2423 or visit their web site at http://ccr.edi.disa.mil. Respondents are cautioned that only contracting officers are legally authorized to commit the government. This request is for information and planning purposes only, not a request for proposal, and does not commit the government to pay for preparation costs. Respondents are advised that no contract will be awarded solely on the basis of a response hereto or any follow-up information subsequently submitted. This information will be used to develop acquisition plans for future MILSATCOM ground architecture. If you have any questions, please contact Phillip Sanchez or Lt Brian Bone at the above stated numbers. WEB: Visit this URL for the latest information about this, http://www.eps.gov/cgi-bin/WebObjects/EPS?ACode=S&;ProjID=Synopsis-67&L ocID=901. E-MAIL: Phillip Sanchez, phillip.sanchez@losangeles.af.mil. Posted 08/03/99 (D-SN362284).

Loren Data Corp. http://www.ld.com (SYN# 0568 19990805\SP-0012.MSC)