Attachment-10_AIS2-Crosswalk_Amendment-0001.xls
XLS spreadsheet 97 KB Posted
- Solicitation number
- 70Z04418R18002300
About this file
Revised Attachment 10 (AIS-2 Proposal Crosswalk) to Solicitation 70Z04418R18002300.
View the file
Other files
Show all 17
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
SPECIFICATION
| TECHNICAL FACTOR / SPECIFICATION | SOLICITATION#: | 70Z04418R18002300 | SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104 | ||
| CONTRACTOR'S NAME: | |||||
| REQUIREMENT | Contractor Proposal-Where requirement is addressed in proposal (Document Name, Page #, Paragraph) | ||||
| Specification Section 1 - AIS-2 Requirements | |||||
| Specification 1 - The AIS-2 system components shall be available on the open market for a minimum of five years after contract award. | |||||
| Specification 1 - Manufacturer upgrades to the components shall be backward compatible to ensure integrated operations are maintained. | |||||
| Specification Section 1.1 - Hardware, Software & Component Items | |||||
| Specification 1.1 - AIS-2 shall consist of the following items, which are covered by this specification: |
1.1.1 One (1) transponder with the following components:
| 1.1.1.1 Minimum Display and Keyboard |
| Objective Requirement |
1.1.1.1.1 Graphical Display in lieu of minimum display, may be integrated with other components or separate Objective Requirement
1.1.1.1.2 AIS-2 graphical display shall be modular from the transponder.
Objective Requirement
1.1.1.1.3 AIS-2 user interface/controls shall be modular from the transponder.
| 1.1.1.2 Internal GPS or GNSS receiver |
| 1.1.1.3 Pilot Port with Cable, may be integrated with other components or separate |
| Objective Requirement |
1.1.1.3.1 AIS-2 pilot port shall be modular from the transponder.
| 1.1.1.4 A method (H/W and S/W) that allows a field technician to perform software/firmware upgrades |
| 1.1.2 VHF Antenna with Cable |
| 1.1.3 GPS/GNSS Antenna with Cable |
| 1.1.4 Power Cable |
| 1.1.5 Mounting Hardware |
| 1.1.6 AC to DC power converter (optional) |
| Specification Section 1.2 - Physical Characteristics |
| Specification 1.2.1 Standards compliance |
| Specification 1.2.1.1 - AIS-2 shall meet requirements contained in IMO Resolution A.694(17). |
| Specification 1.2.1.2 - AIS-2 shall meet the electromagnetic compatibility and immunity requirements contained in IEC 60945, current promulgated edition. |
| Specification 1.2.1.3 - AIS-2 display units and transponder processors shall meet requirements contained in IEC 60945 for “Protected” Equipment. |
| Specification1.2.1.4 - AIS-2 antennas shall meet requirements contained in IEC 60945 for “Exposed” Equipment. |
| Objective Requirement |
Specification 1.2.1.5 - AIS-2 display units shall meet IEC 60945 Chapter 8 standard for EXPOSED equipment.
Objective Requirement Specification 1.2.1.6 - All AIS-2 display units shall meet IPX5 of IEC 60529.
Objective Requirement Specification 1.2.1.7 - All AIS-2 display units shall meet IPX6 of IEC 60529.
Objective Requirement Specification 1.2.1.8 - All AIS-2 display units shall meet IPX7 of IEC 60529.
Objective Requirement Specification 1.2.1.9 - All AIS-2 transponder processors shall meet IPX2 of IEC 60529.
Objective Requirement Specification 1.2.1.10 - All AIS-2 components shall meet IPX2 of IEC 60529.
| Specification 1.2.2 Power |
| Specification 1.2.2.1 - The transponder shall be powered by 12 – 24 Volts Direct Current (VDC). |
| Spcification 1.2.2.2 - If any component or test equipment uses AC power: |
1.2.2.2.1 The equipment shall be powered by 115 Volts Alternating current (VAC).
1.2.2.2.2 The equipment shall utilize power supplies and converters that comply with shipboard environmental and technical requirements contained in NAVSO P-3641A Sections 1-3.
Objective Requirement Specification 1.2.2.3 - All system internal batteries shall be field replaceable.
Objective Requirement Specification 1.2.2.4 - AIS-2 equipment shall have an onboard system self test.
Objective Requirement Specification 1.2.2.5 - AIS-2 maximum power consumption shall not exceed 72W (6A @ 12V or 3A @ 24V)
| Specification 1.2.3 Wireless |
| Specification 1.2.3.1 - Any component of the AIS-2 system which allows wireless networking, shall be capable of having the wireless feature disabled. |
| Specification 1.2.3.2 - AIS-2 shall remain otherwise fully functional when wireless networking (non-VHF) is disabled. |
| Specification 1.2.4 Displays |
| Specification 1.2.4.1 - AIS-2 displays shall be capable of trunnion mount. |
| Objective Requirement |
Specification 1.2.4.2 - AIS-2 displays shall be capable of flush (console) mount.
| Specification 1.2.4.3 - If AIS-2 has a touch screen, the system shall have an alternate method of user data input and system configuration that does not require the use of the touch screen. |
| Specification 1.2.4.4 - All screens to be visible in direct sunlight, with backlight brightness equivalent to 400 NITS (cd/m2). |
| Objective Requirement |
Specification 1.2.4.5 - All screens must have brightness up to 1000 NITS (cd/m2). (Objective Requirement) Specification 1.2.4.6 - All displays shall provide an intensity control that allows:
1.2.4.6.1 All screens to be visible at night without loss of night-vision, down to 1 NITS (cd/m2).
1.2.4.6.4 Dimming shall be accomplished by controls that do not require the screen to be visible. Dimming shall not be accomplished solely via on-screen menus.
Objective Requirements Specification 1.2.4.6 - All displays shall provide an intensity control that allows:
1.2.4.6.2 All screens shall be dimmable to 0.5 NITS (cd/m2).
1.2.4.6.3 All screens shall be able to be powered off, while still maintaining all required transponder behavior.
1.2.4.6.5 All screen shall employ mechanical backlight dimming.
| Specification 1.2.4.7 - The controls and displays of the AIS-2 system shall be visible while the operator is wearing glasses/sunglasses with polarized lenses. |
| Objective Requirement |
Specification 1.2.4.8 - A control shall be provided to vary the contrast between the characters and the background.
Objective Requirement Specification 1.2.5 - AIS-2 shall include an option for a source processor capable of providing the required display remotely.
Objective Requirement Specification 1.2.6 - AIS-2 shall include an option for a source processor capable of providing the required user interface controls remotely.
Objective Requirement Specification 1.2.7 - AIS-2 shall include an option for a source processor capable of providing the required pilot port remotely.
| Specification Section 3.1 - Standards Compliance |
| Specification 3.1.1.1 - AIS-2 shall meet requirements contained in resolution A.1106(29). |
| Specification 3.1.1.2 - The COTS version of AIS-2 shall meet type-certification requirements contained in IEC 61993-2. |
| Specification 3.1.1.3 - AIS-2 shall meet Class-A AIS transponder requirements contained in ITU-R M.1371-5. |
| Specification Section 3.2 - AIS-2 Transponder Modes of Operations |
| Specification 3.2.1 - AIS-2 shall have a selectable transmit mode of Receive-only which conforms to Annex 1 of the EAIS IDD v5.5.3. (P00001) |
| Specification 3.2.2 - AIS-2 shall have a selectable transmit mode of Normal Transmit which conforms to Annex 1 of the EAIS IDD v5.5.3. (P00001) |
| Specification 3.2.2 - AIS-2 shall have a selectable transmit mode of Restricted Transmit which conforms to Annex 1 of the EAIS IDD v5.5.3. (P00001) |
| Specification Section 3.3 - Transmit Mode Select |
| Specification 3.3.1 - The transponder shall complete all Transmit Mode changes within 2 seconds from time of receipt of remote instruction from the Presentation Interface (PI). |
| Specification 3.3.2 - The transponder shall send status message indicating success or failure all Transmit Mode changes within 2.5 seconds from receipt of remote instruction from the Presentation Interface (PI). |
| Specification 3.3.3 - The transponder shall reply to all Transmit Mode queries within 500 milliseconds from receipt of remote instruction from the Presentation Interface (PI). |
| Specification 3.3.4 - The transponder shall allow the operator to configure Mode of Operation within 60 seconds using the MKD. |
| Specification 3.3.5 - The selected Transmit Mode shall be visible on the normal operation screen of the transponder display. |
| Specification 3.3.6 - The transponder will execute the necessary VDL reporting interval changes as specified in ITU-R M.1371-5 for all Transmit Mode changes. |
| Objective Requirement |
Specification 3.3.7 - For all successful Transmit Mode changes locally initiated using the MKD, the transponder shall send a status message indicating success to the PI within 500 miliseconds. (P00001)
| Specification Section 4 - NMEA Data Exchange |
| Specification 4.1 - The transponder shall exchange data with the Presentation Interface using IEC 61162-1 and 61162-2. |
| Specification 4.2 - The Transponder shall comply with Annex 3 of the EAIS IDD v5.5.3, with the following exceptions: (P00001) |
4.2.1 Transponder shall disregard the Message Selection and Asset Type fields for received messages.
4.2.2 Transponder shall use value of “<null>” for Message Selection and Asset Type fields for all response messages.
Objective Requirement Specification 4.3 - The transponder shall exchange data with the Presentation Interface using IEC 61162-3.
Objective Requirement Specification 4.4 - The transponder shall comply with Annex 4 of the EAIS IDD v5.5.3.
4.4.1 Transponder shall disregard the Encrypted Message Selection and Unit Type fields for received messages of PGN 065535. (P00001)
4.4.2 Transponder shall use value of “7” for Encrypted Message Selection field and “1023” for Unit Type field for all response messages of PGN 065535. (P00001) Objective Requirement Specification 4.5 - The transponder shall exchange data with the Presentation Interface using IEC 61162-450. (P00001)
| Specification Section 5 - Integration |
| Specification 5.1 - The transponder shall integrate with Presentation Interface (PI) applications. |
| Objective Requirement |
Specification 5.1.1 - The transponder shall allow PI applications to emulate the transponder’s user interface and controls.
| Specification 5.2 - The transponder shall be capable of processing AIS Message 17 DGPS corrections. |
| Objective Requirement |
Specification 5.2.1 - The transponder shall be capable of providing AIS Message 17 DGPS corrections to an external DGPS receiver using DGPS RTCM SC-104 format (commonly called “MSK”) via a serial port.
Objective Requirement Specification 5.3 - The transponder shall allow the user to filter Class B targets to prevent their transmission to the presentation interface.
| Specification Section 6 - Documentation/Manuals |
| Specification 6.1 - The contractor shall provide technical documentation describing installation, operation, data communication, and maintenance of the AIS-2 system that meets the requirements in Attachment 4 (TMCR) and Exhibit A (CDRLS). |
| Other information required in the Proposal Instructions: |
| Provide ability to deliver the items within the time frames listed in Section 1.6 (Required Delivery Times) of this Combined Synopsis/Solicitation. |
LOGISTICS PLAN
| TECHNICAL FACTOR / LOGISTICS PLAN | SOLICITATION#: | 70Z04418R18002300 | SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104 | ||
| CONTRACTOR'S NAME: | |||||
| REQUIREMENT | Contractor Proposal-Where requirement is addressed in proposal (Document Name, Page #, Paragraph) | ||||
| 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 over the duration of the awarded contract, plus the warranty duration for all items ordered. (Reference the Section 1.9, Logistics of the Combined Synopsis/Solicitation) | |||||
| Combined Synopsis/Solicition Section 1.9 - Logistics | |||||
| Combined Synopsis/Solicition Section 1.9.1 - |
The AIS-2 system components shall be available on the open market for the duration of the awarded contract, plus the warranty duration for all items ordered. Manufacturer upgrades to the components shall be backward compatible to ensure integrated operations are maintained.
Combined Synopsis/Solicition Section 1.9.2 - 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's placement on a USCG vessel.
| 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. |
| 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. |
| Identify if the Government will be provided rights in accordance with FAR 52.227-14, Rights in Data, to use manuals and other documentation provided as part of the system and the level of the Government’s right to use and supplement the information contained in the provided information. |
| Provide notification timelines as well as lead times for software updates, product/component end of life, and reparability support. |
| 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. |
| 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's placement 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. |
| Objective Requirement |
Provide historical data for component failure on, to allow the USCG to develop reliability centered preventative maintenance procedures.
Kotzun, Shandra J CIV:
Why would the USCG be coming up with a preventative maintenace procedure? Why would we accept components that don't work? Shouldn't the components not fail on the whole, with posisble rare exceptions?
WARRANTY
| TECHNICAL FACTOR / WARRANTY | SOLICITATION#: | 70Z04418R18002300 | SOURCE SELECTION INFORMATION – SEE FAR 2.101 and 3.104 | ||
| CONTRACTOR'S NAME: | |||||
| REQUIREMENT | Contractor Proposal-Where requirement is addressed in proposal (Document Name, Page #, Paragraph) | ||||
| Proposed warranty terms and conditions to include at a minimum: duration of the warranty(s), the offeror’s timeline and conditions for the commencement of the warranty period, and a description of the process and timelines for replacement and/or repair. | |||||
| Per Attachment 5, Warranty Terms and Conditions: |
The AIS-2 shall provide at a minimum a standard commercial warranty which commences date of acceptance.
The contractor’s proposed warranty period and terms/conditions shall be clearly articulated in the “Warranty Terms and Conditions Section” of their technical proposal.
Objective Requirement Standard commercial warranty, which commences upon installation of the system/component by approved dealer.
Objective Requirement Standard commercial warranty which commences upon installation of the system/component (regardless of installing activity).
Objective Requirement Standard commercial warranty which permits up to 12 months between acceptance and warranty period commencement.
Objective Requirement A 2 year, standard commercial warranty which commences date of AIS-2 installation. The AIS-2 shall be free from defects in materials and workmanship for no less than two (2) years from the date of acceptance.
Objective Requirement A 2 year, standard commercial warranty which commences date of AIS-2 installation. The AIS-2 shall be free from defects in materials and workmanship for no less than two (2) years from the date of installation.
Objective Requirement The Contractor shall arrange a resolution of a warranty claim within twenty-four (24) hours after receiving notification by the Coast Guard.
Objective Requirement The Contractor shall utilize replacement equipment rather than repaired for warranty resolution.
Objective Requirement If the Contractor utilizes repair for warranty resolution, repaired unit will be returned to the Coast Guard within 30 days of receipt.
Objective Requirement If the Contractor utilizes repair for warranty resolution, repaired unit will be returned to the Coast Guard within 45 days of receipt.
File details come from the government source that posted it.