SF30_Continuation_Page_A005.docx

I. SOLICITATION CHANGES

1. Section B, CLINs 0001, 0002 and 0003 have been modified to reflect the server being priced separately from the software.

2. Section B, CLINs 0013, 0014 and 0015 have been added to reflect the non-mandatory software functionality (reference the answer to number one below under the further clarifications, and the new Attachment 6).

3. Section C, Paragraph C.1 has been modified to reflect the requirement for a PTL software application only and the hardware platform being provided as government furnished equipment (GFE).

4. Section C, Paragraph C.4 has been amended to included two new subparagraphs C.4.1 PTL Server (Optional), and C.4.2 PTL Software.

5. Section C, Paragraph C.5.1.4. The phrase "from capable trackers." is hereby deleted and the following is substituted in lieu thereof, "in the web interface for each tracking device."

6. Section C, Paragraph C.5.1.14. The last sentence is hereby changed to read as follows, "This configuration shall include remotely changing the reporting rate of each tracking device."

7. Section C, Paragraph C.5.1.16. The following has been added as a new sentence, "If configured, when a tracking device enters or exits the Geofence , the PTL System's web interface shall provide an audio and visual warning to those users with the viewing permissions for that device." The word "activates" in the second sentence is hereby changed to "alarms."

8. Section C, Paragraph C.5.1.18. The following sentence is hereby deleted, "When the Geofence for any device activates, the PTL System's web interface shall provide an audio and visual warning to those users with the viewing permissions for that device."

9. Section C, Paragraph C.5.1.20 is hereby deleted in its entirety and the remaining paragraph are renumbered accordingly.

10. Section C, Paragraph C.5.1.32 is hereby deleted in its entirety and the remaining paragraph are renumbered accordingly.

11. Section C, Paragraph C.5.2.1. The following has been added to the end of the paragraph, "This data will include the following device information: device ID, device model, alias/call-sign, last reported latitude/longitude, last reported MGRS, last reported time, emergency status, and brevity code" and that last sentence has been modified to read as follows, "If the external viewing application supports the ability to display speed and direction this data also shall be provided to the external viewing application."

12. Section C, Paragraph C.5.2.2. The first sentence has been deleted in its entirety.

13. Section C, Paragraph C.5.2.3. The phrase "and or develop" is hereby deleted from the sentence.

14. Section C, Paragraph C.5.4.5 is hereby deleted in its entirety.

15. Section C, Paragraph C.5.4.6 is hereby deleted in its entirety and the following paragraphs have been renumbered accordingly.

16. Section F, Paragraph F.4 titled "Deliverables" is hereby amended to reflect the changes to the PWS reflected in this amendment.

17. Section I, Subparagraphs I.2.1 titled "Ordering" has been amended to reflect its application to CLIN 0008 only.

18. Section I, Subparagraphs I.2.2 titled "Ordering Limitation" and I.2.3 titled "Indefinite Quantity" are hereby deleted in their entirety.

19. Section L, the contents of Paragraph L.18.2 titled, "Technical Proficiency" are hereby deleted in their entirety and a new requirements have been added.

20. Section L, a new Paragraph L.18.3 titled, "Requirements Matrix" is hereby added and the remaining paragraphs have been renumbered accordingly..

II. AMENDMENT INSTRUCTIONS

1. Delete the document titled "Solicitation PTL System A004" released November 28, 2012 in its entirety and substituted the attached "Solicitation PTL System A005" in lieu thereof.

2. A new Attachment 6 titled "PTL Requirements Matrix" is hereby added.

III. FURTHER CLARIFICATIONS

1. Regarding the response to Question 43 in Amendment 0004. If all functions are NOT built into the system will we be considered “non-responsive”. Does our offering really have to meet 100% of all requirements listed in section C from day one, out-of-the-box?

Answer: Section M, Paragraph M.3 titled Basis for Award states "It is the Government’s goal to obtain a ready to deploy solution meeting the maximum number of Section C requirements and possesses an existing authorized to operate (ATO). Therefore the best value-tradeoff source selection process will include an evaluation of a proposed solution with an existing ATO which indicates the solution meets minimum government information assurance standards in accordance with NIST or DIACAP standards."

Attachment 6 PTL Requirements Summary provides a listing of the functional requirements enumerated in Section C and provides clarification to which specific requirements are "Mandatory" and which are "Optional." Mandatory functional requirements are required at the time of contract award, and Optional functional requirements must be incorporated into the PTL application during the performance of the contract.

2. Requirements C.5.1.1, C.5.1.2, C.5.1.1.26, C.5.1.1.27, and C.5.2.2 seem to refer to TWO separate applications, one a “built-in web viewer” and one an “external viewing application”, presumably a desktop tool. Is that correct? Are we to deliver TWO applications?

Answer: The requirements enumerated in Section C, Paragraphs C.5.1.1, C.5.1.2, C.5.1.1.26, C.5.1.1.27, and C.5.2.2 are separate capabilities. 1) web-based viewing on the server and 2) ability to use external viewing applications hosted locally on DOS desktop tool. The external viewing application is not intended as a development effort. Rather, the vendor should state which commonly used, tracking data external viewing applications are compatible with the vendor’s tracking server. The external viewing application shall be a ubiquitous third-party COTS geospatial product. Examples of external viewing applications have been provided, such as Google Earth or ESRI’s products.

3. Related to question 2) above and the response to Question 8 in Amendment 0004. Please confirm if Rich Internet Application products such as Flash, WPF are acceptable web interface technology?

Answer: Rich Internet Application (RIA) products (i.e., Flash, WPF) would only be acceptable for a built-in map viewer, but not the entire web application. The government desires HTML/CSS/Javascript for multiple reasons, among them: RIA products can introduce 0-Day vulnerabilities and introduce additional constraints, such as code-signing, that can make the Department's internal approval process much lengthier. The prohibition on RIA makes allowance for the built-in web viewer’s map only, with the rest of the built-in web viewer on the server being RIA-free. The vendor is only responsible for providing a built-in web viewer, and should provide a system capable of sending data to multiple, different, pre-existing geospatial presentation platforms; examples provided.

4. Is a COTS solution that meets all the requirements of the RFP and offers significant cost savings in terms of high side implementation, accreditation and operational compatibility, as well as provide an effective method to export to and be compatible with existing Oracle based systems an acceptable solution? Otherwise, the Government could be limiting its advantage of having competitive alternatives proposed under this RFP.

Answer: Proposed COTS solutions will be considered and evaluated in accordance with Section M, Paragraphs M.3 and M.4.