CRP2 Run Methodology & Monitoring 

Dear SCL Core Team-mates,

At the very outset, kudos to your efforts for providing the data & test cases for the CRP2 requirements. Though, there were a few exceptions but we all could manage the voluminous data & business cases for the CRP2 run.

We are moving through the CRP2 phase wherein you all are running through the BCS (Business Case Scenario) documents.

As discussed in the forum of Mar 03 2008, the steps to be adhered  for the CRP2 run are as under :

  1. All the Data Validations carried out by you to be documented and posted on the "Data Validation Template" alongwith your respective IT co-ordinators.
  2. The BCS processes to be run through as per the "CRP2 Plan" published & circulated to you all.
  3. The BCS process validation to be noted on the BCS & the "Output expectations" to be matched with the CRP2 process run thru by you.
  4. In case, there are no exceptions wrt the expected output / performance of the BCS process, the BCS has to be categorized as "Passed" & duly "Signed-off" by you.
  5. In case, the BCS run does not yield the "expected" output as stated on the BCS document, the exception / bug observed in the process run has to be "noted down" on the BCS. The same exception(s) to be posted under "CRP2" head of your respective module under BUGZILLA before the day close of the referred BCS run.
  6. At 1630 Hrs everyday. the BCS Monitoring Co-ordinators (Rakesh Misra of SCL + Pramod Kumar of TCS) shall take the feedback of your BCS run status, and post on their "BCS Progress Monitoring Chart" which would be updated on the "ERP-Sustainability Blog" for everyone's reference.
  7. At the CRP-2 close, there should be no "exception" apart from the BUGZILLA postings carried out regularly by you all. The BUGZILLA points closure shall render the CRP-2 "sign-off" which shall be executed by your Signing-Off Authorities which is your responsbility.

We have to ensure that the above charter is followed as a mandate, and there should be no exception to it. This would make the entire CRP-2 process run transparent with absolute accountability of all concerned within the ERP-Sustainability team (both TCS & SCL Core Teams).

Ram shall be co-ordinating the module runs and you can escalate any exceptions to him during the course of the CRP-2 run.

We too are available on site to help you out for any exception, for which you may please contact us.

Thanks & regards,

Rajat Sharma & SK Soni

Comments (0)
Rakesh B Mishra March 3rd, 2008 10:15:02 AM