91990018R0002_0001_signed.pdf

NSN 7540-01-152-8070 STANDARD FORM 30. (Rev. 10-83) Previous Edition unusable Prescribed by GSA FAR (48 CFR) 53.243

Page of Pages AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT 1. Contract ID Code

2. AMENDMENT MODIFICATION NO. 3. EFFECTIVE DATE 4. REQUISITION/PURCHASE REQ. NO. 5. PROJECT NO. (if applicable)

6. ISSUED BY CODE 7. ADMINISTERED BY (If other than item 6) CODE

(x) 9A. AMENDMENT OF SOLICITATION NO.

9B. DATED (SEE ITEM 11)

10A. MODIFICATION OF CONTRACT/ORDER NO.

8. NAME AND ADDRESS OF CONTRACTOR (NO., Street, Country, State and ZIP Code)

CODE FACILITY CODE

10B. DATED (SEE ITEM 13)

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

The above numbered solicitation is amended as set forth in item 14. The hour and date specified for receipt of offers 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 ______ copies of 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 OR OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment your 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 ONLY APPLIES TO MODIFICATION OF CONTRACTS/ORDERS. IT MODIFIES THE CONTRACT/ORDER NO. AS DESCRIBED IN ITEM 14.

Check One

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)

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 16B. UNITED STATES OF AMERICA

(Signature of person authorized to sign)

15C. DATE SIGNED

(Signature of Contracting Officer)

16C. DATE SIGNED

Veronica.Price Stamp

Veronica.Price Typewritten Text

Attachment Page

PAGE 2 OF 27 91990018R00020001

The purpose of this amendment is as follows:

1. Post the Department’s responses to clarification questions received from potential offerors.

2. The following solicitation clauses are added:

H.1 3452.239-72 DEPARTMENT SECURITY REQUIREMENTS (MAY 2011)

H.2 3452.242-72 WITHHOLDING OF CONTRACT PAYMENTS (AUG 1987)

I.1 52.203-14 DISPLAY OF HOTLINE POSTER(S) (OCT 2015)

I.2 52.204-9 PERSONAL IDENTITY VERIFICATION OF CONTRACTOR PERSONNEL (JAN 2011)

I.3 52.215-18 REVERSION OR ADJUSTMENT OF PLANS FOR POSTRETIREMENT BENEFITS

(PRB) OTHER THAN PENSIONS (JUL 2005)

I.4 52.219-4 NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE SMALL BUSINESS

CONCERNS (OCT 2014)

I.5 52.227-1 AUTHORIZATION AND CONSENT (DEC 2007)

I.6 52.227-14 RIGHTS IN DATA--GENERAL (MAY 2014)

I.7 52.229-3 FEDERAL, STATE, AND LOCAL TAXES (FEB 2013)

I.8 52.232-8 DISCOUNTS FOR PROMPT PAYMENT (FEB 2002)

I.9 52.232-9 LIMITATION ON WITHHOLDING OF PAYMENTS (APR 1984)

I.10 52.232-11 EXTRAS (APR 1984)

I.11 52.249-8 DEFAULT (FIXED-PRICE SUPPLY AND SERVICE) (APR 1984)

I.12 52.215-19 NOTIFICATION OF OWNERSHIP CHANGES (OCT 1997)

L.1 52.222-46 EVALUATION OF COMPENSATION FOR PROFESSIONAL EMPLOYEES (FEB

1993)

L.2 52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY

AGREEMENTS OR STATEMENTS (JAN 2017)

L.3 52.242-5 PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (JAN 2017)

3. The following solicitation clause is revised:

L.4 Section L – Instruction to Offerors

4. The following solicitation attachments are added:

“SWAT Appendices & Attachments” located in the FBO posting

All other terms and conditions of the solicitation remain the same or unchanged.

PAGE 3 OF 27 91990018R00020001

United States Department of Education (Department)

Request for Proposals 91990018R0002

What Works Clearinghouse: Statistics, Website, and Training (WWC-SWAT)

Clarification Questions and Responses

1. Offeror question: There appears to be a discrepancy in the Instructions to Offerors regarding Past Performance between the instructions on page 89 “past performance information shall be provided in the technical volume” and the separately required Past

Performance volume. Please confirm that Past Performance should be submitted in a separate volume.

Department Response: Past Performance information should be included in the technical volume. Section L has been updated.

2. Offeror question: Can ED confirm the due date for the Contractor Performance

Evaluation forms? Should these be submitted by January 5 as indicated on Attachment B or can they be submitted by the due date of the proposal (January 10)?

Department Response: The Contractor Performance Evaluation forms are due

January 10 th

. Attachment B has been updated.

3. Offeror question: On pg. 84, 85 and 89 the RFP indicates that past performance information should be submitted as a separate volume. On pg. 89, the RFP says that past performance information shall be provided in the technical volume. Can ED confirm (a) whether we should submit past performance information as a separate volume or as part of the technical proposal and (b) that evaluators will have access to both the technical and past performance volumes?

Department Response: Past Performance information should be included in the technical volume. Section L has been updated. Evaluators will have access to the technical volume which will include the past performance information.

4. Offeror question: Can you please confirm whether the letter of transmittal, table of contents, and abstract are included in the 75 page limit?

Department Response: These elements are not included in the 75 page limit.

