HHS-NIH-NIDA(MH)-12-031_Amend05.pdf

OMB Approval 2700-0042 r· CONTRACT ID CODE PAGE OF PAGES

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT N/A 1 I 2

2. AMENDMENT/MODIFICATION NO. 13. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 15. PROJECT NO. (If

05 04/18/2012 N/A N/A

6. ISSUED BY CODE I 7. ADMINISTERED BY (If other than Item 6) CODE N/A

National Institutes of Health Office of Acquisitions- NIDA Neuroscience COAC NIMH R&D Contract Management Section 6001 Executive Boulevard, room 8154, MSC 9661 Bethesda, MD 20892-9661

8. NAME AND ADDRESS OF CONTRACTOR (No. Street, County, State and ZIP: Code) (IIJ) 9A. AMENDMENT OF SOLICITATION NO.

HHS-NIH-NIDA(MH)-12-031 X

TO: ALL OFFERORS 9B. DATED (SEE ITEM 11)

03/23/2012 TITLE: Development of State Health Policy Database for Research (SHPDR) to 10A. MODIFICATION OF CONTRACT/ORDER NO.

Advance Health Economics Research on Health Care Reform

10B. DATED (SEE ITEM 13)

CODE I FACILITY CODE

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

1:8] The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers D is extended, 1:81 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 one (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 ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATA 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 data specified.

12. ACCOUNTING AND APPROPRIATION DATA (If required)

N/A

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

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

(Iii) 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.

1---

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 1:81 is not, D 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.)

PURPOSE: To respond to additional questions asked about this solicitation

NOTE: Offerors should acknowledge receipt of all amendments with their proposal.

(Continued on p. 2)

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

15A. NAME AND TITLE OF SIGNER (Type or print)

156. CONTRACTOR/OFFEROR

(Signature of person authorized to sign)

NSN 7540.01-152-6070

PREVIOUS EDITION UNUSABLE

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

Bruce E. Anderson, Contracting Officer

15C. DATE SIGNED 166. UNITED STATES OF AMERICA 16C. DATE SIGNED

BYiJ/lM-q_ l.~ Ll/t 8' /t ~ (Signature of Contracting Officer)

30.105 Computer Generated

FAR (46 CFR) 53.243

STANDARD FORM 30 (REV. 10-83)

Prescribed by GSA

RFP- HHS-NIH-NIDA(MH)-12-031

Amendment No. 05 SPECIAL PROVISIONS

(04/18/12)

The following are additional questions that have been asked about this acquisition, with NIMH responses (see also Amendments 03 and 04 questions and answers):

Please note that on solicitation Attachment 2, the E-mail address to send this form to should have read: Banderso@mail.nih.gov

Q.1. Two related questions were received as follows:

a. Is the NIH completely relying on the Contractor to provide all technologies used to develop the database (i.e. Oracle, MySQL, Teradata, etc.)? Or, does the NIH have a list of required or preferred technologies?

b. Cali the NIH/NIMH provide any information about its current development environment or a list of preferred technologies to allow the Contractor to create a development plan that can be easily integrated with and is readily accessible to the NIH?

NIMH RESPONSE: The NIH currently uses Oracle for its databases, but any database technology that can export in a format compatible with Oracle would be acceptable for the contract. For software development NIMH currently uses Java.

Q.2. Please confirm that it is acceptable to have separate individuals to assume the roles of Project Director (PO) and Principal Investigator (P.I.) And, if this is acceptable, please confirm that it is acceptable for the P.l. to be a member of a subcontractor organization, as long as the P .D. is a member of the prime Contractor.

NIMH RESPONSE: The roles of a Project Director and Principal Investigator were intended to be one and the same in the RFP and not necessarily two different individuals (although this is not prohibited).

However using both titles creates some confusion since the NIH recognizes only one individual at the Prime to be responsible for the technical direction and oversight of the Project. This individual is recognized in the contract as the Principal Investigator. The Principal Investigator must be an employee of the prime Contractor- the government cannot interact directly with a subcontractor regarding contract performance.

Therefore (as applicable) if two such positions are proposed, the Prime should propose a "Principal lnvestigator"and the subcontract's primary technical person could be proposed as a "Co-Investigator" (rather than "Project Director," to avoid confusion).