W912DR17Q0006.pdf

SEE ADDENDUM

(No Collect Calls)

W912DR17Q0006 06-Jul-2017

b. TELEPHONE NUMBER

410-962-3463

8. OFFER DUE DATE/LOCAL TIME

10:00 AM 21 Jul 2017

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

W912DR9. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

PATRICIA MORROW

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

0 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

USACE, BALTIMORE DISTRICT

10 S. HOWARD ST

ROOM 7000

BALTIMORE MD 21201

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE 16. ADMINISTERED BY

SEE SCHEDULE

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

FAX:

TEL: 410-962-2196 SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$27,500,000

NAICS:

541519

X

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

PAGE 2 OF60

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT

41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

W912DR17Q0006

Section SF 30 - BLOCK 14 CONTINUATION PAGE

INSTRUCTIONS

Instructions of Offerors:

The U.S. Army Corps of Engineers, Baltimore District, has a requirement for Enterprise Data Warehouse Report Writing support.

Contractors shall submit their quotes Contract Specialist, Patricia Morrow, via email patricia.l.morrow@usace.army.mil no later than the time and date specified on Standard Form 1449, Block 8.

Quotes shall contain a cover letter summarizing the pricing total and outlining quotes terms and conditions, signed by the representative managing the project. Please include the Cage Code, Duns # and Tax ID.

The offeror shall submit a technical write-up to be evaluated.

The offeror shall submit up to 3 projects similar to the work requested in the Performance Work Statement completed in the past 3 years. Please include project title, dollar value, performance period, client and a contact’s name, address, and phone number and/or email for verification.

The offeror shall complete the provided bid schedule to include the labor disciple and rate being quoted.

Please direct all questions to Contract Specialist, Patricia Morrow, via email patricia.l.morrow@usace.army.mil. Do not contact any other personnel regarding this project. Please submit all questions no later than 13 July 2017.

Evaluation Criteria:

The quotes will be evaluated to determine whether the Offeror’s methods and approach have both addressed and meet all the solicitation requirements. Offerors MUST NOT MERELY REPEAT BACK the requirements stated in the Request for Quote (RFQ), but must provide narrative evidence in support of any conclusive statements relating to proposed capabilities or performance. Unsupported capabilities to comply with the requirements will not be sufficient.

The award will be based on the best overall proposal that is determined to be the most beneficial to the Government, with appropriate consideration given to the three (3) evaluation factors: 1) Technical, 2) Past Performance, and 3) Price. The evaluation factors are in descending order of importance with the most important listed first: Technical is more important than Past Performance. All non-priced factors combined are significantly more important than Cost/Price.

To receive consideration for award, a rating of no less than “Acceptable” must be achieved for the Technical factor.

Offerors will be cautioned that the award may not necessarily be made to the lowest price offered.

The evaluation process will consider the following:

1. Factor 1: Technical

Understanding of the Problem/Feasibility of Approach - The proposal will be evaluated to determine the extent to which it demonstrates a clear understanding of all requirements in the Performance Work Statement (PWS). This includes the understanding of potential problems and feasibility of resolutions proposed as demonstrated in the plans submitted as part of the Offeror’s response.

The following elements are to be considered when determining technical rating:

1. Writing 5 or more Crystal Reports joining data from 3 or more CEFMS tables and successfully having them migrated to USACE EDW Production Environment.

2. Writing 5 or more Crystal Reports creating new DLOVs and successfully having them migrated to USACE EDW Production Environment.

3. Writing 5 or more Crystal Reports including parent-child relationship queries, sub-queries, or recursive relationship queries and successfully having them migrated to USACE EDW Production Environment.

4. Completion of Enterprise Data Warehouse (EDW) Introductory Training.

5. Completion of EDW Dynamic List of Values (DLOV) Training.

The Technical Factor Rating, described below, focus on the strengths, deficiencies, weaknesses, risks and uncertainties of the Offeror’s proposal.

Table A-1. Technical Ratings

Rating Description

Outstanding

Proposal meets requirements and indicates an exceptional approach and understanding of the requirements. Strengths far outweigh any weaknesses. Risk of unsuccessful performance is very low.

Good

Proposal meets requirements and indicates a thorough approach and understanding of the requirements. Proposal contains strengths which outweigh any weaknesses. Risk of unsuccessful performance is low.

Acceptable

Proposal meets requirements and indicates an adequate approach and understanding of the requirements. Strengths and weaknesses are offsetting or will have little or no impact on contract performance. Risk of unsuccessful performance is no worse than moderate.

Marginal

Proposal does not clearly meet requirements and has not demonstrated an adequate approach and understanding of the requirements. The proposal has one or more weaknesses, which are not offset by strengths. Risk of unsuccessful performance is high.

