Hard Ware and Network Servicing: Information Sheet
Hard Ware and Network Servicing: Information Sheet
Hard Ware and Network Servicing: Information Sheet
MODULE DESCRIPTION:
This module defines the competence required to apply skills and knowledge in using new or upgraded
technology, with the knowledge, skills and right attitudes.
Talk to vendors and other IT professionals to learn as much as possible about the new technology and other
related technologies.
Use IT magazines and other journals to learn about the technology including legal and political impacts.
See how this technology compares with the existing technology to get an idea of the magnitude of the impact
on the organisational functions.
Gather information about the business strategies
Your choice of new technology should comply with the company’s overall business strategy. The strategies of the
business may promote or hinder the application of new technology.
Identify the stakeholders
Stakeholders are the people who have a share or an interest in the business and will be affected by the new technology.
The acceptance of the new technology into the organisation will be increased when you take the needs of all
stakeholders into account before choosing the new technology.
Technical skills
Once a new technology is identified, it is fundamental that you gain the technical skills necessary before migrating to
it. These technical skills may relate to hardware, software, network, PC support or programming knowledge.
Building technical skills is an ongoing and never-ending process for an IT professional. While you rely on your
existing technical knowledge to identify new technologies, you would need to acquire new skills before you can
successfully implement a new technology into the organisation.
Managerial skills
It is important that the IT professional be conversant in managerial and design skills so that new technology is chosen
and implemented in line with business objectives.
Think about the impact of tasks on business as a whole rather than provide solutions for individual tasks.
Concentrate more on end-user experience with new technologies rather than the technology itself.
Modify existing accounting package and retrain users. Or, purchase a BAS-ready accounting package.
Build quotation report software. Provide networked PCs and printers to front counter staff and train them.
Technologies that boost, aid or enhance production/manufacture of goods. Tools, machines and utensils used
for production would fall in to this category. The primary purpose of investing in these types of technologies in
business is to reduce costs, increase flexibility and/or improve the quality of the product, such as machines that
assemble car components with greater precision.
Technologies for the ‘production’ of technical services such as a wide area network (WAN) and computer
software development.
Automation
Automation technologies include:
technologies that automate the tasks that are labour intensive or dangerous, eg human-like machines (robots) to
perform very specific production tasks and point of sale terminals at a warehouse.
Technologies that improve services
Technologies that improve the quality of services will lead to increased profit by drawing clients back for more
service, eg more accurate diagnostics in the medical field made possible by new technologies and automated patient
monitoring in hospitals.
Technologies in design
Design technologies include:
technologies that are used to design or develop a new product or service such as Computer Aided Drafting
(CAD) and Computer Aided Systems Design (CASD)
technologies that promote innovation by introducing new, more efficient, cost effective and improved quality
services or products to the consumer.
reduced costs
existing resources being utilised to optimum capacity resulting in better products and better ways of
conducting business
increased flexibility.
A new technology that does not lead to real benefits to the organisation cannot be justified.
Centralisation/accessibility
Horizon scanning — talk to your circle of friends or other IT professionals. Browse through published reports.
Read IT magazines and the World Wide Web to identify new technologies that are proven to be a success.
Collective scanning — attend meetings of IT professionals such as the Systems Administrator’s Guild to
discuss their findings.
Scalability
Can the new technology cope with growth of the organisation?
Use a rating scale such as: 1 = poor, 2 = below average, 3 = average, 4 = good, 5 = excellent, to compare
alternative technologies.
tasks involved
resources required
schedule
Organisational issues.
Timing
Timing is an important consideration if the implementation is to go smoothly. The adoption of new technology can
place an additional burden on staff having to deal with disruption to their normal workflow. Most departments have
peak periods of activity that should be avoided. For example, an accounting department’s busiest time is the end of the
financial year; therefore this period is definitely not suitable for any implementation of new technology.
Tasks
What are the things that have to get done to implement the new technology? The implementation plan should clearly
identify these tasks and schedule them in an appropriate sequence. Installing a network, for example, will have a
different set of tasks from installing a new software system.
Table 1 shows the tasks required to install new PCs for a group of users.
Table 1: Tasks for installing new PCs
Task Description
1 Back up files on existing computers
2 Remove existing computers
3 Install new computers
4 Test new computers
5 Restore files to new computers
Identifying the tasks and their sequence beforehand should ensure that the implementation goes smoothly. This is a
very simple example, but can you imagine what would happen if Task 2 was performed without performing Task 1?
Resources
Having identified the tasks, the next step is to allocate people and resources to them. To minimize confusion, people
need to know exactly what they are supposed to do. Obtaining resources may involve negotiating with the people
involved or their superiors as they may have other commitments. Table 2 provides an example of resources required
for installing new PCs.
Table 2: Resources required while performing implementation tasks
Task Description Human Resource (tools)
resource
1 Back up files on existing Jessica Gilflan Portable HDD and backup software
computers
2 Remove existing computers John Clark Trolley, packaging tools and inventory forms
3 Install new computers John Clark Trolley and inventory forms
4 Test new computers Mary Lan Testing software and checklist
5 Restore files to new computers Jessica Gilflan Portable HDD and backup software
Schedule
After assigning resources to each task, the next step is to determine how long each task will take to complete. Work
out the start and finish date of each task. Then communicate this to those involved so that they know exactly when
particular tasks are to be done. Table 3 below shows the start and finish dates for each task so that staff know when
the tasks are to be completed. This means that your plan should provide a picture of:
who is to do it
when it is to be completed.
Table 3: Task duration
Task Description Resource Start Date Finish Date
1 Back up files on existing computers Jessica Gilflan 1st Sept 1st Sept
2 Remove existing computers John Clark 2nd Sept 3rd Sept
3 Install new computers John Clark 4th Sept 9th Sept
4 Test new computers Mary Lan 10th Sept 14th Sept
5 Restore files to new computers Jessica Gilflan 15th Sept 15th Sept
Milestones
Milestones are established points in the project used to determine whether or not the project will meet the anticipated
schedule. These are usually major events in the course of the project such as ‘installing new computers’ or ‘software
purchased’.
It is important to establish milestones in your implementation plan and monitor the progress of the implementation on
an ongoing basis. You can also gather project progress reports from implementation team members.
Organisational issues
Any impact on the day-to-day running of the business needs to be identified and planned for. For example the
installation may require that the network not be operational for a period of time. Therefore it should be scheduled for a
time when it will have as minimal an impact as possible, for example, after hours. Sometimes it is difficult to identify
downtime when no one would be affected. In all cases, users who will be affected need to have sufficient warning in
terms of days not hours.
User acceptance
User acceptance of new technology is usually based on:
user-friendliness of the new system
management making it known that staff are expected to use the new technology
identified benefits of the new technology for the users of the system
training provided to ensure that users are comfortable with the new technology and commitment by
management to support staff during the initial stages of use
clear and communicated commitment by management to support the introduction of the new system.
User competence
Training and user support are very important. Without this, you may as well not install the new technology because
the benefit it was intended to bring will not be realised. Not only does training need to occur when the technology is
first installed but it has to be provided on an ongoing basis according to need. Part of the continuing management
function is to analyse the skills users require and ensure that they have them.
Not only do users need to be competent in their use of technology but they need to be well supported in its use as well.
The help desk is an important support tool. Its effectiveness relies upon it being continually monitored.
Does the hardware ever breakdown, eg hard drive crash or system prone to overheating?
Does the network fail, eg device not found or print jobs not being received?
Reflect
Think of a time when you felt apprehensive about using some new technology. What could have been done to make
you less apprehensive about using it?
Feedback
You probably would have appreciated a training session that showed you how to use the technology by applying it to a
familiar problem.
Converting data
A key ingredient of the success of the implementation of new technology is the seamless accessing of data. At some
point the new technology will replace the existing technology (unless there was nothing prior). This usually involves a
conversion process of some kind. The conversion process should ensure that:
Information Sheet for ICT Dep. Date: Sept, 2016
Hardware and Network Service Level IV
Page 13 of 23
TTLM Code : ICT HNS4 TTLM04 1016 Dodota TVET College ICT Department
Learning Module Migrate to New Technology
the data is complete and valid
the structural integrity of both the legacy system and the new database/data warehouse is sound
the data reflects and works with the business rules and data standards
Types of conversion
1. Direct conversion
This is the implementation of the new system and the immediate discontinuance of the old system. Once the
conversion is made there is no way of going back to the old system. It is inexpensive, but involves a high risk of
failure because the entire system is converted at once and going back to the old system will create a lot of hassle and
problems.
This approach is appropriate when:
the design of the new system is drastically different from that of the old system and comparisons between
systems would be meaningless.
2. Parallel conversion
This is an approach where both the old and the new system operate simultaneously for some period of time until a
thorough evaluation is completed. It is the opposite of direct conversion. A high degree of protection from system
failure is provided, but parallel conversion is costly. Usually though, if this conversion type fits in with the
organisation’s IT plan then the extra expense is warranted.
3. Phase-in conversion
This approach allows for a segmented system to be gradually implemented over time until the old system is fully
replaced. Unlike direct or parallel conversion, phase-in conversion uses a step-by-step process of converting one
segment at a time. This method avoids the risk inherent with direct conversion while allowing users to get used to the
new system gradually. The cost of temporary interfaces with the old system, along with not giving IT professionals the
satisfaction of implementing the system in its entirety, can be negative factors in this type of conversion.
4. Pilot conversion
This method segments the organisation, providing a ‘guinea pig’ branch or office where the new system proves itself
before conversion is performed elsewhere. Pilot conversion is less risky than direct conversion and less costly than
parallel conversion, and is preferred where the new system is drastically different from the old. A disadvantage is that
more time is required for full and complete conversion, but this time can be put to good use by training all users at the
pilot test site.
changing the data structure (eg restructuring the fields in a database, converting EBCDIC to ASCII format)
Training and support — showing people how to use technology is often a more effective method than the
trial and error approach.
Direct knowledge can be shared through teamwork, socialisation and informal communication.
Contribute to a knowledge base that will formally document procedures, processes and experiences to capture
the experiences of various people.
Awareness of benefits
Users are more likely to accept new technology if they are aware of the benefits expected from implementation. In the
long run, this would translate into improved organisational practice. Therefore, it would help to highlight the benefits
specific to particular user groups throughout the implementation process. The types of benefits can cover the
following aspects:
new features, performance and breakthroughs
increased productivity
operational benefits
maintenance benefits
reduced waste
administrative benefits
advanced communications
OH&S implications
The implementation of new technology may sometimes change the occupational health and safety (OH&S) conditions
in the workplace. Any new technology that is purchased must be assessed against the compliance requirements of
occupational health and safety standards. The rigour of assessment will depend on the complexity and the novelty of
the technology.
The scope of the assessment process could range from observations to safety training, depending on the nature of the
technology. For example, staff must be educated in ergonomic issues if computer equipment is going to be introduced
and change the set up of their workstations. If new machinery is introduced, workers must be conversant with the
health and safety guidelines before operating it. These guidelines usually come from the manufacturer.
Learning time is reduced as it is easier to learn from past successes and mistakes rather than ‘re-inventing the
wheel’.
Staff satisfaction will increase as they are getting the recognition for their knowledge and innovations.
It is best practice in an organisation to use various tactics such as employee recognition and reward schemes
toencourage all employees to contribute to a knowledge base. A knowledge base typically refers to a database that
holds knowledge in a variety of forms such as facts and rules, and case examples about successful business practices.
Planning evaluation
The evaluation plan should be flexible enough to accommodate new questions and information sources. Here are some
strategies in planning evaluation:
Obtain a list of all stakeholders of the new technology.
Identify stakeholders that must be consulted to evaluate the performance and usability of the system. Ensure
that the sample chosen includes users, power users, support personnel, managers as well as customers (if applicable).
Identify any other data sources to collect information such as documents, reports, performance logs, etc.
Identify key performance indicators with regard to performance and usability of the software applications and
hardware.
Determine the resources that are needed to carry out the evaluation.
Identify the methodologies that will be used to conduct the evaluation. The possible methodologies are:
observations, questionnaires, walkthroughs, interviews, focus groups, etc.
Analyse the information collected and compare it against the targets of performance and usability.
Recommend potential enhancements to the system and identify any shortcomings of the implementation for
the benefit of future projects.
Information Sheet for ICT Dep. Date: Sept, 2016
Hardware and Network Service Level IV
Page 18 of 23
TTLM Code : ICT HNS4 TTLM04 1016 Dodota TVET College ICT Department
Learning Module Migrate to New Technology
Key indicators of usability and performance
The overall objective of conducting usability and performance evaluation is to recommend changes that will
contribute to increase user acceptance, increase productivity, decrease training and learning times, and increase
business performance.
Key indicators of usability
Usability of the system measures hardware and software user interface with respect to attributes such as ease of
learning, ease of use and satisfaction in meeting user needs. A usable system ensures that the user can access the
required feature instantly through its well-planned user interface. It also ensures that all control features are
consistently presented so would need minimum training to identify various processes within the system.
Ease of use — users find it easy to apply to their intended tasks.
Sufficient and easily accessible user support. Users are satisfied with the support procedures such as help
screen with context sensitive help, knowledge bases, help desk, etc.
Satisfactory initial experience. Users have successful initial experience with the software and/or hardware.
Integration with existing processes. The new system integrates well with existing processes.
Overall system capability. Users are satisfied with the overall capability and usefulness of the system.
Key indicators of performance
Performance of the system measures the reliability of the hardware and software. It includes:
error rate
Resources
Labour
Infrastructure
environmental issues relating to disposal of obsolete computer supplies, hardware and other equipment
Information Sheet for ICT Dep. Date: Sept, 2016
Hardware and Network Service Level IV
Page 19 of 23
TTLM Code : ICT HNS4 TTLM04 1016 Dodota TVET College ICT Department
Learning Module Migrate to New Technology
environmental issues relating to communication devices, wireless communication devices in particular
the apparent need of many organisations to purchase large numbers of new computers. (It is estimated
that 1.8 tons of raw materials are required to produce the average desktop personal computer and
monitor. Imagine the negative impact of the production on the environment!)
Another major consideration when purchasing new equipment is whether it is designed with environmental attributes.
The environmental responsibility does not stop there. The users of technology must do so responsibly by using
software and hardware that can reduce wastage as well as minimise printed material and energy consumption, etc.
Using feedback
The value of feedback
Feedback is extremely valuable in the evaluation of hardware and software as it provides an effective balance for your
own observations and walkthroughs on the system. This is an ongoing process of keeping IT professionals informed of
the performance and usability of the system and should not be treated as merely an event.
While positive feedback reinforces the implementation of the system, negative feedback provides very valuable
information about how to improve the usability and the performance of the system. The performance improvements
made due to the feedback will ultimately benefit the organisation.
Gathering feedback
The goal of collecting feedback from users and gathering information from other sources is to enable the technology
committee to assess how well the software and hardware implementation is satisfying the key usability and
performance indicators.
Sources of information
You can gather data from people, documents, performance data, observation of events or any other empirical method
such as experiments and benchmarking.
Basic feedback gathering methods
The ideal form of feedback gathering is to use a combination of the following methods depending on time and
organisational factors.
Observations, walkthroughs and site visits
These are conducted to get first hand information on performance and usability features of the system. The internal or
external evaluators will observe all stakeholders using the technology and observe usability and performance
indicators of the system.
Walkthroughs are conducted where an evaluator walks through a certain feature to assess how the system performs
that feature with respect to usability and performance indicators.
Interviews
Here are some tips for conducting interviews:
Choose stakeholders who would have greater or unique involvement with the new system.
Don’t interrupt.
Be a good listener.
Take notes.
Be prepared with prompting questions to start the discussions about usability and performance of the system.
Engage a note-taker.
Surveys and questionnaires
These are used to gather quantifiable data about the system from a large number of people. You should make
allowances for the low response rate and the slow response time. Here are some tips for conducting surveys:
State the objective of the survey as evaluating the performance and usability of the new technology.
The performance measurements such as error rates will be quantitative and will be easy to interpret.
Performance measurements such as reliability could be a combination of qualitative and quantitative data.