Expedited RFQ Scoring Matrix

Commonwealth of Pennsylvania Master Information Technology (IT) Services Invitation to Qualify (ITQ) Contract, 4400004480

Educator Dashboard Enhancements Phase 1 Solicitation Number: 6100039873 Not to exceed $165,000.00

August, 24 2016

The Pennsylvania Department of Education, Center for Data Quality & Information Technology (CDQ&IT) has posted solicitation #6100039873 for Educator Dashboard Enhancements Phase 1. Please go to the eMarketplace Website to view and download all documentation pertaining to this solicitation.

This is a restricted solicitation, only contractors which are qualified in one (1) or more of the following service category(ies) under the Commonwealth’s Master Information Technology (IT) Services Invitation to Qualify (ITQ), Contract 4400004480, prior to the bid opening date may respond.

 Software Development Services

Organizations interested in doing business with the Commonwealth through this contract must begin by registering with the Commonwealth as a Procurement Supplier. For more information about registration, please view the Registration Guide.

Once an organization is registered with the Commonwealth, they must develop and submit a bid through the PASupplierPortal Website in order to qualify for one, all, or any combination of the service categories associated with this contract. The Commonwealth will evaluate the bid along with all supporting documentation to determine whether the organization meets the minimum eligibility requirements.

For more information about the Commonwealth’s Invitation to Qualify contracts and their policies, please visit the ITQ Website.

1 Pennsylvania Department of Education 333 Market Street Harrisburg, PA 17101

The attached Statement of Work (SOW) is provided for you to develop your bid for the referenced IT Project. The successful contractor will be selected based on Best Value. The Best Value Criteria specified below defines the criteria that will be used to determine the successful contractor to be awarded the Purchase Order. It is imperative that you expound in writing on each of the best value criteria listed. You may complete your bid on this form and respond by reply email no later than 3:00pm on September 15, 2016.

Best Value Criteria:

1. Understanding the Problem: Provide a brief narrative (one paragraph) that accurately assesses the problem to be solved based on your understanding of the project requirements stated in the SOW.

2. Contractor Prior Experience: Experience shown should be work done by individuals who will be assigned to this project as well as that of your company. Studies or projects referred to must be identified and the name of the customer shown, including the name, address, and telephone number of the responsible official of the customer, company, or agency who may be contacted.

Contractors must provide at least three (3) customer references for projects similar to this Project using Appendix F, Project References. To the extent possible, references should be selected to represent projects of similar size and complexity to the project described in this RFQ. The Commonwealth at its sole discretion may request references from any or all proposed subcontractors. Experience shown should be work done by individuals who will be assigned to this project as well as that of your company. Studies or projects referred to must be identified and the name of the customer shown, including the name, address, telephone number, and email address of the responsible official of the customer, company, or agency who may be contacted.

Include experience in the following (All required unless otherwise noted):  A statewide Ed-Fi educator dashboard implementation  Successfully upgrading Ed-Fi to a newer version.  eScholar CDW preferred but not required.

2  Advanced experience with SSIS and SQL Server 2012.  Demonstrated experience with developing applications using Microsoft Visual Studio 2010, C#; ASP.net  Demonstrated experience with SQL server, including SSIS.  Demonstrated experience with Team Foundation Server (TFS) automated build, requirements management, testing management, and issue/bug resolution management.

3. Contractor Personnel and Qualifications: Include the number of executive and professional personnel, analysts, developers, testers, consultants, etc., who will be engaged in the work. For key personnel, include the employee’s name and, through a resume or similar document, the Project personnel’s education and experience in developing and deploying business intelligence dashboards and databases. Indicate the responsibilities each individual will have in this Project and how long each has been with your company. Identify by name any subcontractors you intend to use and the services they will perform. Please complete Appendix G, Proposed Personnel Reference and Appendix H Personnel Experience by Key Position for each of the key personnel being proposed. Do not provide representative resumes.

Refer to the (SOW) for a complete list of staffing requirements.

At the Commonwealth’s sole discretion, additional resources may be requested.

Indicate the responsibilities each individual will have in this Project and how long each has been with your company. Identify by name any subcontractors you intend to use and the services they will perform.

Resumes are not to include personal information that will, or will be likely to, require redaction prior to release of the proposal under the Right to Know Law. This includes home addresses and phone numbers, Social Security Numbers, Drivers’ License numbers or numbers from state ID cards issued in lieu of a Drivers’ License, financial account numbers, etc. If the Commonwealth requires any of this information for security verification or other purposes, the information will be requested separately and as necessary.

The Commonwealth must approve all key personnel appointments and replacements prior to those individuals being assigned to the Commonwealth account throughout the term of this contract; this includes subcontractors.

In the event that PDE requests removal of specific personnel, the Selected Offeror shall provide acceptable replacement(s) with no impact to the project. Replacement(s) shall have qualifications which meet or exceed the original staff member proposed or the staff member holding the position previously and shall be approved by PDE.

3 4. Project Work Plan: Describe in narrative form your technical plan and draft project plan for accomplishing the work. Use the task descriptions in the (SOW) of this RFQ as your reference point. Modifications of the task descriptions are permitted; however, reasons for changes should be fully explained. Indicate the number of person hours allocated to each task. Include a Program Evaluation and Review Technique (PERT) or similar type display, time related, showing each event. If more than one approach is apparent, comment on why you chose this approach.

5. Cost: Complete the attached Cost Matrix Appendix C to submit the cost portion of your bid.

If you are selected for award, you may be required to submit an engagement letter that further details how you propose to meet the requirements stated in the RFQ. Any questions on this RFQ may be sent to: Jim Domen / 717-525-5980 / [email protected]

4 Educator Dashboard Enhancements Phase I Statement of Work

Work Statement

Introduction The Pennsylvania Educator Dashboard Early Warning System (EWS) and Intervention Catalog (IC), launched in 2014, is an Educator- facing Dashboard tool used to provide relevant, timely student education data to assist educators and improve education outcomes for students. The Educator Dashboard is voluntary for LEAs to use and offered at no cost and is maintained by PDE. LEAs that elect to participate will submit existing data from their student information systems into PIMS, PDE’s statewide longitudinal data system (SLDS). PIMS is leveraged as a data collection route for the voluntary Educator Dashboard project. PIMS acts as a clearinghouse to transport the submitted data to the Dashboard. This function is separate from the operational PIMS data collections. The PDE Educator Dashboard is developed upon the backbone of the Ed-Fi dashboard system. The EWS is aligned with best practices and nationally recognized research on dropout identification and prevention. The IC captures information on applicable dropout prevention interventions available through the education community, local county agency programs and partnerships with local businesses. The Dashboard screens display pertinent education information on students, such as attendance, grades and programmatic information, and identify those students considered at risk of dropping out. The PDE Center for Data Quality and Information Technology (CDQIT) and Office of Elementary and Secondary Education (OESE) are seeking a Vendor to implement specific enhancements which are defined within this Statement of Work (SOW) to the Educator Dashboard EWS/IC. The resulting Educator Dashboard will be a robust tool which will allow educators a view into information which can aid in improving student achievement and provide an educational data standard that empowers educators with timely, actionable information on every student in their classroom. PDE will provide the Selected Vendor with access to the Ed-Fi Alliance documentation for use in performing tasks required to accomplish the work outlined in this SOW. Scope This section of the RFQ describes the component and summary tasks to be performed to fulfill the development of production–ready enhancements to Pennsylvania’s Educator Dashboard Early Warning System and Intervention Catalog solution. This SOW covers tasks which will be funded and performed through the SLDS Fiscal Year 2015 Grant.

5 PDE regularly meets with the LEAs using the Dashboard and also the IU partner leads. These meetings allow PDE to understand the issues the LEAs face in using the Dashboard as an instruction support tool. PDE collaborates with these stake holders to steer the strategic planning of future enhancements to the application and training materials. Through these stakeholder and focus group meetings, PDE has determine the need for application enhancements to increase the ease of usability of the Dashboard tool, ability to see additional already supplied SLDS data, and improve training and support materials for the Dashboard and professional development.

The current implementation of PDE’s Educator Dashboard is depicted below:

The PDE Educator Dashboard solution components:

6  PIMS to ODS Extraction-Transformation-Loading (ETL): maps and moves data from PIMS (aka eScholar Complete Data Warehouse) to the Ed-Fi Operational Data Store (ODS).  ODS: the standard Ed-Fi database that allows disparate front end applications to map to the standard Ed-Fi implementation.  ODS ETL to DDS: calculates metrics and moves data from Ed-Fi ODS to Dashboard Data Mart by deploying existing SQL Server Integration Services (SSIS) ETL packages in SQL Server 2012 with Visual Studio 2010 Premium.  SQL Server: Contains Dashboard Data Mart which houses structures and organizes the data to support the user interface.  Team Foundation Server (TFS) Server: Code Repository  Web Server: Host the application website  Load Balancers: Balance web requests between the web servers  Users: The Dashboard User Interface presents the data stored in the Dashboard Data Mart to the end-user

The following functionality is in scope for this project. Educator Dashboard Enhancement Functionality and Development  Upgrade Pennsylvania's Educator  Educator Dashboard (Ed-Fi v1.2.1 to Ed-Fi v 2) Dashboard Solution to newer Ed- Fi version  Ed-Fi ODS v 1.2 to Ed-Fi ODS v 2 See Appendix A-1.

 Dynamic Watch Lists  Implement the Ed-Fi Dynamic Watch List functionality into the Educator Dashboard application, as described in Appendix A-2.  Watch List Enhancements -  Design and develop functionality within the Dashboard application to add a student to a watch list from the student level. See Appendix A-3.

 Intervention Enhancements -  Design and develop functionality within the 7 Dashboard application to send email notifications to the creator of an intervention two weeks prior to the intervention expiration for those interventions that have not been completed. See Appendix A-4.

 Embedded Help  Develop embedded Help functionality within the Dashboard application, as described in Appendix A-5.  External resource and support  Adding links to the Dashboard user interface. links External links include relevant external resource and support materials. See Appendix A-6.

Requirements The Selected Vendor shall be responsible for the configuration and implementation of all of the system components associated with the identified enhancements and must assure the full functionality of the Ed-Fi dashboard modules and EWS/IC components.

Security Requirements The solution must meet or exceed federal and state privacy and security standards, including, but not limited to:

Family Educational Rights and Privacy Act (FERPA) (http://www.ed.gov/policy/gen/guid/fpco/ferpa/index.html)

National School Lunch Act (http://fns.usda.gov/cnd/lunch/)

Protection of Pupil Rights Amendment (PPRA) (http://www.ed.gov/policy/gen/gui/fpco/ppra/omdex.html)

Children’s Online Privacy Protection Act (COPPA) (http://www.ftc.gov/opa/2000/07/coppacompli.shtm)

8 Pennsylvania’s Breach of Personal Information Notification Act (Http://www.schwartzandballen.com/ImportedLawsBills/Pennsyvlania%20Security%20Breach.pdf)

Software Assurance Capability Benchmarking (DHS) (https://buildsecurityin.us-cert.gov/swa/proself_assm.html)

Functional Requirements The Selected Vendor shall implement the requirements for the project enhancements set out in Appendix A – Enhancement Functional Requirements which contains the requirements for the necessary configuration/development of the identified components, Tabs, and Pages for the enhancements of the Educator Dashboard.

Requirements specific to the Dynamic Watch Lists and upgrading to the newer Ed-Fi version can be reviewed at Ed-Fi Alliance http://www.ed-fi.org/tech-docs/ . Additional requirement detail can be found within Tasks and Deliverables.

Performance Requirements Applicable to each enhancement, the average webpage response time (not including network latency) shall be no more than 2 seconds.

Personnel Requirements The Selected Vendor shall have one consultant dedicated to this project full-time, who shall function as the primary technical lead.

1. The proposed Vendor Project Manager shall have a minimum of ten (10) years project management experience, including five years managing projects of similar size and scope deploying MS SQL Server based educator dashboards. PMI PMP certification is desired, but may be replaced by additional experience or other recognized Project Management certification. Two (2) years of experience with K-12 education data related projects. Shall have experience using MS Project 2010. 2. The selected Vendor’s key personnel SQL Server/SSIS Senior Developer shall possess the following minimum experience: a. Two (2) years of experience writing T-SQL stored procedures with Microsoft with SQL Server 2012 b. Two (2) years of experience developing and performance tuning SSIS packages with Microsoft SQL Server 2012 SSIS. c. Five (5) years of experience writing and debugging SSIS programming code in the scripting environment. d. Five (5) years of experience developing and maintaining logical and physical data models. e. Five (5) years of experience using Microsoft Visual Studio in an integrated development environment (IDE)

9 f. Three (3) years of experience with ED-Fi Alliance Dashboard unifying data model, data exchange framework, and application framework. Experience with ED-Fi Alliance dashboard v 2.0 is a plus. 3. The selected Vendor’s Application Developer shall: a. Five (5) years of experience with Object Oriented methodologies and design patterns b. Five (5) years of experience in C#, .NET or other object oriented language. C# strongly preferred. c. Five (5) years ASP.NET MVC web development, Visual Studio 2013 d. Three (3) years Database/SQL experience, SQL Server preferred e. Three (3) JavaScript/JQuery, HTML, CSS. f. Three (3) TFS Automated unit testing, automated build process, code reviews and debugging. g. Experience with Version control systems, specifically TFS and GitHub. 4. The selected Vendor’s testing staff shall possess the following minimum experience: a. Five (5) years of experience writing test plans and test scripts, including regression testing, using UML or similar approved methodology. b. Five (5) years of experience testing dashboards and databases of similar size and scope c. Two (2) years of experience with K-12 education data related projects. d. Two (2) years of experience using TFS to maintain requirements traceability, capture test script development, test execution, and issue and bug fixes. 5. The Commonwealth must approve all key personnel appointments and replacements prior to those individuals being assigned to the Commonwealth account throughout the term of this contract; this includes subcontractors. In the event that PDE requests removal of specific personnel, the Selected Offeror shall provide acceptable replacement(s) with no impact to the project. Replacement(s) shall have qualifications which meet or exceed the original staff member proposed or the staff member holding the position previously and shall be approved by PDE.

Project Execution Requirements

1. General a. The Selected Vendor shall complete all tasks and deliverables as described in Tasks and Deliverables. b. The Selected Vendor shall provide project management services throughout the life of the purchase order. These services include, at a minimum, oversight of Selected Vendor project staff, project communications management, issue management, risk management and change control management, as well as oversight on all project tasks. c. The Selected Vendor shall provide project management related deliverables as specified in, Project Reports and Controls. 2. Deliverable Review and Acceptance process

10 a. The review and acceptance of all deliverables shall be based on the deliverable descriptions and acceptance criteria in the Deliverables Schedule and use the following process: i. PDE and the Selected Vendor shall agree in advance on outlines for all deliverable documents. ii. All deliverables submitted by the Selected Vendor to PDE shall be subject to the review and approval of the PDE Project Manager or his or her designee. iii. The PDE Project Manager will review each deliverable to confirm that the deliverable materially conforms to the acceptance criteria of this SOW and the agreed upon deliverable outline. iv. The PDE Project Manager will have five (5) business days from the date of receipt of a deliverable to complete the review. v. If the deliverable is accepted as a result of the review, the Selected Vendor shall be notified of the acceptance in writing by the PDE Project Manager on or before the fifth (5) business day. vi. If the deliverable or any portion(s) thereof does not comply with the acceptance criteria of the SOW, the PDE Project Manager will notify the Selected Vendor in writing of the deficiencies preventing approval within five (5) business days from the date of receipt of that deliverable. This written notification will identify in reasonable detail the applicable deliverable acceptance criteria in this SOW, all deficiencies, and the corrective actions or changes to be made by the Selected Vendor to make the deliverable conform to such acceptance criteria described below. In the event additional time is required by the PDE Project Manager, then upon the mutual agreement of the parties, the period may be extended for a specific deliverable to 10 business days. vii. The Selected Vendor shall have five (5) business days to complete all such corrective actions or changes for such deliverable to conform to the requirements set forth herein. viii. PDE will have five (5) business days from the resubmission of the deliverable to complete a review of the corrective actions or changes made to the deliverable in response to PDE's written statement of deficiencies and notify the Selected Vendor in writing of acceptance or rejection. PDE’s review and approval of such corrected or changed deliverable shall be solely for the purpose of determining that corrections have been made to bring the deliverable into compliance with the acceptance criteria in this SOW and not for any other purpose, including, without limitation, for format, style or the incorporation of additional ideas or functionality. ix. To the extent that any deliverables are or have been approved by PDE pursuant to this deliverable acceptance process at any stage of the Selected Vendor’s performance under this contract, the Selected Vendor shall be entitled to rely on such approval for purposes of all subsequent stages of the Selected Vendor’s performance. x. Upon PDE’s approval of each deliverable, PDE agrees that in the event of a contradiction between the relevant specifications and the approved deliverable, the contradiction shall be resolved by the approved deliverable.

11 Tasks and Deliverables The Vendor shall be responsible for providing the following deliverables and performing the associated tasks throughout the length of the engagement: Task Task Description Deliverable(s) Deliverable Description Project 1. Develop and deliver for review initial detailed Project Plan. Initial Project Detailed project plan Management 2. Produce weekly status reports to be submitted and reviewed at Plan; should include a each scheduled weekly status meeting. The Weekly Status Weekly Status description of the detailed Report will be submitted and reviewed at each scheduled weekly Report; tasks and their durations, dependencies, responsible status meeting. Updated parties, and percentage Project Plan; 3. Weekly status meetings and capture of meeting minutes complete. delivered to all attendees of the meeting Meeting Minutes 4. Update and deliver project plan on a bi-weekly basis along with Weekly status report the Weekly Status report for that week. includes: and will include the following:  Date of the report and period covered by the report  A list of activities and accomplishments for the completed reporting period  A list of planned activities and accomplishments for the next reporting period  A list of risks and proposed mitigation plans  A list of issues

12 Task Task Description Deliverable(s) Deliverable Description requiring PDE decisions  Knowledge Transfer Status by individual PDE resource Meeting minutes should include the date of meeting, attendees, discussed items, action items, and next steps.

Requirements The Vendor shall conduct requirements review sessions and facilitate Requirements The Phase I Enhancements review and feedback sessions with PDE staff to finalize requirements for the Document with Functional Requirements validation following enhancements: Requirements document to include the 1. Upgrade to newer Ed-Fi version Traceability following: 2. Dynamic Watch Lists Matrix 1. A section for each 3. Embedded Help identified 4. Watch List Enhancements enhancement 5. Intervention Enhancements 6. External resource and support links 2. Within each section, where applicable, the For this task the Vendor shall work with PDE to review the functional document must detail requirements and mockups, provided in Appendix A –Enhancement functional Functional Requirements, to gain a full understanding of the desired requirements enhancement/functionality. From the requirements gathering session(s) 3. Requirements the Vendor shall prepare a requirements document details the functional Traceability Matrix requirements for each enhancement listed above. Included as an appendix to this document the Vendor shall create a requirements traceability matrix. Once PDE has approved the Requirements, the Vendor shall utilize TFS to manage the approved Requirements. Design for Dynamic The Vendor shall design functionality for Dynamic Watch Lists and the Dynamic Watch The Phase I Enhancement

13 Task Task Description Deliverable(s) Deliverable Description Watch Lists and necessary changes for the Upgrade to the newer Ed-Fi version. Using the Lists/ Upgrade Design document must Upgrade to newer accepted requirements, the Vendor shall document the functional and to newer Ed-Fi include the following: technical design as applicable for the above enhancements. Included as Ed-Fi version version Design  Functional and an appendix to this document the Vendor shall complete the document with Technical design requirements traceability matrix. requirements  Requirements Traceability Traceability Matrix Matrix Design for The Vendor shall design functionality for including embedded help within Embedded The Phase I Enhancement Embedded Help the Educator Dashboard application. Using the accepted requirements, Help Design Design document must the Vendor shall document the functional and technical design as document with include the following: applicable for the above enhancement. Included as an appendix to this requirements  Functional and document the Vendor shall complete the requirements traceability Traceability Technical design matrix. Matrix  Requirements Traceability Matrix Design for Watch The Vendor shall design functionality for Watch List enhancements. Watch List The Phase I Enhancement List Enhancements Using the accepted requirements, the Vendor shall document the Enhancements Design document must functional and technical design as applicable for the above Design include the following: enhancements. Included as an appendix to this document the Vendor document with  Functional and shall complete the requirements traceability matrix. requirements Technical design Traceability  Requirements Matrix Traceability Matrix Design for The Vendor shall design functionality for Intervention enhancements. Intervention The Phase I Enhancement Intervention Using the accepted requirements, the Vendor shall document the Enhancements Design document must Enhancements functional and technical design as applicable for the above Design include the following: enhancements. Included as an appendix to this document the Vendor document with  Functional and shall complete the requirements traceability matrix. requirements Technical design Traceability  Requirements Matrix Traceability Matrix Design for External The Vendor shall design functionality for External resource and support External The Phase I Enhancement

14 Task Task Description Deliverable(s) Deliverable Description resource and link implementation. Using the accepted requirements, the Vendor shall resource and Design document must support link document the functional and technical design as applicable for the above support link include the following: enhancements. Included as an appendix to this document the Vendor implementation Design  Functional and shall complete the requirements traceability matrix. document with Technical design requirements  Requirements Traceability Traceability Matrix Matrix Develop - Upgrade The Vendor shall upgrade the PDE Educator Dashboard solution to the  Upgrade of Code changes for the the existing newer Ed-Fi version as defined below and in Appendix A-1 Upgrade to Educator upgrade have been Educator Ed-Fi Version 2.0 Requirements: Dashboard completed and are ready dashboard solution 1. Upgrade Educator Dashboard Ed-Fi v1.2.1 to Ed-Fi v 2 Ed-Fi to be implemented into to newer Ed-Fi 2. Upgrade Educator Dashboard Ed-Fi ODS v 1.2 to Ed-Fi ODS v 2 Solution the staging environment a. Team Foundation Server (TFS) Build version  Upgrade of for testing. b. 14 dashboard extension packages Education c. 4 data warehouse extension packages Dashboard Ed-Fi ODS Additionally in moving to the next version, SSIS packages are no longer and supported. The Vendor shall upgrade the Educator Dashboard Ed-Fi ODS affected v 1.2 to Ed-Fi ODS v 2, revising code for the approximately 14 dashboard packages extension packages and 4 data warehouse extension packages ensuring these upgrades are compatible with using Team Foundation Server (TFS) Build.

Develop/Implemen The Vendor shall implement into PDE’s Educator Dashboard the Educator Dynamic Watch Application component t Ed-Fi Dynamic Dashboard Ed-Fi components for Dynamic Watch Lists. List feature changes for dynamic Watch List Feature See Appendix A-2 Ed-Fi Dynamic Watch List Feature requirements for watch list feature have specific requirements and expected outcome of the Dynamic Watch Lists been completed and are solution development. ready to be implemented into the staging environment for testing. Develop Watch List The Vendor shall develop the functionality within the Dashboard Enhanced Application component 15 Task Task Description Deliverable(s) Deliverable Description Enhancements application to allow a user to add a student to a watch list from the Watch List changes for watch list student level. See Appendix A-3 Watch List Enhancements for functional functionality enhancements have been requirements and example mockup. from Student completed and are ready Level to be implemented into the staging environment for testing. Develop Automatic The Vendor shall develop functionality within the dashboard application Automatic Application changes for Intervention to send email notifications to the creator of an intervention two weeks Intervention automatic intervention Notifications prior to the intervention expiration for those interventions that have not Notification notifications have been been completed. See Appendix A-4 Intervention Enhancements for completed and are ready requirements. to be implemented into the staging environment for testing. Develop Embedded The Vendor shall develop embedded Help functionality based on the Embedded Application changes for Help requirements in Appendix A-5 Embedded Help. Help the embedded help feature have been completed and are ready to be implemented into the staging environment for testing. Develop External The Vendor shall develop the functionality for users to access external External Application changes Resource Support resource and support links easily from the dashboard application. See Resource External Resource support Links Appendix A-6 External Resource and Support Links for functional Support link link functionality has been requirements and mockup. functionality completed and is ready to be implemented into the staging environment for testing. Develop The Vendor shall develop an Implementation Plan which will include: Implementatio Implementation 1. Implementation Schedule/Plan n Plan Plan 2. Implementation steps 3. Roles and Responsibilities

16 Task Task Description Deliverable(s) Deliverable Description 4. Expectations of PDE resources/Vendor resources

Knowledge Transfer Coordinate Knowledge Transfer activities related to: Technical Technical Document – 1. Technical Documentation documentation should contain a section a. The Vendor shall develop documentation describing the for each components, technical implementation and functionality enhancement/component Knowledge for work products detailing the information Transfer 2. Provide a review of the system components and documentation: listed in the description. 2 hours: session a. Upgrade b. Dynamic Watch lists c. Watch List from Student Level d. Automatic Intervention Expiration Notification e. Embedded help f. External resource and support links

Develop Educator Develop a project level Acceptance Test Plan. The Vendor shall develop Educator See Appendix B – Testing Dashboard an Acceptance Test Plan that: Dashboard Definitions Enhancements Enhancements Acceptance Test 1. Defines the process by which PDE will accept software expected Acceptance Plan outcomes Test Plan 2. Describes test strategies, plans, benchmark criteria, and reports 3. Testing Schedule 4. Testing Methodology 5. Bug reporting, revision and retesting process 6. Process for delivery of source code

This is a project level Acceptance Test Plan and should govern the testing of each enhancement. Develop Dynamic Create Test Scripts for Dynamic Watch lists and version Upgrade – Vendor Test scripts Testing scripts include the Watch List and shall develop scripts to test the Educator Dashboard system in Dynamic Watch steps for each test to be version Upgrade accordance with the Acceptance Test Plan. This includes development of lists and performed, identification

17 Task Task Description Deliverable(s) Deliverable Description Test Scripts tests scripts for: version of pre-requisite testing, Upgrade description of successful 1. Unit Testing outcome. 2. System Integration Testing Full regression testing 3. Full Regression Testing must be performed after the Upgrade, and should 4. Security Testing be coordinated with PDE Educator Dashboard 5. Performance Testing support resources.

6. User Acceptance Testing

Refer to Appendix B –Testing Definitions. Dynamic Watch Conduct Testing Dynamic Watch lists and version Upgrade – Vendor shall Test Report The test report based on and version test the Educator Dashboard system solution in accordance with the Dynamic Watch the test script and includes Upgrade List Acceptance Test plan. This includes: lists and the results of testing and Testing version confirmation of successful 1. Unit Testing Upgrade testing, and mapping what requirements are 2. System Integration Testing associated with each test. (requirements matrix) 3. Regression Testing

4. Security Testing Full regression testing must be performed after 5. Performance Testing the Upgrade, and should be coordinated with PDE Results of testing in accordance with the Acceptance Test Plan and test Educator Dashboard scripts. support resources. Support User Support User Acceptance Testing of Dynamic Watch List and version UAT Test The UAT test report shall Acceptance Testing Upgrade – PDE shall perform UAT and the Vendor shall support UAT Report be compiled by the vendor (UAT) - Dynamic Dynamic Watch 18 Task Task Description Deliverable(s) Deliverable Description Watch List and testing of the Educator Dashboard system solution in accordance with List/Upgrade ensuring that user testing version Upgrade the Acceptance Test plan. and acceptance has been UAT Dynamic received for each test in Results of testing in accordance with the Acceptance Test Plan and test Watch the UAT test script. At the scripts. List/Upgrade completion of UAT, the Successful vendor shall deliver the Completion compiled UAT Test Report. Memo. Develop Watch List Create Test Scripts for Watch List Enhancements – Vendor shall develop Test scripts Testing scripts include the Enhancements Test scripts to test the Educator Dashboard system in accordance with the Watch List steps for each test to be Scripts Acceptance Test Plan. This includes development of tests scripts for: Enhancements performed, identification of pre-requisite testing, 1. Unit Testing description of successful outcome. 2. System Integration Testing

3. Security Testing

4. Performance Testing

Refer to Appendix B –Testing Definitions. Watch List Conduct Testing for Watch List Enhancements – Vendor shall test the Test Report The test report based on Enhancements Educator Dashboard system solution in accordance with the Acceptance Watch List the test script and includes Testing Test plan. This includes: Enhancements the results of testing and confirmation of successful 1. Unit Testing testing, and mapping what requirements are 2. System Integration Testing associated with each test. (requirements matrix) 3. Security Testing

19 Task Task Description Deliverable(s) Deliverable Description 4. Performance Testing

Results of testing in accordance with the Acceptance Test Plan and test scripts. Support UAT - Support User Acceptance Testing of Watch List Enhancements – PDE shall UAT Test The UAT test report shall Watch List perform UAT and the Vendor shall support UAT testing of the Educator Report be compiled by the vendor Enhancements Dashboard system solution in accordance with the Acceptance Test plan. Dynamic Watch ensuring that user testing List and acceptance has been Results of testing in accordance with the Acceptance Test Plan and test received for each test in scripts. the UAT test script. At the completion of UAT, the vendor shall deliver the compiled UAT Test Report. Develop Create Test Scripts for Intervention Enhancements – Vendor shall Test scripts Testing scripts include the Intervention develop scripts to test the Educator Dashboard system in accordance Intervention steps for each test to be Enhancements Test with the Acceptance Test Plan. This includes development of tests Enhancements performed, identification Scripts scripts for: of pre-requisite testing, description of successful 1. Unit Testing outcome.

2. System Integration Testing

3. Security Testing

Refer to Appendix B –Testing Definitions. Intervention Conduct Testing for Intervention Enhancements – Vendor shall test the Test Report The test report based on Enhancements Educator Dashboard system solution in accordance with the Acceptance Intervention the test script and includes Testing Test plan. This includes: Enhancements the results of testing and confirmation of successful

20 Task Task Description Deliverable(s) Deliverable Description 1. Unit Testing testing, and mapping what requirements are 2. System Integration Testing associated with each test. (requirements matrix) 3. Security Testing

Results of testing in accordance with the Acceptance Test Plan and test scripts. Support UAT - Support User Acceptance Testing of Intervention Enhancements – PDE UAT Test The UAT test report shall Intervention shall perform UAT and the Vendor shall support UAT testing of the Report be compiled by the vendor Enhancements Educator Dashboard system solution in accordance with the Acceptance Dynamic Watch ensuring that user testing Test plan. List and acceptance has been received for each test in Results of testing in accordance with the Acceptance Test Plan and test the UAT test script. At the scripts. completion of UAT, the vendor shall deliver the compiled UAT Test Report. Develop Test Create Test Scripts for Embedded Help – Vendor shall develop scripts to Test scripts Testing scripts include the Scripts - Embedded test the Educator Dashboard system in accordance with the Acceptance Embedded steps for each test to be Help Test Plan. This includes development of tests scripts for: Help performed, identification of pre-requisite testing, 1. Unit Testing description of successful outcome. 2. System Integration Testing

3. Security Testing

21 Task Task Description Deliverable(s) Deliverable Description Refer to Appendix B –Testing Definitions. Embedded Help Conduct Testing Embedded Help – Vendor shall test the Educator Test Report The test report based on Testing Dashboard system solution in accordance with the Acceptance Test plan. Embedded the test script and includes This includes: Help the results of testing and confirmation of successful 1. Unit Testing testing, and mapping what requirements are 2. System Integration Testing associated with each test. (requirements matrix) 3. Security Testing

Results of testing in accordance with the Acceptance Test Plan and test scripts. Support UAT - Support User Acceptance Testing of Embedded Help – PDE shall perform UAT Test The UAT test report shall Embedded Help UAT and the Vendor shall support UAT testing of the Educator Dashboard Report be compiled by the vendor system solution in accordance with the Acceptance Test plan. Embedded ensuring that user testing Help and acceptance has been Results of testing in accordance with the Acceptance Test Plan and test received for each test in scripts. the UAT test script. At the completion of UAT, the vendor shall deliver the compiled UAT Test Report. Develop Resource Create Test Scripts External resource and support links – Vendor shall Test scripts Testing scripts include the Links Test Scripts develop scripts to test the Educator Dashboard system in accordance External steps for each test to be with the Acceptance Test Plan. This includes development of tests resource and performed, identification scripts for: support links of pre-requisite testing, description of successful  Unit Testing outcome.

 System Integration Testing

22 Task Task Description Deliverable(s) Deliverable Description  Security Testing

 Performance Testing

 User Acceptance Testing

Refer to Appendix B –Testing Definitions. Resource Links Conduct Testing External resource and support links – Vendor shall test Test Report The test report based on Testing the Educator Dashboard system solution in accordance with the External the test script and includes Acceptance Test plan. This includes: resource and the results of testing and support links confirmation of successful  Unit Testing testing, and mapping what requirements are  System Integration Testing associated with each test. (requirements matrix)  Security Testing

Results of testing in accordance with the Acceptance Test Plan and test scripts. Support UAT - Support User Acceptance Testing of External Resource and Support Links UAT Test The UAT test report shall Resource Links – PDE shall perform UAT and the Vendor shall support UAT testing of the Report External be compiled by the vendor Educator Dashboard system solution in accordance with the Acceptance resource and ensuring that user testing Test plan. support links and acceptance has been received for each test in Results of testing in accordance with the Acceptance Test Plan and test the UAT test script. At the scripts. completion of UAT, the vendor shall deliver the compiled UAT Test Report. Educator At the conclusion of successful testing, including successful UAT testing UAT With the issuance of this Dashboard of all enhancement components, the Vendor shall draft a memo stating Completion memo, the Vendor will Enhancement UAT UAT has been completed with full acceptance by the client and the Memo 23 Task Task Description Deliverable(s) Deliverable Description Completion system is ready for production implementation. coordinate scheduling implementation into production. Software Delivery - The Vendor shall deliver the fully tested Educator Dashboard system with Go-Live Memo The Go-Live memo shall Educator enhancements for implementation into the production environment. be drafted stating that the Dashboard The vendor shall coordinate with and support PDE resources in Educator Dashboard Enhancement implementing the system as prescribed in the Implementation Plan. software has been fully Go-Live implemented into production with full success confirmed by the client..

Assumptions 1. Vendor will develop the deliverables utilizing Ed-Fi version v2. It is assumed that there will be no impact on the existing Educator Dashboard functionality.

2. Any changes to final requirements must be jointly agreed-upon in writing among PDE and Selected Vendor.

3. PDE utilizes Sharepoint as a collaborative tool and project documentation repository. PDE will set up user provisioning for Vendor team members and expects all documentation artifacts and project management deliverable items to be uploaded there.

4. The vendor will utilize TFS in the following ways: Version control, Automated build process, requirements management, test development and testing management, and issue and bug fix tracking.

Knowledge Transfer Vendor will provide knowledge transfer for deliverables to PDE staff, in accordance with the requirements specified in the Tasks and Deliverables section for Knowledge Transfer.

24 Technical Documentation Vendor will provide specific technical documentation in accordance with the requirements specified in the Tasks and Deliverables section for Technical Documentation. Place of Performance The Vendor shall support PDE at PDE headquarters, 333 Market Street, Harrisburg, Pennsylvania. Furnished Equipment and Work Space PDE will provide workspace, on site, at the PDE 333 Market Street Office location for Vendor team members working onsite. Technology and Environments Vendor will be responsible to perform services through the activities listed in the above scope to support the development and implementation for the software components utilizing the technologies in the table below: Component Technology Dashboard Microsoft web and database technologies. Database components of the Dashboard SQL Server 2012 ETL (from PIMS to Operational Data Store (ODS)) MS SSIS ETL (from ODS to Dashboard Data Store) MS SSIS (must be converted to custom C#) Application components of the Dashboard EWS/IC Custom C#/.NET code(ASP.NET MVC3)

Period of Performance The period of performance for this engagement shall initiate the week of September 26, 2016 and conclude on or about September 30, 2017. It is a requirement of the SOW that the selected vendor will have a team in place and ready to commence work within five business days of selection

25 APPENDIX A –ENHANCEMENT FUNCTIONAL REQUIREMENTS

A-1: UPGRADE TO ED-FI VERSION 2.0 Providing the ability for the PDE Educator Dashboard solution to support additional functionality for the Phase I enhancements, the Vendor shall upgrade the PDE Educator Dashboard solution from Ed-Fi v1.2.1 to Ed-Fi v 2. Additionally in moving to the next version SSIS packages are no longer supported, and the Vendor shall upgrade the Educator Dashboard Ed-Fi ODS v 1.2 to Ed-Fi ODS v 2. These upgrades must be compatible with using Team Foundation Server (TFS) Build, and affect approximately 14 dashboard extension packages and 4 data warehouse extension packages. Regression testing must be performed as part of this enhancement to ensure that all current functionality has been retained. A-2: Ed-Fi Dynamic Watch List Feature

Provide the ability for LEA stakeholders to make data views in the PDE Educator Dashboard more easily filtered. While the data is available in the Dashboard by attendance, behavior, course grade, and demographics; looking at the data across these metrics is not currently available. Arkansas has developed functionality called “Dynamic Watch Lists” that enables filtering on multiple attributes, for example searching for male students with a Special Education designation with low attendance. This Dynamic Watch List functionality will allow educators to analyze their data by smaller and more distinct groups to ensure they’re focusing efforts on the most at risk students. Implement the Dynamic Watch List feature available in Ed-Fi into the PDE Educator Dashboard. Dashboard Tab Dashboard Pages/Metrics to be Implemented for PDE Dynamic Watch List Dynamic Watch List development is dependent upon the successful completion of the Upgrade for Pennsylvania’s Filters are selected by Dashboard and ODS. the teacher and Complete instructions for implementation of Ed-Fi Dashboard dynamically produce a Dynamic Watch List can be found at https://techdocs.ed- listing of students who fi.org/display/DASH14/Dynamic+Watch+List+Feature meet the selected The StudentList database view has been removed as of criteria. Dashboards v1.3. When using it you will need to remove the code for any extension.StudentList views and the post-load steps that materialize them.  If the extension was present solely to display additional metrics, those metrics should now be present without requiring an extension.

 For nonmetric columns, the extension will have to re- extend the code to support those new columns.

Rev 8.26.2015 Page 26 Dashboard Tab Dashboard Pages/Metrics to be Implemented for PDE  All PagingProviders have been removed as of Dashboards v1.3 (StudentDemographicPagingProvider, StudentGradeListPagingProvider, StudentListPagingProvider, StudentMetricPagingProvider, StudentSchoolCategoryListPagingProvider).

 When using it you will need to remove the code for any extension PagingProviders and, if needed, re-extend the Metrics-based Watch List for the extension functionality.

Rev 8.26.2015 Page 27 A-3: WATCH LIST ENHANCEMENTS Provide the ability for a user to add a student to a watch list from the student level through one click.

A-4: INTERVENTION ENHANCEMENTS Provide the ability for the dashboard application to automatically send email notifications to the creator of an intervention two weeks prior to the intervention expiration for those interventions that have not been completed (no completion date). A-5: EMBEDDED HELP To assist educators in using the Educator Dashboard, embedding Help functionality in the Dashboard will give educators the ability to search an index of Dashboard functionality and topics to help them use the Dashboard to the fullest extent. As educators understand the full capabilities of the dashboard, they are more empowered to help their students on the educational path. Educators and support staff are also more likely to use the data in new and creative ways to improve student outcomes.

Rev 8.26.2015 Page 28 1. Provide users with the ability to access Educator Dashboard embedded help from a single location on the webpage that is uniform with website standards.

2. Provide a single icon which when clicked will initiate a display of Educator Dashboard Help Index.

3. When a Help Index link is clicked display the content associated with the Help topic selected.

4. Provide the ability for the user to search the Help Topics and Index

Below is a sample table of Help Index and Topics that may be referenced for embedded Help, this list will be reviewed and revised by PDE and the Vendor during requirements validation and is provided for scope purposes. Level Tab Help All All Metric definition hover-over where not defined on screen All Defined in Help Add to Header or in the Legend at the bottom of the page: Academic Dashboard - metrics defined under Goal Planning Early Warning System - metrics predefined and list metric threshold

District Academic Dashboard >> Question mark box hover-over Grades and Credits Grades below C level - This metric can be changed in Goal Planning. See System Administrator. All Help Index How to search student/staff All Help Index How to find student at risk? All Help Index How to view student list All Help Index How to view student’s course grades All Help Index How to view/change goals at school and district levels All Help Index How to add interventions All Help Index How to modify interventions All Help Index How to assign interventions to student All Help Index How to assign interventions to a group of students All Help Index How to add security to interventions All Help Index How to close/rate an intervention All Help Index How to import interventions/view other LEAs interventions All Help Index How to add/export notes to an intervention All Help Index How to search interventions All Help Index How to create a watch list Rev 8.26.2015 Page 29 Level Tab Help All Help Index How to upload photos All Help Index How to customize student list views

A-6: EXTERNAL RESOURCE AND SUPPORT LINKS 1. Provide the ability for a user to access relevant external resource and support materials from the Dashboard Early Warning System user interface tab. Provide a relevant link (buttons) for each measure, that, when clicked will display a pop-up with only the associated resource and support material links displayed. See Mockup below.

2. Provide the ability for PDE Operations Support team to easily maintain the list of external resource and support links. Links should be categorized by Attendance, Behavior, Mathematics and English/Language Arts.

Rev 8.26.2015 Page 30 Rev 8.26.2015 Page 31 APPENDIX B –TESTING DEFINITIONS

Testing Vendor will conduct and participate in the following types of software testing:

 Unit Testing

 System Integration Testing

 Security Testing

 User Acceptance Testing

The following defines PDE’s expectations and requirements of each type of testing.

Unit Testing Requirements Vendor shall conduct unit testing as part of the development activity. Unit Testing focuses on validating the individual units of software functionality. Following the completion of any software development, modification, or system configuration change, each developer is responsible for testing the individual software “units” or groups of related units based on test cases supplied by their development lead, and documenting the unit test results.

If a software discrepancy is identified during Unit Testing, steps are taken to document, resolve, and retest the “unit” until expected results are achieved. Once expected Unit Test results and acceptance criteria are met, reviewed, and validated by the appropriate Vendor team member, the individual software “units” or groups of related units are ready for System Integration Testing.

System Integration Testing Requirements The purpose of System Integration Testing (SIT) is to evaluate whether the software “units” perform as expected when integrated with the rest of the application components, ancillary systems, and interfaces. Vendor will perform SIT testing. The SIT effort will focus inter-module functionality. To ensure that the system is fully integrated and working properly, Vendor will use automated tool testing in combination with manual tests, to ensure that all integrated pieces of the system are fully tested from end to end. . The PDE team can, at its option, perform testing on the system prior to its deployment for the next level of testing.

Security Testing Requirements Vendor will perform Security Testing to determine that defined role-based user profiles have access to data and processes and perform functionality as per specifications. This level of testing shall be performed in conjunction with SIT testing. Rev 8.26.2015 Page 32 User Acceptance Testing Requirements User Acceptance Testing (UAT) focuses on validating that the functionality that passed Unit Test and SIT will perform correctly when subjected to user perspectives. UAT test plan and scripts must be provided prior to SIT testing commencement. UAT focuses on validating end-to-end business scenarios that are critical to the successful completion of the business process. This is the first testing Deployment in which end-users (subject matter experts) are introduced to validate functional and usability requirements. The success and quality of the deployment depends on the extent and thoroughness of UAT. The responsibility for UAT lies with PDE. Vendor’s role in UAT is to facilitate the testing, developing the UAT test plan and creating test scripts. In preparation of UAT, Vendor shall work with the LEAs to define appropriate data quality validation processes, and ensure that LEA testers are able to validate their data and identify issues, as needed. During UAT testing, PDE team members and LEA stakeholders identified for UAT will exercise the UAT test scripts, perform testing, and log their results. When a user test script is successfully run and meets the associated specifications and has received sign-off by PDE, it will be considered complete and accepted. Following this process, when all of the identified user acceptance test scripts are passed, the user acceptance test of the system solution will be considered complete.

Rev 8.26.2015 Page 33