[Search for users] [Overall Top Noters] [List of all Conferences] [Download this site]

Conference kernel::csguk_systems

Title:CSGUK_SYSTEMS
Notice:No restrictions on keyword creation
Moderator:KERNEL::ADAMS
Created:Wed Mar 01 1989
Last Modified:Thu Nov 28 1996
Last Successful Update:Fri Jun 06 1997
Number of topics:242
Total number of notes:1855

71.0. "E.C.S.O. Info Interchange." by KERNEL::ADAMS (Venus on Remote Control) Fri Sep 08 1989 14:10

    
    This topic is for information exchange between the CSG group
    ECSO responsible engineers. Details should be entered here
    for handover between engineers, including outstanding issues,
    e.g. "Close call xxx if no activity within yyy days" etc.
    
    Brian.
    
T.RTitleUserPersonal
Name
DateLines
71.1Distribution list.KERNEL::ADAMSVenus on Remote ControlFri Sep 08 1989 14:284
    
    There is a distribution list at POST:SYSECSO.DIS for all ECSO
    responsible engineers
    
71.2Update W/E 9-Sep-1989KERNEL::PETTETNorm Pettet CSC BasingstokeFri Sep 08 1989 14:3411
    w/e 9-Sep-1989
    
    Customer		log number	status
    ========		==========	======
    Banque Paribas	40363		Status report required 29-Sep-1989
    Leyland Daf		01050		Close call if no activity in
    					7 days
    Cranfield Inst	01430		Request status update from CRT
    Minster Insurance	82710		Have requested to close call.
    
    /Norm
71.3new procedureKERNEL::PETTETNorm Pettet CSC BasingstokeWed Apr 25 1990 14:0726
From:	KERNEL::PETTET "MNEMONIC NORM  25-Apr-1990 1030" 25-APR-1990 10:46:35.80
To:	@POST:SYSTEMS
CC:	
Subj:	ECSO

Gents,

	Recently engineers have been dealing with calls on ECSO but haven't 
been informing the engineer responsible for updating ECSO. Can I therefore 
suggest the following procedure be adopted :-

	1) On receiving a call,that is on ECSO, check ECSO notice board for 
	current action plan.

	2) Adopt current action plan if it applies to current fault.

	3) After closing call mail ECSO responsible engineer (see ECSO notice 
	board) with details and also whether the call needs to be noted on ECSO.

	Using this method it will make, what is already a time consuming 
process, very much easier.

	Many Thanks for your assistance

 	Norm
    
71.4KERNEL::GARNETTMon Apr 30 1990 18:529
    HI FOLKS,
            WOULDN'T IT BE BETTER IF "EVERYONE" DOES ECSO...THEN IT
    WOULD BE UP TO THE INDIVIDUAL ENGINEER TO UPDATE ECSO , AFTER A
    CALL
    
    NIGE
    
    PS......TIME FOR THE 'FEW" TO HAVE SOME HELP ??????
    
71.5don't confuse it still further!!KERNEL::PETTETNorm Pettet CSC BasingstokeTue May 01 1990 11:5914
    Nige,
    
    	As I understand it from Brian when you are the assigned ECSO
    person it is upto you to update ECSO and monitor calls on RSDS and
    CFSU. If everyone did ECSO you could well end up with ECSO being
    neglected (is everyone realy going to update ECSO after a call,
    I very much dought it) Further the regions prefer to have some central
    ECSO contact, as opposed to everyone, so atleast for 1 week some 
    sort of consistancy it attchieved. 
    
    Cheers....Norm Pettet
    
    
    	
71.6Let Sanity prevailKERNEL::ADAMSVenus on Remote ControlTue May 01 1990 12:1516
    
    I agree with Norm (Sorry Nige), for the main reason, that if
    everyone accessed ECSO, then who would see the ***s for the 
    updates and print them. Remember that if someone other than the
    assigned person, DISplays an entry that has been updated, then the
    * is no longer appended to that record.
    
    There are more people now with ECSO responsibility, so your turn
    doesn't come round that often. (Unless you have missed a few by
    arranging other activities, then you'll find a few extra weeks
    assigned, to be fair to the others.)
    
    Still, when Regionalisation comes ..................
    
    Brian.
    
71.7KERNEL::GARNETTWed May 09 1990 14:5010
    HI FOLKS,
            
            I WASN'T SUGGESTING THAT THE "DUTY ECSO" MAN GOT DISBANDED
    BUT THAT EVERYONE WOULD HAVE THE CAPABILITY/OWNERSHIP FOR INDIVIDUAL
    CALLS, WITH THE ECSO MAN CONTINUING IN HIS PRESENT ROLE.....LESS
    FREQUENTLY !!!!!
    
    REGARDS
    
    NIGE
71.8nice info on ecsoKERNEL::PETTETNorm Pettet CSC BasingstokeWed Dec 04 1991 13:0146
                  I N T E R O F F I C E   M E M O R A N D U M

                                        Date:     04-Dec-1991 12:14pm GMT
                                        From:     Ken Robb
                                                  ROBB
                                        Dept:     Customer Services
                                        Tel No:   _833 3819

TO: See Below

Subject: ECSO and NICE


Accepting a new call on ECSO.
----------------------------

When accepting a call on ECSO please have a NICE key user set the exceptional 
condition flag

As the flag can only be set against the customer and NOT the system it is 
important that the comments field should identify which system has the problem.
This is a feature of NICE.

Comments field is not the place for the technical action plan. As ECSO gets 
updated, the comments field could be misleading.

Examples.   
      
1.    Reason flag = PS (Problem system)
      Comments: System 8600 Serial 86123456 is on ECSO. see board.
      
2.    Reason flag = PS
      Comments:8530 SN 87006741900 is on ECSO. See RDC notice board ( or  ECSO
           user for action plan ).
           Notify duty manager as soon as call logged on this system.
 
The same applies to the DSDNINFO screen.



Regards,


Ken.