PWS - Task Order 21.pdf

PERFORMANCE WORK STATEMENT for TASK 21: EDGE Bridge Task 21 EDGE Bridge Version Date: 2022-03-02

Task Order #: 21 – EDGE Bridge Task Order Title: Administrative Data Division Website Support Task Order Type: Firm Fixed Price Category B: 12-month base with 6-month option Performance Period: June 1, 2022 – May 31, 2023 (option June 1, 2023- November 30, 2023)

DOCUMENT STRUCTURE

I. Purpose and Overview II. Period of Performance and Task Overview III. Assumptions IV. Scope and Tasks V. Deliverables Schedule VI. Required Knowledge, Skills, and Abilities VII. Achieving a Goal of Diversity at All Levels of Staffing VIII. Pricing Schedule IX. Invoicing and Monthly Reports X. Place of Performance XI. Other Requirements XII. Government Furnished Property XIII. Confidentiality, Security, IT & Other Requirements XIV. Data Security Plan

CONTACT INFORMATION:

Doug Geverdt, Study Director and Task Leader Patrick Keaton, COR 550 12th Street, SW #4038 Washington, DC 20024 550 12th Street, SW #4036 Washington, DC 20024 Douglas.Geverdt@ed.gov (202)245-8230 Patrick.Keaton@ed.gov (202)245-7675

I. PURPOSE AND OVERVIEW

Background The purpose of this task order is to provide support for the Education Demographic, Geographic, and Economic Statistics (EDGE) program in the National Center for Education Statistics (NCES) Administrative Data Division. The EDGE program develops information resources about the social, economic, and spatial context of education in the U.S., and it collaborates with the U.S. Census Bureau to integrate data from NCES and Census collections to produce updated indicators of local educational conditions. Data produced by the EDGE program are used to determine statutory program allocations, guide program administration, support academic research, inform local and state decision-makers, and provide the public with information about local conditions that impact educational inputs and outcomes. The program relies on a variety of IT resources and project support to create, organize, analyze, compile, and disseminate an unusually large and varied data portfolio. In addition to helping EDGE support NCES’s statistical mandate (20 USC 9543), these resources are also needed to satisfy unique statutory requirements related to geospatial data (43 USC 2801). Requests and requirements for socioeconomic data, sociospatial data, and analytic resources have grown substantially over the last decade and are expected to continue evolving rapidly in the future. This PWS is intended to help the EDGE program effectively respond to these needs. Program activities support the Department of Education’s (ED) FY 2018- 2022 Strategic Goal #3 of strengthening the quality, accessibility and use of education data through better management, increased privacy protections and transparency, particularly by increasing the capacity to support education data (Strategic Objective 3.1) and by increasing access to, and use of, education data to make informed decisions both at the Department and in the education community (Strategic Objective 3.3).

mailto:Douglas.Geverdt@ed.gov mailto:Patrick.Keaton@ed.gov

Task overview The EDGE program portfolio is centered on a collection of annually updated custom datasets created in collaboration with the Census Bureau’s EDGE Branch. These data products range in content (e.g., poverty estimates and school latitude/longitude values), format (e.g., text, SAS, shapefile, raster), size (e.g., from a few thousand estimates to a hundred million estimates), and use (e.g., for academic research and federal program allocations). In addition to overseeing annual data production, the EDGE program has other activities that transcend annual production cycles. It develops and maintains data access and analytic tools; it stewards the overall collection of data products; it supports the administration of statutory education programs; it provides guidance to researchers and decision-makers; it serves as the Department’s representative on inter-agency initiatives; it designs and develops specific data and analytic solutions; and it engages in a host of other activities related to its fundamental unified program mission.

The combination of production and non-production activities can be distilled into four primary spheres of work for this task: project management, program management, data management, and systems management. Project management activities ensure that overall contract operations are executed effectively. Program management activities ensure that the content and concepts of the program mission are presented accurately and effectively.

Data management activities ensure that program data assets are appropriately designed, managed, and deployed.

Systems management activities ensure that the systems, applications, and technologies needed to manage projects, execute program mission, and effectively administrate and apply program assets are available and perform effectively. These spheres of activity are highly integrated, and most EDGE program workflows involve facets of each sphere. Consequently, this task is designed to provide support for all aspects of the EDGE program mission and all stages of the EDGE product cycles except for direct data production activities that must be done within the Census Bureau’s restricted operational environment by Census Bureau employees.

II. PERIOD OF PERFORMANCE AND TASK OVERVIEW

The period of performance for this task is 12 months (June 1, 2022 through May 31, 2023) with an option to extend the contract for an additional 6 months (June 1, 2023 through November 30, 2023). This PWS provides a framework for expected performance during the period.

III. ASSUMPTIONS

1. The Contractor must be fully prepared to perform task activities at a high level from the outset. There will not be time after the start of the contract for Contractor personnel to become familiar with the necessary content and skills.

