Attachment 1 - Statement of Work.pdf

FEDERAL MEDIATION AND CONCILIATION SERVICE

STATEMENT OF WORK

for

LEARNING MANAGEMENT SYSTEM

1.0 INTRODUCTION

Created in 1947, the Federal Mediation and Conciliation Service (FMCS) is an independent agency whose mission is to preserve and promote labor-management peace and cooperation. The agency provides mediation and conflict resolution services to industry, government agencies and communities. Headquartered in Washington, DC, the FMCS has mediators located throughout the country including providing mediation services in Hawaii and Alaska. For specific information on the FMCS, refer to the FMCS website at www.FMCS.gov.

FMCS’s mission statement reflects the statutory intent of the Agency. The mission of the FMCS is to promote the development of sound and stable labor management relationships, prevent or minimize work stoppages by assisting labor and management to settle their disputes through mediation, advocate collective bargaining, mediation and voluntary arbitration as the preferred processes for settling issues between employers and representatives of employees, develop and advocate the art, science and practice of conflict resolution through the use of ADR, assist parties in conflict through the provision of conflict resolution services, and foster the establishment and maintenance of constructive joint processes to improve labor-management relationships, employment security and organizational effectiveness.

2.0 BACKGROUND

In 2015, the Education and Training (E&T) Department initiated a contract with a vendor to host an online training system that would register employees, develop, deliver, monitor, and create reports. This system was an interactive multimedia and internet-/intranet-based training environment for an employee population of about 250. The Office of Human Resources (OHR) manages the current learning management system, which posts training courses via a training calendar.

The current system is very labor intensive and requires more man-hours with limited accessibility options for the user, instructors and OHR subject matter experts. There is a need to streamline processes and own a single system that manages all process steps from the submission of the initial SF-182 Training Request by the student to automated evaluation data gathering of the training impact and benefits to reporting of all training completions and eHRI data as required by the Office of Personnel Management (OPM). A technological solution is needed to help reduce the cost of training, travel, and loss of staff production time by providing a solution that can be accessed 24 hours per day from any device. The OHR is required to collect, maintain, and track detailed records of all training and development activities associated with FMCS staff.

This information is used to:

• Plan and evaluate training to support the FMCS’s mission.

• Manage the administrative and logistic processes of training programs.

• Assess and document the learning, competency levels and skills of employees.

http://www.fmcs.gov/

• Comply with OPM regulations that govern how FMCS reports training data (e.g., eHRI data).

• Respond to inquiries from FMCS HQ and field offices, and external sources related to budgetary impact of training resources and utility of topics.

3.0 OBJECTIVE, BUSINESS CASE, AND ACQUISITION STRATEGY

FMCS needs a Commercial Off-the-Shelf (COTS) Learning Management System (LMS) that provides employees with the most up-to-date Operations-related, IT, and Federal Compliance online courses available via an FMCS-branded website and LMS that is available via any internet accessible equipment, 24 hours per day. A LMS that meets the FMCS’s usability criteria, that is cloud-based, vendor hosted and integrated with the Office of Personnel Management’s eHRI is imperative. The FedRAMP requirements and requisite security features to protect employees’ Personally Identifiable Information (PII) is a key aspect of any tool considered as part of this acquisition and necessary to take the FMCS and its learning and training capacity to the next level. The purpose of this document is to communicate the requirements outlined in the tables in Section 4.0. The vendor must also ensure that the LMS provides effective and responsive customer service to the administrators, trainers and OHR subject matter experts. The Review Team Criteria (RTC) for the LMS will need to contain comprehensive information regarding each vendor’s products as they relate to:

• Functionality and federal government regulatory mandates

• Unique features and usability

• Instructor curricula support

• Student accessibility on multiple devices

• Customer service support and training of Administrators

• Government contracting vehicles if any

• List of government clients if any

4.0 FMCS REQUIREMENTS and COLLABORATION

The OHR consulted with the Office of Information Technology (OIT), as well as stakeholders, managers, and administrators/subject matter experts (SMEs), who all contributed to the creation of the critical LMS feature capabilities to inform the context of this document. This collaboration and data collection required the LMS “must haves” of being cloud-based, FedRamp, 508 and SCORM compliant to include the following mandates:

• Federal Risk and Authorization Management Program (FedRAMP) authorization at a Moderate impact level based upon the FIPS 199 classification.

• Provisional authorization at a Moderate impact level based upon the FIPS 199 classification or compliance with NIST 800.53 Rev.4.

• Users must be able to access the LMS and complete coursework 24 hours a day, seven days a week through a variety of computer systems and devices, which can be accessed via the internet.

The FMCS COTS LMS requirements are featured below and include the level of their importance as shown below:

o Critical (C) o Important but not critical (I) o Nice to have (N)

The FMCS has requirements for the following topic areas:

• Technical Requirements

• Instructor Needs

• Student Accessibility

• Competency and Skills Tracking

• Overall System Needs

TABLE 1 TECHNICAL REQUIREMENTS

NO. DESCRIPTION IMPORTANCE

TR1 The solution must operate in compliance with OMB M-15-13 and CISA Binding Operational Directive 18-01.

C

TR2 SMTP Email, messaging and notification system must operate in compliance with CISA Binding Operational Directive (BOD) 18-01 and be compatible with Azure based MS Exchange SMTP mail format.

C

TR3 Must meet Federal Risk and Authorization Management Program (FedRAMP) authorization at a Moderate impact level or compliance with NIST 800.53 Rev 4

C

TR4 System must be in compliance with 36 CFR Chapter XII Subpart B – Records Management Parts 1220, 1222, 1224, 1227 and 1236.26 and General Record Schedule 2.6.

C

TR5 LMS must be ADA Section 508 compliant C

TR6 Service Level Agreement (SLA) must include time windows for maintenance, as well as uptime guarantees. It also must clearly state all support agreements.

C

TR7 Version of software along with release date and change log (document which specifies what has changed/been added/otherwise modified from the previous release) is provided with each release of software patches, updates, and new version releases.

I

TR8 Solution must be securely hosted and compatible with the Microsoft 365 cloud environment to allow integration into other FMCS systems and ease of authentication.

I

TR9 Must integrate/communicate with OPM's Enterprise Human Resources Integration (EHRI) system

C

TR10 Creates/delivers SCORM (or other recognized standard) compliant courses I

TR11 The solution must use current technologies, compatible with the latest browsers, supporting Microsoft Edge, Google Chrome, Apple Safari and Mozilla Firefox at the very least

C

TR12 Any Personally Identifiable Information (PII) must be protected against unauthorized access, disclosure or modification, theft, or destruction

C

TR13 The LMS software will support import and export to/from commonly available software C https://https.cio.gov/ https://cyber.dhs.gov/bod/18-01/ https://cyber.dhs.gov/bod/18-01/ https://cyber.dhs.gov/directives/ https://cyber.dhs.gov/directives/

TABLE 2 INSTRUCTOR NEEDS

I1 Training on the use of the LMS including end user training and administrator training C

I2 Report data can be pulled from other systems (i.e., FMCS systems, eHRI) C

I3 Tracks student attendance C

I4 Training plans can be designated for individuals or groups N

I5 Manages class roster C

I6 Records attendance at outside seminars C

I7 Sets up new classes using templates C

I8 Manages registration cut-off time C

I9 Allows setting of course prerequisites N

I10 Sets class enrollment limits I

I11 Accesses reports on how many sessions necessary for a student to complete a course and the length of each session

N

I12 Compatible with courseware developed in third-party authoring systems C

I13 Schedules training class C formats? PDF, DOCX, PPTX, XSLX, CSV, …, and others. In addition, it must support the migration of all current trainings.

TR14 Allows agency-specific branding on site I

TR15 Automatic emailing to students, managers, administrators and/or instructors/SMEs C

TR16 FMCS must retain unrestricted rights to government data C

TR17 Allows for the creation of metadata that will allow system information to be searchable on FMCS Intranet portal

N

TR18 Allows students to initiate both internal and external training requests with mandatory supervisory reviews and approvals. Data from training requests must import into OMB Standard From (SF) 182.

C

TR19 External training request process recognizes FMCS internal codes, including but not limited to, cost, accounting, and training codes

C

TR20 Automatically tracks trainings; allows for manual input of training information C

TR21 Must be able to generate/maintain Individual Training Plans (ITP) I

TR22 Reports are generated in a character-delineated format (CSV) for easy analysis I