Unacceptable

Proposal does not meet requirements and contains one or more deficiencies. Proposal is unawardable.

2. Factor 2: Past Performance

The Past Performance evaluation will assess the Offeror’s acceptability/unacceptability in successfully performing the solicitation's requirements as indicated by that Offeror’s record of past performance for a period of three (3) years prior to the release of this solicitation. In this context, “Offeror” refers to the proposed prime contractor and all proposed major subcontractors. A major subcontractor is defined as one who will be providing critical hardware or services and/or whose subcontract is more than 20% of the total proposed price. In either case, the prime contractor and proposed major subcontractors will be assessed individually and the results will then be assessed in their totality to derive the Offeror’s Past Performance rating.

When assessing past performance, the Government will focus its inquiry on the past performance of the Offeror and its proposed major subcontractors as it relates to all solicitation requirements. These requirements include all aspects of, performance, including, but not limited to, the Offeror’s record for:

Compliance of products, services, documents, and related deliverables to specification requirements and standards of good workmanship

Effectiveness of project management (to include use and control of subcontractors) Timeliness of performance for services and product deliverables, including the administrative aspects of performance, the ability to meet surge requirements and accelerated delivery schedules Commitment to customer satisfaction and business-like concern for customer’s interest Overall satisfaction

Offerors are cautioned that in conducting the past performance assessment, the Government may use data provided in the Offeror’s proposal and data obtained from other sources. Since the Government may not necessarily interview all of the sources provided by the Offerors, it is incumbent upon the Offerors to explain the relevance of the data provided. Offerors are reminded that while the Government may elect to consider data obtained from other sources, the burden of proving a reasonable expectation that the Offeror will be able to successfully perform the required effort rests with the Offerors.

The past performance evaluation will result in an assessment of the Offeror’s probability of meeting the minimum solicitation requirements. The Past Performance assessment will be based on the Offeror’s record of relevant and recent past performance information that pertains to the products and/or services outlined in the solicitation requirements and how well the contractor performed on those contracts. Past Performance will be rated on an “acceptable” or “unacceptable” basis using the ratings in Table A-2 below.

The Government may use data provided by the Offeror in its proposal and data obtained from other sources, including data in Government files or data obtained through interviews with personnel familiar with the contractor’s current and past performance under Federal, State or Local government or commercial contracts for same or similar efforts of the same scope and complexity. Data used in conducting past performance evaluations shall not extend past three years prior to the issue date of the RFQ, but may include performance data generated during the past three years without regard to the contract award date.

Table A-2. Past Performance Evaluation Ratings

Rating Description

Acceptable Based on the Offeror’s performance record, the Government has a reasonable expectation that the Offeror will successfully perform the required effort, or the Offeror’s performance record is unknown.

Unacceptable

Based on the Offeror’s performance record, the Government has no reasonable expectation that the Offeror will be able to successfully perform the required effort.

3. Factor 3: Price

The Government will evaluate offers for award purposes by adding the total of all CLIN prices to ensure pricing is not unbalanced. Prices will be evaluated for fairness and reasonableness.

The following will be evaluated:

(1) Fair and Reasonableness

(2) Completeness, Accuracy, and Balance of the Proposed Labor Rates and Loadings.

For evaluation purposes only, the Total Evaluated Price shall consist of the sum of the evaluated prices of the CLINS for the base plus four option period contract years.

An offer may be rejected if the Contracting Officer determines that the lack of balance poses an unacceptable risk to the Government.

The Contracting Officer anticipates adequate price competition; however, in the event only one Offeror responds to this solicitation or adequate price does not exist, the Contracting Officer reserves the right to request additional data to support all proposed pricing.

PWS

30 June 2017

PERFORMANCE WORK STATEMENT

Enterprise Data Warehouse Report Writing Support Project U.S. Army Corps of Engineers

Baltimore District

1. Introduction: The intent of this project is for the U.S. Army Corps of Engineers (USACE) Resource Management to obtain an Expert SQL programmer as the Baltimore District has no in-house capability/expertise to modify existing reports and creating additional reports as requested through the Enterprise Data Warehouse (EDW) helpdesk tickets and/or the Corporate Business Report (CBR) Program Manager.

2. Background: Baltimore District facilitated the shutdown of CBR and transitioned approximately 500 existing reports into the EDW system. All queries/reports were recreated in EDW using official USACE established procedures, and utilized Crystal Reports, Aginity, SQL, and PL/SQL.

3. General Requirements: The objective is to ensure all current reports are modified per USACE needs and converting alternate formats of existing reports. The programmer will work with the regional Project Development Team (PDT) through the CBR Program Manager, to create a dashboard reporting a variety of budget information.

