Draft_PWS_LMS_follow-on.docx

Performance Work Statement – (PWS) Wildland Fire Learning Management System (WLMS) Software as a Service (SaaS)

United States Department of the Interior Interior Business Center (IBC) Acquisition Services Directorate (AQD) On behalf of the Office of Wildland Fire April 9, 2025

1. PURPOSE

The purpose of the Wildland Fire Learning Management System (WFLMS) Moodle Workplace Software as a Service (SaaS) PWS is to clearly define the needed business, technology, and subscription services required to maintain the WFLMS for the Federal Wildland Fire Workforce Development Program (FWDP), the National Wildfire Coordinating Group (NWCG) members and other designated wildland fire management organizations.

Since 2018, the WFLMS has been the solution to meet the needs of inter-agency wildland fire management education and training organizations. This PWS will clearly define the scope of effort, objectives, and all needed technical and business requirements for continuation of the WFLMS program and system.

2. BACKGROUND

The WFLMS Program resides within Wildland Fire Information Technology (WFIT), Office of Wildland Fire (OWF), Office of the Secretary, Department of the Interior (DOI).

Collaborating with inter-agency, state and other wildland fire community stakeholders, the WFLMS Program identified the need for an enterprise learning management system, that would enhance the nation’s wildland fire management education and training community’s ability to consolidate training nomination, registration, hosting of online content, training evaluation assessments and reporting metrics.

In November 2018, the WFLMS began operation. The WFLMS operated as a software as a service (SaaS) solution under a managed services solution.

Key features of WFLMS include but not limited to:

· Capable of accommodating individual wildland fire organization needs

· Central host for user training and reporting

· Easy-to-use and responsive interface

· Mobile friendly

· Extensive Administrator and Course Creator support and training

· Telephone and Online Help Desk

· Training courses and videos for all levels of users Core WFLMS Services include but are not limited to:

· LMS operations and maintenance

· Hosting operations and maintenance

· Support mandated training

· Classroom management

· External training management

· Creation of mission-specific online courses

3. OBJECTIVE

The intent of this Performance Work Statement (PWS) is to provide a commercially available off-the-shelf (COTS) Subscription Service, Professional Services, & Hosting Solutions to meet the inter-agency wildland fire management organizations’ requirement for operating and delivering a complete LMS solution. The system solution will support the complete LMS.

This requirement is for a 12-month base period of performance (PoP) and two (2) 12-month option periods to meet the inter-agency wildland fire management’s requirement for approximately 220,000 user accounts, with 90,000 active users at multiple role levels. An active user is defined as a user who has accessed the WFLMS within the last twelve (12) months.

This contract will contain the following Three (3) Delivery Tasks provided in a single solution offering. The requirement of all three tasks offered together is derived from an ability to deliver and maintain continual operations with zero downtime or solution offering gaps and/or delays.

· Task 1: LMS Application and Platform Hosting Services and Support: This task is for Amazon Web Services (AWS) - AWS Government Cloud. Hosting support includes on-going operations and maintenance, technical support and monitoring of the database, content and web servers, full load balancing, with auto backup of the production database data and network failover design.

· Task 2: Migration Support: Support for migration of the current LMS from Moodle Workplace Version 4.4 to the selected LMS

· Task 3: LMS Operations and Maintenance Support: This supplies the required professional services for Project Management Support, Subject Matter Expert (SME) Support, and Software Engineer Support to maintain and develop the WFLMS solution.

4. SCOPE OF EFFORT

The contractor must provide LMS Application and Platform Hosting Services and Support, to accept user data, course backup data, user training completion data, and learning programs data with full functionality; and LMS Operations and Maintenance Support to meet the requirements stated in this PWS. This includes all LMS application & hosting, configuration, testing, deployment, ongoing application or system patching, system security, and program support to the WFLMS Program. The LMS Application and Platform Hosting Services and Support, and Moodle Workplace Operations and Maintenance Support solution requirements must include:

· LMS with the AWS GovCloud (US) region solution.

· Hosting with Amazon Web Services (AWS) - AWS GovCloud with full integrated support between LMS and hosting solution.

· Subscription services for LMS.

