Honda Jp Process.docx

  • Uploaded by: KarthikSelvaraj
  • 0
  • 0
  • June 2020
  • PDF

This document was uploaded by user and they confirmed that they have the permission to share it. If you are author or own the copyright of this book, please report to us by using this DMCA report form. Report DMCA


Overview

Download & View Honda Jp Process.docx as PDF for free.

More details

  • Words: 438
  • Pages: 4
Honda Japan AMS Processes FF ID Process Please check attach document for more details.

FF Request Global GRC Training Approach Firefighter Access Request.pptx

Incident Process: 

In JP & AO we don’t contact incident user directly. We write mail to HELPDESK with our analysis, solution or additional information required if any? --------------------------------------------------------------------------------------------------------------------------------

------------------------------------------------------------------------------------------------------------------------------

pg. 1

Reason on which JP & AO incident can’t kept pending “Awaiting Customer Information”: o Awaiting additional information from business user/Helpdesk o Solution provided, awaiting confirmation o Awaiting reply from COE o Awaiting reply from SAP (Oss message created) o FF id is requested for missing access Note: update the incident on a regular basis.

Honda Japan AMS Processes 

In case of Monitoring tickets, don’t ask Helpdesk. On the other hand, complete your analysis and share the details of JP onsite team consultant (Sawae-san for CO, AA, PS and Yamada-san for GL, TAX, AR, AP, FSCM) and ask them to check with COE whether any action is required from AMS team.

Check attach document for more details on how to handle incident, Ptask etc in SNOW.

SNOW.zip

Rev Track (RFC Process)    

First, update the consultant name in Rev Track, who is working on that RT Consultant is required to provide “Initial Effort”, estimated hours to complete (COR/FS, Configuration/Development, FUT, SIT) JP onsite team validate the initial effort and inform RT lead (Honda) to update the same in Rev track. After initial assessment approved in Rev track, consultant need to provide “Final Effort Estimate” in attach format.

(RTXXXX_InitialorFina l)Honda GSP AMS Process RFC Estimation.xls

HPQC Process: The below points need to be taken care while raising defect in HPQC: 1. 2. 3. 4. 5.

RFC Owner: AMS RFC Phase: SIT/FUT RFC#: Rev Track#: CR Reason:

 

Rev Track History log of Details need to be updated. Update comment section regularly for defect

Other Points:    

pg. 2

When RFC is in TDD step then ask to create Folder for Testing. (folder should be created before development) Re-plan FUT, SIT in case of defect Update the actual hours (only after Rev Track step is complete from AMS side) Update rev track on a regular basis (after completing each step)

Honda Japan AMS Processes BPO and SME JP & AO Please see bi-weekly report of 23th of March, Page#4. (2017-3-23 GSP CoE Leads bi-weekly call.ppt) You can see the name for after 94-Ki per module. http://hondateamlink.ham.am.honda.com/hna/sites/GSP_Prod_Support/Shared%20Documents/Forms/All Items.aspx?RootFolder=%2Fhna%2Fsites%2FGSP%5FProd%5FSupport%2FShared%20Documents%2 FWorking%20Documents%2FMeetings%2FCoE%20leads%20biweekly%2F2016%5F4Q&FolderCTID=0 x0120003070F35F845561469D88E32DD45FD115&View=%7B361BE662%2D8A3F%2D4ABB%2DA31B %2DD8DB61B15148%7D

<SME> Please see COE organization structure document, page #18. (GSP CoE Org Chart.pptx) http://hondateamlink.ham.am.honda.com/hna/sites/GSP_Prod_Support/Key%20Project%20Documents/F orms/AllItems.aspx?RootFolder=%2Fhna%2Fsites%2FGSP%5FProd%5FSupport%2FKey%20Project%2 0Documents%2FCoE&FolderCTID=0x01200065920A6D82DEAA4EBF608E2D17A62E1B&View=%7BA8 A4C962%2DCCFB%2D48FD%2DA0FD%2DCA9747CE1D19%7D

pg. 3

Honda Japan AMS Processes

<SME>

pg. 4

Related Documents

Honda Jp Process.docx
June 2020 0
Honda
November 2019 35
Jp
June 2020 8
Jp
June 2020 12
Hero Honda
May 2020 14
Honda (hmsi)
November 2019 12

More Documents from ""