Conference iosg::all-in-1_v30

    Hi Sue,
    
      You ask a very simple question - why doesn't TM work across time zones - 
    and unfortunately we don't have an answer, but rather more questions.
    
      The biggest problems facing TM across time zones are a lack of
    strategy, followed by a lack of action. 
    
      This is not just a Digital problem!  I am not aware of any TM product
    on the market which does support time zones, and we (in Charlotte at least)
    are painfully aware of the need, as well as the difficulties associated 
    with implementing a solution.  We have some ideas for supporting time zone 
    meetings (and scans!), but it is a significant modification to the existing
    product, and I am not aware of any plans for any such enhancements.
    
      We have endlessly debated and discussed the implementation of time
    zones, and the following points merit consideration:
    
            1)  When scanning, where will the users be?  If they are coming to
                the local time zone for a meeting (or traveling someplace else -
                which is really impossible to consider), then I want to scan
                local hours instead of offset hours.  The most simplistic case
                is to implement a flag to choose whether a user should be
    		scanned locally, or with the offset.  In this case, the 
    		scheduler is required to know where the attendee will be at 
    		the time of the meeting.  Also, to further complicate things, 
    		we have implicitly decided that the scan is based on the 
    		scheduler's time zone.  What if the scan is for a remote event?
    		In that case, the primary scan form should probably prompt for 
    		the 'base' time zone of the scan.
    
            2)  Regarding meeting scheduling, all the same conditions and
                concerns apply.  What is the 'base' time zone for the meeting -
                local or remote?  Every event on the user's calendar should take
                into consideration the time zone in which it will take place.
                For attendees, they must have the option to schedule the meeting
                in _any_ time zone (if they travel a lot), or minimally, either
                the originating or local time zone.  And how do you handle the
                case where the originator scheduled it for a remote time zone?
                What time does the meeting really take place?  (the code can
    		use GMT to track it, but it can be very confusing for us humans)
    
      There aren't any easy answers to the time zone question, but we will
    be happy to discuss it further if you like.
    
    						Cheers, regards, Dan'l

        I've submitted an SPR requesting this functionality.  We get a few
        calls about this every month in the US CSC.
        
        Dave Zaniewski

    RE: .1 --
    
    Dan'l --
    
    In fact, Calendar Manager from Russell Information Sciences (of Laguna
    Beach, Cal) implements time zones. Their UI can either assume local
    time, or assume remote time, or ask you for each meeting (user profile
    choice). 
    
    We haven't seen any other time management system that attempts to do
    it.
    
    Dave.

    Thanks for replies to my initial TM question - I had no idea it was
    such a potential mine field! However, altho' I don't understand  all the
    details, I guess my reponse to the customer will be that almost without
    exception, time zones are not part of the equation but that there is
    on-going debate and development in this area and Digital is at the
    fore-front.Fortunately, we have a good relationship with this customer
    so I think he will understand why we have to be a little wooly in our
    reponse.  regards Sue.