SOURCES SOUGHT
A -- Market Survey notice for follow on contract for Maneuver Control System (MCS) and Global Command and Control System Army (GCCS-A)
- Notice Date
- 3/11/2005
- Notice Type
- Sources Sought
- Contracting Office
- US Army Communications-Electronics Command, CECOM Acquisition Center - DAAB07, ATTN: AMSEL-AC, Building 1208, Fort Monmouth, NJ 07703-5008
- ZIP Code
- 07703-5008
- Solicitation Number
- W15P7T-05-RN420
- Response Due
- 3/30/2005
- Archive Date
- 5/29/2005
- Small Business Set-Aside
- N/A
- Description
- Requirements Office Address Project Manager Ground Combat Command and Control (GC C2), Building 2525, Fort Monmouth, NJ 07703 This notice is to survey the marketplace to identify potential sources, in addition to the current contractor, for the follow on contract for the continued development of the Global Command and Control System (GCCS-A) and sustainment of the Maneuver Contro l System (MCS) 6.3 Unix based platform and integration, test and training of the Army Injectors into the Joint Tactical Common Operational picture Workstation (JTCW). The proposed effort has a period of performance 1 Oct 05- 30 Sep 07. A brief synopsis of the proposed effort is provided below. This notice is to determine if there are contractors qualified to compete for this effort recognizing the product specific expertise, domain experience, and time constraints required to successfully accomplish the specified tasks. Interested contractors should submit information concerning their qualifications and ability to complete the required work to either Ms. Kathleen Maxwell (kathleen.maxwell@mail1.monmouth.army.mil or Ms Barbara Girgus (barbara.girgus@mail1 .monmouth.army.mil.) Task 1: MCS is an automated tactical Command, Control and Communications (C3) system that provides a network of computer terminals to process combat information for commanders and their battle staffs. It provides automated assistance in the collection, storage, r eview, and display of information to support the commanders decision process. Both text and graphics are provided to the user. It enables operation staffs (G3/S3) to process and distribute situational awareness, estimates, plans, orders and reports. Th e system is designed to operate with existing and planned communication networks. It is an essential component of the Army Battle Command System (ABCS) and provides critical coordination among Battlefield Functional Areas (BFAs) within each echelon. MCS provides the Common Operational Picture (COP) software supporting the battlefield situation display for all Command Posts from Corps to Battalion echelons. The COP depicts information provided by all the BFAs to MCS for integration and display and include s a Situation Map, an integrated Blue Picture consisting of platform and unit position reports from all other BFAs, a Red Picture provided from ASAS and from enemy observation reports submitted by other BFAs and soldiers on the battlefield, a set of graphi cal control measures depicting the units scheme of maneuver and concept of operations, Intelligence and Electronic Warfare graphics, Fire Support Control Measures and targets graphics, combat service support location information and graphics, air corridor s and air defense weapons control information. MCS also provides Army Combat Engineering capabilities via the integration of MCS-Engineer software and provides Nuclear, Biological and Chemical (NBC) planning, reporting, warning, analysis, and prediction c apabilities via the integration of the Joint Warning and Reporting Network (JWARN) software. There are 3 MCS software baselines - MCS 6.3.6, MCS 6.3 Delta, and MCS 6.4. The MCS 6.3.6 and 6.3Delta versions have been used in support of OEF/OIF. MCS 6.3.6 (Unix and Windows solution) is issued to 1CAV, III Corps HQ, and SBCT 1, 2, and 3. MCS 6.3 Delta (Windows solution) has been issued to the remaining Army units. MCS 6.4 is in the final stages of development and test and will be deployed in 1st Qtr. 06 in support of OEF/OIF The task that will need to be accomplished, by either the existing contractor or another source established via the market survey process, is the continued maintenance of the MCS Version 6.3.6 Unix-based product in support of all its current fieldings. The contractor tasked to accomplish this effort would have to have detailed knowledge and experience with the code in order to sustain it through security and safety updates, Commercial-Off-The Shelf (COTS) I nfrastructure updates, interface/database updates from other systems that interoperate with MCS, and continued troubleshooting support in the field both CONUS and OCONUS. The MCS 6.3.6 Unix-based system code is written in Java, C++, C, and Unix Scripting Language. Task 2: The Joint Tactical COP Workstation (JTCW) represents the convergence of Army and Marine products into a single joint workstation to meet the U.S. Army and U.S. Marine Corps ground tactical command and control requirements in accordance with JROCM 161-03. T he Army is in the process of adding current capabilities found in their MCS and GCCS-A products onto this single joint workstation platform in the form of injectors/applications needed to satisfy the Army requirements. The initial Army functionality built on the JTCW 7.0 infrastructure is scheduled for a Sept 05 delivery to SPAWAR to continue its development through an integration and IV&V phase and then to an operational evaluation in FY06 with and early FY07 fielding decision. JTCW 7.1 is scheduled to b e delivered in 3rd Qtr 06. This delivery will be targeted to incorporate updates to meet requirements for the DoD network-centric key performance parameters, Army Software Blocking requirement upgrades, and enhanced functionality for Joint interoperabilit y. Army Software Blocking activities and initiatives may drive additional deliveries(s). The effort that is planned for the current Army JTCW contractor or other source established via the market survey process, would be the continuation of the overall coordination of all aspects of JTCW Systems and Software Engineering and full responsibility for Army injector integration, test, configuration management, quality assurance, delivery, logistics, training, and risk management to ensure the JTCW satisfies Army requirements and Army injectors are properly designed, interfaced, and are interoperabl e. This effort is for the JTCW 7.1 delivery and any further deliveries prior to the Sept 07 timeframe. In addition, the contractor will be responsible for continued development and sustainment of the Near Real Time Server (NRTS) /Publish and Subscribe Server (PASS) Data Provider and the Multinational Interoperability Programme (MIP) injector for the JTCW to include: Problem Report resolution Foundation product upgrades ABCS updates and modifications as required for NATO interoperability Enhancements to the configuration GUI, Server console and persistent storage for improved system configuration Modifications as required for Joint and NATO interfaces in the data model, schema and mappings Demonstration team to support exercises, test events and demonstrations of the MIP Understanding of the code base, Domain Business Rules, and data flow for the NRTS/PASS are essential for continued development and sustainment of ABCS interfaces. Understanding of the code base, Domain Business Rules, and Data Model and interoperability i n the NATO environment are essential for continued development and sustainment of the MIP. Task 3 The Global Command and Control System-Army (GCCS-A) is a service specific implementation of the DoDs Joint Global Command and Control System (GCCS-J). GCCS-A is the Armys strategic and theater Command and Control (C2) system and serves as the bridge bet ween the Joint community and the Army Battle Command System (ABCS). Built on the Common Operating Environment (COE) foundation, GCCS-A provides many client/server applications that are used to support critical C2 functions, including force readiness, for ce planning, force projection, and situational awareness. Product Manager (PdM) GCCS-A, part of the PM GCC2 organization, needs to ensure support of the GCCS-As development and deployment of critical functionality that is tightly coupled to the Global Command and Control System Joint (GCCS-J). The upcoming v ersion of GCCS-J 4.0 will require updates to GCCS-A, the Armys extension of GCCS -J. During this period, PdM GCCS-A will synchronize the development and fielding of the GCCS-A Block 4 with GCCS-J Block V . In order to support the PdMs requirements, the contractor will need to provide engineering and technical support services to inc lude system engineering, design, software development, hardware integration, testing, training, field support, program support, system accreditation activities, segmentation support, and on-site support to the Central Technical Support Facility (CTSF) at F t Hood, TX. Two software baselines, Operational and Strategic, are currently under development. The code contains approximately 43 Computer Software Configuration Items (CSCI) with a line of code count of about 6.7 Million, not including the Commercial Off-the-Shelf S oftware and Government Off-the-Shelf Software (COTS/GOTS). The code is written in a variety of languages that include, but are not limited to, Ada, C++, COBOL, Powerbuilder, and Java. Software Development Folders (SDF) are available in various forms but have not been audited for the final delivery. A high level schedule for the period of performance (October 05 thru September 07) is outlined below. All feature lists associated with a release/delivery are notional; the release/delivery will include but not be limited to those functions listed. Durin g this period GCCS-A will be positioning the baseline for transition to a Service Oriented Architecture (SOA) based on web services technologies to include JOPES, SORTS, WebCOP, and WEEMC. This two year period will involve architecture changes to GCCS-A i n order to combine the current operational and strategic baselines into one fieldable baseline with selectable capabilities based on echelon. The major releases during this period will be 4.1, 4.2, and 4.3 which support the corresponding GCCS-J Block V re leases. It should be noted that the breakout of the joint capabilities by release within Block V have not been published. The GCCS-J Block V capabilities/functions that GCCS-A will build upon for 4.1, 4.2, and 4.3 are: Improved security posture " Posture security infrastructure to utilize NCES services as they become available " Authentication (single sign-on), Authorization (role based access control), and Confidentiality (encryption), " Auditing and logging Implement netcentric technologies " Migrate from client/server to a common N-Tier/ Service Oriented Architecture infrastructure " Begin implementation of many-to-many vs. point-to-point data exchanges using web services technologies " Begin transformation from self-contained mission applications to C2 services that can be combined to create JC2 Mission Capability Packages Command and Control functionality " Implement single architecture and enterprise-class infrastructure " Implement NCES-ready, standards-based, services-oriented architecture " Provide scalable to support more users per server enclave " Provide integrated, but application independent, run-time common services: Web and J2EE application servers Load balancing and redundancy Single administration console Expanded use of thin client and rich client technologies in which client functionality is delivered vs. installed Small client administration burden Reduced COE footprint The development cycle will run 12 months for each of the GCCS-J Block V releases (4.1, 4.2, and 4.3). GCCS-A must implement its supporting releases within 30 days of GCCS-J. GCCS-A B4.1 delivery projected for 3QFY06 will implement an enhanced Common Operational Picture (COP). GCCS-A will also integrate and implement the Web Enabled Mission Management Capability (WEEMC) and WebCOP. WebCOP will be a complement to the existing C2PC as a Situational Awareness tool. Additionally COP injectors, as provided by GCCS-J, will be implemented for Army use. This release will build on the existing GCCS-A 4.0a and 4.0b releases to create a single GCCS-A baseline that can be fielded to all echelons. Of particular note, all new software and hardware must be IPV6 compliant and as existing software is opened for enhancements or fixes, it too must be made IPV6 compliant. It is anticipated that this release will require int egration of the JOPES Data Exchange (DEX) implementation along with the common Oracle database for GCCS-A (whether developed by Lockheed Martin or another contractor). Each release will also contain necessary COTS and security upgrades to meet technology insertion and IAVA requirements, respectively. GCCS-A B4.2 delivery is projected for release in 3QFY07. New or enhanced functionality planned for GCCS-J v4.2 will be built upon for the Army implementation. This may include: Initial n-tier capability w/PKI certificates and publish/subscribe capabili ty, 3-D representation of intelligence and imagery data, and Joint STARS. This block must ensure supportable hardware/software end of life cycle issues are addressed. GCCS-A will continue transition to SOA and NCES architectural requirements and the web -enablement of additional application process. This release will also contain necessary COTS and security upgrades to meet technology insertion and IAVA requirements, respectively. GCCS-A B4.3 delivery is projected for 3QFY08. Currently it is anticipated that the functionality enhancements would include: Joint Network Management System (JNMS), Joint Engineering Planning and Execution System (JEPES), Weapons of Mass Destruction Medic al Analysis Tool (WMD MAT), COP - universal interface standard, and Alternative Courses of Action (ACOA), and theater wide LAN, upgrade mission applications and interfaces. Each release will also contain necessary COTS and security upgrades to meet techn ology insertion and IAVA requirements, respectively. In addition to the requirements specified above the contractor will also be responsible for the following: The developer will also be in charge of performing V&V on all user/software documentation and training materials for each release. Developing quarterly patches containing bug fixes, upgrades in support of on-going OEF/OIF activities/deployments, and IAVA update requirements. Support of test reviews, verification testing at Joint and Army levels, Milestone decisions, Joint Family of System (FoS) activities, and documentation requirements. Summary Any source interested in this effort will need to be able to accomplish all three tasks outlined above. The Government will require that you be able to provide backup data showing that your firm has full knowledge of and ability to sustain the various prod ucts, and would be able to continue development, where necessary, in order to meet the Governments requirements and schedule. A detailed response must include how you will meet these requirements, without schedule delays, to include identification of ant icipated risk areas and strategies to mitigate such risks. You will also need to provide backup data showing that your firm in the past has successfully assumed a contract in mid-development. The Government will not reimburse contractors or responders to this notice for any costs incurred in responding, or in subsequent exchange of information. All proprietary and restricted information shall be clearly marked. Please submit all responses no la ter than 30 March 2005.
- Place of Performance
- Address: US Army Communications-Electronics Command, CECOM Acquisition Center - DAAB07 ATTN: AMSEL-AC, Building 1208 Fort Monmouth NJ
- Zip Code: 07703-5008
- Country: US
- Zip Code: 07703-5008
- Record
- SN00767018-W 20050313/050311212104 (fbodaily.com)
- Source
-
FedBizOpps.gov Link to This Notice
(may not be valid after Archive Date)
| FSG Index | This Issue's Index | Today's FBO Daily Index Page |