Document # : TCS-<IOU>-iQMS-001
Tailoring Guidelines for iON
______________________________________________________
Version 1.0
Notice: This is a copy of a document maintained on electronic media (Knowmax ->
iQMS Wiki -> iON) It may not be the latest version. Kindly ascertain the latest
version from the Document Master List available in iQMS Wiki.
iON
Aug 2014
 2014
This is a controlled document. Unauthorised access, copying and
replication are prohibited.
This document must not be copied in whole or in parts by any
means, without the written authorisation of the IOU Head,
TCS <IOU>.
DOCUMENT RELEASE NOTICE
This Tailoring Guidelines, Version 1.0, is released for use in Tata Consultancy Services
Ltd, iON with effect from July 2014
This manual is subject to TCS Document Control Procedure. This document will be
released on the Process Document Repository (iQMS-Wiki).
Comments, suggestions or queries should be addressed to the DEH, using the Feedback
Form at the end of this manual.
Approved by: ____________________
Date: _____________________
(IOU Delivery Excellence Head )
Approved by: ____________________
Date: _____________________
(Head – Enterprise Quality Management) **
Authorised by: __________________
Date: _____________________
(<Name>, IOU Head)
**If the TGL is addressing tailoring in areas other than Delivery, then approval must also be
sought from the relevant Corporate Owner. Examples could be Corporate KM for KM process
tailoring, Global HR for HR process tailoring in the IOU/GDC, etc.
Tailoring Guidelines for <IOU>
Version m.n
DOCUMENT REVISION LIST
Document Name:
Document No.:
Tailoring Guidelines
TCS iON-iQMS-001
Version 1.0
Rev No.
Revision
1.0
First Draft
TCS Internal Use only
Page
No.
Action
Taken
(Add/Modify/Delete)
Uncontrolled when printed/downloaded
Rationale for
revision
v
Tailoring Guidelines for <IOU>
Version m.n
About this document
Purpose
This document gives the guidelines to be used by projects and other groups at TCS, iON
for tailoring the TCS iQMS processes for domain specific, customer specific and other
specific use.
This Tailoring Guideline is applicable for:




Solution Engineering teams in SMB
Quality Assurance Team in SMB
Release Management Team in SMB
Academy Team in SMB
Intended Audience

All entities as above

Delivery Excellence team,

All associates of TCS,
References
The latest version of the documents/guidelines referred to in this document may be
ascertained from the TCS iQMS Document Master List and the SMB iQMS DML
available in iQMS-Wiki.
TCS Internal Use only
Uncontrolled when printed/downloaded
vii
Tailoring Guidelines for <IOU>
Version m.n
List of Abbreviations
BAU
CDD
CR
CSS
DML
DAM
DEH
ID
GD
IOU
IQMS
LO
PVC
SOP
SB
SMB
SME
CM
CDM
FC
UI
WF
TCS Internal Use only
Business as Usual
Course Description Document
Change Request
Cascading Style Sheets
Document Master List
Delivery Assurance Manager
Delivery Excellence Head
Instructional Designers
Graphic Designers
Independent Operating Unit
Integrated Quality Management System
Learning Officer
Professional Virtual Community
Standard Operating Procedures
Story Board
Small and Medium Business
Subject Matter Expert
Content Manager
Competency Development Manager
Functional Consultant
User Interface
Work-Flow
Uncontrolled when printed/downloaded
ix
Tailoring Guidelines for <IOU>
Version m.n
Table of Contents
SECTION 1 - INTRODUCTION ................................................................................................................ 1
SECTION 2 – TAILORING GUIDELINES .............................................................................................. 3
SECTION 3 – IOU LEVEL PRACTICES ................................................................................................12
SECTION 4 – LIST OF IOU SPECIFIC CHECKLISTS, TEMPLATES AND TOOLS ...................21
This document contains a total of 36 pages.
TCS Internal Use only
Uncontrolled when printed/downloaded
xi
Tailoring Guidelines for <IOU>
Version m.n
Section 1 - Introduction
This document provides a set of guidelines to tailor the iQMS for projects and other
groups as defined in the following set of documents

