Augmented Reality for Enterprise Alliance

Overview and Interview Guide

Enterprise AR Interoperability Requirements Project


The AREA Interoperability and Standards Program is conducting in-depth interviews with customer segment AREA members about their requirements for AR-enabling technology interoperability.

Technology interoperability refers to the degree to which software systems, devices, applications or components can connect and communicate with other components (entities) in a coordinated manner without effort from the end user. This is often related to things like data access, data transmission and cross-organizational collaboration. [source: TechTarget].

In addition to the connection and communication being automatic and programmatic (without effort from the end user), all the properties of the original data are preserved and/or all the available features of a component or system are exposed (readable).

It’s valuable to describe interoperability as a property of components within and between systems. Rather than an on/off attribute, it’s also useful to place interoperability between components or systems on a continuum.

Interoperability continuum and the place of interoperability standards

Figure 1. Interoperability continuum and the place of interoperability standards

Interoperability is already key to integration of many value-added enterprise solutions with existing data management systems. For example:

Please see below a few examples of enterprise AR interoperability requirements to better understand the structure of statements that can communicate the enterprise’s AR interoperability needs.

Out of Scope

We do not seek to confirm if interoperability for AR to integrate with IT systems is important.

We are working on the assumption that lack of or low interoperability in AR solutions and integration with existing IT is a significant barrier to adoption. If this assumption is inconsistent with your information or experience, let us know! If you’re not the person responsible for integration, perhaps there’s someone else in your organization who is finding the AR and IT integration challenges a barrier to deployment.

We are not performing these interviews to capture AR system performance requirements. Current AR product features don’t meet all functional requirements for all enterprise AR use cases. We encourage members who have requirements documented for their organizations to contribute to the AREA Requirements Committee. The Requirements Committee is responsible for populating and maintaining the AREA Statement of Needs (ASON) database.


We believe that your company requires AR-enabling technological interoperability to more effectively and tightly integrate AR technologies into its IT systems and platforms. We seek to understand where and how low AR technological interoperability is preventing or reducing enterprise AR deployments. We are entirely agnostic and do not seek information about any specific platforms or tools your company is using or evaluating.

We are seeking “requirements” for interoperability. Requirements are short/simple statements that provide some details of the obstacles, interfaces or data compatibility problems, but do not include how to solve a problem. A requirement can be stated in a positive way: capabilities that are needed for two or more systems to interoperate.

It may help to begin with who or what has the “problem.” Using the word “must” also helps to shape the thinking around (tightening) the requirement. Another tip is to think in terms of flows of actions, data, people, or results.

Here are some examples of technology interoperability requirements for AR:

Questions/Discussion Topics


All interviews will be treated as confidential and the AREA’s staff or non-competitive volunteer member will sign NDAs in preparation for interviews. We may need to interview multiple people in your organization before we reach our goals, and could have separate NDAs, if necessary.

The substance of interviews will be anonymized before it will be included in AREA program deliverables. All our information sources will remain confidential.

Expected Outcomes

By gathering insights across the AREA customer segment (and, perhaps beyond), we seek to reach three outcomes.


The requirements that this project will identify will be compiled and summarized in tables. Tables will capture the type (category) of barrier or challenge this requirement would meet, the interface or data that are being held in proprietary formats and silos, and other information. Specific information around requirements will never be attributed to any AREA member company.

These requirements will be shared in blog posts and with organizations that can use them to develop standards or other approaches to addressing the barriers to interoperability.

Customer Dialogs with Vendors and Partners

In the interview, we ask about if/how interoperability discussions with solution and technology providers have begun, evolved and where the problems are perceived to be. The project will present the status of the dialog with vendors and propose some approaches to advance for win-win resolution.


The project will summarize learnings about the roles of those who are perceived to be most supportive of working on interoperability (and perhaps those roles that might object or fail to see the benefits). This will assist advocates for interoperability in enterprise AR to identify those in their organizations most likely to commit resources for finding interoperability solutions and accelerate AR technology integrations.

Next Steps

The AREA Interoperability and Standards Program will reach out individually to AREA customer segment members and request their time to conduct interviews about the topics outlined above. The team will compile the feedback and knowledge shared by members into materials for different audiences and stakeholders who will find this information valuable.

If you are interested in participating in this program by discussing the topic of requirements with a member of the Interoperability and Standards Program team, please contact Christine Perey [email protected]