Skip to content

Hose Management

The Hose Management module provides comprehensive tracking for fire hoses, including test scheduling, repair history, and status management.

Hose Management enables:

  • Hose inventory tracking
  • Automated test scheduling (interval configurable per brigade)
  • Pass/fail test results
  • Repair tracking and history
  • Status management (in service, out of service, retired)
  • Soft delete capability
  • Compliance reporting

Each hose includes:

  • Reference number: Unique identifier
  • Coupling type: Connection type (Storz, BSP, etc.)
  • Diameter: Hose diameter (e.g., 38mm, 64mm)
  • Length: Hose length in meters
  • Material: Construction material
  • In service date: Date hose was commissioned
  • Status: Current operational status
  • Next test due: Automatically calculated

Hoses can have three statuses:

  • Actively used and operational
  • Available for deployment
  • Must be tested on schedule
  • Temporarily unavailable
  • Triggered by failed test with repair needed
  • Returns to in_service after passing test
  • Permanently removed from service
  • Failed test with retirement flag
  • Cannot return to service
  • Retained in system for records

Configurable test cycle (default: 12 months):

  • Testing interval: Set by brigade admins in Settings (1, 3, 6, or 12 months)
  • In service date: Initial test due based on configured interval from commissioning
  • After each test: Next test due based on configured interval from test date
  • Overdue tracking: Dashboard warnings for overdue tests
  • Due soon: Alerts for tests due within 30 days

Test workflow:

  1. Select hose for testing
  2. Perform physical test (pressure test, visual inspection)
  3. Record test result (pass/fail)
  4. Add test notes
  5. Submit test record

Pass

  • Next test due date set based on your brigade’s configured interval (default: 12 months)
  • Status remains in_service
  • Hose available for use

Fail + Retire

  • Status changed to retired
  • Permanently removed from active inventory
  • Retained for historical records

Fail + Repair Needed

  • Status changed to out_of_service
  • Repair record created
  • Hose unavailable until repaired and re-tested

Repairs can be triggered by:

  • Failed hose test
  • Manual creation for damage
  • Preventive maintenance

Each repair tracks:

  • Hose: Associated hose
  • Repair date: When repair was performed
  • Repair type: Nature of repair (coupling, patch, etc.)
  • Performed by: User who completed repair
  • Notes: Repair description and details
  • Cost: Optional repair cost tracking
  1. Identify issue: Failed test or damage discovered
  2. Create repair record: Document issue and repair plan
  3. Perform repair: Physical repair work
  4. Complete repair: Update record with completion details
  5. Re-test: Conduct new hose test
  6. Return to service: If test passes, status returns to in_service

Hoses support soft delete for data retention:

  • Delete action: Sets deleted_at timestamp
  • Hidden from active lists: Not shown in standard views
  • Recoverable: Can be restored if needed
  • Historical data: Retained for reporting and compliance
  • Test history: All tests and repairs preserved

Generate hose management reports:

  • Inventory report: All hoses by status
  • Test schedule: Upcoming and overdue tests
  • Test history: Past test results by hose
  • Repair history: Repairs by hose or date range
  • Compliance: Test coverage and completion rates
  • Use clear reference numbers (e.g., H-001, STATION1-38MM-01)
  • Label physical hoses to match system
  • Include coupling type in reference for quick identification
  • Document diameter and length clearly
  • Test hoses before due date to allow time for repairs
  • Batch test hoses by location or type for efficiency
  • Review test results promptly
  • Address failed tests quickly

Brigade admins can customize the testing interval:

  1. Go to Brigade SettingsFeatures tab
  2. Find the Hose Testing Settings section
  3. Select your preferred interval: Monthly (1 month), Quarterly (3 months), Bi-annual (6 months), or Annual (12 months)
  4. Click Save Hose Testing Settings

The interval applies to all hoses in your brigade. New units default to 12 months.

  • Document repairs thoroughly
  • Track repair costs for budgeting
  • Identify patterns (recurring failures)
  • Replace hoses with excessive repair history
  • Retire hoses that fail multiple times
  • Keep out_of_service duration minimal
  • Review retired hoses annually for disposal
  • Maintain adequate in_service inventory
  • Track hose age and usage
  • Plan replacement budget
  • Maintain spare inventory
  • Consider hose type standardization
  • Equipment - Track other fire service equipment
  • Vehicles - Hoses may be assigned to vehicles
  • Actions - Repair tasks can be tracked as actions