LMS_PWS_Posted_10112019.docx

DRAFT

Performance Work Statement Learning Management System

1.0 BACKGROUND

The Federal Judiciary (Judiciary) is the third branch of the United States Government and is comprised of appellate and trial courts located throughout the United States (US) and its territories (US Virgin Islands, Puerto Rico, Guam and Saipan/Northern Mariana Islands); it also includes the Judicial Panel on Multidistrict Litigation (JPML), and Federal Public Defender Organizations (FPDO). Several offices also support the Judiciary, such as the Administrative Office of the United States Courts (AOUSC), Federal Judicial Center (FJC) and US Sentencing Commission (USSC).

2.0 OBJECTIVE

Provide the Judiciary with a commercial user-friendly, flexible, configurable, and scalable learning management system (LMS) to include maintenance and support services.

3.0 LMS OUTCOME

a) LMS needs to be scalable for an unlimited number of users and educational assets.

b) LMS needs to consist of a production (live) and development (training) environment. The development database needs to be updatable to mirror the production environment on request.

c) LMS needs to integrate with Blackboard, Skillsoft, Human Resources Management Information System (HRMIS) and Judiciary Enterprise Network Information Exchange (JENIE); including existing Single Sign-On (SSO) integration with the AOUSC’s JENIE portal.

d) LMS services to be performed include updating AOUSC’s custom Skillsoft integration enough to create courses and Web-Based Training offerings and link these to the Skillsoft content modules.

e) LMS needs to allow data import via the User Interface, including individual person records, course transcript records, and course/offerings data, allowing administrators to do all in batch mode.

f) LMS needs to be available 24 hours a day 7 days a week, except for routine outages.

g) LMS needs the ability to provide individualized, configurable main page/interface per domain, with ability to add external links, graphics and colors to main page for each domain (portlets/widgets configurable at the domain admin level).

h) LMS needs to have robust reporting tools for all learning elements, with configuration capability for domain admins and supervisors.

i) LMS needs to have the ability to configure role creation and modification.

4.0 LMS REQUIREMENTS

a) Ability to create and update user records and course/offerings by a designated program and job from a secure File Transfer Protocol (FTP) site available on the internet.

b) Deactivate discontinued Skillsoft courses and related offerings.

c) Single Sign-On interface using a Security Assertion Markup Language (SAML)

d) Migrate the current LMS database a new solution incorporates the existing catalog of all available educational assets with course numbers, names and descriptions (content to be created and maintained by the AOUSC) with only active/available offerings displayed.

e) Structured process for updating of AOUSC’s custom Skillsoft integration.

f) Refresh the development environment to mirror the production environment upon update of production.

g) Experience Application Programming Interface (xAPI*) and Sharable Content Object Reference Model (SCORM) conformant.

h) Display time in regular (non-military) format.

i) Flexible privilege capabilities to allow for multiple administrator/domains, allowing each to manage and view only items in their domain. Supervisory level views of all records of assigned employee with the ability to enroll, approve/deny training registration requests and select manager related analytics (reports).

j) Course catalog view with multiple configuration options.

k) Facilitation support (onsite and/or virtual) as needed for implementation and ongoing training.

l) Ability for all admins to create, display, edit courses/offerings, curriculums, certifications, learning plans, programs for various user roles as well as organizational areas.

m) Ability to configure required fields based on related admin/user processes (e.g., course/offering creation and adhoc training record entry).

n) Flexible means for pushing training to learners based on user roles, organizations, mandatory schedules, etc.

o) Provide a student transcript.

p) Display domain calendar of offerings/training events (Per domain main page).

q) Full and remote administration by the AOUSC for all data.

r) Ability to create analytic reports at the domain admin level.

s) Up and Downloadable materials in all formats (Microsoft Office applications and PDFs at a minimum).

t) Ability to record external training credits and store related completion certificates.

u) Search function across all educational assets and catalog with display of actual offerings or usable assets only.

v) Admin ability to clone class offerings for multiplication locations, dates and times.

w) Ability to capture Instructor credits for course offerings and connect results to analytics.

x) Enrollment management (waitlist, etc.) with auto enroll when seat opens and administrative override (overbook).

y) Seat reservation for new hire (unnamed person).

z) Ability to customize notifications to learners/managers with registration confirmations, reminders, course completions and other announcements (e.g., emails for manager approval or offering reminders) at the domain level.

aa) Ability to associate resource assignments and locations (instructors, classrooms, etc.) for Instructor Led Training course delivery.

ab) Customizable certificates/awards.

ac) Mobile accessibility.

ad) "What's New" Feed for communicate with domain admins.

ae) Permission based help function with ability to offer usage hints or create help.

af) Ability for admins to proxy (act as another user) for troubleshooting.

5.0 LMS REPORTS

Robust reporting tools for all learning elements, with customization capability for domain admins and managers as well as canned reports including:

· Course completion/in progress/enrolled system-wide

· Class rosters

· Assessment scores

· Certification

· Individual learner progress

· Evaluations and course ratings

· Instructor and Learner credit

· External (adhoc) training

· User activity data/Audit (actions taken, time on the system, pages/areas visited, etc.)

6.0 LMS AVAILABILITY

