Inspect a Hose

This guide walks you through conducting hose tests, recording results, and managing follow-up actions.

Prerequisites

• Access to your brigade’s StationOne instance
• Brigade admin, brigade user, or appropriate role
• Hose already created in the system
• Physical testing equipment (pressure tester, etc.)

Steps

1. Navigate to Hose Register

1. Log in to StationOne
2. Select your organisation and unit
3. Click Hoses in the main navigation

2. Select Hose to Test

Find the hose you want to test:

Option 1: From the list

• Browse the hose register
• Look for hoses marked “Overdue” or “Due Soon”
• Click the hose row to open details

Option 2: Use filters

• Apply Test Status filter: “Overdue” or “Due Soon”
• Shows only hoses needing testing
• Click hose to open details

Option 3: Search

• Enter reference number in search box
• Find specific hose quickly
• Click to open details

3. Record the Test

On the hose detail page:

1. Click Record Test button
2. Fill in test details

Test Information

Test Date (required)

• Defaults to today’s date
• Change if testing on a different date
• Cannot be in the future

Test Result (required) Select one:

• Pass - Hose passed all tests
• Fail - Repair Needed - Failed, requires repair
• Fail - Retire - Failed, must be retired

Notes (optional but recommended)

• Document test details
• Record pressure readings
• Note any wear or damage
• Include repair recommendations

Example Notes:

• “Pressure tested to 1500 kPa, no leaks detected”
• “Minor wear on coupling threads, recommend monitoring”
• “Failed pressure test at 800 kPa, bladder leak detected”

4. Submit Test

Click Record Test to save.

System will:

• Update last test date
• Calculate next test due (based on your brigade’s interval)
• Update hose status if needed
• Create repair record if failed

Understanding Test Results

Pass Result

When a hose passes:

Status Changes:

• Remains “In Service”
• Available for deployment
• Ready for use

Next Test Due:

• Automatically calculated
• Based on your brigade’s configured interval
• Default: 12 months from test date
• Options: 1, 3, 6, or 12 months

Notifications:

• No immediate notifications
• Due soon alerts at 30 days before next test
• Overdue alerts after due date passes

Fail - Repair Needed

When a hose fails but can be repaired:

Status Changes:

• Changed to “Out of Service”
• Cannot be deployed
• Requires repair before returning to service

Next Steps:

1. Create repair record (automatically prompted)
2. Perform physical repair
3. Complete repair record
4. Re-test hose
5. Return to service if passed

Notifications:

• Available members notified
• Action item created
• Appears in out of service list

Fail - Retire

When a hose fails and must be retired:

Status Changes:

• Changed to “Retired”
• Permanently removed from active inventory
• Retained for historical records

Next Steps:

• Physically remove from service
• Dispose or store for parts
• Update inventory records

Notifications:

• Admin notification sent
• Removed from testing schedule
• Retained in reports

Test Schedule Overview

Understanding Due Dates

Initial Test Due:

• Calculated from in-service date
• First test due based on configured interval

Subsequent Tests:

• Due from last test date + interval
• Automatically calculated
• Updated after each test

Brigade Testing Interval:

• Configurable per brigade
• Options: 1, 3, 6, or 12 months
• Set in Brigade Settings → Features
• Default: 12 months

Overdue and Due Soon

Due Soon:

• Tests due within 30 days
• Yellow/orange warning
• Plan testing schedule

Overdue:

• Past due date
• Red warning
• Priority for testing
• Compliance issue

Batch Testing

Testing Multiple Hoses

For efficiency, test multiple hoses:

1. Plan Testing Session

   • Filter hoses by “Due Soon” or “Overdue”
   • Group by location or type
   • Schedule testing time

2. Test Sequentially

   • Open each hose
   • Record test
   • Move to next hose
   • System maintains list position

3. Use Filters

   • Test all 38mm hoses together
   • Test by location
   • Test by coupling type

Testing from Dashboard

Monitor testing status:

• Dashboard shows overdue count
• Quick links to overdue hoses
• Statistics on test compliance

Testing Best Practices

Before Testing

Preparation:

• Check test equipment is calibrated
• Review hose specifications
• Have replacement parts available
• Schedule adequate time

Documentation:

• Note current condition
• Photograph any issues
• Record serial numbers
• Check previous test notes

During Testing

Pressure Testing:

• Follow manufacturer specifications
• Test at rated pressure
• Check for leaks at couplings
• Inspect for bulges or damage

Visual Inspection:

• Check exterior for wear
• Inspect coupling threads
• Look for UV damage
• Check for chemical damage

Recording Results:

• Be honest about failures
• Document specific issues
• Note recommended actions
• Record pressure readings

After Testing

For Passed Hoses:

• Return to service
• Update location if moved
• Schedule next test
• Update any reference tags

For Failed Hoses:

• Mark clearly as out of service
• Move to repair area
• Create repair record
• Notify relevant personnel

Common Issues

Can’t Record Test

If test recording fails:

• Check you’re on correct hose
• Verify test date is not in the future
• Ensure result is selected
• Confirm you have permissions

Wrong Next Test Date

If calculated date seems wrong:

• Check brigade’s testing interval setting
• Verify test date entered correctly
• Contact admin to verify interval

Hose Not Appearing

If hose doesn’t show in list:

• Check filters aren’t hiding it
• Verify hose is in your unit
• Confirm hose is not deleted
• Check status filters

Related Guides

• Create a Hose - Add new hoses
• Repair a Hose - Log and complete repairs
• Retire a Hose - Remove from service
• Public Hose Interface - Enable public testing
• Hose Management - Feature overview