Role packages

An INTERA Role Package is a predefined operational structure for a particular area of responsibility, such as sales, finance, billing, operations or IT.

It defines the information that the role needs, the checks that should be performed and the way results are presented. The package is then mapped to the systems and data used by each company.

A Role Package provides a practical starting point without forcing every organisation to use the same software, terminology or process.

What a Role Package contains

Depending on its purpose, a Role Package can include:

• Asset Types and required properties;
• predefined Metrics and health calculations;
• Reconciliations between related data sources;
• dashboards and widgets;
• default thresholds and exception rules;
• required data mappings;
• recommended update schedules;
• descriptions explaining what each result means and where to investigate.

The package focuses on the information needed to identify where attention is required. It does not attempt to reproduce all the data and functionality already available in specialist systems.

Connecting a package to your systems

Role Packages do not depend on one particular ERP, CRM, accounting or monitoring product. Instead, the package declares the information it requires.

For example, a sales package may require:

• customer commitments;
• ordered equipment and services;
• delivery status;
• activation status;
• agreed and invoiced prices.

During setup, each requirement is mapped through the following structure:

Required information → Integration → DataSource → External field or expression

The administrator selects the appropriate Integration and DataSource, then maps the required fields. Integration credentials, schedules, thresholds and exclusions are configured for the individual installation.

This allows the same Role Package to work with different combinations of systems.

What is configured locally

A Role Package provides the structure and default logic. The following settings are normally adjusted for each company:

• Integration instances and credentials;
• selected DataSources;
• field mappings and expressions;
• period and filter parameters;
• thresholds and tolerances;
• exclusions;
• update schedules;
• dashboard terminology.

Role Packages do not contain customer credentials or operational data.

Cross-industry by design

Many operational responsibilities remain similar across industries.

A sales commitment must be checked against delivery. Activity must correspond with billing. Payments must agree with accounting records. IT must know which systems, backups and services require investigation.

The underlying systems and terminology may differ, but the operational questions are often the same. This allows checks and working practices developed in telecommunications, manufacturing, logistics, maritime and other sectors to be adapted for companies in different industries.

Only the structure and experience are reused. Customer data is never shared between installations.

Start with one problem

Installing a Role Package does not mean implementing every included Metric, Reconciliation and dashboard immediately.

The recommended approach is to begin with one clearly defined problem, enable only the required components and connect only the necessary data. This produces a result that can be checked by the person who owns the process.

Once the first result is reliable and useful, the same Role Package and integrations can be extended to cover additional questions.

Initial Role Packages

Sysadmin

Brings together selected information from monitoring, backup, service and ticketing systems. It helps IT identify what requires attention, where investigation should begin and what evidence is available when a problem is escalated.

The Sysadmin package works alongside existing monitoring tools and is included free with every INTERA plan.

Sales and Account Management

Compares customer commitments with delivery, activation, invoicing and other fulfilment information. It helps account managers see what remains outstanding before answering a customer or making another commitment.

Finance and Billing

Compares activity, invoices, payments and accounting records. It helps finance and billing teams find missing transactions, inconsistencies and other exceptions without repeatedly reconciling complete reports by hand.

Additional Role Packages are introduced as reusable operational problems are defined and verified during the Private Beta programme.

Customising a Role Package

Role Packages are intended to be adapted. Administrators can change mappings, thresholds, exclusions, dashboards and terminology while retaining the package’s underlying structure.

A package should reduce implementation work—not restrict how the company operates.