Welcome to STIC
(Note:  These are not user instructions, these are set-up instructions.  All of the following assume you have administrator access to the Daily Log.)

I. System Requirements
Item
Minimum
Preferred
Disk Space Local (front end)
15 MB
20 MB
Disk Space Network (back end) 
20 MB
100 MB
CPU Speed
486/100
Pentium/233
Memory
16 MB
64 MB
Video
640X480 - 256 Colors
1024X768 - True Color

II. Installation Considerations:

A. Before installing any STIC application, you need to carefully consider how you want the files to be installed.  If you are going to share the information with several computers over a network, you will need to install the file "sticdb.mdb" in a location on the network that all of the PC's can access.  This is called the "back end" of the database.  All of the other files can be installed on the network, as well, but for MUCH better performance, they should be installed on each PC.  This is called the "front end" of the database.
B. There is, of course, a problem with installing the application on each local PC.  It means that each time you receive an update, it must be installed on each PC.  To help simplify this process we recommend that you install a copy of the front end database in the same directory as the back end.  STIC will sense if there is an newer version of the software on the back end and install it on the local PC's automatically.  Otherwise, each PC will need to be visited with the new upgrade.
III. Setup
A. Start the Program
B. If you have already run another STIC application and set up the officer and location data, skip to paragraph C.
1. The very first time you run a STIC application the front end will have to find the back end.  You will see a box appear requesting the location of the backend.  In the box provided you can type the location of the backend or click on the small button beside the box ( . . .) and find the location.
2. Click on the "Update Path" button and wait.  Depending on the speed of your PC and network, you could wait more than 5 minutes for this process to complete.  (The good news is that you only have to do this once on each PC, the rest of the STIC applications will use this information, as well.)
C. If you have not registered yet, a box will pop up giving you the opportunity to register the application or Continue with the evaluation.  After 30 days of use, the option to continue will disappear.
D. The next box to pop up will be the sign on box.  The default user ID is "tqt" and the password is "tqt", as well.
E. Computer Identification:  The first time you use STIC on a PC, STIC will ask you to identify the the computer. 
1. The first column is the computer name.  This will be the name the computer is known by on the network.  You can find this name on your PC by clicking on the Control Panel, then Network.
2. The second column is the name you will give to the computer so you will know which one it is.  Sometimes the computer ID is good enough, usually it's not.
3. The third column is for the location codes.  We haven't entered those, yet so leave it blank.
4. You should be adding new computers on the bottom line of this form.  You may need to scroll down if you have more than 15 computers on line.
5. You can always return to this box later by clicking "Admin" on the Menu bar and "Computer ID" on the drop down list.
F. SETTING UP THE USERS:
1. Click on the word "Admin" in the Menu-bar and then the words "Officer Data" in the drop-down menu.
2. A form will appear to enter/alter the officer data.  Let's fill it out, Step-by-Step.
3. In the top left hand of the form there is a box called "Lookup".  Once you have officers in the database you can quickly find a specific officer by entering their radio number and pressing enter.  You can also use the drop-down button and scroll through the officers that way.  For now, let's move on.
4. In the upper right hand corner of the form is a little dot labeled "Show All".  These little dot buttons are called "Radio Buttons".  Under normal circumstances, the officer listing will show only those officers that do not have a date entered in the "Term:" box below.  By clicking the "Show All" radio button you show the officers who are no longer employed.
Note:  For historical purposes it's important to not delete officers from the database.  That's why you do not see a method for doing that.  If you MUST do this for some reason just blank out the individual fields.

5. Beginning on the next line down there is a box labeled "Radio #:".  Enter the radio or badge number for the officer.  It can be letters and/or numbers.  
6. In the next few boxes, enter the officers name; Last, First, then Middle Initial
7. The Data Tab.  You will find a lot of tabs throughout STIC.  They are a convenient method to index and access a large amount of information in a small space.  By clicking on the tab labeled "Data", you can update the following fields:  Fields in BOLD & UNDERLINE are required, all others are optional.
a) Account:  This is the account the user signs on the system with.  Some suggestions for this field might be the same ID the user access the computer/network with or leave it the same as their Radio number.
b) DOB:  enter their birth date in mm/dd/yyyy format.  Note:  ALL DATES USED IN STIC REQUIRE ALL FOUR DIGITS OF THE YEAR TO BE ENTERED.
c) SSAN:  Enter the officer's Social Security Account Number.
d) Comm. Expires:  If your area has a commission renewal process, enter that date here.
e) E-Mail:  Enter the officer's e-mail account.
f) Address:  City:  State: Self-explanatory
g) ZIP:  Requires the ZIP+4, enter zeroes if you don't know.
h) License #:  State:  Exp.:  Driver's License Number & expiration
i) Rank:  Enter the rank of the officer.  To edit the rankings, double-click inside the box.
j) Office, Pager and Home Phone Numbers.  
k) Hire Date
l) Management:  This is for reference purposes only and has no bearing on access to the STIC system(s).
m) Shift: Enter the shift this person normally works.  To edit the shifts, double-click inside the box.
n) Term:  Enter the date the person ceased to work for your department.  Once a date is entered here, the person will not show up in any of the STIC applications.
o) On Duty:  By turning this radio button off, the person will be suspended from showing up in the STIC Applications.
p) Status:  Select the person's scheduling status. To edit the choices, double-click inside the box.
q) Work Week:  Check the days of the week the person is normally scheduled to work.
r) Locker:  Enter the locker number assigned to this person.
8. The Training Tab
a) This tab is a place to record training given to the individual.  The information to be added is self-explanatory.
b) Any of the fields that have a drop-down box can be edited by double-clicking on them.
9. The Equipment Tab
a) This tab is a place to equipment issued to the individual.  The information to be added is self-explanatory.
b) Any of the fields that have a drop-down box can be edited by double-clicking on them.
10. The Emergency Tab:  Enter the information on whom and how to contact someone if the individual has an emergency.
11. The History and Status Tab
CAUTION!!!
Be very certain that you always have at least one person set to "Administrator" access on all modules.  If you remove administrator access to all individuals the only way you will get access back to the database is by shipping your entire back end database to TetraQuest Technologies and have the database re-set!!!!
a) STIC Access:  This setting applies to certain global commands for the system.  This should be set to the highest level a person has on any of the other 4 access levels.  E.g. if the individual has Administrator access on Reports, User Access on Log and No access on Parking, this setting should read Administrator.
b) Parking, Log, MSDS & Report Access:  These should be set to the level of authorization the individual needs on each of the systems.
c) System Timeout:  All of the modules in STIC will close automatically if no activity is detected in a certain time period.  Enter the number of minutes STIC should wait before signing the person off.
d) Clear Password:  If a user has forgotten their password, click this button and it will clear the password for that individual.  Caution:  Make certain the user signs on immediately after the password is reset.  They will be prompted to apply for a new password at that time.
e) Kick Off:  Checking this button will cause the individual to be forced off STIC.  It takes approximately 60 seconds to take affect.
f) Log On History:  This is a running history of all activity on STIC by this particular individual.  It lists their Account, the STIC application they started, the computer they used, their time on and their time off.
12. The Audit Tab:
a) STIC audits all critical data in the database.  This tab will show you Who changed the Roster data of this individual, the dat and time, what fields they changed and what computer they used to change it.
b) STIC does not audit the Training or Equipment information.
13. Print All:  This button will print all of the sheets of all the officer in the database.  If you have a lot of officers in the database with a lot of information, it might take a lot of paper.
14. Print Page:  This button just prints the information for the individual you are viewing.
15. Phone List (Long):  Prints a Listing of Officers and Phone Numbers.
16. Phone List (Short):  Prints the same list in tiny type.  Great for the wallet.
17. Close:  This button means we're done!
G. Setting up location codes:
1. Click on the word "Admin" on the Menu Bar and then on the word "Buildings" on the drop-down menu.  A form will pop-up called "Facility Editor"
2. The first box in the left hand corner is called "Building #".  If you already have a building numbering system for your facilities, enter that number here.  Otherwise you can add a number or leave it blank.  If you do enter a number, it must be unique, that means no two buildings may have the same number.
3. The rest of the top half of the form is self-explanatory.  Enter the address and other pertinent information for this structure.
4. The Location Code Manager:  This is where all of the STIC applications pull their location codes.
a) Code:  This is a code for each location in the facility.  Each location code MUST be unique.  That means no other building can use another's location code.  It can be 10 characters long and should be easily remembered by those using STIC.  We'll be helping them find the right codes throughout STIC but it will help everyone if they all make logical sense.  Heres some suggestions to make this easier:
(1) If you have assigned a Building number, use it.  Building #1's codes could start with B1 and each floor get an F designation like B1F1, B1F2, etc.
(2) Be certain you make a code to refer to the Facility in general, i.e. a "B1" code to refer to the entire facility or some unspecified location in the facility.
(3) If there is a parking structure that shares an address with the building, you may want to give it a G code such as B1G.  If there are several levels to the parking structure you may want to give each level a designation like B1G1, B1G2, etc.  If a parking structure has a separate address, you may want to give it its own building number.
(4) Don't forget to make a location code for the grounds around a building such as B1X for the exterior of Building #1.
(5) Make location codes for those individual departments inside a facility that are critical, that you perform a lot of services for, or that you need to separate their data from the rest of the data.  Make certain they make sense, e.g. the code for the cafeteria could be "CAF".
b) Description:  Put a brief (20 characters or less) description of the location.  This will be what appears on reports and forms.
c) Type:  Select the location type (e.g. storage, medical unit, etc.). To edit the choices, double-click inside the box.
d) Units:  There may be times when you want to enter locations but not have them in your units of service.  By removing the check in this box the location will be in the Daily Log, but not added to the units of service.
5. Index:  This button will create a printable report of all location codes grouped by buildings.
6. Print All:  This button will print all of the details on all of the buildings in the system.
7. Print Page:  This button will print all of the details of the current building
8. Navigation buttons:  In the very bottom left corner of the Facility Editor form are a set of buttons and numbers labeled "Record:".  Use these buttons to move through the different buildings you have entered.  The numbers indicate the record you are on and the number of records that have been entered.  (Note:  These will not be the building numbers.)
9. Close:  This button means we're done.
H. Setting up Activity Codes:
1. Click on the word "Admin" on the Menu Bar and then on the word "Activity Codes" on the drop-down menu.  A form will pop-up called "Activity Codes".
2. Code:  Enter a number between 1 and 199 for the activity.
a) Be certain to leave the activity code "0" in for "No Code"  The STIC expects to see 0 in the list.
b) All of the Activity Codes 200 and above are reserved for STIC use.  You can change any of the check boxes or the weight box on them, just be certain to leave the code and description alone.
3. Description:  Enter a plain text description of the activity (up to 50 characters).  STIC has provided a sample of Activity Codes and descriptions for you to use if you like.
4. Log?:  Check this box if you wish to see this code in the daily log.
a) If you wish to temporarily stop using a code but might want to use it later, un-check this box.
b) For codes 200 and higher:  
(1) If you are using STIC Parking Control be certain to uncheck the Log? box beside Tickets (Code 220).  This will enable STIC to count the actual number of tickets that have been entered into the system when calculating Units of Service.
(2) If you are using STIC Reports Pro be certain to uncheck the Log? boxes beside the report codes (Codes 200, 201, 202, 203 and 209). This will enable STIC to count the actual number of reports that have been entered into the system when calculating Units of Service.
(3) If you enable any of the Ala? Boxes to record alarm events, uncheck the Log? box beside code 209 so STIC can calculate the number of alarm reports for the Units of Service.  Also, be certain to uncheck the Unit? box next to each type of alarm code.
5. Sig?:  There are certain reports, called Highlight Reports, that will only show those codes that are checked here.  Select those reports that you would expect to see in a highlight of report of your daily events.  (e.g. You would certainly want to see a list of all the fires in the facility but certainly would not want to see every patrol round.)
6. Txt?:  Select this box to give the person entering the log entry a visual reminder that this code requires a disposition narrative.
7. Ala?:  If this log entry would require an alarm report to be filed, check this box and the person entering the alarm will receive an alarm report form when they enter the code.  If you check a box here, the Unit? box will automatically be unchecked.  Also, remember to uncheck the Log? box next to the  code #209.
8. Unit?:  Check this box if you want to have this code added to the units of service.  Remember, this box will be unchecked if the Ala? box is checked and vice versa.
9. Weight:  For most units of service, you will want to leave this set to "1/1".  However, if there is an activity that is super-easy, you can raise the first number to weight againt that activity.  Example:  if an officer can check 150 fire extinguishers in a shift, you may not want to count every check as a unit of service.  Instead, by changint the weight to "6/1" the officer would get a unit of service for every 6 extinguishers checked.  The opposite is true as well.  If you had an activity that requires more work than normal tasks, just increase the second number.  Yes, you can get cute here and have ratios like 23/12 or 7/13 but . . .
Note:  The Code #250, Log Activity, is preset to 8/1.  This is how officers/dispatcher obtain units of service for their activity.  One unit of service for every 8 entries.
Note:  Setting any number in the ratio to 0 will cause that code to not be counted as a unit of service.
I. Alarm Set Up:
1. If you have set up an activity code that demands an alarm report to be filed, you may wish to do some setup on the alarm form.  Click on the word "Admin" on the Menu Bar and then on the word "Alarms" on the drop-down menu.  A form will pop-up called "Alarm Reports".  Click on the button labeled "Editor".  The Alarms Editor form will appear.
2. Using the Alarms Editor will be covered in the user guide.  We just need to set up 2 of the drop-down boxes for now.
a) Cause:  Double click on the box labeled cause.  A form will pop-up listing all the available causes for fire alarms.  Don't confuse this with the Alarm Type.  An Intrusion alarm is an alarm type, the cause can be an intrusion, accidental trip or other phenomena.  If the check box labels "Fire" is selected then an extra tab on the Alarms Editor form will appear when a report is given this cause.  This tab will ask the author additional information pertinent to fire alarms.
b) Alarm out of Service:  You can set this to simply yes or no or actually list zones that are taken out of service.  Double-clicking in the box will take you to the form to set this up.
IV.  We're done!!!!  Now go to the user's guide to get started!



