Attachment 12_Logistics Plan Requirements.docx

Attachment 12 Logistics Plan Requirements Solicitation: 70Z04421R21000900

The AIS-2 shall be comprised of supportable components supplied by a vendor utilizing proactive lifecycle management. In order to address this concern, the following requirements shall be addressed in the contractor’s proposed logistics plan.

The contractor’s proposed logistics plan shall be clearly articulated in the “Logistics 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.

Threshold: A detailed logistics plan that sufficiently outlines the overall approach to deliver, sustain, maximize component commonality and provide continuity of the proposed components up to the full vessel kit quantity (12 total vessels) over the duration of the awarded contract, plus the warranty duration for all items ordered.

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

· Mean Time Between Failure (MTBF) for each item;

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

· Expected end of support date for each item;

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

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

Threshold: 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.

Threshold: 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.

Threshold: In accordance with FAR 52.227-14, Rights in Data – General, the Government is asserting unlimited rights to any data produced or delivered under this contract as well as any data previously created by the contractor, which relates to the system, which is the subject of the contract. The contractor should identify any exceptions or rights they deem appropriate under FAR 52.227-14.

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

Threshold: 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.

Threshold: The USCG has a stringent configuration control process that necessitates 12-month lead-time to approve any software and/or hardware changes. The USCG 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 USCG to process the configuration management change of the installed system prior to acquiring the replacement/updated component and placing it in service on a USCG vessel. Address how the required information will be provided and on what schedule to permit the USCG to abide by its configuration change processes.