The programmer will create and modify reports for USACE’s mandated reporting system, EDW, using Crystal Reports and Aginity Workbench for Netezza. The reports will primarily use tables copied from the Corps of Engineers Financial Management System (CEFMS). The programmer will create Dynamic Lists of Values (DLOVs) in Crystal Reports and join multiple tables together when creating reports. The reports will include parent-child relationship queries, sub-queries, and recursive relationships. All reports and DLOVs created must comply with the USACE standard procedures to migrate the reports from the Development database to the Production database. The programmer must have thorough knowledge of the fields contained within CEFMS data tables and a firm understanding of the needs, policies, and business practices of the USACE financial management and project management personnel. The programmer must be a Certified Oracle Developer. The contractor programmer must be able to begin programming reports, creating dynamic lists of values and submitting migration requests for reports using the standard USACE required procedures within forty (40) hours of notice to proceed with minimal or no training required in order to meet helpdesk deadlines for tickets.

4. Performance Requirements: The contractor shall use software description noted in 6.1 below to modify current reports from the EDW system per USACE needs. For all requirements, the contractor will outline a methodology, develop a timeline for completion, and alert the COR of any requirement expected to require more than forty (40) hours of effort. Further, if any requirement requires additional tables or fields or if the requirement cannot be completed based on the restrictions of the software and/or the EDW system, the COR must be alerted immediately upon discovery of the problem. Written status reports are requested by the government on a monthly basis, with the contractor providing an invoice and supporting documentation such as time sheets and a status update for all work performed during the month. All contractor products, when accepted by the government, become property of the government and may be modified and used by the government as it sees fit. Queries/reports should be executable by general district users. All reports and dashboards must pass migration team testing, be migrated to the production environment, and be proven to work as intended in the production environment, for the task to be considered completed and accepted by the government.

The contractor will modify existing CBR reports in EDW with errors found by user testing in the Production environment. User testing is the third level of testing. All reports go through basic testing by the COR before they can be submitted for migration and EDW Migration Team testing before they can be migrated from the Development to the Production Environment. Helpdesk tickets and user requests provided to the COR will be forwarded to the contractor and acknowledgement of receipt must be received from the contractor within two (2) working days. Updates should be completed within ten (10) working days, or a detailed status update must be provided with an estimated date of completion if more than ten (10) working days is required. Documentation shall be provide per report to include PDF or Excel files of the modified report, a copy of the Crystal Reports code, and confirmation of submission of the report for migration.

The contractor will create new EDW financial reports as requested by users. Helpdesk tickets or requests sent directly to the program manager will be forwarded to the contractor and acknowledgement of receipt must be received from the contractor within two (2) working days. An estimated date of completion will be provided to the COR within five (5) working days. If the estimated date of completion is missed, a status update and new estimated date of completion must be submitted to the COR. Documentation shall be provide per report to include PDF or Excel files of the new report, a copy of the Crystal Reports code, and confirmation of submission of the report for migration.

The contractor will modify or create copies of up to 500 existing Crystal Reports in EDW so that the user can select a prior fiscal year on which to run the reports. Reports are limited in the number of parameters allowed, so copies will be required when all allowable parameters are used in the original report. Copies may also be required when the original report is intended to only run for the current fiscal year (CFY), in which case the new report would be designated for prior fiscal years (PFY). In the case of copies when all available parameters are used, the COR will review the report with the programmer to determine if the Fiscal Year selection can replace another parameter.

Documentation shall be provide per report to include PDF or Excel files of the modified report, a copy of the Crystal Reports code, and confirmation of submission of the report for migration.

The contractor will convert approximately 200 additional CBR reports to Crystal Reports using the original report code to mimic availability in CBR. The contractor will use the original Oracle PL/SQL report and change it to use the more generic ANSI SQL in Crystal Reports and Aginity. Documentation shall be provide per report to include PDF or Excel files of the original CBR report (if possible) and the new EDW version for comparison and initial testing, a copy of the Crystal Reports code, and confirmation of submission of the report for migration.

The contractor will support the North Atlantic Division Budget Officers to develop at least 7 dashboards presenting budget data for each district and the division as a whole. The programmer will attend meetings of the dashboard team via conference call or in person when then meetings are held locally. The contractor will submit migration requests using USACE standard procedures and provide confirmation of submission. The contractor will provide a PDF file of the final look of the dashboard and a copy of the Crystal Reports code. Dashboards, when accepted by the government, become property of the government and may be modified and used by the government as it sees fit.

Dashboards should be executable by general district users.

5. Deliverables:

Deliverable #1– Documentation The contractor shall provide all documentation as described in Section 4 to include requirements, design concerns, and reports code for EDW reports and dashboards. Documentation will include Excel or PDF reports of the original report (CBR or EDW) and the new report for comparison, a PDF of the final dashboard, a PDF of the final EDW code, and confirmation of submission of the request for migration on the EDW SharePoint site as indicated in Section 3.5.

Deliverable #2 – Monthly Project Status Reports

The contractor shall provide a monthly project status report to the COR which shall be submitted not later than five (5) working days after the end of the month as follows:

At a minimum, the monthly status report shall contain a discussion, by task, detailing all major accomplishments, problems, resources utilized, products and services delivered during the invoiced period, the specific contractor employee assigned to the project and the number of man-hours performed by labor category during the invoice period. The report may be submitted via email.

6. Special Requirements:

6.1. Services The Government will provide software licenses for PL/SQL, SQL, C/C++, Oracle Pro*C, SAP BusinessObjects, and Crystal Reports in a Sun or Windows NT environment, as required, for report development. The Government will provide access to the following teleprocessing service: USACE WAN and SQL*Net, as well as to CEFMS, CBR and EDW.

6.2. Facilities The Government will provide a workspace in the Baltimore District.

6.3. Equipment The Government will provide access to a laptop, telephone, and multi-function devices for printing, scanning, and copying.

7. Period of Performance: The awarded contract shall consist of a base year and four (4) option years.

8. Site Security. All personnel working on this project will be required to follow all security and access rules and regulations (i.e., physical access and/or network access requirements) as set forth by the U.S. Government in order to gain access to the USACE offices and/or systems to perform work assignments and/or for the delivery of equipment. Foreign Nationals are not authorized to perform work on this contract. The vendor will complete/comply with all of the following:

9. Non-Personal Services. The Government shall neither supervise contractor employees nor control the method by which the contractor performs the required specifications stated in the performance work statement. Under no circumstances shall the Government assign tasks to, or prepare work schedules for, individual contractor employees.

It shall be the responsibility of the contractor to manage its employees and to guard against any actions that are of the nature of personal services, if the contractor believes that any actions constitute, or are perceived to constitute personal services, it shall be the contractor's responsibility to notify the Contracting Officer Representative (COR) immediately.

10. Location of Work Performance: Work is to be accomplished at on-site at the Baltimore District Offices, currently at the City Crescent Building.

11. COR shall inspect all Services performed by the Contractor in accordance with the PWS and through the final reports and provide feedback and acknowledgement of acceptance by the customer of the deliverables.

12. Delivery: Delivery of all documents (see Section 5-Deliverables) shall be emailed to the COR; Delivery shall be made by submitting a request for migration via adding a new item to the EDW SharePoint site for the regional reports submission list. The migration must be approved by the EDW migration team and the reports must be made available in the EDW production database.

13. Attachment/Technical Exhibit List:

13.1. Attachment 1/Technical Exhibit 1 – Performance Requirements Summary

13.2. Attachment 2/Technical Exhibit 2 – Deliverables Schedule

13.3. Attachment 3 – OPSEC Requirements

TECHNICAL EXHIBIT 1

Performance Requirements Summary

The contractor service requirements are summarized into performance objectives that relate directly to mission essential items. The performance threshold briefly describes the minimum acceptable levels of service required for each requirement. These thresholds are critical to mission success.

Performance Objective Standard Performance

Threshold Method of Surveillance

PRS # 1.

Modify reports or create new output versions of reports

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

100% of reports shall meet the standard and the timeline for converting reports shall not lag more than 10% from the estimated date of completion provided by the contractor.

Periodic Sampling

PRS # 2

Provide monthly status report timely to COR

A report is provided each month within five (5) business days of the end of the previous month.

Report shall be 100% accurate and delivered on time.

100% Inspection

PRS # 3

Provide all required documentation timely

Documents must be provided to COR no later than the one (1) week after completion.

All required documentation shall be submitted with not more than 10% lag from the standard.

Periodic Sampling

PRS # 4

Provide timely notification on items requiring government action.

All items requiring government action must be reported within one

(1) business day of discovery.

100% notification within one (1) day of discovery.

Per Occurrence

PRS #5

Create dashboards for budget data

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

100% of dashboards shall meet the standard and the timeline for converting reports shall not lag more than 10% from the estimated date of completion provided by the contractor.

100% Inspection

TECHNICAL EXHIBIT 2

DELIVERABLES SCHEDULE

Deliverable Frequency # of Copies Medium/Format Submit To

New/Modified Reports and New Output formats of reports

Weekly or As Completed (at the discretion of the developer)

1 Upload copies of original and new/modified reports for comparison and PDF of final EDW code to the shared drive. Email confirmation of submitted migration request.

COR, EDW SharePoint site

Dashboards As completed 1 Upload PDF “printout” of the Dashboard and PDF of the final EDW code to the shared drive. Email confirmation of submitted migration request.

