RFQ_DoDEA_PLC_Virtual_Implementation.pdf

HH601014RCPEH04

COMBINED SYNOPSIS/SOLICITATION

General Information

Date: March 18, 2014

Document Type: Combined Synopsis/Solicitation Solicitation Number: HH601014RCPEH04 and issued as a Request for Quote (RFQ) Set Aside: None NACIS Code/Small 611710, Educational Support Services/$14 Million Business Size Standard:

Contracting Office Address:

Department of Defense Education Activity (DoDEA) Procurement Division 4800 Mark Center Drive, 5th Floor Alexandria, VA 22350

Description

This is a combined synopsis/solicitation for commercial items prepared in accordance with the format in Federal Acquisition Regulation (FAR) Subpart 12.6, as supplemented with additional information included in this notice. This announcement constitutes the only solicitation; proposals are being requested and a written solicitation will not be issued.

This solicitation HH601014RCPEH04 is issued as Request for Quotation (RFQ) using FAR Subpart 13.5 procedures. This solicitation document and incorporated provisions and clauses are those in effect through Federal Acquisition Circular 2005-72. This requirement is being procured using full and open competition.

The Department of Defense Education Activity (DoDEA) has a requirement for the implementation of a virtual systemwide Professional Learning Community (PLC). The period of performance is a base period of one year, plus two one-year option periods. The FOB point is Destination. Inspection and acceptance shall be at the Government site. As a result of this solicitation, the Government intends to award one firm-fixed-price contract with a period of performance of one 12-month base period and up to two consecutive 12-month option periods. The anticipated award date is early June 2014.

The following attachments provide additional information and details regarding the Government’s minimum requirements:

Attachment A – Performance Work Statement (PWS), Pages 3-15 Attachment B – Contract Line Item (Pricing) Schedule, Page 16 Attachment C – Government Product Accessibility Template (GPAT), Pages 17-44 Attachment D – Solicitation Provisions and Clauses, Pages 45-57 Attachment E – Past Performance Part 1, Page 58 Attachment F – Past Performance Part 2, Pages 59-60

The following FAR provisions and clauses for commercial items are applicable to this acquisition:

52.212-1, Instructions to Offerors -- Commercial Items (JULY 2013)- (See Attachment D for addendum to this provision) 52.212-2, Evaluation – Commercial Items (JAN 1999)- (See Attachment D for full text version of provision) 52.212-3, Offeror Representations and Certifications -- Commercial Items (NOV 2013) 52.212-4, Contract Terms and Conditions -- Commercial Items (SEPT 2013)- (See Attachment D for addendum to this clause) 52.212-5, Contract Terms and Conditions Required To Implement Statutes Or Executive Orders -- Commercial Items (Deviation 2013-O0019) (JAN 2014)

Addendums to the FAR provisions and clauses 52.212-1, 52.212-2, and 52.212-4, and additional FAR and Defense FAR Supplement (DFARS) provisions and clauses determined by the Contracting Officer to apply to this acquisition are provided at Attachment D – Solicitation Provisions and Clauses.

RFQ Questions Cutoff Date:

Questions and inquiries regarding this RFQ shall be submitted electronically via email to Nina Lin, Contracting Officer, at Nina.Lin@hq.dodea.edu no later than 10 a.m. EST on April 1, 2014, with subject line “Questions - HH601014RCPEH04 PLC.” A consolidated list of answers to questions received will be posted via an amendment to this RFQ on FedBizOpps.gov.

RFQ Closing Date (**Please note there are two separate submission dates**):

Quotes shall be submitted electronically via e-mail to Nina Lin, Contracting Officer, at Nina.Lin@hq.dodea.edu no later than 10 a.m. EST on April 30, 2014, with the subject line, “Quote - HH601014RCPEH04 PLC.” All Information Technology (IT) components and online resources shall be submitted four weeks prior to RFQ close date on April 2, 2014 at 10 a.m. EST to undergo a preliminary review by the DoDEA Information Technology (IT) Division to ensure they do not pose a threat to the DoDEA IT infrastructure before they are evaluated over the DoDEA network by a technical evaluation team (TET).

Point of Contact:

Nina Lin, Contracting Officer 4800 Mark Center Drive, 5th Fl Suite 05G02-02- Attn: Procurement Division Alexandria, VA 22350-1400 Telephone: 571-372-1445 Nina.Lin@hq.dodea.edu

ATTACHMENT A: PERFORMANCE WORK STATEMENT (PWS)

Department of Defense Education Activity Professional Learning Communities (PLC) Initiative:

Virtual Support for Systemwide PLC Implementation

1.0 INTRODUCTION

1.1. The Department of Defense Education Activity (DoDEA) serves the educational needs of the dependents of military and civilian employees by providing PK-12 instruction to approximately 82,000 students in seven states, twelve foreign countries, Guam, and Puerto Rico. The number of students varies based on the deployment of military troops worldwide. DoDEA’s curriculum, resources, and student achievement scores on standardized assessments compare favorably to high-performing US public schools.

1.2 DoDEA is divided into three administrative areas. DDESS (Domestic Dependent Elementary and Secondary Schools) covers the schools in seven states and Puerto Rico, and for administrative purposes, Cuba. DoDDS (Department of Defense Dependent Schools) is divided into DoDDS- Europe and DoDDS-Pacific. The former administers the schools in England, Germany, Italy, Belgium, Netherlands, Spain, Portugal, Turkey, and Bahrain. The latter covers the schools in Korea, Japan, and for administrative purposes, Guam. DoDEA also operates a fully accredited Virtual High School with its main office in Virginia and with teaching hubs in Germany and Okinawa.

1.3 DoDEA has adopted the Common Core State Standards (CCSS), whose curriculum standards are rigorous, research-based, and reflect the knowledge and skills our students need for success in college and careers.

1.4 DoDEA teachers use the same standards-based curriculum and resources systemwide.

Curriculum standards may be found at http://www.dodea.edu/Curriculum/index.cfm.

2.0 BACKGROUND

2.1 Approximately two-thirds of DoDEA’s 191 schools have implemented a professional learning community (PLC). The level of implementation has been far from uniform.

2.2 Due to the wide geographic dispersion of DoDEA schools, systemic professional development initiatives are usually implemented with virtual resources that include archived recordings and/or digital modules that can be used after training has occurred.

2.3 The Virtual Support for the Systemwide PLC initiative is the third prong of a three- pronged initiative. The first prong is providing online professional development resources on a wide variety of 21st century teaching, learning, and leading and the Common Core State Standards topics that are available to educators 24/7. The second prong is providing staff development coaches (approximately one per school) who will provide teachers on-site and/or virtual support. The third prong, which this requirement addresses, uses PLCs to change school culture systemwide, that is, to use PLCs to have a job-embedded focus on collaboration and learning that will result in changes in positive classroom practices and higher student achievement.

2.4 The purpose of the PLC initiative is to improve student achievement and learning by implementing PLCs systemwide that possess the following six characteristics:

Focus on Learning and Results by:

o Identifying essential outcomes/foci o Using common formative assessments to monitor student performance o Using a variety of data to develop interventions and drive instructional decisions o Responding consistently and intentionally when students fail to meet their learning targets.

Engagement in Collective Inquiry and Learning through the following:

o Questioning the status quo, seeking new methods, testing them, and reflecting on their results o Building shared knowledge by clarifying questions the group explores together o Building the capacity of each staff member to implement beliefs, attitudes, strategies, and processes that will result in all students achieving at a high level o Dedicating time and space to collaborative interactions among staff o Learning from each other through peer observation that deepens knowledge of content and instructional practice and fuels continuous growth/engagement.

Focus on Shared Values and Vision evidenced by the groups’ deeply shared commitment to student learning, development, and well-being

Support and Focus on Shared Leadership demonstrated by distributive leadership (1) where staff members share power, authority, and decision making to bring about changes in teaching and learning/expected results and (2) where stakeholder interests are balanced through teams developing, adopting, and observing ground rules and protocols that clarify how team members will work together and fulfill their responsibilities.

Focus on a Culture of Collaboration seen through collaborative team learning which (1) promotes collective responsibility and accountability and (2) engages stakeholders in seeking continuous school improvement.

Exhibition of Mutual Trust and Respect evidenced by (1) honoring the expertise of others; (2) building a sense of loyalty, commitment, and effectiveness necessary for shared decision making; and (3) creating an environment where risk-taking is encouraged, supported, and reinforced.

3.0 SCOPE

3.1 DoDEA requires virtual support for its PLC Initiative that consists of (1) a kickoff meeting featuring a nationally recognized PLC expert, (2) individual and small group coaching of principals, (3) semesterly virtual meetings with each school’s professional learning team (a representative team focused on professional learning and student achievement); (4) an archive of recordings and/or modules to provide new teachers and administrators with this training, and (5) training in Option Years 1 and 2 for one coach in each of DoDEA’s three Areas to provide PLC facilitation for new principals and teachers. A nationally recognized expert is a person who is a published and recognized speaker on professional learning communities.

3.2 DoDEA plans to have a three-year rollout that will include all schools each year.

4.0 REQUIREMENT

4.1 General—The Contractor shall:

4.1.1 Use strategies and materials that promote PLC development based on the six characteristics listed in PWS 2.4.

4.1.2 Use a common and consistent vocabulary to address PLC implementation.

4.1.3 Provide a systemic approach for principals and professional learning teams to build PLCs in each school systemwide.

4.1.4 Provide facilitation/coaching in the U.S. Eastern Standard, European, and Pacific (that is, the Guamanian, Korean, Japanese) time zones to permit real-time interaction among participants.

4.2 Kickoff Meeting—The Contractor shall:

4.2.1 Plan: Provide a draft plan for the kickoff meeting to include the name of a nationally recognized PLC expert as the keynote speaker by July 1 of each year. Based on written feedback from the Contracting Officer’s Representative (COR) provided within ten days of receipt of the draft plan, submit a final plan electronically on August 1 of each year.

4.2.2 Base Year: Provide an introductory meeting to outline the key components of the PLC purpose for impacting student achievement, the PLC process, implementation steps, and exemplars of PLC success for educators and student success.

4.2.3 Option Years: Provide a meeting that focuses on DoDEA’s PLC process with the purpose of celebrating innovative PLC practices in DoDEA, applauding PLC-driven high levels of student results, and guiding DoDEA schools to a higher level of implementation.

4.2.4 Provide the kickoff meetings at a mutually agreed upon time in the first or second week of September each year. Each year the keynote address of the nationally recognized expert shall last approximately 90 minutes with a 10-minute intermission. The entire meeting shall last four hours. The keynote speaker shall attend the entire meeting.

4.2.5 Record the meeting for use by DoDEA leaders and schools to further knowledge, discussions, and for anyone not in attendance.

4.3 Individual and Small Group Coaching of Principals—The Contractor shall:

4.3.1 Small Group Coaching Plan

Provide a draft plan to ensure systemwide consistency in the instructional portion of the small group meetings. At the post-award conference, the contracting officer’s representative (COR) will provide the Contractor with a preliminary list showing the preferred virtual medium for each small group.

The plan shall include the selection criteria for coaches.

The plan shall not address individual coaching except to state that the coach and principal will determine the topic(s) to be addressed.

The final plan shall be provided after receipt of written feedback from the COR provided within ten days of receipt of the draft plan.

The principal small group coaching session shall not exceed one hour in length.

4.3.2 Provide six small group principal meetings in the base year. Each meeting shall not exceed one hour in length. For all schools the meetings will occur at a time agreed upon by the principals in each small group in the last week of the following months:

September, October, November, February, March, and April.

The number of small groups is shown by district in the table below.

The COR will provide the exact principal names and contact information for each group at the post-award conference.

The coach and the group of principals will determine the exact dates and times for the meetings. The Contractor shall provide each school’s meeting schedule to the COR at least one month in advance of their occurrence.

4.3.3 Provide a written report to the COR ten days after each meeting that includes the date, time, Districts ES MS HS Unit* Total Enrollment** Est. # of

Small Groups

DDESS

Area***

Camp Lejeune

5 1 1 0 7 3,282 1

Fort Bragg 9 2 0 0 11 5,146 2 Georgia/ Alabama

8 1 0 1 10 3,920 2

Kentucky 12 3 2 0 17 6,780 3

NY/VA/

Puerto Rico 5 2 1 3 11 3,890 2

SC/Ft.

Stewart/Cuba

7 0 0 2 9 3,952 2

Europe Area Bavaria 10 1 5 4 20 7,858 3

Isles 10 1 1 3 15 5,349 3 Kaiserslautern 11 5 4 2 22 11,636 4 Mediterranean 6 1 1 10 18 6.342 3 Pacific Area

Guam 1 1 1 1 4 2,431 1 Japan 12 3 3 3 21 8,428 3 Korea 4 1 3 4 12 5,082 2

Okinawa 8 3 2 0 13 7,673 2

* Unit schools are either K-8, 6-12, or K-12 schools.

** Enrollment data as of October 4, 2013 *** Not included on this list is the virtual school with one principal but hubs in the US, Europe, and Pacific. All virtual students are enrolled at a DoDEA school.

Total # of Small Groups attendance, summary of the training, summary of the discussion, and ideas for the next meeting.

The Contractor shall propose and the COR will finalize the format of the report.

4.3.4 Individual Coaching

Provide the same coach to lead and support both the small group coaching of principals and the individual coaching, unless written authorization from the COR is received to have different coaches.

Utilize videoconferencing for the coaching sessions. If the DoDEA principal does not have videoconferencing capability, a mutually agreed upon medium shall be used.

Provide five calls lasting up to one hour each per principal in the base year and two calls lasting up to one hour each per principal in each option year.

4.4 Bi-Semester Meetings with each School-Based Professional Learning Community—The Contractor shall:

4.4.1 Provide a draft plan and agenda to guide/ensure consistency in the instructional portion of semester meetings systemwide. The plan shall include:

An initial PLC meeting focused on vetting norms, creating goals, and developing accountability.

Virtual medium through which each meeting will occur. At the post-award conference, the contracting officer’s representative (COR) will provide the Contractor with a preliminary list showing the preferred virtual medium for each small group.

Provide a final plan and agenda based on written feedback from the COR.

4.4.2 Provide each school with four one-hour facilitated PLC meetings each year on a schedule designed by the Contractor and finalized by the COR. The meetings are to support implementation of PLC at the building level. Each PLC is comprised of representative faculty and leadership across the school. The purpose of the team is to lead, guide, and support the PLC implementation. The selection criteria shall be the same as those in 4.3.1.

4.4.3 Provide a written report to the COR after each meeting that includes the date, time, attendance, summary of the training, summary of the discussion, and ideas for the next meeting. The Contractor shall propose and the COR will finalize the format of the reports.

4.5 Archived Trainings and Reports—The Contractor shall:

4.5.1 Record the kickoff meetings each year for DoDEA schools and leadership use and the bi-semester meetings with PLCs systemwide. The unedited recordings will be provided to DoDEA to place on a password-protected portion of its website.

4.5.2 Create a frequently asked question report with answers based on the questions that arise in the small group coaching of principals, individual coaching, and bi-semester meetings.

4.5.3 DoDEA shall possess exclusive ownership of archived training recordings and reports delivered under this contract.

4.6 Option Years 1 and 2 Only—Area PLC Coaching—The Contractor shall:

4.6.1 Provide a draft plan to provide virtually delivered training to all new principals in becoming proficient in leading their school’s PLC initiative by Area. The selection criteria for the Area PLC coaches shall be the same as those in 4.3.1. Provide a final plan after receipt of written feedback from the COR.

4.6.2 Deliver the agreed upon training in eight one-hour sessions in real-time. The sessions will occur in September, October, November, January, February, and March on a schedule that will be provided to the Contractor by the COR in August.

4.6.3 Provide an evaluation of the meetings in a format that will be established post-award by the Contractor with input and final approval by the COR.

4.7 Technical Support—For the kickoff meetings, small group coaching, and semester meetings, the Contractor shall provide real-time IT support to solve or to work with DoDEA IT staff to solve connectivity and related issues that arise from the Contractor’s site.

4.8 Status Updates—The Contractor shall provide a monthly status report via email to the COR. The report shall be in a mutually agreed upon format that includes the dates and times of each individual and group meeting as well as the names of each facilitator and attendee at each individual and group meeting.

5.0 TECHNICAL REQUIREMENTS

5.1 All online resources and instructional software shall meet DoDEA information security requirements (as defined below), such as not containing vulnerabilities posing risk to the network. All software and websites shall undergo preliminary testing to ensure that they pose no security risk to the DoDEA infrastructure. Any IT component of the Contractor’s proposal that fails to meet DoDEA’s information security and technology requirements will be excluded from further evaluation.

5.2 All software/Plugins/Add-ons shall meet DoDEA’s following requirements:

5.2.1 DoD Information Assurance Certification and Accreditation Process (DIACAP) [Accreditation Process (DIACAP), 28 November 2007, which may be found at the following URL: http://www.dtic.mil/whs/directives/corres/pdf/851001p.pdf].

5.2.2 Security Technical Information Guidance (STIG), which may be found at the following URL: http://iase.disa.mil/stigs/stig/index.html.

5.2.3 The Contractor shall provide security patches and upgrades, to include third-party applications, in response to public released security vulnerabilities associated with their software solution. Any deviations from this requirement (paragraph 5.2) shall be approved in writing by the DoDEA Chief Information Officer (CIO).

5.3 Contractor software solutions shall not interfere with other installed software and shall not modify DoDEA’s underlying system security configuration. The Contractor shall develop and provide software upgrades within 30 days of notification should any of the software/plug-ins be found vulnerable and non-compliant with Defense Information Security Agency (DISA) and National Security Agency standards (NSA). Software upgrades and patches shall be included in the licensing cost and performed at the least disruptive times. Any additional software requirements may be subject to the DIACAP process prior to contract award.

5.4 In accordance with its testing criteria, DoDEA requires the use of software which may be installed and/or accessed in a stand-alone environment, network environment or web-based environment that is compatible with standards cited herein. All software shall be completely functional on a standard DoDEA desktop without the need for Administrative-level user rights or a requirement to insert media (CD/DVD) to execute the software. Software shall not require modifications to folder permissions while executing. Additionally, all software shall be compatible with the following hardware baseline:

Specifications Minimum Memory 2GB

Hard Drive 100GB Processor 2.4 GHz

Operating System Windows 7 Pro and Apple MAC

(Lion through Maverick)

5.5 All windows, fly-out menus, etc. shall work from within an environment that blocks popup windows.

Additionally, all web-based software shall not (wherever possible) require the use of streaming videos or downloads, such as Java Applets.

Several DoDEA sites globally are still limited by host country bandwidth. As a result, DoDEA is prudent about the capabilities of these sites when assessing the overall requirements of any proposal.

The Government will carefully consider proposed options based on the nature of each requirement. To facilitate this analysis, the vendor shall cite the estimated per client bandwidth requirements for any proposed transcoded and/or streaming video solution.

5.6 All software packages shall support unattended installation methods used by enterprise software packaging and deployment systems, i.e., Microsoft Systems Management Server. Older 16-bit software shall be closely analyzed against this requirement.

5.7 The Contractor shall deliver any online materials on a web-based platform and provide course or video files in QuickTime, Windows Media and /or Adobe Flash format that are compatible with the hardware and operating system requirements listed in Section 5.4. The software shall run successfully in the existing DoDEA environment.

5.8 The Contractor’s solution shall be robust enough to serve the needs of a large community of learners dispersed across the world using a variety of bandwidths. The Contractor’s solution shall be scalable and able to expand to meet future growth, both in terms of the instruction and the size of the student body.

5.8.1 DoDEA computers include a combination of Windows 7 and Apple Mac Operating System (Lion through Mavericks). The web browsers include a combination of Google Chrome and Internet Explorer 9 (future version 10). Plug-in requirements shall not extend beyond Java, Flash, and Microsoft Silverlight.

5.8.2 Robust environment is meant to imply that the solution, whether stand-alone or web-based, should be capable of running on multiple operating systems and multiple browsers as mentioned above. Understanding that the technological solution is serving a global populous, the system (if web-based) should also be robust enough to accommodate 24/7 connections from hundreds of simultaneous users, if necessary. Due diligent testing should validate the aforementioned requirements as well.

Cloud-based hosted solutions additionally require supplemental scrutiny, reviews, and authorizations from the Department of Defense and DoDEA’s Chief Information Officers.

Premise-based solutions are preferred, wherever possible. Premise-based solutions, whether web- or client-based, shall also be updated/deployed by the DoDEA Information Technology Offices, rather than the vendors themselves.

The vendor is responsible for providing the updates and patches as necessary for a standardized version of the software proposed.

5.8.3 Any portion of the Contractor's solution that involves Internet access by DoDEA students has a duty to comply with the relevant requirements of the Children's Internet Protection Act, Pub.L. 106-554, § 1(a)(4) [Div. B, Title XVII, § 1701], Dec. 21, 2000, 114 Stat.

2763, 2763A-335. Any part of the Contractor's solution that collects or stores agency-owned or agency-controlled personally identifiable information has a duty to do so in accordance with the relevant requirements of the Privacy Act, 5 U.S.C. § 552a. (See http://www.archives.gov/about/laws/privacy-act-1974.html.) Contractor solutions that collect information from children under the age of 13 through the Internet has a duty to comply with the relevant requirements of the Children's Online Privacy Protection Act, 15 U.S.C.A. § 6501 et seq.

5.8.4 Any opportunity for data integration of student or teacher accounts shall adhere to the Federal Government and DoD guidance for security of personally identifiable information available from the following URLs:

http://www.justice.gov/opcl/privstat.htm http://www.whitehouse.gov/omb/memoranda/fy2007/m07-16.pdf http://www.dtic.mil/whs/directives/corres/pdf/540011p.pdf.

All Contractor staff that has access to DoDEA student and/or teacher personally identifiable information shall take the DoD Privacy Act/Personally Identifiable Information (PA and PPI/PII) training before gaining access to the data and yearly thereafter. DoDEA contractors who have a DoDEA username and password may access the training on DoDEA's intranet. All other contractors shall access the PA and PPI/PII slides, a link to which found on DoDEA's homepage (www.dodea.edu). Contractors shall send written confirmation listing the staff members that have taken the mandatory PA and PPI/PII training to the Contracting Officer's Representative.

5.9 Maintenance and support shall be available for the duration of the contract. Maintenance is defined as automatic distribution of upgrades and revisions that can be accomplished using a combination of Internet and or email. Any upgrades to online digital materials shall include compatibility with DoDEA school-level technology and Department of Defense’s (DoD) information technology requirements. The Contractor shall not contact schools directly but shall coordinate the dissemination of upgrades or revisions through the COR and shall provide electronic access of the update and/or revision to the COR for testing.

5.10 The Contractor may be required to sign Non-Disclosure Agreements (NDA), which prohibits the disclosure, publishing, divulgence, or release of any information obtained during the performance of the contract.

6.0 DELIVERY SCHEDULE—The Contractor shall:

6.1 Post-Award Conference: Participate in a post-award face–to-face or telephonic conference at which DoDEA staff and the Contractor will review the contract.

6.2 Delivery of Kickoff Meetings—The Contractor shall:

6.2.1 Draft Plan: Submit a proposed agenda for each kickoff meeting to the COR electronically on or about July 1 of each year, per PWS 4.2.1.

6.2.2 Final Plan: Based on written feedback from the COR provided within ten business days of receipt of the draft plan, the Contractor shall provide a final agenda to the COR electronically on or about August 1 of each year, per PWS 4.2.1.

6.2.3 Deliver the kickoff meeting at the mutually agreed upon time and date in the first or second week of September of each year, per PWS 4.2.2, 4.2.3 and 4.2.4.

6.3 Delivery of Individual and Small Group Coaching—The Contractor shall:

6.3.1 Draft Plan: Submit a draft plan for the individual and small group coaching to the COR electronically by July 30, per PWS 4.3.1.

6.3.2 Final Plan: Based on written feedback from the COR provided within ten business days of receipt of the draft plan, the Contractor shall provide a final plan to the COR electronically by August 30, per PWS 4.3.1.

6.3.3 Small Group Coaching: Provide coaching, per PWS 4.3.2.

6.3.4 Small Group Coaching Report: Provide report electronically to the COR no later than ten days after each coaching session, per PWS 4.3.3.

6.3.5 Individual Coaching: Provide coaching, per PWS 4.3.4.

6.4 Bi-Semesterly Meetings with PLCs—The Contractor shall:

6.4.1 Draft Plan: Submit a proposed plan for each semester meeting to the COR electronically by June 30 of the base year and by September 15 of each option year, per PWS 4.4.1.

6.4.2: Final Plan: Based on written feedback from the COR provided ten business days after receipt of the draft plan, the Contractor shall provide a final plan to the COR electronically by July 30 of the base year and by October 15 of each option year, per PWS 4.4.1.

6.4.3 Bi-Semester Meetings: Provide each school with four one-hour meetings per year, per PWS 4.4.2. The COR will provide the Contractor with the schedule for these meetings which will occur in November and March of each year.

6.4.4 Report: Provide a report electronically to the COR ten days after each meeting, per PWS 4.4.3.

6.5 Delivery of Archived Training and Reports—The Contractor shall:

6.5.1 Recordings: Provide recordings of the kickoff meetings and the bi-semester meetings with PLCs systemwide no later than two weeks after each meeting, per PWS 4.5.1.

6.5.2 Frequently Asked Questions: Based on the small group coaching, individual coaching, and bi-semester meetings, the Contractor shall provide a list of frequently asked questions and answers to the COR electronically by January 15 and June 15 of each year, per PWS 4.5.2.

6.6 Option Year 1 and 2 Only: Area PLC Coaching—The Contractor shall:

6.6.1 Draft Plan: Submit a proposed plan for Area PLC Coaching to the COR electronically by June 30 of each option year, per PWS 4.6.1

6.6.2 Final Plan: Based on written feedback from the COR provided ten business days after receipt of the draft plan, the Contractor shall provide a final plan to the COR electronically by July 30, per PWS 4.6.1.

6.6.3 Coaching: Provide coaching, per PWS 4.6.2.

6.6.4 Evaluation: Provide an evaluation of the meetings three weeks after the sixth meeting at each site (as listed in PWS 4.3.2) in a format that will be determined post-award.

6.7 Technical Support: Provide technical support to ensure that participants can access the virtual kickoff meeting and small group coaching, per PWS 4.7.

6.8 Status Updates: Provide reports, per PWS 4.8, on the last business day of each month beginning in August 2014.

7.0 PERFORMANCE AND DELIVERY SCHEDULE

7.1 The Contractor shall furnish all services to be performed and all items to be delivered in accordance with the following delivery schedule:

Year Task Ref Timeline

Base Year

Post-Award Conference 6.1 Ten days after award

Kickoff Meeting Draft Plan Final Plan

Delivery

6.2

Draft plan due by July 1 Final plan due by August 1 Deliver meeting - first or second week of Sept

Small Group Coaching Draft Plan Final Plan Schedule

Coaching

Report

6.3

Draft plan due July 30 Final plan due August 30 Provide meeting schedule to the COR one month prior to each meeting.

Provide coaching, per 4.3.2.

Report due ten days after each coaching session

Individual Coaching 6.3 Times mutually agreed upon by the facilitator and each principal

Bi-Semester Meetings with PLCs

Draft Plan 6.4

Draft plan due by June 30

Year Task Ref Timeline

Delivery

Report

Final Plan due by July 30 Deliver training as scheduled Report due ten days after each meeting

Archived Training 6.5 Recordings submitted to DoDEA NLT two weeks after each meeting/session.

Frequently Asked Questions

6.5 Draft presented to the COR NLT 15 Jan and NLT 15 Jun

Technical Support 6.7 Available for the kickoff meeting and each small group coaching session worldwide

Status Updates 6.8 Provide status updates on the last business day of each month beginning after the post-award conference.

Option Years 1 & 2

Kickoff Meeting Draft Plan Final Plan

Delivery

6.2

Draft plan due by July 1 Final plan due by August 1 Deliver meeting - first or second week of Sep

Individual Coaching 6.3 Times mutually agreed upon by the facilitator and each principal

Bi-Semester Meetings with PLCs

Draft Plan Final Plan

Delivery Report

6.4

Draft plan due by September 15 Final Plan due by October 15 Deliver training as scheduled Report due ten days after each meeting

Archived Training 6.5 Recordings submitted to DoDEA NLT two weeks after each meeting/session

Frequently Asked Questions

6.5 Draft presented to the COR NLT 15 Jan and NLT 15 Jun

Area PLC Coaching Draft Plan Final Plan

Delivery Evaluation

6.6

Draft plan due by June 30 Final Plan due by July 30 Deliver training as scheduled Three weeks after the sixth session in a format that will be determined post-award.

Technical Support 6.7 Available for the kickoff meeting and each semester PLC meeting worldwide

Status Updates 6.8 Deliver reports as scheduled.

PERFORMANCE REQUIREMENTS SUMMARY

Required Reports Measurement Acceptable

Quality Levels Format

& Copies

PWS 4.2

Draft Agendas of Base and Option Year Kickoff Meetings

Includes all components, per PWS 4.2.2 in base year and PWS

4.2.3 in option years.

Draft: 90% Final: 100%, except minor grammatical errors

Electronic copy

PWS 4.3

Small Group Coaching of Principals

Reports

Draft: Includes all/selected components, per PWS 2.4 and 4.3.

Final: Includes revisions provided by COR Per format provided by COR

90% 100%, except minor grammatical errors 100%, except minor grammatical errors

Electronic copy

PWS 4.4

Bi-Semester Meetings with PLCs

Reports

Draft: Includes all/selected components, per PWS 2.4 and 4.4.

Final: Includes revisions provided by COR Per format provided by COR

90% grammatical errors 100%, except minor grammatical errors

Electronic copy

PWS 4.5.1

Archived Kickoff and other Meetings

Unedited recordings 100% Electronic copy

PWS 4.5.2

Frequently Asked Questions

Draft provided each semester grammatical errors

Electronic copy

PWS 4.6

Area Coaching

Evaluation provided three weeks after sixth session in a format provided by the COR

100%, except minor grammatical errors

Electronic copy

PWS 4.8

Status Updates

All reports accurately depict current status, per PWS 4.8

100%, except minor grammatical errors

Electronic copy

(END OF ATTACHMENT A)

ATTACHMENT B: CONTRACT LINE ITEM (PRICING) SCHEDULE

Contract Line

Item# Item Description Qty Unit Unit Price Total Price

0001 Kickoff Meeting 1 Each $ $

Group Principal Coaching (33 groups x 6 meetings = 198)

198 Each

Individual Principal Coaching (189 principals x 5 calls = 945 calls)

945 Each

0004 Frequently Asked Questions (FAQ) 2 Each $ $

Bi-Semester PLC Coaching (189 schools x 4 meetings = 756 meetings)

756 Each

0007 Technical Support 1 Year NSP NSP 0008 Status Updates 1 Year NSP NSP Base Year Total $

1001 Kickoff Meeting 1 Each $ $

Individual Principal Coaching (189 principals x 2 calls = 378 calls)

378 Each

1004 Frequently Asked Questions (FAQ) 2 Each $ $

Bi-Semester PLC Coaching (189 schools x 4 meetings = 756 meetings)

756 Each

1006 Area PLC Facilitators Coaching Sessions 8 Each $ $

1007 Technical Support 1 Year NSP NSP 1008 Status Updates 1 Year NSP NSP Option Year One Total $

2001 Kickoff Meeting 1 Each $ $

Individual Principal Coaching (189 principals x 2 calls = 378 calls)

378 Each

2004 Frequently Asked Questions (FAQ) 2 Each $ $

Bi-Semester PLC Coaching (189 schools x 4 meetings = 756 meetings)

756 Each

2006 Area PLC Facilitators 8 Each $ $

2007 Technical Support 1 Year NSP NSP 2008 Status Updates 1 Year NSP NSP Option Year Two Total $

Base & Option Years Total $

(END OF ATTACHMENT B)

ATTACHMENT C: GOVERNMENT PRODUCT ACCESSIBILITY TEMPLATE (GPAT)

Summary Column one includes all the Sections of the Standard that may apply to any deliverable. The total number of provisions within each Section of the Standard is shown in parentheses.

Column two identifies the total number of provisions that typically apply to a deliverable of this type. Some of these may not be features of the vendor’s deliverable. Conversely, others not noted may be features of the vendor’s deliverable. If the deliverable includes additional features, the accessibility of these features must also be considered.

Column three is for general notes about the Sections of the Standard. Some apply to all deliverables and some are specific to the deliverable.

Column four is a summary of the vendor’s response to applicable provisions and additional deliverable features from the Sections of the Standard.

Column five is where the vendor can note explanations for any of the preceding columns, e.g. there are differences between expected applicable provisions and actual product features.

CFR 1194

Standard Sections

Total

Number of

Applicable

Provisions

Notes

Total Number of

Supported

Provisions Please explain

Fully Partial Not

Section 1194.21

Software

Applications and

Operating Systems

(12 provisions)

This Section applies because web‐based training typically includes browsers, plug‐ins, extensions, etc which are software applications.

Section 1194.22

Web‐based Internet

Information and

Applications

(16 provisions)

This Section applies to Web as the means of delivering training.

Total

Number of

Applicable

Provisions

Notes

Total Number of

Supported

Provisions Please explain

Fully Partial Not

Section 1194.23

Telecommunications

Products

(14 provisions)

If VoIP or other means of telecommunications services are provided provisions c, d, e, and j would apply.

Section 1194.24

Video and Multi‐ media Products

(5 provisions)

This Section applies if video and multimedia are used to deliver training.

Section 1194.25

Self‐Contained, Closed Products

(13 provisions)

Section 1194.26

Desktop and

Portable Computers

(4 provisions)

Section 1194.31

Functional

Performance

Criteria

(6 provisions)

Functional performance criteria always apply.

Total

Number of

Applicable

Provisions

Notes

Total Number of

Supported

Provisions Please explain

Fully Partial Not

Section 1194.41

Information, documentation, and support

(3 provisions)

If information, documentation, and support are to be provided by the vendor, then this

Section applies.

Subpart B ‐‐ Technical Standards Note: If there is a possibility that the provision applies, the default value is “Yes”.

Column one is the full text of the provision from the Standard.

Column two documents the agency’s accessibility requirement based on common characteristics of the EIT deliverable. Place a Yes or No in this column based on program need and actual characteristics of your expected deliverable (i.e., Is this provision seen as applicable to the expected deliverable?)

Column three provides explanatory information about the provision to help both the agency in determining applicability and the vendor in providing accessibility information.

Column four is for the vendor to check off whether the deliverable meets, partially meets or does not meet the specific provision.

Column five is for the vendor to provide an explanation of how the deliverable meets or does not meet the specific provision. It is also an opportunity to explain why a deliverable does not have an applicable feature or why it has a feature that was not identified as applicable.

Section 1194.21 Software applications and operating systems

Provision Text Applicab le Notes

How does the

EIT meet this requirement?

Please explain le Notes

How does the

EIT meet this requirement?

Please explain

(a) When software is designed to run on a system that has a keyboard, product functions shall be executable from a keyboard where the function itself or the result of performing a function can be discerned textually.

Yes

This applies to

QWERTY keyboards.

__Fully

__Partially

__No

(b) Applications shall not disrupt or disable activated features of other products that are identified as accessibility features, where those features are developed and documented according to industry standards.

Applications also shall not disrupt or disable activated features of any operating system that are identified as accessibility features where the application programming interface for those accessibility features has been documented by the manufacturer of the operating system and is available to the product developer.

Yes

__Fully le Notes

How does the

EIT meet this requirement?

Please explain

(c) A well‐defined on‐screen indication of the current focus shall be provided that moves among interactive interface elements as the input focus changes. The focus shall be programmatically exposed so that Assistive

Technology can track focus and focus changes.

(d) Sufficient information about a user interface element including the identity, operation and state of the element shall be available to Assistive

Technology. When an image represents a program element, the information conveyed by the image must also be available in text.

(e) When bitmap images are used to identify controls, status indicators, or other programmatic elements, the meaning assigned to those images shall be consistent throughout an application's performance.

Yes

In this requirement, the term “bitmap” refers to a broad number of image formats, such as

.bmp, .gif, .jpeg, .tif and .svg.

le Notes

How does the

EIT meet this requirement?

Please explain

(f) Textual information shall be provided through operating system functions for displaying text. The minimum information that shall be made available is text content, text input caret location, and text attributes.

(g) Applications shall not override user selected contrast and color selections and other individual display attributes.

(h) When animation is displayed, the information shall be displayable in at least one non‐animated presentation mode at the option of the user.

Yes

Self‐scrolling and moving text are considered animation.

__Fully

(i) Color coding shall not be used as the only means of conveying information, indicating an action, prompting a response, or distinguishing a visual element.

Yes

This requirement is also addressed in provision

1194.25(g).

__Fully le Notes

How does the

EIT meet this requirement?

Please explain

(j) When a product permits a user to adjust color and contrast settings, a variety of color selections capable of producing a range of contrast levels shall be provided.

Yes

See www.lighthouse.org

/color_contrast.htm

This requirement is also addressed in provision

1194.25(h).

__Fully

(k) Software shall not use flashing or blinking text, objects, or other elements having a flash or blink frequency greater than 2 Hz and lower than 55 Hz.

Yes

Other elements include turning graphics on and off or changing between images.

This requirement is also addressed in provisions

1194.22(j) and

1194.25(i).

__Fully

(l) When electronic forms are used, the form shall allow people using Assistive

Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Yes

This requirement is also addressed in provision

1194.22(n).

__Fully

Section 1194.22 Web‐based intranet and internet information and applications

Provision Text Applica ble

Notes

requiremen t?

Please explain

(a) A text equivalent for every non‐text element shall be provided (e.g., via

“alt”, “longdesc”, or in element content).

(b) Equivalent alternatives for any multimedia presentation shall be synchronized with the presentation.

(c) Web pages shall be designed so that all information conveyed with color is also available without color, for example from context or markup.

(d) Documents shall be organized so they are readable without requiring an associated style sheet.

(e) Redundant text links shall be provided for each active region of a server‐ side image map.

Yes

__Fully

(f) Client‐side image maps shall be provided instead of server‐side image maps except where the regions cannot be defined with an available geometric shape.

Provision Text Applica ble

Notes

requiremen t?

Please explain

(g) Row and column headers shall be identified for data tables.

Yes

__Fully

(h) Markup shall be used to associate data cells and header cells for data tables that have two or more logical levels of row or column headers.

(i) Frames shall be titled with text that facilitates frame identification and navigation

(j) Pages shall be designed to avoid causing the screen to flicker with a frequency greater than 2 Hz and lower than 55 Hz.

Yes

This requirement is also addressed in provisions

1194.21(k) and

1194.25(i).

__Fully

(k) A text‐only page, with equivalent information or functionality, shall be provided to make a web site comply with the provisions of this part, when compliance cannot be accomplished in any other way. The content of the text‐only page shall be updated whenever the primary page changes.

Yes

This should only be used as a last resort.

Provision Text ble

Notes

requiremen t?

Please explain

(l) When pages utilize scripting languages to display content, or to create interface elements, the information provided by the script shall be identified with functional text that can be read by

Assistive Technology.

(m) When a web page requires that an applet, plug‐in or other application be present on the client system to interpret page content, the page must provide a link to a plug‐in or applet that complies with

Section1194.21(a) through

(l).

(n) When electronic forms are designed to be completed on‐line, the form shall allow people using Assistive Technology to access the information, field elements, and functionality required for completion and submission of the form, including all directions and cues.

Provision Text ble

Notes

requiremen t?

Please explain

(o) A method shall be provided that permits users to skip repetitive navigation links.

(p) When a timed response is required, the user shall be alerted and given sufficient time to indicate more time is required.

Yes

This requirement is also addressed in provision

1194.25(b).

__Fully

Section 1194.23 Telecommunications products

Provision Text Applica ble

Notes

requiremen t?

Please explain

(a) Telecommunications products or systems which provide a function allowing voice communication and which do not themselves provide a TTY functionality shall provide a standard non‐acoustic connection point for TTYs.

Microphones shall be capable of being turned on and off to allow the user to intermix speech with TTY use.

No

Provision Text ble

Notes

requiremen t?

Please explain

(b) Telecommunications products which include voice communication functionality shall support all commonly used cross‐ manufacturer non‐ proprietary standard TTY signal protocols.

(c) Voice mail, auto‐ attendant, and interactive voice response telecommunications systems shall be usable by

TTY users with their TTYs.

(d) Voice mail, messaging, auto‐attendant, and interactive voice response telecommunications systems that require a response from a user within a time interval, shall give an alert when the time interval is about to run out, and shall provide sufficient time for the user to indicate more time is required.

(e) Where provided, caller identification and similar telecommunications functions shall also be available for users of TTYs, and for users who cannot see displays.

Provision Text ble

Notes

requiremen t?

Please explain

(f) For transmitted voice signals, telecommunications products shall provide a gain adjustable up to a minimum of 20 dB. For incremental volume control, at least one intermediate step of 12 dB of gain shall be provided.

(g) If the telecommunications product allows a user to adjust the receive volume, a function shall be provided to automatically reset the volume to the default level after every use.

(h) Where a telecommunications product delivers output by an audio transducer which is normally held up to the ear, a means for effective magnetic wireless coupling to hearing technologies shall be provided.

Provision Text ble

Notes

requiremen t?

Please explain

(i) Interference to hearing technologies (including hearing aids, cochlear implants, and assistive listening devices) shall be reduced to the lowest possible level that allows a user of hearing technologies to utilize the telecommunications product.

(j) Products that transmit or conduct information or communication, shall pass through cross‐ manufacturer, non‐ proprietary, industry‐ standard codes, translation protocols, formats or other information necessary to provide the information or communication in a usable format. Technologies which use encoding, signal compression, format transformation, or similar techniques shall not remove information needed for access or shall restore it upon delivery.

Provision Text ble

Notes

requiremen t?

Please explain

(k)(1) Products which have mechanically operated controls or keys shall comply with the following:

Controls and Keys shall be tactilely discernible without activating the controls or keys.

(k)(2) Products which have mechanically operated controls or keys shall comply with the following:

Controls and Keys shall be operable with one hand and shall not require tight grasping, pinching, twisting of the wrist. The force required to activate controls and keys shall be 5 lbs. (22.2N) maximum.

(k)(3) Products which have mechanically operated controls or keys shall comply with the following:

If key repeat is supported, the delay before repeat shall be adjustable to at least 2 seconds. Key repeat rate shall be adjustable to 2 seconds per character.

Provision Text ble

Notes

requiremen t?

Please explain

(k)(4) Products which have mechanically operated controls or keys shall comply with the following:

The status of all locking or toggle controls or keys shall be visually discernible, and discernible either through touch or sound.

Section 1194.24 Video and multimedia products

Provision Text Appli cable

Notes

requiremen t?

Please explain

(a) All analog television displays 13 inches and larger, and computer equipment that includes analog television receiver or display circuitry, shall be equipped with caption decoder circuitry which appropriately receives, decodes, and displays closed captions…