PWS.pdf

Part 5 Specific Tasks The contractor shall provide services for:

5.1 Task 1 Management

The contractor shall manage the contract in an efficient manner that fosters communication with contractor staff, the NLS Contract Officer’s Representative (COR), the Department’s Contracting Officer (CO), the Department’s Contracting Specialist (CS), the NLS project staff, and data users.

5.1.1 Subtask 1.1 Management and Staffing Plan

The contractor shall submit for approval of the COR a detailed management and staffing plan that will ensure the effective accomplishment of all NLS tasks. The plan shall focus on how the contractor will hire, train, and maintain staff, manage day-to-day survey operations, and coordinate activities to prevent problems and bottlenecks and resolve problems as they occur.

The plan shall include scientific staff who are experienced in conducting and publishing social science research using longitudinal data, especially labor market activating over the life course, and have experience designing surveys. The scientific staff shall:

• Assist the NLS program on survey content and design issues, especially during design and planning. They may be asked to provide written feedback on content and attend ad-hoc design meetings conducted in-person or virtually.

• Coordinate with existing and potential survey stakeholders in the government, non-profit and private sectors on the development of survey topics, questions, and methods and use the NLS survey data.

The plan also shall include a detailed timeline for all activities that will take place over the course of this contract. The timeline shall include the dates of each milestone and describe the dependency relationships between various activities. Approval of the plan will depend on whether it provides for qualified staff and the efficient, effective training of all Contractor staff in the project’s objectives and the administration of the surveys.

Deliverables, Timing, and Submission

5.1.1 Management and Staffing Plan:

The contractor shall submit the management and staffing plan 45 business days after the effective date of this contract. Management and staffing of the Field Interviewers (FIs) and managers shall be addressed in Survey Procedures Plan.

5.1.2 Subtask 1.2 Document and Data Transfer sites

The contractor will utilize BLS provided MFT (currently Kiteworks MFT) and SFTP (securetransfer.bls.gov) for the secure managed transfer of data and documentation between contractors and BLS.

Deliverables, Timing, and Submission

5.1.2.1 Kiteworks

The BLS-approved instance of Kiteworks will be used to transfer materials between the contractor and NLS staff for NLS approval of materials.

5.1.3 Subtask 1.3 Records Management

Records management plays a critical role in transparency and open government consistent with law and policy, to disclose information rapidly in forms that the public can readily find and use. This includes records created by the NLS program, the secure storage, maintenance, and accountability of these records, and the proper use and final disposition of these records.

Contractor shall comply with all applicable records management laws and regulations, as well as National Archives and Records Administration (NARA) records policies, including but not limited to the Federal Records Act (44 U.S.C. chs. 21, 29, 31, 33), NARA regulations at 36 CFR Chapter XII Subchapter B, and those policies associated with the safeguarding of records covered by the Privacy Act of 1974 (5 U.S.C. 552a). These policies include the preservation of all records, regardless of form or characteristics, mode of transmission, or state of completion.

In accordance with 36 CFR 1222.32, all data created for government use and delivered to, or falling under the legal control of, the government are Federal records subject to the provisions of 44 U.S.C.

chapters 21, 29, 31, and 33, the Freedom of Information Act (FOIA) (5 U.S.C. 552), as amended, and the Privacy Act of 1974 (5 U.S.C. 552a), as amended and must be managed and scheduled for disposition only as permitted by statute or regulation.

In accordance with 36 CFR 1222.32, the contractor shall maintain all records created for government use or created in the course of performing the contract and/or delivered to, or under the legal control of the government and shall be managed in accordance with Federal law. Electronic records and associated metadata must be accompanied by sufficient technical documentation to permit understanding and use of the records and data.

NLS Program Office records management is aligned with the 36 CFR 1220.324 which is to ensure agencies must create and maintain authentic, reliable, and usable records and ensure that they remain so for the length of their authorized retention period. The NLS follows Statistical Programs Bucket Schedule N1-257-11-1, which was approved by NARA on January 29, 2013. The National Archives and Records Administration (NARA) provides mandatory instructions on how and when to maintain and dispose of operational records

1. Survey Methodology Files

• procedural manuals,

• technical memorandums,

• all data collectors’ training materials for both Field Managers (FMs) and FIs,

• FI CATI manuals,

• FI training starter Kits,

• communication related to survey issues (such as discussions about sample representativeness, interview sample priorities etc.)

• all contractor discussions with Principal Investigators (PIs)

2. Program Subject Files

• planning documents,

• internal explanatory statements regarding objectives, strategy, and methodology,

• monthly progress reports,

• documentation related to any procedural problems and recommendations,

• study reports or other methodological or analytical statements used in reviewing or revising procedures or operational processes,

• weighting plans,

• created variable plans, and

• geocode plans

3. Permanent Output Database Files

• full public use data set without PII, in asci, with associated programs to read said asci data set

