1
User Manual for FF_Chassis_HIL_Planner
For AFS PD - E&E and Relevant users only
Released on 01st Nov, 2016
Strictly Confidential document. All Rights Reserved to Mahindra & Mahindra also
regarding distribution, exploitation, editing, and reproduction as well as in the
event of application for Industrial Property Rights.
1
Document Release History
Revision Date Author Version Summary Approver
V1.0.0 1-Nov-2016 Jawad Ahmed S Initial Version.
2
Table of Contents
1 Introduction 3
2 FF_Chassis_HIL_Planner Process Workflow 4
3 Access eLMS login page through mCONNECT 5
4 FF Chassis HIL Planner workflow states 7
4.1 CREATED ........................................................................................................... 7
4.2 ASSIGNED ....................................................................................................... 11
4.3 UNDER REVIEW................................................................................................ 12
4.4 REJECTED ....................................................................................................... 13
4.5 IN PROGRESS .................................................................................................. 14
4.6 COMPLETED ..................................................................................................... 15
4.7 REOPENED ...................................................................................................... 16
5 View the Tasks as Planner 17
3
1 Introduction
The scope of this document is to instruct / teach an end user on how to
create a Task and assign it to the respective Test Engineer through eLMS
tool. The created tasks are captured in the planner and the planner will
display the planned, actual and due dates in a planner view.
Following are the states whose details are given in Chapter 4.
1.1. CREATED
1.2. ASSIGNED
1.3. IN PROGRESS
1.4. COMPLETED
1.5. UNDER REVIEW
1.6. REJECTED
1.7. REOPENED
4
2 FF_Chassis_HIL_Planner Process Workflow
Any ER stakeholder can
create a TaskCREATED
Responsible engineer
will close the task after
completion
Responsible engineer
will execute the task
Test Lead assigns to
responsible Test
Engineer
COMPLETED
ASSIGNED
IN
PROGRESS
HIL Setup Planner Workflow
If creator is Test Lead
Test Engineer assigns
the Task to Test Lead
for review
If Test Lead agrees
If creator is Test
Engineer
No
Test Lead Rejects the
TaskREJECTED
Assign to
Engineer
Assign to
EngineerUNDER
REVIEW
Assign to Test Lead
No
REOPENED
Assign to
Engineer
Reopen
Test Lead can reopen
the Task if it is not
completed
5
3 Access eLMS login page through mCONNECT
3.1. Launch any browser (IE10 / Firefox / Chrome) and access
https://mahindraonline.sharepoint.com/sites/mconnect/pages/default.aspx
3.2. Click on More link from M&M Subsites section
Click on More link
6
3.3. Click on E&E eLMS link from the MConnect // M&M Subsites list
3.4. eLMS Login page is loaded successfully as shown below
Click on E&E eLMS link from M&M Subsites
7
4 FF Chassis HIL Planner workflow states
4.1 CREATED
4.1.1. FF Chassis HIL Planner is specific to Electronics Reliability team, hence any task created has to be done with ER project area.
4.1.2. To create a task you need to enter your login ID (Mahindra\Token No) and the password that is given for Windows login.
4.1.3. Once you login E&E eLMS Dashboard is displayed (Refer below figure)
8
4.1.4. Select Electronics Reliability link from the Other Projects section.
4.1.5. Electronics Reliability project area is displayed as shown below
9
4.1.6. Click on Project Overview tab and navigate to FF Chassis HIL Planner team area.
4.1.7. Click on FF Chassis HIL Planner, the planner dashboard is displayed as shown below.
4.1.8. Click on Create a FF Task icon from the dashboard, the Task work item is displayed as shown below.
10
4.1.9. The creator can either be a Test Lead or Test Engineer. The creator will fill the Summary field and few fields and save the Task.
4.1.10. The state gets changed to CREATED.
11
4.2 ASSIGNED
4.2.1. Any ER stakeholder can create a Task under FF Chassis HIL Planner.
4.2.2. If the task is created by Test Lead then he has to fill all the mandatory fields, select the action Assign to Engineer, select Test
Engineer name in the Assigned To field and save the task.
4.2.3. The state changes to ASSIGNED and the Test Engineer will be notified with the Task id and the state.
12
4.3 UNDER REVIEW
4.3.1. If the creator is Test Engineer then he has to assign the Task to Test Lead for review.
4.3.2. In order to do that the TE will select the action Assign to Test Lead, fill all the mandatory fields, assign the Task to the Test Lead
and save the Task.
4.3.3. The state changes to UNDER REVIEW, test lead will receive a mail for review.
4.3.4. Test Lead will review the task and if it is valid then he will select the action Assign to Engineer select the engineer name in the
Assigned To field and save the task.
4.3.5. The state changes to ASSIGNED as shown in previous figure.
13
4.4 REJECTED
4.4.1. While reviewing if the task created is not a valid one then the lead will select the action Reject, provide the reason in Reason for
Rejection field and save the task.
4.4.2. The state changes to REJECTED and no further action can be performed.
14
4.5 IN PROGRESS
4.5.1. Test Engineer will start working on the task by providing the Customer Responsible Engineer, Actual Start Date and then select
the action Start Working and save the task.
4.5.2. The state changes to IN PROGRESS, all the stakeholders in the task will be notified with the state change.
15
4.6 COMPLETED
4.6.1. Once the TE completes the task he will close the task by selecting the action Complete, assign the task to Test Lead and save it.
4.6.2. The state changes to COMPLETED, the Actual Completion Date gets automatically filled by the system.
16
4.7 REOPENED
4.7.1. In later point of time if the task needs to be reopened due to incorrect closure or task not yet completed then only Test Lead can
reopen.
4.7.2. In order to reopen the task the lead has to select the action Reopen, provide the reason in the Description field, assign to the
responsible test engineer and save the task.
4.7.3. The state changes to REOPENED and the test engineer will get a notification with the reopen comments.
4.7.4. The lead then select the action Assign to Engineer and the work flow process is repeated as mentioned in the above states.
17
5 View the Tasks as Planner
5.1. All the created task pertaining to the categories can we viewed as a Planner.
5.2. In order to view the planner the ER stakeholder has to navigate to FF Chassis HIL Planner dashboard and click on FF Chassis HIL Planner
icon as shown below.
Click on FF Chassis HIL Planner icon to
view the plan
18
5.3. The plan is displayed as shown below
19
5.4. The plan column views can be customized as required by editing the plan view.