Evaluation_Criteria.pdf

Attachment III 15BNAS19RCA0130

Evaluation Criteria

National Acquisitions Section

The Bureau will evaluate each offer based on the best value, trade-off process as outlined in the Federal Acquisition

Regulations, part 15.101-1- Tradeoff Process. All evaluation factors and sub-factors other than price, when combined, are significantly more important than price. Evaluations will note the strengths, deficiencies, weaknesses (to include significant weaknesses) and risks of each proposal, in a summary format with supporting narrative

Definitions.

Strength is an aspect of the proposal that increases the likelihood of successful contract performance.

Deficiency is a material failure of a proposal to meet a

Government requirement or a combination of significant weaknesses in a proposal that increases the risk of unsuccessful contract performance to an unacceptable level.

A weakness is a flaw in the proposal that increases the risk of unsuccessful contract performance. A “significant weakness” in the proposal is a flaw that appreciably increases the risk of unsuccessful contract performance.

A Risk is a potential to cause disruption of schedule, increased cost or degradation of performance.

The Government reserves the right to award a contract to an offeror other than the offeror proposing the lowest price when the Government’s evaluation determines a proposal is significantly superior from a non-price standpoint and warrants payment by the Government of a premium.

NON-PRICED FACTORS:

Factor 1: Technical

Sub factor A- Written technical proposal. This written proposal shall contain the following: (DUE NO LATER THAN

PROPOSAL DUE DATE)

I. Learning Management System

Content- All standards shall be addressed through the content provided via the LMS.

Skill practice, assignments, and assessments shall provide variation through regular and periodic content updates, question banks, and randomization.

Reading Intervention- All reading sills shall be addressed though the research-based content

(activities, lessons, resources, etc.) provided via the LMS.

Career Technical Education- The LMS shall provide career technical education which leads to and/or provides a specific industry recognized and accepted credential/certificate.

Assessment- The LMS shall provide benchmark/placement assessment which the system shall use to determine which skills and associated assignments the learner has mastered.

Remediation- The assignment of practice for remediation within the LMS shall be assigned to the learner with and without teacher/administrator intervention.

Reporting- LMS shall provide learners report, teachers report, and other reporting views with the ability to create customizable reports.

Additional LMS Features- LMS shall provide scientific calculator, multimedia instruction, Skill practice and assignments

II. Support

Contractor shall provide teachers and LMS administrators with technical and content support via portal, email, chat, and phone Monday – Saturday from 7:00 am – 10:00 pm EST.

III. Professional Development

The contractor shall provide professional development for FBOP staff on the following:

Teacher Training

Administrator training

Provides for teacher/test administrator continual professional development

IV. Miscellaneous

LMS content shall be updated no less than once a year for all learning levels and subject areas.

All data and learner personal information are the property of the FBOP and cannot be shared or disposed of without prior consent of the

Bureau.

The FBOP shall retain ownership of any on-premise LMS platform(s), content, data, updates, etc. The agency shall retain the platform, content, data, etc. post award.

The vendor shall provide the option for multiple forms of delivery, to include but not limited to, zero clients, tablets, handheld devices, and laptops.

The content of the LMS shall prepare learners to earn one of the three HSE tests, GED, HiSET, and TASC.

The vendor shall present the FBOP no less than two licensing options, such as concurrent user license, enterprise license, named user license, etc.

Sub-factor B LMS Systems

I. Scalability

Proposal shall indicate the proposed LMS platform on-premise hosted virtual environment (supported hypervisors)or cloud-based environment.

Proposal shall describe interfaces (consoles, portals, etc.) and tools used for administration of the LMS in the on-premised hosted virtual environment.

LMS architecture must support 100,000 name users.

Proposal shall describe the provisioning process for establishing new user accounts.

Also, the process for bulk uploads for account creation in Active Directory.

Proposal shall describe the process for central management of the LMS environment across multiple datacenters in an on-premise virtual solution.

Proposal shall define the LMS application minimum and recommended requirements for system resource consumption (CPU, memory, disk storage capacity, etc.) at the indicated scale.

Identify the requirements needed for the back-end LMS server environment, as well as any requirements per client.

II. Performance

Proposal shall describe how the LMS architecture may be configured to support an estimated 7,000 concurrent users/sessions.

Proposal shall define the network bandwidth requirements necessary to support streaming educational content to an endpoint in the LMS architecture. Discuss the differences in bandwidth requirements between a cloud-based instance of the LMS solution versus an on-premise distributed VDI implementation (if applicable).

Proposal shall provide any additional specific performance requirements that impact the sizing and scaling of a VDI solution.

Solution must be browser based and browser agnostic.

III. Reliability/Availability

Proposal shall describe how the LMS shall support high availability configurations for an on-premise solution.

For any cloud-provisioned environment offered as-a-Service, proposal shall identify any

Service Level Agreements (SLAs) that relate to system availability.

For cloud solutions, the LMS publisher/developer shall be FedRAMP authorized or an accredited environment.

Proposal shall describe the process of moving user accounts and data between organizational units while accurately maintaining progress and performance data.

IV. Security

The LMS must support integration with Active

Directory for user account management.

The LMS must support role-based access control

(RBAC). Describe access control and permissions assignment within the application.

Application event logging is required to include user transactions logs (system access, duration of general access, time spent per course, etc.). Application logs must be exportable to a syslog database for forensics and analysis. If the LMS accesses external feeds or integrations with third-party software or services, those interactions shall be logged. The government reserves the right to deny any third-party software or services.

Proposal shall describe the method of publishing courses and tests to students.

Proposal shall provide a secured isolated space/domain for the government (i.e., BOP specific URL). Authentication controls must fail securely and deny access.

Proposal shall describe the LMS application’s support for multi-factor authentication for administrative users. Utilizing government-issued PIV/CAC cards for authentication shall be an authentication option.

Proposal shall describe the administrative user self-service feature for password or account reset.

Credentials shall be transported using a suitable (minimal 256 bit) encrypted link.

Identify any pages/functions that require a user to enter credentials that are not done over an encrypted link.

Proposal shall describe the method of request throttling in place to prevent automated authentication attacks.

Proposal shall describe the LMS application’s session management security features.

Cryptographic libraries shall meet or exceed the FIPS 140-2 standard.

Proposal shall describe the LMS key management system (KMS).

Does the LMS application employ client-side storage or caching? If so, is any sensitive data cached at the client?

The LMS application must support binary digital signature by a publicly trusted Certificate

Authority.

The LMS must use encryption for all application traffic. Please describe. Additionally, define which ports and protocols are used for communication.

Please describe additional client software required, if any. Does the LMS use Adobe Flash, Active-X, Silverlight, NACL, client-side Java or other client-side technologies for content delivery?

Isolation and segregation of all authenticated user accounts, to include data, and organizational units is required. Please describe.

For cloud solutions, public access is not authorized.

If the LMS contains tools used for communication (student to teacher or teacher to student announcement, email, other), this function must have the option to be disabled.

V. Interoperability

Please identify any dependencies or limitations that confine the deployment options to specific hardware types, operating systems, or deployment modes (e.g., appliances or endpoints).

For an on-premise deployment model, the LMS must be compatible with the current Microsoft supported server operating system version.

Solution must be browser based and browser agnostic.

The LMS must provide 508 compliance. Please provide 508 VPATs with the proposal.

The BOP reserves the right to provide its own licensing for operating systems, databases, etc.

VI. Other

Describe the extent to which human-machine interfaces and consoles may be customized for

Bureau-specific content, appearance, and functionality.

VII. Proposal Volume

Learning System Management narrative responses to demonstrate project comprehension and address platform and content requirements (See

SOW Learning Management System section) must not exceed 20 pages.

LMS Systems narrative responses to demonstrate project comprehension and address technical requirements (See SOW Technical Requirements section) must not exceed 15 pages.

Total solicitation submission shall not exceed

35 pages in total.

Factor 2: Past Performance

Recent and relevant past performance will be evaluated on its performance under existing and prior contracts for similar services, with an emphasis on the similarity of the Offeror’s experience to the Request for Proposal (RFP). The purpose of

Past Performance is to allow the government to review the

Offeror’s recent and historical probability of meeting the solicitation requirements.

A Offeror’s past performance information shall include three

(3)of the contractor’s most recent contracts occurring during the past five years that are similar and relevant in nature to the services required in the Statement of Work. Contracts listed may include those entered into with the Federal Government, agencies of state and local government, and commercial entities.

Offerors shall address any instances of past performance problems in the referenced contracts and explain how these problems were resolved. The Government may consider efforts performed by the Offeror for agencies of the federal, state, or local governments and commercial customers as potentially relevant to the Past Performance evaluation.

Offerors should not provide general information on their performance on the identified contracts. General performance information MUST be obtained from the references on the Past

Performance Questionnaire and submitted along with the Offeror’s proposal. Offeror’s without a record of relevant company past performance or for whom information on Past Performance is not available will not be evaluated favorably or unfavorably on Past

Performance. References other than those identified by the

Offeror may be contacted. Information utilized may be obtained from the references listed in the proposal, other customers known to the Government or of whom it becomes aware, and any others who may have useful and relevant information (i.e. Past

Performance Information Retrieval System (PPIRS), System for

Award Management (SAM), Federal Awardee Performance & Integrity

Information System (FAPIIS), and internet).

Factor 3: Price

Price is defined as the Offerors’s price proposal. The

Contracting Officer will evaluate price independently. Pursuant to FAR 17.203(b), the Government’s evaluation of offers shall be inclusive of options. Price proposal in Schedule of Items

(Attachment I) will be evaluated on the base period and options periods in total, including the Option to Extend Services clause.