TR23 Training in the use of the LMS including end user and administrator training C

TR24 Vendor must present any system data on request for audit and reporting purposes I

TR25 Integrates with external webinar platforms such as RingCentral and Adobe Connect N

TR26 Training/manual provided to FMCS administrators prior to release of new courseware or major system change

I

I14 Maintains a list of instructors qualified to teach courses N

I15 Sets class location N

I16 Generates "To-Do" list, for planning what needs to happen before and after a class N

I17 Courses can be scheduled on non-contiguous days I

I18 Tracks setup requirements for classroom-based training classes I

I19 Tracks qualified instructors I

I20 Grading criteria can be adjusted N

I21 Questions can be randomized from a pool of questions N

I22 Assigns instructor to classroom N

I23 Questions can be grouped into test pools and reused I

I24 Captures who has completed mandatory training and who has not C

I25 Tracks by course, student, department, and organization C

I26 Instructors can review the students registered for a course and their test statistics N

I27 Tracks assignment and attendance for each participant C

I28 Accesses and analyzes student and group training histories I

I29 Database allows users to define the variables they want to track C

I30 Students who drop a course can be assigned a status (no show, cancelled, etc.) C

I31 Allows for course waitlists N

TABLE 3 STUDENT ACCESSIBILITY

S1 Online self-registration C

S2 Catalog allows users to search for training by keyword, category, or course ID C

S3 Online course catalog with title, description, course objectives, prerequisites, required materials, and credit hours

C

S4 Student can print their progress and training history C

S5 Tracks student training history C

S6 Manages student training plans I

S7 Self-registry requires supervisor approval C

S8 Student can access their own training records C

S9 Student can review progress summaries for each course they have completed or accessed

I

S10 Shows student which courses to take to further their career goals N

S11 Student can edit their own personal information or ITP N

S12 Obtain weekly or monthly student activity schedules N

S13 Student enrollment uses click-and-drag interface N

S14 Tabbed file folder display for viewing classes N

S15 Bookmarks course/module/lesson/page and return later I

S16 Allows printing of teaching materials for classroom-based training I

S17 Student can "test-out" of courses to avoid spending time on topics already mastered N

S18 Ability to link to reference material including outside resources, white papers, threaded discussions with search features, etc.

N

S19 Automatic remedial training based on end of course test results N

TABLE 4 COMPETENCY AND SKILLS TRACKING

C1 Ability to link competencies with tests N

C2 Tracks and compares competencies before and after training events N

C3 Ability to link competencies with courses N

C4 Maps competencies to objectives and test items N

C5 Skills and competency tracking, including non-course-related information N

C6 Competencies can be weighted within roles N

C7 Pre- and post-course assessments N

C8 Ability to include synchronous forms of learning (i.e., GoTo Meeting, Web Meeting, etc.) N

C9 Skills-gap analysis I

C10 Maps competencies to objectives and test items N

C11 Career development - self-evaluation of skills gaps N

C12 Competency Modeling N

C13 Curriculum path can include information for students on the next job role they want to pursue

N

C14 Conduct skills gap analyses N

C15 Manage employee’s training plans C

TABLE 5 OVERALL SYSTEM NEEDS

O1 Automatic Reminder Notifications to students and supervisors of mandatory annual training

C

O2 Certificate of Completions can be attached to student's records C

O3 Track employee information, including positions, job history, reviews, skills, education, etc.

N

O4 Course and survey statistics are available for review N

O5 Report templates – details in technical requirements C

O6 Tracking of all students' progress N

O7 Organize data with user-defined filters I

O8 Course completion status C

O9 Courses can be designated as "downloadable" for remote or mobile learner access C

O10 Built-in authoring system I

O11 Administrators/SMEs can create new online tests or modify existing tests and questions I

O12 Allows use of third-party online courses I

O13 Test and survey creation interface I

O14 Glossary of terms I

O15 Create confirmation letters, name badges, and evaluation forms N

O16 Conflict checking of scheduled resources N

O17 Standard media objects can be shared among courses N

O18 Multiple sessions of the same course can be scheduled for the same day I

O19 Audio, video, graphics, animation, and text objects are centrally stored and can be reused

C

O20 Auto-update of class status (available, canceled, etc.) C

