License file construction
The file has the name 'aa.DAT', where 'aa' is replaced by the application code. The file shall always be located in the program directory, as it is considered as a part of the program. If the program at startup is not able to locate the file in that directory, it will automatically terminate.
The file contains a string list with the following fields:
License number in the format 'aannnnn'.
Expiry date.
Customer's name (for this license).
Customer's location(for this license).
Modules.
Additional text.
Remarks (shall not occur on the customer's screen ).
Reserved.
Reserved
Reserved.
Reserved.
Checksum.
Each of the strings above shall be separated with a fixed character.
The checksum is some kind of sum of all the preceding bytes in the string list. This in order to prevent the user from changing single bytes in the file (for instance to try and modify the expiry date or the modules).
When a license file is produced, it is encrypted before it is written to disk. The encryption will make the file unreadable, and the encryption algorithm or factor will change through the encryption.
Module overview Windows version
Below is for each windows application set up the filename for the license file.
For each application, all the different modules are listed. To the right of the module we have the code letter that this module has in the ‘nnn' behind a code, it means that 'nnn’ shall be replaced with a number consisting of 3 digits.
Onboard Manager (OW.DAT) Base Module, single user |
|
O |
Network units, per 3 users |
| Nnnn |
Personnel Manager (PW.DAT) Base Module, single user |
|
P |
Network units, per 3 users Datagruppe Vessel units, per 3 active vessels |
Gnn | Nnnn
Vnnn |
Crew units, per 100 crew Payroll, shore-side, international |
Y | Cnnn |
Payroll, shore-side, Norwegian | W |
|
Payroll, Currency Module (for Norwegian) | C | |
UK Tax | U | |
Report Generator, Design Program | R | |
Demo version | D | |
Leave days Accounting | L | |
Registering Data Only | T | |
Fleet Manager (FM.DAT) | ||
Base Module, single user | F | |
Adonis Link (AL.DAT) | ||
Base Module, 2 sites | L | |
Multiple sites | M |
GENERAL
number of employee * 100
Number Of Employee: | C001 |
|
Number Of Vessels: | V001 |
|
Number Of Users: | N001 |
|
DATAGROUPS
P = Personal Details P only - All Datagroups // PGXXGXX –selected dgrs
2 = Customized
3 = Activities
4 = Appraisals
5 = Competence
6 = Family
7 = Medical
8 = Travel
9 = Time and attendance
10 = Documents'
11 = Medical Insurance'
12 = Personal Rotation
13 = Onboard Pay Scale and Rank
14 = Flight Details
MODULES
Y = Payroll
M = Time Cards
B = Crew Planning
Q = Rotation
X = Crew Change
Z = Cabin Allocation
J = Travel
F = Global Operations
I = Requisition and Invoicing
H = Ports
K = Contacts
S = Organizer
E = Documents
A = Analysis
R = Report Generator
I = Replicator
U = Direct dialup
W = Payroll Shore-side Norwegian
C = Payroll, Currency Module (for Norwegian)
L = Leave Days Accounting
Alphabetical overview of the codes
A = Analysis
B = Crew Planning
C = Crew Units (persons in the database) The letter is followed by 3 digits representing the number of users
D = Demo
E = Documents
F = Global Operations
G = Datagroup (followed by 2 digits representing the data group number)
H = Ports
I = Requisition and Invoicing
J = Travel
K = Contacts
L = Leave days accounting
M = Time Cards
N = Network users (number of concurrent APM users). The letter is followed by 3 digits representing the number of users
O = Onboard system
P = Personell system (all datagroups)
Q = Rotation
R = Report Generator
S = Organizer
T = Register data only? Will this be used, or is this available?
U = UK Tax
V = Number of vessels. The letter V is followed by 3 digits representing the number of vessels
W = Norwegian Shoreside payroll system
X = Crew Change
Y = Payroll system
Z = Cabin allocation
On the ASP solution, we only differentiate between payroll and personnel. Payroll users then get the ABC999EFHIJKLOPQRSUV999WXZ"