LRTPs

SaaS vs. On-Premise: What’s the Difference?

Shawn L, Client Implementation Analyst

[<5 Minute Read]

SaaS vs. On-Premise

When it comes time to upgrade your transportation improvement program (TIP) software you’ll need to decide whether it’s hosted on-premise or in the cloud. Naturally, cost is always a concern as well. To start, let’s quickly define each.

  • SaaS – An acronym that stands for “software as a service”. It’s a solution that’s hosted and maintained by a 3rd party in the cloud.
  • On-Premise – A solution that is hosted in-house (on premise) and typically supported by a 3rd party.

EcoInteractive’s ProjectTracker TIP software is considered to be a SaaS product, as we have built the product in-house, continuously work to maintain and add relevant features to the software, and provide our clients with end-to-end coverage and 24/7 access to ProjectTracker through the web. Competitors, such as PMG Pro, utilize an on-premise approach, which involves utilizing your agency’s IT resources and infrastructure  to host and maintain the software.

Delivering our ProjectTracker system in a SaaS model afford us several distinct advantages over traditional software.

  • Reduced implementation time
  • Predictable costs
  • Automated data backup
  • ProjectTracker can be deployed and upgraded without taking away from your IT Resources
  • Continuous relevant product updates to stay current with local, state, and national requirements

Let’s examine 3 factors that play a role when deciding which approach to take with your transportation planning software: cost, maintenance, and product updates.

Cost

Cost is typically the biggest issue when deciding on which solution should be deployed by your agency. However, costs can be hiding underneath the surface and not realized until years later. 

For on-premise providers like PMG Software Professionals, you will usually have a higher upfront cost in the form of implementation and licensing fees. Afterwards a yearly maintenance and support fee can be expected. This maintenance and support fee often does not cover additional features for your software. 

Although the on-premise solution can be ideal in the first few years and seem even better in the latter years, often you will need updates, or the desire to have new features added to keep up with the transportation planning industry. Even without enhancing the software you will still need to make sure the on-premise solution can withstand the battle of time and remain fully functional and operable. These additional costs can add up quickly and exceed the original cost estimate in mind during procurement.

With Ecointeractive’s ProjectTracker SaaS model, maintenance, upgrades, and customer support are included in the cost. Simply put, we will be there every step of the way to make sure you have what you need to successfully plan, prioritize, and report on your transportation projects. This helps keep the projected costs over the life of the contract on target so you may properly budget for the future and also keeps your IT department working on the projects that matter the most.

Maintenance & Support

Software is never perfect and technical issues may arise from time to time. On-premise software is not insusceptible to this issue, in fact, it can cause an even bigger headache. Having an on-premise solution provided by a 3rd party may require your IT department to wait on a patch from the software company before they can deploy the fix internally. 

Additionally, with an on-premise solution, like PMG STIP Manager, the product will need to be maintained from the very first day. The solution may stay relevant in the first few years of service, but picture the solution 5-10 years from now, it would be hard to imagine a scenario where major upgrades and enhancements are not required for the software.

A SaaS approach allows us to constantly monitor the performance of our system and quickly deploy any patches without utilizing your IT resources. Also, with a SaaS solution you no longer have to worry about the hardware capabilities you have on-site. We will always update the hardware when necessary to ensure a consistent experience with our ProjectTracker system.

Product Updates

From one STIP or TIP cycle to another, your agency may have a change in priorities, information requested, or a desire to further streamline the software to help with time and cost savings. Alterations or upgrades for an on-premise solution are often costly and require a significant time investment. These costs are not realized during the procurement process and can lead to tough decisions later on when an update is desired or a necessity.

The STIP or TIP should be a living document that is constantly amended and updated. For this reason we believe that a SaaS solution provides the most efficient approach to handling your transportation planning needs. As deploying software through a SaaS model greatly reduces implementation time of a new feature or enhancement. 

Deploying our ProjectTracker software through a SaaS model, instead of an on-premise approach like PMG Pro, allows us to continuously work on improving the workflows and features utilized by our clients. Clients already utilizing ProjectTracker do not need to plan, deploy, and validate the changes to our software. When new features are released they have been thoroughly tested and ready for your use.

We are always engaging with our clients post-launch to understand their needs. This allows us to plan for the changes coming in the transportation industry and deliver relevant product updates on a consistent and timely basis.

Conclusion

Although PMG Pro and other on-premise solutions can seem to be the cost effective solution, often they are anything but cost efficient. From the first day of service with any solution maintenance will be needed to keep the software functioning. After clearing the licensing fees and implementation costs associated with on-premise solutions you will likely desire upgrades and new features not handled in the contract. All of this combines to be a huge resource drain for your agency in the form of time and money. 

With our ProjectTracker SaaS, we want to give you back those years of resources you will need to invest when going with an on-premise solution. Let us handle those hardware upgrades, bug fixes, and product enhancements for your agency. We feel that software should be relevant beyond the first few years of service and we are confident that a SaaS solution will do just that. While you are busy planning the transportation needs of your community we will be busy behind the scenes making sure your software is up to date and ready to tackle tomorrow’s challenges.

Helpful TIP SaaS Links


Long Range Transportation Plans (LRTP) Overview

Kristen Z, Transportation Planner

[<5 Minute Read]

