U.S. DOT FY 2024.2 Phase I Pre-Solicitation Q&A
- To create a new account or to sign in with an existing account please click on “sign in” located at the top right of the page.
- A new pop-up window will open to make a selection, you can use an existing Google or Facebook account to access the site, or you might select to create a new account.
- If you choose to access UserVoice with an existing Google or Facebook account, you will be required to enter your login credentials for Google or Facebook and agree to terms of service.
- If you need to create a new account, click "Create an Account" underneath the password box.
- In the next screen, type in the e-mail and click "Verify E-mail".
- Navigate to your inbox and click the link within the e-mail to verify. The link will be generated by noreply@trymagic.com
- That link will be live for 20 minutes. Once that time elapses, you will have to request another one.
- Navigate back to UserVoice, and you will need to provide your name, a password, and agree to terms of service and storage permissions. Click "Create Account".
- Use the “Enter your idea” box located at the middle of the page to enter your questions.
- You may add more detail in the Description box(optional). Do NOT attach any files. The U.S. DOT shall not consider any submitted materials other than questions.
- Enter your e-mail address and password.
- When finished, select “Post idea.” If you registered, you will be able to track responses to your post. Please include only one question or comment per post to help us keep the forum organized.
55 results found
-
What intellectual property (IP) rights will apply to the data and software deliverables produced in different phases
For phase II's beta software tool, what level of access and usage rights does the DoT expect from companies (government pupose rights, unlimited rights, or negotiated licenses)?
What are the potential(expected) licensing options for the fully functional software developed in phase III (consider commercial-off-the-shelf (COTS) licensing or the DoT wants the IP rights)? What are the DoT's long-term goals for ownership and operation of the phase III software?
Pre-existing IP: if companies use pre-existing IP in their deliverables, can you clarify ownership and licensing rights for those components?
7 votes -
Focus on data, or the decision making tool?
Is the focus of the SBIR the data generation or the decision making tool? The presolicitation talks about both. However, without the underlying data available, we cannot build a good decision making tool, especially the NLP examples given. Is DoT looking for easy to use decision making tools, or the tools to fill in the missing data elements?
7 votes -
Data Ownership Rights
APPENDIX A states “The data and methodologies generated from this initiative that reflect existing bicycle, pedestrian, and accessibility infrastructure shall be hosted publicly in an open and accessible format” — Can you expand on this? Will this be a carveout of data ownership rights? How long will this data be publicly hosted on whose servers?
6 votes -
Scope of the decision support tool?
Should the decision support tool we're developing for this project aim to cover all three aspects outlined in Appendix A: identifying gaps, proposing solutions to fill those gaps, and evaluating the potential impact of those solutions comprehensively? Alternatively, would it be sufficient for the tool to focus on addressing a specific urgent issue within the network, such as bike safety, thereby improving the overall quality of the complete streets network?
5 votes -
Road Weather & Conditions
I don't see weather/road conditions as Context data elements to generate or enhance. Is that data element intentionally not included and is it a data element that should be included as it impacts safety, efficiency, etc.?
5 votes -
Preferred standard for data to fill in
Will the DOT be supplying a preferred standard for each of the unavailable or incomplete data attributes?
For example, for a dataset that collects sidewalk surface conditions, a standard may include categories and values to choose from, such as:
- Surface issue: roughness, cracking, heaving
- Severity: mild, moderate, high
- Etc.
This way, there is a national standard for each of the incomplete data attributes that need to be filled out. Perhaps this can only be created after the development of each dataset.
2 votes -
Working with small business.
Numerous companies that would not be defined as small businesses collect or could collect data that can be used to help develop the tool that this project is seeking. Will Volpe consider curating a list of companies that could be partners to a small business looking to develop the desired tool(s).
3 votes -
Does the DOT have a list of Metro transit agencies or Regional Planning organizations who would be willing to work with Small businesses pla
Does the DOT have a list of Metro transit agencies or Regional Planning organizations who would be willing to work with Small businesses as part of this topic ?
3 votes -
james.menendez@alliedmission.com
Simple Initial Questions:
1. How are geographic areas selected or assigned?
2. Can multiple parties work on the same area?
3. Is there a preference or targeted benefit from starting in a community area that is part of a larger SMSA that will prove effective for broader analysis, testing/proofing, and deployment?
4. Is there additional value from leveraging both urban and rural community examples for initial research to drive a broader data and analytic set and provide correlations between them to gain broader coverage?
5. Are sustainability factors meaningful to add to scoring models for infrastructure or are broader ESG…2 votes -
Focus of the decision support tool?
If the proposed the decision support tool for this project is focused on a particular data element listed in Table 2 of Appendix A, like on-street curb management, would that be a broad enough scope for this project given the multimodal nature of managing curbs safely and effectively?
2 votes -
Testing Our Traffic Planning Tools: How important are simulation features for our tools, and what should they include?
Example: Incorporate simulation modes for visualizing traffic flow changes with 3D models and heatmaps.
2 votes -
Keeping Traffic Tools Up-to-Date: What’s the expected frequency for data updates in our tools?
Example: Refresh data nightly and schedule major software updates quarterly based on user feedback.
2 votes -
Tools Working Together: How can we ensure compatibility of our tools with other urban planning systems?
Example: Develop APIs for easy data exchange with common traffic management systems.
2 votes -
Updating Traffic Information in Real-Time: How critical is real-time data processing for our tools, and what are the expectations?
Example: Real-time processing with data updates within 1 minute is crucial for traffic management.
2 votes -
Designing User-Friendly Tools: What features should be included to make the traffic tools user-friendly?
Example: Incorporate intuitive dashboards with real-time traffic visualizations.
2 votes -
Detailed Traffic Data Needs: Could you provide more details on the specific traffic data to focus on?
Example: Concentrate on lane usage data, peak traffic hours, and bike lane occupancy.
2 votes -
Making Tools Easy for Everyone to Use: How do we ensure our tools are accessible to users with disabilities?
Example: Follow WCAG 2.1 guidelines for accessibility, like screen reader compatibility.
2 votes -
Making Sure Our Tools Work Well: Which performance benchmarks do our tools need to meet for effectiveness?
Example: Your tools should process requests within 2 seconds and maintain a system uptime of 99.9%.
2 votes -
Handling More Data as We Grow: What scalability considerations are needed for our tools as data volume increases?
Example: Design your tools for scalability using cloud services to manage increased data loads.
2 votes -
Protecting Our Systems: What security measures are required to safeguard the traffic data and tools?
Example: Implement SSL encryption for data transmission and robust user authentication mechanisms.
2 votes