DOL RFI - NLS Data Dissemination FY27.docx

DOCX document 76 KB Posted

Download DOCX, 76 KB

Attached to
DOL RFI - NLS Data Dissemination FY27
Solicitation number
OAA-27-00094
Issued by

About this file

This is a Request for Information (RFI) issued by the Department of Labor, Office of the Assistant Secretary for Administration and Management, for market research purposes related to the National Longitudinal Survey of Youth 2027 (NLSY27) Data Dissemination System. The RFI (Solicitation Number OAA-27-00094) seeks to identify potential vendors and evaluate their capabilities to develop, implement, and maintain a cloud-based data dissemination platform. The Bureau of Labor Statistics requires the contractor to build three integrated components: a cloud-based Data Repository to store NLSY27 public-use data and documentation; a Data Search Engine and Retrieval Tool (DSERT) providing a web-based interface for public data access with advanced search capabilities; and a User Website serving as a comprehensive information portal. The system must be built using non-proprietary, open-source software that is transferable, scalable, and capable of accommodating future data rounds. All data, metadata, and code must remain government-owned, and the contractor must transfer all materials to BLS within 90 days of request or provide written certification of destruction upon contract end.

Key deliverables include a repository design using NLSY97 data, a repository prototype within three months of pre-test data release, full repository deployment, DSERT design and prototype versions with iterative BLS feedback cycles, final DSERT deployment within six months of Round 1 data delivery, user website design and deployment, and technical training for BLS staff. The system must support 50 concurrent users, comply with NIST 800-53 and Section 508 accessibility standards, and provide search functionality by multiple criteria including index search, variable titles, question text, variable type, and survey year, with capabilities for logical operators, free-form searches with synonyms, and tagset creation for personalized variable lists. RFI responses of no more than 30 pages are due by December 9, 2026 at 2:00 PM Eastern Time to Jasmine Lee (Contract Specialist) and Oneisha Pickard (Contracting Officer); questions must be submitted by November 26, 2026 at 11:00 AM EST. This RFI does not represent a commitment to issue a solicitation or award a contract, and the government will not reimburse respondents for submission costs or participation in follow-up demonstrations.

View the file

Other files

File Type Posted
RFI Attachment 1 - RFI Response Questions.doc DOC document
RFI Attachment 2 - RFI Questions and Answers.xlsx XLSX spreadsheet

On GovTribe

Work with this file

  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Office of the Senior Procurement Executive (OSPE)

Department of Labor - OSPE Request for Information (RFI) NLSY27 Data Dissemination System

SPECIAL NOTICE: SOURCES SOUGHT & REQUEST FOR INFORMATION (RFI). THIS IS NOT A REQUEST FOR QUOTES OR PROPOSALS. This notice does not represent a commitment by the Government to issue a solicitation or award a contract. The Government is not obligated to and will not pay for information received as a result of this announcement. No reimbursement will be made for any costs associated with providing information in response to this announcement and any follow-up information requests to include an invite to further explain/demonstrate aspects of their proposed approach. Requests for a solicitation will not receive a response. Information provided in response to this RFI is submitted voluntarily and is not being requested as part of a solicitation for actual pricing.

A. PURPOSE OF RFI

This is an RFI per FAR 15.201(e) for market research purposes. Contracted services will include the development, implementation, and maintenance of a new data dissemination system for the National Longitudinal Survey of Youth 2027 (NLSY27).

The purpose of this RFI is two-fold: (1) to identify ways to increase vendor participation, and (2) to evaluate the capabilities of potential vendors to meet the requirements in the draft PWS. The NLSY27 dissemination system will be a public-facing platform and is anticipated to support the inaugural release of the NLSY27 Round 1 public-use data and accommodate the incorporation of subsequent rounds of longitudinal data.

B. BACKGROUND

The Bureau of Labor Statistics (BLS) of the U.S. Department of Labor is the principal Federal statistical agency responsible for measuring labor market activity, working conditions, and price changes in the economy. Its mission is to collect, analyze, and disseminate essential economic information to support public and private decision-making that forms the basis of our democratic, free-enterprise system. Like all Federal statistical agencies, BLS executes its statistical mission with independence, serving its users by providing products and services that are accurate, objective, relevant, timely, and accessible.

In Fall 2027, the National Longitudinal Surveys (NLS) program will launch the first rounds of a new youth cohort, the National Longitudinal Survey of Youth 2027 (NLSY27). As with previous NLSY cohorts, the new cohort will provide deeper insight into issues that impact labor force participation, such as educational attainment, technological change, work-family balance, and occupational shifts. This new cohort will collect detailed information on the labor market, including the effects of job characteristics, job skills, and career paths. Researchers will be able to gain a better understanding of the factors that are influencing labor market outcomes of Generation Z and will be able to conduct cross-cohort analyses with the older NLSY cohorts.