TCS iQMS documents (as per TCS’ iQMS DML)
This document may be used to tailor the iQMS to the specific process requirements of
the project, in order to define the plan and operational processes for the project. The
context of this document within the process definition framework for projects is shown in
the illustration below.
Corporate iQMS
Tailoring Guidelines
(This document)
Relationship/Customer Process
Definition & requirements (if any)
Life-cycle Model
Selection
Project Plan
Process
Assets
Figure 1: Process Tailoring and Definition
Guidelines for tailoring the iQMS for projects are to be referred from
(1) the Corporate iQMS
a. Project Planning Guidelines (TCS-iQMS-102) and Process Handbooks
i. Defining the Operational Process - refer guidelines and minimum process
requirements
ii. Refer the relevant Process Handbook for the project type
b. Project Procedures Manual (TCS-iQMS-052)
i. Appendix I - Project Classification Guidelines
ii. Appendix K - Guidelines for Tailoring Project Processes for different
Engagement Models
TCS Internal Use only
Uncontrolled when printed/downloaded
1
Tailoring Guidelines for <IOU>
Version m.n
(2) IOU Level Tailoring Guidelines – Section 2 onwards in this document.
Note: When to tailor iQMS at IOU level
- Domain/Regulatory Requirements. Eg.,
• Projects required to comply with FDA regulatory requirements require 100% code
coverage in unit and system test
• Projects in xyz ISU to target testing automation of 60% minimum to cater to time to
market objectives of customers in the xxx ISU domain
- Customer Related Requirements. E.g.,
• Relationship specific processes, metrics which are aligned to iQMS and are followed
by all projects in the relationship which may also take the form of SOPs/Process
Frameworks/Operations Manual etc for the relationship.
- New Situations. E.g.,
• OPD for requisition projects
TCS Internal Use only
Uncontrolled when printed/downloaded
2
Tailoring Guidelines
Version m.n
Section 2 – Tailoring Guidelines
This section describes the set of process elements and how they can be tailored for various project types.
No.
Process
element
1. 1Approach to
Courseware
Development
Relation
ship /
Domain
All
Project
Type
Codification
Tailoring guideline
Roles involved in the courseware
are segregated and are multiple.
Study of target audience profile is
imperative for focused courseware
development
iQMS
Referenc
e
TCS-iQMS122
Coursewar
e
Guidelines
Rationale for tailoring
iON SMB comprises of the different
roles – Activation Specialist,
Functional Member, ID, GD,
Technical writer, Reviewer, SME,
Learning Officer, and Content
Administrator.
Courses need to address the
requirements of the various roles.
Review by SME/ Role lead is of
greater significance.
TCS Internal Use only
Uncontrolled when printed/downloaded
3
Tailoring Guidelines
2. 2Learning
Activation
Version m.n
All Customer
Codification
iON SMB has a focused set of
courses specific to iON products,
domains and hosted over multiple
delivery channels.
These courses need to be
accessed by both TCS iON and its
Channel partners/ clients.
The scope of this document is in
consideration of only the set of
courses which are specific to iON
in terms of Product and Domain.-
TCS-iQMS122
Section
1.4.2
Coursewar
e
Guidelines
Considering the frequency of
updates in a perpetual Beta
environment and the release of
updated/ new versions, iON SMB
largely make use of Rapid Content
Development tools for its courseware
and other content related to the
product or solution.
Content Reviews and Quality Checks
are carried out in a stringent manner
at a module level for each content
requirement.
This is addressed with the
Instructional Design team, Subject
Matter Experts and Domain/ Solution
specialists.
This helps in turning out high quality
courseware in line with the release of
the product.
TCS Internal Use only
Uncontrolled when printed/downloaded
4
Tailoring Guidelines
3. 5Deciding on
Buy-orDevelop
Version m.n
Customer
Codification
The Courseware that for
reasons of timelines, ongoing
projects, complexity or market
focus, cannot be developed
internally can be procured offthe-shelf or be made in a
bespoke manner specific to the
requirement on a case-to-case
basis.
TCS-iQMS122
Section 4.1
Coursewar
e
Guidelines
Buying of courseware, although
within scope, is limited for reasons of
product knowledge, security and to
an extent, cost factors.
Given the above, product-related
courseware is developed within the
organization by the iON Codification
team in collaboration with
stakeholders related to the solution.
There could be a common
vendor for all requirements or
different vendors for different
runs of the course. Cost, timelines, quality standards,
compatibility and portability are
the determinants here.
4. 6Course material
Development
iON
internal
groups
Codification
Based on the complexity of the
solution and available time to rollout, the ID or content writer would
get trained on the various aspects
of the product, analyse the
changes/ enhancements from the
previous version(s) and author the
relevant contents for the
courseware.
TCS-iQMS122
Section 2.6
Coursewar
e
Guidelines
IDs would be completely acquainted
with the product and would need to
directly author the courseware based
on the system understanding.
However for reasons of complexity,
access and available time-frames,
the SME/ functional consultant would
be briefly oriented on courseware
development processes and would
need to record the functions and
transactions related to the specific
modules of the solution.
The Codification team would, in such
cases, address the Quality
requirements, packaging and
publishing of such courseware.
TCS Internal Use only
Uncontrolled when printed/downloaded
5
Tailoring Guidelines
5. 7Learning and
Development
Function
TCS Internal Use only
Version m.n
All
Academy
CLP Team
iON does not focus on learning
language and intercultural
competencies.
TCS permits the learning of the
foreign languages due to its
diversification in the various
projects
Uncontrolled when printed/downloaded
TCS-iQMS063
Continuous
Learning
Procedures
No foreign language training is
imparted as the product line of iON
SMB is presently limited to the India
Geography.
Section 1
6
Tailoring Guidelines
Version m.n
6.
iON PVC is the primary platform
for delivery of courses or content
specific to the iON Solutions.
FTC/ BDA, partner sites, iCALMS
and video solutions are additional
learning channels that are used.
Programs are mostly specific to
iON Solutions and can also include
mandatory and domain courses.
Guidelines for
Capturing
Project Internal
Training Data In
iCALMS
Exposure of the content to channel
partners and customers is the one
of the deciding factors for channel
applicability.
All
Academy
CLP Team
Learning Records are maintained
on the respective systems where
the learning is hosted on, collated
and consolidated on a periodic
basis and reported on an overall
basis.
Reports prepared and maintained
by iON would include records
pertaining to the partners/ channel
participants as well.
TCS Internal Use only
Uncontrolled when printed/downloaded
TCS-iQMS063
Continuous
Learning
Procedures
Appendix C
Tracking of learning for iON happens
mainly on the PVC system’s Reports.
Further the reports from PVC, FTC/
BDA, partner sites as applicable,
iCALMS / TCS LnD reports for the
period in consideration are
consolidated and a comprehensive
dashboard is prepared and
presented to management on the
periodic reviews and meetings.
Data pertaining to key generic/
competency-related learning
programs conducted for TCS-iON
associates would be available on
iCALMS.
Data pertaining to key programs
specific to iON and for TCS-iON
associates would be provided for
updating on iCALMS.
iQMS references to Project Internal
Training. -> CLP Procedures Manual
-> CLP_section 22 and Annexures A
and C for the need to not re-duplicate
data pertaining
iON ensures data-duplication and
redundancy is avoided at all possible
levels. Hence learning records and
reports are all maintained online and
on the respective systems. These
records can be fetched and reports
generated for a required
period or set of associates at any
point of time.
7
Tailoring Guidelines
7.
Planning
Version m.n
Solution
Engineerin
g
Product
Development
 For product planning activities,
