Why should moving one roadway project forward mean searching through so many disconnected places?
I’m building Transportation Workbench to keep plans, engineering tools, estimates, reviews, and milestones within reach. This case study shares the direction and the work in progress.
Built a project-centered workspace for roadway engineering.
Approach
Connect plans, design tools, quantities, estimates, and review context.
What to explore
Screenshots, the milestone workflow, and working tool previews.
01 / THE REASON
WHY I STARTED BUILDING
One project. Too many places to look.
I wanted to spend less time rebuilding the project in my head and more time doing the engineering.
A roadway project can move from plan sheets to geometry, drainage, quantities, estimates, review comments, and delivery decisions in a single day. Each move means finding the right file, checking which version is current, and recovering the reasoning behind an earlier decision.
Transportation Workbench grew from that friction. My goal was to give myself and other DOTD engineers a place where the source material, tools, and next steps stay connected. The engineer still reviews the evidence and makes the call.
Transportation Workbench brings project context, useful tools, and engineering news into one workspace.View full image ↗
02 / ONE PROJECT
BUILT AROUND PROJECT FLOW
A project should carry its context forward.
The Workbench follows a project from the first plan set to the final review, keeping the next decision close to the work that led to it.
01 · START
Plans
Bring the source plan set and key project information into one working record.
02 · UNDERSTAND
Plan intelligence
Structure useful sheet and project context while keeping the original source available for engineer review.
03 · DESIGN
Engineering tools
Work through roadway, drainage, traffic, structures, and quantity calculations with project context close by.
04 · QUANTIFY
Estimate
Connect quantities to pay items, pricing context, and documented assumptions.
05 · REVIEW
QA/QC
Keep findings, references, and resolution status visible as the work is checked.
06 · DELIVER
Project control
Carry milestones, submittals, and project decisions through delivery.
Conceptual project workflow. No real project information is shown.View full image ↗
03 / THE TOOLS
USEFUL WORK, CLOSE AT HAND
The right tool should be one step away.
Explore the full calculator catalog and connected project workspaces that carry plans, quantities, reviews, and delivery forward. This showcase describes the local Workbench build; nothing runs on this portfolio page.
TOOLS / QUICK ACCESS · DISPLAY ONLY
Workbench Tools
Browse the calculator library and connected project workflows.
Swipe or scroll to browseComplete tool and workspace catalog
SHOWCASE ONLY · Catalog based on the local Workbench tool set: individual calculators plus project, review, delivery, and exchange workspaces. Feature availability and validation vary by workflow. Cards are informational; no calculations, project edits, or protected-app actions are available here.
04 / LOCAL CONTEXT
ENGINEERING NEWS
The work changes beyond the plan set.
A useful workspace should help me notice what is changing around a project.
Construction updates, revised guidance, and new approaches to managing road assets can all affect the questions an engineer asks. That is why the Workbench includes a source-linked news desk alongside the tools.
These selected briefs illustrate the news feature under development. The publisher links below lead to original sources; official project documents and current criteria still govern the work.
MOVEBR · BATON ROUGE
Nicholson Drive Segment 1 enters construction
A local delivery update connecting roadway capacity, bicycle and pedestrian access, drainage, and utility coordination.
Development preview · selected source articles. The full Workbench news desk is not yet available through this portfolio.
05 / WHAT I HOPE IT CHANGES
EFFICIENCY · EASE · CONTINUITY
Less time recovering context. More time moving the project.
That is the test I keep coming back to as I build: can an engineer find the right source, use the right tool, and see the next milestone without reconstructing the whole project first?
The Workbench is still evolving. If it makes that sequence clearer for my work—and useful to another engineer facing the same friction—it is moving in the right direction.
A useful calculation needs units, assumptions, a source, and a place in the project record. The current local implementation treats ownership and review as part of that data model.
01 / ORGANIZEProject-owned records
Versioned local records carry project identity. Plan PDF storage is separate from the structured engineering records.
02 / EXAMINETools + evidence
JavaScript worksheets and source-linked plan recognition support the work. Recognized title fields are proposals, with evidence attached.
03 / REVIEWEngineer acceptance
A person accepts or rejects proposed fields. Backup/restore creates a new project identity and invalidates restored sign-off.
Calculation records, quantity publications, estimate lineage, QA records and structured project backup/restore.
Drainage + integration
Limited / evolving
Drainage is a workspace with truthful empty states in the reviewed release. Do not interpret this portfolio diagram as a completed hydraulic model or CAD integration.
Design decision
The carousel is a visual catalog: selecting an arrow changes the card, while each tool description remains non-interactive. This keeps the public portfolio focused on what the Workbench is designed to bring together without presenting a live engineering tool or implying design approval.
Source and current status
Local Workbench package v1.0.10, project-storage, calculation-records, quantity-publications and design modules, plus Phase 3A implementation notes. Source capabilities are not a claim of production deployment.
The tool catalog is display-only. It contains no working calculators, project data, or connection to the protected Workbench application.