2. The NCES Task Leader (TL) and Contractor personnel may be collectively referred to as the ‘EDGE team’ throughout this document. NCES employees working with the EDGE program and members of the Census Bureau’s Education Demographic, Geographic, and Economic Statistics (EDGE) Branch may be collectively referred to as the ‘EDGE Program staff.’

3. EDGE program activities are highly integrated and inter-disciplinary, therefore general categories used to classify work in this document reflect a dominant focus rather than exclusive activity. Most EDGE work is a fusion of unique program content expressed through various forms of data that are operationalized and experienced through various systems and technologies. As a result, NCES recognizes that the Contractor will need considerable latitude in identifying and classifying activities for contract reporting purposes.

4. Most EDGE program activities support annually updated data products; therefore, the Contractor can expect that most projects will involve ongoing work with annual cycles or projects that relate to milestones of product cycles.

5. The NCES TL will collaborate with Contract personnel to assess, clarify, and prioritize activities and requests throughout the period of performance. NCES has a dynamic operational environment and the EDGE program depends on many inputs and resources that are outside direct program control.

Therefore, the EDGE team may need to consider adjustments to anticipated products, processes, and schedules to account for changing conditions.

6. All deliverables will be provided to the TL for review and approval, and the TL will address most questions related to contract activities and administration. The TL may request that some questions be directed to the Contracting Officer’s Representative (COR) for additional clarity and guidance.

7. The NCES TL will provide access to internal databases and help to establish organizational accounts used for managing existing program operations. Draft NCES products (reports, data files, file documentation, and web sites) will be provided to the contractor on a flow basis.

IV. SCOPE AND TASKS

1 TASK 1: PROJECT MANAGEMENT

1.1 Post Award and other Meetings

The contractor shall prepare and manage scheduling, meeting logistics, development and distribution of agendas and supporting material, preparation, and distribution of meeting minutes to include proceedings, decisions, and outcomes; and follow up activities resulting from meetings. Meetings include the Post Award meeting; monthly review/update of overall EDGE program activity; monthly review/update of task-specific activities; ad hoc project meetings, and the final close-out meeting.

Within one week of contract extension award, the contractor shall initiate a kick-off meeting with relevant team members, the NCES Contract Officer Representative (COR), and NCES Task Leader. This meeting shall provide an introduction of the contractor team, overview of the contract tasks, identification of potential task-related problems and possible solutions, and the opportunity to discuss areas of concern related to the staffing plan and other management requirements. As a result, the contractor shall make any refinements to the management, staffing, and scheduling plans.

The contractor shall send meeting requests to all invitees through e-mail for all meetings associate and use a document template which combines meeting agenda, meeting minutes, and action items into a single document.

The detailed meeting agenda listing items to be discussed shall be circulated to all invitees 48 hours prior to the meeting. Feedback from attendees shall be solicited and integrated into the agenda and a final agenda shall be distributed within 24 hours of the meeting. A completed meeting document shall be disseminated to all invitees within 3 business days after the meeting.

1.2 Activity Tracking

The contractor shall use a project tracking system (such as JIRA) to capture and track project issues, including new requests and defects. They shall also collaborate with the NCES Task Leader to develop an initial project schedule of activities within 2 months of the kick-off meeting and provide a more detailed version of the actual schedule at the end of the performance period.

1.3 Usage Metrics

The contractor shall compile and provide monthly usage metrics from Google Analytics for all websites, dissemination tools, product downloads, and other relevant activities. The contractor shall also deliver an EDGE Analytics review document one month prior to the close of the contract. The purpose of the review shall be to summarize and synthesize the analytics related to EDGE data products and web applications. The review shall include a summary of key findings and program recommendations based on those findings.

1.4 Reliability Testing

The contractor shall review and test the reliability of all EDGE web pages and applications to ensure that all links and features function as intended, all tools and options rely on current data, all expected data products are available and complete, and that descriptions, references, and documents are clear, current, and accurate. The assessment will include recommendations for improving the value and relevance of the content and function of program assets. The review shall be conducted quarterly and documented using a Website Review document template. Any performance or content issues identified during the review will be logged and tracked in the project management tracking system (e.g., JIRA).

1.5 Standards

The contractor shall apply web and publication standards from ED/IES/NCES, Section 508 of the Rehabilitation Act, and other applicable standards identified by the Task Leader. The contractor shall also apply standards relevant to NCES geospatial data and metadata.

1.6 Timeliness

The contractor shall ensure all deliverables are completed by or before the scheduled delivery date. If conditions arise that may potentially delay expected deliverables, the contractor shall notify the Task Leader within 1 business day to explain the conditions and recommend potential responses. The contractor shall provide meeting summaries within 3 business days, respond to queries and concerns raised by NCES staff within 2 business days, and complete posting of data files and documentation within 5 business days of the request. The contractor shall respond to questions posed by EDGE data users within 2 days of receipt.

1.7 Documentation and Communication

The contractor shall established a SharePoint repository to archive all meeting minutes, monthly reports, and other requested documents including but not limited to the following:

Communication

Documentation Description

Kick-off meeting Meeting minutes The contractor shall introduce the project team and review the project objectives at the initial kick-off meeting. The meeting minutes shall be distributed to the project team and leadership via e-mail and posted to the ESSIN 21 SharePoint site.

Project Team Meeting Meeting minutes The project team will meet via teleconference monthly to discuss completed, current, and upcoming tasks. The meeting minutes shall be distributed to the project team and posted to the ESSIN 21 SharePoint site.

Monthly Report Monthly Task Update Report

The contractor shall draft the monthly Task Update Report, which shall include the usage metrics and a summary of the routine reliability testing. The report shall be distributed to project leadership via e-mail and posted to the ESSIN 21 SharePoint site.

Communication

Documentation Description

Task Leader meeting Task Leaders from NCES and the contractor shall meet via teleconference monthly to discuss the progress of the project.

JIRA issue notification JIRA issue history NCES staff shall receive an e-mail notification when there has been an update to an issue in JIRA (e.g., when an issue has been marked as “Ready for NCES Review”). They shall also be able to view the history of an issue from initiation through completion.

Website Review document

Details of the comprehensive website review shall be formally documented on the contractor’s Website Review document and distributed to the NCES Task Leader via e-mail.

Project schedule The contractor’ Co-Leaders shall work with NCES Task Leaders to construct and maintain the project schedule.

Project brief The contractor shall develop and maintain a brief plan for selected projects.

1.8 Supplemental Management Activities

The contractor shall initiate, manage, track, and resolve issues related to the publication review process for EDGE program products. The contractor shall use the Review Tracking System (RTS) and the NCES review process to create a reliable schedule for final product release dates.

The contractor shall also develop and maintain an updated management plan that identifies and describes the processes used to update and release all EDGE data products and tools. The contractor shall also provide diagrams, schematics, or other visualizations that identify the dependencies and integration between data products, tools, and web services. These documents shall be provided and reviewed with the Task Leader approximately every three months and included in the final report.

2 TASK 2: IT INFRASTRUCTURE

2.1 Architecture

The contractor shall work with IES’s cloud server platform and ensure that IES’s development and production servers have the capacity to support EDGE program activities, including MapED and EDGE support for other ED/IES activities. The contractor shall also provide updated schematics of the overall system architecture, including diagrams and descriptions explaining the function, purpose, and specifications of the system components.

2.2 Interface with IES

The contractor shall work with IES Web Support staff as needed to ensure the tasks are properly documented, implemented, and supported. The contractor shall also communicate with NCES about any issues in the scope of the IES Web Support environment that may impact their ability to support EDGE program activities and operations.

2.3 Operation and testing

The contractor shall ensure robust function of all existing systems and new systems by routinely performing reliability testing. This includes, but is not limited to, functionality provided by web servers; ArcGIS servers;

systems that report metadata to the ED Data Inventory and Data.gov; ArcGIS Online and Open Data organizational accounts; the Living Atlas service collection; solutions provided through the MapED portal;

integrated links between data tools; hosted solutions that support other ED programs (e.g., TRIO); BlindSIDE user accounts; and other functions related to the program’s data management and data hosting strategy.

2.4 License Management

The contractor shall update, maintain, and administrate software licenses to ensure the continuity of NCES program operations and availability of necessary resources. The contractor shall give particular attention and oversight to the ESRI license portfolio to ensure that licenses for all existing applications, extensions, libraries, templates, accounts, and other components are accessible. The contractor shall also work with IES web staff to ensure that all licensed geospatial applications and resources are promptly updated.

2.5 Application Support and Update

The contractor shall provide support to EDGE dissemination tools, including but not limited to: ACS-ED Tables, ACS-ED Maps, Demographic Dashboard, Locale Lookup, Open Data, SAFEMap, School and District Navigator, College Map, story maps, and other dissemination tools as needed. The contractor shall also maintain and update the EDGE program site, including the update of data product time series, the integration of data tools with the program site, and the update of program pages and tools with new data files.

2.6 Security and Standards

The contractor shall ensure that staff have the required security clearances and shall continue to comply with IES IT security standards in accordance with ED ICAM security expectations.

3 TASK 3: CCD COLLABORATION

3.1 CCD Integration and Collaboration

The contractor shall collaborate with CCD staff to ensure that CCD data are integrated and updated in EDGE data products, documentation, program pages, tools, and other activities as needed (e.g., the integration of select CCD items for web services of School and District Characteristics).

4 TASK 4: EDGE TECHNICAL ASSISTANCE

4.1 Maintenance/Update

The contractor shall provide support and maintenance for the EDGE program site, EDGE OpenData, MapED, and other potential sites needed to support EDGE program operations. The contractor shall also modify and create web pages to support EDGE program needs as they arise. Development requests for current and new sites may include but are not limited to:

