Operational support includes a comprehensive combination of reference documentation, reference application code and interactive communications with experienced PSP technical staff to help you through every step of the implementation process.

• Detailed implementation guidelines explaining the “hows” and “whys” of the specification.
• Reference implementations in .Net or Java managing a number of PSP specific requirements for Dealer Service Providers and Suppliers.

Dealer Service Provider Reference Code
PSP Client Code

• Compliant to PSP Web Services Specification
• BOD correlation between request and response
• Caching of supplier endpoints, Service Policy, and Business Rules
• Can simplify DSP effort to implement PSP
• Duplicate message and BOD elimination
• Supports asynchronous confirmation

DMS Implementation Responsibilities

• Display and control of the information related to each BOD supported
• User selection of supplier specifiable business rules
• Error handling and reporting

Supplier Reference Code
PSP Web Service Functional Description

• Compliant to PSP Web Services Specification
• Queue BODs for asynchronous processing and receipt
• Duplicate message and BOD elimination
• Communicates supplier specific Service Policy and Business Rules (can be data driven if needed)
• Translates supplier specific errors into standardized error mechanisms
• Translates between BODs and supplier specific data formats
• Can communicate with the supplier backend system using required protocols

Supplier Interface General Functional Requirements

• Authenticate users (this responsibility could be assumed by the PSP Service)
• Process the PSP transactions supported by the supplier.  These backend transactions may use existing interfaces.  For example:
  • Part order creation
  • Part order status
  • Part pricing and availability
  • Part shipments