Links to purchasing documents contracts
Transmission timing business process
Routing – fields, routing definition, process to handle incorrect routing information, requirements for routing to specific field locations
Data elements and required information – do we have the fields necessary to link to both purchasing documents and invoice documents / meet trading partner requirements
Attachments – how to manage

Develop business process guidelines governing the Field Ticket process and business requirements.

Field Ticket document standards have been in place in 3901 for some time but have not yet been implemented on any broad industry basis. Growing adoption of purchase order and invoice document transactions between trading partners is resulting in acknowledged need to implement electronic transmission of field ticket documents between trading partners in order to support reconciliation to contract, invoice, and purchase order and to electronically capture field ticket authorization from field location approvers.

Current industry standards among industry trading partners using electronic processes is to transact field tickets as document attachments to other PIDX compliant XML formatted transactional documents. The goal of this initiative is to develop initial business processes between trading partners to support standalone exchange of field tickets electronically between trading partners.

3. Initial Contributions

Document name	Type of Document	Document Source
3901 FieldTicket	XML	PIDX
3901 FieldTicketResponse	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	4	1	4
Face to face meetings	1	4	2-3	12

[To be completed by PIDX staff.]

Total PIDX staff time required for this project.

5. Anticipated Completion Date

Project Completion date

TBD – 1^st December 2006

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, Suite 3220, Houston, TX 77057

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
Dann Bews	Digital Oilfield	dbews@digitaloilfield.com
Rob Normandeau	Digital Oilfield	rnormandeau@digitaloilfield.com
Terry Thomas	Schlumberger	Thomas21@houston.oilfield.slb.com
Chris Welch	Baker Hughes	Chris.Welsh@bakerhughes.com

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	TBD