WO2003050768A1

WO2003050768A1 - A method for diver accountability

Info

Publication number: WO2003050768A1
Application number: PCT/AU2002/001665
Authority: WO
Inventors: Bruce Henry Trickey
Original assignee: Trickey, Helen, Ann
Priority date: 2001-12-11
Filing date: 2002-12-09
Publication date: 2003-06-19

Abstract

A method for diver accountability, the method comprising the steps of: I) completing a first set of data, the data including at least the number of divers, II) providing a personal identifying means (PIM) to each diver, III) inputting the PIM into a computer prior to a dive, IV) providing at least one tag on the diving equipment of each diver and which contains information, V) inputting dive information into the computer, the dive information including details of the tank capacity, dive depth, dive time, VI) starting a timer when the divers go into the water, VII) inputting the PIM into the computer when a diver exits the water, VIII) providing an alarm that will trigger if the PIM of a particular diver has not been inputted into the computer after predetermined time has passed.

Description

A METHOD FOR DIVER ACCOUNTABILITY

FIELD OF THE INVENTION This invention relates to a diver accountability system that accounts for divers entering and exiting the water. The invention is not restricted to only a diver accountability it can also extend to cover a guest management system.

BACKGROUND ART Scuba diving is becoming more and more popular and unfortunately, many people engaging in scuba diving are relatively unskilled and untrained. A popular form of scuba diving is in relatively shallow water around reefs and wrecks. It is common to dive as a group with the group consisting of between 2-10 people. In this type of arrangement, it is common to have a divemaster. The divemaster is a senior and experienced person who stays on the surface and accounts for the safe entry and exit of the group. It is extremely important for the divemaster to be able to fully account for all divers. The divemaster must make sure that all divers are present and accounted for at all times, but must also be able to calculate how long a diver has been underwater and when the diver must surface.

To date, the divemaster uses an ad-hoc system which involves good memory, notepads, calculators and general skill and expertise in order to ensure that all the divers are looked after during the dive experience. However, errors have occurred, and reported cases exist where divers have been accidentally left behind due to errors of judgment being made by the divemaster. In our earlier invention, a diver accountability system was provided which had a rather large a master panel and a plurality of dive tags, the dive tags being adapted for removable attachment to a diver's tank or equipment, the dive tags having a surface on which information can be given, the information including information identifying the diver, the tank size and the tank pressure, the master panel having a plurality of tag holding means, a computing means, data entry means to allow data to be entered into the computing means, the data including tank size, tank pressure and dive depth for each diver, and display means to display at least some of the information entered by the data entry means and/or calculated by the computing means.

While this overcame some of the disadvantages, this earlier invention had some inherent limitations and had some restrictions on the versatility that is required to properly provide accountability and to comply with local, State or Federal requirements.

OBJECT OF THE INVENTION The present invention is directed to a method, or system for diver accountability that is quite versatile and where much of the hardware or equipment is "off-the-shelf equipment. In one form, the invention resides in a method for diver accountability, the method comprising the steps of:

I completing a first set of data, the data including at least the number of divers,

II providing a personal identifying means (PIM) to each diver, III inputting the PIM into a computer prior to a dive,

IV providing at least one tag on the diving equipment of each diver and which contains information,

V inputting dive information into the computer, the dive information including details of the tank capacity, dive depth, dive time, VI starting a timer when the divers go into the water,

VII inputting the PIM into the computer when a diver exits the water

VIII providing an alarm that will trigger if the PIM of a particular diver has not been inputted into the computer after predetermined time has passed. BRIEF DESCRIPTION OF THE DRAWINGS

An embodiment of the invention will be described with reference to the following features in which:

Figure 1. Illustrates a flowchart of a dive activity profile.

Figure 2. Illustrates a flowchart of a guest profile. Figure 3. Illustrates a flowchart of the leaving site.

Figure 4. Illustrates a flowchart of the steps followed by the system when going diving.

