1
Overview

Welcome to CA V9.2.1 Pre Alpha, a deterministic workload simulation framework for constrained operational environments. This specification provides guidance for using each module of the framework.

What This Document Covers

This document describes the interface, planning instruments, analysis modules, and operational features available within the current release. Each section corresponds to a functional area of the framework.

Core Capabilities

System Requirements

Browser
Modern browser (Chrome, Edge, Firefox, Safari)
Account
Authorized user account with assigned role
Connection
Internet connection required
Display
Minimum 1280 × 720 resolution recommended
2
Conceptual Positioning

CA V9.2.1 Pre Alpha models maintenance workload as a conserved magnitude within constrained operational systems. For a defined maintenance scope, total required manhours are fixed by task definition, while temporal allocation may vary within prescribed duration and workforce limits.

The framework treats workload redistribution as a deterministic transformation subject to explicit constraints: fixed total effort, defined duration boundaries, and discipline-specific capacity limits. Daily demand is computed directly from task-level allocations and evaluated against declared workforce availability.

Framework Classification — CA V9.2.1 Pre Alpha is an analytical modelling instrument intended for research-oriented and structured scenario evaluation. It is not a certified regulatory system, operational authority, or approved maintenance planning platform.

Governing Principles

3
Access & License Key

CA V9.2.1 Pre Alpha uses license-key-based access. Users enter a valid license key to access the framework with their assigned role and permissions. A guest mode is also available for read-only evaluation.

Access Flow

The access sequence follows a three-step process:

  1. Navigate to the CA V9.2.1 Pre Alpha welcome page in your browser.
  2. Select Enter Access Key for licensed access, or Continue as Guest for read-only evaluation.
  3. If entering a license key, type your key into the access field and click Enter.
  4. On first access (or after a license update), the License Agreement is displayed. Read and accept the terms to proceed.
  5. Upon successful validation, you are directed to the framework dashboard with your assigned role.

License Key

Each license key is tied to a specific role within the framework. The key determines which tabs, views, and features you can access. License keys are issued by the administrator and validated locally using a secure hash-based mechanism. The key itself is never stored after validation — only an opaque session token is retained for the duration of the session.

Security — License keys are validated against a SHA-256 hash registry. No license keys are transmitted to external servers or stored in browser storage. Session tokens are generated using cryptographically secure random values and exist only for the active browser session.

Guest Access

Guest mode provides read-only access to the framework for evaluation purposes. No license key is required.

  • Available views: Dashboard, Allocation Matrix, and Plan Summary.
  • Restrictions: Guests cannot edit project data, allocate staff, create users, or manage project settings.
  • Display: The user badge shows the guest label with a read-only indicator.
  • License Agreement: Guests must also accept the License Agreement on first access.

First-Time Access

Role Assignment Required — Licensed access requires a valid license key issued by the administrator. Your key encodes your role, which determines your access level within the framework. If you do not have a key, contact your administrator to request one. See Section 6: User Roles for available roles.

Signing Out

To sign out, click your user badge in the header bar (which displays your name and role), then select Sign Out. The session token is destroyed and all satellite windows (Display, Charts, Load Shaping Console) close automatically.

4
Project Structure (Planner)

The Project Structure tab is where maintenance work breakdown is defined and managed. Projects are organized in a tree hierarchy that models how maintenance work is structured.

Tree Hierarchy

Root (Organization) ├― Project (e.g., "Scheduled Maintenance Event") │ ├― Asset (e.g., "Asset 1001") │ │ ├― Group (e.g., "Structural Systems") │ │ │ ├― Activity (e.g., "Primary Inspection") │ │ │ │ ├― Task (e.g., "Diagnostic Scan Panel 4L") │ │ │ │ └― Task (e.g., "Visual Inspect Frame")

Adding, Editing, and Deleting Nodes

  1. Add a Node: Select the parent node in the tree, then click the Add button. Enter the node name and relevant details.
  2. Edit a Node: Click on any existing node to open its editing panel. Modify the name, dates, manhours, or other fields as needed, then save.
  3. Delete a Node: Select the node and click Delete. You will be prompted to confirm. Deleting a parent node removes all its children.

Date Fields

Each node can have a Start Date and End Date. When you change dates on a parent node, the dates cascade downward to all child nodes to maintain schedule consistency. Individual child dates can be overridden after cascading.

Manhours (MH)

