To the website Download PDF

documentation

IGNIS 2AB manual

User and administration guide for digital fire department management - from getting started to operations, licensing and MP-FIRE import.

Edition 1.2 As of August 26, 2026 Product status cbf05b51

Languages and translation coverage · REL-20261008-06

Select German or English under Security and language in your account. Release REL-20261008-06 adds 123 missing English and three German translation keys, plus translations for personnel navigation, participant selection, medical validity guidance and the clothing catalogue. Some hard-coded German text remains. Passing automated key checks does not mean the entire interface is English. Names, free text and existing business records are not translated automatically.

Validation: 345 automated tests with 3900 assertions passed; translation and template syntax checked. This is not a complete manual acceptance test of every role, mail delivery path or workflow. Current versions: REL-20261008-06 on App, DEM.REL-20261008-06 on Demo and DEV.REL-20261008-06 on Dev. Versions in older sections describe their historical release.

Rate limits and error pages · REL-20261008-05

Error pages show the crest on a light tile with a high-contrast wordmark. For error 429, the actual server-provided waiting time appears as a countdown and earliest retry time. No duration is guessed when timing information is unavailable. Without JavaScript, the time remains visible. Requests are never retried automatically; another limit may still apply after the countdown expires.

Security limits are unchanged: login allows 5 attempts per account/IP combination in 15 minutes, with additional IP protection. Invitation actions: 10 POST requests per IP per hour. Registration and password reset: 5 requests each per IP per hour. API: capacity 120, replenished by 120 per minute. Users sharing a public IP share its limits. Waiting time depends on the relevant limiter; there is no universal lockout duration. No general application limit is configured for ordinary page views.

Current release: REL-20261008-05 (App), DEM.REL-20261008-05 (Demo), DEV.REL-20261008-05 (Dev). Earlier version references below are historical. Review covers affected error pages, limits and documentation references, not a complete acceptance test of every older feature.

Deletion protection · REL-20261008-04

Department leaders and secretaries cannot delete saved records. This includes direct requests, documents, photos, assignments and bulk deletion. Editing remains available within existing permissions. Active city/tenant administrators may delete only when existing scope and reference checks permit it. An additional administrator role in the same tenant takes precedence. Platform administrators remain subject to existing support-access rules.

Archiving and deactivation show a confirmation. Existing data is retained. Not every module offers archiving; no universal recycle bin has been added. Existing audit logs record changes and deletions. Unsaved order lines remain editable. Replacing a photo or editing an assignment remains an editing operation.

Current release: REL-20261008-04 on App, DEM.REL-20261008-04 on Demo and DEV.REL-20261008-04 on Dev. Earlier release numbers below are historical. Documentation review covers changed permissions, workflows and navigation references, not a complete acceptance test of every feature.

PDF orders and training requests · REL-20261008-03

The central fire-protection/order address applies to every department in the tenant. Authorised administrators maintain it under Central order delivery at the main department or in the tenant form; both edit the same stored value.

  • Clothing: PDF on submission and order changes.
  • Warehouse, materials and consumables: PDF when a warehouse order is placed.
  • Training: PDF on request submission, approval, rejection or cancellation.

The PDF contains the record ID, tenant, items and available context. Missing prices are not shown as zero. Requests do not replace approval and are not automatically sent to suppliers or training providers.

If the address is missing or delivery fails, the record is preserved and a warning reports that the message was not sent. Automatic retries are not currently provided; notify the central office manually. Updates do not retrospectively mail existing records. Internal exercises and evidence records alone do not trigger order emails.

8 October 2026 · REL-20261008-02

This supplement describes the verified changes of 8 October. Older chapters remain as background; the following guidance supersedes conflicting navigation and workflow descriptions.

Navigation and import

Orders are under Administration (Verwaltung). Licences and tenant users belong to Organisation; platform administration manages global accounts. MP-FEUER uses a supervised server import with preview and reviewed approval, not the upload menu described in the older chapter.

Medical fitness

The issue date must be before today. Suggested validity is one year for over-67 and ASÜ, three years for G26, and five years for driving fitness. G41 is manual. These are form suggestions, not clinical rules; the certificate governs. Manual corrections are preserved unless Recalculate is explicitly selected. Date fields are aligned, with guidance below.

Participants and vehicle crews

Children/youth exercises and other operations allow initial selection of people from the selected department before saving. Filtering preserves selections; Select all affects visible people only. Attendance is confirmed separately afterwards. Vehicle crews support multiple simultaneous roles: incident commander, GF, AGT, MA and EK, defaulting to EK if none is selected. Additional personnel can be recorded without a vehicle.

Clothing pools

Municipal administration manages all tenant pools; local leadership manages its own department pool. City fire leadership can view the central municipal pool. Clothing supports authorised pool transfers, personal issue and full return with history. Children/youth pool stock appears alongside personal clothing in the children/youth overview.

