1. 1 Summary of Migration Process HalWorld to Employee Central October 2003

2. 2 Agenda Portal, CMS, Taxonomy Interwise Presentations – Questions Migration Methodology –Preparation –Kickoff –Content Inventory –Solution Concept –Pre-Launch Communication Planning and Change Management

3. 3 Portal Development (Portal, CMS, Taxonomy)

4. 4 Halliburton’s key business drivers link directly to Knowledge Central’s benefits Provide employee self-service for key functions including HR, learning, procurement Eliminate duplication in many aspects of the Halliburton’s business Drive productivity increases through automation of effort in formerly manual business processes (application integration) Internal Focus Profit Management Cost Reduction Process Improvement Benefits Share global standards and processes that support suppliers and customers more effectively Improve access to HSE materials to demonstrate global leadership in this area More easily share new technologies and processes to capture emerging markets Premier Service Quality Customer Satisfaction Competitive Differentiation Customer Focus Benefit s Shareholder Value International Growth Market Share Gains Financial Focus Leverage internal and external resources to identify new and improved business opportunities in emerging markets worldwide Allow expansion to customer facing processes to drive revenue and redesign for growth Benefit s Share knowledge and “best practices” company-wide Provide enhanced, role-based access to information needed for employees to do their jobs effectively Support for all aspects of the employee-employee and employee- business relationships Foster Innovation Employee Accountability Employee Satisfaction Accelerate Learning Employee Focus Benefits ESG Strategy Knowledge Central Benefits

5. 5 Current Intranet ChallengesDesired Results – end of 2004 Organization Disparate PSL and support functions No alignment with PSLs Country Independence Limited measurement (not value-based) Organization Consolidated global IT standards $ Standardized alignment for all PSLs P Global standards for all countries $ Active, value-based measurement P Processes Cumbersome No internal processes for content Management Not user-friendly Processes Streamlined and simple P Single-source content managed and controlled by the business P Easy to learn and use for all P Information Technology Non-standard applications & architecture 400+ Site Administrators 250+ Content Owners 320+ sites 78 GB of files/content Age of files/content: – 0-12 mos: 36% – 1-2 yrs: 22% – 2-3 yrs: 18% – 3+ yrs: 24% Information Technology ESG-wide applications & architecture $ 60+ Portal Managers $ 90+ Content Owners $ 60+ sites $ Greatly reduced amount of files/content $ Age of files/content: P – 0-12 mos: 75% – 1-2 yrs: 25% – 2-3 yrs: 0% – 3+ yrs: 0% Primary Result: $ = Cost Savings P = Productivity Gains Knowledge Central will generate significant value in comparison to HalWorld Transformational Efforts 20042003

6. 6 Employee Central Defined 1)It integrates applications, functions, content, and users. 2)It provides access to information employees need anywhere, anytime. 3)It is personalized to the role, location, and organization of its user, which helps strengthen and automate workflows. Employee Central has three key attributes

7. 7 Employee Central My WorkplaceCommunitiesWorkGroupsOrganizations Description Individually customized pages integrating tools, applications and information needed to perform one’s daily job. Commonly used portlets for specific job roles will be bundled together and made available for ease of further personalization. Groups of employees who address urgent business needs by collaborating more effectively. Communities are managed formally and require the establishment of roles, processes and tools. They also use rigorous metrics to determine their progress. Groups of employees within a department or working on a specific project needing an online space to share documents and tools, with some collaboration. Workgroups are set up in a self-service fashion since they use a standard set of portlets. Provides information and services to all ESG employees, inside and outside any organization; will replace HalWorld sites. Audience IndividualsPeople across organization with common needs/ purpose Intra-departmental/ organizational or project based or ad hoc People outside of the department / organization Open or Closed N/AOpen (preferred) or Closed Open or Closed (preferred) Open Environment Details Personalized by role, organization, location Collaborative Formally facilitated by full-time moderator(s) Collaborative Open discussion forums without a moderator Informational Access to support services Expected Participation One per defined role<100In the 100sOne per internal Halliburton group Examples PE Service Coordinator BD Account Lead OTC Community Logging Community IT ESG Technology Management IT Services HSE

8. 8 Sub-Portals Current Sub-portals – (under Knowledge Central) –Employee Central –Executive Central –Customer Central –Supplier Central –Students –Technical Consultants –Default / Guest identifies the sub-portal

9. 9 CMS and the Portal – Employee Central CMS Published Version Portal DocumentTemplate Workflow (tag, approve, publish) Content Repository (versions)

