Solicitation_PC-17-Q-030_Amendment_0001_Posted_3.29.docx

DOCX document 182 KB Posted

Attached to
Peace Corps Learning Management System Federal contract opportunity
Solicitation number
PC-17-Q-030
Issued by
Peace Corps

About this file

RFQ PC-17-Q-030 Amendment 0001

View the file

Other files for this federal contract opportunity

Other files attached to Peace Corps Learning Management System, newest first.
File Type Posted
Solicitation_PC-17-Q-030_Amendment_0003.docx DOCX document
RFQ_Questions_and_Answers_4.13.17.xlsx XLSX spreadsheet
Solicitation_PC-17-Q-030_Amendment_0002.docx DOCX document
ATTACHMENT_2_-_Functional_and_Technical_Requirements_(Final).xlsx XLSX spreadsheet
RFQ_Questons_and_Answers.docx DOCX document
ATTACHMENT_6_-_Plugins_overview.docx DOCX document
Attachment_11_-_Security_Policies_&_Procedures_Peace_Corps_Manual_Section_542.pdf PDF
Solicitation_PC-17-Q-030.docx DOCX document
ATTACHMENT_2_-_Functional_and_Technical_Requirements_(Final).xlsx XLSX spreadsheet
ATTACHMENT_4_-_SF-182_Requirements.docx DOCX document
Attachment_9_-_Offeror_Representation_and_Certifications.docx DOCX document
ATTACHMENT_3_-_Data_Migration.docx DOCX document
ATTACHMENT_5_-_Workflows.docx DOCX document
Attachment_14_-_Form_SF_1449.pdf PDF
Attachment_13_Solution_Delivery_Framework_SOP_v5.pptx PPTX presentation
Attachment_10_-_Peace_Corps_Manual_Section_899,_Breach_Notification_Response_Plan.docx DOCX document
Attachment_8_Domestic_Vendor_File_Form.pdf PDF
Attachment_1_Pricing_Table.xlsx XLSX spreadsheet
Attachment_7_-_Demonstration_Requirements.docx DOCX document
Show all 19

On GovTribe

Work with this file on GovTribe

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Peace Corps Learning Management System (LMS) Solicitation PC-17-Q-030

SECTION 1 – PRICING SCHEDULE

1.1 GENERAL

The Contractor shall design, configure, deploy, and support a Software as a Service (SaaS) LMS for Peace Corps Staff and Volunteers that meets the objectives, technical and functional requirements listed herein.

1.2 Order Type

A hybrid Firm-Fixed-Price (FFP), Time-and-Materials (T&M), and Labor Hour (LH) contract will be awarded to a Contractor under this Request for Quotation (RFQ) to provide a Learning Management System for the Peace Corps. The resultant contract shall incorporate the Contractor’s completed pricing table (see Attachment No. 1).

1.3 Contract Line Items (CLINs)

Contract line item numbers (CLINs) are unique numbers associated with each separately priced item in the contract. The CLINs listed below are also included in Attachment No. 1 “Pricing Table”. The Contractor shall propose all CLINs as identified below, in Attachment 1, and as instructed in Section 7.3.2 below.

1.3.1 CLIN 0001: LMS Staff and Volunteer Solution (FFP) (Tasks 2.4.1, 2.4.2, 2.4.3):

The contractor shall propose a FFP consisting of all efforts related to the design, configuration, integration, deployment, and initial System Administrator and Content Manager training, and support (including low-bandwidth) of the Learning Management System (LMS).

1.3.2 CLIN 0002 (and if exercised option CLINs 0006, 0010, 0014, 0018): Supplemental Support Services (FFP)(Task 2.4.4):

The Contractor shall propose a FFP for ongoing support of the LMS in accordance with SOO Section 2.4.4. The price shall be inclusive of the necessary software hosting, license(s) and technical support for the LMS. In the contract Base Year support under this CLIN is only appropriate post the go-live date (full deployment).

1.3.3 CLIN 0003 (and if exercised option CLINs 0007, 0011, 0015, and 0019): Customizations (LH) (Task 2.4.5):

The Contractor shall propose fully-burdened hourly rates for Peace Corps requested customization to the LMS in accordance with SOO 2.4.5 below. Services provided on a Labor Hour basis shall be billed at the hourly rates proposed and incorporated in Attachment 1 “Pricing Table”. All hourly rates shall be fixed unit prices that include all costs and profit necessary to provide the level of service specified in the contract.

1.3.4 CLIN 0004 (and if exercised option CLINs 0008, 0012, 0016, and 0020): Training Support Services (LH)(Task 2.4.6):

The Contractor shall propose fully-burdened hourly rates for Training Support Services in accordance with SOO 2.4.6. These services may include, but are not limited to, in-person training courses for multiple Content Managers or System Administrators regarding system functionality or new functionality upgrades, or over-the-phone consultations on issues of a limited scope. Services provided on a Labor Hour basis shall be billed at the hourly rates proposed and incorporated in Attachment 1 “Pricing Table”. All hourly rates must be fixed unit prices that include all costs and profit necessary to provide the level of service specified in the contract. These CLINs do not include the initial deployment training for System Administrators and Content Managers already included in CLIN 0001

1.3.5 CLINs 0005, 0009, 0013, 0017, and 0021 (if exercised): Other Direct Costs (T&M) (Task 2.4.4):