The MH field at the task level represents total manhours required to complete that task. This value drives demand calculations displayed on the Dashboard and is used for coverage and capacity analysis. The FTE requirement is computed as: MH ÷ (days × 8.5).

5
Workforce Categories

CA V9.2.1 Pre Alpha organizes workforce disciplines into five categories. These categories represent functional groupings used within the simulation model for demand allocation and capacity evaluation.

Disclaimer — Category labels are used as simulation identifiers within the framework. They do not imply regulatory licensing, certified qualifications, or jurisdictional authority. All categorization is for modelling purposes only.
Category Scope
Structural Systems Structural maintenance, inspection, and repair activities
Mechanical Systems Mechanical, power plant, and primary systems maintenance
Electrical & Electronic Systems Electrical, electronic, and instrumentation systems maintenance
Interior & Auxiliary Systems Interior, furnishing, and auxiliary component maintenance
Surface Treatment Surface preparation, coating, and treatment activities

Each Group node in the project tree is assigned to one of these five categories. Staff members are likewise assigned a primary discipline category, enabling the framework to compute discipline-specific demand and capacity.

6
User Roles

CA V9.2.1 Pre Alpha uses a role-based access control system with 13 distinct roles organized across three tiers. Each role determines which views a user can access and what data they can modify.

Disclaimer — Role labels are simulation identifiers used for access control within the framework. They do not confer operational authority, regulatory standing, or professional certification. All role assignments are for modelling and interface access purposes only.

Management Tier (Level 100–90)

Role Level Access Edit Scope
Administrator 100 All tabs and views, including User Management All data: projects, staff, allocations, users
Manager 90 All tabs except User Management Projects, staff, allocations, broadcast orders, forecasts

Engineering Tier (Level 80–70)

Role Level Access Edit Scope
Controller 80 Dashboard, Project Structure, Staff Roster, Allocation Matrix, Team Clusters, Plan Summary, Broadcast Order Allocations, broadcast order, staff assignments
Structural Systems Engineer 70 Dashboard, Allocation Matrix, Team Clusters, Plan Summary, Broadcast Order Allocations for Structural Systems group
Mechanical Systems Engineer 70 Dashboard, Allocation Matrix, Team Clusters, Plan Summary, Broadcast Order Allocations for Mechanical Systems group
Electrical & Electronic Engineer 70 Dashboard, Allocation Matrix, Team Clusters, Plan Summary, Broadcast Order Allocations for Electrical & Electronic Systems group
Interior Systems Engineer 70 Dashboard, Allocation Matrix, Team Clusters, Plan Summary, Broadcast Order Allocations for Interior & Auxiliary Systems group
Surface Treatment Engineer 70 Dashboard, Allocation Matrix, Team Clusters, Plan Summary, Broadcast Order Allocations for Surface Treatment group

Specialist Tier (Level 50)

Role Level Access Edit Scope
Structural Systems Specialist 50 Dashboard (read-only), Team Clusters, Broadcast Order View only
Mechanical Systems Specialist 50 Dashboard (read-only), Team Clusters, Broadcast Order View only
Electrical & Electronic Specialist 50 Dashboard (read-only), Team Clusters, Broadcast Order View only
Interior Systems Specialist 50 Dashboard (read-only), Team Clusters, Broadcast Order View only
Surface Treatment Specialist 50 Dashboard (read-only), Team Clusters, Broadcast Order View only
Note — Roles are assigned by administrators. You cannot change your own role. If your role assignment is incorrect, contact your administrator.
8
Dashboard

The Dashboard provides a real-time overview of workforce status for the selected simulation date. It is the default landing page after sign-in and presents a summary of capacity and demand.

KPI Cards

Available Workforce
Staff members available for the selected date, excluding those on off-days.
Capacity
Total manhour capacity the available workforce can deliver.
Demand
Total manhours required by all active tasks on the selected date.
Coverage Ratio
Percentage of demand covered by allocated staff. 100% indicates full staffing.

Allocation Summary Table

Below the KPI cards, the allocation summary table breaks down staffing numbers by workforce category (Structural Systems, Mechanical Systems, Electrical & Electronic, Interior & Auxiliary, Surface Treatment). Each row displays staff assigned, tasks requiring coverage, and coverage percentage.

Demand Filter by Workforce Category

Use the category filter dropdown above the KPI cards to narrow demand figures to a specific workforce category.

9
Staff Roster

The Staff Roster is the central personnel management view. Here you maintain a list of all maintenance staff, their skills, availability, and work schedules.