COR

Monthly Status Reports

Monthly, by the 5th business day of the month

1 Email COR

OPSEC Requirements

AT Level I Training

All contractor employees, to include subcontractor employees, requiring access to Army installations, facilities, controlled access areas, or require network access, shall complete AT Level I awareness training within 30 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever is applicable. Upon request, the contractor shall submit certificates of completion for each affected contractor employee and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at the following website: http://jko.jten.mil/courses/atl1/launch.html; or it can be provided by the RA ATO in presentation form which will be documented via memorandum.

Access and General Protection/Security Policy and Procedures

All contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation/facility access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification of Contractor Personnel) as directed by DOD, HQDA and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any installation or facility change, the Government may require changes in contractor security matters or processes.

For contractors requiring Common Access Card (CAC).

The contractor and all sub-contractors employees will be issued a CAC only if duties involve one of the following:

(1) Both physical access to a DoD facility and access, via logon, to DoD networks on-site or remotely; (2) Remote access, via logon, to a DoD network using DoD-approved remote access procedures; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. At the discretion of the sponsoring activity, an interim CAC may be issued based on a favorable review of the FBI fingerprint check and a successfully scheduled NACI at the Office of Personnel Management.

Suspicious Activity Reporting Training

The contractor and all associated sub-contractors shall receive a brief/training (provided by the RA) on the local suspicious activity reporting program. This locally developed training will be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the project manager, security representative or law enforcement entity. This training shall be completed within 30 calendar days of contract award and within 30 calendar days of new employees commencing performance with the results reported to the COR NLT 5 calendar days after the completion of the training.

Contractor Employees Who Require Access to Government Information Systems

All contractor employees with access to a government info system must be registered in the Army Training Certification Tracking System (ATCTS) at commencement of services, and must successfully complete the DOD Information Assurance Awareness prior to access to the information systems and then annually thereafter in accordance with personnel security standards listed in AR 25-2 (Information Assurance), an appropriate background investigation will be conducted prior to accessing the government information systems.

For Contracts that Require OPSEC Training

All new contractor employees will complete Level I OPSEC Training within 30 calendar days of their reporting for duty. Additionally, all contractor employees must complete annual OPSEC awareness training. The contractor shall submit certificates of completion for each affected contractor and subcontractor employee, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training. OPSEC awareness training is available at the following websites: https://www.iad.gov/ioss/ or http://www.cdse.edu/catalog/operations-security.html; or it can be provided by the RA OPSEC Officer in presentation form which will be documented via memorandum.

For Information Assurance (IA)/Information Technology (IT) Training

All contractor employees and associated sub-contractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoDD 8570.01, DoD 8570.01-M and AR 25-2 within six months of employment.

The Contractor will be escorted in areas where they may be exposed to classified and/or sensitive materials and/or sensitive or restricted areas

All contract employees, including subcontractor employees who are not in possession of the appropriate security clearance or access privileges, will be escorted in areas where they may be exposed to classified and/or sensitive materials and/or sensitive or restricted areas.

Pre-Screen Candidates Using E-Verify Program

