VA ELMS_36C10B23R0017 0001.docx

5. PROJECT NUMBER (if applicable)

CODE

7. ADMINISTERED BY

2. AMENDMENT/MODIFICATION NUMBER

CODE

6. ISSUED BY

8. NAME AND ADDRESS OF CONTRACTOR

4. REQUISITION/PURCHASE REQ. NUMBER

3. EFFECTIVE DATE

9A. AMENDMENT OF SOLICITATION NUMBER

9B. DATED

PAGE OF PAGES

10A. MODIFICATION OF CONTRACT/ORDER NUMBER

10B. DATED

BPA NO.

1. CONTRACT ID CODE

FACILITY CODE

CODE

Offers must acknowledge receipt of this amendment prior to the hour and date specified in the solicitation or as amended, by one of the following methods:

The above numbered solicitation is amended as set forth in Item 14. The hour and date specified for receipt of Offers

E. IMPORTANT:

is extended,

(a) By completing Items 8 and 15, and returning __________ copies of the amendment; (b) By acknowledging receipt of this amendment on each copy of the offer submitted; or (c) By separate letter or electronic communication which includes a reference to the solicitation and amendment numbers. FAILURE OF YOUR ACKNOWLEDGMENT TO BE RECEIVED AT THE PLACE DESIGNATED FOR THE RECEIPT OF OFFERS PRIOR TO THE HOUR AND DATE SPECIFIED MAY is not extended.

12. ACCOUNTING AND APPROPRIATION DATA

(REV. 11/2016)

is required to sign this document and return ___________ copies to the issuing office.

is not, A. THIS CHANGE ORDER IS ISSUED PURSUANT TO: (Specify authority) THE CHANGES SET FORTH IN ITEM 14 ARE MADE IN THE CONTRACT ORDER NO. IN ITEM 10A.

15C. DATE SIGNED

B. THE ABOVE NUMBERED CONTRACT/ORDER IS MODIFIED TO REFLECT THE ADMINISTRATIVE CHANGES SET FORTH IN ITEM 14, PURSUANT TO THE AUTHORITY OF FAR 43.103(b).

RESULT IN REJECTION OF YOUR OFFER. If by virtue of this amendment you desire to change an offer already submitted, such change may be made by letter or electronic communication, provided each letter or electronic communication makes reference to the solicitation and this amendment, and is received prior to the opening hour and date specified.

C. THIS SUPPLEMENTAL AGREEMENT IS ENTERED INTO PURSUANT TO AUTHORITY OF:

D. OTHER

Contractor

16C. DATE SIGNED

14. DESCRIPTION OF AMENDMENT/MODIFICATION

16B. UNITED STATES OF AMERICA

Except as provided herein, all terms and conditions of the document referenced in Item 9A or 10A, as heretofore changed, remains unchanged and in full force and effect.

15A. NAME AND TITLE OF SIGNER

16A. NAME AND TITLE OF CONTRACTING OFFICER

15B. CONTRACTOR/OFFEROR

STANDARD FORM 30

PREVIOUS EDITION NOT USABLE

Prescribed by GSA - FAR (48 CFR) 53.243 (Type or print) (Type or print) (Organized by UCF section headings, including solicitation/contract subject matter where feasible.)

(Number, street, county, State and ZIP Code) (If other than Item 6) (Specify type of modification and authority) (such as changes in paying office, appropriation date, etc.)

(If required)

(SEE ITEM 11)

(SEE ITEM 13)

(X)

CHECK

ONE

13. THIS ITEM APPLIES ONLY TO MODIFICATIONS OF CONTRACTS/ORDERS,

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

11. THIS ITEM ONLY APPLIES TO AMENDMENTS OF SOLICITATIONS

AMENDMENT OF SOLICITATION/MODIFICATION OF CONTRACT

(Signature of person authorized to sign) (Signature of Contracting Officer)

VA-22-00056495

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724

36C10B Department of Veterans Affairs Technology Acquisition Center

23 Christopher Way Eatontown NJ 07724 To all Offerors/Bidders

36C10B23R0017

X

X X

June 30, 2023 @ 11:00 a.m. EDT

The purpose of this amendment, 0001, to Request for Proposal, 36C10B23R0017, is to:

1. Extend the open period to submit questions due date/time to June 5, 2023@ 11:00a.m. EDT.

2. Extend the proposal due date/time to June 30, 2023 @11:00 a.m. EDT.

3. Correct Performance Work Statement (PWS) references within Solicitation and Appendix G Task Demonstration.

