1

2

3

Stock Info

NASDAQ: INTCDow Jones Industrial Average ComponentNASDAQ-100 ComponentS&P 500 Component

Industry Semiconductors

Founded July 18, 1968

Founder(s) Gordon Moore, Robert Noyce

Headquarters Santa Clara, California, United States

Products Microprocessors, SOCs, SSDs, Software, Bluetooth chipsets, flash memory, motherboard chipsets, network interface cards…

Revenue US$ 53.34 billion (2012)Operating income US$ 14.63 billion (2012)

Net income US$ 11.00 billion (2012)

Total assets US$ 84.35 billion (2012)

Total equity US$ 51.20 billion (2012)

Employees 104,700 (2012)

Website Intel.com

Intel Corporation

4

• 2,095 Full-time Employees, Interns, and Contingent Workers• Birthplace of Intel Atom Processor & Atom SoCs (2007)

• Ultra-low-power & low-cost devices for smartphones, tablets, netbooks, & embedded applications.

• Cost between $19 and $64

• Power consumption between 1.4 and 8.1 Watts

• Allows tablets as thin as 8.5 mm and 1.5 lbs in weight

• Provides up to 10 hours of local HD video playback

Intel Austin

Clover Trail(Targeting tablets/convertibles)Penwell, Medfield platform

(Targeting Smart Phones)

5

Digital Signage

Robotics

Digital SecuritySurveillance

Printers

TransportationTest & Measurement

NetworkAppliances

WirelessInfrastructure

Routing & Switching

EnterpriseVoIP

EnterpriseSecurity

IP Services

Military ATM MedicalImaging

GamingAerospace Kiosks

Point of SaleIndustrial PC Thin Client

In-VehicleInfotainment

Medical Portable

IP Cameras

Home Automation

Sensors ResidentialGateway

IP MediaPhones

FactoryAutomation

Energy& Utilities

Control

Atom is Everywhere:More than 30 Segments and 1,000’s of

CUSTOMERS

6

Speaker Intro

David R. Knightdavid.r.knight@intel.com

Home Site: Austin, Texas

Employed at Intel Corporation for 16 years• Austin Site IP & Asset Protection Manager (1 year)

• Operational Tools & Technologies Manager (5 years)– Microsoft SharePoint Server 2010– Microsoft Office SharePoint Server 2007

• Knowledge Manager, Information Architect (4 years)– Microsoft SharePoint 2003– Microsoft SharePoint Portal Server 2001

• Sr. Application Performance & Tuning Engineer (3 years)– Microsoft SharePoint Portal Server 2001

• Sr. Software Engineer in Server Firmware Division (3 years)

7

My SharePoint Environment

• Intel has 3 isolated geographic SharePoint farms

• Intel’s business groups are separate P&L orgs

• I am not in the Information Technology (IT) team

• Try to influence IT, but they are much bigger than me

• I do not have access to central admin

• Tens of thousands of discrete, isolated site collections

8

Image Source: http://littlefishinaverybigpond.blogspot.com/

9

Primary Use of Microsoft SharePoint

To Eliminate: Eliminate overhead, pointless approval loops, no-value added steps, manual status changes, manual update to routing during approvers vacation, etc.

To Automate: Automate business process, approval flows, award submissions, travel & housing requests, catering requests, performance indicators, etc.

To Liberate: Liberate our employees from bureaucracy, overhead, and minutia. Free employee minds to focus on delivering amazing products & services.

10

Some Best Practices…

1. Eliminate Waste, Automate Processes, and Liberate People and ‘in’ boxes with InfoPath, Workflows, and a “LEAN” Mindset

2. Separate Project Sites from Organizational Sites

3. Remove Access Entitlement From SharePoint

4. Separate Environments for Standard and Extreme Power Users

5. Turn on Useful Features

6. Enable ERM

Detour: What didn’t work

7. Follow the Traffic

11

Best Practice #1 : Eliminate, Automate & Liberate with InfoPath, Workflows, and a “Lean” Mindset

12

Best Practice #1 : Eliminate, Automate & Liberate with InfoPath, Workflows, and a “Lean” Mindset

13

Best Practice #2 : Separate Project Sites from Organizational Sites• Organizational Sites Contain Generalized Info

• Org Charts

• Missions

• Strategic Objectives

• Operational Updates

• Awards

• Project Sites have Info Critical to Develop a Product/Service

• Architecture Diagrams

• Test Plans

• Benchmarks

• Project Indicators

• Project plans

• Test programs

• Diagrams

• Code

OPEN ACCESS

RESTRICTED ACCESS

Most members work for same management

team

Most members work in different groups,

divisions, and teams

14

Best Practice #2 : Separate Project Sites from Organizational Sites

Organizational Site, Customized, Branded, etc.

Project Site Out-of-Box

15

Best Practice #3 : Remove Access Entitlement From SharePoint

Permissions Tool:• Ensures Training Compliance• Checks for Control Country • Sets Expirations• Creates Audit Trail• Moves approval to content

owners vs. site/doclib owners

16

Best Practice #4 : Separate Environments for Standard and Extreme Power Users

http://sharepoint.amr.ith.intel.com/sites/....• Standard environment for 80% of employees

• No access to modify master or layout pages

• Active scripting in CEWP or WIKI pages blocked

• No Visual Studio Workflows allowed

• Minimal availability to change look/feel or branding of site

• Allows for IT to do “Sunrise Migrations” to future versions• SCOs will never have to migrate their own content to future versions

http://sp2010.amr.ith.intel.com/sites/....• 20% of employees are super users or require sites with high customization in branding.

• Master and Layout pages can be edited on the local site collection

• Visual Studio used sparingly

• Active scripting allowed

• SCOs must migrate their content, code, and recreate branding efforts on future versions of SharePoint

• Tradeoff of providing high flexibly to SCOs vs easy migration

17

Best Practice #5 : Turn on Useful Features

18

Best Practice #6 : Enable ERM…

19

Detour: What Didn’t Work…

Using SharePoint as the only toolfor EVERYTHING

• Collaboration• File Share• WIKI• Discussion Board

• Surveys• Expert Finder• Development Opportunity Tool

• Mentorship Tool• Media Library• Etc…

20

Practice #7: Follow the Traffic

• Although SharePoint has wikis and discussions boards and lots of other stuff, you may not want to use them.

• We have massive adoption to SecureWIKI (Internal name for 3rd Party Software) and PlanetBlue (Internal Name for 3rd Party Software)

• Link from SharePoint to SecureWIKI or PlanetBlue, rather than try to pull people to your SharePoint’s WIKIs and Discussions Boards

• People from a project website click on discussion link and leave SharePoint

• WIKIs have links to files that are stored on SharePoint

*Trademarks, names and/or brands are the property of the cited companies

21

22