SAR Enterprises Syed Ahmed Abdullah Alsubaiei Ramakrishna G

Agenda  Corporate Overview  Outline the business needs for the System Implementation  Define the Business Case(s)  Brief a high level functionality  Outline assumptions, risks and alternatives

Corporate Overview  SAR enterprises is a local construction and engineering firm emphasizing on the Houston Oil & Gas Industry  Customers include ExxonMobil, Chevron, Murphy Oil, ConocoPhillips and Shell Oil (refer to the Case Studies on our website)  We have over 250 employees working with clients onshore and offshore  Services include civil infrastructure, contracting services, and business ventures including superior planning, construction, operations & maintenance and logistic services expertise.  Project Sponsor: Mohammed Rob PMP, Vice President Professional Services

Business Need  The overall purpose of the project is the implementation of an Enterprise Content Management solution to meet the shift from a paper based to an electronic record-keeping environment.  SAR has papers records since 1990 which includes documents related to Accounting, Construction drawings & diagrams, Environment, Health & Safety, Human Resources, Legal, Marketing, Payroll, Technology development.  Company has decided to implement EMC Documentum as their ECRM and purchased required softwares and licenses already.

Business Requirement  Manage the large quantity of computer based information stored in personal computers, boxes and network servers in accordance with compliance requirements  Provide company-wide access to documents (with appropriate security)  Centralized Electronic Archives - integrated approach for the capture, maintenance, storage, access, disposition and preservation of electronic records  A framework that can be used across the company  Scan certain physical records (such as civil drawings & diagrams and legal documents)  Assign Retention to every object in the system.

Functional Requirements  Reporting - The system shall maintain a full history of modifications to a record (active, inactive, retired) for reporting purposes. The full history shall retain all record properties fields and their values  Versioning - The system shall maintain and display a versioning system (display version) that follows the business model for versioning a document.  Search - The system shall provide the ability to search for records based on the absence or presence of an association to another record of a specific record type.

Non-functional Requirements  Capacity: With the introduction of electronic records, we have expanded the range of storing data.  Availability: Now the content is accessible 24/7  Extensibility: System can be expanded to support new functionality

Business Value  Tangible Cut Iron Mountain and maintenance costs: $2.1M per annum Utilize purchase of EMC Documentum software worth $300,000  Intangible All records will be categorized with respect to the object model hierarchy (Departments & Subdivisions) which would classify them accordingly.

Assumptions/Risks/Issues  Assumption System is being developed on the assumption all 250 users would be using the system All software and licenses have already been purchased to kickoff this assignment.  Issue Remote dedicated satellite link would be required for offshore end-users. Additional resources (contractors) will be required for inventory and scanning of physical records.  Risk PM suggested to rollout before the end of this fiscal year which is not a likely case

We are done!  Questions?  Suggestion??