Figure 5. Illustrates a flowchart of the alarm procedure. Figure 6. Illustrates a flowchart of the management functions Figure 7. Illustrates an embodiment of the invention for snorkelling. Figure 8. Illustrates a variation to the management function screen showing the 'review data' button. BEST MODE

An overview of an embodiment of the invention and with reference to the above figures is as follows:

In an embodiment, the system is suitable for use on vessels that carry up to 20 guests (includes crew). However, the system is modular to accommodate vessels that carry a greater number (20 plus) of guests.

An advantage of the system according to an embodiment of the invention is that most of the hardware components are off-the-shelf available units. In the embodiment, the hardware components include:

• Personal l,D bar coded wrist band • Equipment dive tags

• Portable computing data unit

• Mounting cradle (optional)

• l,P rated sounder (optional)

The software component according to the embodiment includes: • GMS program for portable handheld device

• Larger vessel program for data capture and receipt and transmission of inputted information from GMS

The invention in the embodiment is for use in the marine industry and primarily for use on charter vessels that take crew and guests. The system is designed to operate using specific software housed in suitable hardware components. For instance, the personal identifying means (PIM) may comprise bar-coded wrist bands identifying guests which are scanned into a computer system to give account for location of guests and will alert a responsible person such as the vessel / dive master if guest is not accounted for. This can include diving and snorkelling activities and embarking/disembarking vessel.

The invention encompasses a facility to have guests disembark temporarily (got off at a resort and picked up later on vessel journey). This is coupled with procedural inputs from the dive master/ operator. The diving activity portion of the program can embody part or all of our previous invention the contents of which are incorporated by suitable cross-reference. Our previous invention is described in international patent application PCT/AUOO/01590, and the present invention can embody in total the previous "diver accountability system" process and incorporate the dive tag system which are not housed in a main holder (as described in our previous invention), but are gathered together on a suitable attachment on vessel (such as a snap hook with a mechanical closing mechanism to prevent tags from being dislodged and lost).

The diving and snorkelling activity portion of program also has files created for reference to regular dive sites linking diving and snorkelling activities with dive site profiles, environmental hazards and emergency procedures, and this system is linked to a office PC program to give a complete guest management system. Process

The process starts with a program written for office PC. This program will encompass office management tools such as inventory, booking system, financial audit, point of sale and linked to modem. It will also have the following specific data files which can be edited or created new and downloaded to portable computing device, files are,

• DAP dive activity profile - file contains data of dive/snorkel sites frequently visited. The information would include location name, whether it is a scuba or snorkel site, depth of dive, dive direction, current details. The DAP's can be edited on office PC or on portable computing means can also create new DAP's by either options.

• Environmental Hazards - file contains data of hazards associated with dive sites and are linked to DAP's (see flow charts}, can be edited or added to as per DAP's. • Emergency procedures - file contains information relative to emergencies I.E vessel, pontoon evacuation, lost diver procedure, recalling divers, medical emergencies closest decompression chamber, Ambulance, Police Air sea rescue, Workplace Health and safety issues, can be edited or added to

• Site locations - file contains details of sites regularly visited, recorded by name

• Guest log - file contains details of guest such as name, age, gender, medical certificate to dive, medical conditions, dive qualifications, dive certificate number, contact details.

• Management system functions - start of day file, receiving/ sending files, setup, end of day file.

The program can have the means to transfer/receive data to larger vessel GMS via wireless link, infra red device, and download to modem. Before Leaving Dock

• Operator will access menu screen and select "start of day", and scan his/her wrist tag to log onto system. • Operator will input all relevant data for Guest log, DAP's, Emergency plan, Environmental Hazards, Safety Brief into PC program (ideally based in operators booking office, but not limited to) and download data files to portable device. The program has the option to run over multiple days [typically 2-7 days]. Thus before leaving dock, the operator will firstly access "setup" screen and configure system to request signatures and other information as local, state or Federal Legislation requires, the operator will then select if a single day or multiple day system will be used, and adjust the clock if required. For multi day programs, each new day begins at midnight. A day counter can be displayed in the main menu. If multi day is selected the program will default to an Operator input dive table, where the Operator inputs the proposed dive depth and time and the program calculates all alarm times. Figure 6 illustrates screens suitable for setup and multi day events. • Operator before leaving dock/ departure point, will issue a wristband to each individual, this includes crew. The operator will scan the individual's wristband and link to individuals name into GMS, operator will check "Guest profile" details such as diver qualifications, diver certificate number, medical details, if diver details are not entered then system will prompt dive master that guest cannot be involved in dive activities.

