|
|
| Line 1: |
Line 1: |
| <!-- table for the whole page -->
| | #REDIRECT [[Main_Page]] |
| {| style="width:100%; vertical-align:top; "
| |
| | |
| <!-- include the TOC as a template in the first column -->
| |
| | style="width:250px; vertical-align:top; padding:2px 15px 2px 2px;" | {{GettingStartedTOC}}
| |
| | |
| <!-- here is the second column of the full wiki page - will contain content -->
| |
| | style="vertical-align:top; padding:20px 20px 20px 2px;" |
| |
| | |
| <!-- here is a table for the content of the page -->
| |
| {| style="width:100%; vertical-align:top; "
| |
| | |
| | style="vertical-align:top; font-size:160%; color:#7c1911; " | '''Plan for the Success of Your Trac System''' <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " | <br />Correctly planning for your Trac System and features is crucial to the success of your Trac System. The Trac System is highly customizable and flexible to accommodate your unique needs. It is (if set up properly) a simple system for your users to operate. It can be a complex system for your users if set up with too many options for every user to perform functions in the Trac System. Careful thought should be used throughout the planning process. An individual or team of individuals should have the role of setting up the Trac System. The implementation team should work with the Redrock Support Team to review the Trac System and determine which options will be implemented. Prioritize the Trac System features to set up and establish a timeline to implement and test the features. The team organizes the implementation with Redrock Support and follows up through scheduled phone training sessions. Continue to review your Trac System for changes that can improve your operations and discuss these with Redrock Support as needed.<BR /><BR />
| |
| | |
| ...And don't forget to enjoy yourself! Exploring and implementing a new system that will change and enhance your services is exciting (and a bit frightening!) but remember to look forward and that Redrock Support is here for you.<BR />
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:140%; color:#7c1911; padding:30px 0px 0px 0px;" | Form a Team to Implement and Support Your Trac System <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " | Your Implementation Team might just be one individual or it might be a group of 3 to 5 individuals. We recommend that you try to keep your team to a maximum of 5 people to maintain efficiency and productivity. There should be one person that takes the ''Technical Lead'' for the team. This is the most important role in the team and this individual should be selected based on two primary factors: technical aptitude and cooperative attitude. If you only have a team of one, then this individual needs to be selected for their attributes as the Technical Lead. Other roles that need to be filled in the group would be ''User Liaison'', ''IT Liaison'', and ''Trainer''. These roles might be filled by a single individual or by multiple individuals, but it is important that there be a person on the team that can work directly with the users of the Trac System at your institution, a person that can receive quick and direct access to a member in the IT Department, and a person to train the other users on the program features.<BR /><BR />
| |
| | |
| ''Technical Lead''<BR />
| |
| The Technical Lead is primarily responsible for conducting training sessions with Redrock Support and learning the full configuration and set up of the Trac System. The Technical Lead does not have to have a technical background, however, this individual needs to have the ability to learn software applications, and translate technical information to the 'common' user. The Technical Lead will often be the lead of the Implementation Team even if this user is not in a role of authority with their other responsibilities. The Technical Lead will often share the roles of ''User Liaison'' and/or ''Trainer''.<BR /><BR />
| |
| | |
| ''User Liaison''<BR />
| |
| The User Liaison is primarily responsible for representing the needs of the users. There may be multiple User Liaisons to represent the needs of different departments. The User Liaison often shares the role of ''Trainer'' and is responsible for showing users how to work in the Trac System.<BR /><BR />
| |
| | |
| ''IT Liaison''<BR />
| |
| The IT Liaison is primarily responsible for representing the IT Department and addressing their concerns. The Trac System can interoperate with Student Information Systems, Campus Authentication Systems, Campus Portals, etc. and the IT Department will need to be involved in any of those aspects of the implementation.<BR /><BR />
| |
| | |
| ''Trainer''<BR />
| |
| The Trainer is primarily responsible for introducing the Trac System to the users and demonstrates how the users will operate in the Trac System. The Trainer will often share the role of ''User Liaison'' and is responsible for representing the needs of the users in the sessions conducted with Redrock Support and the Implementation Team.<BR />
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:140%; color:#7c1911; padding:30px 0px 0px 0px;" | Review the Trac System with Redrock Support <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " | Now that your Implementation Team has been formed, it is time to schedule a couple of introductory sessions with the Redrock Support Team. Your first session or two should be to review the capabilities of the Trac System. You will find during these sessions that the Trac System can be configured to meet just about any possible scenario. The sessions will last 45-60 minutes and are scheduled from the Training Request Form from the Trac product web pages.<BR /><BR />
| |
| | |
| Redrock Support will review the standard options for recording visits, scheduling appointments, checking out resources, and utilizing modules. A majority of your configuration will be set up within preferences and settings that you can access and enable or disable through your SysAdmin accounts. Some items discussed will require some customization by the Redrock Support team. During these sessions, your Implementation Team will just be in the 'sponge phase' and soaking up information. There will be many decisions to be made, but first, just take the time to explore the options and discover what the Trac System offers you.<BR /><BR />
| |
| | |
| Keep a written list of features that you want to implement or review in more depth with Redrock Support. This list will be your foundation as you continue further into the set up process.<BR />
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:140%; color:#7c1911; padding:30px 0px 0px 0px;" | Decide Options to Implement in Your Trac System <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " | After your review of the Trac System and options, your Implementation Team will meet together, with or without Redrock Support, and start making decisions on how to set up the Trac System. Use your list to organize and prioritize the Trac System options. This will be the primary role of the User and IT Liaisons as they represent the different departments with an interest in the Trac System. Each of the liaisons will have requirements of the Trac System to meet the needs of their users.<BR /><BR />
| |
| | |
| When deciding the options to implement, organize them into a prioritized list to be set up and tested.<BR />
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:140%; color:#7c1911; padding:30px 0px 0px 0px;" | Establish a Timeline to Implement and Test Features <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " | With your prioritized list of features to implement, you can now work with Redrock Support to set up a timeline to implement the features in your Trac System. Most of the basics (recording visits and scheduling appointments) are simple to set up and are usually at the top of the priorities. Setting up several groups with different levels of access will typically take more time to get in place so usually takes place after the basics. Customizations, such as LDAP Authentication or Data Imports from your student information system, are usually discussed early on, but should not delay the implementation of other features.<BR /><BR />
| |
| | |
| Your timeline should set clear benchmarks for testing features in your Trac System and 'signing off' on their progress. Your Implementation Team sets these benchmarks and assigns members of the team responsible for their follow-up. Your Implementation Team schedules training sessions to follow progress, make adjustments, and complete tasks.<BR />
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:140%; color:#7c1911; padding:30px 0px 0px 0px;" | Follow-up With Your Team and Redrock Support <HR>
| |
| | |
| |-
| |
| | style="vertical-align:top; font-size:120%; " | After your priority items have been set up and tested on your Trac System, your Implementation Team will work with Redrock Support to make any necessary adjustments. Your needs may change. Users may change their minds about some system settings and configuration. New features may be introduced to the Trac System that your team will want to consider for your Trac System. Users may introduce new questions that your team does not know how to answer. There are many reasons to continue to follow-up with Redrock Support. Do not hesitate to work with support when needed.<BR /><BR />
| |
| | |
| |-
| |
| | style="width:100%;" |
| |
| | |
| <!-- this table appears at the bottom of the manual page and contains a previous page and next page link -->
| |
| {| style="width:70%; vertical-align:top; "
| |
| | |
| | style="width:50%; text-align:left;" | [[Support Resources|← Previous Page]]
| |
| | style="width:50%; text-align:right;" | [[Install|Next Page →]]
| |
| | |
| |}
| |
| |}
| |
| |}
| |
| | |
| __NOTOC__
| |