EA-133F-RP-0008_Amendment_0003.pdf

Except as provided herein, all terms and conditions of the document referenced in item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. Name and Title of Signer (Type or Print) 16A. Name and title of Contracting Officer (Type or Print)

15B. Contractor/Offeror 15C. Date Signed 16B. United States of America

(Signature of Contracting Officer)

16C. Date Signed

(Signature of person authorized to sign)

NSN 7540-01-152-8070 30-105 STANDARD FORM 30 (REV. 10-83)

PREVIOUS EDITIONS UNUSABLE Prescribed by GSA FAR (48 CFR) 53.243

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

1. Contract ID Code Page of Pages 1 15

2. Amendment/Modification No. 3. Effective Date 4. Requisition/Purchase Req. No. 5. Project No. (if applicable) 0003 May 5, 2016

6. Issued By Code AJ930073 7. Administered By (If other than Item 6) Code

NOAA/EASTERN REGION ACQUISITION SEE BLOCK 6

DIVISION

200 GRANBY STREET

NORFOLK, VA 23510

CHRISTINE JEFFRIES 757-441-6894

8. Name and Address of Contractor (No., Street, County, and Zip Code) (X) 9A. Amendment of Solicitation No.

X

EA-133F-16-RP-0008

9B. Date (See Item 11) March 23, 2016 10A. Modification of Contract/Order No.

10B. Date (See Item 13)

Code Facility Code

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

X

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of Offers X is extended is not extended.

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

(a) By completing items 8 and 15, and returning 1 copy of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or telegram which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDG- MENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by telegram or letter, provided each telegram or letter makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

12. Accounting and Appropriation Data (if required)

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACT/ORDERS.

IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

(x) A. This change order is issued pursuant to: (Specify authority) The changes set forth in item 14 are made in the Contract Order No. in item 10A.

B. The above numbered Contract/Order is modified to reflect the administrative changes (such as changes in paying office, appropriation date, etc.)

Set fourth item 14, pursuant to the authority of FAR 43.103 (b)

C. This supplemental agreement is entered into pursuant to authority of:

D. Other (Specify type of modification and authority)

E. IMPORTANT: Contractor is not, is required to sign this document and return copies to the issuing office.