· Complete transitional plan from Moodle Workplace Version 4.4 with current vendor to selected LMS.

· Training support for migration to selected LMS.

· Professional services support for ongoing maintenance and operations of LMS.

· Training content integration, support, and delivery.

· Supply WFLMS Program manager with Monthly, Quarterly, and Annual Hosting and LMS metrics The contractor must work with WFLMS Program to develop training materials for Category Managers, Course Creators and Editing Trainers in wildland fire management organizations identified by the WFLMS Program. The contractor must work with WFLMS Program Staff to deliver virtual training sessions to Category Managers, Course Creators and Editing Trainers in wildland fire management organizations identified by the WFLMS Program.

The WFLMS Program will ensure key personnel including Sponsors, Team WFLMS and key Subject Matter Experts will be available to support this project as required, and that the contractor must have access to WFLMS and other required systems as needed to provide support under this contract.

5. APPLICABLE DOCUMENTS

The Contractor is responsible for obtaining and maintaining all the documentation necessary for performance under this contract. The Contractor shall make any specific documentation requests, including applicable standards, known to the COR on an as-needed basis. Applicable standards under which specific work shall be accomplished include but are not limited to:

· WFLMS Program service center agency IT manuals and policy

· WFLMS Program departmental regulations

· Service center agency Configuration Management Standards and Practices

· Attachment 4 DOI IT Baseline Compliance Guidelines

6. ATTACHMENTS

Attachment 1 Quality Assurance Surveillance Plan Attachment 2 Certificate of Non-Disclosure Attachment 3 Certificate of No Conflicts of Interest Attachment 4 DOI IT Baseline Compliance Guidelines

7. TECHNICAL REQUIREMENTS

7.1 LMS Application Operations and Maintenance Support

The vendor will supply a complete solution for all LMS Operations and Maintenance to maintain full functionality, to include but not limited to the following areas and items:

7.1.1 Initial WFLMS LMS build, configuration, testing and release to all environments using the AWS GovCloud (US) region hosting solution.

7.1.2 Complete transitional tasks from previous vendor for solution release and go live.

7.1.3 Complete management of the AWS GovCloud (US) region for the LMS solution.

7.1.4 Security support services for the AWS GovCloud (US) region & Moodle Workplace LMS solution in alignment with the DOI, Federal Information Security Management Act (FISMA), and National Institute of Standards and Technology (NIST) standards and requirements.

7.1.5 Change management and configuration support for LMS and hosting solutions.

7.1.6 Management and alignment to the either Application lifecycle management (ALM) or Software Development Life Cycle (SDLC).

7.1.7 Support of administration of role access management for all users level roles.

7.1.8 Support design, development and implement customizations with reporting and new modules from LMS.

7.1.9 Supply secure Intrusion Detection & Continues monitoring solutions with AWS and LMS.

7.1.10 Project Management Support: The contractor must supply Project management support for the duration of the project including:

i. Status meeting support and status reports.

ii. Managing project schedules, tasks, quality, and budgets for all operations and maintenance (O&M) tasks and special projects.

iii. Communicating and coordinating with WFLMS Stakeholders at all levels.

iv. Supporting Communications with WFLMS System Administrators

v. Coordinating with DOI Contracting Officers, including project finances, proposals, estimates, and compliance issues on a regular basis.

vi. Assisting WFLMS Program in Department costing and resource estimates for identified projects.

vii. Assisting WFLMS Program Management in devising and implementing technical and business process solutions.

viii. Supporting LMS and Standard Operating Procedures (SOP) Documentation

ix. Supporting LMS complete configuration and complete testing for O&M and upgrades.

x. Supporting of LMS security and compliance requirements based on DOI, NITS, and FISMA requirements.

xi. Future system or component integration capability with WFLMS

7.1.11 LMS Subject Matter Expert (SME) Support: The contractor must supply SME support for the duration of the project including:

i. Provide LMS application expertise to the project team .

ii. Serve as the LMS point of contact for WFLMS Program

iii. Training content integration, support, and delivery.

iv. Support the ongoing configuration of the LMS application

v. Manage issue creation, tracking and status within the vendor ticket site for WFLMS Program