iON BizTools solution will be
used
 First release of UPP shall be
authorised by Solution
Engineering Head. The later
versions shall be authorised by
the Product Engineering Head.
8.
MonitoringProgress
reporting
All
Product
Development
 The progress of the product
teams will be tracked on a
regular basis by the product
managers in iON Biztools
instead of IPMS.
TCS-iQMS102
PP3020
PP1070
 Schedule , effort and defect
data related Metrics as
applicable will be reported
through UMP module in IPMS
9.
Review
All
Product
Development
 Review records shall be
maintained in SVN and defects
shall be maintained in ALM
 Defect metrics will be reported
as applicable for product
development through UMP in
IPMS
 DP CA report will be prepared
manually using extracts from
ALM
TCS Internal Use only
Uncontrolled when printed/downloaded
PP3020
PP3030
 Business directive to effectively
use in-house iON solutions.
Usage of iON solutions by the
product teams would provide the
User Experience helping the
Group to evolve the tools to
enhance user experience
 Product Engineering Head
overlooks the product
management activities under the
suite.There may be only minor
changes in the UPP post first
release
 Business directive to effectively
use in-house iON solutions.
Usage of iON solutions by the
product teams would provide the
User Experience helping the
Group to evolve the tools to
enhance user experience.Defect
data would be uploaded to the
UMP