10. 10 CMS Metadata (data about data) General Title Description Content Type Access Control (Security) Content Administrator Content Author Content Owner Site Administrator Legal Approver Subjects Location Organization E&P Lifecycle Business Process HSE Equipment & Materials Product Groups Tools & Components Oil, Gas, Chemicals and Lubricants Customer Challenges Other Materials & Equipment Administrative Data Launch Date Review Date Expiration Date New Technology Commercialization Start Date Allow this file to be indexed for search? Taxonomy Suggestions Taxonomy

11. 11 Taxonomy (categories) (w/definitions) Content Type*: These are classifications of information that help filter the type of content. For example, sales and marketing material is typically not to the same technical level as a procedure or policy would be. Security*: Identifying access to content – restricted, confidential, internal use, public access. Location*: These are “places on earth” that are generally well known to everyone. Although we may think of NWA's as a place, they are really just a collection of Locations. Organization*: A collection of people organized in PSL & sub PSL groupings. Our customers do not generally care about our organization. E & P Lifecycle: This is reflective of a normal working timeline since it represents the serial sequence of events in the life of a well. Many documents relate to several of the lifecycle categories. Business Process: This relates the document to the HMS system. Many documents relate to several Business Process categories but the majority of the documents are under categories called “Develop Solutions” and "Execute and maintain Business.” HSE: Categories of Health Safety & Environment. Note that the HSE facet actually contains HSE categories of information. Product Groups: These are high-level Services or high-level (large category) Products that a customer understands. Sub Categories of Product Groups are smaller groupings of services or Products. For example, “Drill Bits” is a product group and “PDC bits” is a subcategory of Drill Bits. Tools & Components: These are the downhole tools that are used to perform services or make up products. Note that a 6" bit is a tool. Oil, Gas, Chemicals & Lubricants: These are the chemicals, additives, etc that make up the chemical services we offer. Challenges: This is the root problem that a customer faces. Anything that is a service in our price book is not challenge. Challenges are generally reservoir- and environment-related. Other Materials & Equipment: These are basic materials like cement & salt; as well as items that are purchased from others like pumps, trucks and cables. Most of the surface equipment falls in this category. * = Required Fields

12. 12 Components of Knowledge Central Collaboration Doc Sharing Threaded Discussions Content - CMS Web Content Mgmt Doc Mgmt Info Retrieval Search Taxo- nomy Applications…Sub-Portals… Portal Communities Role-based / Personalization / Branding OrganizationsWorkgroups Security / Administration / Tracking = in progress Identity Mgmt Single Sign-on App Sharing Instant Messaging Digital Asset Mgmt Expert Locator Business Process Automation Multichan. Access Wireless Access (e.g. PDA) Mobile Access (on/offline) = future My Workplace / Pages User Profiling

13. 13 Web Communications Involvement

14. 14 Stakeholders Strategic Sponsors Steering Committee Core TeamSite Leadership Extended Team John Gibson Art Huffman Senior ESG VPs Shawn LeBlanc Michael Behounek Mary Rose Martinez / Marcia Trimble Jill Cude Jon Muska Brandon Lackey Global HR Representative Mary Rose Martinez / Marcia Trimble Jon Muska Jim Schmitzer Project Resources Portal Managers Content Owners Communication Planners PSL-based Marketing Managers Country & PSL Communication/IT Managers Country (Regional) VPs HR Development (Learning) Operational Sponsors Operational VPs Global Directors

15. 15 Project Structure Strategic Sponsors Operational Sponsors Strategic Sponsors Operational Sponsors Strategic Direction Conceptual Representation Extended Team Site Leader- ship Core Team Content Owners Portal Managers Authors Approvers Users Site-Specific Stakeholders User Requirements Comm Plan Best Practice Training Roles Streamlined Measurement Cultural Change Tactical Implement- ation Operational Goals & Objectives Employee Central CMS *** Taxonomy *** Portal Steering Committee Core Team

16. 16 Project Resources RoleSelf-Service ProjectFull-Service Project Business AnalystWeb CommunicationsWeb Communications / Information Technology Change Management Communications Training Web Communications Portal/CMS Administration Information Technology Developmentn/aInformation Technology TaxonomyKnowledge Management

17. 17 Search Support Structure Urgency LevelInternal Tier IRTO Help Desk Tier IIGeneral / Content Support (Web Communications) Tier IIITechnical Support (IT Strategic Systems Support) Tier IVTechnical Support (IT Search Team) LevelExampleSLAEscalation NormalCan not find / open document 24 hoursTier I / II / III UrgentSearch is down4 hoursTier III / IV Note: Urgency level is determined by Tier I Support. SLA is from the time a ticket is opened to the time it is closed (in business days).

18. 18 Portal Support Structure Urgency LevelSupport Tier IRTO Help Desk Tier IIGeneral (FHALPORTAL and FHOUMYHALLIBURTON) Communities (Portal Managers) Organizations (Web Communications Beginning Q2 2004 ) Tier IIITechnical Support (IT Portal Team) LevelExampleSLAEscalation NormalContent questions, training requests 7 daysTier I / II CriticalLogin problems, portlet (gadget) errors 24 hoursTier II UrgentPortal is down4 hoursTier II / III Note: Urgency level is determined by Tier I Support. SLA is from the time a ticket is opened to the time it is closed (in business days).

19. 19 CMS Support Structure Urgency LevelInternal Tier IRTO Help Desk Beginning Q4 2003 Tier IIGeneral Support (Portal Managers, Web Communications Beginning Q2 2004 ) Tier IIITechnical Support (IT CMS Team) LevelExampleSLAEscalation Normal“How do I” questions7 DaysTier I / II CriticalMetaTagger timed out24 HoursTier II / III UrgentTeamSite is down4 HoursTier III Note: Urgency level is determined by Tier I Support. SLA is from the time a ticket is opened to the time it is closed (in business days).

20. 20 Project Offering

21. 21 Roles and Responsibilities – Business Analyst and Change/Communication/Training Role Drive for a shared project vision. Ensure that the customer and project team share a common vision of the project Help develop and document the project vision and scope Help develop a project approach, schedule and plan Help identify and manage risk throughout the course of the project Help the departments develop, and document the business case Conduct user needs, usability analyses or surveys Evangelize on Plumtree Portal and CMS features and capabilities Empower business users/clients with Portal and CMS knowledge Communicate and recommend Portal and CMS solutions where fit exists Develop and document the client’s business requirements Drive feature identification and prioritization Communicate the client/customer’s needs and interests to the project team Ensure the project team understands client/customer quality requirements Set and maintain Quality Assurance standards for the project and solution and ensure that they are being met Communicate and Document the team’s solution concept and recommendations to the client/customer Write the functional specification with input from other team leaders Define how the product will interoperate with external software systems and components Implement change control over the functional specification document Ensure that any solution the team develops solves the client/customer’s business problem Ensure client/customer satisfaction Manage client/customer expectations, including associated tradeoffs between features/scope, resources, and schedule/timeframes Develop software test plans, specifications, and test cases Help create the training deliverables Help identify change management issues by assessing organization readiness and degree of business process change Understand all portal and content management benefits and standards at Halliburton Understand Halliburton’s Interwoven TeamSite interfaces, including WebDesk, WebDesk Pro, Metatagger, and Team Portal Understand all aspects of CMS, such as templates, workflows, roles, metadata, and all elements of Halliburton’s content management lifecycle Understand and support Halliburton’s Plumtree portal, CMS and taxonomy governance and implementation standards

22. 22 Project Offering Full-Service Portal/CMS solution Need comprehensive content and UI evaluation Solicit user feedback Requires development effort Requires interfaces with other applications Dedicated project resources Self-Service Portal/CMS solution Wholly owned content Use any existing user feedback Use defined model for Organization portals Use existing components No interfaces with other systems/applications Shared project resources

23. 23 Project Sequence – Training, Workshops, Hands-on Sessions Overall Governance -- Completed/Ongoing Portal II Communication Planning (CP)Communication Planning (CP) CP Workshop Create CP Strategy CP Action Planning CP Execution Taxon- omy I CMS IPortal I Governance Overview I Training & Workshop Activities Format Set-up Content Migration Pre-Launch Slides Interwise Live Mtg. CBT CBT CBT CMS IV CMS V Taxo III Hands-on Working Sessions Taxo II CMS III CMS II KC Over- view WS WS WS WS WS WS WS Delivery WS Solution Concept Content Inventory Preparation Project Timeline Kickoff Interwise and I-Learn ---------- Slide Decks ---------- ------- Slide Decks ------- Key Deliverables 1 Project Proposal 2 Discovery – User Needs (survey) 3 Vision and Scope 4 Communication Plan 5 Content Inventory 6 Taxonomy Needs 7 Functional Specifications 8 Test Plan 9 Communication Deliverables Key Deliverables 123498765

24. 24 Training Sessions Type 1: Portal 5.0 Training – Interwise – PowerPoint (available at Portal Training and Policies site) 1.Governance Overview – 24:00 2.Employee Central Overview – 28:00 3.Portal Management – 7:30 4.Portal (5.0) Overview – 24:00 5.CMS I – Content Management System – 19:00 6.Taxonomy I – 16:00 Type 2: Live Portal 5.0 Training – Interwise – Application Sharing (available at Portal Training and Policies site) 1.Employee Central Overview – 11:00 2.Managing My Workplace – 13:00 3.Communities, Workgroups, Organizations – 6:30 4.Managing Communities, Workgroups, and Organizations – 15:00 5.Project Overview – 10:00 6.Managing Projects – 9:00

