26QE064_ATTCH8_PWS_070726.pdf

CONTROLLED UNCLASSIFIED INFORMATION (CUI)

SOURCE SELECTION INFORMATION – SEE FAR 2.101 AND 3.104

July 7, 2026

DEPARTMENT OF WAR EDUCATION ACTIVITY (DoWEA)

PERFORMANCE WORK STATEMENT (PWS)

FOR

K-8 WORLD DIGITAL LANGUAGE APPS

1.0 Introduction

1.1 Background

The Department of War Education Activity (DoWEA) is one of only two federally operated school systems.

DoWEA plans, directs, coordinates, and manages prekindergarten through grade 12 educational programs in 160 fully accredited schools that serve over 65,000 children of active-duty military and DoW civilian families. Our curriculum, resources and student achievement scores on standardized assessments compare favorably to those of high-performing US public school systems.

DoWEA is overseen by a director located at our headquarters in Alexandria, VA. Our schools are organized into three geographic areas: Americas, Europe, and Pacific. In the Americas, DoWEA operates 50 schools located in seven states, Puerto Rico, and Cuba. In Europe and the Middle East, DoWEA operates 64 schools located in Germany, England, Netherlands, Belgium, Spain, Turkey, Bahrain, and Italy. In the Pacific, DoWEA operates 45 schools located in Korea, Japan (mainland and Okinawa), and Guam. DoWEA also operates one fully accredited virtual high school with teaching hubs in the Americas, Europe, and Pacific.

As a reminder, FAR Clause 52.212 4(q) requires the Contractor to comply with all applicable Federal, state, and local laws, executive orders, rules, and regulations applicable to its performance under this contract. DoWEA is a DoW field activity, providing education from prekindergarten through grade 12. Executive Order 14168, Defending Women from Gender Ideology Extremism and Restoring Biological Truth to the Federal Government, and Executive Order 14190, Ending Radical Indoctrination in K–12 Schooling, are particularly applicable to DoWEA contracts.

DoWEA has never awarded a systemic contract for a world language digital application for K-8 students and teachers.

1.2 Scope

DoWEA requires access to a research-driven, interactive, standards-aligned and immersive language resource that should be available on multiple platforms, designed to help students develop language proficiency in a variety of world languages through scaffolded lessons in reading, writing, listening, and speaking. The selected resource should use a variety of student and teacher tools to give students immediate language feedback, including speech-recognition technology. The resource will also provide language educators with planning and reporting tools to help personalize instruction, identify needs and trends, and monitor student progress. The minimum languages on the app must include, but not be limited to, are Arabic, Chinese (Mandarin), Dutch, English, French, German, Italian, Japanese, Korean, Spanish, and Turkish.

DoWEA cannot determine the exact number of students and teachers who will be using the world language application. Based on current enrollment in world language and culture classes and professional judgement, approximately 23,500 students, 265 classroom teachers, and four above-school-level educators will use it.

Currently, DoWEA estimates a growth of about 500 students per year.

2.0 Requirement Objectives

2.1 General Objective for World Language Digital Application

The objective is to procure a research-driven, interactive, standards-aligned immersive language resource designed to help students develop proficiency in a variety of world languages through scaffolded lessons in reading, writing, listening, and speaking and to provide tools that (1) give language feedback, which may include speech-recognition technology and (2) provide educators with planning and reporting tools to help personalize instruction, identify needs and trends, and monitor student progress. The following tasks help the Contractor understand the requirements to meet the objective but are not exhaustive. The Contractor must develop a complete solution using a performance-based approach.

Supporting Tasks for Requirement - Objective #1 – The Contractor shall:

2.1.1 Provide the world language digital application as a single 5-year license per student and teacher or annual licenses with renewal options corresponding to the contract’s option period. Provide access to, at a minimum, the following languages: Arabic, Chinese (Mandarin), Dutch, English, French, German, Italian, Japanese, Korean, Spanish, and Turkish. Allow users to toggle from one language to another.

Performance Standards (PS) and Acceptable Quality Levels (AQL) - Objective #1 PS 2.1.1: PWS-compliant AQL: Access 24/7/365 except for scheduled downtimes beginning three business days after receipt of the initial delivery order.

2.1.2 Provide world language digital application resources that are appropriate in content and approach to learning for students in kindergarten to 8th grade, and that the cultural representations (if any) are accurate for the nation(s) or groups that speak the language(s).

Performance Standards and Acceptable Quality Levels - Objective #1 PS 2.1.2: PWS-compliant AQL: At least 95 percent of the teachers do not report any concerns/complaints about the content and approach in learning for students.

2.1.3 Ensure language digital application’s resources are correlated to the World-Readiness Standards for Learning Languages developed by the American Council on the Teaching of Foreign Languages (ACTFL), and to the NCSSFL-ACTFL Can-Do Statements. Preference: The world language digital application’s resources should be aligned with and able to report the level of proficiency in the ACTFL Proficiency Scale as the students use the app.

Performance Standards and Acceptable Quality Levels - Objective #1 PS 2.1.3: PWS-compliant AQL: DoWEA verifies the world language digital application’s resources correlated to the World-

Readiness Standards for Learning Languages.

2.1.4 Provide contract support to include responding to teacher incident reports, technical requests generated by the contracting officer’s representative (COR) or DoWEA administrator, and a student and/or teacher usage data report.

Performance Standards and Acceptable Quality Levels - Objective #1 PS 2.1.4: PWS-compliant AQL: Teacher incident reports are resolved two business days after issuance. Technical requests and student and/or teacher usage data report issues shall be provided to DoWEA within 30 calendar days of receipt of the written request.

2.2 General Requirements

The objective is to ensure that the requirements for technical support, single-sign-on, and third-party digital resources are met. The following tasks help the Contractor understand the requirements to meet the objective but are not exhaustive. The Contractor must develop a complete solution using a performance-based approach:

Supporting Tasks for Requirement - Objective #2 – The Contractor shall:

2.2.1 Technical Support: Provide industry-standard technical support for its digital resources for the life of the contract, via telephone or by email within 24 hours from the initial contact, to include but not be limited to, assisting with service problems, product setup, upgrades, troubleshooting and technical support data requests, as needed.

Performance Standards (PS) and Acceptable Quality Levels (AQL) - Objective #2 PS 2.2.1: Completed in the required timeframe AQL: Acknowledge receipt of request within 24 hours of initiation of request. Resolve at least 90 percent of requests in 48 hours. Resolve the remaining 10% in five business days.

2.2.2 Technical Requirements for Digital Instructional Resources: Ensure the following:

2.2.2.1 Provide digital resources that can run in DoWEA latest version of its operating system (WIN), Google Chrome and/or Google Classroom.

2.2.2.2 Deliver digital resources via either (a) digital resources hosted by the Contractor or (b) hosted externally by the Contractor but accessible via DoWEA’s Student Information System (DSIS), DoWEA’s latest version of its operating system (WIN), Google Chrome, and/or Google Classroom. The contractor shall have a product that is capable into integrate into a cloud-based Identity and Access Management (IAM), Single Sign-On (SSO) platform, (e.g.

ClassLink) designed specifically for the education sector.

2.2.2.3. Provide a classroom management component that allows teachers to monitor and assign student work. If the product has any student-to-student communication capabilities (such as chatroom or messaging system), it should be turned off or have the capability of being turned off. As part of the teacher management tools, the product should include also the ability for teachers to keep track of student work.

2.2.2.4 Provide a user (DoWEA student and DoWEA teacher) and superuser (DoWEA administrator) management system, where DoWEA teachers and DoWEA administrators can view, create, filter and/or manipulate data and report: (a) student app usage data (language, how much engagement time, how often, etc.), (b) student language proficiency data (levels of proficiency attained), (c) DoWEA teacher has the ability to assign tasks to individual students or groups of students, (d) where data and data reports can be imported to the DoWEA Student Management System (SMS), currently ASPEN (DSIS) and (e ) data described above can be assigned, organized and reported in a hierarchical order (student/teacher/school/district/region).

2.2.2.5 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. Note: DoWEA does not employ a formal “waiver” process for FedRAMP requirements. If a proposed platform is not FedRAMP‑authorized, vendors shall demonstrate compliance through acceptable alternative security documentation that evidence alignment with the FedRAMP Moderate (Level 2) baseline.

Acceptable alternatives include submission of a FedRAMP‑aligned Body of Evidence (BoE) or equivalent documentation set, which may include:

Documentation equivalent to a System Security Plan (SSP) describing system architecture, authorization boundary, data flows, and control implementation

Independent security assessment results demonstrating that required controls have been tested and validated

Risk and vulnerability management artifacts (e.g., POA&M or equivalent) documenting identified findings and remediation efforts

Security policies and procedures aligned to NIST SP 800‑53 control families Evidence of continuous monitoring, including vulnerability scanning, incident response, and ongoing risk management processes.

Performance Standards and Acceptable Quality Levels - Objective #2 PS 2.2.2.5 Completed in the required timeframe AQL: 100 percent PWS-compliant

2.2.3 Delivery of Digital Resources

2.2.3.1 Deliver digital materials with instructions detailing how the digital resources can be accessed by teachers, students, and above-school-level educators, using proprietary Digital Application features or integrated into DoWEA’s LMS or integrate into a cloud-based

Identity and Access Management (IAM), Single Sign-On (SSO) platform, (e.g. ClassLink) designed specifically for the education sector.

2.2.3.2 Allow DoWEA users (teachers, administrators) to download and/or print resources as needed.

For example, a teacher may want to provide a printed worksheet for students or a student with an individual educational program (IEP) may require the textbook in print form. Note:

DoWEA provides assurances that printable resources will be for internal use only, and that copyrights will be protected, as applicable.

Performance Standards (PS) and Acceptable Quality Levels (AQL) - Objective #2 PS 2.2.3 Completed in the required timeframe AQL: Ongoing access 24/7/365, except for scheduled downtimes and one unscheduled downtime per semester. Contractor must notify the DoWEA contract POC at least 48 hours before maintenance or downtime periods that will prevent access to the online resources and approximate duration of downtime.

2.2.4 Meetings: Contractor representatives attend virtual planning and follow up meetings with DoWEA during mutually agreed upon dates and times, at no cost to the Government, and agree to provide the means to (or participate in) record of each meeting.

2.2.4.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.4.2 IT Meeting: Convene a video- or teleconference with the Agency’s Information Technology staff ten business days after award, per Technical Exhibit #1.

2.2.4.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 the Agency. 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 DoWEA raises.

Performance Standards and Acceptable Quality Levels - Objective #2 PS 2.2.4: Completed in the required timeframe AQL: 100 percent PWS-compliant

2.2.5. Product Training: Contractor will provide asynchronous product training to DoWEA K-8th grade teachers that allow teachers to interact with the application and its tools, and that includes pedagogical suggestions on how to incorporate the product into classroom language and culture instruction. A product training shall be offered at least once a year at the beginning of each DoWEA school year, and for every year of the contract. The asynchronous training must be available for further training. DoWEA’s preferred training session format would be presented in a SCORM compliant (or similar) format that is compatible with the Schoology platform environment.

3.0 Constraints

3.1 Place of Performance: Any required work shall be performed at the Contractor’s facilities.

3.2 Privacy—The Contractor shall:

3.2.1 User Accounts: Allow, wherever applicable, individual language digital application accounts (teachers, students and administrators) to 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 PII DoWEA data in any form shall be U.S. Citizens, U.S. Nationals as defined by 8 U.S.C. §1408, or U.S. Persons as defined by 22 C.F.R. §120.62, including any third-party penetration (PEN)/security testers.

3.2.3 Privacy Training: Ensure Contractor staff who have access to DoWEA’s student, teacher and/or staff personally identifiable information successfully complete the DoW 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 with 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, DoWEA reserves the right to ask for additional verification data so the Agency can comply with DoW’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 provided 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 this role, or a similar role.

3.3.2 Notify the COR in writing regarding any change in the liaison’s roles 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, 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, 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.

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 ensure 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 Sharable Content Object Reference Model® (SCORM®) Compliance: If applicable and included in the offer, provide asynchronous, digital teacher professional learning modules, that are SCORM®-compliant, or a similar format, such as Thin Common Cartridge (TCC). Note: The Department of War Instruction (DoWI)

1322.26 mandates modules comply with the latest version, per https://www.esd.whs.mil/Portals/54/Documents/DD/issuances/dodi/132226_dodi_2017.pdf?ver=2017-10- 05-073235-400.

3.9 Data & Data Rights: All data developed and used for 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 DoWEA—for our 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.10 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.0 Government-Furnished Resources

4.1 Government Furnished Property/Equipment (GFP/GFE): None

4.2 Government Furnished Information/Materials (GFI/GFM): None

5.0 Deliverables

Milestone/Deliverable Format No. of Copies PWS Ref. Frequency/Delivery Date Submit

To

World Language Digital Application and Associated Resources

Digital -- 2.1.1 2.1.2 2.1.3

Access available three business days after receipt of initial delivery order

COR

customers

Teacher Incident Reports

Email, phone call, or ticket created at the Contractor’s website

1 2.1.4

Notification within one business day of occurrence; resolution report within two business days of occurrence

COR

Technical Request (generated by the COR or administrator)

Email, phone call 1 2.1.4

Contractor response to technical request within thirty calendar days

COR

Student and/or Teacher Usage Data Report

Excel, Word, email 1 2.1.4

Contractor response to technical request within thirty calendar days

COR

Technical Support Email or phone call 1 2.2.1 Ongoing after the post-award conference

COR

customers

Milestone/Deliverable Format No. of Copies PWS Ref. Frequency/Delivery Date Submit

To

Delivery of Digital Resources Digital 1 2.2.3

Access available within three business days of receipt of a delivery order

COR

Privacy Training Digital 1 3.2.3

Certificates of completion provided within three business days of a written request from the COR

COR

Privacy Verification Digital 1 3.2.4 Provide verification 120 calendar days prior to the end of each contract year

COR

6.0 Definitions/Acronyms

PA/PII Privacy Act/Personally Identifiable Information

SCORM® Shareable Content Object Reference Model®

Contracting Officer (KO): Only individuals with the expressed authority to obligate (bind) the Government by means of entering, administering, and terminating contracts within the limits of the authority delegated via the 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. CORs do not have the authority to obligate (bind) the Government.

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

Deliverable: Usually physically delivered items but may include such items as digital documents/reports.

7.0 Performance Requirement Summary (PRS)

Objective Performance Standard AQL Method of Surveillance Inspector

World Language Digital Application and Resources, PWS 2.1

PWS-compliant

Access 24/7/365 except for scheduled downtimes beginning three business days after receipt of the initial delivery order

Normal usage by COR and customers

COR

customers

Teacher Incident Reports, PWS 2.1.4 PWS-compliant

Teacher incident reports are resolved two business days after issuance

COR and customer verification

COR and incident-generating customer

Technical Request (generated by the COR or administrator), PWS 2.1.4

PWS-compliant Issues are resolved within 30 calendar days

Review by COR and request-generating customer

COR and request-generating customer

Objective Performance Standard AQL Method of Surveillance Inspector

Student and/or Teacher Usage Data Report, PWS 2.1.4

PWS-compliant Issues are resolved within 30 calendar days

Normal review by COR and customers

COR

customers

Technical Support, PWS 2.2.1

Completed in the required timeframe

Acknowledge receipt of request within 24 hours of initiation of request. Resolve at least 90 percent of requests in 48 hours.

Resolve the remaining 10% in five business days.

Review by COR and request-generating customer

COR and request-generating customer

Delivery of Digital Resources, PWS 2.2.3

Completed in the required timeframe

Ongoing access 24/7/365, except for scheduled downtimes and one unscheduled downtime per semester. Contractor must notify the DoWEA contract POC at least 48 hours before maintenance or downtime periods that will prevent access to online resources and approximate duration of downtime

Normal usage by COR and customers

COR

customers

Vendor Privacy Training, PWS 3.2.3

Completed in the required timeframe 100% PWS-compliant COR surveillance COR

Vendor Privacy Verification, PWS 3.2.4

Completed in the required timeframe 100% PWS-compliant COR surveillance COR

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

(DoW) and DoWEA cybersecurity requirements as defined above and below. Note: Software, cloud services and associated websites are rigorously tested to ensure no security risks are posed to DoWEA 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. If the Contractor has sub-contracted certain software or functionalities of the language digital application to other entities, the Contractor will provide the same cloud services information about the subcontracted software or functionalities.

1.1.3 Ensure its content is accessible from the web and 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 DoWEA.

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 DoW policy for cloud-based services, DoWEA 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, DoWEA 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 DoWEA 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 DoWEA 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.

DoWEA 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 DoWEA in performing the required data integration activities within the Contractor’s system.

1.3.4 Configure DoWEA enterprise within its system and/or databases as the appropriate organizational entity (i.e., student, teacher, school, district, region, HQ) upon a request in writing from the contracting officer’s representative (COR). Note: DoWEA’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.

Specific to this project are: One (1) K-12 Host Nation and World Languages Instructional Systems Specialist at HQ level, three (3) Host Nation/World Languages Regional Instructional Systems

Specialists at Regional Level, and one (1) Host Nation Japan Instructional Systems Specialist (Japan only).

1.3.5 Participate in a technical meeting with DoWEA 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 DoWEA’s Chief Information Security Officer (CISO).

1.4 DoWEA 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 DoWEA schools, districts, or regions only if explicitly required to do so in the contract or in writing by the COR. It is DoWEA’s preference that both teacher licenses and student licenses to the language digital application is a five (5) years license; however, vendors may propose annual licenses with renewal options corresponding to the contract's option periods. Each license must provide access to multiple languages.

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

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

DoW Directive (DoWD) 8500.01E, Information Assurance, be found at the following URL:

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

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

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

DoW Risk Management Framework (DOWRMF) per DoW 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. The vendor must provide a POA&M for any High or Critical vulnerabilities within 48 hours of discovery (Medium/Low can remain at five business days).

Software upgrades/patches shall be included in the licensing cost and be performed at the least disruptive times as determined by DoWEA in writing. Note: Any exception to this requirement must be approved in advance and in writing by DoWEA’s Chief Information Officer (CIO) or designated official.

1.5.3 Protect DoWEA data against all cyberattacks, notification to the COR and CISO within 24 hours of any suspected or confirmed security incident, followed by a detailed report within 48 hours.

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

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 DoWEA 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 DoWEA data in any form shall be U.S. Citizens, U.S. Nationals as defined by 8 U.S.C. §1408, or U.S. Persons as defined by 22 C.F.R. §120.62, including any third-party penetration (PEN)/security testers. Note: If its solution does not involve Internet access by DoWEA students, please ensure the following are included:

1) Maintaining system security IAW the latest versions of the (1) DoW 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 DoWEA Virtual School.

3) Ensuring Contractor staff who have access to DoWEA’s student, teacher and/or staff personally identifiable information take the DoW 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 Google or Azure; and (3) authenticates using Azure Active Directory (AD) or Google AD. Authenticates using Azure Active Directory (AD) or Google AD. Data must be secured in a data center located strictly within the Continental United States (CONUS) to prevent jurisdiction issues.

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) DoWEA’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 DoWEA data in any form shall be U.S. Citizens, U.S. Nationals as defined by 8 U.S.C. §1408, or U.S. Persons as defined by 22 C.F.R. §120.62, 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.

6) The contractor must document their key management practices (rotation schedules, system protection) during the post-award IT meeting.

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 DoWEA’s data at rest to include unique encryption keys for each customer on systems hosting multiple customers.

3) Notification of DoWEA 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 DoWEA’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 DoWEA information. Note: The Contractor’s solution shall support

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

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

10) Provision of detailed feedback on 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 DoWEA either nightly or on another pre-determined scheduled feed.

2) Allow DoWEA 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.