TIMS-SQLPreparing for the Conversion

TIMS-SQL: Introduction

TIMS-SQL will be installed in two parts. Part 1 = ‘TIMS-SQL’ is similar to what you use now –

use the launch pad to enter different modules. Windows are slightly different/more streamlined. This is where you will make map edits, run maintenance and use boundary planning.

Part 2 = ‘ESQL’ module. Most users can accomplish 95% of their daily work with this module. Here you will find easy to use screens that include tabbed pages to navigate and windows that can be docked and undocked for custom screen layouts.

TIMS-SQL

We expect the complete process of converting all NC LEA’s to take between 2 - 3 years.

Things we are taking into consideration to choose sites for conversion. You must have a GIS map in place (real world x/y

coordinates) Hardware meets specs set by Edulog SQL Database Software purchased by LEA if

necessary No major redistricting or opening/closing of schools

planned in the near future “Clean” Data (more on this on the next slides) “Best Practice” implementation (upstu’s, backups

etc.) LEA’s that have expressed desire to convert

TIMS-SQL Preparing for the Conversion

All schools will need to be located at addresses (no more locating at the node number.) Suggestion: number

your school driveway segments 1-199, 2-200. Then relocate your schools to ‘199 Manteo High School Dr’ or whatever number would put the school at the appropriate place on the segment.

199 Manteo High School Dr

School Relocation Steps

Create a backup of TIMS before you begin Make segment/address edits in MARIS and run

the appropriate maintenance Pull up the school in schools/tabular and click

on the ‘relocate’ button Beside ‘New Location’ enter the address where

you want the school to be located (this will be where you want the buses to go) then Confirm

Run POSTRELOCATESCHOOL in EMU. You may need to create this batch

**Also make sure you relocate (edit location) your School Landmarks in

MARIS**

Relocate Stops to addresses

Create a report to identify any stops that are located at nodes – these will need to be relocated to addresses

Click on the following to create the report: Report User defined Stops/Runs/Routes Add New title: 01. Stop Locations - OK Stop Location – contains text - # Done - Done Do you want to run this query now? Yes/OK Choose Stop Stop ID and Stop Location and Run RunID Done/Run Query

TIMS-SQL

The report you just created will give you a list of all stops and checkpoints that will need to be relocated

The RunID is included in this report to identify the runs the checkpoints are on; unfortunately this will cause the ‘school stops’ to show up several times, but you only have to relocate the school stop once using the stops/tabular/relocate function

For each checkpoint you will have to go to the run, de-assign the checkpoint and recreate it using the correct address

Corner stops do not need to be relocated if they were created using two street names (i.e.: Elm St & Pine St); if they were located at a node (#4335) then you would need to locate them using the intersecting street names.

TIMS-SQL

School/Grade Make sure you have all of your grades listed

correctly in each school; delete any grades not currently being used. Make sure you have added PK, P1, P2, P3, P4 and the associated bell times.

Reports Under the User Defined Reports menu, review

all of your reports to make sure they all run properly (no errors or messed up formatting). Delete any reports that you don’t use.

TIMS-SQL

Worklists Under your LIST menu

go through and delete any worklists you don’t use regularly. In TIMS-SQL there is an

option to display or bring up a list in tabular mode by choosing the school code/grade with a drop down box, so you do not need a worklist for each school – clear those out if you have them in your current data

Parts of the last name and district ID number have been blocked in this screen shot.

TIMS-SQL

Clean out Boundaries Go through your list of Boundaries and

Delete any that you know you will not need. If you have ‘old boundaries’ that you wish to keep for historical purposes please take this time to rename them appropriately. Putting a year date on old boundaries may be a good idea in case you need to refer to them in the future. North Middle School 08-09 08-09 North Middle School

Boundary Cleanup

Take some time to review boundaries carefully. You want to make sure boundary points are inserted correctly, streets are split where necessary and the addressing on each side of the split is correct for the associated boundary.

Here are the types of errors I’ve seen this week in different LEA’s data…these need correction! What is the exact

address point where this boundary stops and the next one starts?

Should a boundary point be snapped to the intersection?

Be careful not to cut the ends of the streets out of the boundary.

When you draw in new streets remember to go back to your boundaries to make sure the streets are included in the boundaries you need them to be.

These boundary points are not necessary, and could cause addressing to show up in these boundaries by mistake.

Here is seems that someone tried to trace the street manually rather than using the ‘trace street’ method. This will cause addressing to show up in the wrong boundaries.

Correct Splitting of a Street

Using the ‘trace street’ method will create a boundary to run down the exact middle of a segment. Create a fat map in Autostreeter to get a better view of how your

boundaries are drawn in.

Correct ‘saw-tooth’ method

TIMS-SQL When your time to convert to TIMS-SQL

draws near your project leader will diagnose your data and review any other items that need attention with you.

Best Practices

Regular (daily/weekly) UPSTU’s Daily backups locally Weekly transfer of backup to Core FTP GIS or MARIS (add/edit new streets and/or

addresses) updates as necessary to keep your map up to date  

Daily EMU maintenance

Plus more…check document on the ncbussafety website for more information