DRAFT_Attachment 4 - Logistics Requirements_C2PL-25-3.docx

DOCX document 37 KB Posted

Attached to
DRAFT Combined Synopsis/Solicitation: Next Generation Surface Search Radar (NXSSR)
Solicitation number
70Z04426RC2PL2503
Issued by

About this file

This document is a Draft RFP Attachment 4 for Logistics Requirements related to the Next Generation Surface Search Radar (NXSSR) System for the US Coast Guard. The logistics plan requires contractors to provide comprehensive details about component supportability, including mean time between failures, reparability levels, end-of-support dates, and replacement strategies. Key requirements include proactively managing component lifecycles, implementing software updates, minimizing logistical footprints, and addressing Diminishing Manufacturing Sources and Material Shortage (DMSMS) concerns.

The logistics plan must specifically outline a four-tier DMSMS approach, with contractors required to identify and notify the Coast Guard of component discontinuations at least 18 months in advance, document supply source availability, conduct options analyses, and implement resolution steps. Contractors must find suitable replacement components that minimize design changes while maintaining system functionality, potentially delivering quarterly DMSMS reports. The Coast Guard has a stringent 12-month configuration control process, necessitating early notification of any hardware or software changes to ensure proper system integration and continuity.

View the file

Other files

Show all 11

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Draft RFP: 70Z04426RC2PL2503

DRAFT ATTACHMENT 4

LOGISTICS REQUIREMENTS

The Next Generation Surface Search Radar (NXSSR) System must be comprised of supportable components supplied by a vendor utilizing proactive lifecycle management. In order to address this concern, the following requirements must be addressed in the contractor’s proposed logistics plan, which is a part of the proposal and not a Contract Deliverable Line Item (CDRL).

The contractor’s proposed logistics plan must be clearly articulated in the “Logistics and Training Plan Section” of their technical proposal. The awarded contractor’s logistics plan will be included as an attachment to the final contract at time of award.

1.1 A detailed logistics plan that sufficiently outlines the overall approach to deliver, sustain, maximize component commonality and provide continuity of the proposed components over the duration of the awarded contract, plus the warranty duration for all items ordered.

1.2 For each component proposed under this contract, provide the following information:

1.2.1 Mean Time Between Failure (MTBF) for each item.

1.2.2 Discuss level of reparability of the item (i.e. consumable, extent to which the item may be repaired to the component level, etc.).

1.2.3 Expected end of support date for each item.

1.2.4 If end of support is within five (5) years, provide the form-fit-function replacement item anticipated to replace it and a statement affirming backward compatibility.

1.3 Explain contractor protocol and timeframes for notifying customers of end of life or critical maintenance/support issues throughout component lifecycle.

1.4 Include details as to how software updates will be implemented, and how the system will continue to meet all of the minimum specifications and functions over the life of the contract.

1.5 Address what can be offered to minimize the system's logistical footprint as well as address scalability possibilities and maximal use of common components across the various configurations.

1.6 Provide notification timelines as well as lead times for software updates, product/component end of life, and reparability support.

1.7 Address the methodology and timelines for replacement of components and demonstrate how minimum specifications will be met to include form, fit, power and functions for the life of the contract period.

1.8 The Coast Guard (CG) has a stringent configuration control process that necessitates 12-month lead-time to approve any software and/or hardware changes. The CG will require notification of changes or end of life of components, including planned dates of predecessor purchase non-availability. This notification must be given with sufficient time for the CG to process the configuration management change of the installed system prior to acquiring the replacement/updated component and placing it in service on a CG vessel. Address how the required information will be provided and on what schedule to permit the CG to abide by its configuration change processes.

1.9 Diminishing Manufacturing Sources and Material Shortage (DMSMS) Monitoring (HW/SW)

1.9.1 DMSMS is defined as the loss or impending loss of manufacturers of items or suppliers of items or raw materials. For the purposes of this requirement, DMSMS and obsolescence are used interchangeably.

1.9.2 The Contractor must assist the CG in implementing an aggressive, proactive approach to DMSMS and its impact on NXSSR. The Contractor must provide a four-tier approach focusing on the following concepts. The Contractor must, at a minimum of 18 months in advance:

1.9.2.1Identify and notify the CG of components to be discontinued.
1.9.2.2Document/verify that no other sources of supply exist.
1.9.2.3Accomplish an options analysis.
1.9.2.4Identify steps to implement resolution.

1.9.3 The Contractor must find suitable replacement components of DMSMS items and minimize the amount of design changes necessary to maintain the deployed NXSSR functionality baseline and component baseline. The Contractor may be required to deliver a quarterly DMSMS report describing recommendations and solutions.

1.9.4 The DMSMS effort must be performed in accordance with non-repairable Common Criteria Evaluation and Validation Scheme (CCEVS) approved components and information assurance (IA) accredited/certified processes. For non-IA enabled components, form, fit, function replacements will be investigated.

1.9.5 The Contractor must provide integration assistance when requested by the Contracting Officer and COR for identified DMSMS items.

File details come from the government source that posted it. Updated .