NTLDR Questionnaire and Tables_Fillable.docx
DOCX document 24 KB Posted
- Solicitation number
- 693JK426R700001
About this file
This is a market research questionnaire designed by the Bureau of Transportation Statistics to assess digital repository platform vendors' technical capabilities and solutions for the National Transportation Library (NTL). The Department of Transportation, through its Office of the Chief Digital and Information Officer, is conducting this pre-solicitation market research to identify potential systems for managing and providing public access to NTL's digital collections.
The questionnaire requests vendor information including company details, points of contact, and UEI from sam.gov, along with assessment of whether solutions are Commercial Off-The-Shelf (COTS) without customization or require development. Vendors must address technical capabilities across four structured tables: General Requirements (cataloging, APIs, reporting, submission portals, file handling, analytics, and compliance with OMB M-23-22 digital-first requirements); Cataloging Interface Requirements (record management, metadata configuration, controlled vocabularies, and collection organization); Public Interface Requirements (search functionality, filtering, browsing, previewing, export capabilities, and version control); and Administrative, Security, and Technology Requirements (user access management, FedRAMP authorization, PIV card login capability, .gov domain configuration, and development environments). Vendors must also provide brief narratives addressing specific technical capabilities. The questionnaire emphasizes requirements for FAIR Principles compliance, persistent identifiers (ORCIDs, DOIs, RORs, NAIDs, ARKs), OAI-PMH support, responsive customer support with 24/7 site stability, and FedRAMP authorized solutions with appropriate security and authentication measures.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| NTL Digital Repository Sources Sought Notice.pdf |
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Bureau of Transportation Statistics Market Research Questionnaire – National Transportation Library Digital Repository Platforms
1. Company name, address, and web address.
2. Company point(s) of contact, including name, position, phone number, and email address.
3. Provide your Unique Entity ID (UEI) from sam.gov (https://sam.gov/)
4. Provide link to your product on FedRAMP marketplace (https://marketplace.fedramp.gov/)
5. Are there limits to file size? ___Yes ___No What is the size limit ___
6. Are there limits to file type? ___Yes ___ No Describe file type limits:
7. Will your product offer a solution COTS without development? ___yes ___no
8. Will your product offer a solution with development ___yes ___ % estimate of customization required ___no
Technical Capability Please address your digital repository platform’s ability to meet NTL’s technical needs in the four tables and two brief narratives below. Place an “X” for each requirement along with an explanation of how the solution does or does not meet that requirement.
Table 1: General Requirements
| General Requirements |
| Currently Capable |
| Currently Not Capable |
| Details or Explanation |
Integrated cataloging and public interface
Bi-directional APIs
Reporting functionality
Self-service submission portal with customizable submission instructions
Self-service submission portal allows single, bulk, and large file deposits
Self-service submission portal with mediated workflow
Public interface meets OMB M-23-22 digital-first requirements
Hosts large file sizes and variety of file types
Includes training and user documentation
Data migration/conversion support
OAI-PMH support
Implements persistent identifiers (ORCIDs. DOIs, RORs, NAIDs, and ARKs)
FAIR Principles compliance
Responsive customer support & 24/7 site stability
Usage metrics/analytics
Table 2: Cataloging Interface Requirements
| Cataloging Interface Requirements |
| Currently Capable |
| Currently Not Capable |
| Details or Explanation |
Ability to duplicate records
Ability to make global changes to defined sets of records
Ability to add instructional text on metadata fields
Delete records restricted by user role
Create record templates and set default values for metadata fields
Cataloging by individual record or batch
Flexible, configurable Dublin Core and DCAT-US 3 metadata
Integrate controlled vocabularies (TRT)
Authority control functionality
Ability to add records to multiple collections
Series records functionality
Configurable metadata display per NTL requirements
Repeatable metadata fields
Metadata crosswalking
Create, organize, and customize nested collections
Ability to link repository records for various research outputs
Table 3: Public Interface Requirements
| Public Interface Requirements |
| Currently Capable |
| Currently Not Capable |
| Details or Explanation |
Advanced search functionality
Sort order for search results
Search facets and filtering
Build on previous searches/retain search history
Browse collections
Preview files without downloading
Export records and/or citations
Metadata download in multiple formats
Organize and display image galleries
Curate themed archives exhibits
Pan and zoom features for images
Version control for datasets
Clear file lists with individual file or all file download
Copyright and licensing information
Table 4: Administrative, Security, and Technology Requirements
| Administrative, Security, and Technology Requirements |
| Currently Capable |
| Currently Not Capable |
| Details or Explanation |
NTL administrators can manage accounts and user roles
Different levels of user access privileges
Web-based, open architecture
Help section with online documentation
Development, testing, and training environment
Configurable front-end with USDOT branding
Patching and updates
User login via PIV cards or Login.gov
FEDRAMP authorized
Configurable with .gov URL
Brief Narratives
Briefly describe (<1000 words) additional features and functionality your digital repository platform offers.
Briefly describe (<1000 words) artificial intelligence capabilities to support the repository platform. If your solution can automate the initial screening of complex attachments, please include that information.
Business Classification List all North American Industry Classification System (NAICS) codes used by your firm:
NAICS Codes
Identify all applicable classifications for your organization such as:
| Classification |
| Yes |
| No |
Small business
Small disadvantaged business
Women-owned business
HUB Zone business
8(a) business
Service-disabled veteran-owned small business
Large business
Non-profit
Other (please specify)
1. Is your company on the GSA Schedule? ___ yes ___ no
a. If yes, provide your SIN number:
b. If yes, provide your Schedule number:
2. Is your company registered in the System for Award Management (SAM)? ___ yes ___ no
a. If yes, provide your Unique Entity ID (UEI) number:
Pricing Information
For the potential repository offering, please explain the following:
1. How are the initial migration and start-up costs priced? For example, is it by volume of data migrated, data conversion factors, enterprise-wide, or on some other basis?
2. How is the repository normally priced for ongoing annual maintenance? For example, is it priced out per number of users, by volume of data hosted, enterprise-wide, or on some other basis?
3. Are separate modules or additional packages needed for the cataloging interface and public interface? In other words, will a digital repository with an integrated front and back end require multiple products?
4. How are customization and enhancement requests priced? For example, as a separate Line Item, by the hour, or on some other basis?
5. Is training provided or does training need to be purchased as a separate Line Item? If so, what type, level/amount of training is included?
6. Is support included or does support need to be purchased as a separate Line Item? If so, what type, level/amount of support is included?
File details come from the government source that posted it. Updated .