14. Description of Amendment/Modification (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

Vessel Monitoring System

See Continuation Sheet for a Complete Description of Changes

EA-133F-16-RP-0008, Amendment 0003, page 2 of 15 SF30 Continuation Sheet

a. Subject solicitation is hereby amended to make the following changes:

1. The Standard Form (SF) 1449 is changed to reflect the change to the due date and time for receipt of proposals to May 17, 2016 at 3:00 PM Eastern.

2. The Request for Proposals (RFP), Commerce Acquisition Regulation (CAR) provision 1352.215-70, Proposal Preparation, paragraph (b)(2)(iii)(A)(3), Technical Approach, has been modified to indicate that Offerors shall discuss compliance with Homeland Security Presidential Directive (HSPD) 12, Policy for a Common Identification Standard for Federal Employees and Contractors.

3. The RFP, CAR provision 1352.215-70, Proposal Preparation, paragraph E.3(b)(3) Price Proposal, has been modified to state that Offerors shall use an estimate of $8,000.00 per year for annual on-site training (line items 0005, 0010, 0015, 0020, and 0025).

4. The RFP, CAR provision 1352.215-70, Proposal Preparation, paragraph E.3(b)(3) Price Proposal, has been modified to state that Offerors shall use an estimate $18,000.00 per month for Satellite Communications Charges. The RFP, Attachment 2, Pricing Schedule, has been modified to change line items 0004, 0009, 0014, 0019, and 0024, Satellite Communications Charges to time-and-materials in lieu of firm-fixed-price.

5. The SOW, page 12, paragraph 8.3.1 has been revised to remove the reference to “sightings” within the mapping layers bullet.

6. The SOW, page 15, paragraph 8.3.1, Alerts, has been modified to state that alerts are required for stationary vessels, travel below a defined speed, and travel above a defined speed. The bullet pertaining to “Above Maximum Speed” has been deleted.

7. The SOW, page 17, paragraph 8.4.7 pertaining to latency has been deleted and annotated as “Reserved”.

8. The SOW, page 17, paragraph 8.4.9, has been modified to remove the link to an inaccessible web site.

9. The SOW, page 20, paragraph 9.0.7.b, the reference to Section B.4 is changed to 8.2.B.

10. The SOW, page 20, Paragraph 9.1 is modified to require that the Kick-Off Meeting is to be held within 10 business days after contract award or as agreed upon between the NOAA team and the Contractor.

11. The SOW, page 21, paragraph 9.1.3 has been revised to reflect a requirement to submit bi-weekly status reports and to participate in regularly scheduled meetings. SOW, Section 10, item 10.1.2.C is changed to reflect submission of a bi-weekly Status Report. Section 11 is changed to require that deviations from the approved PMP be reported in the bi-weekly Status Report.

EA-133F-16-RP-0008, Amendment 0003, page 3 of 15

12. The SOW, page 31, Section 11, has been modified to reflect the following Performance Standard for the Write Once, Run Everywhere Development Approach: “The contractor shall adopt a technology approach that allows for only one code base for the application.”

b. A conformed copy of the RFP, Attachment 1 SOW, and Attachment 2, Pricing Schedule, are provided herein.

c. Responses to questions received regarding the RFP are provided as follows:

1. QUESTION: What is the anticipated award date?

RESPONSE: The anticipated date of award is on or about July 15, 2016.

2. QUESTION: Section 8.2.A.5 Hardware and Materials – Is it expected that the award winner will maintain inventory and supply EMTU hardware, cabling and other materials?

RESPONSE: The approach to providing EMTU hardware, cabling, and other materials is within the Offeror’s discretion.

3. QUESTION: Section 8.3.1 – Graphical User Interface (GUI) 8th bullet regarding divisional scenarios– Could NOAA please clarify what is meant by 5 divisional scenarios?

RESPONSE: Each of the five OLE divisions has a monitoring center. The technicians in each monitoring center should only be able to see their own regional/divisional scenario.

Headquarters and some other users will need access to all scenarios. The scenarios are Northeast, Southeast, West Coast, Alaska, and the Pacific Islands.

4. QUESTION: Section 8.3.1 – Graphical User Interface (GUI), (• The following actions must be available to high-level users) (o Change Logging Rate o Request Log Download):

Does NOAA have API’s available for changing logging rates and downloading log files?

RESPONSE: No.

5. QUESTION: Section 8.3.1 – Reports and Data Queries – 5th bullet: (Non-Reporting (silent vessel) list which allows for region-specific data entry). Can NOAA please clarify what the desired functionality of this feature request?

RESPONSE: Silent vessels are units that are not responding but are required to do so.

When the report is viewed, the technician can contact the vessel operator to find out why it is not reporting as required.

6. QUESTION: Section 8.3.1 – Alerts (• Filters for the following conditions must be available), “Permit”. Could NOAA please clarify if the desired functionality is to have permit data is accessible within the VMS?

RESPONSE: Yes. Based on permit information entered into the application, a filter must be available “by permit”.

7. QUESTION: Section 8.4.9 – The Google weblink listed: Security web sites (https://sites.google.com/a/noaa.gov/noaa-itsc/) requires a login. Can NOAA please provide login access?

EA-133F-16-RP-0008, Amendment 0003, page 4 of 15

RESPONSE: Login access will be provided after contract award. Information pertaining to NIST IT Security Standards is available at http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf.

8. QUESTION: With which entity does the EMTU satellite airtime responsibilities fall to?

Is it the EMTU suppliers or the award winner for the VMS program?

RESPONSE: The VMS contractor is responsible for securing the airtime used by NOAA.

9. QUESTION: Sections 9.3, 9.3.1 and 9.3.2 refer to System design, configuration, construction plans and Gap Analysis. Could NOAA please clarify the Timing of these deliverables? Does the eight-month transition period (referenced in Section 3.1) suggest that the software development and customization will take place post award and following the Gap Analysis with NOAA SMEs. In other words, the COTS software upon award will be the baseline and will be enhanced and refined and implemented over the 8-month transition timeframe following consultation with NOAA SMEs and Gap analysis. Therefore it is not the expectation of NOAA that the software is ready at the time of the award. Please clarify.

RESPONSE: The 8-month transition period is intended for software configuration;

deployment including training, outreach, and support; and testing. Refer also to paragraph

8.6 of the Statement of Work (SOW).

10. QUESTION: Firm-fixed satellite comms charges for all EMTUs. In order to provide a quotation, we need to know how many of each type and frequency of reporting. Is this what is required?

RESPONSE: The RFP, Attachment 2, Pricing Schedule, has been modified to change line items 0004, 0009, 0014, 0019, and 0024, Satellite Communications Charges, to time-and-materials in lieu of firm-fixed-price. RFP, CAR provision 1352.215-70, Proposal Preparation, paragraph E.3(b)(3) Price Proposal, has been modified to state that Offerors shall use an estimate of $18,000.00 per month for Satellite Communications Charges.

11. QUESTION: Type approval testing – do we need to cover third party testing & test house or is this in the estimates provided on P.27 of Terms & Conditions?

RESPONSE: This is not included in the estimates provided on page 27 of the Request for Proposals (RFP). This work is accomplished through the work order process as part of the Operations and Maintenance line items. For estimating purposes, assume there will be a maximum of 4 type approval testing situations per year.

12. QUESTION: SOW, page 20, paragraph 7.b includes a reference to Section B.4 - can you please explain?

RESPONSE: Within the SOW, page 20, paragraph 9.0.7.b, the reference to Section B.4 is changed to 8.2.B

13. QUESTION: SOW, Section 9.1 states 5 business days after contract award whereas the task deliverables state 10 business days. Which is correct?

RESPONSE: : Paragraph 9.1 is modified to require that the Kick-Off Meeting is to be held within 10 business days after contract award or as agreed upon between the NOAA team and the Contractor.

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

EA-133F-16-RP-0008, Amendment 0003, page 5 of 15

14. QUESTION: SOW, page 31 states bi-weekly progress report whereas 9.1.2 states monthly (along with a bi-monthly status meeting). Which is correct?

RESPONSE: The SOW, page 21, paragraph 9.1.3 has been revised to reflect a requirement to submit bi-weekly status reports and to participate in regularly scheduled meetings. The SOW, Section 10, item 10.1.2.C is changed to reflect submission of a bi-weekly Status Report. Section 11 is changed to require that deviations from the approved PMP be reported in the bi-weekly Status Report.

15. QUESTION: Pricing Schedule, can you please confirm the meaning of the acronyms:

LO, MO, JB, EA.

RESPONSE: The full meaning of each acronym follows: LO: Lot, MO: Month, JB: Job, and EA: Each.

16. QUESTION: If a consortium wishes to bid for this RFP, how do they proceed?

RESPONSE: The consortium would submit the offer in its own name.

17. QUESTION: In section 8.6 of the SOW you write that NOAA wants a COTS vessel monitoring system, in section 11 you write that you want to own the code for the application, do you want to own the codebase for the entire COTS product or only parts of the application, if you only want to own parts please specify which parts you want to own.

RESPONSE: NOAA will not own the code for the application. Section 11 of the SOW has been modified to reflect the following performance standard for the Write Once, Run Everywhere Development Approach: “The contractor shall adopt a technology approach that allows for only one code base for the application.”

18. QUESTION: If you want to own the code base, do you intend that NOAA in the future will develop and maintain the code without the Contractor.

RESPONSE: NOAA will not own the code for the application. Reference Question #17 above.

19. QUESTION: In attachment 2 “Pricing schedule”, please explain the acronym’s in the column "Unit of issue".

RESPONSE: Reference Question #15 above.

20. QUESTION: Is there a standard API interface for interaction and data connectivity with all VMS EMTU vendors?

RESPONSE: No, not at this time.

21. QUESTION: How does the incumbent connect today to all VMS EMTU suppliers?

RESPONSE: The incumbent contractor’s technical processes will not be identified.

22. QUESTIONS: Section 8.3.1

a. Can NOAA explain what they mean by “Customized Menu Options”?

RESPONSE: Examples of customized menu options include, but are not limited to: user-created groups and any user-chosen color options.

EA-133F-16-RP-0008, Amendment 0003, page 6 of 15

b. How many different types of users are there for documentation purposes?

RESPONSE: Five.

23. QUESTIONS: Section 8.3.1 – Basic Software Requirements

a. Define what is required for a “user indicator with the system is processing information.

Does this require a rotating timer or equivalent icon? Will having a refresh button or a message indicating “applying updates” suffice?

RESPONSE: The intent is for the system to indicate that it is still processing rather than timed out. The manner in which that is accomplished is at the discretion of the Offeror.

b. Will ship summary suffice for a “trip generator”? What are the most critical trip generator requirements? What is the definition of “trip stitching”?

RESPONSE: The requirements for Trip Generation are included in Appendix B of the SOW. Reference pages 37 and 38 of the SOW.

24. QUESTIONS: Section 8.3.1 - Mapping

a. Need full specifications for “NMFS Statistical Areas”. Clarify what is meant by “capability of entering NMFS statistical areas”? Is this intended as an overlay onto the map display?

RESPONSE:. The intent is for NMFS closed and sensitive areas to be shown on the GUI and to be interactive; e.g. ping rate may need to increase if a vessel enters the area, or an alert may be required if a vessel enters or takes certain action in an area. Also, certain user levels should be able to maintain various area files or map overlays. This could be accomplished with an overlay; however, the method for meeting this requirement is left to the Contractor’s discretion.

b. What specific mapping software needs to be exported and viewed? (SOW gave examples for Google Earth (.kml) and ArcGIS (.shp or “shape file”), .gpx.

RESPONSE: The data needs to be able to be exported and viewed in other mapping software, such as those identified.

c. Are Transas Navigational Maps acceptable for "Raster Navigation Charts"?

RESPONSE: NOAA electronic charts are required as an available overlay (SOW, page 11). The method for meeting this requirement is left to the Contractor’s discretion.

d. Is "pan" sub-feature an absolute requirement? Does this imply the need for 3D mapping capability? Describe how panning would work on a 2 dimensional map.

RESPONSE: Panning is an absolute requirement. It includes, but may not be limited to, clicking and dragging the map to reposition the current view, whether in 2D or 3D.

25. QUESTIONS: Section 8.3.1 – Area Shape Files and Geofences

a. How will customized colors for areas or groups of areas be used? Provide use case scenarios. Is using color coding for geofencing sufficient?

RESPONSE: Color coding is used for closed/sensitive areas and other management requirements, not for transit areas. Some areas are ok to transit through while others are not, EA-133F-16-RP-0008, Amendment 0003, page 7 of 15 and some entries into areas are ok for one type of fishery, but not for another. Color coding assists end users in determining possible incursions.

26. QUESTIONS: Section 8.3.1 – Electronic Forms

a. What specific forms and formats are being transmitted? How many different types of forms are received? How many forms are received in a 24 hour period?

RESPONSE: Transmitted forms are in XML format and consist of vessel declarations, pre-landing information, catch reports, and other fishery related data. The number of forms sent in any 24-hour period varies significantly.

b. Could we obtain list and examples for each type of form which is received by NOAA?

RESPONSE: This information is not available at this time.

c. What are the requirements for parsing form data?

RESPONSE: Currently some form data is parsed, some is left in the raw XML form.

Parsing will be set-up post-award.

27. QUESTIONS: Section 8.3.1 – Map Layers

a. What is meant by “sightings”?

RESPONSE: The reference to “sightings” on page 12 of the SOW has been removed.

b. What is the width specification for the “ellipse”?

RESPONSE: The width is the possible distance-traveled for the given vessel traveling at the average speed between the two selected position reports.

28. QUESTIONS: Section 8.3.1 – GUI

a. What customized menu options need to be saved? Is this by group or by individual user? Are permissions and user groups sufficient or are customized views per individual user required?

RESPONSE: The customized menu options that will be able to be saved are at the discretion of the Offeror.

b. What are the differences in views required for the 5 divisional scenarios?

RESPONSE: Reference Question #3 above.

c. Where will user defined colors be used?

RESPONSE: Where user defined colors will be used is determined by the user.

d. Is an intuitively designed UI acceptable in lieu of online manuals and help guides?

RESPONSE: The SOW, page 13, requires that the GUI include a Help Menu to include user and administrator manuals, and other OLE documents which may be added by authorized OLE personnel. This requirement remains unchanged.

e. What specific menu options need to be adapted by group?

RESPONSE: This is dependent on the Offeror’s approach to fulfilling the requirements of the SOW.

EA-133F-16-RP-0008, Amendment 0003, page 8 of 15

29. QUESTIONS: Section 8.3.1 – Messages

a. How are Canadian Herring Transshipment vessel messages different vs. any other transmitted message? What is the format required? Who sends and who receives these messages?

RESPONSE: These messages are sent to a third party in XML format by our Northeast monitoring center. XML data are also received by our Northeast monitoring center.

30. QUESTIONS: Section 8.3.1 – Reports and Data Queries

a. For each report required (i.e., Vessel Information customized by division, SED Gulf Pre-landing, SED HMS Pre-Landing, Silent Vessels, FMC Out, NED and NWD View Declarations, Hourly position data flow analysis, Master Data report, Active Flag Status.), clarification is needed regarding required information for each listed report.

RESPONSE: Detailed requirements for these reports will be provided after award.

b. What “built-in” reports are used?

RESPONSE: An example of built-in and customized divisional reports is provided at Appendix A, page 33, of the SOW.

c. What types of “customized divisional reports” are typically required? Provide examples.

RESPONSE: An example of built-in and customized divisional reports is provided at Appendix A, page 33, of the SOW.

d. How much data must be retained / accessed for historical reporting (i.e., # of months/years)?

RESPONSE: Data retention is the responsibility of the Government.

e. What “External Data Systems” are required for interaction?

RESPONSE: Data are transmitted primarily to partner-agency databases as a database-to-database feed.

f. How many customized queries must be saved? (maximum per user) RESPONSE: This is dependent on the Offeror’s approach to fulfilling the requirements of the SOW.

g. What types of vessel information is customized for divisional custom reporting?

RESPONSE: There is insufficient information provided to address the question.

31. QUESTIONS: Section 8.3.1 – System Interoperability

a. Explanation of the NMFS systems and databases accessed for data inputs.

RESPONSE: NMFS systems include, but may not be limited to, the Northeast Days at Sea program and Sector vessel information, which are updated via Open Database Connectivity (ODBC).

b. What are the 3rd party systems or databases (including regional) inputs accessed?

EA-133F-16-RP-0008, Amendment 0003, page 9 of 15

RESPONSE: No third party systems or databases currently ingest data; however, the SOW, page 14, requires this functionality.

c. What other “communication mechanisms” are required?

RESPONSE: The acceptance of EMTU data from new communication service providers.

d. How would data from other systems be displayed on the map?

RESPONSE: Data from other systems are kept in a table and displayed as any other data, e.g., speed, course, location, and vessel name.

32. QUESTIONS: Section 8.3.1 – Alerts

a. Speed - Is showing actual vessel speed sufficient, or do parameters need to be set up for Stationary, Low, High, Above Maximum Speed?

RESPONSE: Alerts are required for stationary vessels, travel below a defined speed, and travel above a defined speed. The bullet pertaining to “Above Maximum Speed” has been deleted.

b. What is definition of "activity declaration" alert?

RESPONSE: The intent is for the user to be able to set up an alert for particular fishing declarations made by the vessel operator.

c. What are the “other Unit Status indicators sent from the EMTUs”?

RESPONSE: EMTUs send unit status codes (e.g. power up or antenna block). An alert is to be available for each of the status indicators received by the system.

d. What is meant by “within Zone” alert? Is this triggered by amount of time spent in the zone?

RESPONSE: A within Zone alert is an alert for all position reports generated within the zone.

e. What types of permits are required for filtering?

RESPONSE: Fishing permits.

33. QUESTIONS: Section 8.3.1 – Security

a. What are the security requirements/protocols for transfer of date from the land earth stations/gateways?

RESPONSE: Data must be sent via secure communication and not in plain text. See 50

CFR 600.1505-1507.

b. What are the security requirements/protocols for forwarding data to 3rd party systems?

RESPONSE: There is an established data request and approval process that 3rd party systems and users are required to follow. Approved data requests are forwarded to the vendors to implement.

34. QUESTION: Section 8.3.1 – Administration

EA-133F-16-RP-0008, Amendment 0003, page 10 of 15

a. How many user roles are required? What are the differences in rights, access for each role?

RESPONSE: Reference Question #22b above. The Government will furnish differences in access rights after award.

35. QUESTIONS: Section 8.3.1 – NAFO Support

a. What are the specific encryption protocols required for sending electronic reports to

NAFO?

RESPONSE: Current NAFO data is sent using https protocol.

b. What are the details regarding the 2 reports send to the Secretariat prior to the start of the NAFO season?

RESPONSE: Reference the SOW, Appendix C, page 40.

c. What are the formats for sending unit failed messages from the vessel operator to the

FMC?

RESPONSE: There is no specified format.

36. QUESTIONS: Section 8.3.1 – Application Hosting

a. What are the specific latency requirements?

RESPONSE: SOW, paragraph 8.4.7 has been deleted and annotated as Reserved.

b. What are the data mining/analysis requirements?

RESPONSE: Data mining requirements are not fully developed at this time.

c. What is the NMFS OCIO change control process?

RESPONSE: Reference the SOW, page 41 Appendix D.

d. What are the NOAA and NMFS IT security guidelines and the NIST IT security standards?

RESPONSE: For NIST guidance, refer to the link below to NIST 800-53 rev4.

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf.

e. What are the Homeland Security Presidential Directive requirements?

RESPONSE: Refer to the link below for additional information on HSPD-12.

http://www.osec.doc.gov/osy/hspd-12/hspd-12information.html

f. What IT security artifacts are required by NMFS IT security?

RESPONSE: Documentation requirements will vary based on the solution offered.

g. What are the National Archives and Records Administration records retention schedules?

RESPONSE: These requirements are the responsibility of the Government. The Contractor shall not cause data or records to be deleted or removed from access.

http://nvlpubs.nist.gov/nistpubs/SpecialPublications/NIST.SP.800-53r4.pdf

EA-133F-16-RP-0008, Amendment 0003, page 11 of 15

37. QUESTION: Why is NOAA going out to competitive bid for a possible new VMS vendor when they already have vTrack in place? Is NOAA satisfied with the current vTrack system?

RESPONSE: This is a follow-on requirement. 41 U.S.C. 3301 requires executive agencies to obtain full and open competition through the use of competitive procedures in accordance with the U.S.C. and the Federal Acquisition Regulation (FAR).

38. QUESTION: Does NOAA know how many different teams or physical sites have been identified for training? At a minimum, do we take a train the trainer approach at one or possibly more than one site?

RESPONSE: The Government anticipates once-per-year on-site training of approximately 15 OLE/OCIO personnel.

39. QUESTION: What percentage of the work does NOAA anticipate will occur at NOAA headquarters and Regional Offices vs. the Contractor facility? Does NOAA have any specific time requirements per activity for onsite support?

RESPONSE: This will vary based on the solution offered.

40. QUESTION: Section 8.0 - Billing/Invoice, Does the billing process of Contractor include direct invoicing/accounts receiving to vessel operator or will Contractor only invoice NOAA for all services and support based on Work Order?

RESPONSE: It is anticipated that the Contractor will be billed by their subcontractors, and the Contractor will in-turn bill NOAA for all services and materials provided.

41. QUESTION: Section 8.2.A.4 - Support Metrics, Can NOAA provide any metrics on current VMS support operations? Daily call volumes, Electronic tickets, time to resolution, requests by OLE, etc. This will assist in more accurately pricing the support role function to meet requirements.

RESPONSE: This information is not available.

42. QUESTION: Section 8.2.A.4.e - Operator Contact

a. Is it Contractor’s responsibility to contact vessel operator directly with requests for vessel/owner/operator identification and information?

RESPONSE: No. It is the vessel-operator’s regulatory/permit responsibility to properly report all information to OLE.

b. If yes, how would contractor obtain contact information and which party maintains that data?

RESPONSE: Refer to Question #42.a. above.

43. QUESTION: Section 8.2.A.5 - Hardware and Materials, This section implies that an inventory system will be Contractor's responsibility.

a. Is there an inventory minimum threshold that NOAA will set?

RESPONSE: Refer to Question #2 above.

EA-133F-16-RP-0008, Amendment 0003, page 12 of 15

b. In case Operator cannot self-install equipment properly, will a work order be provided for Contractor to perform these duties?

RESPONSE: No. Operator should not self-install. Operators should secure the services of their local marine electronics dealer.

44. QUESTION: Section 8.2 - Electronic Ticket System, Will Contractor have direct access to the electronic ticket system and if so to what level of administration (add, changes, deletes, search, reports)?

RESPONSE: No.

45. QUESTION: Section 8.2.B.5 – Reporting, What is the media for responses to the an intended resolution of an exigent situation?

RESPONSE: The media is the work order system (currently, iSupport) via email.

46. QUESTION: 8.3.1 Specific Software Requirements - Will NOAA provide approved EEZ, state and all other regional GIS boundary data?

RESPONSE: Yes.

47. QUESTION: Browser Version Control

a. Software Solution is stated to be accessible from iOS, Android, and standard web browsers (IE, Chrome, and Firefox). Will there be a minimum version of each of these browsers that is to be supported by the Contractor?

RESPONSE: Yes, application should support browsers that are at least 2 versions behind the latest general release. If applicable, the requirement also applies for Java.

b. If yes, can NOAA designate a technical requirement that Contractor maintains a compatibility matrix with current supported versions and future planned unsupported versions? NOAA would need to designate an approval function for this matrix and a process of dissemination to the user base of this matrix.

RESPONSE: Refer to Question #47.a. above.

48. QUESTION: Section 6.0 - The VMS program will support the day-to-day vessel monitoring activities of law enforcement organizations. Do all of these government organizations have the same requirements?

RESPONSE: The VMS Program supports the day-to-day vessel monitoring activities of the NMFS Office of Law Enforcement. We share this information with other agencies, but the only requirements for the system are those established by OLE.

49. QUESTION: 9.3.2 Conduct Gap Analysis - Will the Gap analysis SMEs include possible requirements from all of the government organizations using the NOAA VMS including:

NOAA NMFS OCIO, US Coast Guard; Joint Enforcement Agreement State partners (JEA), NMFS General Counsel, NMFS Science Centers and NMFS Regional Officers, to support both enforcement/compliance needs as well as data collection/management/scientific needs?

RESPONSE: All requirements are included in the SOW. No other agency/organization will need to be consulted.

EA-133F-16-RP-0008, Amendment 0003, page 13 of 15

50. QUESTION: 8.3 Satellite Software and Systems Integration - Vessel position and other message data from the current system (vTrack) must be migrated to the proposed system.

Please define the size, extent, and quality of archival vTrack data.

RESPONSE:

Size of the VMS database is: ~ 1TB Annual average growth of data: ~50 GB per year Quality of archival data: In good state Backups: Incremental and Full

51. QUESTION: 9.0 Specific Mandatory Tasks and Associated Deliverables - Does NOAA have any preferences or regional requirements for the following vendors?

• FW Telematics

• Boatracs

• SkyMate

• CLS America

• Network Innovations RESPONSE: No.

52. QUESTION: 8.3.1 Specific Software Requirements - Could NOAA please provide examples of the following reports or other VMS reports:

Vessel information customized by Division SED Gulf Pre-Landing SED HMS Pre-Landing Silent Vessels FMC Out NED and NWD View Declarations Hourly position data flow analysis (by date/vendor/fishery) Master Data Report Active flag status

RESPONSE: The forms contain confidential vessel information and cannot be shared.

53. QUESTIONS: Section 8.4 - Hosting Alternatives Alternative 1

a. What level of physical access will Contractor have to NOAA owned data center?

RESPONSE: They can be escorted into the data center at any time. There are also levels of virtual access.

b. For travel purposes, what is the reimbursement schedule for an onsite visit?

RESPONSE: There is no reimbursement for the contractor’s efforts to resolve or maintain their product/services. In some cases, government-requested visits that are not due to any fault of the Contractor, may be reimbursable.

c. Would this be handled through a Work Order for Standard and Emergency situations?

RESPONSE: Travel reimbursement will not be handled through the work order system.

EA-133F-16-RP-0008, Amendment 0003, page 14 of 15

d. Since hardware is residing in NOAA datacenter, will NOAA procure required hardware and operating system software for software solution at no cost to Contractor?

RESPONSE: Yes.

e. If Yes, what is the change protocol to request additional equipment as the new functionality is added?

RESPONSE: Reference the SOW, page 41, Appendix D.

Alternative 2

f. Please verify if this will include the ability to engage Amazon GovCloud Services.

RESPONSE: Yes.

54. QUESTIONS: Section 8.5.2 - Travel and Schedule

a. For travel purposes, what is the reimbursement schedule for annual training?

RESPONSE: CAR provision 1352.215-70, Proposal Preparation, paragraph E.3(b)(3) Price Proposal, has been modified to state that Offerors shall use an estimate of $8,000.00 per year for annual on-site training.

b. Is Contractor responsible for date proposal and approval by a NOAA representative for actual training?

RESPONSE: Yes.

55. QUESTIONS: 8.6 Transition: Design, Development, Deployment, and Testing

a. Does NOAA anticipate that the rollout be maintained concurrent with the current vTrack system?

RESPONSE: Yes, during the development and testing phases of the implementation process.

b. At what point is vTrack taken offline and replaced with the new system?

RESPONSE: After the new system has passed all testing cycles in the development and testing phases, to include user acceptance testing. Reference sections 8.6, 9.3, 9.4 and 9.5 of the SOW. The contractor will work with NOAA OLE to develop a release schedule.

c. Can the NOAA Data Center currently accommodate two systems during rollout?

RESPONSE: Yes.

56. QUESTIONS:

a. What success criteria is outlayed for adoption of the new solution for users? I.e. when is a network wide adoption considered complete?

RESPONSE: The new solution is considered accepted when it has passed user acceptance testing and has deployed into production after review through the change management process.

b. Based on Phased information, there is 5 months to complete Phases 1-3. What is the control mechanism of this timeline and any delays that may occur outside of Contractor

EA-133F-16-RP-0008, Amendment 0003, page 15 of 15 control? example - NOAA datacenter equipment is not available to install software on, which is on the critical path to complete the phase.

RESPONSE: The Contractor will not be liable for delays caused by the Government.

c. If schedule is not met due to Contractor originated delays, what is the recourse schedule?

RESPONSE: The Government reserves the right to invoke contractual remedies for Contractor-originated delays. Reference the full text of FAR clause 52.212-4 I, Contract Terms and Conditions – Commercial Items, which is available at www.acquisition.gov/far/.

57. QUESTION: Section 9.0 - Accounts Payable, Please verify if Contractor is directly responsible for accounts payable to type-approved vendor? Section specifies reporting deliverables only of vendor related costs.

RESPONSE: There is insufficient information provided to address the question. The SOW does not reference Accounts Payable.

58. QUESTION: Section 9.0.3 - VMS Vendor Type, Will Contractor be granted ability to submit to become a type-approved VMS vendor?

RESPONSE: Yes, however any request for type approval from the VMS Contractor will be subject to an organizational conflict of interest review.

59. QUESTION: Section 11.0 -

a. Write Once, Run Everywhere Development Approach : Under Performance Standard, there is a reference that NOAA would own the code base. Please clarify if NOAA is to own the software code for the new VMS system.

RESPONSE: Reference Question #17 above.

b. Agile Development: Is NOAA intending on assigning a representative to attend the Sprint Planning, Demo, and Retrospective meetings to allow for timely releases and consistent team dynamics? If so would that representative be a participant in Daily Scrum activities?

RESPONSE: Yes, NOAA anticipates having representation in development.

60. QUESTION: Section 9.0 Sub 2, Are there vendors that are being reviewed to be type-approved and anticipated to be added to the list prior to completion of the contract.

RESPONSE: No, no new vendors are being considered for type-approval at this time.

61. QUESTION: SOW Section 9.0 Sub 3, Will the data from the type-approved vendor list be supplied by NOAA or be considered part of the cost of this proposal?

RESPONSE: Contact information for type-approved vendors will be made available after award. The technical requirements to interface with the type-approved vendors are the responsibility of the Contractor.

d. All other terms and conditions remain unchanged.

NOTE: Offerors are reminded of the requirement to acknowledge this Amendment.

http://www.acquisition.gov/far/