Splash Image Splash Title

The Master Scheduler


The Master Scheduler. Originally prototyped at the APTA Annual Convention in the fall of 1991, TMS became a production system at Phoenix Transit in 1993.

Product History

When TMS was conceived of, we knew that the next wave of PC-based computing would occur in a Microsoft Windows environment. With that in mind, we embarked upon the creation of the first Windows-based Public Transit Scheduling System. We also knew that computing in the future would be based around component-built systems. This meant that rather than building a street map and reporting interface to the system, we would research the market and integrate those portions into the final product.

When TMS moved from prototype to production at Phoenix Transit in 1993, it brought with it the first successful public transit integration of the highly-respected MapInfo for Windows and Crystal Reports products.

TMS itself follows a table-driven relational database model. Data components, such as routes, patterns, trips, and blocks are all directly input into the system, or are generated based on input data. Node-to-node running, travel, and deadhead times are kept in a central location, offering ease-of-use whenever the data has to be viewed or modified. Blocking can be performed either manually or optimally in the system. The TMS Optimal Blocker offers trip-to-vehicle assignments that are mathematically provable as the most cost-efficient. The TMS Runcutter also runs in manual and optimal modes, and produces beautifully-cut runs based on user-defined costing rules. The TMS Rostering Module creates weekly assignments that maximize the number of consecutive days off. Our Bidding Module allows for "cafeteria-style" operator bidding. Our Trip Planner can produce multiple itineraries in several languages.

Schedule Masters, Inc. adheres to a relatively unique model in the transit software business - all our customers have and use the same release of the software. There are no "one-offs". Any time the system is enhanced, all customers benefit from the enhancement.


We can talk to your systems

The dynamic nature of the TMS database allows us to construct data downloads to your existing systems. For example, the download to the Precursor system, described below, took us under a day to write and implement. If you need schedule data downloaded to other systems, talk to us!

Novell



Yes, TMS runs with NetWare. We've been certified by Novell Labs since 1991 as having a product that's network aware and network ready.

Look for the TMS listing inĀ http://developer.novell.com/nss/

Mapinfo



MapInfo for Windows is used by TMS to geocode timepoints in the TMS database, and to perform proximity searches for the Trip Planner. When TMS sees the longitude/latitude data generated by the geocoding process, it knows how to automatically calculate node-to-node mileages.

MapInfo is also used to show route mapping. Once displayed, the map can easily be imported into any desktop publishing system, and, along with trip data from TMS, can be used for the in-house production of public timetables.

The many possibilities of MapInfo in a Public Transit environment are not restricted to geocoding and route display. Please see the excellent MapInfo web site at http://www.mapinfo.com for more information, and then contact us at sales@themasterscheduler.com.

Crystal Reports


Crystal Reports is the backbone of the TMS reporting engine. Our software is shipped with a number of user-modifiable Crystal Reports templates. When a report is called for within TMS, the Crystal Engine displays it directly on the screen, and offers the scheduler printing and exporting options. The entire Crystal Reports package is bundled with TMS. Complimentary reports to those furnished with TMS can be defined and generated at any time. Please take a moment to visit the Crystal Reports site at http://www.crystaldecisions.com, and then let us assist you further by emailing us at sales@themasterscheduler.com.