SOURCES SOUGHT
A -- Procurement Strategy Approach For Systems Design And Development Phase Deployable Joint Command And Control System Increment II
- Notice Date
- 6/27/2005
- Notice Type
- Sources Sought
- Contracting Office
- NSWC Panama City, Code XPS, 110 Vernon Ave., Panama City, FL
- ZIP Code
- 00000
- Solicitation Number
- N6133105QLH01
- Response Due
- 7/29/2005
- Description
- THIS IS A REQUEST FOR INFORMATION ONLY. NSWC Panama City, on behalf of the Deployable Joint Command and Control (DJC2) System Joint Program Office (JPO), seeks information from firms capable of providing Deployable Joint Command and Control (DJC2) Increment II System Development and Demonstration (SD&D). THIS IS NOT A NOTICE OF SOLICITATION ISSUANCE, BUT RATHER A REQUEST FOR INFORMATION and COMMENTS from Industry that will help the Government develop a longer term contracting strategy for DJC2. The information sought herein is for planning purposes only and should not be construed as a Request For Proposal (RFP) or as any obligation or commitment on the part of the Government to acquire any product or service. There shall be no basis for claims against the Government as a result of any information submitted in response to this RFI. Again THIS IS NOT A REQUEST FOR PROPOSAL. The Government does not intend to award a contract on the basis of this RFI or otherwise t! o pay for any information submitted by respondents to this request. The Government will take reasonable care to protect and limit the access to information submitted to only those Government employees and JPO support contractor employees that are directly involved in the development and execution of the program?s acquisition strategy. The support contractors and their involved employees have executed non-disclosure agreements with the Government in regard to this program. The contractors that administratively support this effort are: Applied Research Associates, Inc., Albuquerque, NM, The Titan Corporation, San Diego, CA, and Radiance Technologies, Inc. Huntsville, Alabama. Background. Summary. DJC2 is a DoD major Information Technology (IT) investment and is designated as an Acquisition Category (ACAT) IAM Major Automated Information System (MAIS) program. DJC2 is required because existing JFC deployable joint C2 capabilities are neither standardized nor interoperable across the Military Services and Regional Combatant Commanders (RCCs), and do not capitalize on emerging technology. The current ad hoc approach to establishing and equipping Joint Task Forces (JTFs) in a crisis delays operations and limits the ability for effective C2 during quickly developing operations. The DJC2 capability is urgently needed to be operationally dedicated for deployment across the full spectrum of conflict, and to be reconfigurable to meet specific mission objectives. DJC2 is one of the Department of Defense?s (DoD?s) highest priority Command and Control (C2) programs, and is a key component of the DoD transformation strategy to achieve a truly joint C2 capability at ! the Joint Forces Commander (JFC) level. System Description. DJC2 will provide a modular and rapidly reconfigurable suite of hardware, networking, supporting infrastructure, and mobility components, as well as limited organic en route and early-entry communications capabilities. The system is designed to provide JFCs a mission critical, integration of systems with which to plan, control, coordinate, execute, and assess operations across the spectrum of conflict. Core C2 functionality of DJC2 Increment II will be transitioned from Global Command and Control System ? Joint (GCCS-J) to the Joint Command and Control (JC2) system. The DJC2 program supports the Standing Joint Force Headquarters (SJFHQ) concept and doctrine developed by the U.S. Joint Forces Command (JFCOM) in coordination with other RCCs and the Joint Staff. DJC2 will be a key enabler of the Joint Functional Concepts described in Joint Operational Concepts, November 2003. It will provide the necessary C2 capabilities for a JTF HQ to handle the full Range of Military Operations (ROMO), as discussed in JROCM 023-3, Interim Range of Military Operations, 28 January 2003. It will be the first system to meet the Joint, Multinational, and Interagency interoperability challenges described in An Evolving Joint Perspective: US Joint Warfare and Cross Resolution, 28 January 2003, endorsed by JROCM 022-03, 28 January 2003. Increment II will be defined by Increment II Capabilities Development Document (CDD) ? refer to Supplemental Information posted to the DJC2 website https://www.djc2.org/industry. The primary capabilities satisfied by DJC2 include supporting Joint Task Force (JTF)/Regional Combatant Commanders (RCC) operations by providing a standard consolidated capability set, through modular configurations. DJC2 enhances an RCC?s ability to rapidly activate and deploy a JTF with a command package that can sustain operations for days or weeks, support efficient routing of distributed C2 through collaborative network, and decrease the lag between deployment and full operational capabilities. DJC2 provides a modular and rapidly reconfigurable suite of hardware (e.g. laptops, computer terminals, servers and peripherals), networking (routers, switches, cables, and security components), supporting infrastructure (e.g. power, environmental control units (ECU), shelters, furniture), and mobility components (e.g. containers, transit cases, limited ground transportation, and pallets). It also provides limited organic en route and rapid response kit communications capabilities, different employment configurations of C2 capabilities, and supporting data systems. Increment II configuration options include: En route for situational awareness with limited C2 capability Rapid Response Kit using reachback with a light system capable of being transported by one or two persons on commercial or military aircraft Core to provide JTF C2 capability (core can subdivide into two separate deployable units of unspecified size to support split-based operations. . Acquisition Strategy. The DJC2 employs an evolutionary acquisition strategy that will be implemented in three distinct increments, using spiral development. Each increment is self-contained, targets a specific set of user requirements, and delivers multiple releases of increasing functional capabilities. Each DJC2 increment also includes a number of spirals. A spiral release consists of functional capability additions/enhancements and/or changes in the underlying system infrastructure. Spiral releases may also include changes in system hardware and software architecture, including technology update. Development for the increment ends with the fielding decision for the last scheduled spiral release. Increment I is a transformational increment, providing five spiral releases over the FY04 through FY07 timeframe. The Increment I systems includes a non-deployable JFCOM Core configuration system to support experimentation, CONOPs development and as feasible, developmental and operational testing. Increment I systems also include two deployable Core configurations for each of the RCCs designated to receive DJC2 systems. Deployable Core configurations will also include limited organic communications capabilities supporting en route and early entry operations. Increment I is migrating toward the DoD Net Centric and Global Information Grid-Enterprise Services (GIG-ES) architectures. Due to the urgent need for this system, NSWC PC is serving as the systems integrator for Increment I to allow maximum flexibility and responsiveness. Increment II is a transitional increment: DJC2 will transition from Global Command and Control System Joint (GCCS-J), providing core C2 for Increment I, to Joint Command and Control (JC2) as software becomes available. Increment II is envisioned to deliver two additional Cores to each RCC beginning in FY08. Statement of Objectives. The main goal of the DJC2 Increment II program is to create a cost-effective, superior means to deploy, setup, install, operate, and maintain a Joint Command and Control (C2) Combat Operations Center (COC) infused with the latest advanced technology in order to improve the ability of Joint Task Force/Joint Force Commanders to provide C2 functions by equipping them with core, tested C2 applications and collaboration tools. A principal objective of the DJC2 Increment II program is to optimize system performance while reducing system footprint to ensure faster time to field through increased concurrency. The Milestone B SD&D effort will focus on: (1) Leveraging new technologies and prototype designs successfully demonstrated during the pre-Milestone B Technology Risk Reduction effort for Rapid Response Kit design and prototyping, as well as identifying additional proven concepts, strategies and technologies that will meet Increment II system performance requirements. (2) Reducing integration and production risk through the development of a robust system design that meets or exceeds CDD requirements, includes sufficient modularity and expandability to allow for incremental inclusion of future requirements as technology upgrades over the system service life, and supports commonality of architecture, configuration, and equipment to reduce overall life cycle costs. Development and demonstration will be aided by an efficient test and evaluation program. Requested Input from Industry. Industry is strongly encouraged to submit information to the DJC2 Joint Program Office (JPO) via email at steven.grant@navy.mil and theodore.hynson@navy.mil. All responses shall be limited to less than 10 normal type (10 pitch or greater) and size pages (8.5? by 11?) and are required by 29 July 2005. Requested information includes but is not limited to: 1. Propose alternative contract strategies and business models, including the following: a. Pros and Cons of single/multiple contractor(s) as Systems Integrator (SI). b. Innovative contract approaches that address the JPO?s desire to: (1) integrate pre-Milestone B efforts into the SD&D effort; (2) foster open architecture; (3) conduct additional rapid prototyping as necessary; and (4) provide for future technology re-fresh/insertion. c. Show why your alternative/approach provides value to the DoD. This is best done by proven benchmarks and metrics, where you can demonstrate achieving the required performance for the minimum amount of dollars. d. Government/Industry Partnering. 2. Response to any or all of the following questions: a. As a corporation, how would you support the transition of SI work from the government to industry? b. Describe how your company would apply sound engineering principles, including security engineering, to the translation of DJC2 capabilities needs into an operational useful system. c. Describe recommended approaches to back fitting and forward fitting if appropriate to Increment II technologies into Increment I systems. d. Describe alternative approaches to system prototyping to evaluate how DJC2 new technologies/capabilities will perform in the actual operating environment. e. Describe how technologies demonstrated during the pre-Milestone B technology risk reduction effort for Rapid Response Kit capability can be matured and further demonstrated to prove their suitability for Increment II system design. f. Recommend test and evaluation and combined test team approaches to a complex C2 system, with multiple interfaces, multiple remote operators, and multiple networks. Discuss how to leverage existing government and contractor test facilities and resources. g. Describe or recommend suitable sustainment strategies for a system deployed worldwide requiring 24x7 technical support, parts management, technology refresh, and system upgrades (spiral releases). h. Outline within the context of a Joint Program with leadership from OASD NII, PEO C4I & Space, Navy acquisition authority, two resource sponsors (JFCOM and Navy), current industry and Government involvement, and extensive use of existing military resources across all Services. i. What are the benefits to the Government for utilizing a lead system integrator and how do you see industry playing a role in this construct? The ?scope? of a lead system integrator? j. If not the primary Increment II SD&D Integrator, describe how, as an innovative company, you would desire to work with the JPO to integrate your product/technology into DJC2. k. Describe performance metrics that should be applied to the Increment II SD&D phase that could be used for a basis of contract structure and award. l. How does the Government determine that it is getting best value for spiral development? 3. Industry perspective on whether the JPO should conduct another DJC2 Industry Day. An Industry Day was conducted in October 2004. If conducted, Industry Day II will be held as an unclassified meeting. The format for Industry Day II will include government briefs from Working Integrated Product Team (WIPT) representatives. Industry questions/inputs from this RFI will be consolidated and briefed at the conference or by industry participants during subsequent working group meetings. The Government believes the information requested above can be submitted without a contractor having to include any business sensitive or proprietary information. However, should such information be submitted and marked by the submitter accordingly, any proprietary information provided as part of the information requested above will not be included in the brief of consolidated inputs at Industry Day II and will be protected in accordance with 18 U.S.C. Section 1905 4. Additional Information on the DJC2 Program An expanded version of this Request for Information with additional detail and description of the DJC2 program will also be published on the following website locations: a. NSWC Panama City Business Opportunities web page: http://www.ncsc.navy.mil/contracts/Ztables/sourcestab.htm b. Deployable Joint Command and Control Increment II System web page: https://www.djc2.org/industry
- Web Link
-
NSWC Panama City Sources Sought
(http://www.ncsc.navy.mil/Contracts/Ztables/sourcestab.htm)
- Record
- SN00837321-W 20050629/050627212309 (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 |