Adding Staff

  1. Navigate to the Staff Roster tab.
  2. Click the Add Staff button.
  3. Fill in the required fields: Name, Staff ID, Strength (primary skill), and Type.
  4. Configure off-day patterns if applicable.
  5. Save the new staff record.

Staff Fields

Field Description
NameFull name of the staff member.
IDUnique identifier for the staff member.
Strength (Skill)Primary discipline: Structural Systems, Mechanical Systems, Electrical & Electronic, Interior & Auxiliary, or Surface Treatment.
TypeEmployment classification (e.g., permanent, contract, temporary).
Off DaysRecurring off-day pattern or specific dates when unavailable.

Daily Strength View

The daily strength view displays how many staff members are available for each discipline on the selected simulation date, accounting for off-days and leave patterns.

10
Customize Strengths

The Customize Strengths tool allows you to rename, add, or remove component-level entries within each of the five workforce categories. Changes propagate to the project tree structure and to the Roster Builder module.

Accessing the Tool

  1. Open the Planning menu from the top navigation bar.
  2. Select Tools.
  3. Click Customize Strengths.

The Strength Manager modal will open, displaying all five workforce categories with their current component names.

Modal Layout

The modal presents each workforce category as a collapsible group with a coloured header matching the category colour used throughout the framework:

Category Default Components
Structural Systems Primary Hull, Secondary Structures, Control Systems, Auxiliary Structures, Access Systems, Housing Assemblies, Stabilization Systems
Mechanical Systems Ground Interface, Deceleration Systems, Hydraulic Systems, Pneumatic Systems, Mechanical Systems
Electrical & Electronic Electronic Systems, Instrumentation, Electrical Systems
Interior & Auxiliary Interior Assembly, Service Area, Auxiliary Facility
Surface Treatment Surface Coating

Editing Components

Each component is shown as an editable text input. You can perform the following operations within the modal:

Action How
Rename Click into any component text field and type the new name.
Add Click the Add button in the category header. A new empty row appears at the bottom of that category.
Remove Click the × button on the component row you wish to delete.

Saving & Resetting

  • Save — Validates the configuration (at least one component must exist), stores the custom names to local storage, and immediately updates the project tree. Component nodes in each group are replaced with the saved names.
  • Reset Defaults — Restores all five categories to the factory default component names listed above and updates the project tree accordingly.
  • Cancel — Closes the modal without saving any changes.

How Changes Propagate

When you save a custom strength configuration:

  1. The configuration is stored in local storage under the key ca_strength_config.
  2. All component-level nodes in the active project tree are updated to reflect the new names.
  3. When the Roster Builder is opened from the main application, the custom configuration is automatically passed via the URL, ensuring the Strength dropdown in the Roster Builder displays the customized component names.
  4. Staff members assigned to a renamed component retain their assignment under the new name.
Note — Customized strength names are stored per browser. If you access the framework from a different browser or clear local storage, the default component names will be restored. Use the same browser to maintain your custom configuration.
11
Allocation Matrix

The Allocation Matrix is the core simulation instrument for modelling staff-to-task assignments. It provides a grid view where rows represent available staff and columns represent active tasks on the selected simulation date.

How the Matrix Works

  • Each row represents one staff member available on the selected date.
  • Each column represents an active task requiring staffing.
  • Use the radio buttons at each intersection to model a staff member's assignment to a task.
  • Each staff member can be modelled against only one task per day.

Coverage HUD

The Coverage HUD at the top of the matrix shows real-time statistics as assignments are modelled. It displays total staff assigned, tasks covered, and overall coverage percentage. The HUD updates instantly as radio buttons are clicked.

Filters

Auto-Allocator

Automatic Staff Assignment

The Auto-Allocate button provides automated modelling that places skilled staff on matching tasks first, then fills remaining gaps with available personnel. After running the auto-allocator, review the modelled assignments and adjust as needed.

Standby Column

The matrix includes a Standby column. Staff modelled as standby represent available capacity not committed to a specific task in the simulation.

12
Team Clusters

The Team Clusters view provides a visual summary of how staff are grouped and modelled within the current simulation date.

View Modes

Cluster Cards

Each cluster card displays team members modelled against that group or asset for the selected date, along with their skill type and modelled task assignment.

Standby Pool

The Standby Pool section shows all staff modelled as standby for the day, representing unallocated capacity within the simulation.

13
Plan Summary

The Plan Summary provides a consolidated analytical report of the current simulation state, aggregating data from the Project Structure, Staff Roster, and Allocation Matrix.

