First Setup Journey

The goal of the first setup is to move from a new INTERA installation to one working Dashboard showing real company data.

A typical first setup journey follows these steps.

Step 1: Install INTERA #

Install INTERA using the method suitable for your environment.

Depending on the deployment, INTERA may run:

• on a Linux server;
• on a Windows system;
• in Docker;
• in a local evaluation environment;
• in a hosted environment.

After installation, open INTERA in a supported web browser.

See the Installation and Administration chapter for detailed installation instructions.

Step 2: Create the First Administrator #

During the first launch, create the initial administrator account.

The administrator is responsible for:

• configuring Integrations;
• creating Asset Types;
• creating Assets and Metrics;
• managing Dashboards;
• assigning Roles;
• creating users;
• maintaining the system.

Use a secure password and keep the administrator account separate from normal daily-use accounts where possible.

Step 3: Complete Basic System Settings #

Review the basic system configuration.

Depending on the available version, this may include:

• company name;
• timezone;
• default language;
• default currency;
• synchronization preferences;
• system URL;
• access settings.

The correct timezone is especially important because Metrics, synchronization schedules, and historical data depend on accurate time settings.

Step 4: Choose a Blank Setup or Role Package #

You may begin with:

• a blank INTERA configuration; or
• an available Role Package.

Choose a blank setup when you want to design your own structure from the beginning.

Choose a Role Package when a predefined package matches your industry or business function.

A Role Package may already contain recommended:

• Roles;
• Dashboards;
• Asset Types;
• Metrics;
• thresholds;
• Integration requirements.

The package still needs to be connected and mapped to your company systems.

Step 5: Connect the First Integration #

Open the Integration settings and create a new Integration Instance.

You will normally need to provide:

• a name for the connection;
• the external system address;
• authentication credentials;
• initialization parameters;
• synchronization settings.

Save the Integration Instance and test the connection.

A successful connection confirms that INTERA can communicate with the external system.

Step 6: Review Available DataSources #

After the Integration is connected, review the DataSources it provides.

For each DataSource, check:

• what business data it contains;
• which fields are available;
• which filters are supported;
• whether time-period filtering is required;
• whether the returned data matches your needs.

Choose a simple and understandable DataSource for the first setup.

Good first examples include:

• invoice totals;
• open ticket counts;
• customer balances;
• active service counts;
• unresolved alarms;
• sales totals.

Step 7: Create or Review Asset Types #

Determine whether the information should be linked to a business object.

For example:

• customer balance may belong to a Customer Asset;
• vessel status may belong to a Vessel Asset;
• product revenue may belong to a Product Asset;
• network alarms may belong to a Network Site Asset.

If required, create the relevant Asset Type and define its fields.

When using a Role Package, review the provided Asset Types and adjust mappings where necessary.

Step 8: Create or Synchronize the First Asset #

Create one Asset manually or synchronize it from the connected Integration.

Verify that:

• the Asset has the correct name;
• required fields are populated;
• external record mapping is correct;
• synchronized values update successfully.

Starting with one Asset makes it easier to confirm that the configuration is correct before importing or mapping a larger set.

Step 9: Create the First Metric #

Create one simple Metric using the connected DataSource.

For the first Metric:

• use one DataSource;
• use a simple filter;
• select one result field;
• apply a simple operation such as count, sum, average, minimum, or maximum;
• avoid complex logical expressions.

Examples include:

• total unpaid balance;
• number of open tickets;
• number of active customers;
• monthly sales total;
• unresolved alarm count.

Run or synchronize the Metric and check the result.

Confirm that the value matches the source system.

Step 10: Create the First Dashboard #

Create a Dashboard and assign it a clear name.

Then:

• select the required Role;
• choose a page layout;
• add a Frame;
• add a Widget;
• connect the Widget to the Metric;
• save the Dashboard.

Keep the first Dashboard simple.

One page with one or two important Metrics is enough to confirm that the complete data flow works.

Step 11: Assign Access #

Create or select a user and assign the appropriate Role.

Log in as that user or use the available preview function.

Confirm that the user:

• can see the correct Dashboard;
• cannot see unauthorized Dashboards;
• sees the expected Metric values;
• can navigate between pages where applicable.

Step 12: Confirm Synchronization #

Review the last update time and current status of the Integration and Metric.

Check that:

• synchronization completed successfully;
• the data is current;
• no error status is displayed;
• the Metric value matches the source system;
• the Dashboard shows the updated result.

After this step, the first end-to-end INTERA setup is complete.

Recommended First Result #

Do not try to model the entire company during the first setup.

A successful first result should be small and easy to verify.

For example:

Accounting System
    ↓
Invoices DataSource
    ↓
Total Overdue Balance Metric
    ↓
Finance Dashboard
    ↓
Finance Manager Role

Or:

Ticketing System
    ↓
Open Tickets DataSource
    ↓
Unresolved Tickets Metric
    ↓
Customer Operations Dashboard
    ↓
Customer Operations Manager Role

Once one data flow works correctly, you can gradually add:

• more Metrics;
• additional Assets;
• more Dashboard pages;
• more Integrations;
• additional Roles;
• thresholds;
• calculated Metrics;
• more advanced Widgets.