This document is intended for software developers or similar technical roles interested in implementing Augmented Reality experiences that leverage the Oracle CX Service suite of applications such as B2C or B2B Service.

An iOS tablet device is required to follow along with the content in this guide. Although iOS phones may be used, the AR projects are not optimized for smaller screens and therefore could exhibit undesired behavior without further configuration.

This accelerator uses different software, cloud applications, and native applications to implement the end-to-end solution. To obtain/procure the various licenses or environments for Oracle software, you must work with the applicable Oracle applications team supporting your organization.

The accelerator is intended to provide introductory content and source code examples to assist the construction of augmented reality applications on iOS; a blueprint for what can be done to assist with the learning experience integrated with Oracle CX applications. By following the examples in this document, you will prepare your development environment to configure a working AR application that can demonstrate a device in 3D space which displays real-time diagnostic data and allows the viewer to submit a service request using Oracle SaaS applications.

OCI F(n) contains the majority of the remote configuration for both the AR application and its integrations with other systems. The AR application uses OCI F(n) functions directly (until the OCI API gateway is made available).

The objective of this accelerator is to limit the amount of coding within the AR experience while delivering a set of data and features to build CX AR experiences on top of. To achieve this, we leverage a set of generic integration calls from the AR experience to OCI Functions service OCI F(n).

Oracle IoT Cloud Service (IoTCS) is used to provide the device sensor data to the AR experience. This data may be live device data, or device simulator data generated from within IoTCS.

You will use either Engagement Cloud or Service Cloud for service requests and knowledge. It is possible to configure both applications, but only one it used at a time. The ARConfigs API call that is configured in OIC determines which service application is used.

OCI Functions are used as the integration back-end for the demo app. As previously mentioned, the application doesn't implement authentication or authorization on a per-user level as is typical for a production app. A single integration user will authenticate to OCI F(n) API calls, and OCI F(n) will perform integrations as needed. In a production instance, you would need a layer of authentication and authorization in between OCI F(n) and the AR application to ensure that each user is authenticated and has access according to your implementation policies.

The source code for the application is developed with demo use cases in mind; it is not intended to be a stand-alone application that can be published to the App Store. Rather, this app should be compiled with the intention of exploring capabilities and providing single-user demos. After you are familiar with the capabilities of the application and the AR technology, you can plan to design your own app with user authentication and integrations specific to your use case.

After compiling the application and deploying it to a device, you must configure it to run a demonstration. The following sections explain how to do this.