Summary Contents

Export

The Plan Summary can be exported for offline review via the export button at the top of the summary view.

14
Broadcast Order

The Broadcast Order generates a simulated allocation summary based on the current modelled assignments. It presents a structured view of how workforce capacity maps to tasks under the active simulation scenario.

View Modes

Mode Description Intended Use
Minimal Names and modelled task assignments only. Compact format. Quick analytical reference.
Standard Names, assignments, asset, and category details. Scenario review and capacity evaluation.
Full Complete details including manhours and modelling parameters. Detailed analytical review.

Email Export

Click the Email button to generate a pre-formatted email containing the simulation summary. This opens your default email client with the content formatted for review.

Display Mode

Click the Display button to open the simulation summary in a full-screen visualisation view for large monitors. See Section 17: Display Mode for details.

15
Forecast

The Forecast instrument provides forward-looking capacity analysis, allowing visualization of how workforce supply and maintenance demand will evolve over a defined time range.

Selection Modal

When you open the Forecast, a selection modal appears with the following options:

Three Visualizations

Visualization Description
Grid (Bar Charts) Capacity and demand as side-by-side bars for each day. Identifies days where demand exceeds capacity.
Timeline (Line Chart) Capacity and demand as continuous lines over time. Identifies trends across the forecast period.
Heatmap Color-coded matrix showing coverage intensity across dates and disciplines. Red indicates under-capacity; green indicates surplus.

Interpreting Results

  • Green / surplus — Modelled capacity exceeds demand in the simulation.
  • Yellow / tight — Modelled capacity is near demand. Warrants further evaluation.
  • Red / deficit — Demand exceeds modelled capacity. Indicates a constraint worth investigating in scenario analysis.
16
Analytics (Charts)

The Analytics view provides statistical breakdowns of planning data through interactive charts and drill-down panels. Opens in a separate satellite window.

Stats Summary Bar

At the top, the stats summary bar displays total staff, total manhours planned, manhours allocated, and overall utilization rate.

Drill-Down Panels

Click on any summary metric or chart element to drill down into the underlying data. Drill-down panels show which projects, assets, categories, or staff members contribute to the selected metric.

Category Breakdowns

Charts show performance metrics broken down by workforce category (Structural Systems, Mechanical Systems, Electrical & Electronic, Interior & Auxiliary, Surface Treatment), enabling comparison of utilization, coverage, and demand distribution across disciplines.

Project-Mode Timeline

The project-mode timeline averaging displays a chronological view of demand across the full duration of active projects, highlighting overlapping work packages.

17
Load Shaping Console (LSC)

The Load Shaping Console is a planning instrument that allows workload redistribution by adjusting when asset maintenance windows occur. By shifting maintenance windows along a timeline, users can evaluate alternative demand distributions while preserving total manhour constraints. Opens in a separate satellite window.

How It Works

The LSC displays a timeline of asset maintenance windows alongside workforce capacity. Drag maintenance windows left or right to explore alternative scheduling. The demand curve updates in real time, showing the impact of each adjustment immediately.

Scenarios

  1. Save Scenario: After making adjustments, save the current arrangement as a named scenario for later comparison.
  2. Compare Scenarios: Open multiple saved scenarios side by side to evaluate which arrangement produces the most favorable demand distribution.
  3. Apply Scenario: When satisfied, apply the scenario to push updated maintenance windows back to the Project Structure.

Syncing Changes

When a scenario is applied, date changes propagate back to the Project Structure tab. All affected tasks, activities, and groups will have their dates updated to reflect the new maintenance window positions. Review the Plan Summary after applying to confirm the updated schedule.

18
Display Mode

Display Mode presents the simulated allocation summary in a large-format visualisation designed for presentation on external monitors. It provides a high-visibility readout of the modelled workforce distribution. Opens in a separate satellite window.

Features

Configuration

Before entering Display Mode, configure:

Tip — For presentations, use Display Mode in full-screen (F11) on a dedicated browser window. Auto-pagination will cycle through all modelled assignments continuously.
19
User Management (Administrator Only)
Administrator Access Required — The User Management tab is only accessible to users with the Administrator role.

User Management allows administrators to view, configure, and manage user accounts and their associated roles within the framework.

Account Provisioning

New user accounts are created through the administrative interface. The administrator assigns the appropriate role, which determines the user's access level within the framework.

Linking Staff Records

Administrators can link staff roster entries to user accounts. This associates a user's login identity with their staff record, enabling personalized views and permission enforcement.

