About

Scott Lecher, P.E.

I am a transportation engineer with extensive experience in the design and construction of civil works, primarily highways and bridges. The first fifteen years of my career were focused on design, primarily in projects involving reconstruction and added capacity of interstate freeways and interchanges. With great coaching and mentoring, I became adept at 3D surface modeling of complex roadway geometry. I also dealt extensively with management and conversion of multiple design data formats such as LandXML. As part of my involvement with Design-Built projects, I was responsible for preparation of data and models for grading and paving construction machine guidance.

In September 2025, I transitioned into full-time independent consulting. I focus on developing and delivering technology solutions primarily related to system interoperability and open data standards. I often function as an individual contributor on software development teams and am experienced in data science, analytics, and machine learning.

One guiding philosophy is to be “Data Focused, Platform Agnostic”. That refers to solutions are not tied to a particular ecosystem, whether that be in reference to a particular vendor or in terms of desktop and on-prem versus cloud and web-first tooling.

Generally I prefer to think in terms of Virtual Design and Construction (VDC) as opposed to Building Information Modeling (BIM). VDC allows a team to build a project virtually first, identifying and correcting issues in a digital collaborative manner, versus in the field during construction.

BIM is often associated to the concept of 3D models of vertical buildings and facilities. 3D parametric modeling is not quite as widespread in the road and bridge infrastructure industry, but structured data in the form of 2D CAD files and Excel spreadsheets can also be leveraged for most of the same benefits.

Note:

All opinions are my own and may not necessarily reflect those of my colleagues, employer, or clients. Professional licensure is state-specific. Content is not intended nor shall be construed as engineering judgement or direction.