Loren Data Corp.

'

 
 

COMMERCE BUSINESS DAILY ISSUE OF MARCH 8,2000 PSA#2552

Commander, Marine Corps System Command, Code CTQ, 2033 Barnett Avenue, Ste 315, Quantico, VA 22134-5010

70 -- UNIT OPERATIONS CENTER (UOC) POC Mr. Stephen Riffe, Contracting Officer 703-784-0937, Fax 703-784-5826 WEB: UOC Web Page, http://www.marcorsyscom.usmc.mil/mcscctq/uoc.htm. E-MAIL: Mr. Stephen Riffe's E-mail address, riffesl@mcsc.usmc.mil. DESC: The purpose of this announcement is to conduct market research. This is not an Invitation for Bid, Request for Proposal, or a Request for Quotations. All information provided in response to this announcement is done so on a voluntary basis and at no cost to the Government. The Marine Corps Systems Command (MARCORSYSCOM) is inviting industry comments and recommendations on its operational requirement, system concept, and program acquisition schedule for the Unit Operations Center (UOC) System. At some future date, the Government intends to request that contractors design, and manufacture for test and eventual production GOTS/COTS/NDI systems to meet the following general concept. The Unit Operations Center (UOC) program is developing comprehensive command operation centers for U.S. Marine Corps Operational Forces and selected training units, both in garrison command centers (CCs) and tactical combat operations centers (COCs). It is envisioned that there will be 162 COCs and 19 CCs. It is desired that 10 percent of these assets be fielded by the end of FY02. Full fielding should occur by the end of FY06. The UOC will provide moodular/scaleable facilities and components, with maximum commonality across command echelons, to integrate current and planned battlefield automation systems at each command level throughout USMC ground-based operating forces. The COC will be used by Command Elements (CEs), Ground Combat Elements (GCEs), Combat Service Support Elements (CSSEs) and the support elements of the Air Combat Element (ACE). The COC will provide a readily transportable operational facility (OPFAC), processing and display hardware, and communications interfaces to support the integration of current and planned Tactical Data Systems (TDSs). The software from these NDI systems supports the six Marine Corps warfighting functions: command and control (C2), maneuver, fire support, intelligence, logistics and force protection. The COC should be capable of interfacing to any current, or planned, USMC communications asset, and to existing and planned TDS. The COC will provide power, cabling, vehicle antennas and networks to augment and interface to the current assigned "table of equipment" communications systems. The COC will be designed to facilitate the interaction and flow of information between the various staff members within the command, and between command levels/echelons. Each COC will provide a centralized operations capability to collect, process and disseminate tactical data via the integration of tactical vehicles, shelters, trailers, communications equipment and operational software programs, with operator workstations, displays, intercommunications and Local Area Network/Wide Area Network (LAN/WAN) systems in a fully functional mobile COC. The government's goal is to minimize the footprint by miniaturizing the current stovepipe systems and reducing the logistics support required through a combination of "racking and stacking" and re-hosting of the current Marine Corps software running on UNIX (Sun and HP), PC, and NT etc., platforms onto a single, more compact and ruggedized platform. The architecture of COC subsystems is intended to be capable of supporting current and future operational environments including but not limited to Operational Maneuver From The Sea (OMFTS), Sustained Operations Ashore (SOA), and Other Expeditionary Operations (OEO). Additionally, to ensure military utility in a broad range of operational scenarios, the COC should have the appropriate mobility and transportability attributes. The UOC is intended to be the first step in the process of automating C2 throughout the USMC. As such, the COC platform is intended to provide input to future requirements for evolutionary systems planned to meet C2 needs across the Marine Corps Operating Force structure, including aviation and logistics elements. MARCORSYSCOM is currrently in the Program Definition Risk Reduction Phase of this program and has initiated a web site for the UOC procurement which can be viewed at http://www.marcorsyscom.usmc.mil/mcscctq/uoc.htm Specific documents will be available in the near future for review/comment. These documents may include, but are not limited to: Excerpts from the Acquisition Strategy Summary; Draft System/Sub-system Specification (SSS); Draft Acquisition Schedule: Draft Acquisition Objectives; List of Government Questions for Industry. Additional documents will be posted to the web site as they become available/applicable. Interested parties are encouraged to comment immediately on all UOC information currently contained in the web site. It is expected that a DRAFT Request for Proposal (RFP), Performance Specification, and other pertinent procurement information will be available for viewing on or around 02 April 2000, with a final version posted in May of 2000. Although there are no time constraints for providing comments, it is requested that initial comments be submitted by 15 April 2000 to coincide with the ongoing RFP development process. As pertinent documentation is posted, MARCORSYSCOM is interested in and will be requesting industry comments regarding: (1) Suggested approaches regarding the general format and structure of the RFP for this effort; (2) Contract type; (3) Acquisition Schedule and timing of key events; (4) Draft System/Sub-system Specification; (5) Past Performance and other proposal evaluation criteria; (6) Availability of mature technologies and manufacturing processes to meet requirements under proposed schedule and the degree to which COTS/NDI solutions and components can be utilized. MARCORSYSCOM may incorporate industry comments into the final solicitation package. The Government is not soliciting proposals at this time. Industry comments and recommendations on the documentation currently contained in the UOC web site identified herein should be submitted electronically, as soon as possible, to: Stephen Riffe, MARCORSYSCOM at riffesl@mcsc.usmc.mil. Upon release of the DRAFT RFP, Performance Specification, etc., interested parties are again encouraged to submit comments and recommendations. All inquiries and comments should reference the applicable document, section, page number, and specific paragraph being commented upon. MARCORSYSCOM intends to hold a UOC Industry Day on Wednesday, 19 April 2000. Additional details will be provided on the UOC web site as they become available. It is the responsibility of the interested party to periodically view the UOC web site for newly released/updated documentation. All communications regarding this procurement should be submitted to: Stephen Riffe at riffesl@mcsc.usmc.mil. Posted 03/06/00 (W-SN431502). (0066)

Loren Data Corp. http://www.ld.com (SYN# 0293 20000308\70-0013.SOL)


70 - General Purpose ADP Equipment Software, Supplies and Support Eq. Index Page