Role Reference

The User Management view includes a quick-reference panel listing all 13 roles with their access levels. See Section 6: User Roles for the full breakdown.

20
Data Import & Export

CA V9.2.1 Pre Alpha supports importing and exporting data to facilitate setup and backup workflows.

Importing Projects from Excel (.xlsx)

  1. Navigate to the Project Structure tab.
  2. Click the Import button in the toolbar.
  3. Select your Excel (.xlsx) file from the file browser.
  4. The system will parse the file and display a preview of the structure to be imported.
  5. Review the preview and click Confirm Import to load the data.

Importing from CSV

CSV import follows the same workflow. The file must use the correct column format described below.

Template Format

Required Columns
  • Level — Node level in the hierarchy (Project, Asset, Group, Activity, Task).
  • Name — Name of the node.
  • Start Date — Start date in YYYY-MM-DD format.
  • End Date — End date in YYYY-MM-DD format.
  • Manhours — Required manhours (applicable to Task-level rows).
  • Group — Workforce category: Structural Systems, Mechanical Systems, Electrical & Electronic, Interior & Auxiliary, or Surface Treatment (applicable to Group-level rows).
Format — Date values must be in YYYY-MM-DD format. Hierarchy levels must be correctly nested. Malformed files will be rejected with a descriptive error message.

Baseline Save and Restore

The Baseline feature allows saving a snapshot of the current plan as a reference point. Click Save Baseline to capture the current state. Use Restore Baseline to revert to a previously saved snapshot.

21
Workflow: Importing Projects & Manpower

This section provides a step-by-step workflow for setting up a complete simulation scenario by importing both project data and manpower records into CA V9.2.1 Pre Alpha.

Overview

A complete simulation requires two data sets: a project structure (tasks with dates, manhours, and workforce category assignments) and a staff roster (personnel with skills, availability, and off-day patterns). The workflow below guides you through importing both.

Phase 1 — Prepare Your Project File

Create an Excel (.xlsx) or CSV file with the following hierarchy and columns:

Required Columns
  • Level — Hierarchy level: Project, Asset, Group, Activity, or Task.
  • Name — Name of the node at this level.
  • Start Date — Start date in YYYY-MM-DD format.
  • End Date — End date in YYYY-MM-DD format.
  • Manhours — Required manhours (Task-level rows only).
  • Group — Workforce category name (Group-level rows only): Structural Systems, Mechanical Systems, Electrical & Electronic, Interior & Auxiliary, or Surface Treatment.
Project ├── Asset │ ├── Group (assigned to a workforce category) │ │ ├── Activity │ │ │ ├── Task (with manhours, start & end dates) │ │ │ └── Task │ │ └── Activity │ │ └── Task │ └── Group │ └── Activity │ └── Task └── Asset └── ...

Phase 2 — Import the Project

  1. Log in to CA V9.2.1 Pre Alpha and navigate to the Project Structure tab.
  2. Click the Import button in the toolbar.
  3. Select your prepared Excel (.xlsx) or CSV file from the file browser.
  4. The system parses the file and displays a preview of the project hierarchy.
  5. Review the preview for correctness — verify node names, dates, and manhour values.
  6. Click Confirm Import to load the project into the framework.
  7. The project tree populates with all nodes. Verify the structure by expanding each level.
Tip — If you have customized strengths (see Section 25), configure them before importing the project so that component-level nodes align with your custom names.

Phase 3 — Prepare Your Manpower File

Manpower data can be entered directly in the Staff Roster or imported via the Roster Builder module. The Roster Builder accepts CSV files with the following fields:

Column Description
NameFull name of the staff member.
IDUnique staff identifier.
DisciplinePrimary discipline or trade.
StrengthComponent-level skill (must match a component name from the workforce category).
TypeWorkforce category name (e.g., Structural Systems).
Off DaysOff-day pattern (e.g., "Fri", "Sat,Sun").
EmailContact email (optional).
PhoneContact phone (optional).

Phase 4 — Import Manpower via Roster Builder

  1. Open the Roster Builder from Planning → Tools → Roster Builder, or from the Staff Roster toolbar.
  2. If you have customized strengths in the main application, they are automatically loaded into the Roster Builder.
  3. Click Import CSV and select your prepared manpower CSV file.
  4. The Roster Builder parses the file and populates the roster table with all staff entries.
  5. Review the imported records — verify disciplines, strengths, and off-day patterns.
  6. Make any adjustments (edit fields, reassign disciplines, or remove entries) directly in the Roster Builder.
  7. Click Push to App to export the roster as a CSV formatted for the main application.
  8. In the main application, navigate to the Staff Roster tab.
  9. Use the Import function to load the exported CSV into the staff roster.