Propose layouts and other design elements for new pages Upload and integrate new data from NCES and Census Upgrade software and maintaining necessary security features Correct potential problems related to the websites and servers Convert data (e.g., MS Word and Excel files to PDF and HTML) Review and updat all documents to ensure 508 compliance Post data files, documents, and other content to the EDGE, MapED, and Open Data sites Maintain, repair, update, and administrate web services Maintain current and legacy web content Update web pages with new content, revised text, and/or data files.

The contractor shall include a summary of all maintenance and development activities in the monthly activity report.

4.2 Data Preparation, Posting, and Dissemination

The contractor shall upload new files, convert data and documents to requested formats, post additions and make edits on the development server, push approved pages and files to production servers, create necessary data web services, and propose and implement solutions to resolve potential problems with these activities. Anticipated files include but are not limited to:

• Iterated ACS-ED custom tabulations (e.g., ST000-Totals, ST030-Children, and ST230-Parents) included for ACS-ED Tables and Dashboard

• Bulk data download and file documentation (e.g., for ST000, ST030, ST230)

• ACS-ED Special Populations tables (ST130)

• Geographic data layers (e.g., school points, district boundaries, locale boundaries, crosswalk files, SIDE raster, and others)

• Open Data web services for geospatial data layers and layers enriched with ACS data and CCD characteristics

• SIDE estimates

• Additional documents as needed

Within 15 days of a request being made, EDGE data files and documentation shall be published on the NCES development server prior to migration to the public facing server. Delivery dates are variable and shall be defined and prioritized by the Task Leader. Given the unpredictability of the Census delivery schedule, the potential need to reprioritize activities, and other previously scheduled work, developers may be unable to clear their schedule in advance of the requested updates. If potential schedule conflicts appear likely, the contractor shall inform the Task Leader and recommend potential solutions to help address and expedite the activity.

The contractor shall load data into databases and develop necessary web data services for the EDGE OpenData collection as soon after the posting of static datasets to the EDGE program site as is feasible. The team shall collaborate with the Task Leader to assess and integrate additional datasets or documentation that may be needed to augment EDGE tools or sites.

4.3 Development Activities

The contractor shall work with EDGE program staff to design, develop, review, and maintain new features and tools to support program activities. These include but are not limited to:

4.3.1 ACS District Demographic Dashboard

The contractor shall monitor the performance and use of the ACS-ED Dashboard, diagnose potential problems with the application, recommend solutions and improvements, and apply appropriate changes. The contractor shall assist EDGE program staff in monitoring data user feedback and in responding to questions about the tool, the data used in the tool, and issues related to other program tools and data products. Additionally, the contractor shall monitor changes in the Census Bureau’s ACS privacy protections that may compromise production and presentation of the ACS-ED and shall propose design changes to address potential problems this may cause.

4.3.2 Web Services for EDGE Data

The contractor shall work with EDGE program staff to develop new web services for geospatial data delivered by the Census EDGE team during the cycle and for other data sources as needed. The contractor shall define required elements, develop and include compliant metadata, provide documentation of plans/processes, and ensure that the resulting services are linked to all appropriate program applications (e.g., the EDGE program site, ACS-ED Maps, EDGE Open Data). The contractor shall continue to develop efficient strategies and workflows for managing new and existing data services and shall submit the services with appropriate metadata in common geospatial catalogues like the federal Geoplatform, the ArcGIS Online Living Atlas and others to help establish them as authoritative sources. Additionally, the contractor shall develop and provide JSON files and links for reporting the EDGE data products so they can be integrated with other ED datasets and provided to Data.gov. The EDGE geodata web services are essential for addressing the Department of Education’s obligations under the Geospatial Data Act of 2018, therefore the contractor shall design, and implement architecture and infrastructure needed to improve the performance and stability of the EDGE web service collection.

4.3.3 SIDE and BlindSIDE

The contractor shall modify the EDGE program site to accommodate new SIDE-related data files and documentation and shall also create web services to disseminate and visualize the SIDE school neighborhood poverty data through existing EDGE mapping tools and Open Data. The contractor shall continue working with EDGE program staff to design and maintain the functionality of the BlindSIDE assignment engine and to develop processes that effectively manage and monitor the tool as it gets used by testers. The contractor shall support the EDGE staff and SLDS grantees as they continue to test the experimental assignment solution and analyze the resulting estimates. This may include responding to geocoding questions; assisting participants with issues related to BlindSIDE assignments, and submitting school-level data to NCES; explaining processes related to IPR estimation and the neighborhood assignment process; and various other procedural and analytic issues. Additionally, the contractor shall maintain the necessary security features of the BlindSIDE login/account system and provide administrative support for data user questions and issues related to the system.

The contractor shall ensure the SIDE and BlindSIDE resources are updated and accessible to program participants. NCES may need to implement revisions to the estimates layer or other data inputs on short notice, therefore the contractor needs to schedule resources in a way that allows for rapid response to any changes.

4.3.4 Census and Data User Support

