AMD 2 21R9001 GPAT Form.pdf

HE125421R9001

HF 1026114421

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

Except as p rovid ed herein, all terms and cond itions o f th e document referenced in Item 9A o r 10 A, as hereto fore chang ed , remains un ch an ged and in full force and effect.

15A. NAME AND T IT LE OF SIGNER (T ype or print )

30-105-04EXCEP TION T O SF 30

AP PROVED BY OIRM 11-84

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

FAR (48 CFR) 53.243

PLEASE SEE ATTACHED CONTINUATION FORM FOR BLOCK 14.

1. CONTRACT ID CODE PAGE OF PAGES

J 1 25

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

16C. DATE SIGNED

BY 29-Jul-2021

16B. UNITED STAT ES OF AMERICA15C. DATE SIGNED15B. CONTRACTOR/OFFEROR

(Signa ture of Cont ract ing Officer)(Signat ure of person aut horized t o sign)

8. NAME AND ADDRESS OF CONT RACT OR (No., St reet , County, Sta te and Zip Code) X HE125421R9001

X 9B. DATED (SEE IT EM 11)

01-Jul-2021

10B. DATED (SEE IT EM 13)

9A. AMENDMENT OF SOLICITATION NO.

11. THIS IT EM ONLY AP PLIES TO AMENDMENT S OF SOLICITAT IONS

X Th e ab ove n umbered solicitation is amend ed as set forth in Item 1 4. Th e hou r and date sp ecified for receipt o f Offer X is extend ed , is not extended.

Offer mu st ackn owled ge receipt of this amen dment p rior to the h our an d d ate specified in the solicitation or as amen ded b y o ne of the following method s:

(a) By completing Items 8 and 15 , and returnin g 1 co pies of the amen dment; (b ) By ackn owled ging receipt of this amen dment o n each copy of the o ffer sub mitted ;

o r (c) By separate letter o r teleg ram wh ich includ es a reference to th e so licitation and amend men t nu mbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY RESULT IN

REJECTION OF YOUR OFFER. If by virtu e of this amen dment y ou desire to change an offer already su bmitted, su ch change may be made by teleg ram or letter, p rovid ed each telegram o r letter mak es reference to th e so licitation and this amen dment, an d is receiv ed prio r to the op en ing hou r and date sp ecified.

12. ACCOUNTING AND AP PROP RIATION DATA (If required)

13. THIS ITEM AP PLIES ONLY T O MODIFICATIONS OF CONT RACT S/ORDERS.

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

A. THIS CHANGE ORDER IS ISSUED P URSUANT T O: (Specify aut horit y) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN T HE

CONT RACT ORDER NO. IN ITEM 10A.

B. T HE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES (such as changes in paying office , appropria tion dat e, et c.) SET FORT H IN ITEM 14, P URSUANT TO T HE AUT HORITY OF FAR 43.103(B).

C. T HIS SUPP LEMENTAL AGREEMENT IS ENT ERED INTO PURSUANT TO AUT HORITY OF:

D. OT HER (Specify type of modificat ion and aut horit y)

E. IMP ORTANT: Contrac tor is not, is required t o sign this document and re turn copies to t he issuing office.

14. DESCRIP TION OF AMENDMENT/MODIFICATION (Organized by UCF section headings, inc luding solic ita tion/contrac t subject mat t er where feasible.)

10A. MOD. OF CONTRACT/ORDER NO.

2. AMENDMENT/MODIFICATION NO. 5. PROJECT NO.(If app licable)

6. ISSUED BY

3. EFFECTIVE DATE

29-Jul-2021

CODE

DOD EDUCATION ACT IVITY

AT TN: PROCUREMENT DIVISION

4800 M ARK CENTER DRIVE

SUITE 05F09-02

ALEXANDRIA VA 22350-1400

HE1254 7 . ADMINISTERED BY (If o ther than item 6)

4 . REQUISITION/PURCHASE REQ. NO.

CODE

See Item 6

FACILITY CODECODE

EMAIL:TEL:

SECTION SF 30 BLOCK 14 CONTINUATION PAGE

SUMMARY OF CHANGES

SECTION SF 1449 - CONTINUATION SHEET

SOLICITATION/CONTRACT FORM

The required response date/time has changed from 16-Jul-2021 01:00 PM to 30-Jul-2021 02:00 PM.

The following have been added by full text:

BLOCK 14 CONTINUATION

The purpose of this amendment is to:

1) Provide offerors with the attached GPAT form to be completed and returned with this signed amendment. The Technical Standards cited on Pages 48-49 of the RFP are highlighted in yellow on the attached referenced form. The contractor's response to the column for How Does the (EIT) meet this requirement? must be filled out (EIT=Electronic and Information Technology).

2) Correct the form attachment label in the 52.212-1 addendum as the labeling was originally transposed in the initial RFP. The GPAT form is Attachment 2. Please return the filled out GPAT form by the designated timeline (Eastern Standard Time) stated in this amendment.

3) Delete item #13 Compatibility with existing Microsoft CRM/xRM technology at Section

2.6.1 from the PWS.

4) Change Item #12 at Section 2.6.1 to read: Compliant with revised Section 508 accessibility standards indicated on the Government Product/Service (GPAT) template (see RFP Attachment 2).

All other items remain unchanged. Reference Summary of Changes herein.

The following have been modified:

PERFORMANCE WORK STATEMENT

ATTACHMENT 1

PERFORMANCE WORK STATEMENT (PWS)