This line item represents other direct costs related to each respective customizations CLIN. Other direct costs may include incidental material and other costs related to labor hours performed under customizations CLINs. The ceiling cost for this line item has been included by the Government in Attachment 1 – Pricing Table and will be included in the contract at award in the amount of $50,000 per contract year.

1.4 TRAVEL

There will be no travel reimbursement to the Contractor for travel within the Washington D.C. metropolitan area. Any requirements for travel outside of the Washington, DC area (non-local travel) will be identified and negotiated in future modifications under this task order. All non-local travel shall be approved in advance by the Contracting Officer Representative (COR). Reimbursement for actual (approved) travel costs incurred during the performance of support services shall be in accordance with part 31 of the Federal Acquisition Regulations and the Federal Travel Regulations (FTR). Travel requirements under this contract shall be met using the most economical form of transportation available. If economy class transportation is not available, the Contractor must submit (to the COR) a request for advance approval to utilize higher class travel. All travel should be scheduled sufficiently in advance to be able to take advantage of offered discount rates. Individual ‘travel authorization letters’ may be provided to the contractor (for all contractor personnel who are required to travel) which may allow contractor personnel to receive government rates when on long distance travel. The federal travel regulations and per diem rates can be accessed at: www.gsa.gov and type “FTR” in their search box. No travel reimbursement will be authorized unless the Contractor provides sufficient written evidence of actual travel costs incurred to include, but not limited to receipts, ticket stubs, registers, and/or other documentation, as required by the Government.

SECTION 2 – STATEMENT OF OBJECTIVES (SOO)

2.1 Purpose

The purpose of this SOO is to outline the requirements for a Learning Management System (LMS) to support the learning and staff development needs of Peace Corps Volunteers and Staff.

2.2 Background

Peace Corps is an independent civilian executive agency of the Federal Government established in 1961 by President John F. Kennedy to promote world peace and friendship through the service of American Volunteers abroad. Peace Corps Volunteers enlist for a two-year term of service in interested countries in need of trained manpower. The Volunteers’ service fulfills the three primary Peace Corps goals established in the founding legislation:

Improve the lives of people through grassroots assistance, Foster a better understanding of Americans on the part of the people served, and Foster a better understanding of other people on the part of Americans.

The Agency is seeking a qualified Contractor to implement a new Learning Management System for the agency’s globally deployed user base. The solution(s) will replace the current LMS system deployed at Peace Corps. The new solution(s) will support the agency’s efforts to:

· Provide, track, and monitor training to all staff, both Federal mandatory and non-mandatory training.

· Provide, track and monitor training to Peace Corps Volunteers throughout the service lifecycle.

2.2.1 Current Learning Management Business Process for Staff and Volunteers Peace Corps currently has two LMS sites (2 Moodle Instances, externally hosted), one for staff members (called PC University) and one for volunteers (called LearningSpace). Further details related to these sites, including the urls, can be found in Attachment 3 – Data Migration. Both sites are administered by Peace Corps staff members at headquarters. When a staff member or Volunteer joins Peace Corps, an account is set up for them on the appropriate site and an automated welcome message along with their login credentials is sent to their email account. Custom profile fields are also automatically populated for them, which denote their region and country of service, as well as the general sector of service and specific job within that sector. For example, John Smith’s Volunteer profile shows that he will serve in Africa, in Uganda, in the Education sector, and as a Teacher Trainer at Primary Teachers College. These profile fields are used to enroll students in courses specific to their job and post. For example, Health sector Volunteers around the world are enrolled in the HIV Basics course, as are all Volunteers going to Africa regardless of sector. Education Volunteers serving in specific countries in Teaching English as a Foreign Language TEFL jobs (but not other education-related positions) are enrolled in (TEFL) courses. The volunteers currently use this system very rarely (about once per year), but we expect this to increase as more field offices utilize the LMS to support their local volunteer training efforts. We expect staff use will grow as more courses are added during the next several years. Over the last year, there were 13,000 course completions.

2.3 Technical/Current State Overview

2.3.1 Peace Corps Environmental Overview

The Peace Corps workstations are currently configured as follows: Windows version 7, Microsoft Office 2010 (including Outlook 2010). The agency’s approved browsers are Microsoft Internet Explorer 11 and Chrome. The workstation environment is regularly updated. Deployed individuals, both Peace Corps staff and PCVs will access the LMS via a variety of different hardware (e.g. desktops, laptops, tablets, smartphones), and any viable LMS solution(s) shall be browser agnostic.

Peace Corps has Forefront Identity Manager (FIM) to manage user identities across systems (such as title, office, post, and similar user data).

2.3.2 Bandwidth issues

Some Peace Corps posts have very low bandwidth. The lowest support required is a 1MB connection with an average latency of 400ms.

2.3.3 Resource constraints

The Peace Corps has a high turnover rate. By Congressional mandate, 85% of employees leave within five years. The average employee lifespan is approximately three (3) years. Because of this, the Agency has constrained resources and must continually plan for succession. As a result, the Agency often has recurring needs for training in courseware uploading, courseware management, systems administration, and other areas.

2.3.4 Current Technology

The two currently-deployed LMSs (volunteer and staff) are Moodle 3.0 based. The Government is interested in a Moodle-based LMS solution, but is also open to any solution that allows migration of legacy data and courses, while maintaining course integrity.

2.3.5 Legacy Data

Within the existing LMS, data includes:

· Courses. At least 50 Moodle-based courses containing SCORM packages, Power Point slides, and pdf files exist in the LMS.

· Tests/Quizzes. Peace Corps estimates that at least 50 courses have assessments that were created using the core Moodle quiz activity.

· User data: Approximately 9,000 Volunteers and Trainees and 3,000 staff have the following data that could be provided in a flat file:

· Volunteer user profiles. In the current volunteer system, the Peace Corps LMS Administrator populates these fields via manual entry or bulk flat file import. While the new system may have additional or modified fields, the current fields include:

· Last name

· First name

· Email address

· Username

· Password

· Volunteer ID # (maximum of 9 digits)

· Volunteer Status - There are only four that we depend on:

· Accepted (ACC)

· Entry on Duty (EOD)

· Start of Service (SOS)

· Close of Service (COS)

· Assignment Type (There are only three that we depend on: PCV, PCR, Staff)

· Region/Location - There are only five that we use:

· Africa

· Europe/Mediterranean/Asia (EMA)

· Inter-America Pacific (IAP)

· Headquarters (HQ)

· Regional Recruitment Office (RRO)

· Post (The field should allow up to 45 characters)

· Sector (There are only six that we use: Agriculture, Youth in Development, Environment, Community Economic Development, Health, Education)

· Project (The field should allow up to 80 characters)

· HQ Staff Office (The field should allow up to 45 characters)

· Staff Position Title (The field should allow up to 45 characters)

· Staff user profiles. In the current staff system, the Peace Corps LMS Administrator populates these fields via manual entry or bulk flat file import. While the new system shall have additional or modified fields, the Peace Corps envisions that staff fields will include:

· Last name

· First name

· Email address

· Username

· Password

· Supervisor or Individual role

· Supervisor y/n

· Supervisor name (last, first)

· Supervisor’s contact information

· Supervisor email

· Entry on duty date

· Tour end date

· Real position title

· Series (for USDH)

· Personal Service Contract (PSC) Y/N

· Assigned office if HQ, e.g. OGO/OPATS/KLU

· Status (active or not)

· Test scores

· Course completion

2.4 Scope

The Contractor shall design, configure, deploy, and support a Software as a Service (SaaS) LMS for Peace Corps Staff and Volunteers that meets the objectives, technical and functional requirements listed herein. The system shall support up to 3,000 staff and 9,000 Volunteers and Trainees.

2.4.1 LMS

The LMS solution shall be accessible to all Peace Corps Staff (for example: United States Direct Hires (USDH), Host Country Nationals (HCN), and Personal Service Contractors (PSC)) and Peace Corps Volunteers (PCVs) (for example: invitees, Trainees, and Volunteers) via a web interface. Given the mission of the Peace Corps to promote world peace and friendship, staff and PCVs are often deployed to locations with little access to the Internet. The LMS solution must meet Federal security (FedRAMP Certification or FISMA-compliant Authorization to Operate [ATO] from the Peace Corps) and compliance requirements (Federal Information Processing Standard (FIPS 200 and Nation Institute of Standards and Technology (NIST) guidelines), must comply with OMB M-15-13 Policy to Require Secure Connections Across Federal Websites and Web Service, have low-bandwidth capabilities, auto-save/rapid refresh, the ability to track users, have a mobile interface, and the ability to track courses/learning paths within the LMS. In developing and operating the LMS Solution the contractor shall meet all requirements listed in Attachment 2 – Functional and Technical Requirements, and comply with all policies and procedures listed in Attachments 10 and 11. The LMS solution shall allow for the managing and monitoring of all learning activities (virtual and face-to-face), while providing an intuitive end user experience. The Government prefers a single solution for a Staff and Volunteer LMS, however, the Government requirement for a LMS may be met with a single solution or a separate LMS for staff and Volunteers. If one solution is proposed it must meet all the requirements for both the Staff and PCV within that one solution.

The LMS shall have the capability to extract data from a Standard Form (SF)-182 and populate a database for queries and reporting. The workflow can be interrogated to determine which SF182s are in progress and in what state along with being able to query the population of completed forms. Further details related to SF-182 requirements are found in in Attachment 4 – SF-182 requirements.

2.4.2 Data and Content Conversion and Migration

The contractor shall migrate legacy LMS data into the new solution(s) as well as convert and migrate legacy courses and their content.

The Contractor shall develop and submit a Data Conversion and Migration Plan (Deliverable item No. 8), which shall detail the Contractor’s approach (both technically and functionally) in migrating from Peace Corps current LMSs to the proposed solution within 10 days of holding an entry conference. The Data Conversion and Migration Plan shall include the approach to migrate both legacy user data and course content. Further details related to Data and Content Conversion and Migration are contained in Attachment 3 – Data Migration.

2.4.3 Initial Implementation and Set-up

The Contractor shall, in coordination with the Contracting Officer’s Representative (COR) and COR-identified Peace Corps staff, determine and implement the necessary LMS configurations, security requirements, customizations, and integrations with current Peace Corps systems, and facilitate a Configuration Workshop with LMS stakeholders within 10 days of the entry conference (Deliverables item No. 6). The workshop will be attended by 6-12 headquarters staff and about 6 post staff. The Contractor shall build clean, user-centered themes that have a look and feel, which is consistent with Peace Corps’ brand (please see www.peacecorps.gov as an example). This could include modifying current themes or a full custom build. As part of the theme development, the vendor will present no less than 3 prototypes based on the inputs received from the Peace Corps which will be used to arrive at the final theme selections and development. The Contractor shall develop a Configuration Workbook (Deliverable item No. 7) that authoritatively documents all aspects of the LMS, including custom configurations and integrations. This will be provided both in print and online with the ability for the Peace Corps to maintain and update. Please see ATTACHMENT 6 for the current list of plug-ins.

The Contractor shall develop, submit, and execute a test plan (Deliverable item No. 9), which shall detail the testing scenarios and scripts in which the system shall be evaluated prior to deployment. The test plan shall be submitted to the COR at the beginning of the test phase in accordance with the Contractor Project Management Plan CPMP. The Plan shall include scenarios and scripts for both system (Contractor) and UAT Testing. The LMS must successfully pass UAT with no more than five (5) Minor Flaws and zero (0) Critical Flaws. UAT must include system administrators, domestic staff (at headquarters and regional offices), and staff and Volunteers in the field. The Contractor shall resolve all flaws/issues during UAT within 10 calendar days. Minor/Critical Flaws are defined as follows:

1. Minor Flaw: An error with a workaround that allows the user to function normally.

2. Critical Flaw: An error that does not allow the user to function normally or the software does not function as designed.

The Contractor shall provide support and maintenance resources during the migration, soft launch, and LMS deployment phases to track and resolve any integration or implementation issues. Support resources shall be available to assist with support and maintenance of all functions within the LMS solution. The Contractor shall work with Peace Corps IT support to integrate user data feeds from existing Peace Corps systems. The contractor shall support creation of Volunteer and Staff user profiles within the LMS solution.

The Contractor shall provide training and training documentation to the Peace Corps COR, Systems Administrator and Course Managers during the soft-launch to the production environment. The Contractor shall track and resolve any integration, implementation or deployment issues prior to completion of the soft-launch.

The Contractor shall coordinate with the COR for full LMS deployment (go-live) to all Peace Corps users. Prior to production, the Contractor shall conduct training for Course and Content Managers and System Administrators, to take place at Peace Corps Headquarters. The Contractor shall submit FedRAMP certification or ATO certification documentation no later than three months prior to scheduled LMS deployment date.

Any customizations created for the Peace Corps are the property of the Government. Please see Sections 5.5 and 5.12 related to Data Rights.

The contractor shall complete a soft-launch within 5 months of contract award, and conclude data migration in time for final LMS deployment within 8 months of contract award.

2.4.3.1 Project Management

The Contractor shall conduct an Entry Conference Meeting within 10 days after contract Award.

The Contractor shall engage with Peace Corps stakeholders to learn about the Peace Corps environment and needs to build and submit a Contractor Project Management Plan (CPMP) within 10 days of the entry conference detailing their approach to the schedule, risks, configuration, integration, QA testing & UAT testing, draft support plan, training approach, and migration for the LMS. The CPMP shall also contain the draft Service-level Agreement (SLA) which shall define uptime expectations (≥99.8%), escalation procedures and response times.

The Contractor shall submit a complete training plan at least 20 days prior to LMS deployment (Deliverable item No. 12). As a part of the CPMP (Deliverable item No. 4), the Contractor shall outline their approach to initial user training and ongoing training and support, including identifying the periodic training of different users by role (e.g. System Administrator, Content Manager, etc).

The Contractor shall develop user guides (Deliverable item No. 11) and related training material to be included with the deployment of the LMS solution that provides technical and functional assistance to users by role, and will revise said materials due to any changes in the LMS that affect user roles. Such revisions shall be accomplished under supplemental support services CLINs. (User roles are defined in Attachment 2 – Functional and Technical Requirements.)

The Contractor shall participate in biweekly meetings throughout this project to review the project schedule and discuss any issues requiring resolution. The Contractor shall submit weekly reports (Deliverable item No. 5). The Contractor shall comply with the Peace Corps Solution Delivery Framework. (provided as Attachment 13)

2.4.4 Supplemental Support Services

After go-live, the Contractor shall provide support to include:

1. Maintenance (for example: patching, updates, fixes),

2. Maintaining Peace Corps customizations as exercised under CLINs 0003 0006, 0009, 0012, and 0015.

3. Service (response times, escalation of issues) as defined by the SLA,

4. Hosting, and

5. Any applicable license fees.

The Contractor shall provide an Operations and Maintenance Plan (Deliverable item No. 15) detailing the ongoing operational support of the LMS, including (but not limited to): Service Level Agreements (drafts as a part of the CPMP and as a final deliverable item No. 14) and tier 1/2/3 support options, recurring maintenance windows and schedules, recurring work and development efforts, and communications.

2.4.5 Additional Customization

Throughout contract performance The Peace Corps may identify areas of improvement or customizations to the LMS. The Peace Corps has already identified areas of interest as follows: user-centered themes that have a look and feel, which is consistent with Peace Corps’ brand, integration with Peace Corp’s SharePoint, integration with Peace Corp’s PC Live, integration with Lynda.com, and integration with OPM’s HR University.

To implement a customization the Peace Corps will provide the Contractor a detailed list of requirements and request a Level of Effort (LOE) estimate. The COR will review the LOE for technical acceptability and work with the Contracting Officer (CO) to authorize the work, if approved. The Contractor shall perform the work and submit a Task Summary following solution implementation. The Task Summary shall consist of the tasks completed, issues encountered, and resolutions. The report shall be provided to the COR in a format and forum approved by the COR.

The Peace Corps may purchase content or customizations from third party vendors. The Contractor shall provide an LOE to integrate the purchased features if requested. The COR will review the LOE for technical acceptability and work with the Contracting Officer (CO) to authorize the work, if approved. The Contractor shall perform the work and submit a Task Summary following solution implementation. The Task Summary shall consist of the tasks completed, issues encountered, and resolutions. The report shall be provided to the COR in a format and forum approved by the COR.

Any customizations created for the Peace Corps are the property of the Government. Please see Sections 5.5 and 5.12 related to Data Rights.

2.4.6 Training

At the Peace Corps’ discretion, the Contractor may be asked to provide additional training support services that may take the form of in-person training courses for new key users, over-the-phone consultations on issues of a limited scope, or other formats as necessary. Such training support services do not include those standard support services covered under section 2.4.4 and included in the contractor’s SLA. Training services may include, but are not limited to:

1. Training targeted courseware and content managers (either in-person and/or virtually) so that they can fully utilize the LMS’s features;

2. Training targeted systems administrators (either in-person and/or virtually) so that they can understand the full operation of the LMS, such as onboarding/offboarding learners, courseware uploads, reporting and tracking, etc.

At the Peace Corps’ discretion, the Contractor may be asked to provide remote or on-site systems administration services at Peace Corps Headquarters to bridge the departure of an existing administrator if necessary, or to supplement operational needs during times of resource constraints. This would be temporary or supplemental support to ensure continuity of an operational LMS. If required, the Contractor shall onboard/offboard LMS users, assist courseware managers, respond to users needing assistance, and other similar needs. The Contractor may also work directly with a Peace Corps Systems Administrator to help facilitate better understanding of the LMS features or functionality, or to provide consultation on the LMS solution, specifically on any additional integrations, configuration needs, etc.

2.4.7 End of Contract Transition Plan

The Contractor shall facilitate the retirement of the LMS solution(s) at the end of the contractual period of performance and provide a plan of action to migrate information and content to a new and/or replacement solution. The Contractor shall support the migration to the replacement. Peace Corps owns all data housed in the LMS.

2.5. Desired Qualifications of Key Personnel

2.5.1 Program Manager and Technical Lead Desired Qualifications:

2.5.1.1 Program Manager:

· Eight or more years of relevant experience working with solutions lifecycle development methodology serving as a business analyst on IT projects.

· Five or more years of experience managing LMS implementations.

· Experience utilizing collaborative communication skills and establishing productive working relationships agency-wide and/or across multiple business units.

· Experience meeting with clients of varying levels to gather, document, and analyze system specifications and requirements, work closely with developers and testers in the fast-paced environment.

· PMI Project Management Professional (PMP) certification.

2.5.1.2 Technical Lead:

· Five or more years of relevant experience working within a solutions lifecycle development methodology serving as a software developer or engineer.

· Five or more years of LMS implementation and development experience.

· Experience utilizing APIs and proven success at integrating LMS solutions and client’s deployed native and GOTS applications.

· Three or more years working as a developer or engineer in the federal space with an understanding of federal security requirements.

· Three or more years working as a developer or engineer with Federal IT systems, with clearly enumerated experience in addressing federal information security requirements for hosting and protecting data.

SECTION 3 – PERFORMANCE

3.1 Deliveries or Performance

The work to be performed under this contract will be primarily at the contractor facilities. When required for operations or training support services, work will be performed at Peace Corps Headquarters, located at 1111 20th Street NW, Washington, DC, 20526. All other work can be performed remotely.

3.2 Period of Performance

The period of performance for each CLIN shall be as follows:

a. Base Period CLINS

· CLIN 0001 - (Time of award) - thru 8 Months after contract award

b. Option CLINs –

· CLIN 0002 – (Date of Option Exercise)* – thru 12 Months after contract award

· CLIN 0003 - (Date of Option Exercise) – thru 12 Months after contract award

· CLIN 0004 - (Date of Option Exercise) – thru 12 Months after contract award

· CLIN 0005 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0006 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0007 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0008 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0009 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0010 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0011 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0012 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0013 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0014 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0015 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0016 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0017 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0018 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0019 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0020 - (Date of Option Exercise) – thru 12 Months after option exercise

· CLIN 0021 - (Date of Option Exercise) – thru 12 Months after option exercise

Option periods may be exercised in accordance with FAR Clause 52.217-9, Option to Extend the Term of the Contract (MAR 2000).

The latest option exercise dates for option CLINs are as follows:

· CLIN 0002* – 12 months after contract award

· CLIN 0003 – 12 months after contract award

· CLIN 0004 - 12 months after contract award

· CLIN 0005 – 12 months after contract award

· CLIN 0006 - 12 months after contract award

· CLIN 0007 - 12 months after contract award

· CLIN 0008 - 12 months after contract award

· CLIN 0009 - 12 months after contract award

· CLIN 0010 - 24 months after contract award

· CLIN 0011 - 24 months after contract award

· CLIN 0012 - 24 months after contract award

· CLIN 0013 - 24 months after contract award

· CLIN 0014 - 36 months after contract award

· CLIN 0015 - 36 months after contract award

· CLIN 0016 - 36 months after contract award

· CLIN 0017 - 36 months after contract award

· CLIN 0018 - 48 months after contract award

· CLIN 0019 - 48 months after contract award

· CLIN 0020 - 48 months after contract award

· CLIN 0021 - 48 months after contract award

*Note: CLIN 0002 Period of Performance only applies after delivery of the LMS. As such, it is anticipated that CLIN 0002, if exercised, will have a period of performance covering four (4) months total: 8 months after date of contract award thru 12 months after contract award. CLIN 0002 shall be priced using these assumptions, however the Government reserves the right to exercise CLIN 0002 in accordance with the period of performance and latest option exercise dates listed above.

3.3 Notice to the Government of Delays

In the event the Contractor encounters difficulty in meeting performance requirements, or when the Contractor anticipates difficulty in complying with the contract delivery schedule or completion date, or whenever the Contractor has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this contract, the Contractor shall immediately notify the Contracting Officer and the COR, in writing, giving pertinent details; provided, however, that this data shall be informational only in character and that this clause shall not be construed as a waiver by the Government of any delivery schedule or date, or any rights or remedies provided by law or under this contract.

3.4 Option to Extend Term of Contract (FAR 52.217-9) (MAR 2000)

a. The Government may extend the term of this contract by written notice to the Contractor at any time within the term of the contract, provided that the Government gives the Contractor a preliminary written notice of its intent to extend at least fifteen (15) days before the contract expires. The preliminary notice does not commit the Government to an extension.
b. If the Government exercises this option, the extended contract shall be considered to include this option clause.
c. The total duration of this contract, including the exercise of any options under this clause, shall not exceed sixty (60) months.

3.5 Option to Extend Services (FAR 52.217-8) (Nov 1999)

The Government may require continued performance of any services within the limits and at the rates specified in the contract. These rates may be adjusted only as a result of revisions to prevailing labor rates provided by the Secretary of Labor. The option provision may be exercised more than once, but the total extension of performance hereunder shall not exceed six (6) months. The Contracting Officer may exercise the option by written notice to the Contractor within the term of the contract.

3.6 Report(s)/Deliverables and Performance Standards

The Contractor shall ensure that all of the deliverables listed below are included in their Performance Work Statement (PWS). The contractor may also include additional deliverables in the PWS.

The Contractor shall complete and submit all deliverables within the time specified in the below chart. The agency will not provide templates for any deliverable. The Peace Corps will review deliverables for quality, completeness and correctness in accordance with the applicable performance standards. The COR will notify the Contractor of any non-conformance or revisions needed before providing final acceptance of deliverables. The COR has the right to reject or require correction of any deficiencies found in the deliverables. Approval of the COR will come after the review and approval by Agency Stakeholders, including business Subject Matter Experts and Peace Corps IT staff. Once these reviews are completed, the COR will notify the Contractor of acceptance of the deliverables. In the event of rejection of the deliverables, the COR will notify the Contractor in writing as to the specific reason why the deliverables are being rejected. Reworks or edits shall be delivered to the COR within 5 business days of receiving feedback from COR.

Item No.
Deliverable
Description
Date Due
Performance Standard
1
Personnel Clearance Documentation Submitted
Personnel Clearance Documentation submitted to Peace Corps’ Office of Safety & Security (Only for individuals who require unescorted access to Peace Corps facilities, which includes buildings or network)
Within 3 business days following award of contract.
All documents are 100% complete with accurate information at time of submission within 3 business days following award of contract.
2
Entry Conference
Entry Conference held
Within 10 business days following award.
The COR will witness the scheduling of the Entry Conference and will participate in the meeting.
3
FISMA Compliance
The LMS application and hosting platform must be FedRAMP Compliant: JAB Provisional Authorization, Agency Authorization, and CSP Supplied Package. If the Contractor does not have FedRAMP Certification, the Contractor must have plans in place that will result in FedRAMP certification within three (3) months from the date of award.
3 months after contract
100% inspection by IT Security.
4
Contractor Project Management Plan (CPMP) to include the Service-level Agreement (SLA)
The Contractor shall develop and submit a final CPMP to include SLAs in accordance with (IAW) Section 2.4.3.1
To be submitted 10 days following the Entry Conference
Upon delivery, the COR or designated representative will provide feedback. Once the required changes have been satisfactorily made, the COR or designated representative shall provide approval and acceptance of the completed deliverable.
5
Weekly Progress Reports
An email with an update on the status of the work completed each week. The weekly progress report may become monthly or quarterly, at the discretion of the COR, once the LMS is implemented and fully operational for at least 3 months.
Weekly in accordance with an agreed-upon CPMP
The COR or a designated representative will confirm receipt within 2 business days of Contractor submission. Weekly Progress Reports may be eliminated after deployment, at the discretion of the COR.
6
Configuration Workshop
The Contractor shall conduct and facilitate a workshop IAW Section 2.4.3.
To be held within 10 days of the Entry Conference
The COR will witness the scheduling of the Configuration workshop and will participate in the meeting.
7
Configuration Workbook
The contractor shall provide this authoritative workbook IAW Section 2.4.3.
To be submitted 10 days following the Configuration Workshop
Upon delivery, the COR or designated representative will provide feedback. Once the required changes have been satisfactorily made, the COR or designated representative shall provide approval and acceptance of the completed deliverable. Reworks or edits shall be delivered to COR or designated representative within 5 business days of receiving feedback from COR.
8
Data Conversion and Migration Plan
The Contractor shall develop and submit a migration plan, which shall detail the Contractor’s approach (both technically and functionally) in migration efforts from Peace Corps Legacy LMS to the new solution(s). The migration plan shall include the approach to migrate both legacy information and content. See Section 2.4.2 and Attachment 3
To be submitted 10 days following the Configuration Workshop
9
Test Plan
The Contractor shall develop and submit a test plan IAW Section 2.4.3.
To be submitted at the beginning of the Test Phase as agreed to by the COR and outlined in the CPMP.
10
User Acceptance Testing
The Contractor shall provide the production environment for Peace Corps COR, System Administrator, and Course Managers for UAT.
To be completed in accordance with an agreed-upon CPMP.
10-15 courses migrated and 15% user profiles created (sufficient for UAT) to be considered ready for UAT. Shall be completed in accordance with the CPMP.
11
User Guides
The Contractor shall develop User Guides IAW Section 2.4.3.1.
To be completed 20 days prior to LMS Deployment
Upon delivery, the COR or designated representative will review and provide feedback. Once the required changes have been satisfactorily made, the COR or designated representative shall provide approval and acceptance of the completed deliverable. Reworks or edits shall be delivered to COR or designated representative within 5 business days of receiving feedback from COR.
12
Training Plan
The Contractor shall develop and submit a training plan, which shall outline the Contractor’s approach to initial user training and ongoing training and support IAW Section 2.4.3.1. The Contractor shall propose ongoing or periodic training for all roles, taking into account Peace Corps lifecycle of staff and Volunteers.
To be completed at least 20 days prior to LMS Deployment
13
Migration and Conversion of Legacy Data
The Contractor shall move all Legacy content and information from the current LMS to the Contractor’s LMS solution(s).
Migration of existing data to be completed 10 days prior to LMS Deployment
Upon completion of the migration efforts, the Contractor shall demonstrate that the migration was successful and complete.
14
Service Level Agreement (SLA)
The Contractor shall submit the final Service-level Agreement (SLA) which shall define uptime expectations (>=99.8%), escalation procedures that are acceptable to Peace Corps, and response times IAW Section 2.4.3.1.
To be completed 10 days prior to the LMS Deployment
Upon delivery, the COR or designated representative will review and provide feedback. Once the required changes have been satisfactorily made, the COR or designated representative shall provide approval and acceptance of the completed deliverable. Reworks or edits shall be delivered to COR or designated representative within 5 business days of receiving feedback from COR.
15
Operations and Maintenance Plan
The Contractor shall provide documentation detailing the ongoing operational support which shall define, but not be limited to: SLAs, maintenance windows, recurring work/development efforts, recurring maintenance schedules, tier 1/2/3 support options, and communications IAW Section 2.4.4.
To be completed 20 days prior to the LMS Deployment
16
End of Contract Transition Plan
The Contractor shall develop and facilitate a plan to ensure that all data developed and housed in the LMS during the course of the contract (to include but not limited to courseware, user information, tests and scores) shall be migrated to a newly awarded solution(s) at the termination of this period of performance.
To be completed 10 days prior to the LMS Deployment
17
LMS Deployment
The Contractor shall submit a letter to the COR to indicate complete Deployment and Support of the LMS Solution(s) for Peace Corps.
Within 10 days of LMS Deployment
Upon delivery of a letter from the Contractor to the COR, the COR or designated representative will review all aspects of the LMS and provide final approval. LMS Solution(s) for Peace Corps shall be live and accessible for all users. LMS Solution(s) shall have no critical flaws and under five (5) minor flaws with workarounds.

Notice to the Government of Delays

In the event the Contractor encounters difficulty in meeting performance requirements, or when the Contractor anticipates difficulty in complying with the contract delivery schedule or completion date, or whenever the Contractor has knowledge that any actual or potential situation is delaying or threatens to delay the timely performance of this contract, the Contractor shall immediately notify the Contracting Officer and the COR, in writing, giving pertinent details; provided, however, that this data shall be informational only in character and that this clause shall not be construed as a waiver by the Government of any delivery schedule or date, or any rights or remedies provided by law or under this contract.

3.7 Observance Of Federal Holidays

Deliverables due on a Saturday, Sunday, or the following Federal holidays shall be due on the Following business day.

1.New Year’s Day1 January
2.Martin Luther King’s Birthday3rd Monday in January
3.President’s Day3rd Monday in February
4.Memorial DayLast Monday in May
5.Independence Day4 July
6.Labor Day1st Monday in September
7.Columbus Day2nd Monday in October
8.Veteran’s Day11 November
9.Thanksgiving Day4th Thursday in November
10. Christmas Day25 December

SECTION 4 – CONTRACT ADMINISTRATION

4.1 Contract Management

4.1.1. Contracting Officer

Brendan Kittredge Acquisitions & Contract Management (ACM) 1111 20th Street NW Washington, DC. 20526 Email: bkittredge@peacecorps.gov Phone: 202-692- 2243

4.1.2. Contracting Officer’s Representative (COR)

(to be inserted at time of award) Office of the Chief Information Officer 1111 20th Street NW Washington, DC. 20526 Email: (to be inserted at time of award) Phone: (to be inserted at time of award)

4.1.3. Contractor Representative

The Contractor's Representative to be contacted for all contract administration matters:

Name: (to be inserted at time of award) Address:

Telephone:

E-mail:

4.2 – Inspection and Acceptance Criteria

4.2.1 Inspection and acceptance of services to be furnished hereunder shall be performed at place of performance or destination, by the COR or his/her designated representative, in accordance with FAR Clause 52.212-4, Contract Terms and Conditions – Commercial Items (December 2014). The Government reserves the right to conduct any inspection and tests it deems reasonably necessary to assure that the services provided conform in all respects to the contract specifications. Services which upon inspection are found not to be in conformance with contractual specifications shall be promptly rejected and notice of such rejection, together with appropriate instructions will be provided to the Contractor by the Contracting Officer.

4.2.2 Inspection will be completed within thirty (30) calendar days after completion.

a. In the event services are of a continuing nature and this contract prescribes periodic payments based upon increments of time rendered (e.g., hours or months of service), completion of services will be deemed to have occurred at the end of each whole or fractional month falling within the contract term.

b. In the event services are not of a continuing nature, such that this contract prescribes payment based upon fixed units delivered (e.g., characters keyed), completion will be deemed to have occurred upon delivery.

c. Payment will constitute notification of acceptance.

d. Written notification of negative inspection results will be furnished within 30 days after completion.

4.3 Invoice Requirements

a. The Contractor shall render invoices not more frequently than monthly, in an original only (i.e., one copy only) to the COR at the address listed in Section 4.1.2. To constitute a proper invoice, the following information and/or attached documentation shall be included with the invoice (as applicable) and submitted in electronic format to:

ATTN: OGAP

GAPdomesticinvoice@peacecorps.gov.

b. For questions regarding payments, please send an email inquiry, including the Peace Corps contract reference number (e.g. to be inserted at time of award), the invoice number, billed amount, due date, and date sent to Disbursing@peacecorps.gov.

c. The invoice shall include, but not be limited to, the following information:

· Name and address of the Contractor

· Invoice date and invoice number

· Period of performance covered by the invoice

· Description, price(s), date of service, and quantity(ies) of services and supplies for which payment is being requested

· Shipping and payment terms, if any

· EFT account/payment information

· Costs incurred under the current voucher or costs incurred to date (cumulative)

· Signature of the Contractor’s authorized representative

· Contractor’s Tax Identification Number (TIN)

4.4 Invoice Certification

Upon receipt of the invoices, the Peace Corps will check the invoices for correctness and appropriateness of the charges and will ensure that chargeable items appearing on the invoices have been formally accepted by the Peace Corps. In the event that the Peace Corps discovers any discrepancies in the invoice, the Peace Corps Contracting Officer and/or COR will, in addition to following the requirements of the Prompt Payment Act, take steps necessary to resolve the discrepancies with the Contractor.

4.5 Invoice Payment

For the purposes of this subsection, “invoice payment” is a Government disbursement of moneys to the Contractor under this ORDER for products and/or services, which are formally accepted by the Government. Invoices are payable in accordance with the requirements of the Prompt Payment Act. Payment will be considered as being made on the day of the electronic funds transfer is made.

The Government will pay the Contractor in arrears, the monthly fixed rate (i.e., unit price), at the applicable rate and for any approved incurred travel costs after Peace Corps acceptance of tasks and deliverables due and upon the Contractor’s submission of a proper invoice. Any approved travel shall be invoiced at cost only. The failure to properly submit invoices may result in a delay in payment.

4.6 Interpretations of Modifications

No oral or written statement of any person and no written statement of anyone other than the Contracting Officer shall modify or otherwise affect the terms and conditions of this contract. Requests for interpretations, modifications or changes must be made in writing to the Contracting Officer. The COR can only respond technical matters that do not result in a change of scope to this contract.

SECTION 5 – SPECIAL CONTRACT REQUIREMENTS

FAR 52.252-1 Solicitation Provisions Incorporated by Reference (Feb 1998) This solicitation incorporates one or more solicitation provisions by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. The offeror is cautioned that the listed provisions may include blocks that must be completed by the offeror and submitted with its quotation or offer. In lieu of submitting the full text of those provisions, the offeror may identify the provision by paragraph identifier and provide the appropriate information with its quotation or offer. Also, the full text of a solicitation provision may be accessed electronically at this/these address(es):

http://farsite.hill.af.mil FAR 52.252-2 Clauses Incorporated by Reference (Feb 1998) This contract incorporates one or more clauses by reference, with the same force and effect as if they were given in full text. Upon request, the Contracting Officer will make their full text available. Also, the full text of a clause may be accessed electronically at this/these address(es):

http://farsite.hill.af.mil

Clauses/Provisions Incorporated by Reference:

52.202-1
Definitions (Nov 2013)
52.203-3
Gratuities (Apr 1984)
52.203-6
Restrictions on Subcontractor Sales to the Government (Sep 2006)(Alt I)

52.203-11

Certification and Disclosure Regarding Payments to Influence Certain Federal Transactions (Sep 2007)

52.203-12
Limitation on Payments to Influence Certain Federal Transactions (Oct 2010)
52.203-13
Contractor Code of Business Ethics and Conduct (Oct 2015)
52.203-17
Contractor Employee Whistleblower Rights and Requirement To Inform Employees of Whistleblower Rights (Apr 2014)
52.204-4
Printed or Copied Double-Sided on Postconsumer Fiber Content Paper (May 2011)
52.204-5
Women-Owned Business (Other Than Small Business) (Oct 2014)
52.204-7
System for Award Management (Oct 2016)
52.204-9
Personal Identity Verification of Contractor Personnel (Jan 2011)
52.204-10
Reporting Executive Compensation and First-Tier Subcontract Awards (Oct 2016)
52.204-13
System for Award Management Maintenance (Oct 2016)
52.204-14
Service Contract Reporting Requirements (Oct 2016)
52.204-16
Commercial and Government Entity Code Reporting (Jul 2016)
52.204-17
Ownership or Control of Offeror (July 2016)
52.204-18
Commercial and Government Entity Code Maintenance (Jul 2016)
52.204-20

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated .