Performance_Work_Statement_-Feb_2018_(clean).pdf

Attachment A – Performance Work Statement (February 2018)

Development And Technical Assistance for Leveraging Analysis Based Websites Page 1 of 48

Performance Work Statement

Development And Technical Assistance for Leveraging Analysis Based Websites

(DATALAB)

I. INTRODUCTION

The United States Department of Education’s (the Department) National Center for Education Statistics (NCES) within the Institute of Education Science (IES) has a requirement to provide web-based data analysis tools that allow users to create tables and graphics representing education data, examine trends over time, and analyze data using bi-variate and multivariate statistical tests and models. These data tools use data from several large and complex data collections including national longitudinal surveys, linked cross-sectional surveys, census data, and administrative record data. The data tool primarily associated with this requirement can be located at this URL: https://nces.ed.gov/datalab. Further, NCES has the need for expert technical support in the development and management of the databases and tools that house and are used to analyze these data. Many of the datasets housed in these analysis systems are derived from complex surveys, and advanced statistical computations are needed in order to yield accurate estimates and standard errors from the data collected. The work outlined in this work statement requires close and continuing collaboration with NCES staff and contractors working across all Divisions in NCES. It also requires the coordination of staff with different sets of expertise including IT programmers, graphic designers, survey statisticians, and educational researchers.

Technical specifications for the website, staging and development environments, and the data structures are located in Appendix A.

Contractor personnel supporting this effort must possess sufficient technical certifications, educational degrees, and experience to support the contract's unique requirements.

Representative software technologies implemented at the unit's include: Hypertext Markup and Extensible Markup Languages; Cascading Style Sheets; Active Server Pages; Java and JavaScript; Microsoft Visual Basic, .Net, SQL Server, ASP, PHP and C#. Software engineering processes and tools include: build management and automation tools, continuous deployment strategies, test-driven and/or behavior-driven development, performance testing strategies, and security testing policies. Contractors must also have personnel with expertise in complex surveys, especially in using replicate weights and Taylor Series linearization to adjust variances.

The contractor shall provide maintenance for the existing databases and tools, develop enhancements to these databases and tools, develop new application modules, and provide front-and back-end web support for these databases and tools. The contractor shall provide expert technical assistance to NCES in managing the databases behind these tools, quality assurance, and support to internal and external data users.

II. LEGISLATIVE AUTHORITY

Legislative authority for the activities detailed in this work statement is granted under 20 U. S. C.

§ 9543.

Development And Technical Assistance in Leveraging Analysis Based Websites Page 2 of 48

III. CONTRACT TYPE

The contract type is Labor Hour.

IV. PERIOD OF PERFORMANCE

The period of performance is 120 months as follows:

• Base Period: 60 months

• Option Period 1: 60 months

V. CURRENT STATUS

NCES currently produces reports, data analysis tools, and a data library to support and encourage the use of its education data collections. An example of a data analysis tool primarily associated with this requirement is located at http://nces.ed.gov/datalab. Examples of web-based tables and reports can be found at https://nces.ed.gov/datatools. The predecessor contract to this requirement is ED-IES-12-C-0094 titled “Postsecondary Education Data Structure Support (PEDSS).” This requirement is different than PEDSS because it supports the dissemination of data at all levels of education.

VI. CONTRACT PHASE-IN AND CLOSEOUT PERIODS

To minimize decreases in productivity and to prevent possible negative impact on services, this contract will begin with a one-hundred and twenty (120) day phase in-period that overlaps with the existing contract ED-IES-12-C-0094. During the phase-in period, the Contractor shall have personnel on board who shall work with the incumbent contractor, become familiar with performance requirements, clarify work requirements, and implement a transition plan provided by NCES in order to commence full performance of services on the date agreed upon for transitioning all IT systems and operations.

During the final one-hundred twenty (120) days of this contract, the contractor shall make staff available to answer technical questions and provide support, as needed, to the new contractor who will support the Department’s web-based data analysis tools.

VII. SCOPE OF WORK

