K
Kalman ControlInstrumentation and Industrial Automation Engineering
Project Dashboard
User Manual

Kalman FAT Suite — Complete User Manual

Industrial FAT/SAT execution, project access control, offline-first test management and professional report generation.

Kalman FAT Suite is designed for structured FAT/SAT execution in industrial automation projects.

The project structure is Project → Test Area → Test Package → Test Item. A Test Item can be an IO signal, HMI screen, alarm, sequence step, communication point, cybersecurity check, cabinet check or documentation check.

Projects can be shared with other users by email using project roles: Owner, Admin, Tester and Viewer.

The software is offline-first: changes are saved locally in the browser first and then synchronized to the cloud when a connection is available.

Project Workspace
Project WorkspaceCreate projects, see your role badge, open assigned projects, manage access and download the Excel template.
Execution Dashboard
Execution DashboardMonitor progress, final readiness, test criticality, cybersecurity summary and package completion.
Test Package Table
Test Package TableExecute signal checks, set status and criticality, add comments, tester, witness, punch actions and evidence.
Project Navigation
Project NavigationUse the sidebar to open project information, references, attendance, report notes, test areas, packages and report view.

Recommended workflow

  1. Create a demo project to learn the process, or create a blank project for a real customer project.
  2. Download the Excel template and fill project information, IO list, packages, reference documents, attendance and notes.
  3. Open the project and use Import Excel to prepare the project database quickly.
  4. If needed, open Access Management and invite Admins, Testers or Viewers by email.
  5. Review Test Areas and Test Packages before starting execution.
  6. Execute each Test Item and set its status: Passed, Failed, Punch, Blocked or N/A.
  7. Add comments, evidence, attachments, tester, witness and punch actions where needed.
  8. Review the Execution Dashboard for progress, final readiness, test criticality and cybersecurity summary.
  9. Open FAT Report & PDF, review the report and save it as an A3 landscape PDF.

Project Dashboard

  • Create oil & gas demo project: creates a realistic demonstration project with architecture, IO, functional tests and cybersecurity checks.
  • Create blank project: starts from an empty project structure. The creator becomes Owner automatically.
  • Download FAT Excel template: downloads the import workbook for customer project preparation.
  • Project list: shows owned and assigned projects with a role badge (Owner / Admin / Tester / Viewer).
  • Project actions depend on your role: rename, customer, Access Management and delete are shown only when permitted.
  • Platform admin links (All Projects / Analytics) remain separate from project-level Admin role.

Project access and roles

Each FAT project can be shared with multiple users by email address.

Access is enforced in the database, not only by hiding buttons in the user interface.

Users invited before they register will see assigned projects after they sign in with the same email.

Roles

OwnerProject creator. Full control including structure, settings, members, import/export and project deletion. Cannot be removed or downgraded by another Admin.
AdminCan edit structure, settings, reports, import/export and manage members (add Admin, Tester or Viewer). Cannot delete the project or change/remove the Owner.
TesterCan execute tests, enter results, comments, punch actions and evidence. Cannot change test structure, import Excel, edit settings or manage members.
ViewerRead-only access. Can open the project, review data and export/view reports. Cannot execute tests or change any project data.

Access Management

  • Open Access Management from the project toolbar or from the project card on the Project Dashboard.
  • Owner or Admin can add a user by email and assign Admin, Tester or Viewer.
  • Pending invites appear until the user signs in with the matching email address.
  • Owner or Admin can change roles or remove members. Owner membership is protected.
  • The Access Management panel includes an audit trail of membership and permission changes.

Security

  • Unassigned users cannot see or open a project, even with a direct URL.
  • Tester saves are restricted server-side to execution fields only (status, comments, evidence, attendance and report notes).
  • Testers cannot modify test areas, packages, procedures, project settings or member assignments through the API.
  • Duplicate membership for the same email is prevented using case-insensitive matching.
  • Future company accounts and Microsoft Entra ID / Azure AD SSO are prepared in the database schema but not yet enabled in the UI.

Offline and revoked access

  • Offline drafts are only restored if the user was previously authorized online on the same browser.
  • If access is revoked while a user is offline, the local draft may still exist on the device until browser data is cleared.
  • When internet returns, cloud sync is rejected if the user no longer has permission.

Main menus and buttons

  • Execution Dashboard: progress, final readiness, criticality summary, cybersecurity summary and package progress.
  • Project Information: project metadata and report template settings such as logos, document number, revision and footer text.
  • Access Management: invite users, change roles, remove members and review the access audit trail (Owner/Admin only).
  • Reference Documents: project drawings, IO lists, cause/effect matrix and other FAT basis documents.
  • Attendance & Signatures: participants and signature placeholders.
  • Report Notes: general notes included in the report.
  • FAT Report & PDF: professional report preview and PDF print/export workflow.
  • Add Cybersecurity FAT/SAT Module: adds the predefined cybersecurity checklist (Owner/Admin only).
  • Search / Next Open / Next Failed / Next Punch: fast navigation during execution.
  • Export Workbook: exports the current project as an Excel backup.

Test status legend

Not StartedThe test exists but has not been executed yet.
PassedThe test was completed and accepted.
FailedThe result is not acceptable and requires correction or retest.
PunchAn issue exists but can be tracked as an action item, subject to project acceptance rules.
BlockedThe test cannot be executed because a prerequisite, document, configuration or condition is missing.
N/AThe test is not applicable to the project scope.

Test Criticality

The software uses Test Criticality instead of a complex risk matrix. This keeps the report simple, useful and understandable for customers.

StandardNormal FAT/SAT verification item.
ImportantImportant for operation, quality, documentation or handover.
CriticalCritical FAT/SAT item. Failed or Blocked status blocks final report readiness.
Safety RelatedFunctional safety, ESD/PSD/F&G, trip, permissive, interlock or protective action. Failed or Blocked status blocks final readiness.
Cybersecurity CriticalCybersecurity item that must be accepted before final readiness. Failed or Blocked status blocks final readiness.
Test Criticality is a practical FAT/SAT prioritization and readiness-control field. It does not replace HAZOP, LOPA, SRS, SIL determination, IEC 61511 verification or IEC 62443 compliance assessment.

Functional Safety / F-IO

  • For F-IO, trip, interlock, ESD, PSD or Fire & Gas tests, set Test Criticality to Safety Related.
  • Use Safety Function Type to classify the item, for example ESD, PSD, Fire & Gas, Trip Input, Trip Output, Permissive / Interlock or Safety Alarm.
  • Use SIL Relevance only as informational data copied from the project SRS or functional safety documentation.
  • The software does not calculate SIL and does not replace HAZOP, LOPA, SRS, validation or IEC 61511 verification.

Cybersecurity FAT/SAT

  • The Cybersecurity FAT/SAT Module adds a predefined checklist for practical FAT/SAT verification.
  • It covers asset identification, user accounts, password policy, backup/restore, endpoint protection, hardening, firewall rules, segmentation, remote access, USB policy, time synchronization, patch review, administrator access, switch backup, VLANs and zones/conduits.
  • The module does not perform network scanning and does not calculate official IEC 62443 compliance.
  • Use Cybersecurity Domain to group items such as Identity & Access, Network Segmentation, Hardening, Backup & Recovery, Remote Access, Patch Management and Zones & Conduits.

Offline-first behavior

  • Every change is saved locally first in the browser.
  • If internet disconnects, continue working in the already-open project if you still have execute permission.
  • When the connection returns, the offline draft synchronizes automatically if access is still valid.
  • Recovery works on the same device, same browser profile and same domain. Do not clear browser/site data before synchronization.

Report and PDF workflow

  1. Open FAT Report & PDF.
  2. Review the cover sheet, document control, definitions and legend, table of contents, project information, progress, criticality, cybersecurity summary, punch list, evidence appendix and detailed records.
  3. Use Print / Save as PDF.
  4. Recommended print settings: Paper size A3, Layout Landscape, Scale 100% or Actual Size, Pages per sheet 1, Background graphics enabled.
  5. Final report readiness is blocked if any Critical, Safety Related or Cybersecurity Critical item is Failed or Blocked.

Customer responsibilities

  • Verify imported project data before starting FAT/SAT.
  • Make sure project documents and acceptance criteria are approved.
  • Use Test Criticality consistently before execution.
  • For safety-related tests, use SRS/SIL information from the official safety documents.
  • Review punch items and deviations before final report acceptance.
  • Assign project roles carefully so only authorized users can change structure or execute tests.