What is an LRTP?

State Departments of Transportations (DOTs) have been producing Long Range Transportation Plans (LRTPs) for decades.  They are a long-standing requirement of federal transportation legislation. The legislation requires that these plans address several planning factors – economic vitality, safety, security, accessibility, mobility, environment, system preservation, system integration and connectivity, system resiliency and reliability, and travel and tourism.  Most LRTPs are policy-based plans, as there is no federal requirement for DOTs to list individual projects in LRTPs.

The LRTP planning process is intended for each DOT to step back from its day to day duties and evaluate the users and the needs of the multimodal transportation system in its state. The needs include the state’s highways, transit services, rail operations, local systems and bicycle / pedestrian systems.  First, data is gathered and analyzed and then needs are defined.  Next, public input is solicited and priorities are determined. The resulting plan is intended to guide investments by the DOT. 

Why is an LRTP Developed?

LRTPs are developed for several reasons.  First of all, they are required.  For several decades now, federal transportation legislation has required State DOTs to develop LRTPs.  They are also used to guide overall investment in the state highway system and the various state and federal transportation funding programs the State DOT administers.  They provide an opportunity for States to define their priorities and goals, which can include system safety, system preservation, economic development or financial stewardship.

Who Participates in the LRTP Process?

When an LRTP is developed, the State DOT engages many stakeholders including local governments, the general public and other regulatory agencies, including the Federal Highway Administration (FHWA).  DOTs engage many different types of stakeholders including system users, affected public agencies, representatives of public transit employees, public ports, freight shippers, private providers of transportation, representatives of users of public transit, people with disabilities and users of the bicycle / pedestrian system.  

Who Benefits from the LRTP?

LRTPs have several beneficiaries.  The LRTP documents the policies, goals and vision for the statewide multimodal transportation system. The documentation is provided to taxpayers, regulators, the press, partners, stakeholders and other interested parties.  The LRTPs also benefit DOTs by providing justification for how the DOT makes its investment choices and other resource allocation decisions.

Example of an LRTP

The recently adopted Long Range Transportation Plan for California is an example of an LRTP.  The California Transportation Plan (CTP) provides a common framework for guiding transportation decisions and investments by all levels of the government and the private sector.  It defines the vision for transportation across the state of California: “California’s safe, resilient and universally accessible transportation system supports vibrant communities, advances racial and economic justice, and improves public and environmental health.”  California’s CTP defines objectives and a path forward for how to accomplish the vision – including specific action items.

Check out California’s CTP for yourself at, https://dot.ca.gov/-/media/dot-media/programs/transportation-planning/documents/ctp-2050-v3-a11y.pdf

Loved this post and want to learn more? Check out what we’ve done for some of our customers and see how transformative a modern database can be when it comes to managing transportation data!


Core DOT Planning Products – LRTPs and STIPs

Kristen Z, Transportation Planner

[<3 Minute Read]

State Departments of Transportation (DOTs) develop and maintain two core planning products – the Statewide Long Range Transportation Plan (LRTPs) and the Statewide Transportation Improvement Program (STIPs).

Statewide Long Range Transportation Plans (LRTPs) Overview

Federal regulations require DOTs to develop and maintain Statewide Long Range Transportation Plans (LRTPs).  LRTPs are policy-oriented plans that set long range goals for the state multi-modal transportation system. These plans incorporate safety, access and mobility.  LRTPs involve the state highway system of interstates, U.S. highways, state highways, and other transportation modes like air, bicycle, pedestrian, rail, and transit.  There are no federal requirements regarding frequency of updating LRTPs or for listing individual projects.  Since most LRTPs do not list projects, many states design and implement separate processes for identifying and prioritizing highway infrastructure projects.

Statewide Transportation Improvement Programs (STIPs) Overview

DOTs also develop and maintain Statewide Transportation Improvement Programs (STIPs).  STIPS provide a list of all projects occurring in the statewide transportation system and all projects associated with statewide transportation initiatives that will be implemented over the next four years.  Projects are listed as either individual projects (i.e. a modernization project to reconfigure an interchange on a highway) or as “bucket projects/programs” (i.e. ongoing transit operations funding program).  STIPs include projects funded with federal funding, state funding and local government funding. In fact, federal funding cannot be approved for any project unless it is specifically listed in the STIP.  STIPs typically are funded by billions of dollars and include hundreds of projects.  Many DOTs utilize EcoInteractive’s Project Tracker software, which contains an administrative portal for DOT staff to manage and track STIP projects at the update and amendment stages.

STIPs require extensive coordination with MPOs in the state because they must include the current Transportation Improvement Program (TIP) from each MPO in the state.  They also require extensive coordination with the division’s Federal Highway Administration (FHWA) office and the regional Federal Transit Administration (FTA) office because federal regulations require approval from these offices. EcoInteractive’s Project Tracker software helps with the flow the process with modules to seamlessly upload MPO TIPs and modules to receive federal review and approval. Additionally, DOTs provide regular opportunities for public input in the STIP and amend it regularly (EcoInteractive’s Project Tracker software includes a public facing portal to assist with public input).

Loved this post and want to learn more? Check out what we’ve done for some of our customers and see how transformative a modern database can be when it comes to managing transportation data!


How can we
HELP?