Electronic Work Paper Solution (EWPS)

Update 7/29/2021

Department of Defense Education Activity 4800 Mark Center Drive

Alexandria, VA 22350

Performance Work Statement for

Electronic Work Paper Solution (EWPS)

1. General Information and Scope of Work.

1.1 Agency

The Department of Defense Office of Inspector General (DoD OIG) mission is to detect and deter fraud, waste, and abuse in DoD programs and operations; promote the economy, efficiency and effectiveness of the DoD; and help ensure ethical conduct throughout the DoD. The DoD OIG keeps the Secretary of Defense and the Congress informed of fraud, waste, abuse, and program deficiencies identified through its oversight work. The DoD OIG’s administrative and criminal investigators, auditors, evaluators, and support staff operate globally, conducting investigations, audits, evaluations, and mission support activities to accomplish the DoD OIG’s mission.

1.2 Background

DoD OIG’s Audit and Evaluations components have issued over 100 reports each year utilizing an Electronic Work Paper Solution (EWPS) since 2001. The evidence and analysis to support the reports are maintained in the EWPS. The DoD OIG Audit and Evaluations Divisions are looking to replace the existing EWPS with a new solution that will require gradual implementation.

1.3 Scope of Work

The contractor shall provide commercially available off the shelf (COTS) software for an EWPS scalable to 1000 users. During year one, 600 users will be required to allow for a pilot user program. During year two the number of users will increase by 300 to 900 and for the 3rd through 10th contract year a total number of 900 users will be required with the option to increase to an additional 100 for a total of 1000 users over the life of the contract. The contractor shall provide project management for the initial software installation, and set-up including the establishment of a customer-based ability to customize the final EWPS environment. The contractor will be required to provide “Train the Trainer” training and maintain responsibility for on-going software security updates, patches, bug fixes, and correction of all software compliance and/or compatibility related issues. The contract period of performance will include a 12-month base contract period with 9 one-year options to continue the software licenses and support. NOTE: Any data/documents/files produced as a result of using the product belongs solely and exclusively to the DoDIG.

2. Requirement (Objectives)

The EWPS must be an on premise solution that serves as the DoD OIG’s system of record for audits, evaluations, and other reviews. The DoD OIG will use the EWPS for project procedures, work papers, and related project functions that support the planning, fieldwork, and reporting for audits, evaluations, and other reviews as well as follow-up work related to recommendations resulting from any of those projects. Project procedures and work papers may include project plans; interview write-ups; analyses of documents, web research, and computer-generated information; summaries; work paper review comments; draft and final reports; and management responses to reports and recommendations.

2.1 (Objective 1) Project Management

The contractor shall assign a single point of contact (POC) that is responsible for planning, installing, and providing software set-up and configuration, and to ensure the successful deployment of the EWPS.

(Task 1) The contractor shall provide a comprehensive milestone schedule within 7 calendar days after contract award, detailing the steps required to install, set-up and establish a fully operational EWPS. The milestone schedule will be submitted for review and approval by the Contracting Officer’s Representative (COR).

(Task 2) The contractor will provide periodic status reports to describe the progress and results to date, and identify matters that may impact the completion of installation or other future work. The frequency of these meetings is at the discretion of the DoD OIG COR. At a minimum, status reports shall include the following:

Significant accomplishments for the reporting period;

A discussion of significant problem areas, including a plan and target dates for resolving each problem and the problem’s impact on deliverable due dates;

2.1.1 Performance Standard (PS) 1. The milestone schedule provides a comprehensive account of all tasks required to result in successful deployment and is included in the Kick-Off Meeting scheduled to occur 7 calendar days after contract award.

Acceptable Quality Level (AQL) 1. No Deviation

2.1.2 Performance Standard (PS) 2. During initial installation and set-up, status reports will be required at the end of each work week. As-required status reports and status meetings shall be delivered or conducted within 3 work days after COR request. Status reports shall contain accurate, complete and timely information. Status meetings shall be proceeded with an agenda provided to the COR at least 1 day prior to the meeting.

AQL 2. 98 % of status reports and meetings will be completed by the date requested by the COR. The remaining 2% shall be completed no later than 5 calendar days after the established due date unless a later date is agreed to by the COR.

2.2 (Objective 2) Installation

(Task 1) The contractor shall remotely install and set-up the EWPS to result in a fully successful deployment within 90 days after contract award. Installation and set-up shall include a customer-based ability to customize the final EWPS environment.

Installation of the EWPS must result in a capability that is fully compliant with DoD standards, e.g. DoD policies and directives, Security Technical

Implementation Guides (STIGs), anti-virus, firewalls and Host Intrusion Prevention Systems.

2.2.1 PS 1. Software installation, set-up and customization will be completed by the required completion date with minimal disruption to on-going operations.

AQL 1. The installation, set-up and customization completion date may be extended upon approval by the COR in consideration of delays that cannot be avoided.

2.2.2 PS 2. The installed EWPS shall be fully compliant with DoD policies and directives, STIGs, anti-virus, firewalls and Host Intrusion Prevention Systems.

AQL 2. No Deviation.

2.3 (Objective 3) Training

(Task 1) The contractor shall provide training for 8 Administrators on how to customize and become proficient in using the EWPS. The training will supplement the knowledge transfer that occurs during the installation, and deployment process. Training documentation shall cover all aspects of Administrator operations.