• NLS Users guides in electronic form,

• data codebooks

• Questionnaires

5.1.3.1 NLSY97 R 24 Submission of Contractor Records

Contractor survey methodology files, program subject files and public use output database: Records will be submitted in electronic form 14 months after the end of data collection upon release of the public use dataset in a FIPS 140 compliant manner.

5.1.4 Subtask 1.4 Monthly Progress Reports

Although monthly reports shall be used to document problems encountered in addition to proposed solutions, the contractor shall not wait to communicate problems to the COR in the monthly report.

The contractor shall inform the COR of challenges being faced on a flow basis as challenges arise.

5.1.4. Monthly Progress Report

The monthly report shall be submitted by electronic transmission. It shall be due on the 5th day each month (or next business day if the date occurs on a weekend or Federal holiday).

5.1.5 Subtask 1.5 Management Conference Calls

The contractor shall prepare for and participate in conference calls with the NLS Director, COR and other BLS staff on a regular basis to discuss survey operations. These calls may occur every one to two weeks as needed and agreed upon by the COR and contractor. The contractor can expect a typical call to last one hour or less. The contractor shall distribute the minutes of the prior conference call with the agenda for the next call.

5.1.5.1 Meeting Agenda

The contractor shall distribute the agenda and all supporting materials to call participants at least one workday prior to the meeting.

5.1.5.2. Meeting Minutes

The contractor shall distribute the minutes of the prior conference call with the agenda for the next call.

5.1.6 Subtask 1.6 Quarterly Survey Management and Design Meetings The contractor shall prepare for and participate 4 times yearly to discuss the management of the NLS program, as well as the design of questionnaires and procedures for future administrations of each survey. The length of these management meetings generally shall be limited to one day each unless otherwise agreed upon by the COR and contractor. Three meetings shall take place by telephone, video conference or other electronic means and one meeting per year will be in person, unless otherwise agreed upon by the COR and contractor.

At these meetings, staff from BLS and the contractor and other invitees shall discuss general administration of the NLS program and each individual survey, as well as design and methodological issues for each survey. Topics for the management portion of each meeting may include a discussion of costs and current and anticipated budgets, survey operations, the status of contract deliverables, program timelines, initiatives to improve services to data users, and other topics.

Prior to each meeting, the contractor shall determine which of its staff members are expected to attend, and the contractor shall inform the NLS Director of the expected attendees. The NLS Director and Contractor also shall decide whether other persons besides BLS and contractor staff shall be invited to attend. The contractor shall suggest potential agenda items at least 4 weeks before the meeting. The contractor shall distribute meeting materials requested by the COR 3 days prior to the meeting.

The COR shall distribute the agenda approved by the NLS Director and all supporting materials to meeting participants at least two workdays prior to the meeting. The contractor shall submit the minutes of each meeting to the NLS Director and COR within one week after the meeting. The minutes shall summarize the discussion, focusing on decisions made, problems identified, and activities to be performed, including a designation of the responsible party and the due date.

Deliverables, timing and submission

5.1.6.1 Contractor provided Quarterly Management Meetings (QMM) meeting topics Agenda topics shall be submitted to the COR 4 weeks prior to the QMM.

5.1.6.2 Contractor provided meeting materials

The contractor shall provide COR requested meeting materials 3 days prior to the meeting.

5.1.6.3 Meeting minutes

The contractor shall take the minutes at the NLS QMM and submit them to the COR for review within one week after the meeting.

5.1.7 Subtask 1.7 Providing Input Services

Survey programs with the scope, complexity, and importance of the National Longitudinal Surveys require input from a large number of individuals and organizations to address the data needs of researchers and policymakers. The NLSY79 and the NLSY97 surveys will have a Principal Investigator (PI), responsible for providing input to NLS on the content and methodology of the survey and promoting the survey to the academic community. All final decisions shall be made by the BLS.

The Contractor shall arrange a Principal Investigator for the NLSY79 and the NLSY97, per the approval of the NLS Director. The Principal Investigator shall have considerable experience conducting and publishing social science research using longitudinal and/or survey data and should have experience designing surveys or other data collections as well as presenting scholarly research to the data user community. The duties of the Principal Investigator shall include providing input to the NLS Director, BLS staff, and members of the research and policy communities to identify appropriate topics to include in each survey. All final decisions shall be made by the BLS.

The Principal Investigator shall provide input to staff members from the Contractor and BLS, on the development of survey questionnaires and methods. The Principal Investigator shall provide input to the BLS on how best to promote the use of survey data among researchers and policymakers. All final decisions shall be made by the BLS.

Deliverables, timing and submission

5.1.7.1 The Contractor shall provide a list of potential Principal Investigators for the NLSY79 and the NLSY97 these shall be delivered within three months of the NLS Director’s request. Selection will be made by the vendor with the approval of the NLS Director.

5.1.7.2 PI Guidance for Surveys