The contractor shall work with the Census EDGE staff to administrate the delivery and review of data, analytic, and reference products developed for NCES. The contractor shall confirm to the NCES EDGE staff when reviews are complete and when the product is available in the IES Development environment for final review. In addition to reviewing the data deliveries, and housing the deliveries in appropriate databases, the contractor shall collaborate with Census EDGE staff to review data updates to the program’s public data tools. In the case of new products, the contractor shall coordinate with the NCES EDGE staff to initiate and monitor a new product record in the Review Tracking System (RTS). The contractor shall also monitor the EDGE mailbox and work with NCES staff (and potentially Census staff) to respond to data user questions and requests.

4.3.5 ACS-ED Maps

The contractor shall monitor the performance and use of the ACS-ED Maps tool and work with EDGE program staff to diagnose potential problems and apply appropriate changes to the application. The contractor shall assist EDGE program staff in monitoring data user feedback and in responding to questions about the tool, the demographic and geographic data used in the tool, and other issues related to program tools and data products.

The contractor shall develop a project plan with procedures and expectations for annually updating the ACS-ED estimates, the school point files, and the boundary layers required for the tool.

4.3.6 Locale Lookup

The contractor shall monitor the performance and use of the Locale Lookup tool and shall work with EDGE program staff to diagnose potential problems and apply appropriate changes to the application. The contractor shall assist EDGE program staff in monitoring data user feedback and in responding to questions about the tool, the data used in the tool, and other issues related to program tools and data products. The 2020 decennial census collection will result in a new delineation of urban areas that will require changes to the locale framework and documentation and will result in fundamental changes to the locale data. The contractor shall work with the

EDGE program team at NCES and Census to plan a strategy for effectively addressing these changes and integrating the new locale boundaries. Additionally, the contractor shall assist in analyzing changes in locale assignments resulting from the 2020 delineation and in developing a strategy to effectively communicate those changes to data users and stakeholders who may be impacted by the updated assignments.

4.3.7 Title I Data Support

The contractor shall work with EDGE program staff to support the data needs of the Title I program. Title I is the largest Elementary/Secondary program in the Department with annual state allocations of $16B.

Additionally, the Title I school district poverty estimates are used as an eligibility criterion in a variety of other federal and state statutory education programs, and they played a significant role in the distribution of COVID relief funding passed by Congress in FY20 and FY21. Therefore, the overall impact of the data extends well beyond the direct Title I allocation. The contractor shall coordinate with the EDGE staff to identify key operational milestones for the FY22 data cycle and shall work with the EDGE staff to review data deliveries from the Census Bureau’s Small Area Income and Poverty Estimates (SAIPE) program, including deliveries of school district boundaries. In addition, the contractor shall provide supplemental support for other necessary activities such as NCES’s mass mailing outreach for the annual School District Review Program and developing a geographic association file between Vermont’s school district and supervisory union boundaries to support fiscal data allocations needed for Title I grant assessments.

4.3.8 School District Poverty

The contractor shall work with EDGE program staff to support the inclusion of additional school district poverty data into the EDGE product portfolio. This may include activities like developing and extending data time series, developing analytic products with documentation to help data users understand how poverty estimates are produced and why they are important, developing additional web services to improve the accessibility of poverty data, and other relevant activities that support this critical data resource.

4.3.9 Product planning, messaging, and data user support

The contractor shall assist EDGE program staff in planning, drafting, and publishing social media content to announce product releases and highlight product content. The contractor shall ensure that the comment and content is communicated effectively and shall be responsible for monitoring the review process to ensure timely posting. Additionally, the contractor shall draft instructional guidance to support the use of EDGE tools and shall work with EDGE program staff to collect, develop, and curate material to promote careful and effective analysis of spatial data. The contractor shall assist EDGE program staff in responding to questions related to the EDGE program and the program’s data products and shall regularly review and develop program metrics from Google Analytics and other relevant sources to anticipate necessary adjustments to program operations, the product portfolio, and tool functionality. The contractor shall also monitor the NCES EDGE mailbox and respond to inquiries within two days or forward to the appropriate NCES point of contact.

4.3.10 Navigator

The contractor shall assist EDGE and CCD program staff in updating the Navigator application to make more effective use of the tool and the supporting API. The contractor shall use available analytics to assess current functionality; recommend and prioritize potential changes; implement recommendations; develop necessary documentation; and provide other related design assistance as needed.

4.3.11 Enhance documentation related to Educational Geography The contractor shall work with EDGE program staff to identify significant issues and conditions related to educational geography and spatial analysis, and collect resource materials (e.g., journal articles, bibliographies, book reviews, websites, product documentation, briefings, instruction, product reviews) that provide useful background related to these issues.

5 TASK 5: MAPED TECHNICAL ASSISTANCE

5.1 Website Maintenance, Data Preparation, and Posting

The contractor shall continue to provide technical assistance for the EDGE MapED site and continue to recommend changes and additions to help curate and enhance the collection of resources.

5.2 Update and Development Activities

5.2.1 Maintain and expand MapED portal

The contractor shall continue to update, expand, administrate, and manage the MapED portal. The contractor shall also continue to work with EDGE program staff to recommend changes and additions to help curate and enhance the collection, and to develop resources about the use GIS, geospatial data, and spatial analysis in educational research and program administration.

5.2.2 Expand, administrate, and manage the NCES geodata web service library The contractor shall continue to update, expand, administrate, and manage NCES’ data web service library.

Administrative tasks include (but are not limited to) maintenance of the EDGE data library summary document, authoring and updating the publishing process for each data file, and updating EDGE program staff on the performance and capacity of the IT infrastructure used to support EDGE/MapED web services. At the conclusion of this contract, the contractor shall submit a final report to NCES that describes and summarizes the web service library collection.

5.2.3 Maintain and expand Open Data

The contractor shall continue to update the Open Data portal with new web services and documentation based on updated data products. These services shall continue to include FGDC compliant metadata, and all services shall be populated with appropriate title, tags, descriptions, and thumbnails.

5.2.4 Assist with requests related to other mapping applications The contractor shall assist the EDGE staff as it attempts to respond to requests by other programs to develop or include ESRI-based mapping applications in the MapED environment. This may involve additional oversight and administration of the MapED portal and the ArcGIS Online organizational account. This may also involve recommendations and guidance related to developing new applications with the existing platform or potential interactions with other data formats or platforms (e.g., QGIS, MapBox, OpenStreetMap).

5.2.5 Shift legacy data users

The contractor shall continue to redirect users of legacy data products to more current EDGE resources and to assist data users with questions and inquires related to the changes.

5.2.6 Geospatial data planning and reporting

The contractor shall work with EDGE program staff to develop content and documentation needed to help respond to federal geospatial data requirements. This may involve review of agency guidance, federal statutes, and various other sources. The contractor shall assist NCES in responding to internal and external requests related to geospatial data and shall provide EDGE staff with recommendations for managing and improving the portfolio of EDGE geospatial data. In addition, the contractor shall assist EDGE program staff in researching and responding to program requests posed as part of the biennial GDA program audits and FGDC reporting requirements.

OPTIONAL TASK 6: CONTRACT TRANSITION ACTIVITIES

Many EDGE projects are on-going activities that require operational continuity and stability at the time of a new contract award, therefore, the Government may decide to implement a transition period if funding is available. The transition period would allow the current contractor to conduct information sessions with new contractors and verify that existing processes and procedures are clearly documented and ready for handoff to support a smooth transfer of contract work. The contractor will provide materials to the Government that include (but are not limited to): procedures for processing, managing, and disseminating all data products and web services; procedures for administrating software and server licenses; procedures for updating and maintaining registered services; procedures for monitoring and maintaining program servers and interactions with IES Web Support staff; procedures for assessing program analytics; procedures for accessing and administrating all administrative accounts; project and product schedules; procedures and heuristics for managing program databases; and other administrative materials to support a stable transition. The incumbent will compile these materials into a project plan and make them accessible on a shared workspace to program staff and other members of the transition team. This optional task is expected to require a mix of staff time from directors, deputy directors, project managers, programmers, analysts, and other members of the incumbent staff that support program activities. If a transition period is necessary, the Period of Performance will be 90 days prior to the end of the contract. The transition period, if implemented, would not affect the contract periodicity described in this task order.

V. DELIVERABLES SCHEDULE

Delivery Contacts The Contractor will make deliverables available to the Task Leader and COR.

Deliverable Number Activity Deliverable Estimated Due Date Task 1 Project

Management

1. Provide project schedules

2. Monthly report on site metrics

3. Bi-monthly summary of reliability testing

4. Schedule kick-off, close-out, and monthly meetings

5. Manage meeting logistics and provide documentation

6. Monitor all activities in a shared tracking system

7. Project briefs; final compilation of project briefs

8. Final summary project report

9. Manage and respond to data user inquiries

10. Identify, track, and summarize potential legislative data requirements with recommended responses

11. Management plan that discusses integration of CCD, IPEDS, and

EDGE

1. Within 2 months of start

2. Monthly (per meeting schedule)

3. Bi-monthly (per meeting schedule)

4. Ongoing – Within 5 days

5. Ongoing – Within 2 days

6. Ongoing (throughout period)

7. Ongoing; one month prior to close

8. Half of payment shall be made with receipt of draft.

Final payment shall be made upon final report.

Due date is one month prior to close

9. Ongoing; within 2 days of contact

10. Ongoing; summarize within 2 weeks;

recommendations within 4 weeks

11. Quarterly

Deliverable Number Activity Deliverable Estimated Due Date Task 2 IT

Infrastructure

1. Systems diagrams; Final systems diagrams

2. Acquire, update, and maintain application licenses

3. Update and maintain robust systems/architecture

1. Ongoing; one month prior to close

2. Ongoing; update within 10 days

3. Ongoing; respond within 2 days

Task 3

CCD

Integration

1. Update and maintain CCD data elements in EDGE data products