• The main menu 21 [figure 2] can allow all diver records to be viewed. The main menu has a management functions button which is tapped to reveal a "Management Functions" menu with a 'review data' option [see figure 8]. This shows a list of divers. A particular diver can be selected to view details of that diver including list of dives, of which each individual dive can be selected to show details of dive and view adjustments etc .Note - this may be a read only file for data security.

• A waiver agreement screen can be developed which can be activated, read by each diver, and signed by each diver using a signature screen.

• Operator will access "Dive Activity profile " file and either create new dive site profile log or open existing dive site profile template, and fill in relevant data for dive site profile, which includes "environmental hazards"

• Operator will ensure "Emergency Plan "section on dive site profile, is filled in. • Operator will brief all individuals on safety procedures and this will be time and date stamped, and recorded.

• Operator will check that "dive tags" are attached to each divers equipment and that the correct information is displayed on same.

I.E Name - Tank Size - Pressure - Time in Time out

• Operator will consult GMS menu and select "leaving site" the program will require operator to scan in vessel identification number (registration) and his/her wrist band bar-code, identifying operator to system and conducting head count, entering number into system, if head count is wrong program will require operator conduct second count, if still not correct program will prompt operator to scan each individual wrist tag, name of guest/s not accounted for will be displayed on screen. Program compares number of guests logged onto vessel (including temporarily disembarked) to number collated in headcount.

• Once head count has been verified then system requires a signature from operator who conducted headcount.

• Note -the wrist bar code can be replaced by another PIM device which carries an antenna and tracking means, also a timing means.

Before Commencing Dive

• Operator will swipe wristband of each diver logged onto GMS and follow the program prompts.

• Prompts are "scuba" "snorkel" "disembark" "back". In a "Scuba" variation the main screen asks which dive tables are to be used.

These can include PADI or other pre-loaded table (which are programmed in the "Scuba" button) or non PADI tables. The selected table will apply for that group only, and will usually default back to a PADI or other pre loaded table. If a non PADI table is selected, there will be no table calculations, and the Dive Master must sign to complete table calculation, Divers are then added with the program recording tank size, pressures etc but no calculations are calculated on group details screen. Dive Master must enter maximum dive time for the dive and the program will calculate the alarms such as full duration, working duration and safety stop. Once a Diver has used the

Non Padi table then all subsequent dives will default back to Non Padi tables.

• Operator selects "scuba"- DAP screen appears, operator will tap on selected DAP or edit DAP or create new DAP, which ever suits site. • Screen will appear asking for information on "tank size" "pressure"

• Operator will have "dive tags" removed from each diver's equipment and check data inputs for accuracy and attach tags to GMS tag attachment means.

• Program will assign all guest's to dive group, inform dive master as to how many dives each guest has had I.E "this is [DIVER NAME] 3^rd dive for today" and as per previous patent program will select lowest capacity and pressure and calculate groups dive time, safety stop, working duration and full duration The program also accesses "repetitive dive table" calculations. The program will access repetitive dive tables after each guest has completed their first dive.

• Program then assigns "buddies". Buddies are generally in pairs, if an odd number precludes a guest from being assigned a buddy then the program will prompt the dive master to assign the guest to a buddy trio.

• Program reveals "Dive activity profile" screen, prompting the dive master to inform dive group of relevant dive details. The operator cannot go to "dive timers" without first going to view "Environmental Hazards' after relevant information has been to dive group operator can move to "emergency procedures screen" by tapping button, giving emergency information and tapping OK. Once this has been completed the program returns to DAP screen and "OK" button appears on DAP screen. • Operator taps "OK" and "dive timers " appear, timers have "safety stop", "Working duration" and "Full Duration" labels,