The PI for each survey shall advise the program on survey content and design issues, in particular during the design and planning phases of each Round. They will be asked to provide written guidance for content changes and attend ad-hoc design meetings conducted by phone, or teams meetings. Guidance on what sections to cut, add or modify shall be provided 2 weeks before the first design and planning meeting.

5.1.7.3 Liaison with Stakeholders: written summary at QMMS

Each PI shall coordinate with existing and potential survey stakeholders in the government, non-profit and private sectors on the development of survey topics, questions, and methods. A written summary of these activities shall be presented at each Quarterly Management Meeting (QMM).

5.1.7.4 Report on Survey Promotion

Each PI shall advise the BLS and Contract staff on how best to promote the use of NLS survey data.

They shall provide written recommendations during the 3rd quarter QMM [Summer, July].

5.1.8 Subtask 1.8 Errata

The contractor shall correct all errors and problems that are discovered in any data files. The contractor shall investigate all questions that arise concerning suspected errors in the data or the documentation. As errors are discovered, they shall be corrected and the contractor shall make such corrections available to researchers by posting the corrected data on the nlsinfo.org website. With permission of the COR, revisions may be delayed and included in conjunction with the release of an additional round of data. Where there is a lack of clarity, apparent inconsistencies or omissions, or similar problems relating to the documentation, these problems also shall be corrected, and such corrections shall be provided to NLS users.

Within 5 business days of finding an error, email notification to COR and NLS Director with description of error, proposed remediation strategy and timing using an Errata form. The Errata form shall include:

• Cohort and either Public Use or Restricted,

• Who Discovered the Issue

• How the issue was Discovered

• Date Issue was reported

• Variables and Rounds Affected

• Description of Issue

• Proposed solution

NLS must approve the solution.

5.8.1 Errata Identification & Remediation

Within 5 business days of finding an error, email notification to COR and NLS Director with description of error, proposed remediation strategy and timing using BLS provided Errata form.

5.8.2 Corrected Data available for Users

After approval by BLS: Notification of error description and corrected variables placed in errata section of the website within 1 week of approval or complete reload of data if deemed necessary by the NLS Director or COR.

5.2 Task 2 Technology and Security Requirements for BLS Data and Systems The confidentiality of individually identifiable information contained in project documents, data, and other information supplied by the National Longitudinal Surveys Program, Bureau of Labor Statistics (BLS), U.S. Department of Labor, or information acquired in the course of this contract must be maintained, secured, and protected from disclosure as provided. The contractor shall maintain the confidentiality, integrity, and availability of all BLS data and systems and their associated hardware, software, and processing capabilities. The contractor shall develop and implement a security program, as approved by the COR, and designate an information security point of contact, to fulfill all security requirements under this contract.

The contractor shall enforce strict procedures for assuring data confidentiality and security. These procedures shall apply to all phases of the project and shall 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.

The contractor shall physically separate the identifying data required for any respondent follow-up from data required for research purposes.

5.2.1 Subtask 2.1 Confidentiality Training Requirements

BLS assures participating individuals that any information collected is protected in accordance with the Confidential Information Protection and Statistical Efficiency Act (CIPSEA), the Privacy Act, and other applicable Federal Laws.

Due to the possible exposure to information protected by law under CIPSEA, the BLS shall, in accordance with this contract, designate contractor employees with exposure to BLS confidential information (NLS data) as agents of the BLS. All such agents are subject to the fines and penalties under 44 USC Section 3572 of CIPSEA and any other fines and penalties that apply to the mishandling of confidential information. The obligation to protect information extends to all CIPSEA-and Privacy Act-protected information including, but not limited to, information previously collected by the BLS and provided to the contractor in order to perform work under this contract, information collected on behalf of the BLS under this contract, and any work that may involve comingling or otherwise using CIPSEA-protected information alongside other data, such as supplemental survey information (e.g., 79 Young Adult).

The contractor shall provide the contract employees with instructions on maintaining the security of all confidential information in accordance with this contract and applicable requirements outlined in the attachment “BLS Confidentiality and Security Requirements”. Such instructions are subject to the review and approval of the BLS upon request.

Deliverables, Timing and Submission:

5.2.1.1 Potential BLS Agent List:

Within 30 days of contract award, the contractor will furnish to the BLS a list of contractor employees who the contractor believes require access to BLS sensitive information in order to perform work on the contract. Contractor employees must become BLS agents and complete the BLS Confidentiality Training to access the NLS system or BLS sensitive information.

5.2.1.2 Annual Training Recertification Reports:

For the life of the contract, all BLS agents currently working this contract during the recertification period will take confidentiality training at least once a year. This annual recertification will begin in the summer and end by September.

5.2.1.3 BLS Agent Status Worksheets:

The contractor will keep records on current Agent designations and will report such information promptly to the COR upon request, but at least Quarterly (Oct 1, Jan.1, April 1, July 1). BLS will provide an excel worksheet for this process.