To support the dissemination of NLSY27 data, BLS seeks to establish a modern, accessible, and scalable data dissemination that enables researchers and other members of the public to discover, access, and use NLSY27 public use data and associated documentation. The system must support the initial Round 1 data release (tentatively planned for Spring 2031) and be designed to accommodate subsequent NLSY27 round-specific data releases.

BLS will provide the public-use data files, metadata, questionnaires, code books, and other supporting documentation for incorporation into the system. The contractor will be responsible for developing and maintaining the system’s requirements and capabilities necessary to ingest and disseminate these materials. The system must comply with all applicable Federal, Department of Labor (DOL), and BLS information technology, security, privacy, and accessibility requirements, including requirements related to system authorization, data protection, and ongoing security requirements.

BLS currently disseminates public-use data from existing NLS cohorts through the NLS Investigator (https://www.nlsinfo.org/investigator/pages/home). Respondents are encouraged to review the NLS investigator for context regarding the types of data and functionality currently available to NLS data users.

Additional Information on the NLS Investigator including video tutorials can be found at:

https://www.bls.gov/nls/getting-started/tutorials.htm

C. PERFORMANCE WORK STATEMENT (PWS)

Task 1. NLSY27 Data Dissemination System The Contractor shall develop a cloud-based Data Dissemination System (DDS) for the NLSY27 public-use data. The system will consist of 3 components: a Data Repository, a public-facing Data Retrieval tool, and a User Website.

The data repository shall store, in a central location, the NLSY27 Round 1 public-use respondent data, accompanying metadata, and all associated survey documentation. The data retrieval tool shall consist of a web-based user interface that allows the public to easily search, access, and extract NLSY27 data. The user website shall, at a minimum, provide information about the NLS program, the NLSY27 survey data, the data retrieval tool, and survey documentation, and information to help data users.

The DDS shall be maintained and operated by the contractor, however all aspects of the system, including data, metadata, and code shall be owned by the government. Furthermore, an important requirement is that software/tools be transferable, accessible, and usable regardless of whether BLS or an external contractor operates and maintains the software. Off-the-shelf/open-source products are preferred, with minimal customization required. The use of proprietary software will not be accepted.

Subtask 1.1 Data Repository The Contractor shall build a cloud-based Data Repository to store public use data and documentation associated with the NLSY27. The repository shall be built using non-proprietary, open-source software, allowing for the repository to be transferred to another Contractor or the BLS with ease. 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:

· NLSY27 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.

The repository shall be dynamic in nature; built to be both flexible and scalable. While it will initially only hold information from Round 1, the Repository shall accommodate updates to existing data, and additional rounds of data. Examples of the types of updates the Contractor should expect include periodic updates of specific variables and documentation due to errors in variable construction, new privacy updates, or changes in variable responses.

The Contractor shall build the data repository such that it includes the following types of functionalities:

· Built on a logical data model or structure, including an easily updated classification structure for key identifiers, that connect data within multiple survey rounds for a single cohort.

· Be easily transferrable to a BLS hosted Amazon Web Service Data Lake repository.

· Utilizes tools and applications that accommodate flexible data retrieval, processing, and downloads that are built using modern industry best practices.

· Deliverable 1.1.1: Repository Design The Contractor shall propose an initial design for the Repository. The initial design shall utilize data from the NLSY97.

· Deliverable 1.1.2 Repository Prototype Within three months of the release of pre-test data, use pre-test data to build the prototype.

· Deliverable 1.1.3 Repository Deployment Expand for use of full round 1 data and deploy this solution on a technology stack to include a modern, industry- standard open-source web application development framework; a modern, open-source relational database; automated testing and deployments; and capable of being hosted on the cloud.

· Deliverable 1.1.4 Repository Data and Code Transfer to BLS and/or Destruction Upon request, the contractor shall deliver the entire data repository with all its contents and associated code within 90 days of the request. At the end of the contract, the Contractor will certify in writing that the return, destruction, and/or removal of all NLS data and documentation from contractor premises.

Subtask 1.2 Data Search Engine and Retrieval Tool (DSERT) The Contractor shall create and maintain a web-based data retrieval tool that allows users to access all NLSY27 public use data, metadata, and other documentation stored in the data repository.

The data retrieval tool shall allow the public to query, explore, save and download NLS public use data along with linked documentation from the NLS data repository. At a minimum, the retrieval tool shall allow users to search through variables to find data relevant to their interests, allow users to filter results based on the information being queried (e.g., employment, assets, child care) and/or characteristics of the information (e.g., cohort, survey year, data type) to obtain a manageable number of results, select variables and then extract the data and programs to read in the variables in R, SAS, STATA, and SPSS. The codebook for the downloaded data set will also be available to the user.

The data retrieval tool shall accommodate changes as needed in the future, such as the ability to incorporate new data elements, search words, or key terms (e.g., Covid) that are added to the dataset or changes in variable classifications. It must meet NIST 800-53 and Section 508 standards and should operate rapidly enough to provide a reasonable user experience for 50 concurrent users.

Search Capabilities The data retrieval tool shall enable users to easily find data relevant to their interests by providing several ways to search the database using multiple criteria. The application shall provide lists of all data matching selection criteria and allow users to browse NLS data that are available. Each variable shall be linked to the electronic codebook so that users may examine question wording, response categories, response frequencies, etc. of the variables in the list.

At a minimum, the variable search function shall allow users to search by:

· Index Search (variable lists grouped by reach topic area)

· Word in title [Pick from list]

· Word in title [enter search term]

· Question text [free form]

· Question Name [Pick from list]

· Question Name [enter search term]

· Reference number [Pick from list]

· Reference number [enter search term]

· Variable type (such as screener, respondent report, parent report, created variable, or event history)

· Survey Year

Queries should also allow for:

· Searches within fields that include the use of “starts with,” “contains,” “doesn’t contain,” “equals”, and “doesn’t equal” as appropriate.

· Combining multiple search terms with logical operators such as AND, OR and NOT.

· A free-form search box that allows for synonyms. Using a dictionary or other word linkage list, the query should return the same results when two different words that mean the same thing are entered into the search term.

· Variable to be sortable by reference number, variable name, variable title, or year.

· Users to modify current search with additional fields.

Search Display Results 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 / indexes browsing. The selected variables should be sortable by reference number, variable name, variable title, or year.

Once a user has queried the repository:

· 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 display the codebook page when the mouse hovers over the Reference Number (Rnumber) or Question name.

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

· After the search engine returns variables, created variables shall be listed first, then in chronological order (by survey year).

· Users shall be able 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 5,000 results. They could then use additional filters to refine the results to only those with the word “business” to get to 400 variables.]