2.3.1 PS 1. EWPS training shall be comprehensive covering all aspects of user operations, detailed to the level required to ensure Administrators are capable of providing the training in a train-the-trainer forum.

AQL 1. No Deviation

(Task 2) The Contractor shall provide “Train the Trainer” training on a simulated production environment after customization is complete. The training shall be robust at the depth required to enable 12 super users (including the 8 Administrators) to conduct user training for up to 1000 users. The contractor shall conduct the required training within the time frame established in the COR approved milestone schedule. Training documentation shall cover all aspects of user operations. All training will be performed remotely through Cisco WebEx or a similar OIG-approved platform.

2.3.2 PS 2. Contractor shall provide training that ensures students are equipped to conduct a

Train the Trainer program covering all of the essential elements needed for EWPS operation.

AQL 2. No Deviation

2.3.3 PS 3. The contractor shall provide a training plan that covers all of the topics to be included in the training program no later than 10 days before the dates established for training.

AQL 3. No Deviation

2.3.4 PS 4. Provide training materials required for the Administrator and Train the Trainer programs.

AQL 4. No Deviation

2.4 (Objective 4) Software Maintenance.

(Task 1) The contactor shall provide on-call software support to resolve user configuration and operator issues and operating anomalies.

2.4.1 PS 1. On-call requests for support shall be responded to within 1 business day.

Problem resolution shall normally be completed within 2 business days. User configuration and operator issues and operating anomalies that cannot be resolved within 2 business days shall be coordinated with the COR. The contractor shall document a plan for resolving the problem and provide a projected date for resolution.

AQL 1. 98% of all problems will normally be resolved within 2 business days, the remaining within 4 business days from initial request, unless coordination with the COR results in acceptance of a later date.

2.5 Post Award Conference (Kick-off Meeting)

(Task 1) Within 10 business days after contract award the contractor shall meet with the DoD OIG to discuss plans for accomplishing the requirements and deliverables in the contract.

Specifically the Kick-Off Meeting will include:

Introduction of key stakeholders; roles and responsibilities;

Review contractual matters, including terms and conditions of the contract;

Contractor reporting requirements;

Project milestone schedule;

Review the PWS and deliverables to ensure a common understanding Address questions from any party and resolve disagreements (if any).

Invoicing and billing procedures.

2.5.1 PS 1. The contractor shall prepare all documentation and coordination required to conduct a Post Award Kick-Off meeting within 10 business days after contract award.

The contractor shall provide meeting minutes of the Kick-Off meeting within 5 business days after the Kick-Off meeting.

AQL 1 Acceptable Quality Level (AQL 1) No Deviation.

2.6 EWPS Required Features:

Unless marked (preferred), the EWPS must include the following capabilities:

2.6.1 Infrastructure

1. Clearly defined software patch and upgrade schedules

2. Ability to test prior to patch/upgrade installations to production environment

3. Scalable to 1,000 users

4. Metrics on System Performance

5. Support for single user sign-on and authorization based on the Common Access

Card

6. Ability to operate via direct connection to network or through VPN/remote connections

7. Support for mobile iOS devices (preferred)

8. Compatible with Windows 10 and higher

9. Compatible with MS Office 2016 and above

10. Compatible with Windows Server 2016 and above

11. Compatible with MS SQL 2016 and above using SQL in transit encryption and only Windows authentication.

12. Compliant with revised Section 508 accessibility standards indicated on the

Government Product/Service Accessibility (GPAT) template (see RFP Attachment 2).

13. System must meet the Information Assurance Acquisition Guide – Mission Accreditation Compliance (MAC) Level requirements for a Mission Support System. Guide is published in the Defense Acquisition University.

14. System must use Internet Information Services (IIS) to integrate with the existing OIG web server and Public Key Infrastructure (PKI) to ensure supportability by ISD and avoid additional costs related to integrating and supporting unfamiliar technologies.

15. System must store structured and unstructured data in SQL Server to ensure supportability by ISD and avoid additional costs related to integrating and supporting unfamiliar technologies

16. System must comply with federal Personally Identifiable Information (PII) regulations. A Privacy Impact Assessment (PIA) will be submitted to OIG FOIA office.

2.6.2 Security

1. Full centralized logging of user activity, including replacement, deletion, and changes

2. Ability to use in closed environment (high side)

3. Easy access to logs and activity reports

4. System must pass the DoD OIG Network Security Information Accreditation requirements. Requirements published by the DoD OIG IA team.

5. System must sit behind a firewall, DMS, and run IDS.

2.6.3 System Configurability and Centralized Management

1. User-friendly, intuitive graphical interface

2. Centralized System Administration policy management

3. Ability to customize software by modifying data fields to meet OIG project management and reporting needs, including ability to add additional fields that can be reported from centralized system, modify field names and field type

4. Self-contained projects with unique permissions and roles

5. Ability to create multiple standard project templates to ensure projects include required elements/steps based on type of project (audit, evaluation, and inspection)

6. Ability to create templates for staff to document work that include designated fields for multiple work-paper elements (e.g. purpose, scope, criteria)

7. Ability to create and assign permissions based on user roles such as administrator, multiple reviewer levels, preparer, read only or combination of roles

8. Ability to assign staff to different projects with permissions specific to each project

9. Ability to copy existing projects with or without edit history

10. Ability for authorized staff to access completed projects by other teams

11. Ability to create workflows

12. Ability to create, send, and receive surveys from outside users via email addresses

(preferred)

13. Ability to export survey data to several Microsoft office and Adobe products (i.e.

Word, Excel, Adobe Pro, etc.) (preferred)

2.6.4 Support

1. Daily technical support

2. Detailed reference materials for the User, Administrator and Technical Staff

2.6.5 Training

1. Ability to train in simulated production environment

2. Robust training for administrators

3. Train the trainers

4. Training documentation

2.6.6 Document management

1. Support for current and future Microsoft Office file types, including Outlook and

Access (Access: preferred)

2. Support for current and future Acrobat PDF files

3. Support for large-scale, complex data and analysis files

4. Unique identifier for each attachment

5. Unique identifier renumbers if deleting attachment (no gaps in identifier) while maintaining fidelity to linked items (preferred)

6. Ability to update/replace/delete attachment

7. Ability to import/export documents

8. Support for large numbers of attachments in each project, and large individual attachments

9. Support for alternative office file types (Google Docs, open source office files, databases, etc.) (preferred)w

10. Support for industry-standard media files including audio (e.g. WAV, MP3), video (e.g. AVI, FLV, WMV, MOV, MP4), and image (e.g. JPEG, JPG, TIFF, RAW, DNG, GIF, BMP)

11. Ability to restrict access to specific attachments within a specific project (ex. limit access by staff person, limit access/opening document to specific individuals on a particular document) (preferred)

12. Ability to easily share selected attachments across projects

13. Ability to retain/recover multiple versions of attachments (preferred)

14. Ability to lock attachments to prevent changes

2.6.7 Working collaboratively in real-time environment

1. Ability for multiple users to collaborate for document creation (preferred)

2. Ability for multiple users to collaborate real-time in editing documents

(preferred)

3. Ability to identify changes made by each staff member (preferred)

4. Ability to accept/reject changes made by staff members (based on project role)

(preferred)

2.6.8 Review processes for all documentation

1. Ability to establish centralized work paper sign-off policies

2. Preparer sign-offs

3. Reviewer sign-offs, multi-level

4. Ability to provide reviewer comments and receive response from preparer prior to reviewer sign-off, and retain

5. Ability to provide peer-to-peer comments

6. Ability to identify what changes were made after supervisory review

2.6.9 Cross-Indexing

1. Ability to reference write-ups to attached files (Word, Excel Acrobat)

2. Ability to link and open documentation (Word, Excel, Acrobat, Images, Videos, etc.) to work papers created within software

3. Ability to efficiently handle large number of references within individual documents and across the project (identified maximum number of indexing and referencing links)

2.6.10 Independent Referencing

1. Ability for staff, not participating in project, to review and verify cross-indexed references of all statements of fact within draft and final reports created in MS Word

2. Ability to add visual cues indicating Independent Reference Reviewer has verified that indexed evidence supports each statement of fact (e.g., tick marks) (preferred)

3. Ability to utilize reviewer tools for feedback and sign-off

4. Ability to identify changes made to document after Independent Reference

Reviewer exits document (not marked reviewed) (preferred)

5. Ability for audit team to see issues identified while Independent Reference

Reviewer works in the document (i.e., comments or reviewer notes)

6. Ability to track progress of review (preferred)

7. Ability to address issues to both the team and individuals

2.6.11 Search Functionality

1. Ability to quickly locate documentation within a project using text-based search of labels and contents

2. Ability to search within common office formats including, Word, Excel, and

Acrobat documents

3. Ability to filter search results based on custom metadata tags such as Personally

Identifiable Information

2.6.12 Miscellaneous Features

1. Support for rich text formatting of text (including font types, highlighting, paragraph alignment, etc.)

2. Support for Copy/Cut/Paste

3. Support for inline and on-demand spell check, with editable dictionary

4. Support for bullet lists, numbered lists, and multilevel lists

5. Support for equations and symbols

6. Support for heading styles linked to a navigation pane

7. Ability to create and format tables

8. Support for inline and on-demand grammar check (preferred)

9. Support for inline and on-demand thesaurus (preferred)

10. Recycling bin feature that allows users to recover deleted items (preferred)

2.6.13 Off-line working mode

1. Ability to create work papers and edit working papers offline

2. Ability to sync project on demand and add support offline

3. Ability to discard after timeline set by admin (preferred)

4. Ability to cancel offline items locked by users that may no longer be using them

5. Process to synchronize offline changes to database

6. Controls to prevent unintentional overwrites by conflicting offline changes

7. Ability for peer review access of entire project file without access to OIG network

2.6.14 Dashboards

1. Staff commitments

2. Status of project and work papers

3. Easily accessible reports for staff indicating completion and review status

4. Visual reminders for pending deadlines and open items

5. Access items directly from dashboards

2.6.15 Notifications

1. Ability to create notifications within the system for user-defined triggers such as pending deadlines, review status, and required actions (should be able to turn on and off)

2. Ability to create e-mail notifications based on user-defined triggers (should be able to turn on and off) (preferred)

2.6.16 Management reporting

1. Ability to generate reports, at any time, across entire database and within specific projects

2. Ability to generate reports on any database field

3. Ability to create ad hoc reports and queries.

4. Ability to export reports into a project file and external to the system

5. Ability to import reports from a project file and external source into another project

2.6.17 Metadata Tags

1. Ability to identify content such as Personally Identifiable Information

2. Ability to create and apply custom tags to user-generated documentation and supporting evidence

2.7 508 Compliance

Section 508 Accessibility Standards. Http://www.section508.gov

The Technical Standards allow persons with disabilities access to information comparable to the access afforded persons without disabilities, in accordance with Section 794d of Title 29, U.S.C., also known as Section 508 of the Rehabilitation Act.

The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable to this acquisition.

Technical Standards 1 1194.21 - Software Applications and Operating Systems

1 1194.22 - Web Based Intranet and Internet Information and Applications 0 1194.23 - Telecommunications Products 0 1194.25 - Self-Contained, Closed Products 0 1194.26 - Desktop and Portable Computers 1 1194.41 - Information, Documentation and Support

The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance.

3. Constraints

3.1 Security Requirements

3.1.1 Personnel Security: This DOD work effort involves unclassified material. Personnel shall adhere to the Privacy Act, Title 5 of the U.S.

code, Section 552a and applicable agency rules and regulations.

3.1.2 Disclosure of Information: The contractor shall not release to anyone any unclassified information. Contractor personnel shall not divulge or release privacy data or information developed or obtained in the performance of this task order, until made public or specifically authorized by the Government. The contractor shall not use, disclose, or reproduce third party companies’ propriety data, other than as authorized and required in performance of this task order. Personnel working on this project will be required to sign a non-disclosure agreement immediately upon their start on the project. The contractor’s procedures for protecting against unauthorized disclosure of information shall not require Department of Defense employees or members of the Armed Forces to relinquish control of their work product, whether classified or not, to the contractor.

3.1.3 Place of Performance: Contractor will perform duties at the contractor location, using remote video and audio processing (i.e. Cisco WebEx or a similar OIG-approved platform), to communicate with Government personnel. As needed, the contractor may be required to work from 4800 Mark Center Drive to address system issues, installation, and training.

3.1.4 Work Schedule and Hours of Operation: The Government’s primary operations are conducted:

Monday through Friday between the hours of 5:30am EST through 7:00pm EST, except Federal holidays. The eleven (11) Federal holidays include New Year’s Day, Martin Luther King Day, President’s Day, Memorial Day, Juneteenth National Independence Day, July 4th Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving, and Christmas Day.

4.0 Government-Furnished Property

4.1 Government Furnished Property will not be provided for this contract.

5.0 Acronyms and Definitions. Alphabetical list of definitions of key words used or acronyms.

AQL Acceptable Quality Level CAC Common Access Card CIO Chief Information Officer COOP Continuity of Operations Plan CO or KO Contracting Officer COR Contracting Officer's Representative CUI Controlled Unclassified Information DECC Defense Enterprise Computing Center DISA Defense Information Systems Agency (US DoD) DoD Department of Defense DOD OIG Department of Defense Office of the Inspector General DODIG Department of Defense Inspector General DSS Defense Security Service FSO Facility Security Officer GFI Government Furnished Information GFM Government Furnished Material IPR In-Progress Review JPAS Joint Personnel Adjudication system MSR Monthly Status Report NIPR-Net Non-Secure Internet Protocol Router Internet OSEC Security Office PAOC Post Award Orientation Conference PWS Performance Work Statement QASP Quality Assurance Surveillance Plan SIPR-Net Secure Internet Protocol Router Internet SME Subject Matter Expert VOIP Voice over Internet Provider VRL Visit Request Letters VTC Video Teleconferencing

6.0 Performance Requirement Summary (PRS).

Performance Objective Performance

Standard AQL Inspection Method

Objective 1 - Project Management.

Task 1. Milestone Schedule

Complete and timely No Deviation

100% Inspection of delivered milestone schedule. Time and contents.

Task 2 - Status Reports

On-Time, complete and accurate with Agenda

98 % of status reports and meetings will be completed by the date requested by the COR. The remaining 2% shall be completed no later than 5 calendar days after the established due date unless a later date is agreed to by the COR.

100% Inspection of delivered milestone schedule. Time and contents.

Objective 2 – Installation

Task 1 – Remotely Install On-Time

Software installation will be completed by the required completion date with minimal disruption to on-going operations.

Installation completion date may be extended upon approval by the COR in consideration of delays caused by DoD OIG network interference that cannot be avoided.

100% Inspection

Task 2 – Software is compliant with DoD standards

EWPS is fully compliant with DoD policies and directives, STIGs, anti-virus, firewalls and Host Intrusion Prevention Systems.

No Deviation

COR performance reports

Objective 3 - Training

Task 1 – Train the Trainer Program

Covers all of the essential elements needed for EWPS operation and is detailed at the level needed for a Train the Trainer program.

COR performance report and customer satisfaction from Trained Users

Task 2 - Provide training materials

Training materials are complete and written to the appropriate level

Customer satisfaction Survey administered by the COR.

Objective 4 Task -1

On-call requests for support shall be responded to within 1 business day, with problem resolution completed within 2 business days

98% responded to within 1 business day. The 2% shall be no later than 2 days after support request.

98% problem resolution in 2 business days. The 2% of problem resolution should be no later than 4 business days after support request.

100% Inspection

7.0 Contract Deliverables.

MILESTONE/DELIVERABLES FORMAT

NUMBER

COPIES

PWS

REFERENC

E

PLANNED

FREQUENCY

MILESTONE SCHEDULE

WORD -

DIGITS 1 2.1 & 2.1.1

7 DAYS AFTER

CONTRACT

AWARD TO BE

REVIEWED AND

APPROVED BY THE

COR

KICK OFF MEETING REPORT WORD 1

2.5

5 DAYS AFTER

MEETING

STATUS REPORTS WORD 1

2.1.& 2.1.2

WEEKLY DURING

INSTALLATION. AS

REQUIRED BY

COR AFTER

INSTALLATION

MEETING AGENDA WORD 1 PER MEETING 2.1.1 AS REQUIRED

TRAINING PLAN WORD 1 2.3.3

10 DAYS PRIOR

TO THE

TRAINING

EVENT

USER DOCUMENTATION WORD 1

ADMINISTRATOR DOCUMENTATION WORD 1

7.1 Quality Assurance Surveillance Plan (QASP)

The Government will utilize a QASP to monitor the contractor’s performance on the contract. The QASP is a living document and can change at any time during the life of the contract. As such, the Government reserves the right to unilaterally edit the QASP at the Government’s discretion.

52.212-1 ADDENDUM – INSTRUCTIONS TO OFFERORS - - COMMERCIAL ITEMS (DEC 2006)

(b)(4) The Technical Description shall address the following factors:

a. General Guidance

This section provides general guidance for preparing proposals as well as specific instructions on the format and content of the offer. The offeror’s proposal must include all data and information requested by the Request for Proposal (RFP) and must be submitted in accordance with these instructions. Non-conformance with the instructions to offerors, and any non-conformance to the administrative requirements provided in this proposal preparation and submission instructions may result in removal of the offer from further evaluation.

The proposal must be clear, concise, and include sufficient detail for DoDIG’s effective evaluation, and for substantiating the validity of stated claims. The proposal should not simply rephrase or restate the Government's requirements but rather provide convincing rationale to address how the offeror intends to meet all requirements. Offerors should assume that the Government has no prior knowledge of their capabilities and experience. Please note that the Government will base its evaluation solely on the information presented in the offeror’s proposal. Additional portions of the successful offeror’s proposal may be incorporated into the contract as an attachment in the award document at the Government’s discretion. NOTE: “Additional portions of the successful offeror’s proposal may be incorporated into the contract as an attachment in the award document at the Government’s discretion. In the event the offeror’s proposal is incorporated into the contract, any terms or conditions in the proposal that conflict or negate the terms and conditions outlined in the subject contract and its attachments will be null and void.”

The narrative shall not exceed a total of 45 pages, including any graphics, photographs, brochures, pamphlets, charts, and diagrams. Page size shall be 8.5 inches x 11 inches or A4 and text font size no smaller than size 11.

Number pages sequentially, when feasible. Page limitations shall be treated as maximums. If exceeded, the excess pages will not be read or considered in the evaluation of the proposal. Pages shall only include graphics, photographs, brochures, pamphlets, charts, and diagrams for the purpose of depicting the technical approach.

b. Proposal Organization

Offerors must organize and present proposals following the format and page limits identified herein. The following are the specific details required to be submitted with each offer in response to this solicitation:

VOLUME VOLUME TITLE

Cover Letter

I Factor I (Technical) II Factor II (Past Performance) III Factor III (Price)

COVER LETTER

The Cover Letter shall include:

a. Complete Business Mailing Address

b. Tax Identification Number (TIN)

c. Dun & Bradstreet Number (DUNS)

d. Cage Code/NAICS Code

e. Contact Name, Phone, Fax, and email adderss

f. A clear statement that the proposal and pricing is valid for a minimum of 120 calendar days from the closing of the RFP.

VOLUME I– FACTOR I - TECHNICAL PROPOSAL

All submission requirements shall be included in the offeror’s proposal by the closing date of the solicitation. Below are the submission requirements for each of the four (4) technical evaluation sub-factors:

The technical section shall be a comprehensive statement of the offeror’s capability to meet or exceed the requirements in the Performance Work Statement (PWS) at Attachment 1.

Subfactor I (IT Government Compliance Forms):

The offeror shall provide:

A fully executed “GPAT” (Section 508) at Attachment 2 A fully executed “Terms of Service Addendum” at Attachment 3

Subfactor II (Technical Specifications):

The offeror shall provide a detailed narrative of their technical capability to meet or exceed the Electronic Work Paper Solution (EWPS) requirements stated in the Performance Work Statement (PWS) Section 2 (Requirements). This includes:

a. Project Management - The offeror shall describe their ability to plan, install, and provide the requested software that can be set up and configured fully compliant with DoD policies and directives, Security Technical Implementation Guides (STIGs), anti-virus software, firewalls and Host Intrusion Prevention Systems (PWS paragraphs 1.3, 2.1, 2.2 and 2.6 ).

b. Required Features – The offeror shall describe in detail their capabilities to provide the EWPS required features and licensing requirements outlined in the PWS at section 2.6.

c. Software Maintenance and Support – The offeror shall descibe their approach to provide software maintenance and support for the entire duration of the resultant contract (potentially 10 years if all options are exercised).

d. The offeror shall address support requirements for both new and experienced users (PWS 2.4).

e. Offeror’s may propose additional capabilities for value-added benefits that may exceed the

Government’s requirements.

Subfactor III (Training Approach):

The offeror shall describe their ability to provide a Train the Trainer program that describes their experience in drafting, delivering, and distributing training materials required for a Train the Trainer program to include lessons learned, iterative content updates and maintenance, and prioritizing user satisfaction. Additionally, the offeror shall describe their experience with knowledge transfer in the train-the-trainer and scenario. (PWS 2.3)

Subfactor IV (Functionality):

The offeror shall provide instructions on how the Government may obtain access to the offeror’s proposed EWPS solution for independent testing by the Government. Access shall be made available to the Government from the date the solicitation closes until an award decision is rendered so that the the Government has access availability to test and evaluate the functionality of the offeror’s proposed EWPS solution.

(b)(10) VOLUME II– FACTOR II – PAST PERFORMANCE

The offeror shall provide at least three (3) Past Performance references using the Past Performance Questionnaire at Attachment 4. These references shall be from relevant and recent contracts, on-going contracts, subcontracts and/or task/delivery orders accomplished within the past three (3) years. Relevant efforts are defined as any efforts that are of similar size and scope as the tasks in the PWS. Recent efforts are defined as those performed to any extent within the last three (3) years prior to the closing date of the solicitation. These efforts shall be the same or similar in type, size and complexity as the requirements of this contract.

The offeror shall list three references in their submittal proposal package to include the filled out information for each reference for items 1-7 below.

1. Company or Organization receiving the goods and services

2. Point of Contact with knowledge of the goods and services received and the offeror’s performance:

a. First and Last name

b. Job Title

c. Phone Number(s)

d. email Address

3. Description of the deliverable(s) and/or service provided, including the location of the service and its relevancy to the requirements of this solicitation effort (if not obvious).

4. Contract/Task Order Number, if any

5. Date(s) or Period of Performance services were provided

6. Total contract and/or delivery or task order value of the resources or services provided

7. Copy of letter sent to company authorizing the Point-of-Contact (POC) to discuss contract performance with Government evaluators.

*NOTE: The offeror shall also send the Past Performance Questionnaire at Attachment 4 to the three references and have them complete it and the offeror shall submit the completed Attachment 4 to the Government with their proposal package by the submittal closing date. The offeror is responsible for ensuring that three references are provided with their proposal package.

*Please note that if an offeror does not have three (3) past performance references to submit in accordance with the above submittal requirement, the offeror shall note this information in their proposal.

(b)(6) VOLUME III– FACTOR III – PRICE PROPOSAL

Offerors shall insert the proposed price in the pricing template provided at Attachment 5 to include the unit price, amount and total amount listed for the base year and option periods.

Offerors shall fill out the columns for the base year and all option periods of the template.

All Items must have a price or be marked “NSP” for Not Separately Priced. Offerors shall also include an explanation for any areas marked NSP to confirm that no price will be populated for that area.

VOLUME IV – CONTRACT DOCUMENTATION

The offeror's proposal shall include a signed copy of the solicitation and any amendments issued.

Offerors proposal must also include a Small Business Participation Plan (applicable to all offerors, including those with commercial plans and comprehensive subcontracting plans). The offeror shall submit a Small Business Participation Commitment Document which specifies the offeror’s level of commitment to small business utilization in performance of this requirement. The Small Business Commitment Document needs to address the following:

a. The extent to which the vendor will utilize small business (SB), small disadvantaged business (SDB), women-owned small business (WOSB), Historically Underutilized Business Zone (HUB Zone) small business, veteran-owned small business (VOSB) and service-disabled and veteran-owned small business (SDVOSB).

b. Level of commitment to use such firms.

c. Types of work the small business firms are to perform.

d. Statement of quantitative degree to which small businesses (including small businesses in all socio- economic categories) will participate in the acquisition relative to the total value of the acquisition. (A minimum quantitative requirement (MQR) of 10% or better of the total contract value for small business concerns participation is required. Small business primes performance is included in the 10% or better participation (less software license and maintenance cost).

e. Detailed explanations/documentation supporting the proposed participation commitment and quantitative degree of participation. (Note: This information will not be incorporated into the resultant contract)

The offeror’s proposal shall also include a Small Business Subcontracting Plan (appliable to large businesses only). Other than small business offerors shall submit a Small Business Subcontracting plan satisfying the requirements in FAR 52.219-9, Alt II and DFARS 252.219-7003. In addition to the requirements of FAR clause 52.219-9 Alt II, the small business subcontracting plan shall address affirmatively all other small business subcontracting requirements in FAR Part 19.7. The small business subcontracting plan shall be submitted separately from the Small Business Participation Commitment Document required above, which applies to both small and other than small businesses.

Note 1: Though difference from each other, the Small Business Participation Commitment Document is a compliment in part to a Small Business Subcontracting Plan for offerors required to submit a plan. Other than small business offerors need to ensure consistency between both documents where appropriate.

Note 2: The Subcontracting Plan is not a requirement for evaluation in source selection, but rather, a requirement for award to other than small business, once determined to be acceptable, the subcontracing plan shall be incorporated into the resulting contract.

Proposal Submission: Proposals shall be submitted via electronic mail (email) To both the Contracting Officer, Georgette Hendricksen, email: Georgette.Hendricksen@DODEA.EDU and Contract Specialist, Wardell Gordon, email: Wardell.Gordon@DODEA.EDU

- Proposals WILL NOT be accepted by mail or hand delivery. Proposals must be received no later than the date and time specified in Block 8 of the SF1449.

- Email subject line shall include the following information: Solicitation number, Offeror’s company name, and number of emails if applicable (e.g., 1 of 3). Electronic files shall be clearly labeled and compatible with Windows 10, Microsoft Office 2013 and Adobe Acrobat DC.

- It is the offeror’s responsibility to ensure receipt of the proposal, and any modifications, or revisions before the closing date and time specified in the solicitation.

Notice: DoDEA HQ has a size limitation of 10MB for each email to a DoDEA HQ email addressee.

Accordingly, the offeror is solely responsible for ensuring that the offeror’s proposal or correspondence successfully transmits to, and is received by, its intended DoDEA HQ email addressee. The offeror is advised to immediately contact the intended email address for acknowledgement email receipt of the offeror’s email proposal and attachments (as applicable).

(c) Period for acceptability of proposal: This paragraph (c) is changed to read as follows:

The offeror agrees to hold the prices in its proposal firm for 120 calendar days from the date specified for receipt of proposal, unless another time period is specified in an amendment to the solicitation.

Questions: Questions regarding this requirement shall be submitted electronically to both the Contracting Officer, Ms. Georgette Hendricksen, Georgette.Hendricksen@DODEA.EDU and the Contract Specialist, Mr.

Wardell Gordon, Wardell.Gordon@DODEA.EDU no later than 11:00 AM Eastern Standard Time on Friday, 9 July 2021. No questions will be accepted after this cut-off time and date.

52.212-2 ADDENDUM – EVALUATION – COMMERCIAL ITEMS (DEC 2006)

Basis for Contract Award:

The Government will award a single, firm-fixed-price (FFP) contract to the responsible offeror whose proposal conforming to the solicitation will be the most advantageous to the Government, price and other factors considered in accordance with FAR Part 13. The following three evaluation factors shall be used for a comparative analysis for the Government’s determination of best benefit to the Government: Factor I (Technical), Factor II (Past Performance), Factor III (Price). The Government will award a contract, resulting from this solicitation, to the responsible offeror that receives at least an Acceptable rating for each non-price factor. For Factor 1, an unacceptable rating for any subfactor will render the overall rating for Factor 1 as unacceptable. This may result in an award to a higher-rated, higher- priced offeror, where the decision is consistent with the evaluation factors, and the Contracting Officer reasonably determines that the technical approach and/or past performance of the higher priced offeror outweighs the price difference.

The Government intends to award without discussions. Therefore, the offeror’s initial pricing proposal should contain the offeror’s best approach/terms for all the evaluation factors (technical, past performance, and price). However, despite this intent, the Government reserves the right to conduct discussions if the Contracting Officer determines they are necessary. As noted in the Addendum to FAR 52.212-1, non- conformance with the instructions to offerors, and any administrative requirements provided in the Addendum to FAR 52.212-1 proposal preparation and submission instructions may result in removal of the proposal from further evaluation.

For a proposal to result in an awardable contract, it must at least be rated acceptable for Factor 1- Technical, have a rating of relevant/neutral confidence for Factor 2- Past Performance, and Factor 3- Price must be determined Fair and Reasonable by the Government.

VOLUME I– FACTOR I - TECHNICAL PROPOSAL

The Government shall evaluate each subfactor for Factor 1. Each subfactor will be given a rating of Good, Acceptable or Unacceptable. Factor 1 will then be given an overall Factor 1 rating of Good, Acceptable or Unacceptable. Any unacceptable rating in one or more of the subfactors makes the overall factor unacceptable and the offeror will not be further considered for award.

The ratings used in Factor 1 are defined as follows:

Color Rating

Adjectival Rating

Description

Blue Good Proposal exceeds the requirements of the solicitation and indicates a thorough approach and understanding of the requirements. Risk of unsuccessful performance is low to moderate.

Green Acceptable Proposal meets the requirements of the solicitation and indicates an adequate approach and understanding of the requirements. Risk of unsuccessful performance is no worse than moderate.

Red Unacceptable Proposal does not meet requirements of the solicitation and, thus, contains one or more deficiencies and is unawardable. Risk of unsuccessful performance is unacceptable

Technical Evaluation Subfactor I (IT Government Compliance Forms):

The Government will evaluate the offeror’s executed submission of :

Attachment 2 - GPAT (Section 508) Attachment 3 - Terms of Service Addendum (Good/Acceptable/Unacceptable)

Technical Evaluation Subfactor II (Technical Specifications):

The Government will evaluate the offeror’s approach to determine if it meets or exceeds the EWPS technical requirements stated in PWS Section 2 (Requirements) at Attachment 1 to include project management, required features, and software maintenance and support.

(Good/Acceptable/Unacceptable)

Technical Evaluation Subfactor III (Training):

The Government will evaluate the offeror’s Train the Trainer program. (Good/Acceptable/Unacceptable)

Technical Evaluation Subfactor IV (Functionality/Software Capability Demonstration):

The Government will evaluate the written response and instructions along with the requirement for administrative rights from offerors for their proposed EWPS solution for independent viewing and interface with the Government’s system capabilities. The Government will view and evaluate the functionality of the proposed EWPS solution in accordance with the Government’s technical requirements. (Good/Acceptable/Unacceptable)

VOLUME II – FACTOR II – PAST PERFORMANCE

The offeror’s past performance shall be evaluated to assess the offeror’s probability of meeting the requirements in the PWS. This assessment is based on the offeror’s record of relevant and recent past performance information that pertains to the resources/services outlined in the solicitation requirements. Relevant efforts are defined as any efforts that are of similar size and scope of the solicitation. Recent efforts are defined as those performed to any extent within the last three (3) years prior to the closing date of the solicitation. Past performance information from an offeror or its subcontractors for which the offeror or its subcontractors were not listed as a prime will not be considered relevant.

In conducting a relevancy assessment, the offeror shall be assigned one of the ratings based on the chart below:

Adjectival Rating Description

Very Relevant Present/past performance effort involved essentially the same…