5. Offeror question: We assume the abstract and table of contents are not included in the

75-page limit for the technical proposal. Could ED confirm that this is the case?

Department Response: Yes, that is the case.

6. Offeror question: Is it acceptable for the abstract and table of contents to be single-spaced?

PAGE 4 OF 27 91990018R00020001

Department Response: Yes, that is acceptable.

7. Offeror question: Is it acceptable to use single-spacing for bullets?

Department Response: No, that is not acceptable.

8. Offeror question: The “Organizational Capacities…” section states: “The technical proposal must contain an internal quality control plan that addresses accountability in each subtask area.” Is this in addition to the Quality Control plan referenced in Subtask

1.7?

Department Response: Yes, this plan is in addition to the Quality Control plan referenced in Subtask 1.7.

9. Offeror question: In the PWS, the narrative description of Task 1 and the schedule of deliverables list some different deadlines. Can you please clarify which deadlines are correct for each item?

Department Response: Each deadline is correct for the deliverable as listed in Task 1.

10. Offeror question: Sub task 1.7 states that additional guidance for the Quality

Management Plan and Risk Management Plan is provided in the solicitation, however no additional guidance is available in the solicitation. Please provide the additional guidance referenced in subtask 1.7.

Department Response: Please see the appendices for IT Reporting Guidance and the

IT Reporting Template.

11. Offeror question: Does this subtask refer to overall Quality Control procedures, or those specific to quality control of WWC study reviews? Although we believe it is typically reserved for overall quality control, the following sentence makes us think otherwise:

“These quality control measures may include tools such as internal quality checks on

WWC study reviews to ensure that all reviewers are accurate and up to date on WWC procedures.”

Department Response: Subtask 1.7 is not related to quality control of WWC study reviews.

12. Offeror question: The final paragraph of Task 2.2 notes that we are to work with the

PEPPER and OREGANO contracts in their development of videos to support users with the WWC tools (SWAT task 3). Tasks 10.2 and 10.3 of SWAT also detail work needed for videos to support users. Can you please explain the difference in the videos described in Task 10 of SWAT versus videos being developed in PEPPER and OREGANO? Will videos be developed in PEPPER and OREGANO through the entire five years of the

PAGE 5 OF 27 91990018R00020001

contracts or will the majority, if not all, of the communications work supporting the

WWC website and tools exist as a SWAT responsibility?

Department Response: The videos that are described in Task 10 of SWAT should be focused primarily on topics that are part of the broader SWAT contract. As an example, a video created under Task 10 might demonstrate how to use features of the

WWC website or explain part of the WWC review process. Videos may be developed in

PEPPER and OREGANO throughout the duration of those contracts.

13. Offeror question: Please provide copies of the requirement and design documents and user guides for the WWC system and tools.

Department Response: Please consult the attached Appendices D – G for more details about the system design and requirements

14. Offeror question: How many databases are used by the WWC web applications?

Department Response: All data used is available here:

https://ies.ed.gov/ncee/wwc/StudyFindings

15. Offeror question: How large are the databases?

16. Offeror question: How many tables are in the databases?

17. Offeror question: How many rows and columns are in the largest tables?

18. Offeror question: Can the database be queried with tools such as SAS or SPSS?

Department Response: The data is exported as a .CSV file that can be imported into statistical software by end users. The WWC contractor is not expected to use statistical software.

19. Offeror question: What is the approximate volume of defects requiring resolution on a monthly basis?

PAGE 6 OF 27 91990018R00020001

Department Response: The rates of records with errors is between 5-10% as users are transitioning to the Online SRG system. IES expects that the rates will be no more than

5% as users learn the new system.

20. Offeror question: Is there a backlog of existing defects and if so, how many are there?

Department Response: There is currently no backlog. It is possible that a small number of newly added records (fewer than 20) will need to be examined for defects immediately after award.

21. Offeror question: Please provide the type and volume for the monthly database updates.

Department Response: New database entries will be in the form of new studies reviewed, either for the first time or under a different protocol or standards. The volume will vary dramatically based on the season and work load of the other WWC contractors. In the past year, the high volume was 410 with a typical volume of 150.

22. Offeror question: How are the database updates provided to the contractor?

Department Response: The updates are automatically created through the Online SRG tool and the contractor will be able to push updates from tool to production.

23. Offeror question: Subtask 4.2 says: “three (3) sets of reviews (under different protocols) for audit…” Could you please clarify what three sets of reviews means?

Department Response: The WWC expects this subtask will account for reviews of up to

20 individual studies, but intentionally does not specify how the studies selected for audit shall be selected. As noted in the PWS, “[t]he contractor shall provide a detailed description of, and justification for, the sampling of particular studies.”

24. Offeror question: This subtask asks contractors to conduct “up to 2 in-person training sessions per year”. The second section says that the trainings will be “Single Case Design or Regression Discontinuity Standards.” Does this mean that all of the trainings will be

Single Case or RDD, or that among the 2 per year conducted, at least 2 will focus on these issues?

Department Response: The trainings will be on Single Case Design or RDD standards.

However, if standards for other designs are developed in a new area over the course of the contract, these new standards could be the focus of some of these trainings.

25. Offeror question: Can you clarify whether this subtask is specific to the Single Case and

RDD training, or more general for group design as well?

PAGE 7 OF 27 91990018R00020001

Department Response: By the time of award for the SWAT contract, the WWC will have an online training system for group design certification. The subtask is specific to training other than group design.

26. Offeror question: What makes a WWC-certified reviewer eligible to conduct peer-reviews? Similarly, will the SWAT contractor and subcontractors be expected to perform all reviews or does IES expect for the reviews to be distributed across the whole pool of certified reviewers who are willing and qualified to do peer reviews?

Department Response: IES expects all new WWC intervention reports and some reviews of individual studies to receive an independent peer review through the SWAT contract. The study documents, draft WWC reports, and Master Review Guide materials needed for peer review will be shared with the SWAT contractor by the COR, together with a list of questions for the reviewer to answer. A full re-review of a study using WWC standards will, in general, not be required, but rather an assessment of the accuracy, comprehensiveness, and clarity of presentation in the draft intervention report or review of individual study. A reviewer is eligible to provide peer review of draft WWC products and publications if the reviewer is certified in the same version of

WWC standards under which the product or publication (or its constituent parts) was prepared. There should be no conflict of interest between the reviewer and either an author of a study reviewed by the WWC, or the organization responsible for the draft

WWC product or publication. Consequently, peer review of materials prepared by the

SWAT contractor should be conducted by WWC-certified reviewers who are independent consultants or who are employees of a subcontractor. The WWC-certified reviewers proposed for peer review purposes may be a subset of all WWC-certified reviewers and should be compensated directly by the SWAT contractor. For budgeting purposes, compensation of $100 per hour, with 10 hours of review per intervention report and 2 hours of review per individual study, should be assumed, as well as 18 intervention reports and 70 individual studies in need of peer review per contract year. A searchable database of selected individuals and organizations with WWC reviewer certification is here: https://ies.ed.gov/ncee/wwc/Reviewer

27. Offeror question: Will IES or the contractor be responsible for compensating peer reviewers? If the latter, what should the contractor assume as an appropriate amount of compensation for this work?

Department Response: The contractor will be responsible for compensating peer reviewers. For budgeting purposes, the offeror should assume compensation of $100 per hour, with 10 hours of review per intervention report and 2 hours of review per individual study, should be assumed, as well as 18 intervention reports and 70 individual studies in need of peer review per contract year.

PAGE 8 OF 27 91990018R00020001

28. Offeror question: Please provide the number of FTEs that currently support the WWC website, database and tools.

Department Response: Contractors should use their best estimate about the number of

FTEs that would provide an appropriate level of support.

29. Offeror question: Please provide help desk metrics by month and or year that include the number of calls and emails and types of inquires received by topic. This information is needed to better understand the level of effort and staffing model for the help desk.

Department Response: The WWC help desk receives, on average, between 150 and 175 inquiries each quarter. Roughly 90% of these are via email, with the remainder by telephone. The inquiries fall primarily into one of the categories listed below:

General requests for information

Complaints about WWC products or procedures

Replies to author queries (related to WWC reviews of a study)

Suggestions for topics or interventions to study

Requests to share content

Many of the requests received by the help desk are ones for which the WWC has prepared a standard response. These standard responses will be shared at the time of award.

30. Offeror question: Please provide the peak periods/timelines and number of calls and emails received when call and email volumes are higher than normal.

Department Response: A typical volume of requests is between 50 and 60 emails per month and 3-5 calls per month. There may be a slight increase in volume after a new product is released, but the increase is usually negligible.

31. Offeror question: Please provide the average amount of time required to prepare an email response

Department Response: Replies to email requests are sent within eight business hours of receipt, with the goal to respond as soon as possible. Exceptions to the eight-hour turnaround time include instances that require input from WWC management, the

Quality Review Team, IES, or other WWC contractors.

32. Offeror question: Please provide the approximate numbers of users supported by the help desk

Department Response: A typical volume of requests is between 50 and 60 emails per month and 3-5 calls per month.

PAGE 9 OF 27 91990018R00020001

33. Offeror question: Please provide the number of FTEs that currently support the help desk.

Department Response: As noted, the WWC help desk receives, on average, between 150 and 175 inquiries each quarter. The offeror should incorporate this level of activity in proposing staffing and other parameters related to the help desk.

34. Offeror question: What help desk ticketing system is currently used?

Department Response: The current contractor uses a proprietary system.

35. Offeror question: Will prior help desk tickets be provided upon award of the contract?

Department Response: Yes, any outstanding help desk tickets will be transferred upon award of contract.

36. Offeror question: Is the toll-free number provided by ED or will the contractor be expected to provide it?

Department Response: The number will be provided by ED.

37. Offeror question: Please provide any standard operating procedures and or training material for the help desk and IT systems operations.

Department Response: Please see the Appendix document Help Desk Guide

Procedures.

38. Offeror question: Does the help desk maintain and update the social media accounts?

Department Response: No, the WWC’s social media accounts are not connected to the help desk.

39. Offeror question: Please specify the duration of the current contractor's Transition-out

Plan.

Department Response: The offeror should plan for a transition period of no more than

15 days.

PAGE 10 OF 27 91990018R00020001

40. Offeror question: Can the Department clarify the difference between Subtasks 12.2 and

13.2?