Phase 5 — Verify the Simulation

  1. Navigate to the Dashboard and select a simulation date within your project date range.
  2. Verify that demand figures appear for the active tasks on that date.
  3. Check that staff capacity is reflected correctly, accounting for off-days.
  4. Open the Allocation Matrix and confirm that staff members are listed under the correct workforce categories.
  5. Model a test allocation by assigning staff to tasks and observe the coverage metrics update in real time.
Checklist — Before running a full simulation, confirm: (1) project dates are correct, (2) manhour values are populated at the task level, (3) all staff are assigned the correct strength and workforce category, and (4) off-day patterns are configured.

Common Issues

Issue Resolution
Import rejected with format error Verify dates are in YYYY-MM-DD format and hierarchy levels are correctly nested (Project → Asset → Group → Activity → Task).
Staff not appearing in Matrix Ensure the staff member's Type matches one of the five workforce categories exactly and the Strength matches a valid component name.
Demand shows zero on Dashboard Confirm the selected simulation date falls within the start and end dates of active tasks, and that manhour values are populated.
Custom strengths not showing in Roster Builder Open the Roster Builder from within the main application (Planning → Tools) so the custom configuration is passed automatically.
22
Roster Builder

The Roster Builder is a dedicated feature module for detailed manpower analysis and team composition planning. It provides a comprehensive environment for building, organising, and analysing staffing rosters before pushing them into the main simulation framework.

Purpose — The Roster Builder is an analytical tool for modelling team structures, evaluating staffing distributions, and preparing manpower data for simulation scenarios. It operates as a standalone module that bridges to the main application.

Accessing the Roster Builder

  1. From the main application, open Planning → Tools → Roster Builder.
  2. The Roster Builder opens in a new browser tab.
  3. If customized strengths have been configured in the main application, they are automatically loaded.

Interface Layout

The Roster Builder interface consists of three areas:

  • Sidebar (Left) — Discipline management panel for creating, editing, and organising disciplines with colour coding and tree group assignments.
  • Stats Ribbon (Top) — Real-time aggregate statistics showing total members, per-discipline counts, and status breakdowns.
  • Roster Table (Centre) — Sortable, searchable table displaying all roster members with inline action buttons.

Member Fields

Each roster member record captures 15 fields for comprehensive personnel profiling:

Field Description
NameFull name of the team member (required).
IDUnique identifier. Auto-generated if left blank.
DepartmentOrganisational unit or department.
SectionSub-department or team section.
DisciplinePrimary discipline, selected from the disciplines defined in the sidebar.
StrengthComponent-level skill. Dropdown populated based on the discipline's assigned tree group.
DesignationJob title or role designation.
EmailContact email address.
PhoneContact phone number.
Leave StartStart date of leave period.
Leave EndEnd date of leave period.
Shift StartShift start time.
Shift EndShift end time.
StatusCurrent status: Active, Sick, Training, or Leave.
Off DaysWeekly off-day pattern selected from a 7-day selector (Mon–Sun).

Discipline Management

Disciplines are user-defined categories that organise staff by trade or specialisation. The sidebar panel provides full discipline lifecycle management.

Operation How
Create Enter a name, select a colour from the 15-colour palette, optionally assign a tree group, and click Add Discipline.
Edit Click the edit icon on a discipline card. The name becomes an editable field. Press Enter to confirm or Escape to cancel.
Delete Click the delete icon. A confirmation modal shows the number of affected members. Deleting a discipline sets affected members to unassigned.
Group Tag Assign a discipline to one of the five tree groups (Structural, Mechanical, Electrical & Electronic, Interior & Auxiliary, Surface Treatment). The group tag drives the Strength dropdown and the Push to App type mapping.

Strength Dropdown Behaviour

The Strength field dynamically adapts based on the selected discipline:

  • If the discipline has a tree group assigned, the Strength dropdown lists all component names within that group (e.g., selecting a discipline tagged as "Electrical & Electronic" shows Electronic Systems, Instrumentation, Electrical Systems).
  • If the discipline has no group assigned, only a "General" option is available.
  • If custom strengths have been configured in the main application (see Section 25), the customised component names appear in the dropdown.

Statistics Ribbon

The stats ribbon above the roster table provides real-time aggregate analytics:

Metric Description
Total MembersCount of all roster entries.
Per-Discipline CountsIndividual count cards for each discipline, colour-coded to match discipline colours.
UnassignedMembers without a discipline assignment.
SickMembers with status set to Sick.
TrainingMembers with status set to Training.
On LeaveMembers with status set to Leave.

Search and Filtering

  • Search Box — Real-time search across Name, ID, Department, Section, Designation, Strength, and Status fields. Case-insensitive substring matching.
  • Discipline Filter — Dropdown to show only members of a specific discipline.
  • Column Sorting — Click any column header to sort ascending or descending. Sort direction is indicated by an arrow icon.

Data Import & Export

Function Format Description
Import CSV CSV Bulk import members from a CSV file. Disciplines are auto-created if they do not exist. IDs are auto-generated if missing.
Export CSV CSV Export the full roster table as a CSV file including all 15 fields plus the group tag.
Save Roster JSON Save the complete roster (disciplines and members) as a dated JSON file for backup or transfer.
Open Roster JSON Load a previously saved JSON roster file. Replaces the current roster entirely.

Push to App

The Push to App function bridges the Roster Builder to the main CA V9.2.1 Pre Alpha application. It transforms roster data into the format expected by the Staff Roster in the main application.

  1. Click Push to App in the Roster Builder footer.
  2. A confirmation modal displays the number of members to be exported.
  3. Confirm to generate the export. The system produces a CSV file (roster_staff_import.csv).
  4. In the main application, navigate to the Staff Roster tab.
  5. Use the Import function to load the generated CSV.

Push to App Field Mapping

Roster Builder Field Main App Field Mapping Rule
NameNameDirect copy.
IDIDDirect copy.
EmailEmailDirect copy.
PhonePhoneDirect copy.
StrengthStrengthDirect copy. Defaults to "General" if empty.
Discipline → Group TagTypeResolved from the discipline's tree group name (e.g., "Electrical & Electronic"). Defaults to "Staff" if no group assigned.
Off DaysOff DaysDirect copy.

Data Persistence

Roster Builder data is stored in the browser's local storage under the keys rb_disciplines and rb_roster. Data persists across browser sessions until explicitly cleared. Use the Save Roster (JSON export) function to create portable backups.

Analytical Use — The Roster Builder is designed for analytical modelling of team structures. Use it to evaluate staffing distributions, identify discipline coverage gaps, and prepare optimised rosters before committing them to the simulation framework via Push to App.
23
Scenario Evaluation Logic

CA V9.2.1 Pre Alpha evaluates each simulation scenario by comparing daily demand against declared capacity for each workforce category. The evaluation is fully deterministic: identical inputs produce identical outputs.

Feasibility Determination

For each simulation day t, the framework computes:

A day is classified as feasible when W(t) ≤ C(t), and infeasible when W(t) > C(t). This evaluation is performed independently for each workforce category and in aggregate.

Redistribution Effects

When maintenance windows are shifted (via the Load Shaping Console or date edits in Project Structure), total effort is preserved while daily demand profiles change. The framework recomputes feasibility across all affected dates, enabling users to compare scenarios and identify constraint violations.

What the Framework Does Not Do

24
Architecture, Data & Licensing

Framework Architecture

CA V9.2.1 Pre Alpha is a static web application. All computation, modelling, and simulation logic is executed entirely on the host device within the user's browser. There is no server-side processing, no backend computation, and no remote execution of framework logic.

Data Storage

All project data, staff records, allocation models, and simulation state are stored locally in the browser's storage on the host device. Data does not leave the user's machine during normal operation. Users are solely responsible for backing up their data.

Local Data Summary
  • All data resides in the browser's local storage on the host device.
  • No project data is transmitted to or stored on external servers.
  • Clearing browser data will remove all stored project information.
  • Data is isolated per browser profile and device.

Telemetry & Tracking

CA V9.2.1 Pre Alpha does not include any telemetry, analytics, tracking scripts, or usage monitoring of any kind. The framework does not collect, transmit, or report user activity, session data, or behavioural information. No cookies are used for tracking purposes.

Third-Party Libraries

CA V9.2.1 Pre Alpha uses the following open-source libraries. These are loaded from public CDN services at runtime and are not modified or redistributed by the framework.

Library Version Purpose License
Chart.js 4.x Interactive chart rendering for analytics, forecast, and load shaping visualisations. MIT License
SheetJS (xlsx) 0.18.5 Client-side parsing of Excel (.xlsx) and CSV files for project data import. Apache License 2.0
Font Awesome Free 6.x Icon library used throughout the framework interface. Icons: CC BY 4.0 / Fonts: SIL OFL 1.1 / Code: MIT License
Note — All third-party libraries are used in their unmodified, publicly available forms. No proprietary modifications have been made to any third-party code. Full license texts are available from each project's respective repository.

Framework Code

All framework logic, simulation algorithms, interface code, and styling outside of the above third-party libraries is original work. All intellectual property rights associated with the framework code are reserved.

25
Scope & Limitations

CA V9.2.1 Pre Alpha is a simulation framework for analytical and academic evaluation. Users should understand the following boundaries when interpreting framework outputs.

What This Framework Is

What This Framework Is Not

Important — All outputs are dependent upon user-defined inputs, structural definitions, and declared assumptions. The framework does not validate inputs against external standards or regulatory requirements. Users bear full responsibility for interpreting and applying framework outputs within their operational context.
26
Troubleshooting & FAQ

Below are answers to common questions and solutions to frequently encountered situations.

Frequently Asked Questions

"No Role Assigned" notification

Cause: Your account has not been assigned a role.
Resolution: Contact your administrator and request role assignment. Once assigned, sign out and sign back in.

"Data not updating"

Cause: Cached data may not reflect the latest changes.
Resolution: Click the Update button in the header bar to refresh all data. If the issue persists, perform a full browser refresh (F5 or Ctrl+R).

"Cannot see certain tabs"

Cause: Your assigned role does not have access to those tabs.
Resolution: Refer to Section 6: User Roles to see which tabs are available for your role. Contact your administrator to discuss role changes if needed.

"Can I access from a mobile device?"

The interface adapts to tablets and mobile devices. However, for planning instruments such as the Allocation Matrix and Display Mode, a desktop or large-screen display is recommended.

Browser Compatibility

Browser Minimum Version Status
Google Chrome90+Supported
Microsoft Edge90+Supported
Mozilla Firefox88+Supported
Apple Safari14+Supported
Internet ExplorerAnyNot supported
27
Versioning & Support

If you require assistance with CA V9.2.1 Pre Alpha, use the appropriate support channel based on the nature of the issue.

Support Channels

When Contacting Support

To assist resolution, please provide:

Version Information

Framework
CA V9.2.1 Pre Alpha
Version
V9.2.1
Specification Date
February 2026
Status
Stable — Analytical
This software is provided for academic and analytical evaluation purposes only.
28
Acknowledgements

CA V9.2.1 Pre Alpha incorporates the following open-source libraries. These libraries are vendored locally within the application and loaded without any external network calls. No runtime dependencies on external servers or CDNs exist.

Chart.js

Version4.4.7
LicenseMIT License
Copyright© 2024 Chart.js Contributors
Websitechartjs.org
UsageAnalytics charts and data visualisation across the Dashboard, Forecast, and standalone Analytics window.
Chart.js bundles @kurkle/color v0.3.2 (© 2023 Jukka Kurkela, MIT License) as an embedded dependency for colour manipulation.

SheetJS (XLSX)

VersionCurrent release at time of integration
LicenseApache License 2.0
Copyright© 2013–present SheetJS
Websitesheetjs.com
UsageExcel (.xlsx) and CSV file parsing for project structure import and staff roster import.

Font Awesome Free

Version6.4.0
Copyright© 2023 Fonticons, Inc.
Websitefontawesome.com
UsageUser interface icons across all application views, navigation, and status indicators.

Font Awesome Free is distributed under three licenses:

Component License Details
Icons (SVG/design) CC BY 4.0 Creative Commons Attribution 4.0 International. Attribution to Font Awesome is required.
Fonts (TTF/WOFF2) SIL OFL 1.1 SIL Open Font License 1.1. Fonts may be redistributed with software but may not be sold separately.
Code (CSS/JS) MIT License Standard permissive open-source license.

License Summary

All third-party libraries used in this framework are distributed under permissive open-source licenses that allow use, modification, and redistribution for both non-commercial and commercial purposes, subject to attribution requirements. No additional permissions are required beyond retaining the original license headers and providing acknowledgement in documentation.

Note — Third-party library license headers are retained in their respective source files within the lib/ directory. This acknowledgements section fulfils the attribution requirements of the CC BY 4.0, MIT, and Apache 2.0 licenses.