3rd Parties
Seller
3rd Parties
Transaction
1st & 2nd Parties
Buyer
Entities providing services or products on behalf of the primary parties, that enable the transaction or provide value to the primary parties.
3rd Parties are a new “dimension” for AgGateway. Including them will require thinking differently about connectivity. Therefore, we need to “Think in 3D”! (QR Codes come later…)
So, who are some “3rd Parties”? • Toll Manufacturer ▫ Raw Materials ▫ Packaging • Transportation Provider ▫ Rail ▫ Truck ▫ Barge • Storage Warehouse • Waste Disposal Service
• • • • • • • •
Storage Tank Cleaning Shipment Surveyor Product Inspector Application Consultant Documentation Broker Wash-Out Service Permitting Agency ?
Typical Characteristics of: 1st/2nd Party Connectivity
3rd Party Connectivity
• • • •
• • • •
Broad Market High Value & Volume Product Centric Transaction Extended Relationship “Life-Span” • “Foundational” Infrastructure for Future Expansion • High to Medium “Technology Footprint” (What does this mean?)
• (Typical participants in past AgGateway projects.)
Local Market Variable Value & Low Volume Service Centric Transaction Limited Relationship “Life-Span” • Limited Future Connectivity Needs • Low to No “Technology Footprint” (What does this mean?)
“Technology Footprint”?
Typical 3rd party IT environment.
Category
Description
Examples
HIGH
Internally maintained, fully supported, state-of-the-art information technology environment.
Major to middle tier enterprises with full-time staffs having application development capabilities using sophisticated toolsets and ERP-class systems.
MEDIUM
Largely vendor support technology environment with business automation capabilities
Small to middle tier enterprises without, or with minimal, dedicated staff. Functionality enhancements are provided by ISV.
LOW
Basic office computer productivity and communications capabilities, including Internet access and printing.
Rural offices of larger entities, or small single/multi location companies.
NO
Rudimentary personal communications tools; cell/land phones, and perhaps fax machines. No dedicated information technology support capabilities.
Remote, isolated service entities, e.g. transportation, product storage, in-field applications, or agents of higher functionality footprint enterprises working in remote, isolated locales.
“Technology Footprint” Originate/Receive
“Transport/Translate”
Originate/Receive
Standards Based Sample Connectivity Chain HIGH – to – HIGH SAP - “NexusE2E” - JDE
HIGH
HIGH
Process
Process
Partner
Partner
Security
Security
“Technology Footprint” Originate/Receive
“Transport/Translate”
Originate/Receive
Standards Based Sample Connectivity Chain HIGH – to – LOW / NO SAP – “????” – HTML / Cell Phone
HIGH
Low / No
“Technology Footprint” Originate/Receive
“Transport/Translate”
Originate/Receive
Standards Based Sample Connectivity Chain HIGH – to – HIGH ERP (SAP) - “ebXML via NexusE2E” – ERP (JDE)
HIGH – to – MEDIUM ERP - “ebXML / Web Service” – Mid-Tier System
HIGH – to – LOW JDE – “Proprietary” – HTML
HIGH – to – NO SAP – “Proprietary” – Cell Phone
New Territory
Solutions to 3rd Party Connectivity must be “Reality-Based” ▫ Proprietary communication protocols & channels hinder, or even preclude, broad adoption. ▫ Messages used must be based on AgGateway Standards. ▫ Simplified, standards based connectivity will encourage essential Allied Provider support. ▫ Requires nominal (unit) cost & complexity of adoption to drive into ‘lower’ tiers of value chain. ▫ Realistic adoption rate expectations that provide value throughout adoption curve. ▫ Respect the available “Technology Footprint” across the entire industry spectrum of trading partners. ▫ Low to No training and implementation requirement.
Keeping in mind the prior concepts and challenges, how might a system to allow 3rd Parties to participate look? (BTW – In the following high-level overview, addressing the required security is implied, but not specifically addressed.)
AgGateway Connectivity Enablement System
AG CIO Roundtable rd
“ACES” - The Future of 3 Party Connectivity.
ACES – Architecture Options
Load Notification - Scenario Setup 1st & 2nd Parties Transaction
Order Supplier
Confirm
Purchaser
3rd Parties
Warehousing
Transportation
Scenario Setup Load Notification – Change Issues P.O. Confirm
3rd Parties
Warehousing
Transportation
Scenario Setup Disclaimer • The hardware (iPhone), software (Optishare, codeREADr) and barcoding technology (QR Code) used in this demonstration are not endorsed by AgGateway or the presenters. • This combination of technologies was used because they allowed the construction of the highest functioning demonstration with the least amount of time and effort. • There are other technologies that could have been used that may be equally suitable.
Scenario Setup Possible Bar Codes (Samples) QR Code
Data Matrix
Code 128
[GS1 Number + Company Unique Sequential Transaction Number]
Scenario Setup Possible Smart Phones (Samples)
BlackBerry
Android (HTC)
Windows Phone 7
Apple iPhone
Scenario Setup Scenario - Validate Load @ Pick-Up 3rd Party Service Providers Warehousing
Transportation
ACES “Post Office”
1st/2nd Party “ERP” Systems
Standard AGW QR(?) Standard AGW XML Standard AGW XML
Validate Load @ Pick-Up Scenario
Value Point #6: Single, non-proprietary , message handling protocols. (Likely pre-existing.) Near realtime data collection.
Value Point #2: Single interface to multiple customers. Confirm current details, avoid mistakes. Notify customer of service.
3rd Party Service Warehousing
ACES “Post Office” Value Point #4: Industry standard XML message format. Single delivery endpoint. (Value-add application opportunity.)
1st/2nd Party “ERP” Systems
Transportation
Value Point #3: Industry standard QR(?) message format. Universal ‘readability’. (Value-add application opportunity.)
Standard AGW QR(?)
Standard AGW XML
Value Point #5: Single, non-proprietary, message collection and distribution architecture.
Value Point #1: Single interface to multiple customers. Confirm current details, avoid mistakes. Notify customer Providers of service.
Standard AGW XML
• How would a project like this be organized? Sequential, modular approach.
•
Architecture design Business use & Standards definition(s) Modules
• • • • •
ACES Backbone Connectivity Enablers
• How would this project be paid for? • •
Developmental costs Usage costs
• Interested in the 3rd Party Connectivity Project? Contact:
• • • •
Bruce Blitch - [email protected] Tim Piper - [email protected] Rod Conner - [email protected]
3rd Parties
Transaction
1st & 2nd Parties
Buyer
Entities providing services or products on behalf of the primary parties, that enable the transaction or provide value to the primary parties.
3rd Parties are a new “dimension” for AgGateway. Including them will require thinking differently about connectivity. Therefore, we need to “Think in 3D”! (QR Codes come later…)
So, who are some “3rd Parties”? • Toll Manufacturer ▫ Raw Materials ▫ Packaging • Transportation Provider ▫ Rail ▫ Truck ▫ Barge • Storage Warehouse • Waste Disposal Service
• • • • • • • •
Storage Tank Cleaning Shipment Surveyor Product Inspector Application Consultant Documentation Broker Wash-Out Service Permitting Agency ?
Typical Characteristics of: 1st/2nd Party Connectivity
3rd Party Connectivity
• • • •
• • • •
Broad Market High Value & Volume Product Centric Transaction Extended Relationship “Life-Span” • “Foundational” Infrastructure for Future Expansion • High to Medium “Technology Footprint” (What does this mean?)
• (Typical participants in past AgGateway projects.)
Local Market Variable Value & Low Volume Service Centric Transaction Limited Relationship “Life-Span” • Limited Future Connectivity Needs • Low to No “Technology Footprint” (What does this mean?)
“Technology Footprint”?
Typical 3rd party IT environment.
Category
Description
Examples
HIGH
Internally maintained, fully supported, state-of-the-art information technology environment.
Major to middle tier enterprises with full-time staffs having application development capabilities using sophisticated toolsets and ERP-class systems.
MEDIUM
Largely vendor support technology environment with business automation capabilities
Small to middle tier enterprises without, or with minimal, dedicated staff. Functionality enhancements are provided by ISV.
LOW
Basic office computer productivity and communications capabilities, including Internet access and printing.
Rural offices of larger entities, or small single/multi location companies.
NO
Rudimentary personal communications tools; cell/land phones, and perhaps fax machines. No dedicated information technology support capabilities.
Remote, isolated service entities, e.g. transportation, product storage, in-field applications, or agents of higher functionality footprint enterprises working in remote, isolated locales.
“Technology Footprint” Originate/Receive
“Transport/Translate”
Originate/Receive
Standards Based Sample Connectivity Chain HIGH – to – HIGH SAP - “NexusE2E” - JDE
HIGH
HIGH
Process
Process
Partner
Partner
Security
Security
“Technology Footprint” Originate/Receive
“Transport/Translate”
Originate/Receive
Standards Based Sample Connectivity Chain HIGH – to – LOW / NO SAP – “????” – HTML / Cell Phone
HIGH
Low / No
“Technology Footprint” Originate/Receive
“Transport/Translate”
Originate/Receive
Standards Based Sample Connectivity Chain HIGH – to – HIGH ERP (SAP) - “ebXML via NexusE2E” – ERP (JDE)
HIGH – to – MEDIUM ERP - “ebXML / Web Service” – Mid-Tier System
HIGH – to – LOW JDE – “Proprietary” – HTML
HIGH – to – NO SAP – “Proprietary” – Cell Phone
New Territory
Solutions to 3rd Party Connectivity must be “Reality-Based” ▫ Proprietary communication protocols & channels hinder, or even preclude, broad adoption. ▫ Messages used must be based on AgGateway Standards. ▫ Simplified, standards based connectivity will encourage essential Allied Provider support. ▫ Requires nominal (unit) cost & complexity of adoption to drive into ‘lower’ tiers of value chain. ▫ Realistic adoption rate expectations that provide value throughout adoption curve. ▫ Respect the available “Technology Footprint” across the entire industry spectrum of trading partners. ▫ Low to No training and implementation requirement.
Keeping in mind the prior concepts and challenges, how might a system to allow 3rd Parties to participate look? (BTW – In the following high-level overview, addressing the required security is implied, but not specifically addressed.)
AgGateway Connectivity Enablement System
AG CIO Roundtable rd
“ACES” - The Future of 3 Party Connectivity.
ACES – Architecture Options
Load Notification - Scenario Setup 1st & 2nd Parties Transaction
Order Supplier
Confirm
Purchaser
3rd Parties
Warehousing
Transportation
Scenario Setup Load Notification – Change Issues P.O. Confirm
3rd Parties
Warehousing
Transportation
Scenario Setup Disclaimer • The hardware (iPhone), software (Optishare, codeREADr) and barcoding technology (QR Code) used in this demonstration are not endorsed by AgGateway or the presenters. • This combination of technologies was used because they allowed the construction of the highest functioning demonstration with the least amount of time and effort. • There are other technologies that could have been used that may be equally suitable.
Scenario Setup Possible Bar Codes (Samples) QR Code
Data Matrix
Code 128
[GS1 Number + Company Unique Sequential Transaction Number]
Scenario Setup Possible Smart Phones (Samples)
BlackBerry
Android (HTC)
Windows Phone 7
Apple iPhone
Scenario Setup Scenario - Validate Load @ Pick-Up 3rd Party Service Providers Warehousing
Transportation
ACES “Post Office”
1st/2nd Party “ERP” Systems
Standard AGW QR(?) Standard AGW XML Standard AGW XML
Validate Load @ Pick-Up Scenario
Value Point #6: Single, non-proprietary , message handling protocols. (Likely pre-existing.) Near realtime data collection.
Value Point #2: Single interface to multiple customers. Confirm current details, avoid mistakes. Notify customer of service.
3rd Party Service Warehousing
ACES “Post Office” Value Point #4: Industry standard XML message format. Single delivery endpoint. (Value-add application opportunity.)
1st/2nd Party “ERP” Systems
Transportation
Value Point #3: Industry standard QR(?) message format. Universal ‘readability’. (Value-add application opportunity.)
Standard AGW QR(?)
Standard AGW XML
Value Point #5: Single, non-proprietary, message collection and distribution architecture.
Value Point #1: Single interface to multiple customers. Confirm current details, avoid mistakes. Notify customer Providers of service.
Standard AGW XML
• How would a project like this be organized? Sequential, modular approach.
•
Architecture design Business use & Standards definition(s) Modules
• • • • •
ACES Backbone Connectivity Enablers
• How would this project be paid for? • •
Developmental costs Usage costs
• Interested in the 3rd Party Connectivity Project? Contact:
• • • •
Bruce Blitch - [email protected] Tim Piper - [email protected] Rod Conner - [email protected]