Tagset Saving and Download Capabilities NLS defines a tagset as a ‘user generated list of preferred variables for use at a later time’. The Contractor shall incorporate a tagset feature into the data retrieval tool, allowing NLS users to select variables of the choosing, create a tagset, and save it on their personal computer. Users shall have the ability to upload previously saved tagsets and modify or add data to them.

Users shall be able to download the data and documentation associated with their tagset. The data retrieval tool shall create a download packing including the data and program to read in the variables in R, SAS, STATA, and SPSS. The codebook pages corresponding to the variables in the downloaded data set will be included in the download package.

The Use of Codebook Pages The electronic codebook is intended to allow users to examine individual variables in the data sets. It shall provide convenient access to all the codebook pages provided in Task 12 and stored in the repository. In conjunction with the query application, users shall be able to flexibly search the electronic codebook using multiple criteria to select variables for analysis, examine their documentation, create and retain lists of variables of interest, and download and print the list and its corresponding codebook pages. Users shall also be able to use predefined lists to create and download extracts with the relevant codebook pages.

The electronic codebook shall also include links to the user’s guide, so that users can readily connect from variable documentation to relevant overview sections (and vice versa); and links to the questionnaires and other collection instruments, so that codebook users can readily reference the relevant questionnaire entry as well as lead-ins and default next questions.

· Deliverable 1.2.1 DSERT Design Plan The Contractor shall provide a proposal to BLS for the construction of the dissemination tool including descriptions of its capabilities and mock-ups of its look and feel. BLS will provide feedback on the look and feel and requests for revisions.

· Deliverable 1.2.2 DSERT Prototype Within 3 months of BLS’ approval of the DSERT Design Plan, the Contractor will deliver a test version of the DSERT to BLS. Throughout this process, BLS shall retain editorial control over naming conventions and other aspects of the look and feel.

•BLS shall provide feedback on draft 1 the tool within 14 days, and the Contractor will provide a revised test version within 14 days of receiving BLS feedback.
•BLS shall provide feedback on draft 2 the tool within 14 days, and the Contractor will provide a revised test version within 14 days of receiving BLS feedback.
•BLS shall provide feedback on draft 3 the tool within 14 days, and the Contractor will provide a final version within 14 days of receiving BLS feedback.

Barring data errors, the final version of the DSERT will be delivered within 6 months of the delivery of the public use data set.