The scope of this requirement will primarily focus on data tools in the Data Lab website (https://nces.ed.gov/datalab). The current Data Lab website includes tools that range from simple table generators to full statistical packages with a web-based graphical interface (e.g., bivariate estimates (means, medians, percentiles) and statistical tests, linear regression, logistic regression, with and without replicate weights). While work primarily focuses on the Data Lab website, additional work includes any website or data tools housed on the NCES or IES websites (https://nces.ed.gov or https://ies.ed.gov websites) that are related to Data Lab such as maintaining old data tools, integrating other tools into the Data Lab website, or the maintenance of data structures or data tools.

http://nces.ed.gov/datalab https://nces.ed.gov/datatools https://nces.ed.gov/datalab

Development And Technical Assistance in Leveraging Analysis Based Websites Page 3 of 48

VIII. REQUIREMENTS

The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform all tasks as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract or as revised by the Office of Management and Budget or the Department’s Office of the Chief Information Officer. All IT systems, software, and databases funded under this contract are the property of the U.S. Government.

To achieve the development objectives for the DataLab website and other websites covered by this work statement, the contractor shall:

• Maintain a code repository,

• Automate incremental builds,

• Ensure that builds are self-testing using behavior driven approaches,

• Implement unit, integration, acceptance, and performance tests in the build automation process,

• Catalog the builds,

• Test in a clone of the production environment,

• Generate metrics for performance tests and results for performance benchmarks with every build,

• Provide build reports to NCES, and

• Automate the deployment process.

Prior to submitting the first monthly report, the contractor shall propose Test Key Performance Indicators (TKPIs) aligned with the priorities written in this work statement to assist in monitoring the performance of the software and database. The TKPIs shall include measures both within and outside the contractor’s control so that the Department can identify the performance characteristics of the whole system (e.g., DataLab applications, the Department’s infrastructure, network, etc.) in a controlled environment, understand bottlenecks, and the identify resolutions to problems in performance. The primary TKPIs that need to be measured are as follows:

• Response time (latency);

• The number of user steps completed in a set period of time (throughput);

• Resource utilization (i.e., CPU and memory utilization);

• Efficiency (throughput divided by utilization);

• Statistical accuracy; and

• Time between data release and posting to the DataLab website..

For each component of the DataLab website, the contractor shall continuously optimize computational efficiency in queries to the database and in computing estimates. The contractor shall examine the load on the server and develop solutions to decrease computation time and burden on the web and database servers as new features/datasets move through the work flow.

The contractor shall utilize TKPIs to document a reduction in the frequency of response latency during peak load periods or propose solutions for improving performance if a resolution to a problem is outside the contractor’s control.

Development And Technical Assistance in Leveraging Analysis Based Websites Page 4 of 48

This section describes the requirements for this contract. Section IX below provides specifications for the deliverables associated with each requirement.

BASE PERIOD:

TASK 1: MANAGEMENT

The Contractor shall manage the online analysis and reporting of data in a manner that establishes quality control at all levels and fosters communications between the contractor's staff, the Contracting Officer's Representative (COR), and online data users. This task continues for the entire contract period. Task 1 includes the following requirements, which is designed to monitor progress on the activities in this contract:

Subtask 1.1: Monthly Progress Reports

The contractor shall report monthly on the progress made in accomplishing the project tasks, problems encountered, report Test Key Performance Indicators (TKPIs), and plans for the next month. The contractor shall attach an updated schedule, a financial statement showing consumption of funds, and a staffing plan showing labor usage to each monthly report.

Subtask 1.2: Security Screening, Confidentiality Documents, and Data Security Reports

The contractor shall file reports as outlined in Appendix B with the NCES COR that identify staff with access to restricted data and with access to sensitive Information Technology (IT) resources.

Subtask 1.3: Conference Calls

The Contractor shall update NCES project staff via conference calls. The contractor shall plan for bi-weekly calls, though calls shall be held weekly during the phase-in period.

Subtask 1.4: Meetings

The contractor shall attend an in-person kick-off meeting to be held at the Department upon within four weeks from the award date of the contract and a second kickoff meeting if the option period is exercised. Additionally, the contractor’s Project Director, or designee, shall attend at least two in-person meetings per year to obtain feedback from external constituents or NCES program staff. Meetings will occur within the Washington, DC metropolitan area.

TASK 2: DATALAB WEBSITE

The DataLab website is the home or entry page from which users can access a suite of data tools (https://nces.ed.gov/datalab) including PowerStats, QuickStats, TrendStats, the Career and College Tables Library, and others. The contractor shall perform the following activities related to DataLab:

https://nces.ed.gov/datalab

Development And Technical Assistance in Leveraging Analysis Based Websites Page 5 of 48

Subtask 2.1: Maintenance of existing datasets and database functionality

The contractor shall ensure that all databases (meta-data as well as data from respondents/individual surveys) are maintained to ensure continuing functionality of the data tools on the DataLab website. Changes (including software upgrades, modifications to the IES Infrastructure as a Service (IaaS) virtual hosting solution, or modifications to other tools) shall be implemented so that functionality is not diminished. Any issues with diminished functionality shall be resolved.

Subtask 2.2: Maintenance of existing software and tool functionality

The contractor shall maintain the web interface functionality of the data tools on the DataLab website, ensuring compatibility with non-beta versions of web browsers. At minimum, the contractor shall maintain compatibility with the five web browsers most commonly used to accessed the IES website. The contractor shall consult the COR prior to changing the list of compatible web browsers.

Subtask 2.3: Weight Selection Module

The contractor shall add a module to the DataLab website to assist users in selecting the most appropriate weight using a Public-Use or Restricted-Use data file based on the variables chosen. The contractor shall develop a method for including a stand-alone version of the module that can run on a Restricted-Use file (Restricted use-files can only be used on a computer without access to the internet). After this module is complete, the contractor shall update the Weight Selection Module within DataLab each time a study is added.

Subtask 2.4: Integration of Tayler-Series Linearization Variance Correction Option

Most NCES sample survey datasets are derived from studies with complex sampling designs, rather than from studies with simple random samples. Appropriate methods that account for the design must be used to calculate correct variances and standard errors.

The data tools in DataLab currently support the use of replicated weights to produce corrected standard errors. The contractor shall create an option for computing corrected standard errors that employs Taylor Series design variables across all data tools on the DataLab website.

Subtask 2.5: Search Optimization

The contractor shall improve the search function and optimize the table lookups using a matching algorithm. The new search algorithm shall be implemented for QuickStats, PowerStats and TrendStats when searching for variables, variable labels, and variable descriptions; the Tables Library when searching tables; and other search functions on the DataLab website.

TASK 3: POWERSTATS

PowerStats is an online tool on the DataLab website which allows registered users to build complex statistical tables and run basic regressions on large sample survey datasets. It was

Development And Technical Assistance in Leveraging Analysis Based Websites Page 6 of 48 designed to allow the public access to restricted-use data while maintaining the confidentiality of the case-level data. The contractor shall perform the following activities:

Subtask 3.1: Enhancements to Statistical Modules

The contractor shall enhance the statistical modules within PowerStats to increase the utility of the web-based software. The contractor shall add the following features and propose additional features based on feedback from the user community:

- Integrated chi-square test option on output screen

- Integrated t-test option on output screen

- Additional regression options such as multiple regression (or entry of variables into blocks)

- Conversion of continuous variables to standardized (z-score) measures (if technically feasible)

- Conversion of continuous variables to logarithms (if technically feasible)

Subtask 3.2: Enhancements to Output Functionality

The contractor shall enhance the output options in the web-based data tool to increase the utility of the web-based software. The contractor shall add the following features and propose additional features based on feedback from the user community:

- Add new functionality to provide graph and chart output options

- Add new functionality to display data geographically, but consistent with a study’s sampling design.

- Add a module or mechanism for comparing estimates across states for datasets with state-representative data.

TASK 4: QUICKSTATS

QuickStats is an online tool which allows users to produce simple statistical tables using data from large sample survey datasets quickly. QuickStats allows users to generate bivariate tables for a limited number of recommended or frequently used variables. QuickStats is designed for users without a background in statistics to have access to NCES data, so features are limited and does not include complex statistics. It is designed to allow the public access to restricted-use data while maintaining the confidentiality of case-level data. The contractor shall perform the following activities:

Subtask 4.1: Enhancements to Output Functionality

The contractor shall enhance the output options in the web-based data tool to increase the utility of the web-based software. The contractor shall add the following features and propose additional features based on feedback from the user community:

- Enhance current functionality to provide graph and chart output options

- Add a module or mechanism for comparing estimates across states for datasets with state-representative data.

Development And Technical Assistance in Leveraging Analysis Based Websites Page 7 of 48

TASK 5: TRENDSTATS

TrendStats is an online tool based on PowerStats which allows registered users to build complex statistical tables showing estimates for repeated cross-sectional and longitudinal studies with repeated measures over time. It was designed to allow the public access to restricted-use data while maintaining the confidentiality of case-level data. The contractor shall perform the following activities:

Subtask 5.1: Enhancements to Statistical Modules

The contractor shall enhance the statistical modules within TrendStats to increase the utility of the web-based software. The contractor shall add the following features and propose additional features based on feedback from the user community:

- Integrated chi-square test option on output screen

- Integrated t-test option on output screen appropriate for repeated measures over time

- Conversion of continuous variables to standardized (z-score) measures (if technically feasible)

- Conversion of continuous variables to logarithms (if technically feasible)

- Multivariate models appropriate for examining repeated cross-sectional data such as pooled regression (if technically feasible)

Subtask 5.2: Enhancements to Output Functionality

The contractor shall enhance the output options in the web-based data tool to increase the utility of the web-based software. The contractor shall add the following features and propose additional features based on feedback from the user community:

- Enhance current functionality to provide graph and chart output options

TASK 6: DATA ANALYSIS SYSTEM (DAS) MAINTENANCE AND PHASE OUT

The Data Analysis System (DAS) (https://nces.ed.gov/das) is the online data tool which is the precursor to PowerStats. Similar to PowerStats, the DAS allows users to build complex statistical tables and run basic regressions on large sample survey datasets, but without the more contemporary Graphical User Interface (GUI). It was designed to allow the public access to restricted-use data while maintaining the confidentiality of case-level data. The contractor shall perform the following activities:

Subtask 6.1: Maintenance of existing datasets and database functionality

The contractor shall ensure that all databases (meta-data as well as data from respondents) are maintained to ensure continuing functionality of the data tool. Changes (including software upgrades, modifications to the IES IaaS virtual hosting solution, or modifications to other tools) shall be implemented so that functionality is not diminished.

Any issues with diminished functionality shall be resolved.

https://nces.ed.gov/das

Development And Technical Assistance in Leveraging Analysis Based Websites Page 8 of 48

Subtask 6.2: Maintenance of existing software and tool functionality

The contractor shall maintain basic web interface functionality of the data too,l ensuring compatibility with non-beta versions of web browsers. At minimum, the contractor shall maintain compatibility with at least one of the top five web browsers accessing the IES website. The contractor shall consult the COR prior to changing the list of compatible web browsers. The recommended browser shall be noted on the web page.

Subtask 6.3: Phase out

The contractor shall develop a plan to transfer all datasets currently in the DAS into the DataLab website. Upon approval of the phase-out plan, the contractor shall gradually move all datasets into to DataLab. After the transfer has occurred, the contractor shall decommission the DAS website. Any public-use dataset versions of the DAS shall be converted to restricted-use versions when moved to DataLab.

TASK 7: TABLES LIBRARY

The Career and College Tables Library is an online tool which allows the public access to NCES’ published Postsecondary Education tables via one, central location. It was developed to make finding published tables easier than searching through individual published reports. It has complex search functionality and allows users to import the tables into QuickStats/PowerStats (where available). The contractor shall perform the following activities:

Subtask 7.1: Table Updates

The contractor shall update the databases when provided new tables by NCES staff or its authorized contractors.

Subtask 7.2: Update Browse Functions

The contractor shall update the categories/subcategories, glossary, and search terms used to locate tables in the database using the graphical interface.

TASK 8: WEBVTS

WebVTS is the central repository of NCES’ survey data and metadata in DataLab. It is supposed to serve as the backend system for the tools on the DataLab website and it can be used to create the the restricted-use datasets issued by IES. It features a web GUI that allows NCES and its authorized contractors to upload data and define the metadata to be displayed in the tools.

WebVTS is currently a stand-alone system that provides output files that can be uploaded to the DataLab website and processes restricted-use data files for final review and release through NCES’s licensing program. The contractor shall complete the following activities:

Subtask 8.1: WebVTS Content Management System (CMS)

The contractor shall convert WebVTS to a Content Management System (CMS) for the DataLab website so that NCES users without IT programming expertise can use a GUI to customize features of PowerStats, QuickStats, TrendStats, (and other integrated tools on

Development And Technical Assistance in Leveraging Analysis Based Websites Page 9 of 48 the Data Lab website) without requiring a programmer. WebVTS shall be integrated into a work flow to allow for the review and approval of new data sets being added to DataLab in staging websites before moving to a production environment. Upon completion, authorized NCES staff shall be able to upload and customize features of DataLab to accomodate a dataset without intervention from IT programmers or contractors. The contractor shall add the following features and propose additional features based on feedback from NCES staff using WebVTS:

- Customizable reserve codes – staff should be able to define reserve codes using other than negative numbers and shall toggle them on or off using WebVTS.

Capabilities should be built in to toggle reserve codes on a variable by variable basis or for groups of variables.

- Allow for legitimate negative values in PowerStats (z-scores other standardized measures).

- Customizable pop-up messages – staff can create a pop-up message on select pages to address any immediate or long-term issues with the data or provide special instructions.

- Allow for edits to the Dataset selection screens, variable titles, variable labels, etc.

in real time.

- Change the weighting recommendations without programming

Subtask 8.2: Dataset Compatibility

The contractor shall customize WebVTS and the related Datalab tools to accommodate new NCES studies with data that may be formatted differently than the current studies loaded into the data tools. Such features may include:

- A different reserve code schema.

- Treatment of missing values that may differ from how DataLab currently treats missing values or cases.

- The conversion of weights/design variables to be compatible with DataLab.

- Pop-up messages informing or warning users of special data features.

- Different routing through menus and web pages (for example, directing users to specific cohorts or different surveys within the same study).

Changes made through this subtask may become a permanent feature of WebVTS and DataLab to increase the utility of the overall system for NCES studies.

TASK 9: DATA SECURITY

Subtask 9.1: Comprehensive Review and Report

The contractor shall conduct a comprehensive review of the DataLab website to ensure compliance with existing Confidentiality/Privacy Laws, the Department’s and OMB’s IT requirements/Federal Laws outlining IT security, and best practices that balance security with the usability of the data tools/website. The contractor shall write a report making recommendations to enhance the security of the website and the databases on the IES server.

Development And Technical Assistance in Leveraging Analysis Based Websites Page 10 of 48

Subtask 9.2: Implementation of Recommendations

Upon COR approval, the contractor shall implement recommendations of the report developed in Task 9.1.

TASK 10: POSTING OF NEW DATASETS

Subtask 10.1: Posting of New Data (Pre-formatted data)

The Contractor shall move certain datasets through the work flow as presented in Appendix A (or as modified) using data and meta data supplied by NCES or a third-party data collection contractor. The contractor shall assist NCES or the third-party data collection contractor in ensuring that DataLab can accommodate the dataset, and make any adjustments to the programming necessary to accommodate the new dataset.

The Contractor shall conduct a quality check of the data tool and of the data to ensure that the data tool yields accurate estimates, that these estimates match the microdata, and the additional dataset is in full compliance with IES’ Web Publishing Guidelines, Standards & Procedures. These quality checks should occur at each stage of the work flow presented in Appendix A. After the new dataset has been cleared for release by the COR (or designee [typically the study director]), the contractor shall instruct IES Web Services to review and publish the new files the NCES’ “Development” web server for final quality review by the NCES Chief Statistician. Following approval, the contractor shall instruct IES Web services to review and publish the approved study to the NCES “Production” web server allowing public access to the data. The Contractor shall inform the NCES project staff of the likely publication date and time. The data files that will be provided to the contractor under this task will have already been formatted for upload into WebVTS. Any structural edits to the data or metadata under this task are the responsibility of NCES or the third-party data collection contractor.

After a new database is moved to the production website, the Contractor shall complete another quality control check of the changes on the live website within two (2) hours of data being made available to the public in DataLab. The Contractor shall inform the NCES project staff of the passage or failure of quality checks associated with all files pushed to production within this two (2) hour window. If any failure occurs, the Contractor shall work with IES Web Services staff to rectify the situation as soon as possible.

The contractor shall plan for regular releases from the National Postsecondary Student Aid Study (NPSAS and NPSAS-AC), the Beginning Postsecondary Students Longitudinal Study (BPS), and the Baccalaureate and Beyond Longitudinal Study (B&B) under this subtask.

Subtask 10.2: Conversion of the National Longitudinal Study of 1972 (NLS-72) for use in DataLab

The contractor shall convert the DOS-based Electronic Codebook (and associated data files) for the NLS-72 study to be used on the DataLab website. The NLS-72 dataset includes Taylor Series design variables, which must be available for use in DataLab to

Development And Technical Assistance in Leveraging Analysis Based Websites Page 11 of 48 ensure that estimates match previous publications. Thus, completion of this task is dependent on the completion date of the subtask 2.4. After the data and meta data files have been formatted for upload to the DataLab website, the contractor shall post the new using the process described in Subtask 10.1.

TASK 11: QUALITY ASSURANCE

Subtask 11.1: Quality Control Assurance Plan

The contactor shall develop and deliver a quality control assurance plan that applies to all web products developed under this contract. Specifically, it shall detail the verifications made prior to pushing affected files from the build servers to the Data Lab staging server and from IES development to IES’ production server. Further, it shall detail the tests and subsequent results once the files are live on the production server, including but not limited to performance testing and benchmarks, build acceptance tests, and functional tests. The contractor shall document all known defects and issues with their corresponding workaround and provide a plan to address these defects/issues.

Upon acceptance and approval of the Quality Control Assurance Plan described in subtask 11.1, the contractor shall implement the Quality Control Assurance Plan across all activities in the work statement.

TASK 12: DOCUMENTATION

In compliance with IES’ Web Publishing Guidelines, Standards & Procedures, the Contractor shall provide programmatic documentation of all compiled applications developed under this contract.

Subtask 12.1: Annual Documentation

NCES project staff should be advised annually as to progress toward full programmatic documentation. The documentation shall include a Master Architecture Plan, which shall provide a 3-5 year forecast for changes in technology, architecture, interfaces, capabilities, testing, and user requirements. The contractor shall revise the previous year’s Annual Documentation and resubmit it to NCES annually.

Deliverables: Annual Documentation Update (12.1)

Subtask 12.2: Final Documentation

The Contractor shall deliver a full programmatic documentation upon contract completion. This documentation shall include annotations at all application, library, class, and object levels. In addition, the documentation shall comprise programmatic records of build and test code, including but not limited to:

• Build scripts,

• Unit tests,

• Integration tests,

• Performance tests, and

Development And Technical Assistance in Leveraging Analysis Based Websites Page 12 of 48

• Functional end-to-end tests.

Deliverables: Documentation Final Delivery (12.2)

BASE PERIOD: OPTIONAL TASKS

OPTIONAL TASK 13: ADDITIONAL DATASETS

The Contractor shall derive WebVTS-compliant datasets from datasets for studies that also release data using tools or platforms other than DataLab or WebVTS systems, or other existing external data sources. The Contractor shall convert/edit the datasets and metadatasets for import and export to/from WebVTS, then make the new dataset available via QuickStats, PowerStats, and/or TrendStats (if applicable). The contractor shall post data from the additional studies using the process described in Subtask 10.1. It is estimated that NCES will exercise five optional subtasks per year at differing levels of complexities. The contractor shall make the following studies available in DataLab:

Subtask 13.1: High School Longitudinal Study of 2009, High School and Beyond 2020, Middle Grades Longitudinal Study, or equivalent, follow-up

Subtask 13.2: High School Longitudinal Study of 2009, High School and Beyond 2020, Middle Grades Longitudinal Study, or equivalent, follow-up

Subtask 13.3: High School Longitudinal Study of 2009, High School and Beyond 2020, Middle Grades Longitudinal Study, or equivalent, follow-up

Subtask 13.4: High School Longitudinal Study of 2009, High School and Beyond 2020, Middle Grades Longitudinal Study, or equivalent, follow-up

Subtask 13.5: High School Longitudinal Study of 2009, High School and Beyond 2020, Middle Grades Longitudinal Study, or equivalent, follow-up

Subtask 13.6: Postsecondary Education Transcripts/Student Records or equivalent

Subtask 13.7: Postsecondary Education Transcripts/Student Records or equivalent

Subtask 13.8: Postsecondary Education Transcripts/Student Records or equivalent

Subtask 13.9: Postsecondary Education Transcripts/Student Records or equivalent

Subtask 13.10: Postsecondary Education Transcripts/Student Records or equivalent

Subtask 13.11: School Survey on Crime and Safety, or equivalent

Subtask 13.12: School Survey on Crime and Safety, or equivalent

Subtask 13.13: School Survey on Crime and Safety, or equivalent

Subtask 13.14: School Survey on Crime and Safety, or equivalent

Development And Technical Assistance in Leveraging Analysis Based Websites Page 13 of 48

Subtask 13.15: School Survey on Crime and Safety, or equivalent

Subtask 13.16: National Household Education Surveys (all components), or equivalent

Subtask 13.17: National Teacher and Principal Survey (all components), or equivalent

Subtask 13.18: National Teacher and Principal Survey (all components), or equivalent

Subtask 13.19: National Teacher and Principal Survey (all components), or equivalent

Subtask 13.20: National Teacher and Principal Survey (all components), or equivalent

Subtask 13.21: Early Childhood Longitudinal Study, Birth Cohort (ECLS-B) (all releases), or equivalent

Subtask 13.22: Early Childhood Longitudinal Study, Kindergarten Class of 1998-99 (ECLS-K) (all releases), or equivalent

Subtask 13.23: Early Childhood Longitudinal Study, Kindergarten Class of 2010-11 (ECLS-K:2011) (all releases to date), or equivalent

Subtask 13.24: Early Childhood Longitudinal Study, or equivalent, follow-up

Subtask 13.25: Early Childhood Longitudinal Study, or equivalent, follow-up

OPTIONAL TASK 14: PUBLICATION MODULE

The contractor shall create a module that would allow users to convert estimates from the DataLab website into a formatted Data Point publication. In addition, the contractor shall explore using innovations in Artificial Intelligence (AI) to analyze DataLab usage statistics (tracking tables that data users actually generate) and use that information to automatically generate Data Point publications.

OPTIONAL TASK 15: INTEGRATION OF ONLINE CODEBOOK (FORMERLY

EDUCATION DATA ANALYSIS TOOL OR EDAT) INTO DATALAB

The contractor shall review, update, and integrate the code, databases, and datasets from the Online Codebook (formerly called that Education Data Analysis Tool or eDAT) (see:

https://nces.ed.gov/edat/index.aspx?agrmnt=1) onto the DataLab website. The website shall include a GUI consistent with the DataLab products and allow for users to download public-use dataset versions of the output screens of the DataLab components (i.e., PowerStats, TrendStats, and QuickStats) without the need to browse and login to another website.

OPTIONAL TASK 16: DATALAB ENHANCEMENT PLAN

The contractor shall draft an enhancement plan for improving the DataLab website, and its components, using the same scope and level of effort for the following tasks as a guide:

https://nces.ed.gov/edat/index.aspx?agrmnt=1)

Development And Technical Assistance in Leveraging Analysis Based Websites Page 14 of 48

- Subtask 2.3: Optimization of Programming and Computational Efficiency

- Subtask 2.4: Integration of Tayler-Series Identifiers(except for another weight/design variable)

- Subtask 2.5: Search Optimization (or a plan for other methods for quickly accessing information)

- Subtask 3.1: Enhancements to Statistical Modules (except for other additions)

- Subtask 3.2: Enhancements to Output Functionality

- Subtask 4.1: Enhancements to Output Functionality

- Subtask 5.1: Enhancements to Statistical Modules (except for other additions)

- Subtask 5.2: Enhancements to Output Functionality

- Other subtasks that need to be updated to reflect the remainder of the contract.

The contractor shall provide multiple drafts using an iterative feedback process. Upon approval of the enhancement plan, the contractor shall implement the plan during the option period using the same level of effort estimated in the base period for the same tasks.

OPTIONAL TASK 17: CONTRACTOR PROVIDED HOSTING INFRASTRUCTURE

The contractor shall provide a hosting solution for all the database and web servers required for to maintain and enhance the Data Lab website except for IES Development and IES Production (as shown in Figure A-1 in Appendix A). The contractor shall comply with all additional requirements described in the ED IT Security Policy as presented in Appendix B including, but not limited to:

• obtaining a full Authority to Operate (ATO);

• performance of annual self-assessments of security controls;

• annual Contingency Plan testing;

• performance of periodic vulnerability scans;

• updating all information system security documentation as changes occur; and

• other continuous monitoring activities.

OPTION PERIOD 1:

The contractor shall complete the following tasks as described in the base period and in the DataLab Enhancement Plan described in Optional Task 16:

• Task 1 - Management

• Task 2 – Datalab Website

• Task 3 – PowerStats

• Task 4 – QuickStats

• Task 5 – TrendStats

• Task 7 – Tables Library

• Task 8 – WebVTS

• Task 9 – Data Security

• Subtask 10.1 – Posting of Data for New Studies

• Task 11 – Quality Assurance

• Task 12 - Documentation

• Optional Task 13 – Additional Datasets

Development And Technical Assistance in Leveraging Analysis Based Websites Page 15 of 48

• Optional Task 17 – Contractor Provided Hosting Infrastructure

BASE PERIOD OR OPTION PERIOD OPTIONAL TASKS

OPTIONAL TASK 18: CONTRACT CLOSEOUT AND TRANSITION

To facilitate the transition of the IT systems in this contract to the Department or another entity designated by the CO, the contractor shall maintain existing datasets and the functionality of the systems in this contract. The contractor shall deliver all data files and documentation for all the work conducted under this contract (including all tasks and exercised optional tasks). The contractor shall develop a plan to transition all the deliverables in the tasks/subtasks to another contractor. The contractor shall document the transition plan in a memorandum to the COR for approval 3 months after this option is exercised. The contractor shall submit documentation (including an EXCEL spreadsheet) to the NCES COR indicating the original task/subtask start date and end dates from the original management plan, as well as actual delivery date. The plan shall clearly outline roles and responsibilities for the new and old contractors; allow for a period of testing of the IT databases, systems, and software on IES servers (or in the new environment, if applicable); and include a date when the new contractor shall assumes responsibility for all IT development and production operations.

IX. DELIVERY SPECIFICATIONS

The specifications for all deliverables described in this Performance Work Statement are presented below. Unless otherwise specified, all deliverables should be submitted to the NCES COR via e-mail and posted in a file repository that retains all records on this contract and is accessible to NCES and contractor staff:

1.1: Monthly Progress and Financial Report and Project Schedules

The monthly report shall detail the progress made in accomplishing the project tasks and subtasks, problems encountered, and plans for the next month. By attachment, the financial status of the project shall be described, in total and by task, including detailed monthly charges by named staff and comparisons with projected spending through an Earn Value Management report (or equivalent).

The monthly report shall be due three (3) business days prior to submitting the invoice.

The monthly report shall be accompanied (after three days) by an invoice (SF No. 1034) and documentation of expenses via the Invoicing Payment Platform (IPP). The monthly report, invoice, and supporting documentation shall cover the previous month’s activities, for both the contractor and subcontractor(s). The monthly progress report and financial report shall be submitted at the same time. The Monthly and Financial report shall also be posted to the IPP website with the invoice.

For all activities within the project, the schedule shall detail the key staff assigned and the projected start and completion dates. For any monthly schedule, all completion dates shall be entered and the future three (3) month’s activities shall be described. Each month (concurrent with the monthly report) an updated schedule shall be submitted with completion dates or targeted dates for completion in a Microsoft Word or Excel file. The

Development And Technical Assistance in Leveraging Analysis Based Websites Page 16 of 48 contractor shall also document all TKPIs and document changes from a baseline date as well as the previous (3) months. Any deviations from a trend shall be noted with solutions recommended or implemented.

1.2: Security Screening, Confidentiality Documents, and Data Security Reports

Confidentiality reports shall be in three (3) parts. Part 1 shall be a list of all staff position titles with assigned risk levels (None, Low, Moderate, or High) based upon access to personally identifiable information, the Department’s IT infrastructure, or access to the Department’s buildings. Additionally, the contractor shall provide a list of all project staff, the assigned risk level associated with their responsibilities, work start date and E- QIP application status (if applicable). The contractor shall note which project staff will have access to restricted data or sensitive personally identifiable information of survey respondents. Part 2 shall be a completed (signed and notarized) set of NCES Affidavits of Nondisclosure (see http://nces.ed.gov/statprog/rudman/g.asp) for all project staff with access to restricted data or sensitive personally identifiable information of survey respondents listed (in Part 1). Part 3 shall be all the necessary paperwork related to implementing contractor employee personnel screening requirements as detailed in Appendix B.

Before the start date for the period of performance, Part 1 shall be included within the Document Repository as two Microsoft Excel spreadsheets. Each NCES Affidavit of Nondisclosure shall be completed prior to being assigned to the contract in a position with access to restricted data or the sensitive personally identifiable information of survey respondents. A copy of the completed NCES Affidavits of Nondisclosure, Part 2, shall be retained by the contractor, with originals and scanned electronic PDF copies sent to the NCES COR, as required. Part 1 shall be updated on a flow basis. Within two days following the start date of the contract, Part 3 shall be implemented for all contractor employees working on the contract within two (2) days following the start date of the contract as detailed in Appendix B. Within three (3) days that a contractor employee is no longer working on the contract, the contractor shall notify the COR that the person is no longer working on the contract, the date when employment ceased on the contract, and the reason why the person is no longer working on the contract.

The contractor shall provide a Data Security Plan as detailed in Appendix A within 30 days following the contract award date. The contractor shall not undertake any Information Technology work or have access to any of the Department’s data until a Security Plan is approved. Additionally, 60 days before any webpage or data tool is posted to a production website (excluding static state activities or new data files being added to a suite of existing data tools), the contractor shall provide to the COR an addendum to the Data Security Plan that details the specific security specifications of the website that implements redundancy in IT and physical security procedures to protect sensitive personally identifiable information, if applicable.

1.3: Agenda and DataLab Production Report

Each conference call shall be accompanied by an agenda and a detailed listing of current activities at each stage of development from inception of the idea or enhancement, through development, test, staging, and production.

Development And Technical Assistance in Leveraging Analysis Based Websites Page 17 of 48

1.4: Memorandum

Three weeks after the completion of the travel for the in-person meeting, a memorandum of findings shall be presented to the COR detailing the feedback received from the meeting, recommendations for implementing the feedback (or not), and an action plan.

The memorandum shall not exceed 5 pages, but may include attachments for reference.

2.1: DataLab IT Code Posted on the IES Production Website (Dataset Maintenance)

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the website. All components shall be operational 100% of the time (excluding periods in which the IES server is not operational). If a component of the DataLab website is not operational or functioning as designed due to a problem with the programming code or settings on the IES servers, the contractor shall immediately notify the COR via telephone and email and provide a one-page action plan to correct the problem within twenty-four (24) hours. Corrective actions shall be included in the DataLab Production Report and the Monthly report. The contractor shall clearly outline when such corrective action is beyond their immediate control (e.g., accessing secured features/control on Federal servers/websites; working with other Federal staff/contractors, etc.) and the corrective action the contractor has taken.

2.2: DataLab IT Code Posted on the IES Production Website (Browser Compatibility)

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the website. All components shall be operational 100% of the time (excluding periods in which the IES server is not operational). If a component of the DataLab website is not operational or functioning as designed due to a new browser version, a browser enhancement, or change plug-in version, the contractor shall immediately notify the COR via telephone and email and provide a one-page action plan to correct the problem within twenty-four (24) hours.

Corrective actions shall be included in the DataLab Production Report and the Monthly report. The contractor shall clearly outline when such corrective action is beyond their immediate control (e.g., accessing secured features/control on Federal servers/websites;

working with other Federal staff/contractors, etc.) and the corrective action the contractor has taken.

2.3: Computational Efficiency Report

The contractor shall randomly select estimates that external users send to the IES server through the DataLab website and submit them to the COR for review and approval. The contractor shall then re-run the estimates and record how long it takes to return output during a low use period and a peak period. The report shall include at least one of each type of estimate (e.g., percentage distribution, percentage, average, median, correlation, etc). Once the set of estimates is established and approved by the COR, the contractor shall provide baseline measures for the time it takes to return output for each type of estimate. The contractor shall report monthly on these tests until it is verified that (1) all estimations successfully provide output without obtaining an error or no response from the application and (2) there is a 20% reduction in the time it takes to yield output OR the COR approves an alternate plan to address latency (such as the use of a batch process).

Development And Technical Assistance in Leveraging Analysis Based Websites Page 18 of 48

The results shall be attached to the monthly progress report until the target metric is achieved.

2.4: DataLab IT Code Posted on the IES Production Website with Taylor Series Design Variables (or related)

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the IES production website with the option to produce standard errors using the Taylor series linearization method incorporated.

2.5: DataLab IT Code Posted on the IES Production Website with the new search engine incorporated

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the IES production website with the new search engine incorporated across components.

3.1: DataLab IT Code Posted on the IES Production Website with the New PowerStats Statistical Modules Incorporated

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the IES production website with the new PowerStats statistical modules incorporated.

3.2: DataLab IT Code Posted on the IES Production Website with the New PowerStats Output Functionality Incorporated

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the IES production website with the new PowerStats output functionality incorporated.

4.1: DataLab IT Code Posted on the IES Production Website with the New QuickStats Output Functionality Incorporated

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the IES production website w with the new QuickStats output functionality incorporated.

5.1: DataLab IT Code Posted on the IES Production Website with the New TrendStats Statistical Modules Incorporated

A current working copy of the DataLab website (and its components) shall be posted with all datasets accessible and in full operation on the IES production website with the new TrendStats statistical modules incorporated.

Development And Technical Assistance in Leveraging Analysis Based Websites Page 19 of 48

5.2: DataLab IT Code Posted on the IES Production Website with the New TrendStats Output Functionality Incorporated

A current working copy of the DataLab website (and its components) shall be…