O21 Compatible with new authoring tools out on the market C

O22 Calendars show resource use and schedules C

O23 Customizable toolbars I

O24 Tree view for navigation N

O25 Contains a Frequently Asked Questions section I

O26 Feature for talent management I

5.0 SCOPE OF WORK

The FMCS requires a means to track registration, develop, deliver, monitor, report on and evaluate online training courses in an interactive multimedia training environment for over 2000 users of its overall employee population in its Headquarters and Field offices nationwide. The scope of the work is as follows:

5.1 IMPLEMENT FMCS-BRANDED, VENDOR-HOSTED ONLINE LMS

The Contractor must provide and host a dedicated LMS website, branded for FMCS, that can be customized by the owner, serve as the online portal through which FMCS employees will log-in, review and access courseware, register, complete training, bookmark locations, document course completion, and receive course completion certificates and evaluations. This LMS will further facilitate instructor/course utility by creating accessibility to report formats that can be delineated from the organizational, team and individual levels regarding progress, assignments, group learning plans and individual training plans (ITPs).

The infrastructure for this site will include a customized and unique FMCS header, administrative and public URLs, as well as database meta-sites. It is required that FMCS Administrators have access to the administrative sites and can create and edit learning groups, designate administrators on multiple levels, assign permissions, create and edit reports, as well as modify individual and group learning and development plans.

5.2 COMMERCIAL OFF THE SHELF (COTS) PRODUCT SOLUTIONS

The FMCS requests a Commercial off the Shelf (COTS) solutions that meet the requirements outlined in Section 4.0 in this document. Limited use of a programmer to create a tailored system is preferred.

5.3 SYSTEM REQUIREMENTS

The system requirements as described in Section 4.0 lay out the detailed and prescriptive needs for the FMCS LMS. Of significant importance is the ability of the system to track each student’s online, mobile, and instructor-led class participation to include competency assessment capacity through surveys and assessments.

The end-user page should have the capability to be managed and modified using a web editor.

As noted in the requirements, training trackers, standard and customizable reports by office and or program topic areas are mandated. Of significant import is the ability of the LMS to have the capacity to customize automatic notifications for various user groups based on selected requirements. These notices must be able to be distributed by email, text (SMS), within the LMS, or via the user’s calendar (for instructor-led trainings).

New course content will need to automatically update as these courses are added, with messaging sent to students who have indicated an interest. The financial management capability of the LMS must allow for the completion of the SF-182 Training Request form, budget allocation codes and declination of submission, if not approved by the supervisor.

5.4 SYSTEM ACCESSIBILITY

The FMCS considers universal accessibility to information a priority for all its employees and external customers, including individuals with disabilities. Under Section 504 and 508 of the Rehabilitation Act of 1973 (29 U.S.C. sections 794 and 794d, as amended), FMCS must ensure the accessibility of its programs and activities, specifically its obligation to acquire and use accessible electronic and information technology. To comply with the provisions of this clause, the Contractor shall refer to the Section 508 Standards described at www.section508.gov and must ensure its LMS contains this accessibility.

5.5 CONFIDENTIALITY, PRIVACY AND NON-DISCLOSURE

All data and other information supplied to the Contractor and all communications between the contractor and FMCS personnel are confidential and will not be disclosed by the Contractor to any source. Failure to meet this requirement will result in prosecution under 42 U.S.C. 2000e-8(e) and/or prosecution under 42 U.S.C. 2000e- 5(b).

FMCS's information systems contain personal information subject to the Privacy Act of 1974 (PL 93-579) and amendments. It will be the Contractor's responsibility to familiarize and brief employees and subcontractors on the provisions of the Privacy Act.

FAR clauses, 52.224-1: "Privacy Act Notification" and 52.223-2: "Privacy Act", are hereby incorporated by reference.

5.6 SECURITY

a. FMCS's information systems (including those systems or portions of systems supported or maintained by contractors) are Federal Information Systems, as defined in the Federal Information Security Management Act of 2002, and are required by this statute to be provided information security protections commensurate with the risk and magnitude of the harm resulting from unauthorized access, use, disclosure, disruption, modification, or destruction of information collected or maintained by or on behalf of the agency; and information systems used or operated by an agency or by a contractor of an agency or other organization on behalf of an agency. The Contractor shall agree to employ all appropriate safeguards to ensure compliance with this requirement.

b. All applications and systems must comply with the NIST 800.53 controls for a federal system with a FIPS

199 ranking of “Moderate.” This includes security monitoring, compliance with baseline security benchmarks, provision for continuity of operations and disaster recovery, monthly vulnerability scanning and related mitigation, and annual penetration testing. Any non-compliance with NIST 800.53 controls must be reported to the government for risk review and consideration of risk acceptance.

c. The Contractor shall provide an infrastructure that supports the FMCS’s compliance with Government standards and requirements (e.g. Clinger-Cohen, Section 508, Federal Information Security Management Act, etc.) as well as appropriate inventory, configuration management, security, quality control, architecture standards, and reporting requirements.

d. The Contractor must comply with GSA FedRAMP information technology systems security requirements at the FIPS 199 “moderate” level The FedRAMP baselines controls are based on NIST SP 800-53, Recommended Security Controls for Federal Information Systems and includes a set of additional controls for use within systems providing cloud services to the federal government. The contractor shall maintain a security management continuous monitoring environment that meets or exceeds the latest edition of FedRAMP Cloud Computing Security Requirements Baseline and FedRAMP Continuous Monitoring Requirements. For more information, see the GSA FedRamp website:

http://www.gsa.gov/portal/category/102371 under the key documents section. FedRamp Security Controls documents are located at:

http://www.gsa.gov/graphics/staffoffices/FedRAMP_Security_Controls_072912.zip. FedRamp Continuous Monitoring Requirements are located at:

http://www.gsa.gov/graphics/staffoffices/Continuous_Monitoring_Strategy_Guide_072712.pdf. Any deviation from the FedRAMP requirements must be outlined in your proposal along with rationale for the non-compliance, for review and consideration of risk acceptance by FMCS.

e. If the system provides public access or a web-service, the system must provide service over HTTPS;

automatically redirect HTTP requests to HTTPS, or disable HTTP entirely; AND have an HSTS policy in place with a max-age of at least 1 year. Web services used by non-browser clients (e.g. APIs) must still individually enforce HTTPS, as HSTS is not supported by non-browser clients.

http://www.gsa.gov/portal/category/102371 http://www.gsa.gov/portal/category/102371 http://www.gsa.gov/graphics/staffoffices/FedRAMP_Security_Controls_072912.zip.

http://www.gsa.gov/graphics/staffoffices/Continuous_Monitoring_Strategy_Guide_072712.pdf.

f. The Contractor shall be responsible for properly protecting all information used, gathered, or developed under this contract. The Contractor shall also protect all Government data, equipment, etc. by treating the information as sensitive. All information about the systems gathered or created under this contract should be considered as Sensitive. It is anticipated that this information will be gathered, created, and stored within the primary work location. If Contractor personnel must remove any information from the primary work area, they should protect it to the same extent they would their proprietary data and/or company trade secrets. The use of any information that is subject to the Privacy Act will be utilized in full accordance with all rules of conduct as applicable to Privacy Act Information.

g. The government will retain unrestricted rights to government data. The ordering activity retains ownership of any user created/loaded data and applications hosted on vendor’s infrastructure, as well as maintains the right to request full copies of these at any time.

h. The data that is processed and stored by the various applications within the hosted infrastructure contains personally identifiable information (PII). This PII shall be protected against unauthorized access, disclosure or modification, theft, or destruction. PII data that is maintained on external media must be encrypted in a method compliant with FIPS 140-2. The Contractor shall ensure that the facilities that house the network infrastructure are physically secure. Any potential breaches or data compromise will be immediately reported by the Contractor to the Government Contracting Officer Representative (COR) and Chief Information Security Officer (CISO) at ecso@FMCS.gov.

i. Government data will be retained by the Contractor only for the duration of this contract. At the conclusion of this contract, or upon direction of the Government COR (whichever comes first), all government data, including data extrapolated or added, will be permanently sanitized from Contractor systems, following the standards outlined in NIST SP 800-88, Guidelines for Media Sanitization. Any external media (including hardcopy) containing government data will also be destroyed. Destruction of data will be coordinated with the Government COR and completion will be confirmed with both the Government COR and the Chief Information Security Officer.

j. Documentation/Reporting: The FMCS requires the Contractor to provide documentation related to configuration management, security, and hosting facility policies and standards. Unless otherwise specified, the documentation shall be updated annually, at a minimum, to include the status and to reflect any changes.

5.7 SYSTEM CAPABILITIES

The selected LMS must be capable of delivering Aviation Industry Computer-based Training Committee (AICC) and Sharable Content Object Reference Model (SCORM) compliant eLearning to enhance the integration of current FMCS COTS courseware, tracking student progress and monitoring training and competency connectivity of selected training.

5.8 SYSTEM REPORTING

The LMS must have built-in reporting capabilities. For example, predefined reports that enable FMCS instructors and supervisors to generate course-specific weekly, monthly, or quarterly reports that are user-specific and mailto:ecso@FMCS.gov.

provide student transcripts and grades, as applicable.

5.9 SYSTEM ADMINISTRATOR

The FMCS administrators of this system require that management of the LMS be accessible via a cloud- based platform which enables the administrator to manage multiple learning tools for specific training initiatives by office and/or location. The administrator should be able to create curricula, set up user profiles, manage, document, track, and report information for classes, individual learners, and groups by office location.

Within permissions set by a super administrator, local administrators shall enable managers/supervisors to document, track, and report on classes, individual learners, and groups of learners assigned to each manager role by the administrator. Levels of administrator access will be determined by the OHR. An administrator should be able to:

• Configure all system options

• Establish user-defined fields

• Add, delete, modify, and import all course information

• Create subordinate administrators with access to specific and assignable components and/or learning groups, and assign/remove permissions as desired

• Create learner/user groups based on common fields

• Create or import groups and group managers

• Specify course re-certification requirements and notification period(s)

• Customize security options: intruder detection, password expiration

• Manage transaction logging

• Use full reporting capabilities relative to his/her authorized learning/user group

• Modify user-definable fields

• Track course costs

• Participate as learners without having to encumber an additional license

• Structure learners into specific groups or hierarchies based on content assignment and reporting needs

• Determine and adjust what information learners’ managers/supervisors will be able to access and/or edit

• Manage assigned courses, individual learners, and groups of learners

• View and print learner reports

• Monitor learner progress

• Mark course completions

• Electronically sign appropriate training documents

• Modify learner information

• Assign courses and curricula to learners

• Designate courses as required or as elective

• Track course usage

5.10 ADMINISTRATOR TRACKING, MONITORING AND REPORTING

Administrator tracking, monitoring, and reporting of individual and group usage and activity on the system will include:

• Reports by FMCS position, grade, location, series, component, role/group designations

• Reports by specific courses completed for FMCS employees and/or groups

• Report by specific learning programs or individual development plans assigned to employees

• Mandatory training, which needs to show completion during multiple timeframes by an employee

• User access to the system

• Courses accessed

• Time online (in seat)

• Access dates and times

• Progress toward course or learning program completion

5.11 ADMINSTRATOR LEVELS

Level 1 – Chief Administrative rights over entire system within FMCS’s platform including creation of sub-administrators and assignment of permissions, administrative rights, and areas of responsibilities to all other administrative levels. Level 1 Administrator has ability to monitor, review, modify or delete actions performed by any other FMCS administrator at any level (e.g. Chief Administrator).

Level 2 – Same administrative rights as Level 1 except ability to create other Level 2 administrators. Level 2 administrator cannot modify actions of other Level 2 administrators unless assigned such permission by the Level 1 Administrator (e.g. Deputy Chief Administrator).

Level 3 – As assigned by upper level Administrators, ability to manage assigned courses, individual learners, and groups of learners, including:

• View and print learner reports

• Monitor learner progress

• Mark course completions

• Electronically sign appropriate training documents

• Modify learner information

• Assign courses and curricula to learners

• Designate courses as required or as elective

• Track course usage

5.12 COURSEWORK AND E-LEARNING COMPETENCY MAPPING

The Contractor shall provide unlimited access to interactive instruction and assessment on a wide range of relevant information technology, computer desktop skills, business skills, career pathways and compliance subjects. The Program shall include current and future releases of the following:

• Courseware

• Desktop Skills

• IT Skills

• Business Skills

• Federal Employee-Focused Legal Compliance

