1 / 10

Micron and SharePoint 2013 for Document Management

Micron and SharePoint 2013 for Document Management. Chuck Steffens Knowledge Management Service Manager Micron Technology, Inc. About Chuck…. At Micron nearly 23 years, ~ 18 in a variety of IT roles

karlyn
Télécharger la présentation

Micron and SharePoint 2013 for Document Management

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Micron and SharePoint 2013for Document Management Chuck SteffensKnowledge Management Service ManagerMicron Technology, Inc.

  2. About Chuck… • At Micron nearly 23 years, ~18 in a variety of IT roles • Knowledge Management Service Manager for the past five years, responsible for content management and business process solutions

  3. Disclaimer • Required by my Legal and Procurement teams… • The following slides are the opinion of Chuck Steffens, a Micron team member, and do not necessarily represent the views of Micron Technology, Inc. and should not be viewed as an endorsement by Micron of any particular service or solution…

  4. Topics • Background and why did we skip 2010? • Why did 2013 meet our needs for a document management system • Significant Areas of Concern

  5. Background and why did we skip 2010? • SharePoint 2010 planning was well underway when we had to put the project on hold due to resource availability • In Sept 2011, we were still on track for a mid- to late 2012 upgrade • Then SharePoint 2013 was announced, and other projects aligned to that feature set • So rather than impact the business with two back to back upgrades, we skipped and focused on SharePoint 2013 • Atypical for Micron, we prefer to wait for upgrades

  6. Why did 2013 meet our needs? • Document hold/e-Discovery • Reusable and more powerful workflow (e.g. workflow 1.0) • Documents have a unique document ID • Cost barrier removed

  7. Significant Areas of Concern • Significant architectural changes, even from SP 2010 plans • Virtualization • Opted for virtualized farms (except for dbs); easier to scale • Consolidation • Dropping from 11 prod farms to 6; 2 enterprise, 2 site specific, 2 function specific • Storage changes to further reduce costs • Used Premier Support early in process to validate plans • Hired Microsoft Consulting to assist with some aspects • Sometimes conflicting information

  8. Significant Areas of Concern • Business Intelligence customer impacts • PowerView, PowerPivot, plans to expand Excel Services usage • PerformancePoint dashboards and Report Center reports needed to be republished • Hired partner to assist with conversion

  9. Significant Areas of Concern • SharePoint customer impacts • Office 2003 Web Components widely used • Meeting Workspace template • Search and security • Migration Tools to minimize upgrade impact

More Related