vi. Provide insight and recommendations on new LMS releases.

vii. Manage the approach and execution of any development efforts

viii. Support of the following Team WFLMS activities:

· Internal training

· User Acceptance Testing

· Change Management

· Standard Operating Procedure development

7.1.12 LMS Consultation Meetings. The contractor must participate in weekly consultation meetings for the duration of the project, not to exceed two hours each week, to provide:

i. Consultation, technical direction, and recommendations to streamline, improve and optimize the government’s use of the Moodle Workplace application.

ii. Documentation of the weekly consultation meetings and recommendations.

7.1.13 Development and implementation of a a Wildland Firefighter Apprenticeship Program (WFAP) apprentice learning tracking solution within the LMS application. The contractor must provide a solution that:

i. Provides the ability for apprentices to input hours of learning experience they complete outside of the formal Basic and Advanced WFAP Academies. The apprentice must be able to select the type of learning experience (e.g. on-the-job learning; elective hours for other courses completed; experiential learning experiences such as staff rides, participation in prescribed burns, etc.) as well as inputting hours to the nearest tenth of an hour.

ii. Routes to or makes available to the apprentice’s supervisor, or other designated approving authority, the input form for validation of hours input.

iii. Provides aggregate reports to WFAP staff, designated agency or regional WF training staff, apprentices, and supervisors of an individual’s progress within the entirety of the WFAP. WFAP staff and designated agency or regional WF training staff must be able to view progress for all apprentices within their area of responsibility.

iv. Provides the apprentice’s supervisor, or other designated approving authority, the ability to submit a removal request form to WFAP staff.

v. Creates a unified Apprentice Dashboard that integrates the progress or completion data from all aspects of the apprenticeship program that are required for successful completion.

vi. Provides a notification capability for key events that happen during the apprenticeship program (e.g. completion of hours required, changes in apprentice status, approval needed reminders, etc.)

vii. Allows external certificates from RAPIDS or other systems to be uploaded into Moodle Workplace and linked to the apprentice’s profile for viewing by the apprentice, WFAP staff or other designated training staff.

7.1.14 Development and writing of the necessary API calls for pushing course completion records to the Integrated Reporting of Wildfire Information (IRWIN) application.

