W911SD-18-R-0008-0001.pdf

MICC - WEST POINT PCO

681 HARDEE PLACE

PH: 845-938-4490

MAUREEN.A.FLANAGAN2.CIV@MAIL.MIL

WEST POINT NY 10996

0011266145

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

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)

30-105-04EXCEPTION TO SF 30

APPROVED BY OIRM 11-84

STANDARD FORM 30 (Rev. 10-83) Prescribed by GSA

FAR (48 CFR) 53.243

THE PURPOSE OF THIS AMENDMENT IS TO ANNOTATE RFI RESULTS. SEE SECTION SF30 BLOK 14 CONTINUATION PAGE

1. CONTRACT ID CODE PAGE OF PAGES

J 1 5

16A. NAME AND TITLE OF CONTRACTING OFFICER (Type or print)

16C. DATE SIGNED

BY 14-Feb-2019

16B. UNITED STATES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signature of Contracting Officer)(Signature of person authorized to sign)

8. NAME AND ADDRESS OF CONTRACTOR (No., Street, County, State and Zip Code) X W911SD19R0008

X 9B. DATED (SEE ITEM 11)

31-Jan-2019

10B. DATED (SEE ITEM 13)

9A. AMENDMENT OF SOLICITATION NO.

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 Offer is extended, X is not extended.

Offer 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 copies 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 ACKNOWLEDGMENT 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 CONTRACTS/ORDERS.

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

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 FORTH IN 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.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If applicable)

6. ISSUED BY

3. EFFECTIVE DATE

14-Feb-2019

CODE

MICC - WEST POINT

681 HARDEE PLACE

WEST POINT NY 10996-1514

W911SD 7. ADMINISTERED BY (If other than item 6)

4. REQUISITION/PURCHASE REQ. NO.

CODE W911SD

FACILITY CODECODE

EMAIL:TEL:

W911SD19R0008

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 30 - BLOCK 14 CONTINUATION PAGE

The following have been added by full text:

RFI'S

REQUEST FOR INFORMATION – RFI

Submtted on Tue 2/12/2019 2:23 PM

Q ‐1‐ Would FEDRAMP Tailored Authorization suffice?

A – 1 ‐The certification would be for the specific application/service the vendor is providing and must encompass all components of that.

Q ‐ 2‐ Will West Point absorb the cost of FEDRAMP Certification? –

A ‐ ‐2 ‐No.

Submtted on Thu 2/14/2019 8:49 AM

Q‐1: Is there a budget for this job?

A‐1: Bid accordingly‐ lowest price technically acceptable

Q‐2: Would a flat rate for access be acceptable? Opposed to the per user annual cost?

A‐2: Flat rate would be acceptable; numbers of users were included to give potential vendors an idea of how many users there may be and to plan accordingly

Q‐3: Will the bid be accepted for testing if the security criteria is, "in progress" of getting accepted?

A‐3: As laid out in the PWS #5, "Within 180 days of award (phase II), the vendor must have FEDRAMP level 1 certification application submitted for this app and within 270 days of award be on the DISA certified list of applications." If this is not met, the government may terminate the contract.

Q‐4: Could the app be hosted directly on the USMA servers?

A‐4: No. USMA is not the contracting entity. This will be between US Army Garrison West Point and the selected vendor. This application is intended to be hosted by the vendor on hardware that is secured in accordance with the PWS.

SUBMITTED ON Thu 2/14/2019 12:06 PM

Q‐1‐ At what date do the system have to be delivered? Is the 1st of April a hard requirement or can we deliver, for instance during Q2 of 2019?

A‐1‐ delivery date is 04/01/19

Q‐2‐ The procurement specification mention Windows as a supported platform.

Does this mean that the application will have to be supported on Windows Phone? Especially since Microsoft has ended support for Windows Phone. Our dash board solution will however be supported on all major platforms with a modern web browser.

A‐2‐The phone/mobile instance will have to " iOS, Google and Android compatible." This was an oversight on the author's part. The dashboard will have to operate in a Windows environment with modern browsers.

Q‐3 The requirements also request Mesh‐communication features, that we do not currently support, or plan on supporting. We have interpreted this as an optional requirement, are we correct in this assumption?

A‐3‐ The PWS states that this capability is desirable, but not required.

The availability of this function may be used as a discriminating factor in the Technical Review phase but not a disqualifying factor.

Q‐4 Can you clarify the embeddable requirement? What part of the system needs to be available as an SDK? Just the apps or perhaps the dash board?

What platforms do we have to support?

A‐4‐ The selected application must be able to have at least an icon or "hot link" that results in the user being able to access a function of the entire application. In this solicitation the ability to report a tip is the target functionality. For example, a visiting fan who has downloaded a stadium information application will be able to send a "tip report" to a dashboard user of the selected vendor's product by selecting a "hot link" or icon in the stadium information application. The tip would be routed to the Law Enforcement user dashboard. It is acceptable if this communication is one‐way, from mobile user to dashboard user. It is preferable if the communication can be two‐way even if it is basic text.

SUBMITTED ON Thu 2/14/2019 12:41 PM

Q‐1. Referring to this portion of the document:

"Vendors will provide access and a written set of instructions on how to register and use the functions to be tested."

Are these materials the "Sample" submission that is required with the response? In other words, we create a test account for West Point in our system and provide you with a list of instructions of how you can download and access the application on your devices so you can test it with the Technical Review Team?

A‐1‐ This is preferable. However, if a vendor has a training or beta version or if they would prefer to use an existing instance of their product to for the TRT to use, that is up to vendor. Given the advertised order of events in the solicitation, the TRT does not need to have a completely customized/finished product to test. But must have an exemplary product of the one the that will be customized for West Point once selected.

Q‐2. Am I correct in stating that the submission consists of 2 hard copies?

A‐2‐ 2 COPIES‐ CORRECT VIA EMAIL TO maureen.a.flanagan2.civ@mail.mil

Q‐3. What different materials explicitly have to be part of the submission? Below is the list that we believe it is. Could you clarify if we are missing any documents, sections, or materials?

* SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS (First page)

* DETAILED DESCRIPTION OF THE SUPPLIES AND/OR SERVICES REQUIRED

(Section with the 21 Parts)

* Sample submission (written instructions of how you can access and register a test version of the solution so it can be reviewed)

* Technical Review Criteria (Phase 1) section

* Section SF 1449 ‐ CONTINUATION SHEET (Price listing for the five 1 year periods stated)

A‐3‐ The technical review criteria is what will be used by the Tech Review Team to evaluate submissions.

4. Technical Review Criteria (Phase II) is not to be included as part of the submission correct?

A‐4‐ That is correct. The TRT (tech review team)will use this criteria sheet to evaluate submission

Q‐5. Where should the submission be delivered to? Should it be the Contracting Office?

681 Hardee Place West Point, New York 10996‐1514 United States

Or is it another address the hard copy submission should be delivered to?

I saw that in the document it mentions a Brian Heverly and underneath it "See instructions", but I could not find where those other instructions are when I did a Find search in the document. Is there information that I missed that states what the exact address is for the submission to be sent to?

If the location of where the submission should go is not the contracting office stated above, what is it?

A‐5‐ 2 COPIES‐ CORRECT VIA EMAIL TO maureen.a.flanagan2.civ@mail.mil

Q‐6. The solution calls for the ability to report anonymously, but also the capability where users have to register with an email address. How is this aspect being envisioned, or rather, how will users believe they are anonymous when they need to register with personal information such as email to use the app? We were curious as to how this aspect will be communicated.

A‐6 In order to have an instance of the application on the phone will require some form of discriminatory information provided so that only those with a "need" to have the application will be able to access it. A feature of the tip reporting function will be to "mask" the user's identity and location from the dashboard user if the mobile user desires to make the tip anonymously. So, the user can choose, by selecting an option, to report the tip with full attribution to the dashboard user or anonymously. The anonymity must be between the mobile user and the dashboard user with the understanding that if an emergency (life, limb, eyesight) is at hand, the vendor could be contacted for identifiable information.

(End of Summary of Changes)