1. Ongoing; update within 10 days

Task 4 EDGE Technical Assistance

1. Update and maintain EDGE program site

2. Update files for ACS-ED Tables and Dashboard; modify tool as needed

3. Update geodata files, web services, metadata, and documentation for Open Data layers

4. Update SIDE data and services.

5. Support BlindSIDE pilot for SLDS and others

6. Ingest, review, and track data deliveries; revise Dashboard presentation

7. Update files for ACS-ED Maps and Table tools; support and modify tool as needed

8. Update files for Locale tool; modify tool as needed

9. Review and support Title I data activities

10. Update files and content for public school district poverty data

11. Monitor and respond to EDGE mailbox; Product planning, messaging, and data user support;

Update web analytics for EDGE, MapED, and Open Data

12. Update and improve Navigator

13. Enhance educational geography documentation

1. Ongoing; within 7 days of request

2. Within 15 days of file availability; Ongoing and within 21 days of request

3. Within 15 days of file availability

4. Within 15 days of request

5. Ongoing; within 3 days of request

6. Within 15 days of file availability

7. Within 15 days of file availability; Ongoing and within 21 days of request

8. Within 15 days of file availability; Ongoing and within 21 days of request

9. Ongoing; within 3 days of request

10. Within 15 days of file availability or request

11. Within 2 days; Ongoing;

Monthly (per meeting schedule)

12. Ongoing

13. Ongoing

Task 5 MapED Technical Assistance

1. Update and maintain MapED site

2. Update and administrate library of geodata web services

3. Update and maintain Open Data

4. Assist with requests related to

MapED additions

5. Support geospatial data requirements

1. Ongoing

2. Ongoing; within 15 days of file availability

3. Ongoing

4. Within 15 days of request;

ongoing as needed

5. Within 15 days of request;

ongoing

Deliverable Number Activity Deliverable Estimated Due Date Task 6 (Optional)

Contract transition activities

Proposed response to each request; data products that meet the need of the request

Within 14 days of receipt from the Task Leader

VI. REQUIRED KNOWLEDGE, SKILLS, AND ABILITIES

The Contractor will provide personnel and resources needed to lead and perform the activities described in this task. The Contractor will ensure that all personnel assigned to these efforts are fully qualified and do not require additional training to meet the performance requirements.

Replacement The Contractor will provide written notice of proposed staff replacements at least two weeks prior to the change.

This notice will be provided to the TL and COR with a detailed justification, an assessment of potential impact, and a proposed substitution, so that the TL can evaluate potential program implications. All resumes of proposed replacement staff must be provided and approved by the COR and TL.

Position Risk The table below provides the risk level for categories of staff who may bill to this contract. The contractor will use the position titles below in contractor personnel listings submitted to the Department.

Position title Risk Level Justification Program Manager (Task Leader) Low No exposure to PII GIS Project Manager Low No exposure to PII Senior Developer Low No exposure to PII Developer Low No exposure to PII Senior GIS Developer Low No exposure to PII GIS Developer Low No exposure to PII Senior Designer Low No exposure to PII Senior GIS Analyst/Researcher Low No exposure to PII GIS Analyst/Researcher Low No exposure to PII Subject Matter Expert Low No exposure to PII Content Area & Assessment Specialist Low No exposure to PII

VII. ACHIEVING A GOAL OF DIVERSITY AT ALL LEVELS OF STAFFING

The contractor, to the extent possible, will provide staffing diversity represented at every level of professional responsibility. The purpose of this requirement is to ensure that important perspectives that might otherwise be overlooked be brought to light so as to better serve all the constituencies that have a stake in program products. These diverse perspectives may be based on gender, race/ethnicity, and educational qualifications.

VIII. PRICING SCHEDULE

The Contractor will submit to the Government an invoice for the hours worked during the preceding month.

The Government will take into account the deliverables produced and the status of ongoing work in accepting or rejecting the monthly invoice ensuring that level of effort is commensurate with work hours.

IX. INVOICING AND MONTHLY REPORTS

In accordance with the invoicing clause set forth in the contract, the contractor shall submit to the Government an invoice for the deliverables that were submitted to and accepted by the Government during that month. The invoice shall be submitted to via Internet Processing Platform (IPP).

The Contractor will invoice for individual subtasks to assist with contract management and the large number of related deliverables. The Contractor will bill for certain deliverables only after the deliverable has been submitted and approved by the Government, as specified below:

Along with the invoice, the contractor shall submit monthly reports on or before the 10th of each month. The monthly reports are to be submitted via electronic transmission. The monthly report shall be submitted to the COR, Task Leader, and Contract Specialist. The report shall include the following:

1. The progress on each task and activity relative to the schedule and a discussion of discrepancies.

2. Accomplishments associated with each task and activity for the month.

3. Problems that have been resolved or need resolution.

4. A discussion of the work to be performed during the next monthly reporting period.

5. The number of hours expended by all contractor staff by staff person.

