110 likes | 346 Views
ADM Screener Transition to ASB adm Team. Kun Chen October 2010. Contents. Transition time DCT tools for adm screener CR Screener CRe Support GSP/customer support Lab support Adm CR delivery Adm Warning status of load clean up. Related Documents. PMXXX Documentation
E N D
ADM Screener Transition to ASB adm Team Kun Chen October 2010
Contents • Transition time • DCT tools for adm screener • CR Screener • CRe Support • GSP/customer support • Lab support • Adm CR delivery • Adm Warning status of load clean up
Related Documents • PMXXX Documentation • FS Document ID in KioskLive • Link is https://wcdma-ll.app.alcatel-lucent.com/livelink/livelink.exe?func=ll&objId=31677044&objAction=browse&viewType=1 • ADM Design Wiki page • Like is http://wcdma.ih.lucent.com/bin/view/WcdmaRNC/Adm_Design_Env_Web_Page#V7_1_2_adm_design_environment • ADM mediation Requirement & MD SFS • Refer to ADM Design Wiki page
Transition time • Transition time from now on to November 30, 2010 • What I should do: step by step adm transition process • Form now on to Nov. 10, continue to screen adm • From Nov.10 to Nov. 30, adm screener support • What you should do • From now on to Nov.10, learn purpose • From Nov.10 to Nov.30, adm screener practice • On Nov.30 transition over
DCT tools for adm screener( Train time 1 Work Day) • You should able to login DCT as adm screener • When CR come to adm FA • Adm FA is 9370 RNC_SW_DEV_Adm. make sure all trace files (OMU, MIB, and/orPROXY) attached in this CR • Change CR status to Analyze • CR Update status in Custom:Custom 3, like: • 10W42.4: jchan004 reviewed for CallP; assigned to kunch to screen. • 4. Change CR status to AnalysisCompleted If you complete your analysis • If CR is NOT adm CR • Update the reason in Analysis note and Custom.Custom 3 • Change FA to 9370 RNC • Change CR status to NEW • If CR is ADM: • Open CRI for adm • Open another CRI for prop • Put ahmedhu in Custom.Custom 4 • Put PROP into CRI Custom.Custom 1, if CRI is for prop • Put SURF into CRI Custom.Custom 1, if problem is for perious version
CR Screener (2 days) • Find Error message from the trace file • What is the problem CR complained • Is this error trace belong to adm? • Check Mediation requirement and SFS MD to understand if feature required • What does parameter (s) do? • Does MIB parameters with correct ? • What TGE messages value? • Is this TEA correct to send callp? • Useful tools ( those are in OCB Sever (uottso13) • Mib table read tool • TGE decoder
CRe Support (2 Days) • Understand the requirement from CRe • Clarify OAM Modeling and mib parameters • Make sure implementation steam and delivery stream with callp • Assign the right person to do the good thing • DE • time for delivery
GSP/customer support ( 2 days) • Trace files may come to you to investigate the problem • If the trace files not completed, you may need to read through mib value and/or try to understand work order • Mib diff tool is also in OCB Sever (uottso13)
Lab support (1 day) • Integration Test goup may contact to you for mib support • Most of case for support is for feature DI • You will need to know what the feature flag parameter, and the correct value • If it have problem, you need to look at the trace files and/or mib value.
Adm CR delivery and Adm Warning status of load clean up (1 day) • Before the delivery • Make sure you are in the latest load label • Processing adm global test and target compiling • Make sure CI closed • DWO.inspection info is linked to this CI, and DWO.RCA is updated • Make sure description template is fill in the description of activity • Delivery • Need send email to doina.lepadatu@alcatel-lucent.com to ask delivery permit. • Cut new baseline label for adm CR • Recommended this new baseline label for adm CR • Adm Warning status of load clean up • 1. when the Warning status of load come from email, please note if there are any Warning from adm • 2. Open CR for adm Warning, and assign this to adm fellow to fix .