4. All other terms and conditions remain unchanged and in full force and effect.

Updated: Section 5.4 System Design and Implementation (page 67), end of 3rd paragraph:

The Contractor shall design and develop the solution in accordance with the identified VA requirements listed within 5.1516 Technical Requirements, and subparagraphs.

Updated: E.11 PROPOSAL SUBMISSION INSTRUCTIONS (page 188)

1. The Offeror’s proposal shall be submitted electronically by the date and time indicated in the solicitation via email to Contract Specialist, Kawana Tyler-Simms, Kawana.Tyler-Simms@va.gov, and Contracting Officer Patrick Hamilton, Patrick.Hamilton2@va.gov in the files set forth below by the date and time indicated in the solicitation. The Offeror’s proposal shall consist of four (4) volumes. The Volumes are I -Technical Factor 1 – Written Technical Approach, II – Past Performance, III – Price and IV – Solicitation, Offer and Award Documents and Certifications/Representations. Volume I – Technical Factor 1 – Written Technical Approach is required with initial proposal submission; Technical Factor 2 – Task Demonstration is a live real-time Task Demonstration that does not require a deliverable. Technical Factor 2 – Task Demonstration will be required for those vendors who are invited to participate in the live real-time Task Demonstration. The use of hyperlinks or embedded attachments in proposals is prohibited. Accordingly, any hyperlinks or embedded attachments included with a proposal will neither be accessed nor viewed by the Government and thus, not evaluated as part of the Offeror’s proposal submission. Total submitted file size shall not exceed 100MB. NOTE: Due to file size limitations, not all emails may be received, please request a receipt response to ensure files have been delivered; multiple emails may be required due to size limitations (10MB per email). If more than one email must be submitted, please number emails as appropriate, for example, 1 of total emails to be received (e.g., 1 of 4, 2 of 4 etc.). Proposals submitted by any other method will not be considered. WARNING: Please do not wait until the last minute to submit your proposals! Late proposals will not be accepted for evaluation. To avoid submission of late proposals, we recommend the transmission of your proposal file 24 hours prior to the required proposal due date and time. Please be advised that timeliness is determined by the date and time an Offeror’s proposal is received by the Government not when an Offeror attempted transmission. Offerors are encouraged to review and ensure that sufficient bandwidth is available on their end of the transmission.

2. PROPOSAL FILES. Offeror’s responses shall be submitted in accordance with the following instructions:

a. Format. The submission shall be clearly indexed and logically assembled. Each volume shall be clearly identified and shall begin at the top of a page. All pages of each volume shall be appropriately numbered and identified by the complete company name, date and solicitation number in the header and/or footer. Proposal page limitations are applicable to this procurement. The Table below indicates the maximum page count (when applicable) for each volume of the Offeror’s proposal.

All files will be submitted as either a Microsoft Word (.docx) or Microsoft Excel (.XLSX) file as indicated in the table. Page size shall be no greater than 8 1/2" x 11" with printing on one side, only. The top, bottom, left and right margins shall be a minimum of one inch (1”) each. Font size shall be no smaller than 12-point. Arial or Times New Roman fonts are required. Characters shall be set at no less than normal spacing and 100% scale. Tables and illustrations may use a reduced font size not less than 8-point and may be landscape. Line spacing shall be set at no less than single space. Each paragraph shall be separated by at least one blank line. Page numbers, company logos, and headers and footers may be within the page margins ONLY and are not bound by the 12-point font requirement. Footnotes to text shall not be used. All proprietary information shall be clearly and properly marked. If the Offeror submits annexes, documentation, attachments or the like, not specifically required by this solicitation, such will count against the Offeror’s page limitations unless otherwise indicated in the specific volume instructions below. Pages in violation of these instructions, either by exceeding the margin, font, printing, or spacing restrictions or by exceeding the total page limit for a particular volume, will not be evaluated. Pages not evaluated due to violation of the margin, font or spacing restrictions will not count against the page limitations. The page count will be determined by counting the pages in the order they come up in the print layout view.

b. File Packaging. All of the proposal files may be compressed (zipped) into one file entitled “proposal.zip” using WinZip version 6.2 or later version or the proposal files may be submitted individually.

c. Content Requirements. All information shall be confined to the appropriate file. The Offeror shall confine submissions to essential matters, sufficient to define the proposal and provide an adequate basis for evaluation. Offerors are responsible for including sufficient details, in a concise manner, to permit a complete and accurate evaluation of each proposal. The Volume Number, Factor, File name and Page Limitation requirements (if applicable) for each file are specified in the table below:

***All Volumes under Step 1 are due at time of solicitation closure***

Step 1 Initial submission should include all Volumes and Factors below

Volume IV

Step 2 Technical Factor 2 – Task Demonstration is a live real-time Task Demonstration that does not require a deliverable.

A Cover Page, Table of Contents and/or a glossary of abbreviations or acronyms will not be included in the page count of the Technical Volume. However, be advised that any and all information contained within any Table of Contents and/or glossary of abbreviations or acronyms submitted with an Offeror’s proposal will not be evaluated by the Government.

See also FAR 52.212-1, Instructions to Offerors – Commercial Items.

(i) VOLUME I – TECHNICAL FACTOR. Offerors shall propose a detailed written approach that addresses the following:

0. Technical Factor 1 - Written Technical Approach: For this Factor

I. Describe in detail your company’s approach and ability to meet the functional requirements of a COTS SaaS solution as referenced in the PWS Section 5.1 to 5.14, including all subparagraphs. The Offerors shall specifically address the following:

a. FedRAMP/ATO: Describe your approach to obtain Federal Risk and Authorization Management Program (FedRAMP) moderate certification for your proposed SaaS solution and environment and your approach to obtain VA Authority to Operate (ATO) IAW PWS section 5.6.1. While Offerors will not be penalized during the evaluation process for not having its SaaS Solution and Environment FEDRAMP Moderate authorized at time of award/proposal submission, please be advised that Offerors that can affirmatively demonstrate their entire proposed SaaS Solution and entire Environment are FEDRAMP Moderate authorized at time of proposal submission, may receive an assessed strength or significant strength, through the evaluation process.

b. Section 508: Offerors shall submit their company’s most recent Accessibility Conformance Report (ACR) in accordance with Section 508 Accessibility Compliance of the American Disabilities Act IAW the PWS, section 5.4.1.2. **Note the ACR submission shall not count toward the total page limit of proposal submission.

c. Describe the technical approach to accomplish systems integration and interoperability in accordance with PWS Section 5.10.

d. Describe the technical approach in providing maintenance and subscription licensing to support the Government’s need for up to 700,000 profiles, as well as the five Enterprise-wide instances (Customer Testing, Sandbox, Train, Pre-prod, and Production) in accordance with PWS Section 5.7.

e. Provide a high-level Work Breakdown Structure (WBS) of the overall Project Management Plan in accordance with PWS Section 5.2.1.

f. Describe the technical approach to support the Data Migration requirement in accordance with PWS Section 5.4.2.1.

II. Describe in detail your company’s approach and techniques to implement a fully-compliant Section 508 Accessibility Compliance of the American Disabilities Act Commercial-Off-The-Shelf (COTS) Software as a Service (SaaS) Talent Development Solution in a Cloud-Based environment and all associated services as identified in PWS paragraph 5.1516, including all subparagraphs. The Offeror shall specifically address the following:

a. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that incorporates capabilities that can automate the ability to recommend talent development opportunities in accordance with PWS Section 5.1516.1.13.

b. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that can manage user attributes in a single profile that synchronizes data across the solution and uses that data to manage learning and development in accordance with PWS Section 5.1516.2.

c. Describe how the solution can support the Government’s need for permissioned administrators to use any user attribute to automatically manage assignments of courses, curricula, and content libraries accordance with PWS Section 5.1516.2.21

d. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that can emulate the Federal Authorization, Agreement, and Certification of Training Form SF-182 in accordance with PWS Section 5.1516.2.24.

e. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that can manage clinical accreditations for users of accredited training, developers of accredited training, and providers of accredited training in accordance with PWS Section 5.1516.3.7 and 5.1516.3.8.

f. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that can support the ability to create, configure and deliver dashboard reporting in accordance with PWS Section 5.1516.4.2.

g. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that enables administrators to manage competency and skills assessments, profiles, and development roles in accordance with PWS Section 5.1516.7.3.

h. Describe how the solution can support the Government’s need for an integrated virtual classroom environment that will automatically record completions and attendance in accordance with PWS Section 5.1516.6.3 and 5.1516.6.4

i. Describe in detail your company’s technical approach and ability to implement a COTS SaaS Solution in a Cloud-Based environment that enables the Government to implement and manage electronic Individual Development Plans in accordance with PWS Section 5.1516.8.

2. Technical Factor 2 - Task Demonstration:

1. Only Offerors who are determined to be among the most highly rated in Step 1 will be invited to participate in Technical Factor 2 -Task Demonstration. Offerors shall provide a live, real-time, demonstration of their ELMS solution as described in its proposal, in accordance with Appendix G (attached). The demonstration will consist of a live, real-time demonstration of the solution. Note: Vendors are expected to demonstrate each of the use cases identified in Appendix G of this document.

2. Offerors will be notified a minimum of five (5) business days in advance of the specific date/time of their demonstration which will be determined at random. The demonstration will be conducted virtually utilizing Microsoft TEAMs. All costs associated with the demonstration shall be borne by the Offeror and will not be reimbursed by the Government. The demonstration will occur over a period not to exceed two hours. Offerors do not have to use the entire two-hour time period allotted but cannot exceed the allotted time period. Interactions between Offeror and Government personnel shall be limited to opening remarks and greetings during the demonstration. Discussions, to include questions and answers, will NOT be held during the Task Demonstration.

(ii) VOLUME II – PAST PERFORMANCE FACTOR. Offerors shall submit a list of all contracts (including Federal, State, and local government and private) (prime contracts, task/delivery orders, and/or major subcontracts) in performance at any point during the three (3) years immediately prior to the proposal submission date, which are relevant to the efforts required by this solicitation. Areas of relevance include Enterprise Learning Management System, COTS implementation and SaaS, including support for client business process re- engineering, large scale software integration which include an active user base over 200,000 and/or 30,000 concurrent users. Data concerning the prime contractor shall be provided first, followed by each proposed major subcontractor, in alphabetical order. This volume shall be organized into the following sections:

(1) Section 1 – Contract Descriptions. This section shall include the following information:

(a) Contractor/Subcontractor place of performance, CAGE Code and Unique Entity Identifier (UEI). If the work was performed as a subcontractor, also provide the name of the prime contractor and Point of Contact (POC) within the prime contractor organization (name, and current address, e-mail address, and telephone and fax numbers).

(b) Contracting activity, and current address, Procuring Contracting Officer's name, e-mail address, telephone and fax numbers.

(c) Technical representative/Contracting Officer’s Representative (COR), and current e-mail address, telephone and fax numbers.

(d) Contract administration activity and the Administrative Contracting Officer's name, and current e-mail address, telephone and fax numbers.

(e) Contract Number and, in the case of Indefinite Delivery type contracts, GSA contracts, and Blanket Purchase Agreements, include Delivery Order Numbers also.

(f) Contract Type (specific type such as Fixed Price (FP), Cost Reimbursement (CR), Time & Materials (T&M), etc.) In the case of Indefinite Delivery contracts, indicate specific type (Requirements, Definite Quantity, and Indefinite Quantity) and secondary contract type (FP, CR, T&M, etc.).

(g) Awarded price.

(h) Final or projected final price.

(i) Original delivery schedule, including dates of start and completion of work.

(j) Final or projected final, delivery schedule, including dates of start and completion of work.

(2) Section 2 - Performance. Offerors shall provide a specific narrative explanation of each contract listed in Section 1 describing the objectives achieved and detailing how the effort is relevant to the requirements of this solicitation. For any contract(s)/task order(s) that did not/do not meet original schedule or technical performance requirements, provide a brief explanation of the reason(s) for the shortcoming(s) and any corrective action(s) taken to avoid recurrence. The Offerors shall list each time the delivery schedule was revised and provide an explanation of why the revision was necessary. The Offerors shall indicate if any of the contracts listed were terminated and the type and reasons for the termination.

(3) Section 3 – Subcontracts. Offerors shall provide an outline of how the effort required by the solicitation will be assigned for performance within the Offeror’s corporate entity and among the proposed subcontractors. The information provided for the prime Offeror and each proposed major subcontractor must include the entire company name, company address, CAGE Code, UEI Number and type of work to be performed by citing the applicable Government PWS paragraph number.

(4) Section 4 – New Corporate Entities. New corporate entities may submit data on prior contracts involving its officers and employees. However, in addition to the other requirements in this section, the Offeror shall discuss in detail the role performed by such persons in the prior contracts cited. Information should be included in the files described in the sections above.

Customer/Client Performance Risk Assessment Questionnaire - A Past Performance Questionnaire prepared by the Offeror’s Government customer/client for each of the Offeror’s contract citations is required, unless a separate Contractor Procurement Assessment Reporting System (CPARS) has been completed. For any listed contract that has a CPARS rating vendors are not required to submit a separate questionnaire and the Government will rely on the CPARS rating for past performance. The Offeror shall send the questionnaire electronically to the POCs for each Government contract/subcontract cited. It is the Offeror’s responsibility to prepare and issue instructions with the questionnaire requesting that each customer/client complete their response and send it electronically directly to the Contract Specialist and Contracting Officer identified below by time of proposal due date. The Offeror shall specifically request that the Government customer/client prepared questionnaire response NOT be provided back to the Offeror, either as an original or as a copy. The Government POC(s) completed questionnaire shall be sent via e-mail to the Contract Specialist, Kawana Tyler-Simms, Kawana.Tyler-Simms@va.gov, and Contracting Officer Patrick Hamilton, Patrick.Hamilton2@va.gov. The Offeror shall request that the Government POC(s) maintain the original completed/signed questionnaire as a record of their response.

(iii) VOLUME III– PRICE FACTOR The Offeror shall complete the Price Schedule found in solicitation, Section B4. Proposed unit prices shall be no more than two (2) decimal places. The Offeror shall include all items that are part of the technical solution. The list of items contained there will form the Contractor’s Price List to be incorporated in any resulting contract and will serve as the basis for prices for the IT Hardware/Software/Services, warranties, and installation for each of the ordering years specified in the Contract Schedule in Section B. These prices are binding as ceiling prices for each of the applicable ordering periods, regardless of the quantity being ordered. Consistent with the Technology Refresh requirements of the ELMS PWS, the Contractor cannot submit an ECP for Technology Refresh of an IT Hardware Commodity Product that reflects a price higher than that proposed in Section D and incorporated into the contract. Calculation of the Total Evaluated FFP will be done by adding all items contained in the Price Schedule to arrive at the total FFP for the base, all option periods and optional tasks.

(iv) VOLUME IV – SOLICITATION, OFFER AND AWARD DOCUMENTS AND CERTIFICATIONS/REPRESENTATIONS.

Certifications and Representations - An authorized official of the firm shall sign the Standard Form (SF) 1449 and all certifications requiring original signature. An Acrobat PDF file shall be created to capture the signatures for submission. This Volume shall contain the following:

Offerors are hereby advised that any Offeror-imposed terms and conditions and/or assumptions which deviate from the Government’s material terms and conditions established by the Solicitation, may render the Offeror’s proposal Unacceptable, and thus ineligible for award.

Updated: APPENDIX G – TASK DEMONSTRATION

Demonstration Agenda:

1. Introductions

2. Vendor Demonstration System Description

3. Relationship of Demonstration System to Proposed Solution

4. Configuration Overview

5. Use Cases – Four Categories (A. Learning Management, B. Accreditation, C. Reporting & Analytics and D. Virtual Learning)

1. Introductions:

The vendor demonstration team will introduce itself to the Government evaluation team.

1. Vendor Demonstration System Description:

Display and describe the demonstration system. Include hardware, operating system, server containers (database server, application server, web server, etc.), client containers, and show the configuration, including any clustering or caching mechanisms.

1. Relationship of Demonstration System to Proposed Solution:

Display and describe how the demonstration system models the proposed production system. Include how the demonstration system configuration and capabilities relate to the proposed solution in terms of architecture, design, and system level capabilities.

1. Configuration Overview: Display and describe how all major components of your proposed solution integrate with one another.

1. Use Cases:

A. Learning Management IAW PWS sections 5.1516.1 and 5.1516.2 B. Accreditation IAW PWS sections 5.1516.3 C. Reports & Analytics IAW PWS sections 5.1516.2, 5.1516.4, and 5.1516.7 D. Virtual Learning IAW PWS section 5.1516.6

Offerors shall clearly announce each Use Case by corresponding letter and number prior to demonstration so there is no confusion as to what is being demonstrated. Offerors are required to complete each of the steps outlined in the demonstration requirements in order. Specifically, Offerors shall present its Use Case portion of the demonstration in the following order, A. Learning Management, B. Accreditation, C. Reports & Analytics, and D. Virtual Learning. As each of the steps reflects one or more requirements outlined in the performance work statement, Offerors are required to demonstrate every step. All demonstrations will be evaluated on:

A. Learning Management

1. Demonstrate the administrator’s ability to:

a) Enter the record for a web-based course

b) Make the course listing available to learners

c) Assign that course to specific learners to be completed at a specified date.

2. Demonstrate the learner’s ability to search for a course using a specific key word (title, description, and metadata), add the course to a list of content the learner wants to take, and on that list find that course.

a) Show the ability to launch the course.