5.2.2 Subtask 2.2 Annual Self Security Assessment (SSA)

As part of ongoing Assessment and Authorization (A&A) activities, a Security Self-Assessment (SSA) is conducted annually. The NLS contractor and subcontractors are expected to assess mandatory managerial, operational, and technical elements. The NLS contractor and subcontractors are expected to cooperate with BLS staff to coordinate interview schedules; provide applicable documentation or copies; and set up time for observation of applications to demonstrate application functions and controls. The contractor shall support security inspections conducted by government auditors or other government representatives, as designated by the BLS, at no additional cost. The contractor shall permit security inspections of its approved worksites, system configuration, and operating environment to ensure a secure operation and protection of Federal information processed by any system or operation supporting BLS data collection or processing.

Deliverables, Timing and Submission:

5.2.2.1 NLS Partial System NIST Security Self-Assessment, (Annual) In a Controls Audit, the contractor will show compliance on a subset of NIST controls selected by Department of Labor Office of the Chief Information Officer.

5.2.3 Subtask 2.3 Full NIST Security Controls Assessment (SCA) The Security Controls Assessment (SCA) is conducted every 3 years, at a minimum, as part of the Assessment and Authorization process. Staff from BLS or a third-party contractor will assess the managerial, operational, and technical elements, completing a full FISMA audit of all applicable NIST 800-53 controls for a Moderate system. The NLS contractor and subcontractors are expected to cooperate with the Security Controls Assessment team to coordinate interview schedules; provide applicable documentation or copies; and set up time for observation of applications to demonstrate application functions and controls. The next SCA of the NLS system supporting Ongoing Authorization will occur in the early spring of 2029.

Deliverables, Timing and Submission:

5.2.3.1 NLS Independent Full System Audit

At least every 3 years, or as requested by BLS, the Contractor will fully assist an outside auditor provided by BLS to complete a full FISMA audit of all applicable NIST 800-53 controls for a Moderate system.

5.2.4 Subtask 2.4 Plan of Action and Milestones (As needed)

The contractor shall document the contractor’s efforts in identifying, assessing, prioritizing, and monitoring the progress of security efforts, vulnerabilities, and corrective actions for fixing or mitigating security weaknesses found in operations, or operating environments of any systems involved in storing, processing, or collecting BLS data. This information should be recorded in the form of a Plan of Action and Milestones (POA&M) and should be updated when a security weakness is found on the NLS system. The POA&M describes a weakness and the steps planned for resolving or mitigating the weakness. Each step also includes a planned completion date. The contractor shall promptly report defects or deficiencies to appropriate supervisory and/or security personnel for follow-up action. For a weakness to be resolved and removed from the POA&M, the NLS program must provide evidence demonstrating the resolution of the weakness.

The POA&M should be accompanied by a security progress report that demonstrates that the contractor has reviewed the audit trail, listed major security issues highlighted in the review of the audit log, and described the contractor’s action(s) on those security issues.

Deliverables, Timing and Submission:

5.2.4.1 Plan of Action and Milestones (Ongoing)

Templates and instructions for documenting POA&Ms will be provided to the contractor by the NLS ISSO. As needed, POA&Ms will be continually monitored, with progress updates required quarterly or as requested by BLS. If there are no POAMS, no reports will be required.

5.2.5 Subtask 2.5 System Security Plan (SSP)

The contractor shall develop and document a formal plan detailing the security policies, procedures, and controls required for any systems involved in storing, processing, or collecting BLS data, as required. The System Security Plan (SSP) shall be completed and submitted to the NLS ISSO within the first quarter following the contract award. The SSP shall be updated annually or upon major changes to the system or system environment. The SSP shall address all management, operational, and technical controls specified in NIST Special Publication 800-53, Recommended Security Controls for Federal Information Systems: Minimum Security Controls, Moderate Baseline. The contractor shall implement all security controls as prescribed by NIST and shall report to and seek approval from the BLS for any deviations from NIST 800-53. To provide assurance that the implemented controls are operating as intended, the contractor shall follow NIST SP 800-53A, Guide for Assessing the Security Controls in Federal Information Systems.

The purpose of the System Security Plan (SSP) is to ensure controls are properly selected, authorized, implemented, and maintained in accordance with NIST standards. The SSP lists all controls for the NLS system and specifies their implementation status.

Deliverables, Timing and Submission:

5.2.5.1 The System Security Plan (SSP)

The SSP shall be completed and submitted to the NLS ISSO within the first quarter following the contract award. The SSP shall be updated at least annually or upon major changes to the system or system environment, or as requested by BLS.

5.2.6 Subtask 2.6 Configuration Management Plan

A Configuration Management (CM) plan must be established, documented, maintained, and applied to the NLS system. The appropriate hardware, software, and procedural configuration mechanisms must be defined and developed during the Planning & Requirements Definition Phase of the system development life cycle. The CM plan must be updated and maintained throughout the remaining life cycle phases for the system. The information system personnel and information system must develop a baseline configuration and inventory, control and monitor configuration changes, enforce access restrictions and least functionality, and configure security settings.

