Appendix A: REAL TIME OPTIMIZATION WORKFLOWS IN PRODUCTION OPERATIONS AND THEIR IMPACT ON IT INTEGRATION - PROJECT CHARTER
I. Scope
The Real Time Optimization Workflows in Production Operations and their impact on IT Integration project is established to:
• Convert the workshop content to a standard use case format reflecting one of the three workflows that were elaborated:
1. Gas Lift Optimization
2. Multiple Low Volume Well Field Optimization
3. Joint Venture Production Reporting
• Initially select and produce Project Charter deliverables of one of the three cases using a University of Houston - College of Technology team of 2 students – Contingent upon success, additional cases will be added
• Review the results from the workshop with subject matter experts (SMEs) at Oil & Gas companies
• Suggest improvements to the use case based on feedback from the SMEs
• When possible, analyze and document the business case in terms of the economic impact of the workflow in the use case
• Consider the use of a semantic web (ontology) to capture the workflows and use cases as the start of a library for Oil & Gas workflows
II. Benefits
The benefits are expected to be:
SPE OI and RTO TIG benefits:
• Finalize and publish the results from the Digital Energy workshop
• Establish a library of workflows and use cases for Oil & Gas
• Improve student awareness of Oil & Gas for future workforce development
UH College of Technology benefits:
• Improve student awareness of Oil & Gas
• Challenge students to think from a workflow perspective
• Establish contacts for the students in Oil & Gas companies
• Publish and present research and thesis papers related to real time optimization and its impact on IT integration
• Increase the Oil & Gas industry’s awareness of the College of Technology and its Petroleum Technology Initiative
III. Measurable Objectives
• Develop a standard use case format to document the workflow
• Convert the workshop content to the standard use case format reflecting the selected workflow
• Review use case documentation with the project steering committee
• Review the results from the workshop with SMEs at Oil & Gas companies
• Further elaborate and document the selected use case based on feedback from the SMEs
• Analyze the business case in terms of the economic impact of the workflow
• Evaluate the use of a semantic web (ontology) to capture the workflow and use case as the start of a library for Oil & Gas workflows
• Publish the results to the SPE OI teamsite and in other SPE venues
IV. Deliverables
Deliverable | Description |
---|---|
Standard use case format | A template to use for documenting the workflow, potentially useful for programmability and support of semantic web applications. |
Workshop results document | A document based on the “standard use case format” that captures the content from the workshop. Meeting Notes Notes from the reviews with the SMEs and site visits. |
Final Workflow documentation | A document that captures the workflow in some detail based on the workshop and SME input. Where possible, this will include documentation of the business case in terms of the economic impact of the workflow. |
Semantic Web evaluation document | A document that describes the results of the semantic web evaluation. If the recommendation is to use a semantic web, this document should include steps to implement the semantic web. |
Published documents on the SPE OI teamsite | Post all documentation, draft and final versions, to the SPE OI team site and share results through appropriate outlets. |
V. Workplan and Schedule
Calendar Weeks | Deliverable | Tasks |
---|---|---|
1 | Kick-off | Meeting with workshop facilitators to initiate the development of the use case format. |
2 | Standard use case format | Research use cases in other similar industries and applications. Define general sections, scopes, general outline, e.g. one based on UML has been provided during the workshop. Keep the purpose aligned with programmability and support of semantic web applications. |
1 | Workshop results document | Prepare a document based on the standard use case format that captures the content from the workshop. Utilize this activity to fill in the use case and create a background or framework for future workflow research. Create questions for SMEs. |
8 - 10 | Meeting Notes | Identify SMEs (for both workflow and business case) who are willing to spend time with students. Schedule appointments with SMEs. Conduct workflow reviews and site visits (whenever possible) with the SMEs. |
same as above | Final Workflow documentation | Prepare a document that captures the workflow in some detail based on the workshop and SME input. This will include analyzing the business case in terms of the economic impact of the workflow where possible. |
N/A | Semantic Web evaluation | A document that describes the results of the semantic web evaluation. If the recommendation is to use a semantic web, this document should include steps to implement the semantic web. Research vendors on semantic web related tools. |
1 | Review workflows | Create value by analysis of discrepancies and inefficiencies in the workflows. |
Ongoing | Publish documents on the SPE OI team site | Post all documentation, draft and final versions, to the SPE OI team site: possible venues can be wiki pages, white papers, chapter meeting presentations, SPE conference presentations, etc. |
VI. Budget
[Apply to SPE for budget approval to cover the costs of the students.]
2 students from the Network Communications Master’s program for 1 semester (4.5 months with 2 students = 9 months) $11,168 (see the attached calculator from UH for the cost)
$1000 for one conference presentation attendance.
VII. Out of Scope/Out of Bounds
• Semantic web evaluation will be out of scope until an expert can be found for input
• One workflow will be chosen for this first 4.5 months phase according to the criteria of importance, accessibility, and scope
VIII. Constraints
Site visits with SMEs may have safety, security, confidentiality, liability, and permission constraints for the students.
IX. Organization
Team Member | Functional Area | Role(s) and Responsibility(ies) |
---|---|---|
Student 1 & 2 | Team Member | Execute assigned tasks |
Dr. Deniz Gurkan | Advisor/Steering Team | Support project |
Dr. Jami Kovach | Project Manager | Manage overall project and student assignments |
Jack Christiansen | Advisor - Steering Team | Support project |
Yanni Charalambous | Steering Team | Support project and help with access to SMEs |
Kemal Farid | Steering Team | Support project and help with access to SMEs |
X. Team Contact List
Deniz Gurkan dgurkan @ uh . edu
Jack Christiansen jhchristiansen @ uh . edu
Jami Kovach jvkovach @ uh . edu
XI. Other Communication Information
Status Meetings
Meeting Day & Time
Person Responsible for Calling / Cancelling Meeting
Person Responsible for Creating Agenda
Person Responsible for Taking/Recording/Distributing Minutes
Issues Log
Document Location
Person Responsible for Documenting Issues
Person Responsible for Approving Issues
Person Responsible for Following-Up on Issues
Project Web Site
http://communities.spe.org/TechSections/IT/ITOI/default.aspx
Next Appendix: B - SME Meeting Minutes