i. The course completion records pushed to IRWIN will include the course full name, the course official code (a custom course field), the course completion date, the learner’s last name, the learner’s first name, the learner’s unit (a custom profile field), the learner’s dispatch unit (a custom profile field to be added to the user profile) and the learner’s IRWIN Resource ID (a custom profile field.

ii. The development must be consistent with the IRWIN Integration Specification Learning API v10 last updated August 29, 2024. This document is available for download on the wildfire.gov site.

iii. The records to be pushed must be checked to ensure there are no null fields other than the learner’s unit and the learner’s dispatch unit. If there are other null fields, then the records must not be pushed and must be flagged in some fashion so the government site administrators or training personnel can take appropriate action to correct the record.

7.1.15 LMS Software Engineer Support: The contractor must supply Software Engineer support for the duration of the project including:

i. Providing technical direction, consultation, and recommendations

ii. Troubleshooting high level issues

iii. Installing upgrades, patches, and new modules

iv. Designing, developing and implementing customizations and reporting

v. Supporting the transfer of data between environments

vi. Developing/Updating interfaces as needed

vii. Installing, configuring and troubleshooting any LMS Plug-Ins requested by WFLMS Program

7.2 LMS Platform Hosting Services and Support: Amazon Web Services (AWS) - AWS GovCloud

7.2.1 Supply WFLMS with a complete managed AWS hosting services in a world-class redundant peering environment for Internet connectivity, allowing unprecedented fault tolerance

7.2.2 Supply transition and O&M hosting services with Amazon Web Services (AWS) - AWS GovCloud (US) region directly aligned to the O&M of the WFLMS Moodle Workplace LMS solution

7.2.3 The supplied Hosting Services will include on-going operations and maintenance, technical support and monitoring of the database, content and web servers, full load balancing, with auto backup of the production database data and network failover design. In addition, hosting services will include immediate identification of an outage within 5 minutes, and a quick response to correct the problem. Production environments maintained by vendor include will be Service Level Agreement compliant maintaining a 99.5% uptime. In the event of a Production environment outage, the contractor must provide an outage report with a detailed description of the event and the corrective action taken to restore services

7.2.4 Supply WFLMS Program with monitoring of the bandwidth utilization and make timely recommendations.

7.2.5 Supply government with monitoring alerts and taking simple corrective action (i.e. – restarting the application or web server, rebooting the machine, changing server or firewall configurations, etc.)

7.2.6 Hosting services include:

i. 24 x 7 monitored networks

ii. 24 x 7 performance monitoring

iii. Performance guarantees for server response

iv. Load balancing and architecture to handle redundancy and heavy traffic

v. Backups of the database system are to be managed by vendor to ensure data integrity. The use of industry best practices will be utilized to maintain the backup data. This includes, at minimum, daily incremental backups, and weekly full backups

7.2.7 Alternate storage site. Establishes an alternate storage site including necessary agreements to permit the storage and retrieval of information system backup information; and ensures that the alternate storage site provides information security safeguards equivalent to that of the primary site.

7.2.8 180 day max off-site retention available

7.2.9 Reacting to monitoring alerts and taking corrective action (i.e. – restarting the application or web server, rebooting the machine, changing server or firewall configurations, etc.) – This does not include editing any code or any type of professional services

7.2.10 Restarting services or processes

7.2.11 Creating/editing firewall rules

7.2.12 Performance and usage monitoring (recommending upgrade or service if applicable)

7.2.13 Cloud Partnership: Contractor must currently have or be able to setup presences in the AWS GovCloud (US) region.

7.2.14 The vendor with AWS Cloud will provide a broad set of infrastructure services, such as computing power, storage options, networking, and databases, delivered as a utility: on- demand, available in seconds, with pay-as-you-go pricing.

7.2.15 The contractor must partner with the AWS GovCloud (US) solution to supply an isolated AWS region designed to allow U.S. government agencies and customers to move sensitive workloads into the cloud by addressing their specific regulatory and compliance requirements. The AWS GovCloud (US) Region adheres to U.S. International Traffic in Arms Regulations (ITAR) requirements. The AWS GovCloud (US) Region supports the management of regulated data by offering the following features:

i. Restricting physical and logical administrative access to U.S. citizens only.

ii. Providing FIPS 140-2 endpoints.

7.2.16 The contractor must supply Hosting Configuration Management: The contractor must provide policy and procedure surrounding configuration management reviews and updated. The contractor must use an online inventory application to track hardware and software deployments in the hosting solution.

7.2.17 The contractor must provide hosting services and ongoing maintenance support for the environments listed below:

i. WFLMS Production Environment

ii. AWS GovCloud Infrastructure and Support

iii. SSL Certificate

iv. Security and compliance to WFLMS Program standards

v. Moodle Workplace build, configuration, and release

vi. WFLMS Development Environment

vii. AWS GovCloud Infrastructure and Support

viii. SSL Certificate

ix. Security and compliance to WFLMS Program standards.

x. Moodle Workplace build, configuration, and release

7.2.18 The contractor must include multi-factor authentication (MFA) as part of the solution.

7.2.19 Hosting Project Assumptions: WFLMS Program requires and agrees to the following Vendor assumptions.

i. The contractor must host the WFLMS environments in the AWS GovCloud, and all virtual machines will be dedicated to WFLMS Program.

ii. Backups are not to exceed 1.2TB per month.

iii. WFLMS Program Security will continue to maintain ownership of the Authority to Operate process and documentation. The contractor must function in a consultative role to provide environment or process specific information.

iv. Production environment sizing is intended to support standard WFLMS Program Production usage.

7.3 Transition-In:

The requirement includes a transition-in period, in accordance with the vendor’s quoted transition-in plan and schedule. The government estimates the transition will include 200,000 user profiles, 2,500 courses, 40 learning programs, 50 audiences and 20 user roles that must be transitioned from Moodle Workplace version 4.4. The vendor must be able to independently use a Moodle Workplace version 4.4 course backup file to re-create the same course in the vendor’s LMS, without the Government’s assistance. The vendor must anticipate that capturing a database snapshot from Moodle Workplace version 4.4 to migrate courses may not be available and that migration requires the vendor do manual course backups and restore. The government requires that the vendor collaborate with OWF’s current vendor to execute a successful and efficient transition of service. Key milestones for this transition are outlined below.

· Kick-off meeting and confirmation of Transition Schedule and Plan to include key stakeholders from all parties.

· Back up and document transitions for all systems, data, and content

a. File Directories (and content for lower tier systems). Production and Development.

b. Databases for all systems.

c. Content Server

· LMS Infrastructure Provisioning and Configuration (Initial)

· LMS system transitions

a. Production

b. Development

· UAT Testing of system performance

· Production Refresh Data

· Final Production Refresh – freeze – cutover(s)

7.4 Transition-Out

The requirement includes a transition-out period of 20 business days prior to the end of the POP. The vendor must provide a transition-out plan for the Government’s approval no later than three months prior to the PoP end date. The government requires that the vendor collaborate with the incoming vendor to execute a successful and efficient transition of service. Key milestones for this transition are outlined below.

· Back up and document transitions for all systems, data, and content

a. File Directories (and content for lower tier systems). Production and Development.

b. Databases for all systems.

c. Content Server

· LMS Infrastructure Provisioning and Configuration (Initial)

· LMS system transitions

a. Production

b. Development

· UAT Testing of system performance

· Production Refresh Data

· Final Production Refresh – freeze – cutover(s)

8. SECURITY REQUIREMENTS

The contractor’s solution must:

i. Meet application, hosting, architectural, planning, and other security requirements necessary to achieve FISMA Assessment &Authorization (A&A). As needed, the contractor must provide support for current Authority to Operate (ATO) documentation, issued at the minimum of FISMA-Moderate level, by a U.S. Federal agency and/or the FedRAMP program

ii. Comply IaaS and SaaS requirements including regulations pertaining to the United States Government Configuration Baseline (USGCB) or formerly known as Federal Desktop Core Configuration (FDCC), and Security Content Automation Protocol (SCAP)

iii. Comply with Attachment 4 DOI IT Baseline Compliance Guidelines

iv. Be kept current with the most recent vendor product version. The contractor must submit a project plan for transition to all new versions

v. Upon awared, the vendor must provide:

a) System Security Plan (SSP) for the contracted system;