During review of the DSERT, any issues shall be discussed with the COR. However, if the data provider’s output does not have errors, the dissemination provider will be responsible for ensuring that the outputs from the dissemination tool do not contain errors.

· Deliverable 1.2.3 DSERT Deployment The DSERT tool containing the first round of NLSY27 data shall be delivered within 6 months of the Round 1 NLSY27 public use data files delivered to the contractor.

· Deliverable 1.2.4 DSERT Training The contractor will provide technical assistance and training to NLS staff members upon initial system deployment. The contractor will provide this initial technical assistance/training to NLS/ BLS staff on system operation and use, but not to the public. Tool help tips will accompany the tool deployment. The vendor will not interpret query results nor perform disclosure analysis of the data released. Training for this system may occur via a variety of methods including in-person, phone, email, Microsoft teams or Webex.

After delivery of the DSERT, the Contractor shall provide training, troubleshooting and service support to NLS staff has they test the system. The contractor must address all issues identified by NLS within three business days.

· Deliverable 1.2.5 DSERT Code Transfer to BLS and/or Destruction Upon request, the contractor shall deliver t the code for the DSERT tool to BLS within 90 days of the request. At the end of the contract, the Contractor will certify in writing that the return, destruction, and/or removal of all NLS data and documentation from contractor premises.

Subtask 1.3 User Website An internet site provides a medium through which information and publications about the NLS program 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. For this reason, the Contractor shall maintain Internet sites dedicated exclusively to the NLSY27 program. It will act as an all-encompassing venue through which users can learn about and use NLSY27 data.

The site shall include the DSERT so users can find specific topics of interest. The contractor will update the home page regularly as new information about data releases, corrections, and updates, and other NLS news becomes available. With input from the Contractor, NLS designated staff will decide 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. NLS designated staff shall review all NLS-related materials that the Contractor proposes to place on the Internet before those materials can be made available to the public.

· Deliverable 1.3.1 User Website Design

· Deliverable 1.3.2 User Website Prototype

· Deliverable 1.3.3 User Website Deployment

· Deliverable 1.3.4 User Website Data and Code Transfer to BLS and/or Destruction

D. TABLE OF RFI ATTACHMENTS

Attachment Number
Document Name
Number of Pages
Document Type
Document Date
RFI Attachment 1
RFI Response Questions
4
Word Document
11/19/2026
RFI Attachment 2
RFI Questions and Answers
-
Excel Document
11/19/2026

Attachment 1 – RFI Response Questions: Contractors must address all questions in this attachment, organized by the following sections: General Information, Clarity of the Performance Work Statement, Vendor Participation, and Capability Statement. Responses should demonstrate your firm's experience, technical approach, and ability to meet the NLSY27 dissemination system requirements.

Attachment 2 – RFI Questions and Answers: This document contains questions submitted by contractors during the RFI period along with responses provided by the Government. The Q&A log will be updated and posted as amendments to the RFI as additional questions are submitted and answered.

E. RESPONSE TO RFI

RFI responses shall conform to the format below and provide the following information:

1. Cover Letter – The cover letter must include the following information:

· Company name

· Company point of contact, telephone number and email address

· Date submitted

2. Offerors shall respond to each of the questions located in RFI Attachment 1 – RFI Response Questions.

3. If the offeror chooses not to respond to a question, indicate “no response.”

4. Submit a capabilities package that include the above considerations that demonstrate capabilities and expertise related to the information outlined.

5. Marketing and/or reference materials, if included, shall be placed at the end of the response, in an appendix.

6. Responses shall not exceed 30 pages, and should be submitted in Microsoft Word .doc or .docx formats, Times New Roman 11-point or 12-point font, with 1-inch margins minimum all around.

F. RFI SCHEDULE

Responses to this RFI shall be submitted via email to the Contract Specialist, Jasmine Lee at Lee.Jasmine.4@dol.gov and Contracting Officer, Oneisha Pickard at Pickard.Oneisha.S@dol.gov, by Wednesday, December 9, 2026 at 2:00 PM Eastern Standard Time (EST). The subject line must read "RFI Response for OAA-27-00094 [Company Name]."

Questions regarding this RFI shall be e-mailed to the above points of contact by Thursday, November 26, 2026 at 11:00 AM EST. Questions and answers shall be posted as an amendment to this RFI (see Attachment 2 – RFI Questions and Answers). The Government reserves the right to edit any questions as needed to protect the identity of the source, but absent this consideration, the Government intends to quote each submitted question verbatim in its response. The subject line must read "RFI Question for OAA-27-00094 [Company Name]" in order to be included in the government's response.

image1.jpeg

File details come from the government source that posted it. Updated .