CONTROLLED UNCLASSIFIED INFORMATION (CUI)

SOURCE SELECTION INFORMATION – SEE FAR 2.101 & 3.104

PERFORMANCE WORK STATEMENT

Department of Defense Education Activity 4800 Mark Center Drive

Alexandria, VA 22350

Interactive Slideshow Software with Formative Assessment

1. General Information and Scope of Work

1.1 Agency

The Department of Defense Education Activity (DoDEA) is one of only two federally operated school systems operated by DoD. DoDEA plans, directs, coordinates, and manages prekindergarten through 12th grade educational programs in 161 fully accredited schools that serve over 66,000 children of active-duty military and DoD civilian families. Our curriculum, resources and student achievement scores on standardized assessments compare favorably to those of high-performing US public school systems.

Operating as a field activity of the Office of the Secretary of Defense (Personnel and Readiness), DoDEA is overseen by a director located at our headquarters in Alexandria, VA. DoDEA’s schools are organized into three geographic areas: Americas, Europe, and Pacific. In the Americas, DoDEA operates 50 schools located in seven states, Puerto Rico, and Cuba. In Europe and the Middle East, DoDEA operates 64 schools located in Germany, England, Netherlands, Belgium, Spain, Turkey, Bahrain, and Italy. In the Pacific, DoDEA operates 46 schools located in Korea, Japan (mainland and Okinawa), and Guam. Finally, DoDEA also operates a fully accredited virtual high school with teaching hubs in the Americas, Europe, and Pacific.

Table 1: School Year 2025-26 Projected Enrollment (December 3, 2024) - Rounded to nearest 25

Grade Students Grade Students Grade Students Grade Students -- --- 3 5,875 7 4,625 11 2,975 K 5,525 4 5,750 8 4,400 12 2,800 1 5,950 5 5,450 9 3,650 K-12

Total 61,325 2 5,850 6 5,150 10 3,325

1.2 Background

DoDEA procured interactive slideshow software with formative assessment in 2020 and now, per Federal regulations, must recompete this requirement.

1.3 Scope of Work

DoDEA requires interactive slide software with formative assessment functionality that includes (1) an age-appropriate lesson bank or templates and (2) the ability to make customized lesson for use by K-12 students and teachers systemwide. As shown in the table above, the estimated number of K-12 student licenses needed is about 61,325. The number of school-level and above-school-level educators is approximately 12,000.

DoDEA also requires related virtual product training for teachers and related technical support, maintenance, and upgrades. DoDEA expects to make one award for a 5-year base period.

2 Requirements

2.1 Objective 1, Slideshow Software: The objective is to provide interactive slide software with formative assessment functionality and related professional learning and technical support.

The tasks listed below help the Contractor understand the requirements but are not exhaustive.

The Contractor shall develop a complete solution using a performance-based approach.

2.1.1 Task 1, Functionality—The Contractor’s solution shall accommodate the needs of a school system of our size and unique global structure and shall possess the following functionality:

# FUNCTIONALITY

Integration and Compatibility

1 Functions optimally with Google Chrome and Chromebooks (Chrome Extension) and Microsoft OS and Microsoft Edge.

2 Integrates seamlessly with Google Slides and PowerPoint.

3 Integrates seamlessly with DoDEA's learning management systems and platforms, specifically, Schoology, Google Classroom , and Microsoft Teams for Schools & Students.

Assessment and Feedback Tools

4 Provides multiple ways to formatively assess student understanding (multiple choice, constructed response, short answer, annotation, drag and drop).

5 Allows teachers to add formative assessment to Google Slides and PowerPoint.

6 Permits teachers to create ad hoc assessment questions.

7 Permits teachers to receive student data in real time and provide feedback and comments.

8 Allows teachers to display exemplars while keeping the student authors anonymous.

9 Enables teachers to export student data to a spreadsheet or a PDF.

10 Allows students to view feedback and track progress from learning activities.

11 Permits teachers to view single or all student responses and activity within the activity.

12 Allows for voice recordings on each slide.

User Interaction and Content Management

13 Enable users to easily connect to and interact with the presentation from their own devices.

14 Allows teachers to lead activities or assign self-paced asynchronous activities for individuals, small groups, and the whole class.

15 Provides teachers the option to see presentations from the view of their students.

16 Permits teachers to instantly create lessons and exit tickets by uploading existing files.

Includes a library of templates and or lessons that are standards-based age appropriate and covers a variety of content including but not limited to English Language arts, mathematics, social studies, science, art, music, PE, health, world languages, and digital citizenship.

18 Allows teachers to edit the library templates or lessons.

2.1.2 Task 2, Product Training & Professional Learning—The Contractor shall:

2.1.2.1 Product Training: Provide asynchronous webinars and/or digital modules that give an overview of the proposed solution and guidance on navigation and use. Recording of these asynchronous webinars shall be made available and accessible at any time. Digital modules shall be Shareable Content Object Reference Module® (SCORM®) compliant. See PWS 3.9 for additional information about SCORM® compliance.

2.1.2.2 Professional Learning: Provide each year during the duration of the contract one 60-minute synchronous session for educators annually, each of which shall be delivered three times—a total of three hours. Deliver two additional 60-minute synchronous webinars three times each—a total of six hours.

Each year’s webinars shall include information about software updates and features to improve instruction and student learning. Each webinar shall occur during the normal business hours for the Americas, Europe, and Pacific regions. (For additional information about each region’s hours of operation, see PWS 3.4.)

Record all webinars and place them on DoDEA’s learning management system, (LMS, Schoology, SharePoint). Note: In consultation with the Contractor, DoDEA will determine the exact topics and will schedule the webinars post award.

2.1.2.3 Library: Provide a Contractor-hosted library of on-demand videos and guides designed to help teachers and support professionals to use the software to promote student learning and achievement.

2.2 Objective 2, General Requirements—The Contractor shall:

2.2.1 Task 1, Technical Support: Provide industry-standard technical support for its digital resources for the life of the contract via telephone or email within one business day from the initial contact to include but not limited to assisting with service problems, product setup, upgrades, and troubleshooting.

2.2.2 Task 2, Technical Requirements for Digital Resources—The Contractor shall:

2.2.2.1 Provide digital resources designed to run in DoDEA’s learning management system (LMS, Schoology), which operates within our virtual learning environment (VLE). In addition, provide teacher and student access to the Contractor’s digital resources through a single sign-on platform that uses one username and password to access what is needed, specifically, via DoDEA’s identity, rostering, and management platform (currently, ClassLink).

2.2.2.2 Deliver digital resources in one of the following formats:

1) Integrated via DoDEA’s LMS to the digital resources hosted by the Contractor.

2) Hosted externally by the Contractor but accessible via DoDEA’s LMS to the digital assignments and assessments imported, hosted, and maintained in the LMS.

2.2.2.3 Ensure the course content meets the following specifications:

1) Conforms to IMS Learning Global Consortium (IMS) content packaging specifications.

2) Uses imported content, if required, conforming to IMS content packaging specifications.

3) Uses code that does not disable LMS features when digital resources are accessed.

4) Requires single—not multiple—authentications to access content via DoDEA’s LMS.

5) Incorporates, where applicable, assessments that are IMS Test and Question Interoperability

(QTI)-conformant.

6) Uses content-hosted externally that conforms to any of the existing versions of IMS

Learning Tools Interoperability (LTI), per www.imsglobal.org.

2.2.3 Task 3, Third-Party Programs, Software, and Applications: Ensure its own and its subcontractors’ (third-party) programs, software, and applications meet—at a minimum—the same technical requirements as the Contractor must meet, such as single sign on (SSO) and Federal Risk and Authorization Management Program (FedRAMP) Level 2, etc. On a case-by-case basis, DoDEA may honor requests to waive the FedRAMP Level 2 requirement. For more information, see Technical Exhibit #1, 1.1.

2.2.4 Task 4, Delivery of Digital Resources: The Contractor shall deliver digital materials with instructions detailing how the resources can be accessed by teachers, students, and above-school-level educators.