b) Show the ability to exit and resume the course at the point they left it at a later date.

3. Show how a learner would complete a solution-generated pre-test, post-test, and course evaluation. Show how a learner/user would find their score on a test.

4. Demonstrate how a learner could enroll in a course that is scheduled for a future date. Show how the learner could cancel the registration, if needed.

5. Demonstrate how the learner can view current, past, and future training requirements. Display how the learner can access their transcripts and show the options available to the learner for exporting, saving, or printing them.

a) Demonstrate how a learner could generate a certificate for a completed course.

b) Demonstrate how a learner will be able to manage or upload training transcript/ certificate data from external courses or conferences attended.

6. Demonstrate the ability to enable supervisors to manage their teams:

a) Demonstrate that a supervisor can view all learners assigned to them

b) Demonstrate that a supervisor can assign and unassign learning to all their subordinates

c) Demonstrate that a supervisor can approve learning and development request from all subordinates

d) Demonstrate that a supervisor can generate reports on all their subordinates’ learning and development activities

e) Demonstrate that a supervisor can review, comment on, and indicate acceptance of their subordinates’ individual development plans

B. Accreditation

1) Demonstrate the ability to manage courses as an accredited provider of clinical training by:

a) Managing course and content metadata identifying specific accreditations and accreditation-related information

b) Demonstrating the ability to manage workflows for approved accreditation managers to assign clinical accreditations to specific clinical content

c) Demonstrating the ability to create custom accredited certificates of completion for clinical accredited training (e.g., ACCME and ANCC)

d) Demonstrating the ability to generate reports for all accredited activities recorded in the system. Demonstrate the ability for administrators to report by accreditation type within the system to generate reports according to the accreditation source, learner, supervisor, Government agency audiences and course, and demonstrate a sample report

e) Requiring the completion of a survey to receive an accredited completion

f) Tracking delivery of and reporting on use of courses and content per accrediting body requirements

2) Demonstrate the ability to support learner requirements associated with clinical accreditations:

a) Demonstrate the ability for the learner to select a preferred accreditation

b) Demonstrate how a learner can document accreditation-related unique accreditation provider identifiers on their profile

c) Demonstrate how a learner would search for and track progress in, and record completion of, content offering specific accreditations

d) Demonstrate how a learner would generate certificates of completion conforming to individual accrediting body requirements (e.g., ACCME, ANCC)

3) Demonstrate the ability for a learner to record completion of external accredited training, including the ability to attach an associated document.

C. Reporting & Analytics

1) Demonstrate the creation of an ad-hoc reporting tool that will meet an emergent need, i.e., the number of nurses who completed or did not complete an assigned learning activity.

a) Demonstrate the different report output formats available

2) Demonstrate the ability to deliver drill down dashboards at the enterprise level, enabling the head of a 700,000-person organization to see the department’s compliance and deficiency rate on a mandatory training assignment and then drill down to the lowest organization level to show the same data.

3) Demonstrate the out of the box reporting & analytics capabilities of the Learning Record Store (LRS).

a) Demonstrate the ability to receive, store, and return data about learning experiences, achievements, and employee development

b) Demonstrate the ability to define and apply access permissions to read and write data

c) Demonstrate the ability to provide reporting, dashboards, and analytics functions that are designed to interpret and analyze the data

4) Demonstrate the ability to assess competency skill gaps and deliver associated reports.

a) Demonstrate an administrator’s ability to implement the competency model with all associated pieces e.g., proficiency levels

b) Demonstrate the system’s ability to assign competency models to individuals

c) Demonstrate a learner’s ability to complete a competency self-assessment

d) Demonstrate the system’s ability to compare the individual’s self-assessment with the expected proficiency levels for the position they occupy and show the competency skill gaps that result in the solution

e) Demonstrate the system's capability for routing and approving an employee competency or skills assessment to another user, e.g. manager, in order to generate an official rating

D. Virtual Learning

1) Demonstrate how an administrator sets up the virtual classroom.

2) Demonstrate the virtual classroom’s ability to deliver breakout rooms, multi-dimensional polls, moderated chats, host and presenter staging, interactive content, and interactive whiteboards.

3) Demonstrate how an instructor can manage all aspects of the virtual classroom

4) Demonstrate how a learner can find the time-based virtual classroom offering in the learning platform

5) Demonstrate how the learner’s ability to access the virtual classroom environment from the learning platform with no second login requirement

6) Demonstrate how the learner’s participation in the virtual classroom gets recorded in the learning platform automatically