• Operator taps "Start timers' and program begins to count down to calculated times whereby alarms sound, alerting dive master. Alternatively, the operator can start timer or hold timer, then enter the next dive group details, and can start any grouping in any order.

Operator can now enter details of next dive group using the same process Up to 10 groups can be entered onto a single GMS device. This number may vary, more groups or less, with vessels carrying larger numbers of guests. • Operator can access "snorkelling" screen and the program will require

"Lookout" to scan in wrist ID, select a DAP. The snorkel group will be allocated" buddies' .The DAP will be displayed and program will prompt operator to display and give information to snorkel group on relevant "Environmental Hazard & Emergency procedures" he snorkel "start" timer will be displayed and operator will activate the program which will prompt the Lookout person to do a snorkellor head count every 20 minutes, until all snorkellors have been scanned out.

• Screen will display status of dive and snorkel groups and display timers to alarms. There can be a group screen to cover groups and an individual group screen will display total time elapsed.

• On activation of "safety stop" alarm, the operator will tap the screen to acknowledge alarm, on .activation of "working duration & full duration "alarms. The alarm will keep activating until all divers are scanned out of water.

• The operator can manually stop each dive group as they surface by tapping the 'stop timer' icon. This will stop the dive timer for the individual dive group but divers are still required to be scanned out as per the normal program function. The same applies for snorkellor groups.

• Operator will be alerted by GMS of the names of divers whom have not returned. The GMS will display relevant dive profile and emergency procedure. • Operator will be prompted to have each diver sign the device after being scanned out of water, and may input information such as actual depth, air pressure, and computer dive. This procedure may be required to satisfy local state of Federal legislation.

• The above alerting sequence and signatures applies also for snorkellors

• After all divers from group (or snorkellor group) have scanned and signed out, the program will prompt operator to verify completion of dive/snorkel activity by inputting signature into device.

• Dive tags will be returned to each diver's equipment on logging out of water.

• GMS will incorporate repetitive dive tables for subsequent scuba dives

• Note - the software can include air/gas mixture tables, and other relevant recognised dive tables and possibly dive computer data inputs.

• Operator will conduct "leaving site" head count

• Operator will "log off vessel", all individuals at the end of day/ tour, verifying return of individual to point of entry/departure. • Operator will view menu screen tap "management functions", management menu will appear and operator will tap "end of day"

• "End of day" function culminates all activities for day, that is all vessel head counts, embarking / disembarking, temporary disembarking, dive and snorkel activities and alerts operator as to any guests who have not been scanned off the vessel. A possible scenario would be if a guest had temporarily disembarked and not scanned back on or not scanned off vessel at end of trip. Once the files are completed, the program prompts the operator to verify all activities as correct by inputting signature into device.

• Note - program has facility for operator to access emergency functions to log guests off vessel or out of water if guest has lost wrist band or was not scanned off vessel, in these cases program will prompt operator to scan in their ID to identify themselves to system and enter reasons for logging guest off without scanning guest ID.

Return to Office

• Operator will download GMS activities onto main computer for storage printout and records for regulatory requirements such as Workplace Health and safety requirements. System Modular

System has been designed to be modular. The current GMS is intended to service vessels with up to 20 guests/crew. For vessels with 20 plus, the system can use wireless communication from GMS to central computing system on vessel. This has advantages of, • More than 1 portable device being used, giving greater scope for operation

• Greater number of guest's can be monitored

• Constant data being sent from device's to main computer giving accurate data capture • Note - future R&D to incorporate emergency guest tracking device

Referring to the embodiment in greater detail, reference will be made to the figures, and the following description.