The Contractor must pre-screen Candidates using the E-verify Program (http://www.uscis.gov/e-verify) website to meet the established employment eligibility requirements. The Vendor must ensure that the Candidate has two valid forms of Government issued identification prior to enrollment to ensure the correct information is entered into the E-verify system. An initial list of verified/eligible Candidates must be provided to the COR no later than 3 business days after the initial contract award.

Threat Awareness Reporting Program

All new contractor employees will complete annual Threat Awareness and Reporting Program (TARP) Training provided by a Counterintelligence Agent, IAW AR 381-12. The contractor shall submit certificates of completion for each affected contractor and subcontractor employee(s) or a memorandum for the record, to the COR or to the contracting officer (if a COR is not assigned), within 5 calendar days after completion of training. Authorized web-based TARP training for CAC card holders is available at the following website:

https://www.us.army.mil/suite/page/655474.

QASP

QUALITY ASSURANCE SURVEILLANCE PLAN

For CBR/EDW Programming Support Contract Number: W912DR-17-X-XXXX

Contract Description: Professional contract support to develop and maintain production reports.

Contractor’s name: TBD (hereafter referred to as the contractor).

1. PURPOSE.

This Quality Assurance Surveillance Plan (QASP) provides a systematic method to evaluate performance for the stated contract. This QASP explains the following:

What will be monitored.

How monitoring will take place.

Who will conduct the monitoring.

How monitoring efforts and results will be documented.

This QASP does not detail how the contractor accomplishes the work. Rather, the QASP is created with the premise that the contractor is responsible for management and quality control actions to meet the terms of the contract. It is the Government’s responsibility to be objective, fair, and consistent in evaluating performance. In addition, the QASP should recognize that unforeseen and uncontrollable situations may occur.

This QASP is a “living document” and the Government may review and revise it on a regular basis. However, the Government shall coordinate changes with the contractor. Updates shall ensure that the QASP remains a valid, useful, and enforceable document. Copies of the original QASP and revisions shall be provided to the contractor and Government officials implementing surveillance activities.

This QASP was developed to comply with the Federal Acquisition Regulation (FAR), Subpart 37.6, Performance Based Acquisition and 46.4, Government Contract Quality Assurance. In addition, FAR, Subpart 46.103, Contracting Officer Responsibilities, states that agencies shall develop quality assurance surveillance plans when acquiring services.

2. GOVERNMENT ROLES AND RESPONSIBILITIES.

The following personnel shall oversee and coordinate surveillance activities.

a. Contracting Officer (KO) - The KO shall ensure performance of all necessary actions for effective contracting, ensure compliance with the contract terms, and shall safeguard the interests of the United States in the contractual relationship. The KO shall also assure that the contractor receives impartial, fair, and equitable treatment under this contract. The KO is ultimately responsible for the final determination of the adequacy of the contractor’s performance.

Assigned KO: Sharon Alexander Organization or Agency: Baltimore District, US Army Corps of Engineers Telephone: 410-962-0191 Email: Sharon.L.Alexander@usace.army.mil

b. Contract Specialist - The Contract Specialist acts as an acquisition consultant and serves as the liaison between the contractor and the KO.

Assigned Contract Specialist: Patricia Morrow Telephone: 410-962-3463 Email: patricia.l.morrow@usace.army.mil

c. Contracting Officer’s Representative (COR) - The COR is responsible for technical administration of the contract and shall assure proper Government surveillance of the contractor’s performance. The COR shall keep a quality assurance file. At the conclusion of the contract or when requested by the KO, the COR shall provide documentation to the KO. The COR is not empowered to make any contractual commitments or to authorize any contractual changes on the Government’s behalf. The contractor shall refer any changes they deem may affect contract price, terms, or conditions to the KO for action.

Assigned COR: Khrystina Campana Telephone: 410-962-3639 Email: Khrystina.N.Campana2@usace.army.mil

d. Other Key Government Personnel – Idana Folson Title: Deputy, Resource Management Office Telephone: 410-962-3818 Email: Idana.A.Folson@usace.army.mil

3. CONTRACTOR REPRESENTATIVES:

The following employees of the contractor serve as the contractor’s Primary and Alternate Point of Contact for this contract.

a. Primary Point of Contact - <upon award, enter name> Telephone: <enter number> Email: <enter address>

b. Alternate Point of Contact - <upon award, enter name> Telephone: <enter number> Email: <enter address>

c. Other Contractor Personnel - <upon award, enter name or delete these lines if not applicable> Title: <enter title> Telephone: <enter number> Email: <enter address>

4. PERFORMANCE STANDARDS.

Performance standards define desired services. The Government performs surveillance to determine if the contractor exceeds, meets or does not meet these standards.

The Performance Requirements Summary Matrix (PRS), Technical Exhibit 1 in the Performance Work Statement includes performance standards. The Government shall use these standards to determine contractor performance and shall compare contractor performance to the PRS thresholds.

Performance Objective Standard Performance Threshold

Method of Surveillance

PRS # 1.

Modify reports currently in

EDW

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

100% of reports shall meet the standard with not more than 10% of modifications taking more than 10 days each

100% Inspection

PRS # 2

Create new reports in EDW

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

100% of reports shall meet the standard with not more than 10% lag from the contractor plan.

100% Inspection

PRS # 3

Modify up to 500 existing reports in EDW for use with prior fiscal year data

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

100% of reports shall meet the standard with not more than 10% of modifications taking more than 10 days each

100% Inspection

PRS # 4

Convert approximately 200 reports from Oracle PL/SQL to Crystal Reports and migrate to EDW Production Environment

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

100% of reports shall meet the standard with not more than 10% lag from the contractor plan.

100% Inspection

PRS # 5

Provide all required documentation timely

No more than 10% of the documents may be provided to COR later than the specified time period in the Project Plan.

All required documentation shall be submitted with not more than 10% lag from the project plan.

Periodic Sampling

PRS # 6

Provide timely notification on items requiring government action.

All items requiring government action must be reported within 1 business day of discovery.

100% notification within 1 day of discovery.

Per Occurrence

PRS #7

Provide monthly status report timely to COR.

A report is provided each month within 5 business days of the end of the previous month.

Report shall be 100% accurate and delivered on time.

100% Inspection

5. METHODS OF QA SURVEILLANCE.

Various methods exist to monitor performance. The COR shall use the surveillance methods listed below in the administration of this QASP.

Regardless of the surveillance method, the COR shall always contact the contractor's primary point of contact when a defect is identified and inform the point of contact of the specifics of the problem. The COR shall be responsible for monitoring the contractor’s performance in meeting a specific performance standard.

a. 100% INSPECTION.

Provide monthly status report timely to COR.

Timely completion and delivery of Project Plan.

b. PERIODIC SAMPLING.

Provide all required documentation timely (ex. technical documentation, requirements, design, and reports documents).

Transition all reports from CBR into EDW

c. PER OCCURRENCE.

Provide timely notification on items requiring government action

6. RATINGS.

Metrics and methods are designed to determine if performance exceeds, meets, or does not meet a given PRS standard. A rating scale shall be used to determine a positive, neutral, or negative outcome. The following ratings shall be used:

PRS # 1-4

SATISFACTORY:

All reports (tasks) confirmed by the COR are created in EDW, published to the production database, and function as agreed upon.

UNSATISFACTORY:

Reports are not created, are delivered after agreed upon delivery date, or do not function as agreed upon.

PRS #5:

SATISFACTORY:

No more than 10% of the documents are provided to COR later than the specified time period in the Project Plan.

UNSATISFACTORY:

More than 10% of the documents are provided to COR later than the specified time period in the Project Plan.

PRS #6:

Notification on items requiring government action within 1 business days of discovery.

UNSATISFACTORY:

No notification or notification of items requiring government action after 1 business days of discovery.

PRS #7:

Complete and thorough monthly status report is delivered by the fifth working day of the month.

UNSATISFACTORY:

Monthly status report is incomplete, delivered after the fifth working day of the month, or is not delivered.

7. DOCUMENTING PERFORMANCE.

a. ACCEPTABLE PERFORMANCE.

The Government shall document positive performance. A report template is attached. Any report may become a part of the supporting documentation for fixed fee payments, award fee payments, or other actions.

b. UNACCEPTABLE PERFORMANCE.

When unacceptable performance occurs, the COR shall inform the contractor. This will normally be in writing unless circumstances necessitate verbal communication. In any case the COR shall document the discussion and place it in the COR file and courtesy copy the KO.

When the COR determines formal written communication is required, the COR shall prepare a Contract Discrepancy Report (CDR), and present it to the contractor's primary or alternate point of contact. A CDR template is attached to this QASP.

The contractor shall acknowledge receipt of the CDR in writing. The CDR will specify if the contractor is required to prepare a corrective action plan to document how the contractor shall correct the unacceptable performance and avoid a recurrence. The CDR will also state how long after receipt the contractor has to present this corrective action plan to the COR. The Government shall review the contractor's corrective action plan to determine acceptability.

Any CDRs may become a part of the supporting documentation for contract payment deductions, fixed fee deductions, award fee nonpayment, or other actions deemed necessary by the KO.

8. FREQUENCY OF MEASUREMENT.

a. Frequency of Measurement.

During contract/order performance, the COR shall take periodic measurements, bi-monthly, as specified in the PRS matrix, and shall analyze whether the negotiated frequency of measurement is appropriate for the work being performed.

b. Frequency of Performance Assessment Meetings.

The COR shall meet with the contractor semi-annually to assess performance and shall provide a written assessment on an annual basis. This applies to the base contract and any awarded option years.

9. DOCUMENTING EVALUATIONS

a. Payment Deductions

Due to the critical nature of the support, the Contractor’s performance will be compared to contract requirements on a monthly basis against the Acceptable Quality Levels using this Quality Assurance Surveillance Plan to guide evaluations and the 100% Inspections, Direct Observation, and Period Sampling to document findings. If the performance in any required service fails to meet the performance threshold identified in the PWS, payments to the contractor may be reduced by the contracting officer.

The Government’s primary quality assurance procedures are based on validated customer complaints and incidental inspections by the Contracting Officer’s Representative (COR).

Prepared by: Khrystina Campana

Signature – Contracting Officer’s Representative

PERFORMANCE REPORT

1. CONTRACT NUMBER: <insert number>

2. Prepared by: (Name of COR) <insert name>

3. Date and time of observation:

4. Observation:

<Examples of items to include in a report are:

- Method of surveillance.

- How frequently you conducted surveillance.

- Surveillance results.

- Number of observations.>

Prepared by: <Enter COR’s name>

Signature – Contracting Officer’s Representative Date

CONTRACT DISCREPANCY REPORT (CDR)

1. Contract Number: <insert number>

2. TO: (Contractor Point of Contact) <insert name>

3. FROM: (Name of COR) <insert name>

4. Date and time observed discrepancy:

5. Source of Complaint:

6. Discrepancy of Problem:

<Describe in detail. Identify any attachments.>

7. Corrective action plan:

A written corrective action plan < is / is not > required.

< If a written corrective action plan is required include the following. > The written Corrective Action Plan will be provided to the undersigned not later than < # days after receipt of this

CDR. >

8. Government actions (payment deductions, performance evaluation meetings, or other actions):

Prepared by: <Enter COR’s name>

Signature – Contracting Officer’s Representative Date

Received by:

Signature - Contractor Task Manager or on-site representative Date

< The COR may initiate a CDR at any time, including whenever the number of monthly recorded defects for a performance standard exceeds the allowable number of defects; anytime unacceptable performance is determined critical in nature and requires formal corrective action; and whenever an unfavorable trend is detected in contractor performance.>

Section SF 1449 - CONTINUATION SHEET

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 1 Job

BASE YEAR

FFP

Job Category Estimated Hours $_____/ Hr.

FOB: Destination

NET AMT

0002 1 Job

OPTION YEAR 01

FFP

Job Category Estimated Hours

0003 1 Job

OPTION YEAR 02

FFP

Job Category Estimated Hours

0004 1 Job

OPTION YEAR 03

FFP

Job Category Estimated Hours

0005 1 Job

OPTION YEAR 04

FFP

Job Category Estimated Hours

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 N/A N/A N/A Government 0002 N/A N/A N/A Government 0003 N/A N/A N/A Government 0004 N/A N/A N/A Government 0005 N/A N/A N/A Government

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 N/A N/A N/A N/A

0002 N/A N/A N/A N/A

0003 N/A N/A N/A N/A

0004 N/A N/A N/A N/A

0005 N/A N/A N/A N/A

CLAUSES INCORPORATED BY REFERENCE

52.202-1 Definitions NOV 2013 52.203-3 Gratuities APR 1984 52.203-17 Contractor Employee Whistleblower Rights and Requirement

To Inform Employees of Whistleblower Rights

APR 2014

52.204-4 Printed or Copied Double-Sided on Postconsumer Fiber Content Paper

MAY 2011

52.204-7 System for Award Management OCT 2016 52.204-9 Personal Identity Verification of Contractor Personnel JAN 2011 52.204-10 Reporting Executive Compensation and First-Tier

Subcontract Awards

OCT 2016

52.204-16 Commercial and Government Entity Code Reporting JUL 2016 52.204-19 Incorporation by Reference of Representations and

Certifications.

DEC 2014

52.209-7 Information Regarding Responsibility Matters JUL 2013 52.209-10 Prohibition on Contracting With Inverted Domestic

Corporations

NOV 2015

52.212-4 Contract Terms and Conditions--Commercial Items JAN 2017 52.215-20 Requirements for Certified Cost or Pricing Data or

Information Other Than Certified Cost or Pricing Data

OCT 2010

52.217-5 Evaluation Of Options JUL 1990 52.217-8 Option To Extend Services NOV 1999 52.217-9 Option To Extend The Term Of The Contract MAR 2000 52.224-1 Privacy Act Notification APR 1984 52.228-5 Insurance - Work On A Government Installation JAN 1997 52.229-3 Federal, State And Local Taxes FEB 2013 52.232-1 Payments APR 1984 52.232-8 Discounts For Prompt Payment FEB 2002 52.232-39 Unenforceability of Unauthorized Obligations JUN 2013 52.233-1 Disputes MAY 2014 52.233-3 Protest After Award AUG 1996 52.233-4 Applicable Law for Breach of Contract Claim OCT 2004 52.237-2 Protection Of Government Buildings, Equipment, And

Vegetation

APR 1984

52.237-3 Continuity Of Services JAN 1991 52.242-13 Bankruptcy JUL 1995 52.243-1 Alt I Changes--Fixed Price (Aug 1987) - Alternate I APR 1984 52.246-1 Contractor Inspection Requirements APR 1984 52.253-1 Computer Generated Forms JAN 1991 252.201-7000 Contracting Officer's Representative DEC 1991 252.203-7005 Representation Relating to Compensation of Former DoD

Officials

NOV 2011

252.204-7000 Disclosure Of Information OCT 2016 252.204-7003 Control Of Government Personnel Work Product APR 1992 252.204-7008 Compliance With Safeguarding Covered Defense Information

Controls

OCT 2016

252.204-7011 Alternative Line Item Structure SEP 2011 252.204-7015 Notice of Authorized Disclosure of Information for Litigation

Support

MAY 2016

252.209-7004 Subcontracting With Firms That Are Owned or Controlled By The Government of a Country that is a State Sponsor of Terrorism

OCT 2015

25…