Back

CORE

This module contains the technical platform and generic functionalities, used to configure the behavior of all functional domains. It maintains the important master data, lists, settings and administrative features supporting all other functions of the COMET system.

1. AUTHENTICATION AND AUTHORIZATION

1.1. User Authentication

COMET platform requires login with username and password. User authentication is managed by a specialized Identity and Access Management Solution called Keycloak, which provides SSO and may be used for authentication by other apps used in the associations.

1.2. Password Policy

Standard password policy (min 8 chars, 1 uppercase, 1 lowercase, 1 digit, 1 special char) is applied by default, but can be strengthened in agreement with the Association.

1.3. Administration of Users and Roles

Each user belongs to an organization and is assigned one or more roles (e.g. Club Admin, Referee, Competition Manager, etc.). The structure of roles in COMET follows a generic hierarchical structure, where the authorizations of an individual user depend on:

  • her/his granted roles – giving the authorization to carry out certain functions, or view certain data
  • her/his organization – limiting the scope of given authorizations to the organization of the user, and the organizations below in the hierarchy.

Such a structure is easy to manage, while at the same time highly robust and flexible, and allows declarative configuration of authorizations in every step of the process workflow.

Authentication

2. USER SETTINGS

2.1. Design Themes

Various themes are used to customize COMET user interface to fit the preferred visual style of each user.

2.2. Languages

The superior modular design allows great flexibility and adaptability of the system, which is today adjusted to more than 30 languages, including English, Spanish, Arabic, Russian, etc.

2.3. Profile Update

Users can edit their user account data, such as e-mail, phone number, or photo. They can initiate security-related procedures, such as requesting to update their password.

Theme Settings

3. TENANT CONFIGURATION

3.1. Countries

The list of countries is used for e.g. player’s country of birth, referee’s nationality, or club’s address.

3.2. Currencies

The list of currencies is used for e.g. payments for disciplinary sanctions, player’s transfer value, or referee match expenses.

3.3. Notifications

COMET has advanced notification features and communicates with users automatically via e-mail and push notifications. Notifications can be triggered by an action in COMET (e.g. registration status changed) or by a recurring procedure (e.g. daily reminder on expiring contracts). For example, referees are notified that they have been appointed to a match when the status of the match is changed from Entered to Scheduled.

3.4. Workflows

All our customers operate exactly the same version of COMET, yet all have very different configurations of process workflows. The workflow elements, such as statuses, status transitions, transition triggers, status-specific authorizations, can be configured to the needs of the association.

3.5. Validations

Validations are sets of measures used to check the compliance of any action with its purpose and functions. E.g. a player who was born in 1985, cannot play in a U-15 youth competition.

3.6. Recurring Jobs

Jobs can be configured to carry out certain actions in the system in a recurring manner. E.g. a nightly procedure can be setup to explicitly terminate all the coach licenses that have expired.

4. AUDIT LOG

4.1. Contexts

Each and every read/write transaction is logged in different contexts (Login, Person, Organization, Match…) and securely stored, including username, timestamp, IP address, and all relevant transaction data (e.g. when an update transaction is committed, the Audit Log stores the old and new value of the field).

4.2. Filters

The audit log can be filtered by category, time interval, username, name, organization and IP address.

4.3. IP address tracking

The IP address of the client request is tracked as part of transaction logging (Black box).

5. SEARCH

5.1. Quick Search and Advanced Search

A Quick Search field is always accessible in the upper-left part of the screen and can be used to access any piece of information in COMET. If more complex search criteria are required, advanced search functionality is available for all entities.

5.2. Indexing

COMET uses indexing for arranging documents systematically (collecting, parsing and storing of documents). It is done to increase the speed and performance of a search query while finding a required document.

5.3. Autocomplete

COMET uses Autocomplete, which is a very useful tool, that makes suggestions to the user as she/he types data into a field, similar to any contemporary search engine, such as Google.

6. ORGANIZATIONS

6.1. Associations

Code list containing Associations, and other similar organizations, is managed by administrator and superuser. Superusers can add, edit and inactivate existing associations in the list.

6.2. Sub-organizations

Some organizations have relations such as parent-child, e.g. National association is the parent organization to Regional association. In case the user is registered for an organization, he/she will be able to work with the organizations below in the hierarchy.

6.3. Officials Registration

All the organization’s administrative officials may be registered in COMET. Example registration types are: President, Manager, Secretary, Agent, Media officer, Referee instructor, Steward, etc.

7. PERSONS

7.1. Unique ID Validation

All persons registered in COMET have only one unique COMET ID for their lifetime. e.g. the Player can be the Coach, or the Referee can be the Referee assessor at the same time with the same ID provided after the first registration. COMET has a deduplication mechanism that prevents creating users with the same National ID (government-issued) if available, or similar personal data (e.g. Name + Last Name + DOB).

7.2. Titles and Licenses

Titles and licenses, such as e.g. UEFA B Coach License, are stored in the additional info tab. Information important for licenses and titles are: number of the document, document type, issued by, date from/to.

7.3. Identification Documents

Identification documents, such as Passport, Visa, or National ID, are stored in the additional info tab. Information important for ID documents are: number of the document, document type, issued by, date from/to.

8. CONTACT MANAGEMENT

8.1. Regions and Places

