POC Process for AuraPlayer’s Invoices and PO to SO Apps Follow

There are two types of POCs:

• AuraPlayer's environment POC - Offline POC
• Customer's environment POC - live POC

AuraPlayer's environment POC Steps:

This is the simplest POC. The POC will be done in the following steps:

• The customer will send 10 different files - POs or Invoices
• AuraPlayer will upload these files to the Application
• The customer will get a video of the application using these files, and analyzing them by the AI. The customer will be able to view the application via the video and the quality of the AI analysis.

Pros:

• No need for any environment preparation on the customer side
• Simple and short POC
• Free POC
• The customer gets easily the look and feel and the capabilities of the application

Cons:

• No data validation and no integration with private environment and data - In a broader POC, AuraPlayer validate some of the data against the customers' real data from Oracle. It significantly improves the work and the results, during the POC, and improve the work and the results during real deployment.

Customer's environment POC Steps:

• Customer will send AuraPlayer 10 different files - POs or Invoices
• AuraPlayer will setup/deploy an on-premise server (ServiceManager)
• AuraPlayer will Install Invoices or PO to SO application on the above AuraPlayer server
• AuraPlayer will build a DB schema on the customer's DB for AuraPlayer application
• AuraPlayer with assistance of the customers' DBA will build a couple of validations queries of the analyzed data - Customer/Vendor, item ID. In order to improve data integrity.
• AuraPlayer will do Mapping and adjust the application to the customer's Test EBS environment
• The customer will have access to the application and "play" with it seeing his own items on his own environment

Pros:

• Real customer's environment
• The customer will be able to understand the integration of AuraPlayer's application to his own environment
• The customer will understand the power of data validation that is based on his own private data

Cons:

• Longer POC
• Paid POC
• Customer involvement is required to build the POC

Pre-requisites

• Machine to install AuraPlayers ServiceManager on-premise for Development - Prerequisites and installation

  1. AuraPlayer's team will assist in the installation phase, make sure to prepare the machine according to the above pre-requisites

  2. The machine should resides in the same network as the Test EBS for better performance

• VPN

  1. For AuraPlayer's team members

  2. Access to the above machine, the Test EBS, the Test EBS DB

  3. Which type of VPN can be set?

      1. Preferred: a VPN type that let our team use their own laptops to access your environment

      2. VM Windows desktop, so we can install our development tools and work with it

• EBS 

  1. EBS should have configured with all required data - customers, items, prices, etc

  2. EBS user with responsibility to add SOs or Invoices

• Email 

  The application will be triggered from an email. One email or several emails will need to be created, so AuraPlayer will be able to be registered to be triggered once a new email arrives. Defining email is NOT must during the POC. Invoices or POs can be manually upload as well.

• Contacts

  1. Contact person to instruct us about functional flow

  2. Contact person for IT issues - machine setup, EBS access, EBS DB

  3. DBA - helping in creating DB schema and relevant queries

Notes

• POC is done by using EBS credentials. SSO and more advanced configuration will be done as part of security and architecture session after the POC.