2.2.5 Meetings: Attend virtual meetings at no additional cost to the Government and provide the medium through which each meeting occurs, record each meeting’s minutes. Submit the draft minutes to the COR within two business days of the event and finalize the minutes two business days after receipt of written feedback from the COR. Note: Costs associated with attending any face-to-face meetings shall be handled/paid for as stated in the contract.

2.2.5.1 Post-Award Conference: Participate in a video- or teleconference with the COR five business days after award IAW FAR Subpart 42.5.

2.2.5.2 IT Meeting: Convene a video- or teleconference with DoDEA Information Technology staff ten business days after award, per Technical Exhibit #1.

2.2.5.3 Other Post-Award Meetings: Meet with the Contracting Officer (KO), COR, and/or other

Agency personnel, as appropriate, to review Contractor performance, as required by DoDEA.

The KO may discuss the Agency’s view of Contractor performance, and the Contractor shall apprise the Agency of any problems being experienced. The Contractor shall take appropriate action to resolve any outstanding issues the Agency raises.

2.3 Performance Standards and Acceptable Quality Levels

2.3.1 Performance Standard: Tasks shall be completed by the required completion date.

2.3.2 Acceptable Quality Level: See PWS Section 7, Performance Requirement Summary (PRS).

3 Constraints

3.1 Place of Performance: Work shall be performed at the Contractor’s facilities.

3.2 Privacy—The Contractor shall:

3.2.1 User Accounts: Require, wherever applicable, that individual accounts possess unique usernames and passwords that do not require personally identifiable information (PII) to access online content, i.e., first & last name and any other unique personal information.

3.2.2 Contractor Personnel

Ensure personnel assigned to this contract take proper precautions to protect information from disclosure. Collect and/or store all agency-owned or agency-controlled PII in accordance with the relevant requirements of the Privacy Act, 5 U.S.C, which may be found at the following URL:

http://www.archives.gov/about/laws/privacy-act-1974.html.

All Contractor personnel that have access or may potentially have access to DoDEA data in any form shall be US citizens, including any third-party penetration (PEN)/security testers.

3.2.3 Privacy Training: Ensure Contractor staff who have access to DoDEA’s student, teacher and/or staff personally identifiable information successfully complete the DoD Privacy Act/Personally Identifiable Information (PA/PII) training before gaining access to the data and yearly thereafter. Provide copies of the certificates of completion to the COR which can be audited at any time by the Chief Information Security Officer (CISO) or his/her designee.

3.2.4 Privacy Verification: Provide the COR written verification of compliance to the Privacy requirements (listed above) 120 calendar days prior to the expiration of each year’s contract option period or annually, as required. Note: After reviewing the Contractor’s verification, DoDEA reserves the right to ask for further verification data in order for DoDEA to comply with DoD’s evolving privacy mandates.

3.3 Liaison and Alternate Liaison—The Contractor shall:

3.3.1 Provide a liaison and alternate liaison to be responsible for the performance of work. Their names shall be designated in writing to the Contracting Officer. They shall have full authority to act for the Contractor on all contract matters relating to the daily operation of this contract. Each shall have at least one year of experience working in a similar role.

3.3.2 Notify the COR in writing regarding any change in either the liaison’s role ten business days in advance of the change If the liaison or liaison alternate is changed post-award, the replacement shall meet or exceed the qualifications and experience of the person assigned upon contract award.

3.4 Holidays and Hours of Operation

3.4.1 The liaison or alternate liaison shall be available during the hours of 9AM to 3PM Eastern Standard

Time (EST), except for Federal holidays and Federal government closures/shutdowns. The following list shows recognized Federal holidays: New Year’s Day, Martin Luther King Jr.’s Birthday, Presidents Day, Memorial Day, Juneteenth National Independence Day, Independence Day, Labor Day, Columbus Day, Veterans Day, Thanksgiving Day, and Christmas Day.

3.4.2 Although there are different time zones within Europe and the Pacific and different hours for specific schools throughout DoDEA, the normal business hours for the regions roughly correspond to the following: Americas, 0700-1500 EST; Europe, 1300-2100 EST; and Pacific, 2000-0400 EST. there are different time zones within Europe and the Pacific and different hours for specific schools throughout DoDEA, the normal business hours for the regions roughly correspond to the following:

Americas, 0700-1500 EST; Europe, 0200-1000 EST; and Pacific, 2000-0400 EST.

3.5 Availability: The Contractor shall make all resources available for the life of the contract.

3.6 Nondiscrimination: The Contractor shall provide resources free of bias regarding race, color, religion, sex, national origin, or disability.

3.7 Section 508 Compliance—The Contractor shall:

3.7.1 Background: Section 508 of the Rehabilitation Act, as amended by the Workforce Investment Act of 1998 (P.L. 105-220) requires Federal agencies that develop, procure, maintain, or use information and communication technology (ICT) to endure they are accessible to people with disabilities.

Federal employees and members of the public who have disabilities must have access to and use of information/data that is comparable to people without disabilities.

3.7.2 Requirement: Ensure that products, platforms, and services delivered as part of this work statement that are ICT or contain ICT conform to the Revised 508 Standards, 36 C.F.R. § 1194.1 & Apps.

A, C & D which are located at the following URL: https://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-ict-refresh/final-rule/text-of-the-standards-and-guidelines.

3.7.3 ARS: See the attached ICT Accessibility Requirements Statement (ARS). All functional performance criteria apply when using an alternative design or technology that achieves substantially equivalent or greater accessibility and usability by individuals with disabilities, than would be provided by conformance to one or more of the requirements in Chapters 4-6 of the Revised 508 Standards or when Chapters 4-6 do not address one or more functions of ICT. Note the guidance in the table below:

Applicable Requirements Directions

Software Features and Components

Applies to all WCAG Level AA Success Criteria, 502 Interoperability with Assistive Technology, and 503 Applications.

Hardware Features and Components All requirements apply.

Support Services and Documentation All requirements apply.

Outputs/Deliverables Ensures that outputs/deliverables do not adversely affect accessibility features of the existing EIT technologies.

3.8 Optical Character Resolution (OCR): The Contractor shall provide, upon request, two digital OCR copies of print materials in one or more of the following five formats: Digital Accessible Information System/National Instructional Materials; Accessibility Standard (NIMAS) with cascading style sheet; HyperText Markup Language (HTML); Portable Document Format (PDF, unlocked, embedded fonts, single page); and Rich Text Format (RTF)/Word document.

3.9 Sharable Content Object Reference Model® (SCORM®) Compliance: Provide digital modules, if included among the proposed/required resources, that are SCORM®-compliant. Note: The Department of Defense Instruction (DoDI) 1322.26 mandates that modules comply with the latest possible version of SCORM®, per https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/132226_dodi_2017.pdf?ver=2017- 10-05-073235-400.

3.10 Data & Data Rights: All data developed from any work awarded under this contract is and shall remain the property of the Government. The Contractor shall ensure that digital rights to all visual materials embedded in the resources will be given so that DoDEA for DoDEA’s internal use only may use resources without incurring copyright costs or infringing on copyright laws. All data developed from any work awarded under this contract is and shall remain the property of the Government.

3.11 Organizational Conflict of Interest (OCI): The Contractor (including any subcontractor) personnel performing work under this contract may receive, have access to, or participate in the development of, proprietary or Privacy Act information (e.g., personal information, education, etc.) may create a current or subsequent OCI as defined in FAR Subpart 9.5. Whenever the Contractor becomes aware that such access or participation may result in actual or potential OCI, the Contractor shall (1) immediately notify the Contracting Officer (KO) in writing and (2) promptly submit a plan to the KO to avoid or mitigate any such OCI. Note: The KO will unilaterally determine if the Contractor’s plan is acceptable. If the KO determines the plan cannot satisfactorily avoid or mitigate an OCI, s/he may implement other remedies to include prohibiting the Contractor’s further participation in contracted requirements.

4 Government-Furnished Information / Resources None

5 Contract Deliverables

Milestone/Deliverable Format PWS Planned Frequency

Submit To

Objective 1, Slideshow Software Task 1, Functionality Digital 2.1.1 Ongoing after receipt of initial delivery order COR customers Task 2, Product Training Digital 2.1.2.1

Tsk 2, Professional Learning Digital 2.1.2.2 As scheduled post-award

Milestone/Deliverable Format PWS Planned Frequency

Submit To

Objective 2, General Requirements

Task 1, Technical Support Digital 2.2.1 Ongoing after receipt of initial delivery order COR or Requestor

Task 2, Technical Require-ments for Digital Resources Digital 2.2.2 Ongoing COR/IT

Task 3, Third-Party Programs, Software, and Applications Digital 2.2.3 Ongoing COR/IT

Task 4, Delivery of Digital Resources Digital 2.2.4 Ongoing access in three business days after receipt of initial delivery order COR

Constraints

User Accounts Digital 3.2.1 Ongoing after receipt of initial delivery order COR

Privacy Training Digital 3.2.3 Three days after receipt of a written request COR

Privacy Verification Digital 3.2.4 120 calendar days prior to end of contract year COR

6 Acronyms and Definitions

PA/PII Privacy Act/Personally Identifiable Information SCORM® Shareable Content Object Reference Model®

Contracting Officer (KO): Only individual with expressed authority to obligate (bind) the Government by means of entering, administering, and terminating contracts within the limits of the authority delegated via a KO’s warrant.

Contracting Officer’s Representative (COR): Qualified and trained Government employee, nominated by the requiring activity (RA) and appointed in writing by a KO primarily to perform specific technical or administrative functions on a specific contract(s); serves as the ‘eyes and ears’ of a KO to assure the Government’s best interests are protected via the terms and conditions of the contract(s) appointed. COR’s do not have authority to obligate (i.e., bind) the Government.

Contractor: Supplier or vendor contracted to provide specific supplies or services to the Government. The term may also be referred to as the prime.

Deliverable: Usually physically delivered items but may include such items as digital documents/reports, which are provided by the Contractor to the Government.

Performance Work Statement (PWS): Statement of work for performance-based acquisitions describing the required results in clear, specific, and objective terms with measurable outcomes.

7 Performance Requirement Summary

Performance Objective

Performance Standard Acceptable Quality Level Method of

Surveillance Inspector

Objective 1, Slideshow Software

Task 1, Functionality PWS 2.1.1 Completed in required timeline

Accessible 24/7/365 except for scheduled downtimes and one day per semester.

Accessing resources

COR &

customers

Task 2, Product Training

PWS 2.1.2.1

Task 3, Professional Learning

PWS 2.1.2.2

Completed in required timeline

At least 75 percent of DoDEA participants rate the professional learning as good or excellent.

(DoDEA will conduct the survey.)

Digital feedback from participants

Objective 2, General Requirements

Performance Objective

Performance Standard Acceptable Quality Level Method of

Surveillance Inspector

Task 1, Technical Support, PWS 2.2.1

Completed in required timeline

Acknowledge receipt of request within two hours. Resolve 90% of requests in one business day.

Resolve the remaining 10% in five business days.

Normal usage of digital resources and customer complaints

COR &

customers

Task 2, Technical Requirements for Digital Resources, PWS 2.2.2

Completed in required timeline 100% PWS-compliant Initial and random inspections IT

Task 3, Third-Party Programs, Software, and Applications, PWS 2.2.3

Completed in required timeline 100% PWS-compliant Initial and random inspections IT

Delivery of Digital Resources, PWS 2.2.4

Completed in required timeline

Ongoing access 24/7/365, except for scheduled downtimes and one unscheduled downtime per semester.

Normal ordering of resources

COR &

customers

Constraints

User Accounts, PWS 3.2.1

Completed in required timeline 100% PWS-compliant

Normal usage and customer complaints

COR &

customers

Privacy Training, PWS 3.2.3

Completed in required timeline

No more than one certificate per year sent to the COR more than three business days from the date of the COR’s request for it.

Receipt of a copy of the certificate

COR &

PII

Specialist

Privacy Verification

PWS 3.2.4

Completed in required timeline

Submitted 120 calendar days prior to the end of each contract year.

Written verification of compliance

COR &

PII

Specialist

Technical Exhibit #1 - TECHNICAL REQUIREMENTS

The Contractor shall comply with the applicable technical requirements detailed below.

1.1 Software and Cloud Security Requirements—The Contractor shall:

1.1.1 Ensure all online resources, cloud-based services and instructional software meet Department of Defense

(DoD) and DoDEA cybersecurity requirements as defined below. Note: Software, cloud services and associated websites are rigorously tested to ensure no security risks are posed to DoDEA infrastructure and its users.

1.1.2 Complete the Cloud Services questionnaire that was submitted as part of the proposal submission and provide copies of and/or access to any software listed in the proposed solution.

1.1.3 Ensure its content accessible from the web is compatible with the following browser platforms: Google Chrome, and Edge. Ensure that any applicable STIGs are implemented.

1.1.4 Provide a plan of actions and milestones (POA&M) to mitigate any cybersecurity findings resulting from non-compliant and/or vulnerable components in 30 calendar days of written notification from DoDEA.

1.1.5 Be able to meet Federal Risk and Authorization Management Program (FedRAMP) Level 2 standards for all proposed software/digital resources and ensure that any third-party resources that are part of its proposed solution also meet the FedRAMP Level 2 standard. For more information on FedRAMP, see the following URL: www.fedramp.gov. Participate, if required, in interviews and deep system architecture inspections.

Per DoD policy for cloud-based services, DoDEA conducts a supplemental series of validations, which closely mirror the FedRAMP Internet Cloud vetting processes. Contractor participation/cooperation is normally required to complete this process.

On a case-by-case basis, DoDEA may honor requests to waive the FedRAMP Level 2 requirement.

1.2 System Requirements—The Contractor shall:

1.2.1 Provide, per Section 1.1 (above), any software installed and/or accessed in or by a DoDEA system, network whether stand-alone or web-based, is compatible with the standards cited herein.

1.2.2 Provide minimum desktop/server system technical specifications, reference architectures, networking specifications and diagrams, and applicable systems configuration documentation for the proposed solution.

1.2.3 Provide software that is compatible with the following minimum baseline:

Specifications Minimum Memory 4 GB

Hard Drive 100 GB

Processor Intel® Core™ i5-8365U Processor 8th Generation (up to 4.1GHz, 6MB cache) equivalent or better (Must show benchmark/passmark scores)

Video Graphics Integrated Intel HD Graphics 620 (1920x1080) equivalent or better Operating System Windows 11

Browser Environment Chrome, Edge, Edge Chromium

1.2.4 Provide software that is completely functional on a standard DoDEA desktop without the need or requirement for administrative-level user rights and/or permissions or the requirement to use or insert external media to execute the software.

1.2.5 Provide software that does not require modifications to folder permissions while executing.

1.2.6 Provide, if applicable, software packages that support unattended installation methods used by enterprise software packaging and deployment systems.

DoDEA currently distributes software packages via Microsoft’s System Center Configuration Manager

(SCCM) and Microsoft Intune.

All older 16-bit software are automatically denied.

1.3 Data Management Requirements—The Contractor shall:

1.3.1 Provide a mechanism for batch administration and automation of routine data management tasks via flat file import, or representational state transfer (REST) based web service application programming interfaces (APIs). The mechanism shall provision and manage data objects within the Contractor’s system, including but not limited to organizational structures, student accounts, staff accounts, courses, and class rosters.

1.3.2 Provide all necessary documentation and assets to facilitate batch administration and automation of routine data management tasks, including but not limited to roster template files (i.e., comma separated value templates); data element/field definitions documentation; data interchange formats and schemas (XML/ JSON); and/or data dictionaries for the purpose of mapping organizational student information system (SIS) data to the Contractor’s required input formats.

1.3.3 Provide a single point of contact to support DoDEA in performing the required data integration activities within the Contractor’s system.

1.3.4 Configure DoDEA enterprise within its system and/or databases as the appropriate organizational entity (i.e., region, district, school) upon a request in writing from the contracting officer’s representative (COR).

Note: DoDEA’s organization hierarchy consists of the following: one system, three regions, nine districts, 62 communities, and 161 schools, including the K-12 virtual school programs.

1.3.5 Participate in a technical meeting with DoDEA within ten business days after award for the purposes of preparing for onboarding of new services and initial configuration of administrator-level accounts.

1.3.6 Ensure the transfer of any Sensitive, Confidential data including but not limited to PII data be transferred in a secure means meeting any requirements set by DoDEA’s Chief Information Security Officer (CISO).

1.3.7 Current CMMC 2.0 Level attestation/certification status and roadmap (if a Plan of Action and Milestones POA&M) is permitted under Level 2 interim).

1.3.8 SPRS score and NIST 800-171 assessment results; remediation POA&Ms with target dates.

1.3.9 Security program evidence (e.g., System Security Plan (SSP), Security Assessment Report (SAR), POA&M), incident response plan, data flow diagrams, and logging/monitoring approach.

1.3.10 (Optional, when available) SOC 2 Type II or ISO/IEC 27001 certifications.

1.3.11 Implement and maintain NIST SP 800-171 controls; provide continuous monitoring along with monthly security status reports.

1.3.12 Use encryption in transit and at rest with FIPS 140-2/3 validated cryptography; enforce Multi-Factor Authentication (MFA) and Role-Based Access Control (RBAC).

1.3.13 Maintain audit logging, vulnerability management (including regular scanning and patching), configuration management, and incident response protocols; provide a 72-hour breach notification to the Contracting Officer (CO) and DoDEA Cyber.

1.3.14 Submit and update SPRS scores in accordance with DFARS; allow government access (or third-party assessor access) to facilitate required assessments.

1.3.15 Ensure that all subcontractors handling DoDEA data adhere to DFARS/CMMC requirements.

1.3.16 For cloud services: Prefer FedRAMP Moderate or High Authority to Operate (ATO) or other DoD-authorized equivalents for hosting CUI; provide necessary documentation and details regarding data residency.

1.3.17 Comply with FERPA/COPPA for student data and execute the DoDEA Data Privacy Agreement (DPA) where applicable.

1.4 DoDEA Software License Keys: The Contractor shall provide (1) license keys and electronic downloads for software required under this Contract to the COR and (2) software directly to DoDEA schools, districts, or regions only if explicitly required to do so in the contract or in writing by the COR.

1.5 Cybersecurity Supporting Elements/Requirements and Scalability—The Contractor shall:

1.5.1 Comply with the same Federal law and DoD policies and guidance to which DoDEA is subject that include but are not limited to the cybersecurity requirements defined in the following documents:

DoD Directive (DoDD) 8500.01E, Information Assurance, be found at the following URL:

https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/850001_2014.pdf.

DoD Security Technical Implementation Guidance (STIG), which may be found at the following

URL: https://public.cyber.mil/stigs/downloads/.

DoD Risk Management Framework (DODRMF) per DoD Instruction 8510.01, which may be found at https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/851001p.pdf?ver=2019-02- 26-101520-3004.5.2.

1.5.2 Provide security patches/upgrades to include third-party applications in response to public-released security vulnerabilities associated with its software solution. Provide a POA&M for any security vulnerabilities within five business days of discovery. Software upgrades/patches shall be included in the licensing cost and be performed at the least disruptive times as determined by DoDEA in writing. Note: Any exception to this requirement must be approved in advance and in writing by DoDEA’s Chief Information Officer (CIO) or designated official.

1.5.3 Protect DoDEA data against all cyberattacks, notifying DoDEA within 72 hours of an identified and confirmed breach/intrusion.

1.5.4 Perform security incident investigations upon identification of an event or at the request of DoDEA.

1.5.5 Address all information assurance vulnerability messages (IAVM) in the defined timelines to include IA vulnerability alerts (IAVA), IA vulnerability bulletins (IAVB), and technical advisories (TA).

1.5.6 User passwords must not be readable by anyone having access to the system.

1.5.7 Ensure any portion of its solution that involves Internet access by DoDEA students complies with the relevant requirements of the Children's Internet Protection Act, Public Law 106-554, § 1(a)(4) [Div. B, Title XVII, § 1701], Dec. 21, 2000, 114 Stat. 2763, 2763A-335. All Contractor personnel that have access or may potentially have access to DoDEA data in any form shall be US citizens. Note: If its solution does not involve Internet access by DoDEA students, please ensure the following are included:

1) Maintaining system security IAW the latest versions of the (1) DoD Cloud Computing Security

Requirements Guide, (2) Family Educational Rights and Privacy Act (FERPA), and (3) Protection of Pupil Rights Amendment (PPRA).

2) Providing a solution robust enough to serve the needs of a large community of learners dispersed across the world using a variety of bandwidths and scalable to meet future growth, both in terms of instruction and the number of users. In addition, provided solutions shall be applicable to the digital learning environment of the DoDEA Virtual School.

3) Ensuring Contractor staff who have access to DoDEA’s student, teacher and/or staff personally identifiable information take the DoD Privacy Act/Personally Identifiable Information (PA and PPI/PII) training before gaining access to the data and yearly thereafter. Provide copies of the certificates to the COR which can be audited at any time by the CISO or his/her designee.

1.6 Program and System Integration—The Contractor’s solution shall:

1.6.1 Provide Single Sign-On (SSO) Capabilities / Platform which (1) integrates with an Industry Standard SSO login solution. (ClassLink, Google, Azure, etc.); (2) supports Oauth 2.0, Security Assertions Markup Language (SAML) for integration with Azure, or Google; and (3) authenticates using Azure Active Directory (AD) or Google AD. Authenticates using Azure Active Directory (AD) or Google AD.

1.6.2. Support industry-standard data rostering standards via ClassLink and standard data formats such as OneRoster.

1.6.3. Ensure that data storage, handling, and security meet the following minimum standards:

1) DoDEA’s information and data shall be secured in data center located in the United States.

2) The system, including its server(s) and network devices, shall be in an environmentally controlled and secure facility under controlled circumstances (e.g., using authorized personnel access lists, ID cards, entry logs, etc.).

3) All Contractor personnel that have access or may potentially have access to DoDEA data in any form shall be US citizens, including any third-party penetration (PEN)/security testers.

4) All data transit shall be secured with Transport Layer Security (TLS) encryption.

5) All data at rest shall be secured with Advanced Encryption Standard (AES)-256 encryption.

1.6.4 Ensure that data integration includes the following:

1) Automated industry standard form of data integration using Representational State Transfer Application

Program Interface (RESTful API), Learning Tools Interoperability (LTI), or Secure File Transfer Protocol (SFTP) data sets (ClassLink, OneRoster, etc.).

2) Encryption of DoDEA’s data at rest to include unique encryption keys for each customer on systems hosting multiple customers.

3) Notification of DoDEA in writing within 72 hours of any changes made to corporate policies for data protection.

4) Use of only masked student data in a non-production environment.

5) Integration scheduling that meets DoDEA’s required timeframes.

6) Provision of fully automated data uploads per Agency schedule(s) and Agency requirements.

7) Support of SFTP capabilities using a single set of login credentials.

8) Provision of a single data set of DoDEA information. Note: The Contractor’s solution shall support

DoDEA at all levels: school, community, district, region, and HQ.

9) Maintenance of a backup and restore plan for DoDEA data in the event of a disaster.

10) Provision of detailed feedback of what caused errors if an integration transmission results in errors.

1.6.5 System Features—The system shall:

1) Allow user accounts to be created automatically based on a file provided by DoDEA either nightly or on another pre-determined scheduled feed.

2) Allow DoDEA to be able to choose the format of user login identification, e.g., an email address, and be able to create manual accounts, if needed.

3) Require the user—for manually created accounts—to reset the password on the user’s initial login or, upon request, a password reset.