To design ThingWorx applications to connect and monitor your products, first learn about your users' needs. Research what data is most important and how users will interact with the applications. Then sketch a first draft.
Before you begin, complete these steps:
User experience (UX) requirements will help you understand how users will interact with your ThingWorx applications. They define what an application will look like and how the user interface (UI) will work. We recommend that a solution architect and UX/UI designer work together.
To gather UX requirements, do research by talking with experts in your organization. Also, find out who your users are. Talk to the people who will use the data from the application. Find out what data is most important to them and how they’ll search for it in the application. Document this research.
There is not a single way to document UX requirements. Yet, different requirements will result in different UI designs. Requirements may also affect the performance and security of the application.
The research for your UX requirements should answer the following:
Once you document UX requirements, next define user groups. This will clarify what different types of users can see and do in the application. For example, one person may need to look at data but will never make changes in the application. Another person may need full access. These two types of users are in different user groups.
Document the visibility (what they can see) and permissions (what they can do) for each type of user. Be as accurate as you can. If users have too much access, they could see confidential data they should not have. If users have too little access, they may not be able to see the data they need.
In ThingWorx Composer, you’ll create groupings at 3 levels:
Different user roles drive what different types of permissions need to be given. For visibility, is it based on a Thing’s organization, location, region, product lines, or other attributes. A user role is an intersection of visibility and permissions. For instance, a user role could be a support engineer (run time permission) for eastern Europe (visibility). Make sure that your user groups and organization units are scalable.
There are 3 forms of permissions you can adjust:
ThingWorx offers built-in user groups for administrators, developers, and users. Depending on your needs, these may be enough to start with. You can set up more user groups, invite users, and make changes to visibility and permissions later.
Design a wireframe, or a first draft, of the user interface (UI) of your ThingWorx application. The goal of the UI is to make it easy for users to get the information they need when they need it.
A wireframe is a low-fidelity, early-stage design. It provides direction to the developers who will build the application. It also shows how users interact with the application. A wireframe often contains a grid of empty boxes that represent elements on a screen. To make a wireframe, you can use a tool like Balsamiq or Axure or draw it by hand.
Focus on what is most important for functionality. Look back on requirements and user research. Instead of filling up the screen with widgets, we recommend that you leave blank space. The fewer elements users see, the easier the application will be for them to learn and use.
In your wireframe, include the following:
Do not include colors, images, or other styling choices. You’ll make those decisions later.
Remember that wireframes change and evolve over time. Later, you’ll review, test, and improve upon your early-stage design.
In addition to the recommended resources named above, PTC offers Success Services that fit seamlessly into your Success Path, making it even easier to reach your desired business outcome.Rapid Outcome
Have a question? Submit your contact information and we’ll reach out within 1 business day. You’re never obligated to purchase or commit.