Evaluation, Management, and Support

Evaluation, Management, and Support

Dane Conrad (Forrest County School District, USA)
Copyright: © 2013 |Pages: 19
DOI: 10.4018/978-1-4666-2656-0.ch014
OnDemand PDF Download:
$30.00
List Price: $37.50

Abstract

A technology leader’s day-to-day responsibilities and tasks can be divided into three basic categories: evaluation, management, and support. Evaluation involves making informed decisions and planning tasks when considering new technologies. Management not only maintains the infrastructure of technology systems, but also the data that flows through the system. Finally, support covers the responsibilities related to customer service for the technology leaders’ end-user environment. Each category poses a unique challenge to technology leaders and requires them to be both adaptable and consistent. This chapter explores these three areas giving detailed insights into topics and concerns within each.
Chapter Preview
Top

Evaluation Of Relevant Technologies

Successful technology leaders implement technologies only after careful consideration and evaluation. In best case scenarios, the technology leader is able to establish a working test lab environment, garner demonstration copies of software or hardware units, complete an extended test of normal or expected user interaction over time, allow small sample of users to experiment with the technology, and then make an informed decision about whether to go forward with implementation or to look for another solution. Many times however, this scenario is not fully possible due to upper administration timelines, availability of test equipment, or lack of staff expertise. In spite of these challenges, there are many traditional factors to consider in the evaluation process. Common evaluation factors to consider in evaluating a solution include:

  • Total cost of ownership (TCO): What are the hidden costs like having to upgrade existing server hardware or operating system, technical training, required peripherals, and proprietary components?

  • Fulfills Discovered Instructional or Administrative Need: Does the technology actually do what people need that technology to do (when and how)?

  • Integration into Existing Authentication Scheme (Active Directory, Open Directory): Will the technology allow for the existing user database to be incorporated for rights management, drive mapping, directory syncing, etc.?

  • Compatibility with Main Instructional or Administrative Software Applications or Hardware: Will the new application run on existing hardware or will the new hardware run existing software?

  • Recommendations/Feedback from Existing Users in other Districts or Businesses: What do other organizations who already use the technology say about its performance?

  • Availability of the product during the time frame needed: Will the technology leader be able to obtain the item during a specific time frame that fits into the implementation or project management plans?

  • Ease of Use: How much training will be necessary for new users to incorporate the technology efficiently?

  • Warranty/Support Mechanisms: How will the user or administrator obtain or acquire timely support (e.g., phone, online documentation, onsite engineer, chat)?

Complete Chapter List

Search this Book:
Reset