Professional Documents
Culture Documents
Sector
IT-ITeS
Engineer
Sub-Sector
Technical
IT Services
Support
Occupa on
IT Support Services/Helpdesk (Level 1)
Reference ID: SSC/Q0101, Version 2.0
NSQF Level:4
Published by
Copyright©2022
CC
BY SA
This license lets others remix, tweak, and build upon your work even for commercial purposes, as long as
they credit you and license their new crea ons under the iden cal terms. This license is o en compared to
“copyle ” free and open-source so ware licenses. All new works based on yours will carry the same
license, soany deriva ves will also allow commercial use. This is the license used by Wikipedia and is
recommended formaterials that would benefit from incorpora ng content from Wikipedia and similarly
licensed projects.
Disclamer
The informa on contained herein has been obtained from sources reliable to IT – ITES Sector Skill Council
NASSCOM. NASSCOM disclaims all warran es to the accuracy, completeness or adequacy of such
informa on.NASSCOM shall have no liability for errors, omissions, or inadequacies, in the informa on
contained herein, orfor interpreta ons thereof. Every effort has been made to trace the owners of the
copyright material included inthe book. The publishers would be grateful for any omissions brought to their
no ce for acknowledgements infuture edi ons of the book. No en ty in NASSCOM shall be responsible for
any loss whatsoever, sustained byany person who relies on this material. The material in this publica on is
copyrighted. No parts of thispublica on may be reproduced, stored or distributed in any form or by any
means either on paper or electronicmedia, unless authorized by the NASSCOM.
ii
iii
Facilitator Guide
iv
Engineer Technical Support (Level 1)
Acknowledgement
This par cipant's handbook meant for Engineer-Technical Support is a sincere a empt to ensure the
availability of all the relevant informa on to the exis ng and prospec ve job holders in this job role. We
have compiled the content with inputs from the relevant Subject Ma er Experts (SMEs) and industry
members to ensure it is the latest and authen c. We express our sincere gra tude to all the SMEs and
industry members who have made invaluable contribu ons to the comple on of this par cipant's
handbook. We would also like to thank all the experts and organiza ons who have helped us by reviewing
the content and providing their feedback to improve its quality.
This handbook will help deliver skill-based training in the field of Engineer-Technical Support . We hope that
it will benefit all the stakeholders, such as par cipants, trainers, and evaluators. We have made all efforts to
ensure the publica on meets the current quality standards for the successful delivery of QP/NOS-based
training programs. We welcome and appreciate any sugges ons for future improvements to this handbook.
v
Facilitator Guide
· Knowledge and Understanding: The relevant opera onal knowledge and understanding to perform the
required tasks.
· Performance Criteria: The essen al skills through hands-on training to perform the required opera ons
to the applicable quality standards.
· Professional Skills: The Ability to make appropriate opera onal decisions about the field of work.
The handbook details the relevant ac vi es to be carried out by a Engineer-Technical Support. A er
studying this handbook, job holders will be adequately skilled in carrying out their du es according to the
applicable quality standards. The handbook is aligned with the following Na onal Occupa onal Standards
(NOS) detailed in the latest and approved version of Engineer-Technical Support QP:
SSC/Q0101: Engineer Technical Support
The handbook has been divided into an appropriate number of units and sub-units based on the content of
the relevant QP. We hope it will facilitate easy and structured learning for the par cipants, allowing them to
obtain enhanced knowledge and skills.
ask
Example
vi
Engineer Technical Support (Level 1)
Table of Contents
S.No. Modules and units Page No.
vii
Facilitator Guide
viii
1.Introduc on
Unit 1.1 - Overview of the Indian IT-ITeS Industry
Unit 1.2: Career Opportuni es for Technical Support Engineers
and Job Responsibili es
Facilitator Guide
2
Engineer Technical Support (Level 1)
3. Conduct an Internet search to collect data, evidence, and ar cles pertaining to IT-ITeS/support services.
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment and Tools (as recommended for the job role)
Note
This is the first session of the program, which will provide you an Introduc on to the IT-ITES/BPM as an
Industry, its composi on and structure.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
Ÿ Which industry in India has shown remarkable growth and has made it a leader on the world map?
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
3
Facilitator Guide
Elaborate
In this session, we will discuss the following points:
· Informa on Technology, Informa on Technology Enabled Services and Business Process Management
(BPM) and its contribu on to the Indian economy.
· IT-BPM Industry and its structural component.
ask
Ask
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity-1
· In this ac vity, you invite a Senior Associate from a renowned company IT firm to give an overlook on the
IT Industry, its Size and how the IT-ITES/BPM services are growing exponen ally.
· You will conduct a group discussion session.
· If the students have any queries or they have any confusions regarding this chapter, they will raise their
hands
· On availing permission from you, the students can ask ques ons.
· In addi on to this, the Senior IT associate will also share important pointers on areas like:
o The importance of IT-ITES/BPM services in Indian economy.
o India's posi on in providing related services globally.
· A er the doubts are cleared, the senior associate or you may add a few points in rela on to mee ng the
requirements.
· In addi on to those, you can also include few extra points that you may find reliable to the topic and
beneficial for the students.
4
Engineer Technical Support (Level 1)
Say
Did you enjoy this ac vity? Can you see how much informa on you had previously and the informa on you
have now? Let us summarize the points discussed.
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
· Ask them to answer the ques ons given in the par cipant manual.
· Ensure that all the par cipants answer every ques on.
5
Facilitator Guide
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment and Tools (as recommended for the job role).
Note
This is the second session of the program, which will provide you an understanding of the role and
responsibili es of a Technical Support Engineer, its a ributes & skills important to succeed in it as well as
the career path.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
· What are the key skills and a ributes required to succeed in the IT industry?
· What are the career op ons or the associated opportuni es post comple ng Technical Support
Engineer course?
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
6
Engineer Technical Support (Level 1)
Elaborate
In this session, we will discuss the following points:
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity-1
· In this ac vity, you invite a Technical Support Engineer from a renowned company to give an overlook on
the roles and responsibili es, desired a ributes, and the career growth into this field.
· If the students have any queries or they have any confusions regarding this chapter, they will raise their
hands
· On availing permission from you, the students can ask ques ons.
· In addi on to this, the Test Engineer will also share important pointers on areas like:
o Job responsibili es of a Technical Support Engineer and its associated opera ons and day to day
ac vi es.
o A ributes and skill required by a Technical Support Engineer to succeed in this career.
o Opportuni es and career path for a Technical Support Engineer.
7
Facilitator Guide
Say
Did you enjoy this ac vity? Can you see how much informa on you previously had and what you have now?
Let us summarize the points discussed.
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add to what they talk about.
· Ensure that all students par cipate in the class.
· Encourage other par cipants to answer it and encourage peer learning in the class.
· Answer all the doubts in case any to the par cipants.
· Ask them to answer the ques ons given in the par cipant manual.
· Ensure that all the par cipants answer every ques on.
8
Engineer Technical Support (Level 1)
Answer Keys
A. Fill in the Blanks
2. The aggregated revenues from the IT sector in 2017 were es mated to be around
9
Facilitator Guide
10
2. Concept of Service
Requests/ Incidents
Unit 2.1 - Concept of Service Requests/ Incidents
(SSC/N0101)
Facilitator Guide
12
Engineer Technical Support (Level 1)
3. List general policies, procedures, and processes for dealing with basic IT service requests or incidents.
4. Analyse the methods to resolve common issues, including account maintenance/access problems,
networking/connec vity problems.
5. List methods and techniques and guidelines for categorizing and priori zing service requests.
6. Examine technical knowledge to handle hardware, opera ng system, and configura on problems.
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the third session of the program, which will provide you an understanding of Service and Incident
Management.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
13
Facilitator Guide
ask
Ask
Ask the par cipants the following ques ons:
Ÿ What is Service Request?
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
Elaborate
In this session, we will discuss the following points:
· Service Request (SR), its Objec ve and Scope.
Say
Let us now par cipate in an ac vity to understand the concept be er.
14
Engineer Technical Support (Level 1)
Ac vity-1
· You will divide the class into 4 teams.
· Each team will have an even number of students.
· You will instruct the students that each of the teams will be par cipa ng in a symposium of 15 minutes
on the topic that will be assigned to them.
· You will evaluate the best team based on quality and insigh ul informa on.
· Encourage and mo vate each par cipant to ac vely par cipate in the discussion.
· The best team with detailed informa on shall be appreciated with accolades.
Say
Did you find the ac vity frui ul? I hope all of you are aware of the Concept and Handling of Service
Requests.
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
15
Facilitator Guide
Answer Keys
1. Answer the following ques ons:
16
Engineer Technical Support (Level 1)
ii. b and c
17
Facilitator Guide
18
3. Technical specifica ons
related to service requests
Unit 3.1: Technical specifica ons related to service requests
(SSC/N0101)
Engineer Technical Support (Level 1)
2. Demonstrate proper func oning of technologies related to the job role like hardware devices, opera ng
systems, networks, servers, PC management, etc.
20
Facilitator Guide
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the fourth session of the program, which will provide you an understanding various technologies and
hardware devices required to handle service requests.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
Ÿ What do you understand by Service Request Management?
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
21
Engineer Technical Support (Level 1)
Elaborate
In this session, we will discuss the following points:
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity-1
· In this session, you will divide the class into few groups
· The Trainer will take the Trainees to a computer lab where they will be asked to used different Incident
Management tool and display it to other students.
· Each group will be given a specific topic on which they have to work.
· The 1st group will work on Support Incident Tracker (SiT)
· The 2nd group will work on JIRA
· The 3rd group will work on Incident Tracking System
· The teams will get 20 minutes to complete their given work
· The Trainees must work with essen al tools and use the methods as discussed to resolve respec ve
issues
· The trainer will take 10 minutes to evaluate the work of Trainees.
· The team that can complete their given work with finesse will be appreciated with accolades.
· The best presenter with detailed informa on shall be appreciated with accolades.
Say
Did you find the ac vity frui ul? I hope all of you are aware of the tools used for service and incident
management.
22
Facilitator Guide
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
· Ensure that all students par cipate in the class.
23
Engineer Technical Support (Level 1)
Answer Keys
Mul ple Choice Ques ons:
3. What is the first thing that you need to do when you receive a complaint?
a-Ask open-ended purposeful ques ons
4. List out Some popular incident management tools that can be used for tracking incidents.
24
Facilitator Guide
25
4. Remote Dealing with
Basic IT Service
Requests or Incidents
Unit 4.1 Dealing Remotely with Basic IT Service Requests/ Incidents
(SSC/N0101)
Engineer Technical Support (Level 1)
2. Monitor service requests closely to understand their progress and upda on.
27
Facilitator Guide
2. Collect informa on to understand the nature of problems and perform ini al diagnosis.
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the fi h session of the program, which will provide you an understanding of Basic IT Service
Requests/ Incidents.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
· Explain what are Basic IT Service Requests/ Incidents.
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
28
Engineer Technical Support (Level 1)
Elaborate
In this session, we will discuss the following points:
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity
• In this ac vity, the trainer will divide the class into 4 groups.
• All the groups will enact the task that the trainer will give them.
• The first group will troubleshoot the issue 'Unable to log in.'
• The second group will troubleshoot the issue 'Got the Blue Screen of Death.'
• The third group will troubleshoot the issue 'Internet speed is slow.'
• The fourth group will troubleshoot the issue 'Computer or laptop does not iden fy the USB device.'
• The group comple ng the given task in the best way will be declared as the winner and will be
appreciated in the class with accolades.
Say
Did you find the ac vity frui ul? I hope all of you are aware of the Basic IT Service Requests/ Incidents.
29
Facilitator Guide
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
· Ensure that all students par cipate in the class.
· Ask them to answer the ques ons given in the par cipant manual.
· Ensure that all the par cipants answer every ques on.
30
Engineer Technical Support (Level 1)
Answer Keys
A. Fill in the blanks
2. Service Requests with approvals, which mandatorily require the __________ phase.
(b) Approval
3. LAN cables are standard cables that are used for connec ng a system (computers or laptops) to a
________________________.
(b) Network
4. The __________________ servers are extremely thin and have few elements like integrated
network controllers, memory, and CPUs.
(c) Blade
31
Facilitator Guide
32
5: Customer specific
service requests
Unit 5.1 - Customer specific service requests
(SSC/N0101)
Facilitator Guide
1. Design solu ons/workarounds for service requests/incidents based on various incident reports.
2. Apply technical handling skills for various types of incoming service requests.
34
Engineer Technical Support (Level 1)
2. Iden fy incidents and their specifica ons, related to internal or external query.
3. Create a database of resolu on of various service requests using the incident management tool for
best prac ce.
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the sixth session of the program, which will provide you an understanding of Customer specific
service requests
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
· Discuss the design solu ons/workarounds for service requests/incidents based on various incident
reports.
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
35
Facilitator Guide
Elaborate
In this session, we will discuss the following points:
· Internal or External Users
· User Categories
· Types of Incidents
· Incident Response Workflow
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity
· This ac vity is in the form of “Prac ce Session”
· The Trainer will drive the session
· The Trainer will call the Trainees one by one in front of the class
· He/ she will play the role of a customer and furnish complicated scenarios
· The Trainees should use right empathy statements to tackle the situa on
· The Trainer will assess the so skill of the trainees and guide them by giving feedback
· The Trainees should work on the feedback shared by the trainer
· The best performers will be appreciated by the class
Say
Did you find the ac vity frui ul? I hope all of you are aware of the scope of customer specific service
requests.
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
· Ensure that all students par cipate in the class.
36
Engineer Technical Support (Level 1)
37
Facilitator Guide
Answer Keys
1. Answer the following ques ons:
1. List out any different types of Incidents.
Logging on.
This can involve issues with locked accounts and issues with a forgo en username or password. For the
benefit of external users, many organiza ons use automated techniques, but they also directly help
internal users. The CAPS LOCK key, which has impeded successful logins for decades, is a common
source of login problems.
Asking for informa on.
Users frequently call the help desk to ask ques ons regarding products or services. Most help desk staff
members are familiar with the company's goods and services and are able to direct customers to other
departments if necessary. For example, if a consumer phones about a product and wishes to place an
order, the technician can pass the call to the sales department.
Beginning the applica on process. An applica on may occasionally be difficult for users to launch
because they can't find it or because of a so ware problem. For example, if there's a problem, like a
corrupt file or an incorrect configura on, it might not start correctly and end in an error.
Troubleshoo ng or Configuring hardware.
Users may run into issues and need assistance from the help desk if they are in charge of configuring or
troubleshoo ng hardware. However, mouse, keyboards, hard drives, displays, sound cards, and speakers
also regularly require maintenance.
Using or performing a task with an applica on.
Users frequently encounter difficul es performing par cular tasks within an applica on. Users may
experience difficul es performing rou ne tasks and may need help, for instance, when an organiza on
introduces a new email applica on. In this case, by offering users training prior to the rollout of the new
applica on, help desk calls can frequently be decreased. Many organiza ons offer online documenta on
and perhaps videos to address the most frequent issues and ques ons.
38
Engineer Technical Support (Level 1)
Numerous issues are brought on by malware, such as system slowdowns, erroneous reboots, lost files,
errors, and more. In order to prevent infec ons, users should have the most recent an virus so ware
installed on their computers, but when malware does infect a system, users frequently need assistance
removing it.
Recovering data.
You have probably not been using computers very long if you have never lost a file as a result of corrup on,
malware infec on, or simply being unable to find it. Almost everyone has misplaced a file at some point.
Users may ask for assistance in recovering a file if it is significant. Technicians may be able to restore the
corrupted file using specialized file recovery tools. Depending on whether the file is backed up, technicians
might be able to restore it from a backup. In the event that the file is not backed up, technicians can use the
issue as an opportunity to emphasize the value of making backups. Some people just don't back up their
data, so they wait un l they lose crucial files before they do.
Rolling back changes.
There are mes when users want to roll back system changes. This could involve removing recent opera ng
system or applica on updates, uninstalling so ware, or rolling back a hardware driver. Most opera ng
systems and applica ons have ways to carry out each of these tasks, but some mes these methods are too
technical for regular users.
One of the simple user groups is based on the rela onship between the user and the organisa on. Typically,
help desk agents assign incident priori es depending on the user who requested assistance and internal
users who work for the same organisa on.
39
Facilitator Guide
For instance, when an execu ve has an IT issue, the help desk frequently gives this a high priority.
External users are customers of the organiza on. Help desk employees frequently assist customers who are
having issues with another product or service that an organiza on is selling.
3. Mul ple Choice Ques on:
a- Incident Detec on -> Logging -> Diagnosis/ Priori ze -> Resolu on, Recovery -> Closure
2. VPN stands for?
b. Virtual Private Network
40
Engineer Technical Support (Level 1)
41
6: Monitoring and
valida on of incidents
Unit 6.1 - Monitoring and valida on of incidents
(SSC/N0202)
Engineer Technical Support (Level 1)
43
Facilitator Guide
4. Explain how to validate automated Process and ensure they are genuine incidents unit, par cipants will
be able to:
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the seventh session of the program, which will provide you an understanding of Monitoring and
valida on of incidents.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
44
Engineer Technical Support (Level 1)
Elaborate
In this session, we will discuss the following points:
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity
• In this ac vity, the trainer asks to pair up amongst themselves.
• 1 person will act as Support Engineer and will create a log and the 2nd student will enact as a customer
for support requirement.
• Trainer ask to choose the issue from the list below or open to choose as per their wish:
Login Issue/Blue Screen on Desktop/Slow Internet Speed/USB is not traceable by Computer/Wi-Fi is not
detectable
• Encourage student for ac ve par cipa on. A er comple on of the task they will submit it to the trainer.
• Trainer will appreciate the best filled logging sample and accolade for the best efforts.
Say
Did you find the ac vity frui ul? I hope all of you are aware of the Monitoring and valida on of incidents.
45
Facilitator Guide
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
46
Engineer Technical Support (Level 1)
Answer Keys
1. Discuss various methods to monitor service requests.
1. The ac ons taken to keep track of all open service requests from their incep on to resolu on are
outlined in the service request monitoring process. In accordance with the associated SLA, Service
Request Monitoring also determines whether ac on or escala on is necessary to meet the target
resolu on. The Service Request Analyst begins reviewing, valida ng, and closing a Service Request once
it has been accepted and completed.
2. Alert Monitoring is a process that records data inputs con nuously and reports them to a monitoring
system that is integrated. An alarm is a configura on that specifies an undesirable condi on and
ini ates alerts on such problems as a suitable response. An alert is a no fica on of a change in the
system's state, typically one that suggests a poten al problem.
2. How to categorize and filter the alerts.
An Alert's control factor is intended to be provided by categorizing and filtering it. Making decisions about
how to handle alerts is done using this informa on. The classifica on, priori za on, and filtering of alerts is
the task that presents the greatest difficulty in alert handling.
Thresholds help in categorizing alerts by defining the frequency and the values for different condi ons of
the alert that will trigger the alarm when violated.
For example:
If an applica on's average response me has been greater than 5 seconds for the past 15 minutes or more,
an alert will be sent regarding the website's response me.
No fying the user when any plugin, component, or summary metric has an average rate that has been
greater than eight units for the previous 10 minutes or more.
There may be situa ons when alerts are triggered for a rate of error is <=10%, at least for once, for the last 1
hour. In the event that the alert thresholds are set too high, such circumstances may lead to risky scenarios
if discovered too late.
On the contrary, Thresholds, which have been set too low, can result in an overload of informa on and Alert
Messages. It would then result in the monitoring system, tools, and staff opera ng above their pre-
specified capacity.
The common categories of Alerts are:
• Informa onal Alerts– The Alert is logged, and no further steps are required.
• Excep onal Alerts– Alert is forwarded to Incident, Problem or Change Management team, thus
genera ng Request For Change (RFC), Incident Record or Problem Record.
• Warning Alerts– Alert is triggered, but the process con nues with the next step.
The Incident Management team can receive only the alerts that sa sfy certain criteria and thresholds by
implemen ng filters while managing alerts. Filtering by matching a par cular severity level or a string is
one example of a typical filter condi on. By no fica on policies, these filter condi ons are laid out.
47
Facilitator Guide
Answer Keys
3. Explain Incident Management Process.
48
Engineer Technical Support (Level 1)
49
7. Deal Directly With IT
Service Requests/ Incidents
Unit 7.1 - Dealing Directly with IT Service Requests/ Incidents
(SSC/N0202)
Engineer Technical Support (Level 1)
51
Facilitator Guide
1. List the guidelines and standard scripts to resolve service requests/incidents within your level of
competence and authority.
2. Discuss technicali es of service requests/incidents outside the level of competence and authority with
experts.
3. Explain the policies and compliance requirements that apply to IT service requests
4. Demonstrate how to access your organiza on's knowledge base to iden fy solu ons/workarounds
5. Show how to record and acknowledge service requests/incidents using your organiza on's tools and
procedures
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the eighth session of the program, which will provide you an understanding of technicali es of
service requests for iden fica on of the nature of incidents.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
· Discuss how to deal directly with IT Service Requests/ Incidents.
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
52
Engineer Technical Support (Level 1)
Elaborate
In this session, we will discuss the following points:
· Access management
· Record and Acknowledge Service Requests/Incidents using your Organiza on's Tools and Procedures
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity-1
• The Trainer asks the Trainees the following ques on: “What are the ways to deal directly with IT Service
Requests/ Incidents?”
• In this ac vity candidate need to raise their hands to volunteer and speak.
• The language spoken during the session should be known by the majority of Trainees in the class.
• While the session goes on, the Trainer should jot down the crucial points on the Whiteboard with the
help of a marker.
• The best answer shall be appreciated by the Trainer in front of the whole class.
Say
Did you find the ac vity frui ul? I hope all of you are aware of the how to deal directly with IT Service
Requests/ Incidents.
53
Facilitator Guide
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
· Ensure that all students par cipate in the class.
54
Engineer Technical Support (Level 1)
Answer Keys
A. State whether True or False
1. True
2. False
3. True
4. True
5. True
6. False
55
Facilitator Guide
56
8. Technical skills for
handling incidents
Unit 8.1 Technical Skills for Installa on/Configura on
(SSC/N0202)
Facilitator Guide
58
Engineer Technical Support (Level 1)
2. List the most recent modifica ons, procedures, and prac ses to the incident management process.
Resources to be Used
Par cipant Handbook, Pen, Wri ng Pad, Whiteboard, Flipchart, Markers, Laptop, Overhead Projector,
Laser Pointer, equipment, and Tools (as recommended for the job role)
Note
This is the ninth session of the program, which will provide you an understanding of the purpose of
analyzing results to iden fy defects and track the same in defect tracking system.
Say
Good day and a very warm welcome to this training program. Before we begin this session, let us have a
round of interac on.
ask
Ask
Ask the par cipants the following ques ons:
· Examine how applying different values and data impacts the manual test report.
Write down the par cipants' answers on whiteboard/flipchart. Take appropriate cues from the answers
and start teaching the lesson.
59
Facilitator Guide
Elaborate
In this session, we will discuss the following points:
Say
Let us now par cipate in an ac vity to understand the concept be er.
Ac vity-1
• In this session, the trainer will play a videos.
• The video will be learning about data extrac on and its uses.
• The YouTube link for the video is h ps://www.youtube.com/watch?v=O6GFM_uGVFY
• The trainees will observe the video with pin drop silence.
• They can note down pointers from the video that they may find relevant.
• Trainees will maintain decorum in the class and not talk, whisper or discuss in the class.
In case of any queries or confusions, trainees will write those down in their notebooks.
Say
Did you find the ac vity frui ul? I hope all of you are aware of the technical skills required for handling
incidents
Do
· Jot down the crucial points on the whiteboard as the students speak.
· Share your inputs and insight, to encourage the students and add onto what they talk about.
60
Engineer Technical Support (Level 1)
61
Facilitator Guide
Answer Keys
Answer the following ques ons
1. Define Document storage and Document retrieval.
A digital document is typically used when saving a document in a document management system
(DMS). Instead of filing cabinets, we employ electronic storage today. It saves me and room. When a
document is stored, it is usually marked with a set of metadata to designate a par cular type or
categoriza on. Then it is placed into the digital file.
The process of connec ng a requester with the necessary material is known as document retrieval (s). A
professional may help with the search and recovery of the record when dealing with specialised
documents and management systems.
Informa on storage and retrieval is the process of systema cally gathering and cataloguing data so that
it can be located and shown on demand. Computers and data processing techniques have enabled the
rapid, selec ve retrieval of vast quan es of data for government, commercial, and academic
applica ons.
There are various types of informa on storage-and-retrieval systems.
· Document retrieval systems hold full documents, which are o en retrieved using the document's
tle or associated keywords.
· In certain systems, document text is kept as data. This enables full text searching and retrieval based
on any term in the document. In other cases, a digital image of the document is saved, typically on a
write-once op cal disc. Database systems store informa on as a sequence of discrete records
divided into discrete fields (e.g., name, address, and telephone number); records can be searched
and retrieved based on the content of the fields (e.g., all people who have a par cular telephone
area code). The informa on is saved on the computer, either in primary storage or secondary
storage, for easy access.
· Reference retrieval systems retain references to documents as opposed to the actual documents. In
response to a search query, these systems provide the document names and, frequently, their actual
loca ons.
2. Enlist some of the technical skills required for Technical Support Engineer.
Technical Skills
Naturally, technical support engineer jobs require a strong set of hard skills. You may need experience
using various so ware and hardware, web-based applica ons, and more, depending on the business
and the par cular job.
IT support engineers should maintain current knowledge of the latest hardware and so ware in addi on
to having a solid technical founda on.
62
Engineer Technical Support (Level 1)
Technology advances rapidly, making it essen al for tech employees to keep up.
· Maintain Data Reports
· Microso SQL server
· Opera ng Systems
· Basic Coding
· Project Management
· Read and Analyze Applica on Logs
· Server
· NoSQL
· Basic Scrip ng and Programming Experience
· PC
· Mac
· Familiarity with Support Ticket
· Call Center Support
· Knowledge-based Systems
· General Knowledge of Industry Principles
· Java and JavaScript
· Linux/Unix
More Technical Support Engineering Skills
· Phone E que e
· Emo onal Intelligence
· Focus
· Cyber Securing
· Remote So ware
· Backup So ware
· Ac ve Learning
· Research
· Oral Comprehension
· Email Management
· Virtual Communica ons Systems
· Mobile Devices
· Diagnos cs
63
Facilitator Guide
64
Engineer Technical Support (Level 1)
65
9. Annexures
Annexure 1: Training Delivery Plan
Annexure 2: Assessment Criteria
Facilitator Guide
Annexure-I
Training Delivery Plan
Training Delivery Plan
Qualifica on Pack
SSC/Q0801, Ver.3.0
Name & Ref. ID
Training Outcomes A er comple ng this programme, par cipants will be able to:
· Iden fy policies and procedures to handle IT service requests.
· Collate technical knowledge about configura on, opera ng system, etc.
· Iden fy features of various hardware devices required to handle service
requests.
· Demonstrate proper func oning of technologies related to the job role like
hardware devices, opera ng systems, networks, servers, PC management,
etc.
· Categorize, priori ze, and monitor service requests received.
· Design solu ons/workarounds for service requests/incidents based on
various incident reports.
· Apply technical handling skills for various types of incoming service requests.
· Monitor systems promptly for automated alerts and analyse the same for
iden fying the nature of incident.
· Demonstrate error mi ga on techniques related to access management,
applica on installa on, network installa on, etc.
· Demonstrate applica on of source coding standards, cke ng tools and
other IT related technologies.
· Explain the purpose and use of data configura on.
· Demonstrate effec ve work planning principles using me and resources
effec vely.
· Describe how to maintain a health, safe and secure environment at
workplace.
· Demonstrate how to communicate and work effec vely with colleagues.
· Explain the importance of effec ve collabora on at workplace.
· Iden fy best prac ces to maintain an inclusive, environmentally sustainable
workplace.
67
Engineer Technical Support (Level 1)
68
Facilitator Guide
69
Engineer Technical Support (Level 1)
· Build a database of
resolu on of various
service requests using
the incident
management tool for
best prac ce.
6. Deal · List the standard Pc5, P8, Discussion Chairs, round T-15
directly guidelines scripts to P9, P10, Ac vity: table in U shape P-30
with IT resolve service P11, P12, Group si ng shape,
service requests/incidents P13 Discussion Whiteboard and
requests/in within the level of KA1, KA3, Video Markers Chart
cidents competence and KA7, KA8, Ac vity- paper and
authority. KA9 YouTube sketch pens LCD
· Design methods to Projector and
extract sufficient Laptop for
informa on from presenta ons
customers to
accurately
iden fy the nature of
service requests.
· Use range of methods
and techniques,
including
types of ques oning,
used when dealing
with customers.
70
Facilitator Guide
7. Technical · Explain the purpose and Pc2, PC9 Video Whiteboard and T-10
skills for use of data Ac vity- Markers Chart P-25
handling configura on. YouTube paper and
incidents · Discuss how to store Interac ve sketch pens LCD
and retrieve informa on Discussion Projector and
related to service Laptop for
requests. presenta ons
· List the latest changes,
procedures, and
prac ces in incident
management process.
· Evaluate the mechanism
of source coding
standards, cke ng
tools and u li es/tools
for handling service
requests.
· Deploy informa on
technology effec vely to
input and/or extract
data.
· Iden fy methods and
importance of data
configura on for
dissemina ng relevant
informa on to
customers.
71
Engineer Technical Support (Level 1)
72
Facilitator Guide
On-the-Job Training 60
73
Engineer Technical Support (Level 1)
Annexure-II
Assessment Criteria
CRITERIA FOR ASSESSMENT OF TRAINEES
Assessment Criteriafor Engineer Technical Support (Level 1)
Job Role Engineer Technical Support (Level 1)
1. Criteria for assessment for each Qualifica on File will be created by the Sector Skill Council. Each
Performance Criteria (PC) will be assigned marks propor onal to its importance in NOS. SSC will also lay
down propor on of marks for Theory and Skills Prac cal for each PC.
2. The assessment for the theory part will be based on knowledge bank of ques ons created by the SSC.
3. Assessment will be conducted for all compulsory NOS, and where applicable, on the selected elec ve /
op on NOS/set of NOS
4. Individual assessment agencies will create unique ques on papers for theory part for each candidate at
each examina on/training center (as per assessment criteria below)
5. Individual assessment agencies will create unique evalua ons for skill prac cal for every student at each
examina on/training center based on this criterion
6. To pass a QF, a trainee should score an average of 70% across generic NOS' and a minimum of 70% for
each technical NOS
7. In case of unsuccessful comple on, the trainee may seek reassessment on the Qualifica on File.
MARKS
ALLOCATIONS
Assessable Assessment criteria for the outcome Total Out of Theory Skills
Outcomes Marks Prac cal
74
Facilitator Guide
Total 100 30 70
75
Engineer Technical Support (Level 1)
76
Facilitator Guide
PC10. Entrepreneurship
5 2 3
Total 50 20 30
77
Engineer Technical Support (Level 1)
78
Facilitator Guide
89