25. 25 Agenda – CMS II Reminder on CM Definition What is a content inventory? What is the purpose of doing a content inventory? Column descriptions Identify existing folder structure with a view to creating a new folder structure Exercise: Content Cleanup – identify obsolete content. The criteria to consider (no links to the content, older than x, outdated by x, superseded by x, etc.)

26. 26 Agenda – Taxonomy II Review Taxonomy Definition and Benefits Discuss Required Facets (categories) Review Content Inventory Results Taxonomy Matrix Discuss how Taxonomy Affects Documents on the Portal (Search and Document Directory – Folders)

27. 27 Agenda – CMS III Reminder: CM definition (and content types) Review content lifecycle Creating content –Templates –Identify appropriate content for templates –Import content –Review standards & guidelines Template features Available templates

28. 28 AGENDA – Portal II Employee Central – Defined Different types of portal pages (My Workplace, Community, Organization, Workgroup) Portlets, Personalization, Roles Portal Governance Reminders Interwise Sessions – see Portal Training and Policies page for portal training Adding a Community Community Overview Project Overview Creating a Project/Project Leader Role Adding additional Leaders to a Project Adding Guests and Members Editing Permissions Announcements Calendar Tasks Documents Discussions

29. 29 Agenda – CMS IV Reminder: CM definition (and content types) Review content lifecycle CMS Roles Identify Participants – Job Descriptions –Portal Manager –Content Owner Workflow Concepts Review current available workflows Identify content types with distinct workflows

30. 30 Agenda – CMS V: Folders, Metadata, & Security Criteria for New Folders Create New Folder Structure Security – Groups/ACLs

31. 31 Agenda – Taxonomy III Review all other Facets (categories) Discuss Matrix Identifying all Applicable Facets Review Customized Taxonomy Guide Review Metadata Review Metatagger Interface (required fields, tabs, etc)

32. 32 Communication Planning Approach – Key Steps For XYZ Project, the key steps driving change center around the following activities: Time Identify Stakeholders Communication Strategy Stakeholder Responsibilities Final Action Planning Complexity Change Management For XYZ Project Four Phases: Preparation Support Review Delivery Execution Iteration & Follow- up

33. 33 Project Sequence – Training, Workshops, Hands-on Sessions Overall Governance -- Completed/Ongoing Portal II Communication Planning (CP)Communication Planning (CP) CP Workshop Create CP Strategy CP Action Planning CP Execution Taxon- omy I CMS IPortal I Governance Overview I Training & Workshop Activities Format Set-up Content Migration Pre-Launch Slides Interwise Live Mtg. CBT CBT CBT CMS IV CMS V Taxo III Hands-on Working Sessions Taxo II CMS III CMS II KC Over- view WS WS WS WS WS WS WS Delivery WS Solution Concept Content Inventory Preparation Project Timeline Kickoff Interwise and I-Learn ---------- Slide Decks ---------- ------- Slide Decks ------- Key Deliverables 1 Project Proposal 2 Discovery – User Needs (survey) 3 Vision and Scope 4 Communication Plan 5 Content Inventory 6 Taxonomy Needs 7 Functional Specifications 8 Test Plan 9 Communication Deliverables Key Deliverables 123498765

34. 34 CMS Working Session – Sample Agenda TimeItemFacilitation 8:30 – 8:35Kick-off and Safety Moment by Brandon Lackey, Project SponsorBrandon Lackey 8:35 – 9:00Introductions and Expectation Setting, Ice Breaker, and Parking Lot (share and review training manual) Barbara 9:00 – 10:00Using Interwoven (from perspectives of Content Administrators and Content Owners)  Benefits and Challenges of CMS (Interwoven)  Review, Tag, Approve – your role  Overcoming Challenges and Emphasizing Benefits  Content Overview Page (Brandon) Brandon, Melissa, Jan, Barbara 10:00 – 10:15BREAK--- 10:15 – 11:00Taxonomy Review  Facets (including new – Location & Organization)  Metatagger  Maintenance Ron Daniel, David Smith 11:00-11:30Facet Exercise with your taxonomy guide – highlight the tags you are likely to be using David Smith 11:30 – 12:45LUNCH (Ice Breaker Results)--- 12:45 – 3:00Working Session: Content Administrators work w/emails from Jan & Melissa – focus:  Live Review of TeamSite  Review  Tag (Metatagger and Dates)  Approve (or reject documents) and Show how documents pushed to Portal Jan, Melissa, Barbara 3:00 – 3:15BREAK--- 3:15 – 4:30Mass Tagging, Review of current CMS tags Review Taxonomy Challenge 2003 Jan, Melissa, Barbara 4:30 – 5:00Closing Comments  Questions  Review action items (parking lot) and Expectations  Next steps Brandon, Barbara