b) Security Assessment Report (SAR) provide by a FedRAMP recognized Third Party Assessment Organization (3PAO);

c) Information System Continuous Monitoring Plan (ISCMP) describing ongoing monitoring of the contracted system’s security monitoring;

d) System Contingency Plan describing how agency service and information is protected and recovered in case of an outage

e) System Incident Response Plan describing how the contractor minimizes and recovers from information system security incidents (attacks).

vi. Be an extremely scalable model to support the entire organization

vii. Have no failed implementations

9. PERIOD OF PERFORMANCE

The base period of performance will be 1/5/2026 to 1/4/2027.

10. PLACE OF PERFORMANCE

Work will be performed at the Contractor location. It is anticipated most of the work will be performed virtually. The Contractor must comply with the DOI IT Security policy.

11. TRAVEL

No travel is required in the performance of this contract.

12. KEY DELIVERABLES

12.1 Deliverable Table

a)System Security Plan (SSP) for the contracted system;

b)Security Assessment Report (SAR) provide by a FedRAMP recognized Third Party Assessment Organization (3PAO);

c)Information System Continuous Monitoring Plan (ISCMP) describing ongoing monitoring of the contracted system’s security monitoring;

d)System Contingency Plan describing how agency service and information is protected and recovered in case of an outage e)System Incident Response Plan describing how the contractor minimizes and recovers from information system security incidents (attacks).

12.2 Deliverable Acceptance

The deliverables required hereunder will be inspected for conformance with the terms, conditions, and specifications contained herein.

1) Reports, documents, and narrative type deliverables will be accepted when all discrepancies, errors, or other deficiencies identified in writing by the Government have been corrected.

2) If the draft deliverable is adequate, the Government may accept the draft and provide comments for incorporation into the final version.

3) All Government comments to deliverables must either be incorporated in the succeeding version, or the contractor must demonstrate, to the Government's satisfaction, why such comments should not be incorporated.