The contractor may use a combination of commercially available software and custom developed software established under the secure software development framework defined in NIST SP 800-

218. The commercially available software shall have been developed by major software vendors, be widely used, and be actively supported by the developer or other third parties. When selecting among competing commercial off-the-shelf (COTS) software products, the contractor shall choose software and versions that are free from known security vulnerabilities. The chosen COTS software shall reflect the standard commercial practice of industry. The contractor shall consult available security checklists or recommendation guides in selecting secure product configurations and parameter settings. Any custom-developed software shall be developed in compliance with relevant NIST security requirements. After assembling the COTS and custom software elements of the system, the contractor shall undertake a thorough and methodical search for ways by which the security of the integrated system might be undermined. The government has the right to perform a similar analysis.

The contractor shall remedy any vulnerability found from the contractor’s review or the government’s review in a timely manner. The contractor will consult with the COR, the NLS System Owner and the NLS ISSO on the usage of software applications.

The standard installation, operation, maintenance, update, and/or patching of software shall not alter the configuration settings from the NIST national checklist program repository (https://nvd.nist.gov/ncp/repository ). Any non-standard configuration settings must be approved by the BLS ISSO.

Applications designed for end users shall run with full functionality in the standard user context without elevated system administration privileges.

Deliverables, Timing and Submission:

5.2.6.1 Configuration Management Plan

The CM plan must be updated at least annually and updated as needed between annual submissions.

5.2.7 Subtask 2.7 Contingency Plan and Testing

Contingency planning ensures that an information system can recover from processing disruptions, regardless of the source of disruption. The contractor shall develop a contingency planning program in accordance with NIST SP 800-34, Contingency Planning Guide for Information Technology Systems.

Contingency planning documentation consists of three deliverables: Contingency Plan (CP), CP Test Report and the Business Impact Analysis.

i. The Contingency Plan shall include step-by-step procedures to be followed in the case of a major or minor disruption to normal operations. The contractor shall develop a CP that can be used to ensure that any systems involved in storing, processing, or collecting BLS data can continue to operate and perform its function, as needed, during and after any processing disruption, localized emergency, or large-scale disaster. The CP shall provide detailed procedures in these cases for loss of single files, loss of machines, and loss of the entire system.

ii. The CP shall be completed and submitted to the NLS ISSO within the first quarter following the contract award. The CP shall be updated annually or upon major changes to the system or system environment. The CP shall be maintained in a state of current operational readiness to ensure continuity of support if events occur that prohibit normal operations. Current operational readiness means that the contractor shall perform necessary reviews and updates to keep the CP current. The contractor may develop separate documents that, combined, provide the information required in the CP. A hardcopy of the combined and complete CP shall be maintained at both the primary contract site and at an off-site location.

iii. The Contingency Plan contains the NLS program’s detailed plans for responding to an incident that renders an information technology system partially or completely inoperable. The contingency plan is the repository for the NLS system’s business continuity and disaster recovery information, tasks, and procedures to be used when responding to interruptions of normal business operations and services.

iv. Additionally, the Contingency Plan must be tested and updated annually. Annual reviews must be conducted, and records of these reviews must be included with the Contingency Plan. The contractor shall conduct annual notification tests, and biannual technical and tabletop CP tests as required.

The contractor shall analyze test results, report to the NLS ISSO annually on the results of these tests in a CP Test Report, and subsequently modify the CP, as appropriate. The contractor shall present sufficient documentation and evidence of action in the CP Test Report to validate the findings presented. The test report shall include details on what elements of the CP and CP Test Plan did and did not work properly.

v. The Business Impact Analysis (BIA) is designed to characterize the system components, supported mission/business processes and functions, and note interdependencies. Based on this information, the agency must characterize the consequences of a disruption or system unavailability. As part of the contingency planning process, a BIA is developed to identify and prioritize system components as they correlate to the mission/business process(s) and essential function(s). The Business Analysis Plan will list system hardware and software, location, quantity, other resources needed to function, and links to other critical system resources.

Deliverables, Timing and Submission:

5.2.7.1 Business Impact Analysis

Updated at least annually, usually in conjunction with the Contingency Plan and updated as needed between annual submissions.

5.2.7.2 Contingency plan

Updated at least annually and updated as needed between annual submissions.

5.2.7.3 Contingency plan testing

Will be completed at least annually at BLS direction.

5.2.8 Subtask 2.8 Incident Response Plan

The Incident Response (IR) Plan contains detailed information on how security incidents are handled, tracked, monitored, and reported. Annual reviews must be conducted. The contractor shall conduct annual tests as required. The contractor shall analyze test results, report to the NLS ISSO annually on the results of these tests in an IR Test Report, and subsequently modify the IR Plan, as appropriate. The contractor shall present sufficient documentation and evidence of action in the IR Test Report to validate the findings presented. The test report shall include details on what elements of the IR Plan and IR Test Plan did and did not work properly.

Deliverables, Timing and Submission:

5.2.8.1 Incident Response Plan

Updated at least annually and updated as needed between annual submissions.

5.3 Task 3 Public Use Data Dissemination System (DDS)

with Data Extraction Tool Creation and Maintenance

An internet site provides a medium through which information and publications about the NLS program, including discontinued cohorts, can be disseminated to the public. Some NLS information and functions may be presented more efficiently on an Internet site or sites maintained by the NLS Contractor, rather than by BLS. For example, it is preferable for the Contractor, rather than BLS, to maintain a secure Internet site through which NLS users can download data files and documentation. All NLS cohorts, including those discontinued, should be accessible from the data dissemination system. The system will consist of 3 components: a Data Repository, a User Website, and a public-facing Data Retrieval tool.

Deliverables, Timing and Submission

5.3.0 Data Dissemination System Project Plan

If needed, the contractor shall develop a DDS Project Plan creating a new system within 6 months of award for DDS creation. If DDS already exists, the contract shall submit a project plan for enhancements or improvements to the current system.

5.3.1 Subtask 3.1 Data Repository

The Contractor shall build a web-based Data Repository to store public use data and documentation associated with the NLS. The repository shall be built to accommodate a public facing, data search and retrieval tool.

The Data Repository shall be capable of ingesting, storing, and updating the following types of data:

• NLS Public Use Data

• NLS Codebook Pages

• NLS Topical Guides

• NLS Questionnaires and Other Collection Instruments

• Sampling Reports

• Metadata Items, Descriptions, and Tags

• Metadata items inform users of important characteristics and potential differences in the variables/data they are selecting. The metadata will include links to data codebook webpages, topical guides, questionnaires, and other collection instruments.

Deliverables, Timing and Submission

5.3.1.1 Repository Deployment

As approved in the Project plan or in consultation with the COR.

5.3.2 Subtask 3.2 NLS Public Use Website

The NLS’s public use web site shall be maintained by the contractor and shall provide users with survey data and documentation for all cohorts. NLS owns all material on the public use website including visual design, website text, content and website source code, all of which will transfer to BLS at BLS’s request. This website must follow OMB Memorandum M-17-06 and be Section 508 compliant. The website shall include the following core content and tools:

• Public Use Data with a data extraction tool

• Survey Documentation

• Errata

• Bibliography

• Tutorials

• News and Updates

Decisions concerning particular content to be included on the website shall be made in collaboration with the COR or other NLS designated staff. The COR will direct which NLS materials and functions should be located on the Internet site maintained by BLS and which should be located on the sites maintained by the contractor. Other content and features of the Internet site maintained by the contractor shall be determined after consultations between the NLS Staff and the contractor. Current functionality of the sites shall be maintained or improved. The website shall be programmed in a language as determined in consultation with the COR.

5.3.2.1 Website Domain Names

The contractor shall maintain for BLS the Domain names of the NLS public use website, NLSinfo.org, for the BLS and shall keep these registries current. Proof of registration shall be provided upon request. BLS retains ownership of these domain names.

5.3.2.2 Website Initial Deployment or Enhancement

5.3.3 Subtask 3.3 Data Query and Extraction tool

The Contractor shall create and maintain a web-based data retrieval tool that allows users to access all NLS public use data, metadata, and other documentation

All public use NLS microdata will be made available in a single easily accessible, free data repository. The system must be flexible, user friendly, store data and manage data in compliance with CIPSEA and NIST SP 800-53. The contractor shall provide web-based data structures and tools that serve as an interface with the NLS data files on the NLS public use website. The contractor shall maintain or upgrade the existing data structures and tools (NLS Investigator), develop enhancements to these structures and tools, and provide front end web support for these data structures and tools. It shall provide expert technical assistance to BLS in data structures and tools quality assurance, and support to data users.

At a minimum, the data extraction tool shall allow users to search through variables for each cohort data set online, select variables and then extract the data and program to read in the variables in R, SAS, STATA, and SPSS. The codebook for the downloaded dataset will also be available to the user.

Goals for the Data Query and Extraction tool are to develop and implement one or more high-level approaches that will enable the public to:

• Browse NLS data that are available

• Provide lists of all data matching selection criteria

• Zero in on and select the variables of most interest to them;

• Download this data with accompanying statistical programs (including SAS, STATA and SPSS) and a variable specific codebook

• Save to their own computer the specific list of preferred variables for use at a later time

(called a “Tagset”)

• Provide an easy way to upload those tagsets previously saved on the researchers’ own computers for expansion with new data

Specifically, the data extraction tool shall fulfill, at a minimum, the following requirements:

• Searching – the system must allow users to search for variables by index of selected variables, area of interest, word in title, question text, question name, reference number, year, codebook, or variable type.

• Searches within fields should allow the use of “starts with,” “contains,” “doesn’t contain,” “equals”, and “doesn’t equal” as appropriate.

• Searching functionality should allow users to combine search terms with logical operators such as AND, OR and NOT.

• Index Browsing – the system must allow users to retrieve already prepared sets of variables commonly used in research by topic area.

• Review of Variables and Codebook – Results of searches should be displayed to users as a summary table with the reference number, question name, variable title and year. The table should allow the users to hyperlink to the codebook for each variable, including the functionality of reviewing the code book for the lead-in and default question for that variable, as well as any further documentation. The display of frequencies for the codebook shall also be available to the user via hyperlink as pie chart, bar chart or line graph.

• Selection of Variables – From the review screen, the system must allow users to easily select or deselect variables to create a personalized list of variables of interest from one or multiple searches or index browsing. The selected variables should be sortable by reference number, variable name, variable title or year.

• Saving Selected Variables – The user will be able to save the selected variables to a “tagset” which will also serve as instructions on which variables to download. The tagset can be saved on the user’s personal computer, and the user will have the option of saving the tagset by reference number or by question number and year.

• Management of Tagsets – The system will allow the user to upload a tagset from his or her personal computer. In addition, the contractor shall make available user guides and tutorials for how to use the query and extraction tools.

Query Results Requirements

Once a user has queried the repository, the results of searches will:

• Be displayed to users as a summary table with the reference number, question name, variable title and year.

• Contain a table that displays the codebook when the mouse hovers over the Rnumber or Question name.

• The table should allow the users to hyperlink to the variable page by selecting either the Rnumber or Question name. The variable page will include the code book, links for the lead-in and default question for that variable, as well as links to any further documentation.

• Display results always listing created variables first, then in chronological order (by survey year)

• Allow users to continue to refine their query results in an iterative manner using any combination of search elements until they have found the data of interest.

For example, a user could search for “employment” within the index and get 50,000 results. They then could use the filters to refine the results to only those with the word “business” to get to 1,399 variables

5.3.3.1 Data Extraction tool deployment or enhancement.

5.4 Task 4 NLSY79 Round 32 Interim Contact

To maintain respondent cooperation and maximize response rates, the contractor shall develop and implement methods to locate and contact NLSY79 respondents between Rounds of the survey.

Respondent contacts during non-field periods should maintain and improve respondent interest in the survey, enhance respondent recall, and update locator information without overburdening or alienating respondents.

5.4.1 Subtask 4.1 Interim Contact Plan

The contractor shall develop an interim contact plan for Round eligible respondents. The interim contact plan shall be delivered no later than 3 months after the end of the field period for the previous round.

The plan shall include (but is not limited to) elements such as the type of interim contact (newsletter, interim survey, respondent satisfaction card etc.), the mode (or mode mix), the period during which the distribution shall occur, whether respondents will receive generic or targeted materials and a discussion of the intended outcomes of the contact.

5.4.2 Subtask 4.2 Interim Contact Respondent Materials

The contractor shall provide a draft of the interim contact materials, as agreed upon in the Interim Contact Plan, at a date to be determined in conjunction with the COR. The contractor shall respond to NLS staff edits and suggestions within 2 weeks.

5.4.3 Subtask 4.3 OMB Materials

The contractor shall provide requested OMB Materials, including the final incentive plan and tables showing the expected cost of incentives or other the necessary inputs required for OMB submission, at a date to be determined in conjunction with the COR.

5.4.1. Interim Contact Plan.

The interim contact plan shall be delivered no later than 3 months after the end of the field period for the previous round.

5.4.2. Interim Contact Respondent Materials.

Interim contact materials will be submitted as agreed upon in the Interim Contact Plan, at a date to be determined in conjunction with the COR.

5.4.3 NLSY79 R32 Main OMB Clearance Package

All requested OMB package documents, including the incentive plan and tables showing the expected cost of incentives at a date to be determined in conjunction with the COR.

5.5 Task 5 NLSY79 Round 32 Questionnaire Design and Planning

At the start of the planning phase for each round, the contractor Project Director, PIs, NLS Director, and NLS COR shall establish a design team composed of survey and subject matter experts from the NLS program office and contractor staff. People on the design team must be either contract or subcontract employees who are already agents on the contract or an NLS staff member. The design team will be responsible for determining questionnaire topics and developing questions. BLS staff will lead the design team, and the NLS Director will have final authority over questionnaire content.

Results from earlier rounds of data collection and new findings in the economics, sociology, demography, and survey methodology literature shall be incorporated in the design of questionnaires. The design team shall consult with relevant federal agencies, outside researchers, as necessary.

The questionnaire will include all questions respondents will be asked to answer, plus any computer instructions that indicate the sequencing of questions based on prior information about the respondent or answers they gave earlier in the interview. The questionnaire is anticipated to include a set of core questions that will be repeated in each interview, topical modules that may be repeated in nonconsecutive rounds, and items that may appear in only one round. The NLS questionnaires have always been flexible in nature to accommodate the progression in the respondents’ age, changes in the labor market, and shifts in current policy or research interest. The questionnaire shall maintain this ability to accommodate changes in content and design from round to round. These types of changes may include, but are not limited to:

• Subject matter

• The frequency with which questions are asked, (i.e. every round, in non-consecutive round, and in one round only).

• The mode of interview (i.e. in-person, phone, Internet, etc.) It’s important to note that NLSY instruments depend heavily on preloaded information, particularly information since the Date of Last Interview (DLI). Asking items with preloads, specifically PII such as employer names, names of spouses or partners, and children’s names, in a web interview has not been approved internally at BLS. NLS is open to considering aspects of the youth interview such as the SAQ module to be conducted via web-administration, provided there are no preloads except the date of last interview and are approved as part of the SPR process. If the contractor proposes web based modes, the contractor shall provide sufficient detail on how the web instrument will be developed, tested, and prepared for timely field collection and account for all technical and security requirements. It is the responsibility of the contractor to adhere to CIPSEA and Privacy Act protocol in administering the contract.

The design team shall refine the questionnaire, developing topics consistent with the economics, sociology, demography, and other relevant literature. Choices of questions to be included in the survey shall balance the need for consistency with other NLS cohorts or other data sources and the use of modern survey methods. The contractor shall provide advice on the content, wording, sequence, layout, and presentation of the questionnaire. Topics and questions not taken from an existing, tested source must be researched, developed, tested, and analyzed meticulously. The design team shall consider the cognitive aspects of survey design along with methodological considerations of questionnaire preparation, particularly as they apply to different modes of data collection, such as personal-visit interviews, telephone interviews, Internet, and other modes.

During the development process, the design team shall produce an annotated outline of the proposed questionnaire, highlighting differences from the previous round and include a brief rationale and a discussion of priorities. This will be produced after question topics have been decided, but before final questions are determined. A revised draft of the questionnaire will be produced to reflect the decisions made during the review. It will include annotations regarding changes from the previous draft. This is the version that will be submitted to OMB for approval and programmed into CAPI/CATI.

At the end of the design process the contractor will create a report listing new variables and explaining how those variables will be categorized in the data query tool. This will include the variable type, area of interest and Index tree categorization. BLS has final approval for variable categorization.

The BLS shall have final authority over all aspects of the questionnaire. The contractor shall have ultimate responsibility for implementing decisions and preparing materials in time to meet the schedule.

5.5.1 PI priority and recommendations memo

PI will submit a memo outlining their priorities for the survey for both the long term and what are the highest priority changes for the upcoming round. Attention shall be paid to how changes in the upcoming round will advance long term survey goals. Due 2 weeks before date of first Questionnaire and Design team planning meeting.

5..2 Annotated outline of proposed questionnaire, Annotated Outline with changes from previous questionnaire clearly marked and reasons for changes described. Annotated Outline, a word document, will be submitted at a date to be determined in conjunction with the COR.

5.5.3 Draft of proposed questionnaire.

Draft Questionnaire materials will be submitted, at a date to be determined in conjunction with the

COR.

5.5.4 Questionnaire Topics Report

Questionnaire Topics Report to be jointly written by BLS and contractor listing reasons to include any topics and/or questions not taken from an existing, tested source, and results from testing the new questions. Materials will be submitted as agreed upon, at a date to be determined in conjunction with the COR.

5.5.5 New variable categorization report

A report listing new variables and explaining how those variables will be categorized in the data query tool. This will include the variable var type, area of interest and Index tree categorization. Due at a date to be determined in conjunction with the COR.

5.6 Task 6 NLSY79 Round 32 Survey Preparations

5.6.1 Subtask 6.1 CATI Questionnaire aides and testing

Included with the questionnaire will be a series of questions and answers that interviewers can use to aid respondents. Respondent preloaded data shall be loaded into the system to facilitate longitudinal data collection.

The questionnaire shall be loaded into a CAPI/CATI system that meets the requirements. The contractor will test that the questionnaire works and report to the COR, 30 days prior to the beginning of fielding.

The NLSY79 questionnaire shall be fully translated into Spanish for use with respondents who prefer to speak Spanish.

Deliverables, Submission and Timing

5.6.1.1 Spanish translation of Questionnaire:

The contractor shall create a separate Spanish version of the instrument to accommodate Spanish speakers and report completion 30 days prior to the beginning of fielding period, with last minute changes to be translated within 60 days.

5.6.1.2 Instrument Testing Report:

The contractor shall develop and test the Instrument in both English and Spanish and all systems for data collection and report completion to the COR 30 days prior to the beginning of fielding period.

5.6.2…