From the inception of iON SVN
has been used for review records
and hence the same can
continue as teams are used to it.
iON has every 4 monthly release
cycle and we do Causal analysis
of defects during that time.The
Defect related data same data
can then be ported into UMP
8
Tailoring Guidelines
10. Review-EQA
(Requirements
and design)
Version m.n
All
Product
Development
 Review & Sign-off for
requirements and design for
release would be by the cross
solution team within the
product.
PP3020
 In-depth deliberation on
requirements done by product
team involving market trend,
customer need, product
knowledge. So, an external view
point on the same is already taken
by above means.
 Multiple solution teams exist within
the product, and cross product
EQAs will add value
 Teams outside the suite would not
have the required functional
knowledge to conduct a review.
11. Review-EQA
(Code)
Al
Product
Development
 EQA will be done by crosssolution teams within the
product.
12. Tools
All
Product
Development
Enterprise Process tools such as
IPMS and EQP for project
management, engineering and
governance would not be used.
However all applicable iQMS
processes will be followed using
offline forms as appropriate
13. CSS
All
All
CSS will be collected using offline
excel template and will be
uploaded as Client format and
analysis will be done outside the
system till this is supported in
IPMS.
TCS Internal Use only
Uncontrolled when printed/downloaded
PP3040

In-depth knowledge of the
product, its intent and the
technology exists within the
suite, which will make the
review more beneficial.

