Categories
Uncategorized

Russia will abolish Daylight Saving Time, Microsoft to provide updates and guidance

[Note: please see http://blogs.msdn.com/b/mthree/archive/2011/08/11/dst-081111.aspx for the released Windows Update for August 2011…]

 

Remember when I wondered out loud about Russia abolishing daylight saving time?

Well, I do. We’ve been following this quite closely at Microsoft, and have seen the news updates.  I have really improved my understanding of the Cyrillic alphabet in the last few months.

From the “more detail than you want to know department”: this Bill went through what’s called the first reading with their legislature (the State Duma) this past week (April 19) and will likely be signed into law within the next 14-20 days, and effective 60 days after it’s official publication. But our engineering and services teams are already anticipating this change.

As we understand it, Russia will not “fall back” and revert to the established Russian Standard time zones this fall. Instead, the country will remain on perpetual “Summer Time”. From a technical standpoint, this can be a challenging way to handle a permanent transition away from DST. This will be known, I think, as “Decree time” but effectively will be Russia’s new standard time.

We also know that other countries – including Ukraine and Belarus – may follow Russia’s lead in their move to abolish DST. I expect that as Russia enacts this Bill into law we will see other countries in the region follow suit.

[Revised 8/11/2011] Russia has signed this into law, and we’ve released KB article 2570791 for the August 2011 cumulative time zone update for Windows operating systems. See this post for more details.]

A few interesting facts on DST:

As you may know, daylight saving time was originally proposed and adopted as a response to energy conservation early in the 20th century. It was repealed after World War I in 1919, and then reinstated by the Uniform Time Act of 1966 in the U.S.

Originally, a report by the California Energy Commission in 2001 (available here) concluded that both Daylight Saving Time would probably save marginal amounts of electricity. At the time, California considered adopting DST throughout the year to address the electricity problems in the state in 2000. For the proposed Summer Double DST, the study suggested that the state would “save hundreds of millions of dollars because it would shift electricity use to low demand (cheaper) morning hours and decrease electricity use during higher demand hours.”

