Success Path
Everything you need to get started with augmented reality

Design Technical Architecture

Make final decisions about what information you need to integrate with your AR experience. Then start planning how you will connect to the systems, tools, and/or data you need to achieve your use case.

Identify integration needs

As your AR project progresses, you will determine how to integrate with existing systems, tools, and/or data. Earlier in the project, you planned what information you need to flow into and out of Vuforia Studio. Now document how you will integrate to the systems that house that information.

Review the storyboard you created when you designed the user experience. Throughout the AR experience, document all the information the user will need, data they will generate, and where that information currently lives.

Your integration needs should include:

  • What you need: Note the specific pieces of information you need to create your AR experience.
  • How often that information needs to be updated: Does the information being used in your AR experience change frequently and need to be continually updated in order to be useful? If so, what are your performance expectations? Keep in mind that the higher the frequency of updates, the more transactions your infrastructure will need to support.
  • Where that data lives: Whether in a cloud-hosted third-party system, an in-house solution, a .csv file, a machine, or something else—you’ll need to identify where this information is currently housed.
  • Whether the connection needs to be unidirectional or bidirectional: Will the information flow into the AR experience? Will the AR experience feed information back out to the system? Or both?
  • Security considerations: Are there any firewalls or other security barriers that prevent you from accessing the system?
  • Version control: How will you ensure you’re always using the most up-to-date version of the information in the system?

We recommend you work with your IT team and other internal partners to identify your integration needs. They can help you determine what information can integrate into your AR experience. Negotiate your requirements and adjust your scope, if necessary. Focus on the integrations you’re most likely to re-use as you grow your portfolio of AR experiences.

Document integration strategy

Create an architecture diagram that illustrates your integration strategy. This diagram will include all the interconnected systems necessary to achieve your AR use case. It will also illustrate the methods or technology you will use to connect those systems. The complexity of your architecture diagram will vary depending on your use case and other factors.

If you are not integrating Vuforia Studio with any other systems or data, your diagram will look like this:

Vuforia Studio architecture diagram 

If you are integrating Vuforia Studio with other systems, your diagram will be more complex.

Later in the project, you will implement the necessary integrations to achieve your use case. ThingWorx will facilitate connections to a variety of systems, tools, and/or data.

ThingWorx Flow can help you connect to some systems. This integration platform enables you to connect to on-premise systems, cloud systems, and devices. If ThingWorx Flow does not meet your needs, you will use REST APIs to create those connections.

Identify who manages the systems you’re connecting to. Ideally, these experts will commit some time later in the project to help integrate these systems. 

Recommended Resources

Did you find this helpful?

ADDITIONAL RESOURCES

Technical Support

Log a case with eSupport using your Service Contract Number. Don’t have it? Ask the Community.

Product Documentation

Find step-by-step instructions and information about using Vuforia Studio and Vuforia View in the Help Center.

Ask the Community

Visit the PTC Community to get product assistance, share ideas, and browse information about using Vuforia Studio.

Contact Us

Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.