4) If the Government finds that a draft or final deliverable contains spelling errors, grammatical errors, improper format, or otherwise does not conform to the requirements stated within this contract, the document may be immediately rejected without further review and returned to the contractor for correction and re-submission. If the contractor requires additional Government guidance to produce an acceptable draft, the contractor shall arrange a meeting with the COR.

12.3 Deliverable Quality Assurance and Acceptance

The COR will review for completeness draft and final documentation that the contractor submits and may return it to the contractor for correction. Absence of any comments by the COR will not relieve the contractor of the responsibility for complying with the requirements of the order. The contractor shall not construe any letter of acknowledgment of receipt of material as a waiver of review or as an acknowledgment that the material is in conformance with this PWS. Any approval given during preparation of the documentation or approval for shipment shall not guarantee the final acceptance of the completed documentation. Final approval and acceptance of documentation required herein shall be by written approval and acceptance by the COR.

12.4 Non-Conforming Deliverables

Non-conforming products or services will be rejected. Deficiencies will be corrected by the contractor within five (5) business days of the rejection notice. If the deficiencies cannot be corrected within five (5) business days, the contractor shall immediately notify the COR of the reason for the delay and provide a proposed corrective action plan within two (2) business days.

13. NON-DISCLOSURE AGREEMENT (NDA) & ORGANIZATIONAL CONFLICT OF INTEREST (OCI) AGREEMENT Contractor employees who will have access to DOI information or will develop custom applications must sign Attachment 3 Non-Disclosure Agreement and Attachment 4 Organizational Conflict of Interest Agreement prior to gaining access to any information or the DOI system. Copies of the signed NDA and OCI will be maintained in the contract file.

All information regarding the work products developed and made available to the contractor under the contract and resulting orders must be regarded as sensitive information by the contractor and not be disclosed or used in any other way than on the performance of this contract to anyone outside the contractor’s organization or outside the DOI without the written permission of the Government. This includes, conference calls, in person meetings, and other various means of communications.

All contractor personnel shall sign an NDA and organizational OCI certification. The contractor shall take all reasonable precautions not to divulge information about the requirement and/or use this information for the contractor’s gain and shall not divulge any information to any other organization (outside the DOI) without written permission from the Government.

ATTACHMENT 1 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP)

For: Department of the Interior (DOI) Office of Wildland Fire (OWF) Wildland Fire Learning Management System (WLMS) Contract Number: To be completed at time of award Contractor’s name: To be completed at time of award (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.

The following FAR clauses may apply depending on contract type:

52.246-4 Inspection of Services – Fixed-Price

2. GOVERNMENT ROLES AND RESPONSIBILITIES.

The following personnel shall oversee and coordinate surveillance activities.

a.) Contracting Officer (CO) - The CO 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 CO shall also assure that the Contractor receives impartial, fair, and equitable treatment under this contract. The CO is ultimately responsible for the final determination of the adequacy of the Contractor’s performance.

Assigned CO: Ali Tsybulevsky Organization or Agency: DOI Interior Business Center (IBC) Acquisition Services Directorate (AQD) Telephone: 703-964-3682 Email: Alexandra_tsybulevsky@ibc.doi.gov b.) Contracting Officer’s Technical Representative (COTR/COR) - The COTR/COR is responsible for technical administration of the contract and shall assure proper Government surveillance of the Contractor’s performance. The COTR/COR shall keep a quality assurance file. At the conclusion of the contract or when requested by the CO, the COTR/COR shall provide documentation to the CO. The COTR/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 and / or terms or conditions to the CO for action.

Assigned COTR/COR: To be completed at time of award Telephone: To be completed at time of award Email: To be completed at time of award

3. CONTRACTOR REPRESENTATIVES.

The following employee of the Contractor serves as the Contractor’s Program Manager for this contract.

a.) Program Manager - To be completed at time of award Telephone: To be completed at time of award Email: To be completed at time of award

4. PERFORMANCE STANDARDS.

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

Performance standards are specified in the PWS where applicable. The Government shall use these standards to determine Contractor’s level of performance. The Government shall compare the Contractor’s performance to the Acceptable Quality Level (AQL) that is established in the PWS.