The Energy Commission has also published a report titled “The Effect of Early Daylight Saving Time on California Electricity Consumption” in May, 2007. The report concluded that DST had little or no effect on energy consumption in California. A more recent study from the University of Santa Barbara (available at http://www.nber.org/papers/w14429) concluded that there is little evidence that DST actually saves energy, and in the terms of the study, may actually increase residential electricity demand. The study focused on residential electricity demand over a three year period, and concluded that energy consumption actually increased approximately 1 percent during DST, and as much as 2 to 4 percent in the fall. The authors also hypothesize that the impact of the energy increase during DST would likely be higher in other parts of the U.S.

Health concerns also play a role, as recent studies showed an increase in heart attacks, sleep disorders and other problems associated with time changes. As I noted in this article, the Russian government originally considered abolishing daylight saving time in the country as there are serious negative impacts on people’s health, calling out how the time changes attributed to up to 70,000 premature deaths a year in Russia alone. They cited “medical emergency calls increasing by 12% in the first two weeks after each change, suicide rate jumping 66%, accident rate rising by 29%, heart attack rates – by 75%.” This research was also supported by a Swedish study referenced here.

So, that’s all nice, but what’s Microsoft doing about this change?

We’re working hard at Microsoft on this change at many different levels.  As past readers of this blog will know, most applications and services reference the underlying Windows OS for their TZ and DST rules, with some exceptions. This change in Russia has the potential for worldwide impacts on time references for multinational customers. Updates will be important not only for users in Russia but for connected systems around the world.

As such, our Windows team that follows DST and TZ changes globally will provide guidance to all product and services teams on the changes as the measure is formalized and put into law. We will announce more details on our support and updates to our products and services in the upcoming weeks and ensure that the changes are represented into our regularly scheduled Windows OS updates for DST and time zones.

[Added 05312011]  At this time, in preparations for the changes to the UTC offsets and elimination of DST in Russia, we plan to include the changes for the Windows Daylight Saving Time Cumulative Update, scheduled to be published in August, 2011. We will also include a roll-up of DST hotfix changes released during 2011, including those for Fiji, Samoa, Turkey, Chile, Egypt, Morocco and Newfoundland. See this post for more details. While Microsoft’s Services infrastructure will be updated to reflect these DST changes, it’s important that your computers — both clients and servers that connect to and interact with these services — should have the Windows DST updates applied in order to ensure data integrity.

We’ll also provide guidance and updates to help support the new changes in Russia run as smoothly as possible on our corporate site on DST at http://www.microsoft.com/time, with worldwide guidance and details on this important change. This site will provide the information needed by our customers and partners to react and issue updates to their products and services to accommodate this change. Our groups around the world will promote these changes locally, similar to the work that Microsoft New Zealand provided on http://www.microsoft.co.nz/timezone, supported and promoted by the efforts of the government here. For the change in Russia, we provide specific details and guidance in country at http://support.microsoft.com/gp/cp_dst/ru.

Which reminds me: we are also communicating our recommendations to help achieve more seamless transitions to new DST and time zone policies. (More information is also available at http://support.microsoft.com/gp/dst_ms_response.)

That’s a lot of work. Так давайте работать! 😉

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, RSS, DST, Russia

Also available via http://bit.ly/fiyMlX

Delicious Bookmark this on Delicious Bookmark and Share

Categories
Uncategorized

Will Russia abolish Daylight Saving Time?

buildings,Moscow,Photographs,religion,Russia,Saint Basil's Cathedral,St. Basil's Cathedral,travelJust back from vacation and good to see that some things never change. In this instance, it’s the discussion of changes to daylight saving time rules around the world.

Back in early 2008 Last year, I recall that the Russian government considered a bill abolishing daylight saving time or ”summer time” in the country.  Noting "ample research and statistical data” the bill highlighted that the move to and from summer time had serious negative impacts on people’s health, calling out how the time changes attributed to up to 70,000 premature deaths a year in Russia alone. They cited "medical emergency calls increasing by 12% in the first two weeks after each change, suicide rate jumping 66%, accident rate rising by 29%, heart attack rates – by 75%. "

Now Russia has again been considering a move to eliminate DST, and indications in the press are that they will do just that later this year. I’ve read in the news that Medvedev said he has "decided to cancel the shift to winter time, starting from this autumn," and that Russia will not move to daylight saving time on the last Sunday of October. 

A side comment: In his proposal, Medvedev said that the country would not “fall back” and revert to Standard time this fall. But, it would seem better for Russia to in fact move back to Standard time in October 2011, and then not make the “spring forward” change to clocks in March 2012. But who am I to argue with President Medvedev. 😉

We’ll continue to watch the developments on Medvedev’s plan. We do provide some guidance on http://www.microsoft.com/time, that in order to achieve more seamless transitions to new DST and time zones policies, Microsoft requests that governments provide the following:

  • Ample advance notice (1 year or more) of the planned change.
  • Official published confirmation of planned changes to DST or time zones.
  • Concentrated efforts on promoting the change to the affected citizens.

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, RSS,DST, Russia

Also available via http://bit.ly/heDKaM

Delicious Bookmark this on Delicious Bookmark and Share

Categories
Uncategorized

Of interest: Daylight Saving Time Issues with Alarms on Apple iPhones

As I noted earlier today, It’s Time To Fall Back An Hour in the US and Canada as Daylight Saving Time Ends This Sunday.

I know of several customers who use Apple iPhones in their Windows environments and of note is an issue in Apple’s iOS that impacted their European customers recently…

http://www.zdnet.com/blog/hardware/iphone-bug-leads-to-mass-european-sleep-in/10187

Apple notes this issue in their article on iOS 4.1: Repeating alarms may trigger incorrectly before or after DST change (http://support.apple.com/kb/TS3542):

Symptoms: In some regions, shortly before or after the daylight saving time (DST) change, repeating alarms created in the Clock app may work incorrectly.

Products Affected: iPod touch (4th generation), iPod touch (3rd generation), iPhone 3G, iPhone 4, iPhone 3GS, iPod touch (2nd generation)

Resolution: To resolve this behavior for existing alarms, set the repeat interval to Never. You will need to reset these alarms for each day you need them. After November 7th, 2010, you can set your alarms to repeat again.

Users of the iPhone and iOS should please note that there may also be a problem for systems over this coming weekend (thanks, Will) with the move to DST in North America: 

http://www.cnn.com/2010/TECH/mobile/11/05/apple.alarm.daylight.savings/index.html

Users who depend on the iPhone to wake them up should create one-time alarms specifically for Monday morning, said Apple spokeswoman Natalie Harrison.

"We suggest customers set nonrepeating alarms for now and reset after November 7 to resolve the issue," she told CNN.

Of course, good to know that “Later this month, Apple will release an updated version of its mobile software, iOS 4.2, which will permanently fix the problem, Harrison said.”

It’s not clear whether or not this update will be available prior to the upcoming "fall back".

 

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time,DST:

References to DST on Bing: 15,400,000 (up several million items); 15,500,000; 2,890,000.

Share this post: Bookmark and Share

Also available via http://bit.ly/cqxg0L

Categories
Uncategorized

Samoa adopts daylight saving time in 2010, but why at midnite?

I read in the Samoa Observer, and in case you missed the original news, Samoa will implement daylight saving time this September… MC900189348[1]

"…in response to the need for national strategies to address the crises with fuel and food prices. This new and exciting change will come into force on Friday night Saturday morning 25th September 2010 adjusting clocks forward 12:00am (0000Hrs) to 1:00am (0100Hrs) readjusting it back one hour from 1:00am (0100Hrs) to 12:00am (0000Hrs) on Friday night Saturday morning 2nd April 2011.

"Enquiries on daylight saving can be made to the Fair Trading and Codex Division of the Ministry of Commerce, Industry and Labour on the 4th Floor of the Accident Compensation Commission (ACC House), Apia, or its Telephone 20441."

More details may be found here: http://www.sits.ws/Home/tabid/1306/mid/6724/newsid6724/175/Samoas-Daylight-Saving-Starts-in-September-2010/language/en-NZ/Default.aspx

I wonder: do we have an office in Samoa? (Answer: no, but I think our offices in New Zealand may work with the nation.)

My concern here is the midnite change.

Here’s my regular advice for governments: in support of these types of changes, we provide guidance and Microsoft’s Policy in Response to DST/TZ Requests. It’s important for countries and territories to work towards seamless transitions to new DST and time zones policies, providing ample advance notice (of a year or more) with published confirmation of planned changes.

In addition – and this is important – we suggest that entities considering moves to DST implement changes at the next clock tick after 01:59:59 rather than at 00:00:00. Making the change at midnight can impact daily scheduled system events that sometimes occur at 12:00 midnite, such as back ups, data pulls or other automated tasks.

Apparently, I need to send out a few more emails to our folks in Public Sector.

 

Tags: Microsoft, Daylight Saving Time, Daylight Savings Time, RSS,DST, Samoa

Also available via http://bit.ly/aGDExf

Delicious Bookmark this on Delicious Bookmark and Share

Categories
Uncategorized

Connecting with Customers via Windows Error Reporting (Watson) and CEIP

Earlier this week, I provided a couple of glimpses at how product groups listen and respond to customers and partners.  In the seven plus years I’ve been at Microsoft, I’ve seen lots of different ways how product teams listen and respond to customers.  Previously, I worked along side the Engineering Excellence group, working on CPE across the product groups; now, I’m back in the Windows group… but I still work across product groups as they concentrate on improving customer satisfaction.

And core to the effort in most teams is the product and machine telemetry we get from millions and millions of customers through Microsoft Windows Error Reporting, the Customer Experience Improvement Program and software quality metrics (aka SQM, or ‘squim’).  For more on SQM, see this prior post.

Windows Error Reporting dialogWindows Error Reporting (WER) is based on the technology that was originally known as Dr. Watson, the Windows program error debugger tool included in previous versions of Windows, as far back as Windows 3.0, and was included in Windows 98, Me, and XP.(Check out Raymond’s blog to understand why Windows Error Reporting is nicknamed “Dr. Watson”.) 

WER captures software crash and hang data from end-users who agree to report it. You can access the data that is related to your applications online at https://winqual.microsoft.comGregg offers an overview on his blog on developers can use WER to debug what went wrong.  In Windows, WER feedback technology is part of Microsoft Windows XP, Windows Vista, and Microsoft Windows Server 2003 and 2008 operating systems.

We know that the effort makes an impact: as outlined in the above article, our analysis shows that across all the issues that exist on the affected Windows platforms and the number of incidents received:

  • Fixing 20 percent of the top-reported bugs can solve 80 percent of customer issues.
  • Addressing 1 percent of the bugs would address 50 percent of the customer issues.

Considering the hundreds of millions of customers around the world, that’s a considerable impact. 

Steve Ballmer outlined the effort in his 2002 letter on “Connecting to customers,” when he discussed how Microsoft can do a better job of serving our customers, and ultimately improve the customer experience through better communications and connections…

“The process of finding and fixing software problems has been hindered by a lack of reliable data on the precise nature of the problems customers encounter in the real world. Freeze-ups and crashes can be incredibly irritating, but rarely do customers contact technical support about them; instead, they close the program. Even when customers do call support and we resolve a problem, we often do not glean enough detail to trace its cause or prevent it from recurring.

“To give us better feedback, a small team in our Office group built a system that helps us gather real-world data about the causes of customers’ problems–in particular, about crashes. This system is now built into Office, Windows, and most of our other major products, including our forthcoming Windows .NET Servers. It enables customers to send us an error report, if they choose, whenever anything goes wrong.”

With WER, product groups get information that helps them identify the most common issues that our customers encounter on their computers, along with details that can help the teams debug the problem.  If you’ve every run into a problem or application crash on your computer, chances are that you’ve seen the prompt to provide more information to Microsoft on the failure.

We also provide WER for Independent Software Vendors (ISVs) and Hardware Vendors (IHVs) on the MSDN forums, helping them find and correct issues with their application, ultimately leading to improvements in their products.  These companies access our error reports database and discussion forums to address the errors and incompatibilities that creep up in their equipment drivers, software utilities and applications. (As noted on our sites, WER data is available to ISVs, IHVs and OEM and ODMs.)

Bill Gates said at PDC 2003…

“We allow anyone who has an application that runs on Windows to sign up and get the reports that relate to their application, and we’ve got winqual.microsoft.com where people can do that.

“Today we’ve seen a lot of that activity from the driver manufacturers, but we want to see even more at the application level so it gets us working together on anything where a user is not having a great experience.”

Coupled with the telemetry from WER is the feedback we get through the Microsoft Customer Experience Improvement Program (CEIP).  Through these programs, hundreds of millions of customers help Microsoft improve upon the design, quality and features of our products and services. Participation in the CEIP is anonymous: when you sign up for the CEIP, information about how you use certain products is automatically sent to Microsoft, collected in the aggregate with CEIP data from other computers.  Microsoft doesn’t use your collected CEIP data for any product marketing or promotions. (More details are provided in the Customer Experience Improvement Program Privacy Policy.) 

According to the CEIP site…

CEIP collects information about how you use Microsoft programs and about some of the problems you encounter. Microsoft uses this information to improve the products and features you use most often and to help solve problems. Participation in the program is strictly voluntary, and the end results are software improvements to better meet your needs.

The Windows Server team uses the CEIP for their products, include Windows Server 2008.  The team uses CEIP to improve the product in the following ways:

  • Helps to discover and fix software bugs in the operating system more quickly.
  • Helps to prioritize future Windows Server products and interim releases.
  • Helps to understand our customer system configurations more clearly, allowing Windows Server product teams to more accurately reproduce customer environments in their labs.
  • Helps to determine industry trends in computer hardware.

As John Song notes on the Dynamics CRM team blog, the team gathers information on how our customers are using the customization tool and how much they are customizing the out-of-the-box CRM. 

CEIP“Through SQM/CEIP data, now we know that the Account is the most updated form in the CRM 3.0 (Well, that wasn’t a surprise for us, but the number of changes made was). A quarter of the CRM customers are adding good amount of new fields in the Account and other “main” forms.

It’s all about providing feedback to the products teams. 

Mauro Meanti on the WSYP Project[Update: you can see the WSYP video here on YouTube: https://youtu.be/D28FkfJiauk]

When I’m asked about how this data is used, I often point people to my post “TwC’s site on Product Reliability… and WSYP” that has has a link to the WSYP Project, looking at how we leverage customer feedback in near real-time to improve software quality. (You can find this and other clips on the TechNet UK Spotlight page.)

And yes, Mauro is a real Microsoft employee. ; )

You can take advantage of WER to investigate the most frequently reported software crashes, resolve the problems, and inform your customers of the fixes, establishing a strong feedback loop with your customers. 

 

Bookmark this on Delicious Bookmark and Share

Also available via http://bit.ly/AxnhyW 

Link: How Windows Error Reporting Helps Customers

Tags: Microsoft, Watson, customer feedback, WER, Windows Error Reporting, SQM, CEIP, Video.