The list of regions and places are used e.g. for player’s region/place of birth or club’s address. A place may belong to a specific region. Regions and places are initially imported into COMET usually from an official source, and are always selected from a list. Some smaller countries do not use regions.

8.2. Map View

COMET may locate stadiums and other locations (e.g. club addresses) on the map using Google Maps, or other geolocation services such as Yandex.

8.3. Contact Types

Various contact types can be added to the system, and applied to organizations and persons. The most common ones are address, mobile number, e-mail. We also allow tracking of social accounts, such as Facebook, Instagram, Twitter, vKontakte, etc.

Contacts

9. DOCUMENTS AND PICTURES

9.1. Upload

Various pre-configurable documents types (photos, logos, competition regulations, ID copy…) can be uploaded into the system.

9.2. Preview

For certain file types (PDF, photos), uploaded documents can be previewed in the system, without being downloaded.

9.3. Type Management

Different types of documents can be defined for each profile or module. E.g. in player’s profile – photos, passport and contract; in club’s profile – logo and club’s statute; in stadium’s profile – photos and club licensing certificate.

9.4. Constraints

Document constraints limit the type of data (e.g. PDF, PNG, JPG only) or file size (e.g. 10MB max) of a document uploaded in the system.

9.5. Photo and Logo Upload

Photos are uploaded to person profiles e.g. profiles of referees, players, team officials, etc. Logos are uploaded for clubs, associations and competitions. Photos and Logos are used on match lineups, reports, ID cards, etc.

9.6. Photo Capture

Instead of uploading a person’s photo, there is an option to capture the live photo by using the web camera attached to your PC or laptop.

9.7. Crop and Rotate
Photos can be cropped and rotated in the system. Since these photos are used for documents such as reports, it’s important to remove unwanted outer areas.

9.8. Resizing and Optimization

Altering of the file size of the captured photo is executed automatically on upload, for performance reasons.

10. ID CARDS

10.1. Templates

ID card templates can be added to the specific competition or in the administration module through the ID Card template console.

10.2. Roles

ID cards for different roles in the system can have different designs and logos.

10.3. QR Code

ID cards may incorporate a QR Code for purpose of retrieving data, and authenticating the owner of the card.

10.4. Configuration Console

Administrators and superusers have access to the Administration section and configuration console for the ID cards (electronic and printed).

10.5. Electronic Format

An electronic (PKPass) format of ID cards is available. It has fewer possibilities when it comes to design, but more flexibility when it comes to presented data, and does not require printing and physical distribution (it is distributed via e-mail). Therefore, we strongly recommend using the electronic format of ID cards.

IDs

11. CUSTOM ATTRIBUTES

11.1. Definition

Beyond the standard/default fields, additional custom attributes can be added and defined by superusers/admins to profiles of Players, Coaches, Referees, Organizations, Stadiums.

11.2. Validation

Validation is applied to the custom attribute, e.g. if the field is mandatory, the profile cannot be saved without populating this field.

11.3. Attribute Types

Different attribute types are available in the system, such as: text fields, checkmarks/booleans, dates, numbers, dropdowns and files.

12. SUPPORT MODULE

12.1. Workflow

Analyticom supports superusers via its electronic support/incident system. Once the incident has been escalated to Analyticom, support team members categorize it into any of the predefined categories, such as a defect, information provision, data manipulation, configuration, etc. Users will be notified of every status update.

12.2. Consoles

The Help console connected with our incident system is built into COMET. All users can access the system however, only superusers can track the tickets which were sent by other users in their association.

12.3. Status

Once the ticket has been created, the status is set to: Open. If our support agent needs more information, the status will be changed to Waiting. If the ticket is clear and categorized, the status will be changed to In progress. Resolved tickets are closed and inactivated.

12.4. Notifications

An automated e-mail notification will be sent to the user on every status change of the ticket.

12.5. Assignment

Superusers need to review the incoming tickets and decide what to do next. If the ticket is clear and can be resolved by Superusers, they can “Accept“ a ticket as their own task.

12.6. Escalation

If the Superuser assigned to the ticket cannot resolve the issue, he/she can escalate the ticket to the next support level (i.e. COMET support team).

12.7. Knowledge base

COMET Knowledge base provides user reference documentation in relation to all COMET functional modules, and is a valuable resource for end-users. It is available in English language.

Support Tickets

13. ENTITY NAMES

13.1. Short Names

The most prominent entities in the system (Organizations/Associations, Clubs, Competitions, Facilities) have not only a formal (and usually longer) name, but also a short name that is used for convenience in reporting and on public websites and apps. For example, the formal name of the club in COMET is “HNK Hajduk Split š.d.d.”), while its short name is “Hajduk”. The full name is used in official processes such as player registration, while the short name is used in most reports and public sources, e.g. in league standings.

13.2. International Names

In Associations where the local alphabet is not Latin, on top of default/local names, we also operate international names of Organizations/Associations, Clubs, Competitions, Facilities, Persons. The international names are used primarily for international competitions, international transfers, and in general for presenting relevant data to international audiences (e.g. matches, standings and statistics in English version of the Association’s website).

13.3. Person Names

The structure of Person Names can be adjusted to the specifics of the Association’s country. E.g. in most countries there are 2 official person names (first name and last name), in the Middle East there are 3 official names, while in South America there are 4 official names (2 first names and 2 last names).

Back