Core Services related info

Core services defines and handles the organizational data for ranking purposes
Core services handles the following data stores
  • All markets which makes use of ranking sevices
  • All stores afiiliated to the existing markets
  • All devices which makes use of ranking services
  • The ranking zones
Also, Core services are responsible for running DBMS jobs which performs data aggregation
There are currently two specific Core services:
  • Core market services -> It is a market oriented service. Handles the organizational data
  • Core global services -> Handles the data aggregation jobs and other administrative services not related to market
All the above services are directly integrated with Acrelec SSO services.

Engage Services related info

Engage platform is an attempt to enhance the ranking system deplyed at store level by creating similar user experiences to those experienced when playing games in order to motivate and engage users.
This is accomplished through the application of game-design elements and game principles in non-game contexts of daily store activity Engage platform encourages the competition between stores regions, markets etc by providing customizable challenges aor achievements. Fulfilling a challenge (for instance occupying first place) is rewarded with badges and experience points
Based on the overall number of experience points the store may gain an avatar which spans from the slowest pedestrian up to the fastest man-made vehicle to date: Juno spacecraft
All aspects of the Engage platform are controlled from the two available portals:
  • Engage [Dashboard] -> The portal responsible for Engage services for Dashboard
  • Engage [QTimer II] -> The portal responsible for Engage services for QTimer II (SuperTimer)
Note: Engage platform is not yet fully integrated with Acrelec SSO services. Therefore, separate user profiles must be defined for Engage users

QTimer API related info

These are the Swagger pages which fully describes the API available for Acrelec Timer services
The QTimer API is used by field devices to report the data into the cloud back-end database.
There are two API endpoints, one for each flavor of Acrelec Timer service
  • Dashboard API -> The endpoint wich is responsible for handling data reported by Dashboard solution
  • QTimer II API -> The endpoint wich is responsible for handling data reported by QTimer II (SuperTimer) solution

Core API related info

These are the Swagger pages which fully describes the API available for Acrelec Core services
The Core API is used by field devices to store and define organizational data.
The definitions of organizational data is created automatically based on definitions in ATP platofrm, available at device level from Environment.About structures. There are two Core services API endpoints, one for each flavor of Acrelec Timer service
  • Core API [Dashboard] -> The endpoint wich is responsible for handling Dashboard solution
  • Core API [QTimer II] -> The endpoint wich is responsible for handling QTimer II (SuperTimer) solution

Engage API related info

This is the Swagger page which fully describes the API available for Acrelec Engage services
The Engage API is used by field devices to retrieve the Engage ranking data, achievements, rewards ond so on.
There are two Engage services API endpoints, one for each flavor of Acrelec Timer service
  • Engage API [Dash] -> The endpoint wich is responsible for handling Engage data related to Dashboard solution
  • Engage API [QTimer II] -> The endpoint wich is responsible for handling Engage data related to QTimer II (SuperTimer) solution

Mobile API related info

This is the Swagger page which fully describes the API available for Mobile devices
Part of this API endpoint is also used by store devices to report mobile devices related data.