Project
Team Proposal
Specification
Support
Purchase Order Process
TABLE OF CONTENTS
1. Proposed
Project Team / Study Name
5. Anticipated
Completion Date
6. Sponsoring
Member /Work Group/ Sub-Committee
1.
Proposed Project Team / Study Name
Project Name: Purchase Order Process
2.
Description
2.1 Purpose
Develop
business process guidelines governing the Purchase Order Process
2.2
Scope
Areas to be
addressed include:
·
Documents available in 3901:
o
OrderCreate – purpose, structure and sequence of line items
o
OrderResponse – purpose, structure, sequence of line items
o
OrderChange
o
OrderStatusRequest
o
OrderStatusResponse
·
Purchase Order vs. Service Order – what constitutes
each; how to address each from a process perspective
·
Materials vs. Complex Services
·
Detailed vs. Blanket vs. Limit
·
Routing – fields, routing definition, process to
handle incorrect routing information
·
Data elements and required information – do we have
the fields necessary to meet trading partner requirements
·
Attachments – how to manage
·
Clarify and agree definitions and terminology and
document in the PIDD
2.3
Goal
·
Determine what is supported according to
current business priorities in the industry
o
1. PO Submission and Receipt (including
technical acknowledgement)
o
2. PO Response (including technical
acknowledgement)
o
PO Change and PO Change Response (including
technical acknowledgement)
·
Update PIDD with Agreed terminology and
schema definitions
3. Initial Contributions
|
Document name |
Type of Document |
Document Source |
|
3901 OrderCreate |
XML |
PIDX |
|
3901 OrderResponse |
XML |
PIDX |
|
3901 OrderChange |
XML |
PIDX |
|
Data Dictionary |
|
PIDX |
4. Resource Requirements
To be determined as project
progresses. None anticipated at this time.
[Check each activity required.]
|
Minute taking |
|
|
Facilitation |
|
|
List other
activities |
|
[Fill-in the
anticipated time commitments of each of the activities in the table below. The
specification manager should help with these time estimates.]
|
Planned activity |
Number per month |
Number of months |
Duration (hrs) |
TPIDXl Time (hrs) |
|
Conference calls |
1 |
6 |
1 |
6 |
|
Face to face meetings |
1 |
6 |
2-3 |
18 |
[To
be completed by PIDX staff.]
|
Total PIDX staff time required for
this project. |
188 |
5. Anticipated Completion Date
|
Project Completion date |
1st March 2007 |
6. Sponsoring Member /Work Group/
Sub-Committee
This specification has been
submitted by Jana Schey on behalf of the Business Process Work Group/Sub-Committee.
Contact Information:
Name: Jana Schey
Company: OFS
Portal
Mailing Address: 5847
San Felipe,
Telephone: 832-681-7319
Fax #: 832-681-7396
E-Mail Address: jschey@ofs-portal.com
The chair of this Work Group/
Sub-Committee has reviewed this submission for completeness and understands
this particular Work Group/ Sub-Committee is the Sponsoring Work Group/ SIG,
responsible for the communication process.
This does not mean the Chair or Work Group/ SIG is approving the actual
work or its inclusion in any specification.
Jana E. Schey
Chair’s Signature or
Initials
(electronic is acceptable)
7.
Additional Participants
The
following PIDX members/companies are participants in the development of these
specifications:
|
Member |
Company |
E-Mail Address |
|
Jana
Schey |
OFS
Portal |
|
|
John
Stukes |
OFS
Portal |
|
|
Andy
Ross |
BP |
|
|
Chris
Welsh |
Baker
Hughes |
|
|
Tony
Aming |
Baker
Hughes |
|
|
Terry
Thomas |
Schlumberger |
|
|
Darren
Ebanks |
Schlumberger |
|
|
Tim
Morgan |
Wellogix |
|
|
Carlos
Castillo |
National
Oilwell Varco |
|
|
David
Petty |
Cameron |
|
|
Kreg
Anderson |
Smith
International |
|
|
Michael
Lanier |
M-I
Swaco |
|
|
Sashi
Vinjamuri |
Halliburton |
|
|
Shyam
Sunder-Potta |
Halliburton |
|
|
Paul
O’Shaughnessy |
Chevron |
|
|
Rich
Gould |
Chevron |
riga@chevron.com |
Others to be determined.
I have approached the following companies:
ExxonMobil, Digital Oilfield, Quadrem, BHP Billiton. Waiting for responses.
|
Mail distribution list required? |
No |
|
Please provide the name of the mail distribution
list: |
N/A |
8.
Deliverable Schedule
|
Component |
Status |
Estimated Completion Date |
|
Business Process Guidelines documentation –
including: Use Case(s), diagrams, best practices |
Not
started |
3/1/2007 |
|
Requirements
– if any – for message modifications |
Not
started |
3/1/2007 |
|
PIDD ·
Clarify and agree terminology and definitions ·
Update PIDD entries throughout life of the project ·
Workgroup chair is responsible for ensuring PIDD is
updated |
Not
started |
TBD |