Multiple solution teams exist
within the product, and cross
product EQAs will add value
- Internal tools have been used since
inception of iON and hence the same
would continue but we would port the
data as necessary in IPMS for Q25
and UMP dashboards and metrics
respectively
PP1160
The iON templates captures product
feedback with parameters specific to
product lifecycle.
9
Tailoring Guidelines
14. FI
Version m.n
All
All
FI Checklist will be in iON
customised format (available in
iON wiki)
PP3060
FI Checklist for Product Development
has been modified in based on the
product specific requirements.
The FI checklist for Activation
projects would focus on adherence to
process documented for activation.
Since activation focuses only on
product configuration and is done
through an installer. The FI would be
done by the TM doing the
configuration
15. DP
All
All
iON DPCA Template will be used
for DP & Causal Analysis at the
product level
16. Measurement
and Metrics
All
All
To capture all defect related data
,PR related data and Customer
feedback data from different
stakeholdres like solution
engineering/customer support and
Activation teams
17. Contract Review
All
All
The
contract
review
and
authorization process would not be
followed for individual customer
contract.
Only
the
contract
template would be reviewed and
authorized before it is released for
use.
TCS Internal Use only
Uncontrolled when printed/downloaded
PP3090
PP3010
-
Raw data is available in ALM and
not available in IPMS across the
unit
-
Data captured in sync with the
corporate requirements
-
Data analysed at every release
once in 4 months.
-
Schedule Slippage/Effort
Slippage and End timeliness
would be difficult to capture for
each product as the CR
incorporation happens in tandem
and it would be difficult to give an
exact measure of the same.`
SMB does not have different Terms
and Conditions for each customer
since it is a license based offering.
The Standard Contract template
undergoes the review process
whenever there is a change.
10
Tailoring Guidelines
Version m.n
< List all relationships that have process frameworks/operation manuals/SOPs etc defined which are applicable to all projects in that relationship.
Provide reference to the related documentation, so that projects and DAG will refer to it for tailoring and deployment, and auditors will use it for
verification.
For relationship level tailoring, if there is any risk due to the tailoring aspect, it should be managed and documented as part of the Risk
Management Plan in the relationship, and reference to the plan mentioned in the Rationale for tailoring.>
TCS Internal Use only
Uncontrolled when printed/downloaded
11
Tailoring Guidelines
Version m.n
Section 3 – IOU level Practices
This section describes the practices followed in the IOU and any directives given by the IOU Head with respect to
deployment of iQMS.
No.
1.
Process element
Assessments
Project Type
All
Practice/Directive
Contents are modularized and
structured according to the major
processes (or functions) of the iON
product/ solution.
The assessment is usually taken up at
each module and just not at the final
level.
Rationale
This helps, within a short cycle-time,
ensure that the learner has understood the
various aspects and functionalities of the
product or version of the product being
addressed in the specific learning module
This serves as a qualifying milestone
before the learner moves into the
subsequent module.
TCS Internal Use only
Uncontrolled when printed/downloaded
12
Tailoring Guidelines
2.
Delivery Channels
Version m.n
All
The delivery channels used with iON
SMB are limited to a vital few. This is
due to the course lifespan, coverage
required in a limited time-frame and the
profile of the stakeholders (internal and
external).
Channels such as PVC, Hi-Ox, Moodlebased systems are preferred in iON for
ease of access and absence of
employee-based authentication
mandates.
The delivery channels used with iON
SMB are sparse as all are not used as
of now
TCS Internal Use only
Uncontrolled when printed/downloaded
For delivery of courseware, multi-domain
and multi-stakeholder channels like PVC
and Hi-Ox are used for hosting courseware
and video requirements.
(Note: Channels such as iCALMS and
Brain Bench may not always be relevant to
the scope of iON specifications and hence
not being considered for current learning
and assessment / certification
requirements).
Currently the various channels to use are
not tested ones. Used ones include the
PVC LMS
13
Tailoring Guidelines
3.
Review process
Version m.n
All
SMB – iON has multiple review stages
for each aspect of the content
development lifecycle.
Given the volume of the contents
associated with the product (learning
plus Product Feature and Help
references) and the timespan of the
product version, it is not possible or
necessary to have a formal team doing
the reviews at each stage.
SMEs, Senior IDs and Quality
personnel within the team officiate and
address the review process and ensure
delivery of quality and optimal learning
content. They have been formally
trained by Techcomm on the
requirements and hence compliance to
all aspects of the review process is
ensured.
Due to the very short content development
lifecycle and the volume of the product
contents in terms of courses and product
configuration references the Reviews are/
can be/ are taken up by Senior
Instructional designer, Quality personnel or
SME. The courseware is base lined to the
current version of the product, signed off
by the CoE on the various content factors
(correctness, relevance, inclusion of
features and quality) and rolled out on the
iON learning management systems and
delivery channels.
Techcomm reviews are also addressed
in this manner.
This team would be formally
approached for client-focused
courseware or in cases of absolute
necessity.
TCS Internal Use only
Uncontrolled when printed/downloaded
14
Tailoring Guidelines
4.
Re-imbursement
Version m.n
All
iON provides Product & Domain
specific Trainings to the Students/
Learners
The training and certifications on iON
specific products and domains are
offered by TCS iON to TCS associates
in iON and iON clients/ partners.
Since the certifications are specific to
iON, there is no need for the usual
certification process of an initial
payment from the learner and
reimbursement on completion
Learning or Certification on the iON
product would be a win-win requirement
for both user/ learner and iON.
For the TCS-iON associates, the
various iON product and domain
certifications earned would need to be
recorded on iCALMS using the
‘Certification without Reimbursement’
option
As the Team addresses mostly
certifications based on iON product and
domain, there is no monetary transactions
at the student end, Thus no reimbursement is required for these
certifications.
iQMS references on the Certifications, as
applicable, CLP section #25.
iQMS references to Project Internal
Training’s as mentioned in the section ->
CLP Procedures Manual -> CLP_section
#22 and Annexures A and C.
However for the other external Certification
programs that TCS supports as per the
policy, workflows, approvals, payment
modes and reimbursement requirements
are applicable and addressed as per the
terms and conditions of the TCS
Certification Policy.
The onus of recording the certifications
earned on iCALMS lies with the
associate.
Note: For the TCS-iON associate the
other external Certifications and
reimbursements thereof would be
applicable as per the TCS Certification
Policy. Corresponding workflow defined
in iCALMS would need to be followed.
TCS Internal Use only
Uncontrolled when printed/downloaded
15
Tailoring Guidelines
5.
Approach & Strategy
Version m.n
All
Codification process follows shorter life
cycle of the Product as compared to a
bespoke content development cycle.
This is to ensure that the right content
is available at the right time (coinciding
with the release of the new product/
version) and with focus on the role(s)
for which the content is intended.
6.
Review of the
Instructional Design
iON Internal
groups
iON - review process comprises of the
review with instructional designer and
then followed by the SME/ CoE review.
The cycles are, short although detailed.
The Techcomm review aspect is often
addressed by qualified senior IDs and
the base-lined content is rolled out.
iON has a product release of every 3
months, the time possible to develop and
roll-out the right version courseware is
much lesser than the custom flash-based
WBTs.
Bespoke WBTs are used in cases such as
generic or leadership skills, marketing
concepts, or aspects of products where the
time between versions is larger.
iON review process is a rigorous although
short process with many stakeholders
involved given the duration for the course/
product lifecycle and the complexity of
having role-based content.
This is in consideration of the short
time-lines for the product line and the
volume of contents – Courseware, Help
Documentation, Product Features and
Configuration References.
The senior IDs carry out the
requirement based on guided training
sessions provided by Techcomm in
consideration of the above limitations.
TCS Internal Use only
Uncontrolled when printed/downloaded
16
Tailoring Guidelines
7.
8.
Version m.n
Formulation of the
strategy for
Continuous Learning
Program
All
Close the Learning
Program
All
CLP 01
CLP 10
TCS Internal Use only
Like TCS we have Academy strategy of
Review and approvals where
CLP Lead: Continuous learning
program strategy.
Academy Lead/BU Lead : Review and
Approval of strategy for CLP
CLP Lead: Communicate Strategy for
CLP.
The responsibility owners are different in
iON with a limited involvement of HR.
PVC LMS is not integrated with
iCALMS and hence not updated. Hence
iCALMS data is not updated.
Programs essential to iON or its
products are defined on iCALMS and
are tracked.
The Learning Officer is given the
names of successful candidates
pertaining to these programs and these
are updated on iCALMS from the back
end.
Major part of hosting and tracking of
learning is done on PVC.
In future we plan for integration with
TCS NxtGen LMS
Learning records and details of the
programs are maintained in a lean manner
on the respective Host Learning system.
Uncontrolled when printed/downloaded
There is no duplication of data between
systems on a generic and regular basis.
Data pertaining to critical programs and
certifications taken on other channels
would, as per requirement, be replicated
on the TCS central LMS – iCALMS.
17
Tailoring Guidelines
9.
Version m.n
All
CLP 19
Creating Learning
solutions
10.
Bespoke WBTs are used in cases such
as generic or leadership skills,
marketing concepts, or aspects of
products where the time between
versions is larger.
All
CLP 23 - 25
Managing Certifications
And Professional
Membership
With a product release of every 3
months, the time possible to develop
and roll-out the right version
courseware is much lesser than the
custom flash-based WBTs.
The differences in iON’s Certification
program are in terms of product/
domain, structure, variations in versions
( as applicable ), channels available for
pursuing the certification, the
movement of associates over roles and
teams.
Further these certifications are offered
to TCS-iON associates, clients and
partners.
.
Certification data is maintained
internally with iON for the complete
participant-base (both internal and
external learners), periodically sync'd
with various delivery channels and
reported.
If the learning solution does not meet
the needs of iON in terms of the
product/ features/ content or domain,
then this is taken up with the
respective Product owner teams and
corrective requirements addressed in
the form of a version update / new
release.
Certification at iON SMB provides different
levels of certification process which is
defined as bronze, silver, gold, and
platinum. Certification is based on role,
experience and credit points to maintain
validity
Certification levels are governed by pre
requisite, eligibility criteria and
maintenance criteria at each level.
There are points for each requirement item
and are granted to the associate on
completion of the requirement. This
qualifies the associate for TechNet level of
certification.
The Value-addition of such a dualchannel reporting process, however,
needs to be justified before making it
necessary/ mandatory to sync the data
between iON systems and iCALMS
.
TCS Internal Use only
Uncontrolled when printed/downloaded
18
Tailoring Guidelines
11. Maintain List Of
Certifications Eligible
for Reimbursement
Version m.n
All
CLP 24
iON and FTC certifications are
presently not charged and hence the
reimbursements workflow is not used.
May be it can be applicable in future for
iON customer or channel partners.
iON uses the PVC LMS instead of the
TCS LMS namely iCALMS. This is
because the iON courses are
applicable to and referenced by TCS
iON associates, Partners and clients of
iON.
12.
Tracking is done for all learners of
these courses.
All
Guidelines for capturing
iLearn Data in iCALMS
Appendix B
For certain programs essential to iON,
the records of TCS iON associates are
filtered out, updated on iCALMS and
monitored internally so as to meet the
targets and timelines of the Business
Units.
iON has several courses specific to the
solutions and Domain of operation. These
courses, taken as a curriculum, are on the
lines of the iLearn program and are
mandated / tracked for completion and
compliance requirements and not in
ICALMS.
Going forward, learning access and
details would be synced with the TCS
NxtGen LMS and transparent to the
learner. Automatic central tracking of
the course progress is also enabled
13.
All
Metrics
TCS Internal Use only
Where metrics are not defined in IPMS,
it would be captured in excel, ALM and
uploaded in Knowmax.
The UPP will specify the methodology
followed for the specific product
development. The Corporate MDP for
Development, maintenance and agile
will be followed accordingly
Uncontrolled when printed/downloaded
Tools like ALM are used for Defect
capturing and hence the same would be
uploaded in IPMS once in 4 months for
required analysis.
19
Tailoring Guidelines
Version m.n
14. PMR
Product
Development
Quarterly reviews of Product Heads,
Solution Engineering head, VBU Head
is done by the ISU Head which would
be considered as PMR. Process rigor
would be introduced as a part of PMR
reviews
-The review covers product progress and
process review and also strategic
milestones achieved,risks and issues and
concerns of each teams.
15. Knowledge
Management
Process
Knowledge repository for iON will be
available in Ultimatix /Knowmax as well
as the iON portal PVC (Professional
Virtual Community)
-
To ensure sharing of information
related to the ISU which includes
product information,roadmaps,best
practices and lessons learnt.
16. Audit
Process
Product development and support audit
checklist will be referred for project
audits in iON
-
To ensure process defined for
products are covered adequately
17. Audits
Process
For all BAU projects the Regional
Manager/Regional Delivery Manager
who handles the accounts would be
audited from the entity audit
perspective
-
The number of SMB projects are huge
and hence auditing each one of them
would be challenging and auditing the
RM/RDM would help cover most of the
project related areas.
18. Tools
Solution
Engineering
However all applicable iQMS processes
will be followed using offline forms as
appropriate and internal tools would be
used to collect data related to
timeliness and defects
- Internal tools have been used since
inception of iON and there is a directive to
maximize usage of internal tools.Also most
associates are well versed with the tools
being used and for them it is Business as
usual.All the necessary data would be
ported into UMP and IPMS for required
metrics derivations
TCS Internal Use only
Uncontrolled when printed/downloaded
20
Tailoring Guidelines
Version 1.0
Section 4 – List of IOU specific Process Assets
iON Document Master List
(PF1000) DOCUMENT MASTER LIST
Customer
Project
Internal
SMB – Apps Business
Ver.
No.
Media
Release date
Document Name
No. of Copies
Manual
ON Activation Process Handbook (TCS-iQMS-351)
Conduct Solution Walk-through
Track Solution Usage
Start-up Presentation Template
Welcome Mail Template
Solution Fitment Analysis Template
Monthly Adoption Dashboard Template
Issue Tracker Template
Go Mail Template
Activation Plan Template
Customer Feedback Form
Sales to Delivery Handover Checklist
Tailoring Guidelines
TCS Internal Use only
1.0
Handbook
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
Forms /Templates /Checklist
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
1.0
Soft Copy
Guidelines
1.0
Soft Copy
Uncontrolled when printed/downloaded
21
Tailoring Guidelines
Version 1.0
(PF1000) DOCUMENT MASTER LIST
Customer
Project
Internal
SMB – Platforms - iON Assessments
Ver.
Release
No. of
Document Name
No.
Media
date
Copies
Manual
Assessment Procedures Manual
1.3
Soft Copy
Handbook
Assessment Process Handbook
1.3
Soft Copy
Guide Lines
iAG2050 Center Heads Training Instructions
1.0
Soft Copy
iAG2055 IT Manager Training Instructions
1.0
Soft Copy
iAG2085 Invigilator Training Instructions
1.0
Soft Copy
iAG3011 File Upload
1.0
Soft Copy
Media Crisis Management Final Version 1
1.0
Soft Copy
Third Party Payroll Hiring Guidelines-V.1
1.0
Soft Copy
Check List
1.0
Soft Copy
Exam Day Audit Cheklist_v1.3
1.0
Soft Copy
iAC1020 LISP Audit Checklist
1.0
Soft Copy
iAC2020_City Head Check List
1.0
Soft Copy
iAC2021 Last Mile Checklist
1.0
Soft Copy
iAC2075 MockTest UserCase Checklist
1.3
Soft Copy
iON Assessment _Daywise Activity Checklist
1.0
Soft Copy
Pre Assessment Audit Checklist
Templates
AT1011 Facilities Agreement for Bulk Pricing
1.0
Soft Copy
iAT1012 Facilities Agreement for Contract Pricing
1.0
Soft Copy
iAT 2025 Assessment Project Tracker
1.0
Soft Copy
iAT 2026 Work Order Template
1.0
Soft Copy
iAT2045 Cash Requirement Request
1.0
Soft Copy
Forms
iAF1015 LISP Code Creation (LCC) Form
1.0
Soft Copy
iAF2010 Exam Confirmation Form (ECF)
1.0
Soft Copy
iAF3010 Feedback Form
1.0
Soft Copy
iAF3011 Acknowledgment Form
1.0
Soft Copy
Governance Model
iON Assessment_Governance Model
1.0
Soft Copy
iON Platforms_Governance Model
1.0
Soft Copy
TCS Internal Use only
Uncontrolled when printed/downloaded
22
Tailoring Guidelines
iON Application
BusinessName
Associate
Nomination Template
Version 1.0
Purpose
Requested nominations are
captured in the particular
sheet.
PVC Course content
This document explains the
details of the course
mentioned in iON SMB.
Release Recording
As per the smaller cycle of
iON SMB every release is
captured in form of a
recording.
E Learning content
To provide easier access to
the customers the content is
uploaded in form of ELearning.
Assessment
After conducting the
Trainings the associate
needs to appear for the
Assessment which is
designed for the attended
course.
Defect Logging , tracking
Causal analysis
TCS Mastercraft
Application Lifecycle
Manager (ALM)
iON BizTools
CEG SRS Template
- CEG_Feature
Roadmap_Template
- CEG_Sales
Force_Training and
Briefing_Template
- CEG_Onboarding
Process_Template
- CEG_Customer
Deck_Template
- CEG_Deployment
Plan_Template
CEG_Feature_Capabilities
- CEG_Architecture and
Design_Template
-TCS
CEGInternal
DPCA Use
Template
only
Location on iQMSWiki
Requirement tracking
(Backlog)
WBS planning and tracking
CEG Templates
Rationale
Trainings are taken based
on the Planned or On
Demand basis thus it is
required to have a
nomination sheet.
It is necessary to provide
the explanation of the
course which is being
developed.
Release recoding includes
all the new features
incorporated in the latest
release which is being
deployed.
To reduce the accessing
time of the customer and to
make it more approachable
it is uploaded in the form
as E- learning content
prepared by the E-Learning
Team.
Assessment helps evaluate
the student as it’s an output
for analyzing the course
and derive his level of
understanding.
 Defect logging
 Multi User support
 Exhaustive
functionality
In line with process and
product requirements , thus
avoiding duplication of
data
Aligned with the CR
Management Tool in iON
Templates specific to
Product teams
Uncontrolled when printed/downloaded
Details specific to
product lifecycle
captured
23
Tailoring Guidelines
Solution Engineering UPP
Version 1.0
iON Templates
VBU Level UPP
iON_Final
Inspection_Checklist
iON Checklists
iON Coding Guidelines
iON Guidelines
PF
1160_CSS_Form_Products
iON Forms
Defect Analysis and
Metrics
Reporting Product
specific metrics
- In sync with
Corporate UPP
template. Details
common to suites
across for iON
customers pre-filled in
for operational ease
- Refers to Solution
Engineering UPP for
pre-filled common
sections
Checklist specific to
Product life cycle
Guidelines specific to
iON Product teams
Details specific to
iON product lifecycle
captured
Metrics specific to
product team to be
collected and
uploaded in
Knowmax
Note : Refer to iON iQMS for the complete list of current documents
TCS Internal Use only
Uncontrolled when printed/downloaded
24
Tailoring Guidelines
Version 1.0
Mandatory Note:
TCS Internal Use only
Uncontrolled when printed/downloaded
Tailoring Guidelines
Version 1.0
FEEDBACK FORM
To: DEH, <IOU>
Date:
Location:
From:
Project/Support Group/Other Functional Group:
Feedback details (Comments / Suggestions / Corrections / Queries)
(Please use additional sheets, if necessary)
For IOU DEH’s use
Action assigned to:
Details of action taken:
TCS Internal Use only
Date assigned:
Uncontrolled when printed/downloaded