Theater Battle Management Core Systems (TBMCS) System Sustainment

REQUEST FOR INFORMATION For U.S. Marine Corps Theater Battle Management Core Systems (TBMCS) System Sustainment This Request for Information (RFI) is for planning purposes only and should not be construed as a solicitation for applications or an obligation on the part of the Government. The Government will not pay for the preparation of any information submitted or for the Government's use of that information. This is a request for market research for information purposes only and does not constitute an Invitation for Bid or a Request for Proposal. As such, it should not be considered as a commitment on the part of the Government. Pursuant to FAR 15.201(e), responses to this RFI are not offers and cannot be accepted by the Government to form a binding contract. Vendors/interested parties are solely responsible for all costs and expenses associated with their respective response to this RFI. Industry responses to this market research request are placed on notice that any information received by the Government does not ensure participation in any planned/anticipated future solicitations or contract awards. Description: This RFI is to gather information as part of a market survey to determine the availability of sources able to provide software sustainment and post production life cycle software support of the U.S. Marine Corps (USMC) Theater Battle Management Core Systems (TBMCS) system baseline. TBMCS is a U.S. Air Force lead program, with joint interest. TBMCS serves as the focal point for Joint air warfare command and control, integrating systems for planning, tasking, intelligence-gathering and execution into a single, common interface. It is the primary system for planning, managing and executing the air battle, feeding real-time, decision-quality information to users from the Joint Forces Air Component Commander (JFACC) and the staff at the Air Operations Command (AOC) to pilots, navigators, and weapons control officers on the battlefield. TBMCS links the command and control systems for the United States Air Force (USAF), United States Navy (USN), and United States Marine Corps (USMC), and integrates with ground systems for the Army systems, enabling coordinated, synchronized air battle management. The program is post Milestone C and in sustainment. Sustainment is currently being performed by Lockheed Martin Information Systems and Global Solutions (IS&GS) at their Colorado Springs, CO facility, and Hill Air Force Base (AFB), UT. The Government is not capable of providing additional Government Furnished Equipment (GFE) for this effort due to fiscal constraints and without causing a break in existing software sustainment efforts at LM IS&GS. TBMCS software is approximately 5 million total source lines of code, made up of various programming languages (ADA, Java 2 Platform Enterprise Edition (J2EE), C, C++, Perl, Unix Shell Scripts, SQL, Ant, Batch Code, Visual Basic, and AWK). Additionally, it utilizes multiple specific compilers and libraries for legacy UNIX applications which include Sun C++ compiler, Forte Developer 7 C++ 5.4 2002/03/09, Sun C compiler, Forte Developer 7 C 5.4 2002/03/09, KL Group XRT Table v2.2.1, Field v1.1.0, Gear widgets, v2.0.1, etc. Operating systems include Solaris 8, Solaris 10, Windows 2000, Windows XP, Windows Server 2003/2008, with middleware consisting of Oracle 9i/11g, Oracle Weblogic Server 9.2/10.3, Systematic IRIS, and Java Runtime Environment 1.6. TBMCS Unix applications are Defense Information Infrastructure Common Operating Environment (DII COE) compliant with sustainment actions required to be able to maintain that DII COE baseline for interoperability and Information Assurance. USMC sustainment efforts will have to be integrated with USAF/Joint sustainment efforts in order to maintain interoperability with the USAF/USN TBMCS baseline. The USMC sustainment support must be able to be accomplished without compromising joint TBMCS performance and functionality, and without compromising the Information Assurance posture of the system. The intent is to not only sustain the USMC baseline, but increase the Information Assurance posture of the system. Requirements: The USMC is requesting information from industry sources that have systems development and integration and hardware/software engineering experience in the sustainment of products that include tactical Command and Control (C2) applications which include the integration of hardware/software updates required to maintain fielded system capabilities from a capabilities and information assurance perspective. Respondents are requested to provide information specifically on the following: a. Evidence of competent systems engineering and integration experience that includes both legacy and engineering integration of web-based applications (first and second generation) and service inventories and deployment in the sustainment of TBMCS software and software languages; or equivalent C2 software and proficiency in the various TBMCS software languages (i.e., ADA, J2EE, C, C++, Perl, Unix Shell Scripts, SQL, Ant, Batch Code, Visual Basic, AWK), operating systems (Solaris 8, Solaris 10, Windows 2000/2003/2008/XP, DII COE 3Z) and middleware (Sun Java Runtime Environment 1.6, Oracle 9i/11g, Oracle WebLogic Server 9.2/10.3, Systematic IRIS), Apache Web Server and COTS application (Microsoft Office 2003, Internet Explorer 7, Firefox). b. Evidence of competence in implementing Information Assurance in relation to Web and Solaris-based and DII COE based architectures for multiple security level domains from unclassified through Secret (with desirable understanding of Sensitive Compartmented Information (SCI)), including Department of Defense (DoD) Information Assurance Certification and Accreditation Process (DIACAP) and Security Content Automation Protocol (SCAP) processes. c. Demonstrated knowledge of and capability to support fielded software maintenance including a Tier II 24-Hour Help Desk, urgent maintenance, fixes, documentation, and contingency support for TBMCS. The support will include technical expertise and assistance on questions and issues related to TBMCS fielded systems, system patches, service packs, real-world contingencies, exercises, and testing. This support will require the availability of a secret classified lab configuration capable of addressing the USMC TBMCS fielded baselines, and interoperability with the USAF and USN TBMCS baselines, and all requisite system interfaces. d. Capability to integrate and assume software maintenance responsibility for any other software code base not originally developed by your organization (i.e., third party software), but of similar complexity and scope to that of the TBMCS system. e. Minimum Capability Maturity Model Integration (CMMI) Level 3 compliance in the respective business unit and process controls to ensure that work performed by subcontractors is consistent with CMMI Level 3. f. Demonstration of understanding of Joint Interoperability of C2 systems. g. Understanding of the Air Operations Center and the Tactical Air Command Center TBMCS operations and challenges. h. Capability to perform testing/regression testing and to resolve hardware/software issues resulting from baseline changes in fielded systems (i.e., Information Assurance Vulnerability Alerts (IAVAs), Technical Change Notification Orders (TCNOs), and Group Policy Objects (GPO) upgrades. i. Availability of resources to sustain large scale, software intensive fielded systems, including but not limited to: (1) Qualified Staff with proper clearances for selected key personnel at time of award. (2) Adequate facilities, including labs, for analyses and testing (which includes classified communication capabilities) to maintain system baselines. j. Demonstration of an understanding of net-centric data/service exposure. k. Demonstration and familiarity with DoD Community of Interest (COI) processes, relevant COI schemas and specifications (e.g., the Air Operations COI (AO COI) schemas)), and overall data registration and discovery processes. l. Demonstration of proficiency in business process modeling/management (BPM), electronic workflow, and service orchestration. m. Evidence of understanding the Net-Centric Data Strategy, Net-Centric Enterprise Solutions for Interoperability (NESI), Net-Centric Enterprise Services (NCES), Modular Open Systems Architecture (MOSA). n. Demonstrated ability to perform Releasability Analysis. o. Evidence to perform TBMCS sustainment and sustainment transfer activities with no break in service to the end user (Warfighter). ? Response Format: Interested vendors who believe they are capable of providing a voice network solution as described above are invited to express their interest by responding to the Requested Information in this RFI with a white paper in Microsoft Word for Office 2007-compatible format. RFI responses are limited to 20 single-sided, 1" border pages, including cover and administrative pages, and shall be delivered using 12 point font or larger. The paper size shall be 8.5 x 11 for text and 11 x 17 for diagrams. Please be advised that any vendor proprietary information must be marked as such on a page-by-page basis. The Government will not assume that any of the information provided by a respondent is proprietary unless it is conspicuously marked on a page-by-page basis. Moreover, the Government does not assume any duty to contact a respondent and inquire whether any unmarked information submitted in response to this RFI is proprietary. Additionally, interested firms are requested to provide the following information in their RFI response: (a) company name, company address, overnight delivery address (if different from mailing address), cage code, point of contact, e-mail address, telephone number, fax number; and (b) indicate business size (i.e., large, foreign, small disadvantaged, veteran owned, minority owned, etc.) to the Government representative listed below. Response Deadline and Submissions: Responses are requested no later than 29 March 2013 at 16:00 EDT. Responses shall ONLY be submitted via email to Natasha Jones in accordance with the address below. It should be noted that telephone replies will not be accepted. Contact Information: Natasha Jones PEO-LS AC2SN, Contracts Email: natasha.jones@usmc.mil