• State of California Email Strategy is Best Practice

    April 4th, 2011 by admin Categories: Blogs Tags: , , , , , , , , ,

    SacBee’s Jack Chang has a story today about the state’s email strategy. “State streamlining its email system: Some ask, is it necessary?”

    Considering all the more obvious computer project implementation problems at the State of California, file this under ho-hum.

    And for those who disagree, especially the commenters in the SacBee story, consider this. In 2009, the state had 130 siloed email systems running on at least three different platforms, representing 185,000 mailboxes across the Executive Branch alone. This means literally hundreds of different email system administrators and patchwork security protocols; separate archiving, retrieval, eDiscovery and storage requirements, and so on. Different + Separate = Expensive + Unsecure.

    The State of California is a Fortune 10 sized company. Hell, show me even a Fortune 100 company that would even consider having multiple email systems and I’ll take it all back.

    Sure, you might find examples of ostensibly cheaper, individual solutions for email; however, when these individual solutions become the rule, these total costs for the organization and the security risks become unsustainable.

    The State of California’s enterprise approach is best practices. All the whining is from people who don’t like the new consolidation direction and having to follow orders.

    Welcome to a strong, centralized CIO governance model.

    1. Shawn says:

      If history is any indicator of how this project will end, it will end in tears and state workers (who have no part in the decision process) will end up saddling with the blame of the project. Far too much of the state’s information is treated as sensitive or confidential and can not be used on a 3rd party server. Then there will be rules associated with which accounts can talk to others when dealing with inter-agency or department affairs. This doesn’t even begin to account for any homebrew (in house programming) dealing with specific software to automate various projects and send them using the existing mediums that can also be linked to team based sites.

      This solution can work for some areas and departments, but it is not a universal solution and will not achieve the projected savings. This is in part why there are so many systems in place currently and honestly was supposed to be the reason for forming the ocio to help streamline those processes where it could work rather than becoming an administrated arm for pet IT projects to funnel into prefered companies ala RDA.

    2. Anonymous says:

      Wow, then show us the FSR that was done for consolidated email.

    3. Annonymous says:

      Yes Consolidated services can save money in the long run if done correctly. They should have strengthen OTech’s email system first before consolidating other agencie’s email systems into it. Otech has resource and budgetary problems. Their email system goes down all the time without notice. Before our department’s consolidation we had very little to no down time. We had two IT staff taking care of our Exchange server and it was a reliable service. Now we pay an emormous amount of money to Otech for a service that is down way too many times.

    Anonymous Commenting is Welcome. To have your name or website appear with your comment, fill out the form below. All Comments are moderated to prevent spam. Thanks for joining in the discussion!