5. INCENTIVES.

The Government shall use past performance ratings as incentives. Incentives shall be based on exceeding, meeting or not meeting performance standards.

6. METHODS OF QA SURVEILLANCE.

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

Regardless of the surveillance method, the COTR/COR shall always contact the Contractor's Program Manager or on-site representative when a defect is identified and inform the manager of the specifics of the problem. The COTR/COR, with assistance from the PM, shall be responsible for monitoring the Contractor’s performance in meeting a specific performance standard/AQL.

The COTR/COR shall also inform the Contracting Officer of any defect that has been identified.

a.) MANAGEMENT INFORMATION SYSTEMS (MIS). (Evaluates outputs through the use of management information reports. Best used for general surveillance and may need to be supplemented by periodic inspections.) - 99.5% Service level agreement compliance b.) PROGRESS OR STATUS MEETINGS. – Weekly status meetings in accordance with PWS section 13 Key Deliverables.

c.) ANALYSIS OF CONTRACTOR'S PROGRESS REPORTS. (Evaluate cost, schedule, etc.) – Review of the monthly status reports in accordance with PWS section 13 Key Deliverables.

Surveillance results may be used as the basis for actions (to include payment withholdings) against the Contractor. In such cases, the Inspection of Services clause in the contract becomes the basis for the CO’s actions.

7. RATINGS.

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

8. 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 or incentive fee payments or other actions.

b.) UNACCEPTABLE PERFORMANCE.

When unacceptable performance occurs, the COTR/COR shall inform the Contractor and the Contracting Officer. Notice to the Contractor will normally be in writing unless circumstances necessitate verbal communication. In any case the COTR/COR shall document the discussion and place it in the COTR/COR file.

When the COTR/COR determines formal written communication is required, the COTR/COR shall prepare a Contract Discrepancy Report (CDR) and present it to the Contractor's Program Manager or on-site representative. A copy of all CDRs shall be forwarded to the Contracting Officer and maintained in the official contract file. 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 COTR/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 withholdings, fixed fee reductions, award / incentive fee nonpayment or other actions deemed applicable by the CO.

10. FREQUENCY OF MEASUREMENT.

a.) FREQUENCY OF MEASUREMENT.

During contract/order performance, the COTR/COR shall take measurements, monthly, and shall analyze whether the negotiated frequency of measurement is appropriate for the work being performed.

b.) FREQUENCY OF PERFORMANCE ASSESSMENT MEETINGS.

The COTR/COR shall meet with the Contractor monthly to assess performance and shall provide a written assessment.

PREPARED BY:

John (Rick) Gividen Contracting Officer’s Representative

PERFORMANCE REPORT

CONTRACT NUMBER: <insert number>

PREPARED BY: (Name of COTR/COR) <insert name>

DATE AND TIME OF OBSERVATION:

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 COTR/COR’s name>

CONTRACT DISCREPANCY REPORT (CDR)

CONTRACT NUMBER: <insert number> TO: (Contractor’s Program Manager or on-site representative) <insert name> FROM: (Name of COTR/COR) <insert name>

DATE AND TIME OBSERVED DISCREPANCY:

DISCREPANCY OR PROBLEM:

<Describe in detail. Identify any attachments.>

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. >

PREPARED BY: <Enter COTR/COR’s name>

Received by:

Signature – Contractor’s Program 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’s performance.

PWS ATTACHMENT 2 CERTIFICATE OF NON-DISCLOSURE

CONTRACTOR

Non-Disclosure Agreement between the U.S. Department of the Interior and Contractor Employee or Other External Entity Granting Conditional Access to Information

This agreement applies to Task Order #XXX

· Items lined out for any reason contained in this non-disclosure statement by the signatory, shall cause the signatory to be removed from the project without further consideration, and all USAID credentials removed.

I, _________________________________________(Print Full Name Legibly), hereby consent to this agreement in consideration for my being granted conditional access to certain United States Government documents or materials containing USAID information. I understand and agree to the following terms and conditions:

1. Sensitive but unclassified information is any information, the loss, misuse, or unauthorized modification of which could adversely affect the national interest, the conduct of Federal programs, or the privacy to which individuals are entitled under Title 5 U.S.C. paragraph 552a, but which has not been specifically authorized to be kept secret in the interest of national defense or foreign policy.

1. Upon the execution of this agreement, I may be granted conditional access to sensitive information and other business/confidential information not covered under the above definition of sensitive but unclassified information. This information concerns USAID and other Governmental agencies. Information may be in the form of system data, files and records, contract data, contract pricing, independent price estimates, analyses, memos, meeting content, conversations, or any other form.

1. I will not use, release, or disclose any information or data, in any form whatsoever, to any person or entity except as is necessary to perform the duties under the above-cited contract or except as authorized by the Contracting Officer or the Contracting Officer’s Representative. I will not take, alter, or convert such information to any use not specifically authorized under the contract or this agreement.

1. I will not seek access to non-public information beyond what is required for the performance of my duties under the above-cited contract.

1. I will ensure that my status as a contractor employee is known when seeking access to and receiving non-public information.

1. I will protect all sensitive information in accordance with the provisions of 18 U.S.C. 1905 (Trade Secrets Act), 5 U.S.C. 552 (Privacy Act of 1974), P.L. 104-294 (Economic Espionage Act of 1996), P.L. 103-339 (Counterintelligence and Security Enhancement Act of 1994), and other pertinent laws and regulations governing the confidentiality of privileged information. If I become aware of any improper use, release or disclosure of non-public information, I will advise the Contracting Officer as soon as possible.

1. I will surrender any written or electronic non-public information given to me pursuant to this agreement, including my own notes, upon completion or termination of my duties under the above-cited contract, or upon the request of the Contracting Officer, Contacting Officer’s Technical Representative, or my supervisor.

1. Unless and until I am provided with a written release from this agreement, all conditions and obligations contained herein apply both during my period of conditional access and at all times thereafter.

1. I will submit any book, article, column or other written work for general publication that is based upon any knowledge that I obtained pursuant to this agreement to USAID for security review, prior to submission for publication, to ensure that no sensitive information is disclosed.

1. I hereby assign to the United Stated Government all royalties and remuneration that have resulted or will result from any use, release or disclosure that is inconsistent with this agreement.

1. I understand that any unauthorized use, release or disclosure of non-public information in violation of this agreement may subject me and/or my employer to administrative, civil, or criminal remedies as may be authorized by law.

1. These provisions are consistent with and do not supersede, conflict with, or otherwise alter the employee obligations, rights, or liabilities created by existing statute or Executive order relating to (1) classified information, (2) communications to Congress, (3) the reporting to an Inspector General or the Office of Special Counsel of a violation of any law, rule, or regulation, or mismanagement, a gross waste of funds, an abuse of authority, or a substantial and specific danger to public health or safety, or (4) any other whistleblower protection. The definitions, requirements, obligations, rights, sanctions, and liabilities created by controlling Executive orders and statutory provisions are incorporated into this agreement and are controlling.

Signed By: __________________________________________ (Contractor Employee) / Date Reviewed

Approved By: _______________________________________ DOI Contracting Officer / Date (Authorized Government Official)

PWS ATTACHMENT 3 CERTIFICATE OF NO CONFLICT OF INTEREST

CONTRACTOR

Certificate for No Organizational Conflict of Interest

This agreement applies to Task Order #XXX

I certify that I am not aware of any matter that might limit my ability to work on the task order and other related actions in an objective and unbiased manner or which might place me in a position of a conflict, actual, potential, or apparent, between my responsibilities as a support contractor.

In making this certification, I have considered all my stocks, bonds, voluntary commitments and other financial interests, and employment arrangements (past, present, or under consideration) and, to the extent known by me, all the financial interests and employment arrangements of my spouse, my minor children, and other members of my immediate household.

If, after the date of this certification, any person, firm, or other organization with which, to my knowledge, I (including my spouse, minor children, and other members of my immediate household) have a financial interest, or with which I have (or had) an employment arrangement, becomes involved in the acquisition I am responsible for, I will notify the Contracting Officer of this apparent conflict of interest. In such case, until advised to the contrary, I will not participate further in any way.