1

User Manual for Design Review Council Audit in

eLMS

For AFS PD - E&E and Relevant users only

Released on 18th July 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.

2

Document Release History

Revision Date Author Version Summary Approver

V1.0.0 18-Aug-2015 Jawad Ahmed S Initial Version.

V2.0.0 18-July-2016 Jawad Ahmed S Modified version based on

new workflow

3

Table of Contents

1. INTRODUCTION ....................................................................................................... 4

2. DESIGN REVIEW COUNCIL AUDIT PROCESS WORKFLOW .............................................. 5

3. ACCESS ELMS LOGIN PAGE THROUGH MCONNECT ....................................................... 6

4. DRC WORKFLOW STATES.......................................................................................... 8

4.1. SUBMITTED ....................................................................................................... 8

4.2. AUDIT UNDER PLAN .......................................................................................... 11

4.3. REJECTED ....................................................................................................... 13

4.4. AUDIT REPORTS ATTACHED ............................................................................... 14

4.5. CLOSURE IN PROGRESS .................................................................................... 16

4.6. CLOSED .......................................................................................................... 17

4

1. Introduction

The scope of this document is to instruct / teach an end user on how to initiate, manage and

control DRC Audit use case using eLMS tool.

DRC Audit is performed 4 times in a vehicle project lifecycle based on the MPDS gateways. The

following illustrates the DRC Audit frequency.

DRC1 & DRC2 Audits – It is performed before VV gateway and the vehicle build phase falls in

Concept Phase (MULE)

DRC3 Audit – It is performed before SOP gateway and the vehicle build phase falls in VP0 or

VP

DRC4 Audit – It is performed before SOP gateway and the vehicle build phase falls in VP or PP

Following are the states whose details are given in Chapter 4.

1.1 SUBMITTED

1.2 AUDIT UNDER PLAN

1.3 AUDIT REPORT ATTACHED

1.4 CLOSURE IN PROGRESS

1.5 REJECTED

1.6 CLOSED

5

2. Design Review Council Audit process workflow

Figure 1:

6

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

(Refer Figure 2)

3.2. Click on More link from M&M Subsites section (Refer Figure 3)

Click on More link

7

3.3. Click on E&E eLMS link from the MConnect // M&M Subsites list (Refer Figure 4)

3.4. eLMS Login page is loaded successfully as shown below (Refer Figure 5)

Click on E&E eLMS link from M&M Subsites

8

4. DRC workflow states

4.1. SUBMITTED

4.1.1. DRC creation is not project specific. People who has access to Design Review Council

project area can create a DRC and also view the status of DRC.

4.1.2. To create a DRC 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 Figure 6)

Figure 6:

4.1.4. User can create a DRC by clicking the Create a Design Review icon from the Dashboard

(Refer Figure 7).

Figure 7:

9

4.1.5. The DRC page is displayed as shown in Figure 8.

Figure 8:

10

4.1.6. User can also create a DRC by navigating into the DRC dashboard and clicking on Create a Design Review icon as shown in Figure 9.

Figure 9:

4.1.7. The DRC page is displayed as shown in Figure 8.

Select Design Review Council

project from Other Projects area

11

4.1.8. The creator has to be either System Engineer or System Lead. A DRC auditor will not have access or permission to create a DRC.

4.1.9. The creator will fill all the mandatory fields, assign the DRC to auditor by selecting his name in Assigned To field and save the work

item. The state gets changed to SUBMITTED (Refer Figure 10). The creator will also add the HOD and CC Lead names in the

Subscribers section. Reason for Rejection field also gets enabled.

Figure 10:

4.2. AUDIT UNDER PLAN

4.2.1. The auditor will get a mail notification regarding the DRC work item. The auditor can either accept or reject the DRC.

4.2.2. If the audit is legal then auditor will select the action Auditor Accepts and save the work item (Refer Figure 11).

4.2.3. Observe that all the fields become read only except Task Completion Date.

4.2.4. DRC auditor will not be able to modify any fields in the SUBMITTED state.

12

Figure 11:

4.2.5. The state changes to AUDIT UNDER PLAN, the Open Audit, Closed Audit and Total Audit Points fields gets enabled (Refer Figure

12).

13

4.3. REJECTED

4.3.1. While reviewing the DRC if auditor find the DRC is not genuine then he will reject the DRC by selecting the action Auditor Rejects,

provides the reason for rejection in Reason for Rejection field, assign it back to creator in Assigned To field and save the work item

(Refer Figure 13).

Figure 13:

4.3.2. The state gets changed to REJECTED, no further action can be performed (Refer Figure 14)

Figure 14:

14

4.4. AUDIT REPORTS ATTACHED

4.4.1. The auditor will fill the open audit, closed audit points and the total will automatically sum the two and will be displayed in the Total

Audit Points column.

4.4.2. The auditor has to attach the audit points gathered through excel in the tool by clicking on Attach Supported Documents link as

shown in figure 15.

Figure 15:

4.4.3. The auditor will browse the audit findings sheet, attach it to the DRC and save the work item as shown in figure 16.

Figure 16:

15

4.4.4. After attaching all the audit points, the auditor will fill the Open and Closed Audit Points field, select the action Attach Audit

Reports and save the work item DRC (Refer Figure 17).

Figure 17:

4.4.5. The state changes to AUDIT REPORTS ATTACHED, all the stakeholders will get a mail notification regarding the attached audit points

status (Refer Figure 18).

Figure 18:

16

4.5. CLOSURE IN PROGRESS

4.5.1. The auditor will then fill all the audit points and once all open points are closed (i.e. Closed Audit Points becomes 0) then he will

assign the DRC to the creator by filling the Closed Audit Points section, assign it to the creator in Assigned To field, select the action

Assign to SE / SL and save the DRC (Refer Figure 19).

Figure 19:

4.5.2. The state changes to CLOSURE IN PROGRESS, all the stakeholders including the creator will get a mail regarding the closure of the DRC

(Refer Figure 20).

Figure 20:

17

4.6. CLOSED

4.6.1. Once all the points are closed then audit will attach the final updated audit findings, select the action Audit Closure and save the DRC

(Refer Figure 21).

4.6.2. Observe that all the fields get greyed out and no further action can be performed.

Figure 21:

4.6.3. The state changes to CLOSED and all the stakeholders are notified about the DRC closure (Refer Figure 22).

Figure 22: