Arms of CALI Provide US Navy with a Helping HandMay 25, 2010 18:30 UTC by Defense Industry Daily staff
Modern navies run on computers. Unfortunately, computers don’t last nearly as long as ships, something that’s both a hardware and a software problem. The computer console over there might be up to operating key systems on a billion-dollar warship, but a casual observer might be forgiven for wondering if it would be up to the task of running Pong. Behind that computer, an array of wiring and other mechanical components snake through the ship. They, too, have finite lifespans, but the networks they carry are vital. On top of it all, software systems run key programs, and tie various networks together. Some of those programs must change or be re-created when hardware shifts, while others change when new software replaces them.
All this has to be managed, and warships worth hundreds of millions of dollars have been retired early because their electronics upgrades were seen as too costly. Hence recent pushes toward open-architecture computing on many modern navy ships, built with commercial rather than military-proprietary components. Hence, also, programs like the US Navy’s future CANES (Consolidated Afloat Networks and Enterprise Services), designed to streamline and update shipboard networks, to improve interoperability across the fleet.
What to do until CANES? Enter the Common Afloat Local Area Network Infrastructure (CALI) effort:
From CALI to CANES
The goal of the CANES program is to build a secure shipboard network for naval and joint operations, consolidating and reducing the number of shipboard networks by using cross-domain technologies, and common computing environment (CEE) infrastructure standards. CANES Full Operational Capability is expected in 2017.
Until then, buying and maintaining existing legacy systems will be covered by the Common Afloat Local Area Network Infrastructure (CALI) contract. It will buy shipboard network infrastructure and CCE components, along with related engineering support, configuration management, test and evaluation, quality assurance, and installation support. Specific requirements will be defined in individual orders, issued within a multi-vendor umbrella contract.
CALI contract is intended to support production, deployment, operations and support of the following systems and equipment, which will eventually be brought under the US Navy’s CANES once it reaches full operational capability:
- CENTRIXS-M (Combined Enterprise Regional Information Exchange System – Maritime)
- ISNS (Integrated Shipboard Network System)
- NTCSS (Navy Tactical Command Support System)
- SCI (Sensitive Compartmented Information) Networks
- CSRR (Common Submarine Radio Room)
- SubLAN (Submarine Local Area Network)
Other systems also may utilize the CALI contract as needed, in support of the United States Navy’s overall shipboard I.T. portfolio.
Contracts & Key Events
May 24/10: The US Space and Naval Warfare System Command in San Diego, CA issues the CALI contract to 3 firms, each of which can compete for future task orders. Each contract is worth up to $408.8 million, with ordering period extensions that could raise it to $502.2 million. Of course, the near-certain outcome is division of that contract total among the winning firms.
This requirement was solicited using full and open competition via the Space and Naval Warfare Systems Command e-Commerce and Federal Business Opportunities Web sites, with 8 offers received. The 3 winners were:
- Lockheed Martin Corp. in Eagan, MN (N00039-10-D-0002)
- Science Applications International Corp. in San Diego, CA (N00039-10-D-0003)
- General Dynamics One Source, LLC in Fairfax, VA (N00039-10-D-0004),
Work will be performed in Eagan, MN; San Diego, CA; and Fairfax, VA, and is expected to be complete by May 31/14 – or May 31/18 if the optional ordering period is included.
- SPAWAR Business Opportunity Headquarters (Solicitation
- FedBizOpps (Feb 5/09, #N00039_SNOTE_0000C562) – Common Afloat Local Area Network Infrastructure (CALI) Industry Day
- DID – US Navy to Lean on CANES to Integrate Shipboard Networks [updated]