Referring initially to figure 1 , there is illustrated a flowchart outlining the diver activity profile requirements. Dive Activity Profiles (DAP, (see figure 1)

DAP's can be created prior to the boat leaving the dock at first using a spreadsheet program such as Excel Spreadsheet. These profiles can be pre-loaded to a hand held computing device such as a SPT 1700 allowing easy selection once on the water. The DAP's can also be edited or created once the boat has left on the hand held device, by entering the DAP screen 10 the user is displayed with a list of current DAP's 11. By tapping a DAP, the user is shown the details of that DAP 12. From here the DAP can be edited to suit the conditions if that DAP has changed since the original collation of that DAP. If changes are made, and the OK button is pressed from the New/Edit View DAP screen the record will be saved. Pressing Cancel will ignore any changes to the DAP. New DAP's can be created in the field by tapping the New button 13 when in the DAP screen. As with Edit DAP, the changes will not be saved until the OK button 14 is pressed. When new records are entered the OK button will be not available until the Environmental Hazards and Emergency procedures screen 15, 16 have been entered. The Emergency Procedures screen 16 is a multi line text field. The Environmental Hazards screen 15 has a multi line input field that can be edited using the normal Palm input methods. An Add button 17 will allow entries from a drop list to be added to this field. Guest Profile GP (see figure 2)

Guest profiles GP need to be created before guests can board the boat he only data that can not be pre-loaded is the tag number, medical certificate details, diver certificate details and signatures. This data can be created in an Excel spreadsheet at first. If the guest wishes to dive, the Diver screen must be entered. The GP can be pre-loaded as with the DAP for convenience. GP's can be altered if they are incorrect, by tapping the GP from the list. Tapping the new button 20 can create new GP's. New and changed records will be sent to the PC on download. All people on board the vessel are required to have a GP, including staff. Once the GP's are created and have a barcode assigned (the PIM); guests are presumed to have boarded the vessel. Each guest must wear the PIM, and in the embodiment, the PIM is a wrist strap, or tag containing the barcode, the barcode being unique for each guest.

This is done through the Main Menu screen 21 , by simply scanning the wrist strap or tag of that particular guest which will board that guest if they are not on the vessel. After scanning the barcode, the user will need to select the guest or create a new guest, as the tag ID is initially blank.

The guest status will then be updated to "O".

The user is shown the Activity Selection Screen (see figure 3), if the guest is already on the vessel. The user then selects the disembarking button 30 if the guest is to leave the vessel; they are then asked if the guest is leaving the vessel permanently or not. If yes are selected 31 , the guest status is set to "L", and their record is closed, and that barcode will not be able to be re-used. If No are selected 32, the guest's status is set to "T", yet their record remains active. If the guest is scanned once they have been temporarily removed, they will be returned to the vessel as per the boarding procedure once a guest has boarded, the record will not be able to be edited and will be locked. Leaving Site (Including Dock) (see figure 2)

Before leaving any site, including the dock, the user must scan their ID, enter the location which they are leaving from This can be scanned from a template or selected from the location search screen 33. They then must do a head count 34, and it must be completed correctly before the program will allow the user to return to the Main Menu 21. This process will create a record in the vessel log. If a dive has been completed that will be the default location. If the head count is incorrect, compared with the number of guests on the boat shown by the status field in the guest file, the User will be notified 35, and a re-count must occur 35. If the head count is still incorrect 36, the User must scan 37 all guests to confirm the head count. If all guests cannot be scanned, the missing guest will be shown. At this time the User must enter comments on circumstances 38. Once user has completed a correct and verified head count, program will prompt user to sign screen to verify. This data is saved to the Vessel Log. Going Diving (see figure 4)

Only Guests with a GP, medical certificate details and current diving certificate details can go diving. Groups (dive header records) are not created until on the site, as certain details are unknown until that time. From the Main Menu 21 , the User can scan a wrist tag to initiate the dive, at this time the User will need to select the Scuba 40 or Snorkel 41. From here the dive header record is created. After the Record is created the DAP is selected 42. At this stage the DAP can be edited, or a new DAP created, by selecting the DAP and tapping Edit 43. The User will then be sent to the New/Edit screen 44. If no DAP is selected, and the New button 45 is selected the User will be sent to the same screen with no details pre-entered .In the case of scuba 40, once the DAP has been selected, only scuba DAP's will be shown. The details are stored in the dive record and the OK tapped, the Tank size and pressure is required to be entered by ticking the relevant box 46. They will then be added to the Group by creating a diver record that is linked to the diver header. Another screen can be developed after 'enter tank details' which displays 'pressure group and surface interval'. This will be displayed after the 2^nd dive.

In the case of snorkel (see figure 7), once the DAP has been selected, only snorkel DAP's will be shown. The details are stored in the dive record and the OK tapped, the lookout 70, being the person monitoring the alarms and divers in the water, is required to be entered by scanning or using the palm data entry methods. They will then be added to the group by creating a diver record that is linked to the dive header. Referring to figure 4, each diver will be assigned a Buddy automatically 47 (i.e. Diver 1 : Buddy: Diver 2). If there is a diver without a buddy, the User will be sent to the buddy allocation screen 47 where that diver can be allocated to a Buddy pair, making a Buddy trio. This buddy information is recorded in each diver record. Also if there is not a valid group leader to diver ratio the user will not be able to proceed (except in the case of snorkelling where the group leader is not recorded). The group leader to diver ratio is 1 :4. If the ratio is wrong the user will be asked to assign a group leader, this will change the guest record to enable them to be a group leader. Once all divers have been scanned and allocated buddies, OK

48 is tapped and the details of the DAP is read from the dive record and are displayed for re-confirmation. The User is not able to proceed to the" Start the

Dive" until the Environmental Hazards 50 and Emergency Procedures 49 have been viewed.

When Ready to Dive OK 51 is tapped from the DAP, and the dive times 52 are calculated, in the following way;

If Dive 1 , check depth and O² consumption rate, giving max time. Compare max time with scuba diving tables, to ensure no decompression dive, if outside deco table use no deco time.

If multiple dive check depth and O² consumption rate, giving max time. Compare max time with deco table, taking into account surface interval, ABT (actual bottom time) & RNT (residual nitrogen time). Use lower value for safety. The lowest value for the entire group is the value used for all divers in that group. Full duration = Max dive time - 5 min Working duration = Max dive time - 10min Safety stop = Max dive time - 15min Snorkel head count check equals every 20 minutes from first start time (no separate timers for each group).

Once the dive times are known, the divers enter the water after setting their watches. When the start timer is tapped the dive times are started and the User is shown the dive timer countdown and alarm screen. Pressing the Back key in any Menu will take the User back 1 step, and ignore any changes to the screen the User is going back from. The cancel button will remove all dive details and deletes dive header and diver detail records.

It is envisaged to download dive times to a timer through the Infra red port or by wireless communication means Alarms (see figure 5)

After the Divers enter the water, the dive timers are started. Once the dive timers are started the default screen 55 will show the dive timer count down, where a count down of each group is kept. Also in this screen is a scan line 56. If a barcode is scanned from this screen the program will determine if the diver is in the water. If they, they are scanned back onto the vessel, the time out will be recorded for that diver. If the diver is not in the water the program will treat this diver as the first diver for a new group and proceed as per Going Diving procedure.

Once the Safety Stop time has been reached, an alarm will sound. The User should check to assure the divers are under the vessel. Once this is confirmed tapping the alarm on the screen 57 can disable this alarm.

When the working duration alarm sounds it will continue until all divers are scanned onto the boat. When scanning the divers back on to the boat, the diver is required to sign the screen to verify boarding 58, and the operator may enter other details such as exit pressure, actual depth and record if the dive was done using a dive computer.

If the full duration alarm sounds, the procedures are the same as for the working duration.

When the snorkel head count check alarm sounds the user will need to acknowledge the alarm by tapping it. This alarm will show the number of snorkellors in the water, and prompts the user to conduct a head count.

If for some reason a tag cannot be scanned, the User must invoke the Emergency procedure, tap Emergency and then type 4321 on the keys, and manually enter comments.

By tapping on the alarm or the group countdown the User can check whether the divers and their buddies have or have not yet been scanned back onto the boat. From here it is also possible to view the DAP to see where the divers should be.

After the entire group has been scanned out of the water the group leader must sign to verify 59. The signature reference will be recorded in the dive file.

If the barcode of a guest is scanned and they are on the boat and alarms are going off the user will be returned to the going diving/disembarking screen to process the guest. At the end of each dive, comments about the dive can be entered into the device. Management Functions (see figure 6) Receive Files ^■ On selecting Receive Files 60 from the main menu the user will be prompted to confirm the operation. At this time the user should ensure the comms software on the PC is running

^■ After confirmation communication will begin and the number of records being received will be shown on both the handheld and the PC ^■ Cancel will take the user back to the main menu

^■ At the end of the communication process the total number of records will be shown on both the handheld and the PC at this time the user will be prompted to return to the main menu

Send Data " On selecting Send Data from the main menu 61 the user will be prompted to confirm the operation. At this time the user should ensure the comms software on the PC is running

^■ At this stage the user will need to select the files to be sent. The only file that is optional is the DAP, which will only be available if the DAP has been flagged as changed.

^■ After confirmation communication will begin and the number of records being sent will be shown on both the handheld and the PC

^■ Cancel will take the user back to the main menu

^■ At the end of the communication process the total number of records will be shown on the PC. At this time the user will be prompted to return to the main menu

^■ When sending the data to the PC all of the records on the handheld will be removed to ensure the most up to date information at the start of each collection process ■ Exit will return the user to the Application Menu

■ Start Day

^■ On selecting Start Day 62 the user will need to enter the details as asked. First the user will be asked for the Vessel ID (Registration No) and have to scan the Dive master's ID.

^■ Tapping OK will save the record and Cancel will return to the Management functions screen without recording the details.

^■ Data File Definition Dive Tables

• Data will be uploaded from the PC to the handheld in ACSII CSV format from a file with the name of padi(xj.txt where x is the dive table represented. The parameter data will be taken from recognised dive tables such as PADI dive tables. Emergency Procedures

• Data will be uploaded from the PC to the handheld in ACSII CSV format from a file with the name of emergency.txt. The data will be in the following format:

^■ Text (Alphanumeric - 500 Characters) Guest Log

• This data file when downloaded to the PC will be sorted by "Tag ID" with a file name of guests.txt. It will be in the following format:

^■ Tag ID (Numeric - 6 Characters)

^■ Group Leader (Alphanumeric - 1 Character) ■ Diver Master (Alphanumeric - 1 Character)

^■ Diver Surname (Alphanumeric - 15 Characters)

^■ Diver First Name (Alphanumeric - 15 Characters)

^■ Sex (Alphanumeric - 1 Character)

^■ Age (Numeric - 3 Characters) ^■ Medical Verification (Alphanumeric - 1 Character)

^■ Medical Check Comments (Alphanumeric - 50 Characters)

^■ English Speaking (Alphanumeric - 1 Character)

^■ Dive Number (Numeric - 1 Character)

^■ Status (Alphanumeric - 1 Character) temporary, not outputed • The PDE will maintain the following indexes on the guests file

> Tag ID

> Surname It should be appreciated that all data files as described are an embodiment only and changes to the type, size and format of data files can be made. Diver File

• This data file when downloaded to the PC will be sorted by "Tag ID" then "Dive Start Time" with a name of dives.txt. It will be in the following format and there will be 1 per diver per dive:

Dive Number (Number - 2 Characters)

Tag ID (Numeric - 6 Characters) ^■ Buddy Tag ID (Alphanumeric - 6 Characters)

Buddy 2 Tag ID (Alphanumeric - 6 Characters)

Environmental Hazards Check (Alphanumeric - 1 Character)

Procedure Check (Alphanumeric - 1 Character)

Dive Time In (Alphanumeric Time - dd-mm-yy/hh:mm) ^■ Dive Time Out (Alphanumeric Time - dd-mm-yy/hh:mm)

Surface Interval (Alphanumeric - dd-mm-yy/hh:mm)

ABT (Alphanumeric Time- hh:mm)

RNT (Alphanumeric Time- hh:mm)

TBT (Alphanumeric Time- hh:mm) ^■ Pressure Group In (Alphanumeric - 1 Character)

Pressure Group Out (Alphanumeric - 1 Character)

Emergency Procedure Comments (Alphanumeric - 100 Characters)

Tank Size (Alphanumeric - 3 Characters) ^■ Tank Pressure (Alphanumeric - 3 Characters)

• The PDE will maintain the following indexes on the dives file > Tag ID

Dive File

This data file is the dive header file when downloaded to the PC will be sorted by "Dive Number" with a file name of guests.txt. It will be in the following format:

^■ Dive Number Location (Alphanumeric - 10 Characters) Diver Master ID (Alphanumeric - 6 Characters) Dive Depth (Numeric - 3 Characters) Dive Direction (Alphanumeric - 10 Characters) Current (Alphanumeric - 10 Characters) Environmental Hazards (Alphanumeric - 100 Characters) Type Of Dive (Alphanumeric - 1 Character "N" - Snorkel or "C" - SCUBA) Profiles • This data file when downloaded to the PC will be sorted by "Location" with a name of profiles.txt. It will be in the following format:

^■ Location (Alphanumeric - 10 Characters)

^■ Dive Depth (Numeric - 3 Characters)

^■ Dive Direction (Alphanumeric - 10 Characters) ^■ Current (Alphanumeric - 10 Characters)

^■ Environmental Hazards (Alphanumeric - 350 Characters)

^■ Emergency Procedures (Alphanumeric - 350 Characters)

^■ Update Flag (Alphanumeric - 1 Character)

Type Of Dive (Alphanumeric - 1 Character "N" - Snorkel or "C" - SCUBA)

• The PDE will maintain the following indexes on the profiles file

> Location

> Type Vessel • This data file when downloaded to the PC will be sorted by "Vessel ID" then "Location" with a name of vessel.txt. It will be in the following format:

^■ Vessel ID (Alphanumeric - 10 Characters)

^■ Date (Alphanumeric Date - dd-mm-yy)

^■ Location (Alphanumeric - 10 Characters) ^■ Start Time (Alphanumeric Time - hh:mm)

^■ Finish Time (Alphanumeric Time - hh:mm)

^■ Head Count (Numeric - 2 Characters) ^■ Counted (Numeric - 2 Characters)

^■ User ID (Alphanumeric - 6 Characters)

^■ Missing Guest Comment (Alphanumeric - 100 Characters) Location Data will be uploaded from the PC to the handheld in ACSII

CSV format from a file with the name of emergency.txt. The data will be in the following format:

^■ Location (Alphanumeric - 10 Characters) i.e. Dock Temporary Guest List This file is a temporary file that records the guest numbers on the vessel for verification when leaving a site.

^■ Tag ID (Numeric - 6 Characters)

^■ Diver Surname (Alphanumeric - 15 Characters)

^■ Diver First Name (Alphanumeric - 15 Characters) • Data Storage Requirements

^■ The SPT1700 required for the expected data requirements can be a SPT1700-ZRG80200 (1 D Batch, 2MB ROM/8MB RAM), although this can change.

Claims

CLAIMS:

1. A method for diver accountability, the method comprising the steps of:

II providing a personal identifying means (PIM) to each diver,

III inputting the PIM into a computer prior to a dive,

IV providing at least one tag on the diving equipment of each diver and which contains information, V inputting dive information into the computer, the dive information including details of the tank capacity, dive depth, dive time,

VI starting a timer when the divers go into the water,

VII inputting the PIM into the computer when a diver exits the water

VIII providing an alarm that will trigger if the PIM of a particular diver has not been inputted into the computer after predetermined time has passed.