6. The number of hours expended by all subcontractor staff by person.

7. Brief description of the work performed by each subcontractor during the month.

8. Funding expended by major category, including staff, travel, consultant, subcontractors, and other costs, including obligated costs of subcontractors.

9. Expected future technical and budgetary problems and proposed solutions to these.

10. Each monthly report will include a section titled, “Security Clearance” that identifies the following:

(a) each staff person or subcontractor who has been added to the contract during the month who will require a Security Clearance; (b) the level of Clearance required and the date the Security application was submitted to NCES; (c) the name of each staff person or contractor who left the contract during the month and the date of separation. If the person held a Security Clearance, identify the level of Clearance and position they held while employed under the contract. If there are any outstanding Clearance issues for which the contractor is awaiting a response from the government, identify those. If there are no Security Clearance submissions or related changes during the month, clearly state this.

X. PLACE OF PERFORMANCE

The contractor will perform the majority of the work in this task at contractor provided off-site facilities.

XI. OTHER REQUIREMENTS

Confidentiality The Contractor will implement such confidentiality and security provisions as NCES may require.

Pursue subject matter experts The Contractor will pursue support from recognized experts if needed to support the EDGE program mission.

Plan and convene events, workshops, etc.

The Contractor will assist the EDGE TL in planning and hosting conversations, meetings, and other interactions with individuals in federal agencies, state and local agencies, academic institutions, non-profits, and other relevant organizations or institutions to support the program mission

XII. GOVERNMENT FURNISHED PROPERTY

At the initial meeting the government will supply the NCES Statistical Standards, NCES Tabular Guidelines, NCES and IES Style Guides, and the electronic versions of Reviewing NCES Reports—Statistical Research Assistants, Reviewing NCES Reports—Technical Reviewers, and the electronic NCES Reviewer Template; the existing data bases for use in monitoring data quality and for monitoring the use of NCES data.

XIII. CONFIDENTIALITY, SECURITY, IT & OTHER REQUIREMENTS

IES Confidentiality of Individuals and Institutions NCES assures participating individuals and institutions that any data collected conforms to the IES standards for protecting the privacy of individuals as required by Section 183 of the Education Sciences Reform Act of 2002 (P.L. 107-279): “. . . all collection, maintenance, use, and wide dissemination of data by the Institute, including each office, board, committee, and Center of the Institute, shall conform with the requirements of section 552A of Title 5, United States Code [which protects the confidentiality rights of individual respondents with regard to the data collected, reported, and published under this title].” (Section 183)

Under the Education Sciences Reform Act of 2002 (ESRA 2002), all individually identifiable information about students, their families, and their schools shall remain confidential. To this end, this law requires that no person may:

1. Use any individually identifiable information furnished under the provisions of this section for any purpose other than statistical purposes for which it is supplied, except in the case of terrorism;

2. Make any publication whereby the data furnished by any particular person under this section can be identified; or

3. Permit anyone other than the individuals authorized by the Commissioner to examine individual reports.

Further, individually identifiable information is immune from legal process, and shall not, without the consent of the individual concerned, be admitted as evidence or used for any purpose in any action, suit, or other judicial or administrative proceeding, except in the case of terrorism. Employees, including temporary employees, or other persons who have sworn to observe the limitations imposed by this law, who knowingly publish or communicate any individually identifiable information will be subject to fines of up to $250,000 or up to 5 years in prison, or both (Class E felony).

Data Protection and Security The confidentiality of individually identifiable information contained in project documents, data, and other information supplied by the National Center for Education Statistics, U.S. Department of Education (the Department) or information acquired in the course of performance under this contract where the information was furnished under the provisions of Section 183 of the Education Sciences Reform Act of 2002 is a material aspect of the contract and must be maintained, secured, and protected from disclosure as provided in Section

183. The Privacy Act of 1974 (5 U.S.C. 552a) also applies.

The contractor shall enforce strict procedures for assuring confidentiality. These procedures shall apply to all phases of the project and should include but not be limited to: information used to locate study respondents, data collection in the field, coding and editing phases of data prior to machine processing, safeguarding response documents, and maintenance of any respondent follow-up information. Contractor shall physically separate the identifying data required for any follow-up from data required for research purposes.

The contractor shall be familiar with and comply with:

1. The Privacy Act of 1974 (5 U.S.C. 552a),

2. Confidentiality Information Protection and Statistical Efficiency Act (CIPSEA) of 2002 (P.L. 107-347, Title V, Subtitle A, “Confidential Information Protection”),

3. Family Educational Rights and Privacy Act (FERPA) (20 U.S.C. 1232g; 34 CFR Part 99),

4. The Freedom of Information Act (5 U.S.C. 552),

5. Part C of the Education Sciences Reform Act of 2002 (P.L. 107-279),

6. Part E, Section 183 of the Education Sciences Reform Act of 2002 (P.L. 107-279),

7. No Child Left Behind Act (20 U.S.C. 70),

8. USA Patriot Act of 2001 (P.L.