The LMS shall be available 24 hours a day 7 days a week except for routine outages (i.e., time required for patches, firmware updates, viruses/malware and bug fixes). The contractor shall provide U.S. based customer support accessible via toll-free phone number, email and website. The contractor shall provide timely notification of bugs, updates, and revisions for all products covered under this requirement. Electronic notification and distribution are preferred.

a) Non-emergency Updates Scheduled routine maintenance which includes patches and updates, minor bug fixes, refreshes (development environment) and system upgrades.

All non-emergency updates shall occur over the weekends between 11:59 pm Friday to 2 pm Sunday EST and shall be coordinated with the Contracting Officer’s Representative (COR) via email five (5) business days prior to initiation.

b) Emergency Updates Any non-scheduled maintenance which includes patches and updates, viruses, malware, major bug fixes and system upgrades.

All emergency updates shall be brought to the COR’s attention via phone with a follow-up email within fifteen (15) minutes after discovery. Within sixty (60) minutes of notification, the contractor shall provide a written plan/solution that explains and resolves the emergency to the COR, via email.

If an emergency occurs, the system shall not be down no longer than four (4) hours. Any longer than four (4) hours requires COR approval.

c) Redundancy The LMS shall have system redundancy, backup and failover capabilities. The contractor shall periodically test backup to ensure the backup is working properly.

7.0 LMS SUPPORT

a) System Maintenance: indexing of catalog, chronology jobs and logs, notification, single Sign On with JENIE, and server login.

b) Provide ongoing technical support services including troubleshooting, response(s) and resolutions, testing and documentation.

c) Create and document the testing data scripts and integrations in development and production environments.

d) Document best practices for system processes.

e) Advise system admins on user interface configuration (i.e., themes, desktop layout and logo) and maintenance of business rules (i.e., enable and disable functionalities per the Judiciary’s needs).

f) Direct technical support for basic and customized LMS functionality.

8.0 LMS SECURITY

a) Security Compliance and Privacy Data Protection The contractor shall protect all sensitive and personal data as outlined in Clause 7-35, Disclosure or Use of Information and 2-140, Judiciary IT Security Standards.

The contractor shall follow and remain compliant with the Federal Risk and Authorization Management Program (FedRAMP) authorization or at a minimum the Judiciary Information Security Framework (JISF) requirements based on the security categorization of the system.

The contractor shall engage with the IT Security Officer (ISO), Information System Security Officer (ISSO), and other designated security personnel to ensure all security and privacy requirements are met.

b) Security and Privacy Documentation The contractor shall ensure all security and privacy documentation is delivered to the IT Security Officer (ISO), Information System Security Officer (ISSO), and other designated recipients. Documentation includes, but not limited to:

· System Boundary Definition (SBD)

· System Categorization/System Security Level

· System Security Plan (SSP)

· Privacy Threshold Analysis (PTA)/Privacy Impact Analysis (PIA)

· Memorandum of Understanding (MOU)

· Interconnection Security Agreements (ISA)

· Contingency Plan

· Continuous Monitoring Plan

· Configuration Management Plan

· Incident Response Plan

· Corrective Action Plan (CAP)/Plan of Action and Milestones (POAM)

9.0 TRANSITION

The contractor shall provide phase-in transition from two separate support contractors to the new LMS. Phase-in transition shall be completed by June 30, 2020. The transition includes but is not limited to:

· Creation of transition plan that demonstrates how the contractor will successfully transition from two contractors to one by the June 30, 2020 deadline.

· Create, conduct and document onsite training for Admins

· Develop interface to load user records REST API (Representational state transfer Application Programming Interface) from JENIE The contractor shall provide phase-out transition from this contract to the recompete. Submit a phase-out plan which details how the contractor will successfully transition to the new contractor if not the incumbent. The transition includes but is not limited to:

· Export of AOUSC content packages to be retained on media and delivered to AOUSC upon request.

10.0 LMS DELIVERABLES

a) Bi-weekly status report due to COR by close of business (COB) the 2nd and 4th Tuesday of each month via email.

b) Emergency status report due to the COR by COB of the next business day.

c) Emergency Update due to COR within sixty (60) minutes of initial notification.

d) Final transition plan two business days after award.

e) Provide documentation (i.e., job aids, user guides, videos, etc.) for admin and basic use.

f) Ability to export finalized configurations from the development environment to the production environment plus document the process.

g) Documentation of system changes and related functionality to be provided after bugs fixes, updates, etc. to be provided within 5 days after completion.

h) Security and Privacy Documentation to be provided 60 days after official award. These documents must be live (always available) and kept current. :

a. System Boundary Definition (SBD)

b. System Categorization/System Security Level

c. System Security Plan (SSP)

d. Privacy Threshold Analysis (PTA)/Privacy Impact Analysis (PIA)

e. Memorandum of Understanding (MOU)

f. Interconnection Security Agreements (ISA)

g. Contingency Plan

h. Continuous Monitoring Plan

i. Configuration Management Plan

j. Incident Response Plan

k. Corrective Action Plan (CAP)/Plan of Action and Milestones (POAM)

11.0 PERIOD OF PERFORMANCE

Phase-in transition is four (4) months from date of award and live performance starts August 1, 2020 thru July 31, 2021 and the potential for four (4) options on the anniversary.

12.0 PLACE OF PERFORMANCE

Contractors facility. Contractor will be required to attend meetings at the Administrative Office of US Courts.