Department Response: Subtask 12.2 is related to changes in the WWC Standards

Handbook, while Subtask 13.2 is related to changes in the WWC Procedures

Handbook. With the release of the updated handbooks in October 2017, the

Handbooks are two separate documents, which allows the WWC to update each separately.

Table of Contents

PAGE 11 OF 27 91990018R00020001

SECTION H SPECIAL CONTRACT REQUIREMENTS

H.1 3452.239-72 DEPARTMENT SECURITY REQUIREMENTS (MAY 2011)

H.2 3452.242-72WITHHOLDING OF CONTRACT PAYMENTS (AUG 1987)

SECTION I CONTRACT CLAUSES

I.1 52.203-14 DISPLAY OF HOTLINE POSTER(S) (OCT 2015)

I.2 52.204-9 PERSONAL IDENTITY VERIFICATION OF CONTRACTOR PERSONNEL (JAN 2011)

I.3 52.215-18 REVERSION OR ADJUSTMENT OF PLANS FOR POSTRETIREMENT BENEFITS (PRB) OTHER THAN PENSIONS

(JUL 2005)

I.4 52.219-4 NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE SMALL BUSINESS CONCERNS (OCT 2014).13

I.5 52.227-1 AUTHORIZATION AND CONSENT (DEC 2007)

I.6 52.227-14 RIGHTS IN DATA--GENERAL (MAY 2014)

I.7 52.229-3 FEDERAL, STATE, AND LOCAL TAXES (FEB 2013)

I.8 52.232-8 DISCOUNTS FOR PROMPT PAYMENT (FEB 2002)

I.9 52.232-9 LIMITATION ON WITHHOLDING OF PAYMENTS (APR 1984)

I.10 52.232-11 EXTRAS (APR 1984)

I.11 52.249-8 DEFAULT (FIXED-PRICE SUPPLY AND SERVICE) (APR 1984)

I.12 52.215-19 NOTIFICATION OF OWNERSHIP CHANGES (OCT 1997)

SECTION L INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 52.222-46 EVALUATION OF COMPENSATION FOR PROFESSIONAL EMPLOYEES (FEB 1993)

L.2 52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS OR STATEMENTS

(JAN 2017)

L.3 52.242-5 PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (JAN 2017)

L.4 Instructions to Offerors

PAGE 12 OF 27 91990018R00020001

SECTION H

SPECIAL CONTRACT REQUIREMENTS

H.1 3452.239-72 DEPARTMENT SECURITY REQUIREMENTS (MAY 2011)

(a) The contractor and its subcontractors shall comply with Department security policy requirements as set forth in the "Bidder`s Security Package: Security Requirements for Contractors Doing Business with the Department of Education" at www.ed.gov/fund/contract/about/bsp.html.

(b) The following are the contractor employee positions required under this contract and their designated risk levels:

High Risk (HR): N/A Moderate Risk (MR): Project Director, Key Staff Low Risk (LR): N/A

(c) All contractor employees must undergo personnel security screening if they will be employed for 30 days or more, in accordance with Departmental Directive OM:5-101, "Contractor Employee Personnel Security Screenings." The type of screening and the timing of the screening will depend upon the nature of the contractor position, the type of data to be accessed, and the type of information technology (IT) system access required. Personnel security screenings will be commensurate with the risk and magnitude of harm the individual could cause.

(d) The contractor shall--

(1) Ensure that all non-U.S. citizen contractor employees are lawful permanent residents of the United States or have appropriate work authorization documents as required by the Department of Homeland Security, Bureau of Immigration and Appeals, to work in the United States.

(2) Ensure that no employees are assigned to high risk designated positions prior to a completed preliminary screening.

(3) Submit all required personnel security forms to the contracting officer`s representative (COR) within 24 hours of an assignment to a Department contract and ensure that the forms are complete.

(4) Ensure that no contractor employee is placed in a higher risk position than that for which he or she was previously approved, without the approval of the contracting officer or the COR, the Department personnel security officer, and the Department computer security officer.

(5) Ensure that all contractor employees occupying high-risk designated positions submit forms for reinvestigation every five years for the duration of the contract or if there is a break in service to a Department contract of 365 days or more.

(6) Report to the COR all instances of individuals seeking to obtain unauthorized access to any departmental IT system, or sensitive but unclassified and/or Privacy Act protected information.

(7) Report to the COR any information that raises an issue as to whether a contractor employee`s eligibility for continued employment or access to Department IT systems, or sensitive but unclassified and/or Privacy Act protected information, promotes the efficiency of the service or violates the public trust.

(8) Withdraw from consideration under the contract any employee receiving an unfavorable adjudication determination.

(9) Officially notify each contractor employee if he or she will no longer work on a Department contract.

(10) Abide by the requirements in Departmental Directive OM:5-101, "Contractor Employee Personnel Security Screenings."

(e) Further information including definitions of terms used in this clause and a list of required investigative forms for each risk designation are contained in Departmental Directive OM:5-101, "Contractor Employee Personnel Security Screenings" available at the Web site listed in the first paragraph of this clause.

(f) Failure to comply with the contractor personnel security requirements may result in a termination of the contract for default.

(End of Clause)

H.2 3452.242-72 WITHHOLDING OF CONTRACT PAYMENTS (AUG 1987)

Notwithstanding any other payment provisions of this contract, failure of the contractor to submit required reports when due or failure to perform or deliver required work, supplies, or services, or failure to meet any of the requirements of the contract, will result in the withholding of payments under this contract in such amounts as the contracting officer deems appropriate, unless the failure arises out of causes beyond the control,and without the fault of negligence, of the contractor, as defined by the clause entitled "Excusable Delays" or "Default", as applicable. The Government shall promptly notify the contractor of its intention to withhold payment of any invoice or voucher submitted. Payment will be withheld until the failure is cured, a new delivery schedule is agreed upon, or payment is made as part of a termination settlement.

PAGE 13 OF 27 91990018R00020001

SECTION I

CONTRACT CLAUSES

I.1 52.203-14 DISPLAY OF HOTLINE POSTER(S) (OCT 2015)

(Reference 52.203-14)

I.2 52.204-9 PERSONAL IDENTITY VERIFICATION OF CONTRACTOR PERSONNEL (JAN 2011)

(Reference 52.204-9)

I.3 52.215-18 REVERSION OR ADJUSTMENT OF PLANS FOR POSTRETIREMENT BENEFITS (PRB) OTHER THAN PENSIONS

(JUL 2005)

(Reference 52.215-18)

I.4 52.219-4 NOTICE OF PRICE EVALUATION PREFERENCE FOR HUBZONE SMALL BUSINESS CONCERNS (OCT 2014) (Reference 52.219-4)

I.5 52.227-1 AUTHORIZATION AND CONSENT (DEC 2007)

(Reference 52.227-1)

I.6 52.227-14 RIGHTS IN DATA--GENERAL (MAY 2014)

(Reference 52.227-14)

I.7 52.229-3 FEDERAL, STATE, AND LOCAL TAXES (FEB 2013)

(Reference 52.229-3)

I.8 52.232-8 DISCOUNTS FOR PROMPT PAYMENT (FEB 2002)

(Reference 52.232-8)

(The following clause shall apply as prescribed in FAR 32.111(c)(2).)

I.9 52.232-9 LIMITATION ON WITHHOLDING OF PAYMENTS (APR 1984)

(Reference 52.232-9)

I.10 52.232-11 EXTRAS (APR 1984)

(Reference 52.232-11)

I.11 52.249-8 DEFAULT (FIXED-PRICE SUPPLY AND SERVICE) (APR 1984)

(Reference 52.249-8)

I.12 52.215-19 NOTIFICATION OF OWNERSHIP CHANGES (OCT 1997)

(a) The Contractor shall make the following notifications in writing:

(1) When the Contractor becomes aware that a change in its ownership has occurred, or is certain to occur, that could result in changes in the valuation of its capitalized assets in the accounting records, the Contractor shall notify the Administrative Contracting Officer (ACO) within 30 days.

(2) The Contractor shall also notify the ACO within 30 days whenever changes to asset valuations or any other cost changes have occurred or are certain to occur as a result of a change in ownership.

(b) The Contractor shall--

(1) Maintain current, accurate, and complete inventory records of assets and their costs;

(2) Provide the ACO or designated representative ready access to the records upon request;

(3) Ensure that all individual and grouped assets, their capitalized values, accumulated depreciation or amortization, and remaining useful lives are identified accurately before and after each of the Contractor`s ownership changes; and

(4) Retain and continue to maintain depreciation and amortization schedules based on the asset records maintained before each Contractor ownership change.

(c) The Contractor shall include the substance of this clause in all subcontracts under this contract that meet the applicability requirement of FAR 15.408(k).

(End of Clause)

PAGE 14 OF 27 91990018R00020001

SECTION L

INSTRUCTIONS, CONDITIONS, AND NOTICES TO OFFERORS

L.1 52.222-46 EVALUATION OF COMPENSATION FOR PROFESSIONAL EMPLOYEES (FEB 1993)

(Reference 52.222-46)

L.2 52.203-19 PROHIBITION ON REQUIRING CERTAIN INTERNAL CONFIDENTIALITY AGREEMENTS OR STATEMENTS

(JAN 2017)

(a) Definitions. As used in this clause-- "Internal confidentiality agreement or statement" means a confidentiality agreement or any other written statement that the contractor requires any of its employees or subcontractors to sign regarding nondisclosure of contractor information, except that it does not include confidentiality agreements arising out of civil litigation or confidentiality agreements that contractor employees or subcontractors sign at the behest of a Federal agency.

"Subcontract" means any contract as defined in subpart 2.1 entered into by a subcontractor to furnish supplies or services for performance of a prime contract or a subcontract. It includes but is not limited to purchase orders, and changes and modifications to purchase orders.

"Subcontractor" means any supplier, distributor, vendor, or firm (including a consultant) that furnishes supplies or services to or for a prime contractor or another subcontractor.

(b) The Contractor shall not require its employees or subcontractors to sign or comply with internal confidentiality agreements or statements prohibiting or otherwise restricting such employees or subcontractors from lawfully reporting waste, fraud, or abuse related to the performance of a Government contract to a designated investigative or law enforcement representative of a Federal department or agency authorized to receive such information (e.g., agency Office of the Inspector General).

(c) The Contractor shall notify current employees and subcontractors that prohibitions and restrictions of any preexisting internal confidentiality agreements or statements covered by this clause, to the extent that such prohibitions and restrictions are inconsistent with the prohibitions of this clause, are no longer in effect.

(d) The prohibition in paragraph (b) of this clause does not contravene requirements applicable to Standard Form 312 (Classified Information Nondisclosure Agreement), Form 4414 (Sensitive Compartmented Information Nondisclosure Agreement), or any other form issued by a Federal department or agency governing the nondisclosure of classified information.

(e) In accordance with section 743 of Division E, Title VII, of the Consolidated and Further Continuing Appropriations Act, 2015, (Pub. L. 113-235), and its successor provisions in subsequent appropriations acts (and as extended in continuing resolutions) use of funds appropriated (or otherwise made available) is prohibited, if the Government determines that the Contractor is not in compliance with the provisions of this clause.

(f) The Contractor shall include the substance of this clause, including this paragraph (f), in subcontracts under such contracts.

(End of clause)

L.3 52.242-5 PAYMENTS TO SMALL BUSINESS SUBCONTRACTORS (JAN 2017)

(a) Definitions. As used in this clause-- "Reduced payment" means a payment that is for less than the amount agreed upon in a subcontract in accordance with its terms and conditions, for supplies and services for which the Government has paid the prime contractor.

"Untimely payment" means a payment that is more than 90 days past due under the terms and conditions of a subcontract, for supplies and services for which the Government has paid the prime contractor.

(b) Notice. The Contractor shall notify the Contracting Officer, in writing, not later than 14 days after--

(1) A small business subcontractor was entitled to payment under the terms and conditions of the subcontract; and

(2) The Contractor--

(i) Made a reduced or untimely payment to the small business subcontractor; or

(ii) Failed to make a payment, which is now untimely.

(c) Content of notice. The Contractor shall include the reason(s) for making the reduced or untimely payment in any notice required under paragraph (b) of this clause.

(End of clause)

PAGE 15 OF 27 91990018R00020001

L.4 Instructions to Offerors

INSTRUCTIONS TO OFFERORS

What Works Clearinghouse: Statistics, Website, and Training Contract (WWC-SWAT)

I. Proposal Submission Instructions The U.S. Department of Education (Department) anticipates the award of one hybrid noncommercial contract (with Firm-Fixed-Price (FFP) and Cost-Plus-Fixe-Fee (CPFF) tasks).

This competitive procurement is open to both large and small businesses and will be conducted in accordance with Federal Acquisition Regulations (FAR) Part 15 (Contracting by Negotiation).

In addition, the Contracting Officer is the only individual who can legally commit the

Government to the expenditure of public funds in connection with this acquisition.

Anticipated Period of Performance. This contract contains a 12-month base period and four

12-month option periods, with periods of performance as follows:

Base Period (March 1, 2018 –February 28, 2019)

Option Period 1 (March 1, 2019 –February 29, 2020)

Option Period 2 (March 1, 2020 –February 28, 2021)

Option Period 3 (March 1, 2021 –February 28, 2022)

Option Period 4 (March 1, 2022 –February 28, 2023)

Clarification Questions. All questions regarding this solicitation must be submitted via email no later than Monday, December 11, 2017 at 10:00am Eastern Time. Clarification questions must be submitted with the email subject line “Clarification questions for 91990018R0002 ([Name of

Offeror])” (e.g., “Clarification questions for 91990018R0002 (ABC Co.)”) to

Veronica.Price@ed.gov with a cc: to Gibran.Mills@ed.gov.

Proposal Submission. Offerors shall submit their proposal in three separate volumes: (i)

Technical Proposal and (ii) Business Proposal. The technical proposal must not contain reference to specific costs/prices, although resource information may be included so that the offeror’s understanding of the scope of the work may be evaluated.

Cost/price information is restricted to the business proposal. The technical and business proposal volumes must be separate and complete so that evaluation of one may be accomplished independently of the other.

Proposals must be submitted electronically by Wednesday, January 10, 2018 at 10:00am Eastern

Time, no extensions will be granted. Proposals must be submitted with the email subject line

“Proposal for 91990018R0002 ([Name of Offeror])” (e.g., “Proposal for 91990018R0002 (ABC

Co.)”) to Veronica.Price@ed.gov with a cc: to Gibran.Mills@ed.gov. Each proposal volume must be signed by an official authorized to bind the offerors organization.

Electronic Submission: Proposals are to be submitted by email as three separate documents with the following file names:

(i) “[Name of Company] Technical Proposal ([Version Date])” (e.g., “ABC Co.

Technical Proposal (January 5, 2018)”);

Deleted: , Deleted: , and (iii) Past Performance Volume

Deleted: four

PAGE 16 OF 27 91990018R00020001

(ii) “[Name of Company] Business Proposal ([Version Date])”;

(iii) “[Name of Company] Business Proposal Spreadsheets ([Version Date])”;

The technical proposal and business proposal may be submitted as either a PDF or

MSWord documents. The business proposal spreadsheets document must be submitted as an MSExcel document. The Department’s email system cannot handle emails larger than 20mb. Submissions should be broken into separate emails if necessary, for example, “Proposal for 91990018R0002 (Email 1 of 3) ([Name of Company]).” With the qualification set forth above, the Department prefers document consolidation.

Appendices to the technical proposal should be contained in the technical proposal document, unless there is a problem keeping the file size below 20mb. Likewise, the offeror’s conflict of interest policy (a requirement of the business proposal) must be contained in the business proposal document, not submitted as a separate attached document.

Oral Instructions Given Prior to Solicitation Closing Date. Oral explanations or instructions given by the Government before the award of the anticipated contract shall not be binding. Any information given to a prospective offeror concerning a solicitation will be furnished via a formal solicitation amendment posted on www.FBO.gov to all other prospective offerors if that information will facilitate the submission of proposals or if a lack of information would be prejudicial to any other prospective offerors.

II. General Proposal Instructions While the intent of each task is spelled out in the Performance Work Statement (PWS), it is up to offerors to propose the most effective method for carrying out these tasks. The task specifications contained in the RFP are a starting point; the proposal is expected to build on them, providing examples, where appropriate, not simply repeating the language contained in the RFP. Any proposed changes to the scope of the work or to the deliverable dates shall be justified.

It is important that the offeror completely addresses all of the tasks described in the PWS, and provides enough detail on its approach to executing each task that technical merit can be determined.

The offeror does not need to repeat information within the same volume. Such information should be presented in detail in one area of the volume where it contributes most critically to achieving the program’s objectives. In other areas where discussion of the same information is necessary, the offeror may refer to the detailed discussion and identify its location within the volume. If the offeror determines that the same or similar information is required in separate volumes, that information shall be detailed in each volume.

III. Technical Proposal The technical proposal has a page limit of 75 pages (8.5” x 11” pages). Excluded from this page count are: (i) the technical proposal cover page, (ii) a resume appendix, (iii) letters of commitment appendix, (iv) sample research reports appendix (see “Organizational Capabilities, Deleted: “[Name of Company] Past

Performance Volume ([Version Date]).”

Deleted: , Deleted: , and past performance volume

PAGE 17 OF 27 91990018R00020001

Experience & Resources” section below). Included in this page limit are, among other things, tables/graphics, corporate references, abstracts of current corporate work, and lists of current contractual commitments of proposals staff. All pages in the technical proposal and appendices shall be numbered. The formatting requirements for the technical proposal are as follows: (i) double-spaced text, (ii) font that is 12-pt, (iii) 1-inch margins. The formatting requirements for the technical proposal do not apply to any graphs or tables included in the technical proposal.

The resume appendix has no formatting requirements or overall page limit. However, no single resume may be longer than four pages. Each resume should clearly demonstrate that individuals have the skills to perform the work for which they are proposed.

The primary author for each section of the Technical Proposal shall be identified by name. The technical proposal shall contain the following elements:

Cover Page: At a minimum, the cover page shall contain: the words “Technical Proposal”; the solicitation number 91990018R0002; the title of the procurement (“What Works Clearinghouse:

Statistics, Website, and Training Contract (WWC-SWAT)”); the version date of the technical proposal (e.g., MONTH DAY, YEAR); the name, website address (if applicable), and DUNS number of the offeror; and a list of primary subcontractors and consultants (name of company, website address (if applicable), and DUNS number) along with one of the following labels for each subcontractor/consultant: “Not Small,” “Small Business,” “Small Disadvantaged Business,”

“Woman-Owned Small Business,” “HUBZone Small Business,” or “Service-Disabled Veteran-

Owned Small Business.”

Abstract: A one-page summary is to be provided abstracting the proposal contents in language understandable to an informed layperson. The abstract shall indicate full acceptance of the solicitation requirements or note any exceptions or assumptions (to be justified in the technical proposal).

Table of Contents: The Table of Contents must provide a means of quickly accessing important points of discussion in the proposal and should contain either 2 or 3 levels of headings.

Introduction: The offeror must briefly summarize and justify their overall approach to achieving the purpose of the procurement, its scope of work, and required deliverables. This section also should describe ways in which the offeror’s proposed approach is unique, insightful, or particularly comprehensive. The offeror must demonstrate an understanding of the project and familiarity with the issues relevant to designing and conducting random assignment impact evaluations in a school setting.

Technical Approach (Task Descriptions): This section shall provide information addressing each task and subtask area, including the offeror’s understanding of the nature and scope of each of the project tasks/subtasks, in the order presented in the PWS, along with a discussion of any potential issues and the means to address them.

Management Plan and Timelines: The offeror shall present a proposed timeline addressing the

PAGE 18 OF 27 91990018R00020001

subtasks, deliverables, and Department approval of deliverables together with the responsible staff. A summary table should be included presenting critical milestones with dates. This table shall include starting and ending dates of each major project task and activity. The offeror shall also delineate any materials or services expected from the Department in the timetable (e.g., data, applications, reports, etc.). As it is of the utmost importance that the anticipated contract meet its timelines, the technical proposal shall describe in detail the offeror’s process for ongoing evaluation of progress on the anticipated contract and methods proposed to manage potential delays or performance problems.

Proposed Personnel: The names of the proposed project director and other key personnel and consultants, a narrative description of staff qualifications and how they will meet the requirements of the contract, and resumes for proposed project staff including dates of work and role in such work for all experience. Include detailed vitae for all proposed professional staff (in the resume appendix) and letters of commitment (in the letters of commitment appendix) from all proposed subcontractors, consultants, professional staff not currently employed by the offeror, or collaborators delineating the nature of their agreement. Offerors are encouraged to suggest specific experts who might be appropriate for the Practice Guide Optional Task.

In the main body of the technical proposal (not an appendix) describe any sub-contractual arrangements including work to be done, responsibilities for tasks, reporting arrangements, and any other terms of the contract pertinent to the technical proposal. Justifications must be provided for the use of subcontractors or consultants on this project, and the offeror shall state that such entities or individuals are free of conflicts of interest that might bias their approach to this study.

Offerors shall demonstrate that the proposed key personnel are not overextended during the first three years of the contract by including a chart showing how the labor hours proposed for

91990018R0002 compare to other commitments (including other contracts and projects). At a minimum, offerors shall include a chart with the following data:

Staff Total labor hours Total labor hours Total labor hours Total labor hours Total labor Total labor hours

Member proposed for this proposed for other proposed for this proposed for other hours proposed proposed for other contract projects contract projects for this contract projects

(3/1/2018 – (3/1/2018 – (3/1/2019 – (3/1/2019 – (3/1/2020 – (3/1/2020 – 2/28/2019) 2/28/2019) 2/28/2020) 2/28/2020) 2/28/2021) 2/28/2021)

The technical proposal must contain, per period and per task, the labor categories and labor hours proposed (but not the labor rate or total labor price/cost). This information should be formatted so that the Department can easily discern which personnel are offeror employees and which personnel are subcontractor/consultant employees (and which subcontractor/consultant). Where an individual can be identified by name, the name should be provided along with that person’s labor category. This information will allow for a determination to be reached as to whether the offeror is proposing labor categories that are appropriate and reasonable to the work set forth in the PWS.

As a general matter, proposals that include plans to subcontract parts of the work (whether to

PAGE 19 OF 27 91990018R00020001

small or large business subcontractors) shall provide evidence that any proposed subcontractor or consultant has agreed to perform the work specified in the proposal, is fully capable of performing the assigned tasks, and that the offeror has effective control of the subcontractor’s/ consultant’s work on the project.

Organizational Capabilities, Experience & Resources: This section shall describe pertinent corporate experience and qualifications in conducting the tasks outlined in the PWS. The technical proposal must contain an organizational chart and a statement relating corporate experience to the subtask areas in this project. The technical proposal must contain an internal quality control plan that addresses accountability in each subtask area. The offeror must include links to materials or provide high quality samples of materials that have been developed to communicate research findings to the public.

Short abstracts of current work shall include the name, current affiliation, current email address, and current telephone number of the study's project officer. This section should briefly identify resources (other than personnel), such as facilities and equipment that is available for use in carrying out the activities of this project. Applicable corporate experience should include evidence of managing large-scale multi-site education studies that involve: challenging large-scale study recruitment; random assignment in an education setting; implementation support;

collection and analysis of quantitative and qualitative data including sophisticated correlational analyses and collection/analyses of classroom observation data; content knowledge of postsecondary education and preparation interventions; prior successful work in conducting evidence reviews and communicating the findings of such reviews to diverse audiences.

Sample Reports. In the “sample reports” appendix, the offeror shall provide exemplars of its prior or current work conducting research and evaluation studies, or systematic evidence reviews and conveying the content of the work and its findings to a policy audience. Specifically, in this appendix, the contractor shall provide two (and no more than two) research/evaluation papers or reports (or parts of papers or reports) that the contractor has conducted within the last three years. The papers or reports provided should demonstrate the contractor’s commitment to quality, rigor, relevance, and usefulness to policy-makers. There is no overall page limit for the sample research reports appendix. However, each report may be no longer than 8 single-spaced pages or 15 double-spaced pages; though, the following pages do not count toward this page limit: (i) table of contents, (ii) title page, (iii) other introductory pages. If an individual report exceeds the page limit, the offeror shall instead provide an excerpt that includes relevance, methodology, and analysis. Neither of the two samples submitted may have been revised to reflect any comments from IES or other federal oversight. Each exemplar shall include the following written assurance on its cover sheet: “This document does not reflect any comments from IES or other federal oversight.” The offeror may choose to develop a product for this proposal if one does not exist.

Past Performance Offerors shall provide evidence of prior successful work in the following areas: (1) the assessment and synthesis of studies of the effectiveness of polices, programs, practices, or products focused on improving outcomes in the areas of early childhood education, elementary education, or secondary education; (2) the use of analytic techniques to summarize results across intervention studies and report these results clearly and accurately; and (3) the

PAGE 20 OF 27 91990018R00020001

production of engaging reports and other web-accessible documents and tools that communicate the results of technically complex research in plain language to decision makers and other stakeholders with limited technical expertise. Offerors may also provide evidence of successful past performance in other areas not mentioned in the preceding text but required for successful contract performance. Pat performance information shall be provided in the technical proposal volume. Consideration of the offeror’s reputation in terms of quality, problem resolution, cost control, timeliness, business relations, and customer service will be evaluated.

In addition to the above, the offeror shall submit information about its four most recent contracts

– either completed in the last three years or currently-in-process (so long as at least 12 months of performance have occurred) – that are of similar size, scope, complexity or are, in any way, relevant to the effort required by this solicitation.