Document & Records Management (DRM)

1. Document & Records Management (DRM) Statement of Work Information Changes in Red

2. Scope • Scope of the development phase to pilot includes the following: • Migration/Conversion of content for selected pilots • Physical to Electronic • Electronic to Electronic • Updated taxonomy addressing content for all the pilots • Document Destruction • Agree on Disposition Table • DRM Enterprise & Department specific procedures, training, and structured communications to all employees • Development of the following DRM tools: • 1) New taxonomy implemented in Documentum • 2) Entry and Access mechanism implemented in Documentum • 3) Structured and unstructured search • 4) Interface with Tobin for property population • Following are within the scope of the overall DRM project, but not part of the SLB scope: • Modifications to InputAccel to interface with the new DCTM system • Modifications to Cuadra, Houston & Calgary for RM functionality, if needed • Records Retention Schedule definition, population, and implementation • Department level content conversion and data quality clean-up • Interface with SharePoint, Primavera • Modifications to Uxbridge DCTM application • VMWare Implementation

3. Scope for Dept:Buckets are 1 . Document, 2. Classification/Taxonomy, 3. Technology 4. Workflow • Data migration new classification and clean up • Manual clean up & decision (is this document needed in the future?), current files • Backfile conversion • Taxonomy Mapping • B. Documents destroyed that are approved for destruction • C. Physical documents relocated to authorized DRM location as needed • D. Documents in Shared network drives and other unmanaged storage (C drives, CDs) • E. Process/Technology use case (Touch Points) • Interfaces with existing departmental software (Tobin, Excalibur) • User interaction with other software • F. Disposition of documents agreed to and documented • Originator • Scanning required? • Storage Location • Physical Storage • Taxonomy mapping (existing to future) • Backfile size, scope, managed by department or separate project

4. Scope DRM User Interface (Entry/Access) DRM Scope Rules Engine Other Enterprise Apps SharePoint Primavera Tobin InputAccel WINS Excalibur Other DRM Apps Documentum Object Model Cuadra – Houston Cuadra – Calgary Taxonomy Structure Tool

5. Approach • Key elements of our approach include: • Early kick-off of departmental readiness activities • Departmental content assessment during development • Kick-off of pilots once the content, training, and tools are ready • Key benefits of this approach include: • Early implementation of a tool in a new department • Accepted design of taxonomy & tool for an asset team • Structured process to close down a file room

6. Development Approach Development Phase Pilot Phase Pilot 1 Content Readiness Pilot 3 Content Readiness Pilot 1 Roll-out Pilot 3 Roll-out Document Process Assessment Target State Definition Backfile Migration Plan Roll-out Process Document Process Assessment Target State Definition Backfile Migration Plan Roll-out Process Pilot 2 Content Readiness Pilot 2 Roll-out Pilot 4 Content Readiness Pilot 4 Roll-out Document Process Assessment Target State Definition Backfile Migration Plan Roll-out Process Document Process Assessment Target State Definition Backfile Migration Plan Roll-out Process Tools Development Tools Testing Pilot Roll-out Pilot Content Conversion Training & Communications Development Training Change Control Process

7. Approach W1 W2 W3 W4 W5 W6 W7 W8 W9 W10 W11 W12 W13 W14 Dept 1 (Land Admin) Content Readiness Dept 2 Content Readiness Validation Workshop DRM Priorities To-Be Design Dept 3 Content Readiness Pilot Plan Content Validation Final Design Ready Dept 4 Content Readiness Dept 1 Rules Population Rules Engine Development Dept 2 Rules Population Dept 3 Rules Population Dept 4 Rules Population User Interface Development DRM System Testing DCTM Object Model Dept 1 (Land Admin) DRM Process Dept 2 DRM Process (Includes Exiting Dept apps/processes) Decide on centralized or decentralized approach Dept 3 DRM Process Dept 4 DRM Process Training Development Change Control Process Development – Deployment Handbook Calgary DCTM Migration Content/taxonomy validation Uxbridge DCTM Modifications Content/taxonomy validation Retention Schedule Development and population

8. Deliverables • At the end of the development phase, following will be delivered to Anadarko: • Content mapped for the pilot groups • Updated taxonomy • DRM Procedures & Rules • Detailed Training Outline & Instructional Plan • DRM Website Established • Training Materials Developed • Structured All-Employee Communications for Deployment • UI (Entry/Access) Portlet Routines • Documentum - Modified to reflect new taxonomy • Documentum - Modified to use new UI Routines and Rules Engine • Taxonomy Maintenance Tool

9. Resources Department 1 Team 2.5 FTEs (SLB+APC core) Department 2 Team Content Readiness Development Pilot Content Assessment Taxonomy Business Rules Content Dept. Specific Process Dept. Specific Process Process Core Teams Deployment Rules Engine Testing Tech Comm Training Tool Development