Quarterly allowances

Children and youth are generally excluded from the EUR 7 allowance. Youth qualify after a documented passed TM1 examination, including youth-only exercises, assessed at the activity date. Column headings link to their activities. Light category backgrounds and dark centred text replace solid colours without changing amounts.

Versions and review limits

Current identifiers are REL-20261008-02 (App), DEM.REL-20261008-02 (Demo) and DEV.REL-20261008-02 (Dev). Older build examples are historical. This review is not a complete acceptance test of every feature, role, email path or import.

I2

Digital fire department management

Edition 1.2
Product status cbf05b51 · August 8, 2026
German · Role-oriented operation

Document conventions

Labeling Meaning
action A concrete sequence of operating actions.
Notice Additional information or role-dependent behavior.
Danger Action affecting data, rights or operations.
Administration only Feature for tenant or platform administration.

1. System overview

IGNIS 2AB bundles personnel, operations, technology, warehouse, organization, training, finance and administration in a multi-client web application.

1.1 Terms

Expression Explanation
Client/Organization Independent municipal data room, usually a city or municipal fire department.
Main fire department Central administrative unit of the client.
Local fire department Subordinate fire department with its own data and responsibilities.
Active fire department The currently selected fire department; it determines the visible data stock.
Org ID Unique identifier of the organization.
Site ID Unique identifier of an individual fire department within the organization.
Installation ID Unique UUID of the operated IGNIS installation for license verification.

1.2 Main areas

Additional areas may be visible depending on the expansion and license status. A menu item that is not visible does not automatically mean an error; Role, module release or fire brigade assignment are often missing.

1.3 Authorization principle

2. Registration and personal settings

2.1 Login

  1. Open your instance's URL, for example app.ignis2ab.com.
  2. Enter email address and password.
  3. If necessary, confirm the second factor.
  4. After successful registration, the overview of the primarily assigned fire department appears.

2.2 Forgotten password

  1. On the login page, select “Forgot password”.
  2. Enter the registered email address.
  3. Open the time-limited link from the email.
  4. Assign a new password that will only be used for IGNIS 2AB.

2.3 Security and language

Click on the username in the top right corner and open “Security”. The password and supported language can be changed there and – if activated – two-factor authentication can be set up. The system productively supports German and English.

2.4 Logging out

Always use the logout function in the user menu, especially on shared workstations. Closing the browser window does not replace logging out.

3. Surface and fire department change

3.1 Navigation

Area function
Left sidebar Opens specialist modules and their submenus.
Top bar middle Shows the active fire department.
Top bar on the right Username, security and logout.
Breadcrumbs Shows position in the system and enables jumps back.
Action icons Open, edit, delete, download or send - depending on the role.

3.2 Change active fire department

  1. Open the fire brigade selection in the top bar.
  2. Select the fire department you want.
  3. If possible, IGNIS 2AB stays in the current specialist mask and loads its data for the new fire department.
  4. Always check the “Active Fire Department” display before creating or editing.

4. Overview

4.1 Home page

The overview summarizes the most important information from the active fire department. Tiles and key figures depend on role and activated modules.

4.2 Anniversaries

Age anniversaries from the age of 50 are planned in fixed stages as well as service anniversaries of 10 years or more. The basis is correctly maintained birth and entry dates.

5. Personnel

5.1 Personnel overview

The personnel overview only shows people from the active fire brigade authorized by the user. Rank, functions, department and status are determined from the respective assignments.

5.2 Create person

  1. Open Human Resources > Human Resources.
  2. Select the icon to create a person.
  3. Check the active fire department.
  4. Enter master data, entry, contact details and department.
  5. Have the personnel number assigned automatically or explicitly activate manual assignment.
  6. Save the record.

5.3 Personal profile

5.4 Ranks and functions

Ranks and functions are maintained via time-related assignments. Changes should not be documented by overwriting the history, but rather by ending the old assignment and beginning a new one.

5.5 Member Groups

The assignment depends on the professional status. Age-dependent suggestions do not replace the examination by the responsible administration.

5.6 Organization chart

The graphical personnel organization chart represents functions, ranks and hierarchies as vertically as possible. Missing elements are caused by missing or inactive assignments.

5.7 Loss of earnings

Loss of earnings data contains confidential employer and compensation information. They are only visible to explicitly authorized administrative roles. People with a complete data record are highlighted in the selection.

6. Training, courses and qualifications

6.1 Catalogs

Ranks, qualifications, courses, technical equipment standards and other catalogs are provided as expandable standards for new fire departments. Changes apply within the respective client.

6.2 Book training

  1. Open Personnel > Qualifications and Equipment > Training Applications.
  2. Choose a person and a training.
  3. Enter the appointment and required information.
  4. Submit the booking.
  5. The administration approves or rejects with comment.

6.3 Status

status Meaning
Under examination Booking has been submitted and awaiting decision.
Approved Participation was approved by the administration.
Rejected Booking was rejected with reasons.
Canceled An existing booking has been canceled.
Completed Participation and results were documented.

Planned and approved training courses also appear in the person profile so that parallel shadow lists are not required.

7. Operations and reports

7.1 Create an assignment

  1. Open Assignment & Service > Assignments > Create Assignment.
  2. Check the active fire brigade.
  3. Enter the type, period, location and short description.
  4. Assign personnel, vehicles, equipment and materials.
  5. Save and add to the history if necessary.

7.2 Resources involved

7.3 Mission report

A report can be generated from the operation, checked, printed and sent by email. The fire department logo is used on appropriate reports and certificates; Local fire departments can inherit the logo of the main fire department.

7.4 Facilities and Shipping

Photos and documents are stored privately and client-specific. Approved attachments are taken into account when sending emails. Before sending, check the recipient, contents and personal information.

7.5 Certificate of participation

Certificates of deployment or participation can be created for people involved. The output depends on the documented operating times.

8. Exercises, briefings and operational readiness

8.1 Exercises

Exercises are recorded separately for the operations department, youth fire brigade and children's fire brigade. People involved, content, duration and evidence can be documented.

8.2 Instructions

Instructions and instructions have participants, validity and documentation status. Due repetitions should be checked regularly.

8.3 Personnel traffic lights and respiratory protection

The personnel traffic light evaluates mission-related requirements. In the respiratory protection area, medical validity, stress training, instruction and mission-related training are managed.

8.4 Scheduling and standby

Services, staffing and availability are planned and people are assigned. Actual visibility depends on module release.

9. Vehicles

9.1 Manage vehicle

9.2 Equipment list

The equipment list assigns devices and materials to a vehicle. When changing the active fire department, only vehicles and items from this fire department are offered.

9.3 Tests and repairs

Exams are maintained as recurring events with date, result, due date and evidence. Repairs are reported, processed and completed in a comprehensible manner.

10. Devices and radio technology

10.1 Devices

Devices always belong precisely to a fire department. Categories and device standards can be expanded. Inspections, maintenance, repairs, expenses, returns and retirements are documented as lifecycle events.

10.2 Radios

Field use
Manufacturer/Model Standardized for Motorola and Sepura, among others.
Device type Handheld radio or fixed installation in the vehicle.
Serial number Manufacturer-related unique number.
ISSI / TEI Identifiers in digital radio.
BSI card number Assignment of the security card.
Explosion protection Indicates devices intended for this purpose.
vehicle Mandatory assignment for permanent installation, if known.
Call name / speaking group Operational radio configuration.

10.3 Generic Tests

With AssetInspection, inspections of different types of devices can be recorded uniformly. AssetLifecycleEvent represents maintenance, repair, issue, return and disposal.

11. Stock and Orders

11.1 Inventory

Stocks belong to a fire department. Items, storage locations, minimum quantities and available quantities form the basis for movements and order proposals.

11.2 Movements

Occurrence Result
Goods receipt Increases inventory with documented quantity and origin.
output Reduces inventory and documents recipient or purpose.
return Returns returned material to inventory.
Inventory Compares target and actual inventory in a comprehensible manner.

11.3 Orders

Under Organization > Orders, all order types are brought together, not just clothing. Administrative roles can open, review, accept, or reject orders.

12. Organization

12.1 Fire departments

The organizational administration represents main and local fire departments. Every organization has an Org ID, every fire department has a Site ID. Vehicles, devices, inventory and technical data remain assigned to the respective site.

  1. Open Organization > Fire Department.
  2. Select the fire department to edit.
  3. Upload the logo in the supported image format.
  4. Check appearance in sidebar and on a report.

If a local fire department does not have its own logo defined, the logo of the main fire department can be used.

12.3 Merge the local fire department into the main fire department

For imported dual structures, a selected local fire department can be transferred to the main fire department. Associated specialist data is reassigned in a controlled manner. A backup must be created beforehand and the result checked in a test instance.

12.4 Organizational chart

The fire brigade organizational chart graphically represents the main fire brigade and subordinate local fire brigades. It serves as orientation and does not replace a license or authorization check.

13. Licenses

13.1 License model

type Validity
M license Client or main fire department and central administration.
S license Individual affiliated local fire department; requires an active M structure.
Trial Time-limited test operation.
Read only Reading operation after expiry or deactivation; Data is retained.

13.2 Check license status

  1. Open Organization > Licenses.
  2. Select “Check License Now.”
  3. Check connection, status, operating mode, validity and last check.
  4. Check the indented list of local fire departments and their individual status.

Each check uses Org ID, Site ID, and Installation ID. The license server shows registered installations and the time of the last successful query.

13.3 After an update

A software update must not overwrite an active license configuration. If the system still shows “Subscription inactive”, first run a manual license check and then check the connection, tenant key and installation ID.

14. Users, Roles and Rights

14.1 Create user

  1. Open Administration > Users.
  2. Set email address and display name.
  3. Assign the user to a client.
  4. Select role and responsible fire department.
  5. Activate access and transmit the access data securely.

14.2 Typical roles

role Typical purpose
Platform Super Admin System-wide administration, import and technical support.
Tenant Administrator Organization, users and settings of the tenant.
Administration Personnel, orders, training approvals and confidential administrative processes.
Military management Operational management of the assigned fire department.
user Personal and professionally approved functions.

14.3 Fire department assignment

The primary or managed fire department determines the start context and processing area. A local fire service user is not allowed to edit their specialist data by switching to another local fire department.

14.4 Deactivate and delete users

Users are deactivated first. Before deletion, the system checks existing references and prevents self-deletion. Deletions are audited.

15. Import from alternative systems

15.1 Requirements

15.2 Workflow

Import is supervised using the app:import:mpfeuer server command. Review backups, isolated preview and mappings before approving import.

15.3 Client identification

If a client does not yet exist, it is suggested from the backup department master data. Fire department name, municipality, postal code and technical identifiers must be checked before takeover.

15.4 Import log

The log stores source system, source ID, checksum, target object and alerts. This makes repetition, assignment and error analysis comprehensible.

15.5 Follow-up inspection

16. Administration and system operation

16.1 Audit Log

The audit log documents security-relevant changes with the client, fire department, acting user, action, time and technical metadata. The current automatic retention period is three months.

16.2 Sending emails

System emails are sent via the centrally configured SMTP connection. Check sender, server, port, STARTTLS, authentication and reachability. Credentials must not be in the manual, Git or support ticket.

16.3 Standards

When a client is created, the standard catalogs provided are initialized. These include, among other things, ranks, qualifications, courses and technical categories. Standards can be expanded, but not changed in an uncontrolled manner across clients.

16.4 Build Display

system Scheme
Development DEV.B01.XXXX
Demo DEM.B01.XXXX
production Build.B01.XXXX

17. Data protection and information security

17.1 Basic rules for users

17.2 Special Data

Health data, information from minors, loss of earnings and participation in missions require special access restrictions. A visible function is not permission to access data without a technical purpose.

17.3 Documents and photos

Uploads are stored in private, client-specific directories. Acceptable types and sizes are checked; Files are given internal UUID names and SHA-256 checksums. When deleting a data record, it is important to check whether linked documents can also be deleted or must be retained.

17.4 Rights of those affected

Requests for information, correction, deletion or restriction are sent to the responsible municipality or its data protection contact. Exports must be checked for identity, completeness and third-party data before handover.

18. Error Help

18.1 Common Situations

symptom Test/measure
Menu item is missing Check role, active fire department, module release and license status.
403 Forbidden Check authorization, CSRF token, session and fire department association.
404 Not Found Check URL, deployed build, route and access to the target object; unauthorized objects may intentionally appear as 404.
500 Internal Server Error Note time, user, URL and action; Check application log and container status.
Nothing clickable after login Clear browser cache, log in again and check delivered assets/build.
License inactive Manual check, accessibility of license.2ab.it, check keys and IDs.
Email delivery fails Check SMTP authentication, STARTTLS, sender approval and server log.
Data missing after fire department change Check active fire brigade and technical object assignment.

18.2 Support message

19. Operational checklists

19.1 Daily operations

19.2 Before an update

  1. Document current build and Git status.
  2. Secure database and private uploads.
  3. Define restore and rollback path.
  4. Check migrations and dependencies in Dev.
  5. Update demo and test core processes.
  6. Define production windows and responsible persons.

19.3 After an update

20. Role-related shortcuts

Task Menu path
Create person Human Resources > Human Resources Management
Apply for training Personnel > Qualifications and equipment > Training applications
Approve training Personnel > Training applications > Under review
Create deployment Deployment & Service > Deployments > Create Deployment
Send report Open deployment > Report > Email
Put on the radio Technology > Devices > Radio technology
Vehicle loading Technology > Vehicles > Vehicle loading
Check order Organization > Orders
Change logo Organization > Fire Department
Check license Organization > Licenses
Manage users Administration > Users
Import from alternative systems Administration > Data import

Current feature status - August 2026

Role-based dashboards and deadlines

Personnel and evidence

Incidents, activities and finance

Appendix A – Release and acceptance list

Appendix B – Release Notes

This manual describes the verified product build cbf05b51 dated August 26, 2026. It is updated with every major functional expansion or every change to navigation, role model, data import or licensing.

Product name: IGNIS 2AB
Publisher: 2AB IT
Document: User and Administration Guide
Edition: 1.2

No matching content found.