• Employee Engagement and Career Pathways

To meet the specific needs of the FMCS and the Federal workforce in general, courseware in the following required Federal compliance subject areas must be current and validated by recognized subject matter expertise.

• The No Fear Act

• Accessibility and Section 508 Awareness

• IT Security / Privacy Awareness

• Sexual Harassment Prevention for Federal Employees

• Workplace Safety

• Federal Budgeting Process

• Government Ethics

• Proper Use of Government Charge Cards

• HR Flexibilities

• Harassment in the Federal Workplace

• Performance Management Training for Employees

• Controlled Unclassified Information (CUI)

5.13 COMPETENCY MAPPING

The LMS must have the capacity to create course maps by linking courses to identified competencies. The Contractor shall provide and maintain competency mappings between their courseware and critical government competencies, knowledge, and skill requirements, including:

• OPM Executive Core Qualifications (ECQs)

• OPM Human Resource Competencies

• FMCS Mission Critical Occupations Competencies (MCOs)

• OPM Career Pathways Competencies

• New OMB Program/Project Management Certification

• OPM Acquisition Competencies (1102 job series)

• Clinger-Cohen CIO Core Competencies

• NIST 800-16 Information Security training requirements

• Information Technology Professional (IT 2210) Competencies and Job Series Requirements

6.0 PERIOD OF PERFORMANCE

The Period of Performance (POP) will consist of a 12-month base period, plus four (4) 12-month option periods.

7.0 KICK-OFF MEETING

Within five (5) business days of award, the Contractor will attend a meeting with the FMCS during which the parties will review the task order vehicle and the expectations of both parties. The Contractor will take minutes of that kick-off meeting and any subsequent follow-up clarification and contract update meetings and provide a copy of those minutes to the FMCS COR for review and concurrence.

8.0 TRANSITION PLAN

The Contractor shall be responsible for ensuring the orderly transfer of all associated business processes. All relevant data as subsequently negotiated by the FMCS and the current contract vendor shall include the critical elements of the LMS platform and must be received from the current contractor vendor and provided to the Government or to another contract vendor, as agreed upon during the final months of the task order. Turnover includes all necessary actions to transfer the business process, data, and system from one entity to another with appropriate data validation and training activities.

Offerors shall submit with their quote a Draft Transition Plan to demonstrate how to successfully transfer all associated data and businesses processes from the FMCS’s current solution to the proposed solution.

This plan will be updated and finalized prior to the point of turnover of the awarded solution. During the transition period, the Contractor shall be responsible for resolving production support issues and knowledge transfer. The Contractor shall provide documentation on the specific roles and responsibilities of the transition team that will be delivered to the COR as a work product. The Contractor shall be responsible for all information as specified in the approved Final Transition Plan.

9.0 DELIVERABLES

All dates as indicated on this table are in workdays.

DELIVERABLE Due Date

Accepted copy of Contractor’s Minutes of the Kickoff Meeting. 5 days after the meeting in 7.0

Hosting for the branded website, LMS and administer active portals. Implement Version 1 of FMCS-Branded Contractor-Hosted Online Registration/Training Portal complete.

15 days after Date of Award (DoA)

Contractor vendor administrative support and LMS platform review of contract vendor’s learning content and learner-related materials with the OHR.

20 days after DoA

Online platform review of FMCS’s learning content and learner- related materials by the OHR.

25 days after the DoA

FMCS OHR and End-User volunteers/administrators can perform student, supervisor, and administrative functions as a test of the LMS capabilities

30 days after the DoA

Access to Contractor’s Business Skills/Federal Legal Compliance courseware and learning content, for at least 250 FMCS employees.

Beginning 30 days after DoA and thereafter, no more

Access to Contractor’s Information Technology Skills courseware and learning content, for at least 50 FMCS employees.

than 24 hours after FMCS provides User information to Contractor

Access to Contractor’s Federal Compliance Courseware and learning content for additional 200 FMCS employees not included

No more than 24 hours after FMCS provides User information to Contractor

Implementation assistance and technical and administrative training to FMCS primary administrators and 30 designated subordinate administrators nationwide.

Upon Award and no more than 72 hours after FMCS provides Administrators’ designation and information to Contractor

Final Transition Plan Within 90 days of task order expiration