FIELD

[0001] The present description generally relates to creating risk assessments for a geological fie!dtrip, and more particularly, to creating risk assessments and dynamically assessing the risks during the course of the geological fieldtrip to provide updated information of the risks encountered during the geological fieldtrip.

BACKGROUND

[0002] Geological fieldwork is a fundamental component in geoscience teaching and research, and involves performing geology related activities (e.g., research, exploration, investigation, etc.) out in the field as opposed to in a laboratory or office. Health, Safety, and Environment (HSE) regulations require risk assessments to be created and distributed to the fieldtrip participants as well as the participants host institution(s) and/or organization(s). The risk assessment for the geological fieldtrip is designed to ensure that all participants are aware of the various risks, also referred to as threats, that may potentially be encountered, their likelihood (e.g., Low, Medium, High) of occurrence, consequence (e.g , lost field time, injury, or fatality) and to detail the factors for mitigating each risk (e.g. wearing correct protective equipment, ensuring participants are not trapped by rising tides).

[0003] The generation of such risk assessments is often time consuming and the risk assessments are typically created in advance of going into the field. While some risks can be anticipated beforehand (e.g., environmental conditions, severe weather conditions, etc.) and included in the assessment, it can be challenging to include non-predictable site-specific risks or dynamic or evolving risks. Thus, the reports including the different risk assessments are generally“static” reports because risk assessments in these reports will often remain unchanged during the fieldtrip. As a result, the fieldtrip trip participants are only made aware of changes in the existing risks and/or of the occurrence of new risks verbally by fieldtrip leaders and the participants host organization(s) have no way to monitor these dynamic changes. BRIEF DESCRIPTION OF THE DRAWINGS

[0004] The following figures are included to illustrate certain aspects of the embodiments, and should not be viewed as exclusive embodiments. The subject matter disclosed is capable of considerable modifications, alterations, combinations, and equivalents in form and function, as will occur to those skilled in the art and having the benefit of this disclosure.

[0005] FIG. 1 illustrates a flowchart of a method of generating a risk assessment for a fieldtrip itinerary, according to one or more embodiments disclosed.

[0006] FIG. 2 illustrates an example risk assessment form for creating a risk assessment of one or more risks to be encountered at a desired fieldtrip destination.

[0007] FIG. 3 is a flowchart of a method of providing field participants with risk alerts when on the field, according to one or more embodiments disclosed.

[0008] FIG. 4 illustrates an example risk assessment form for a single parameter, infectious diseases, in three separate countries.

[0009] FIG. 5 illustrates an example risk assessment form for a single parameter, tidal range, in three different locations.

[0010] FIG. 6 illustrates a schematic diagram of an example of an environment for implementing aspects in accordance with various embodiments.

[0011] FIG. 7 illustrates a schematic diagram of a set of general components of an example computing device for implementing the methods of FIGS. 1 and 3, according to embodiments disclosed.

[0012] In one or more embodiments, not all of the depicted components in each figure may be required, and one or more embodiments may include additional components not shown in a figure. Variations in the arrangement and type of the components may be made without departing from the scope of the subject disclosure. Additional components, different

components, or fewer components may be utilized within the scope of the subject disclosure.

DETAILED DESCRIPTION

[0013] The present disclosure is related to methods of creating dynamic risk assessment, and more particularly, to dynamically assessing the risks during the course of the fieldtrip and providing an updated risk assessment based on the changes.

7 [0014] Embodiments disclosed also improve upon the risk assessment procedure by automating the assessment of risks prior to visiting the field. While in the field, participants are automatically provided with risk alerts in real time (or near real-time) so that participants can take corrective actions to mitigate or otherwise avoid developing threats (e.g., extreme weather events, security issues).

[0015] Embodiments disclosed also provide crowdsourcing capabilities, wherein present fie!dtrip participants can obtain the risk assessment of destinations previously visited by other individuals since these individuals may already have identified non-predictable, location specific threats, thereby ensuring that present fie!dirip participants can be aware of current conditions and more easily address them.

[0016] According to embodiments disclosed, a fieldtrip participant may manually update the risks while in the field and provide this information to the other participants. In other embodiments, if the conditions on the field become increasingly dangerous, the fieldtrip leader may be able to transmit a notification to indicate stoppage of work to all fieldtrip participants. These manual updates may be stored for future use. For instance, the updates may be stored for use in future crowdsourcing situations.

[0017] As disclosed herein,“risk assessment,” or variations thereof, relates to identifying ways by which risks or threats encountered on a fieldtrip may be mitigated. This may include identifying personal protective equipment to be used on an action to be undertaken when a risk is encountered.

[0018] FIG. 1 illustrates a flowchart of a method 100 of generating a risk assessment for a fieldtrip itinerary, according to one or more embodiments disclosed. The method 100 may constitute the planning stage of the fieldtrip and may therefore be performed prior to visiting the field. In an embodiment, the method 100 (or at least a portion thereof) may be performed using one or more data processing devices including, but not limited to, desktop computers, laptops, workstations, or any other data processing device having appropriate processor, memory, and communications capabilities. In the method 100, a user, e.g , a fieldtrip participant, may create a fieldtrip itinerary including a destination (e.g., geological site) to be visited, as at 102. The fieldtrip itinerary may be created using a risk assessment software application that generates the risk assessments reports. The application may be stored in the memory of the data processing device. The memory is coupled to the processor and the application may be executed using the processor. In an embodiment, the application may be an internet-based application and may be accessed using a web browser of the data processing device. The web browser may be displayed on a display screen communicably coupled to the data processing device, thereby providing the user interface for creating the fieldtrip itinerary.

[0019] For each destination listed in the itinerary, a risk assessment may be generated from the beginning or a pre-existing risk assessment may be used if available. For instance, previous users have already created a risk assessment of one or more risks encountered at one or more destinations in the current itinerary. At 104, after the destination has been added to the fieldtrip itinerary, the user is notified of any such existing risk assessment(s). At 106, if an existing risk assessment is not available, or if a user desires to ignore the existing risk assessment and create a new risk assessment, then, at 108, the user may create a new risk assessment. In creating the new risk assessment, the user may be provided guidance to fill in the required information. In an example, the risk assessment software application may include a set of subroutines or protocols that may guide the user for generating the trip itinerary

[0020] Referring briefly to FIG. 2, illustrated is an example risk assessment form for creating a risk assessment of one or more risks to be encountered at a desired trip destination. As illustrated, the form 200 is in a tabular format including the one or more risk elements 202. Also included in the form 200 is the risk information corresponding to each risk. The risk information may include the cause 204 of each risk (or the conditions that cause the risk), one or more consequences 206 of encountering the risks, the probability 208 (of each consequence occurring), effect 210 of each risk consequence, the overall risk level 212, control measures 214 to be performed to mitigate (or avoid) each risk, the individuals 216 on the trip who should implement the control measures, and a level 218 of any residual risk remaining after actions to mitigate the consequences of risk have been undertaken. The probability, the level of each consequence, the effect of each consequence, and the residual risk level may be indicated using a scale of L-Low, M-Medium, and H-High. Embodiments disclosed enable auto-populating certain aspects of the risk assessment form. For instance, the effect 210 of each risk consequence and/or the overall risk level 212 may be auto-populated using one or more user-defined API’s (e.g., FIGS. 4 and 5). In an example, users may populate the consequences 206 from a drop down list which in turn auto-populates that effect 210 field using the API’s. Based on the probability 208 and effect 210, risk 212 may be auto-populated. [0021] Returning to FIG. 1, instead of creating a new risk assessment, at 110, the user may use an existing risk assessment (e.g., created via the ri sk assessment form 200) for one or more destinations in the itinerary. The existing risk assessment may be obtained from a database that may store all newly created and old risk assessments for future retrieval. At 112, the user may obtain an existing risk assessment and modify based on the current itinerary.

[0022] In both instances where the new risk assessment is created from the beginning (108) or from existing risk assessments (112), some of the risk information in the risk assessment form may be auto-populated, as at 114. Auto-populating as used herein indicates that the risk information is filled in the risk assessment form autonomously without user intervention. Auto population of the risk information may be based on the destination indicated in the risk form. Auto-populating may use a set of subroutines or protocols (e.g., API’s) that check one or more external resources for data related to the risk information. For instance, the one or more external resources may include government agencies such as the National Oceanic and Atmospheric Administration (NOAA), National Weather Service, or other private or public sources of information. As an example, the risk element‘exposure to adverse weather’ may be auto- populated from data obtained from one or more external resources including government agencies such as the National Oceanic and Atmospheric Administration (NOAA), National Weather Service, or other private or public sources of information

[0023] For example, the risk information that may be auto-populated may include risks such as, climate hazards associated with the destination, traffic conditions in the area, dangerous wildlife, local security advisories, and the like that may be encountered for the duration of the field visit. As an example, if the fieldtrip is planned for a destination in June, a risk associated with severe heat at the destination may be auto-populated when creating a risk assessment. The location of the nearest emergency services is of importance when in the field, and accordingly this information may be auto-populated for each destination. However, it will be understood that the user may be able to edit the auto-populated information, without departing from the scope of the disclosure.

[0024] Additionally or alternatively, the information in the risk assessment form may be auto-populated based on information provided by users that have visited the destination previously. This crowdsourcing of information may be useful in assessing risks that can be assessed only when in the field. For example, risks such as the nature of the ground in the field (e.g. slippery boulders on coastal sections), the stability of coastal cliffs, the quality of trails, and the like, may be assessed only when in the field. Assessing these kinds of risks at the planning stage may often require a reconnaissance trip or may require dynamic risk assessments to be made in the field, costing time and money. Example embodiments disclosed overcome this issue through users being able to recycle risk assessments created by prior users who have visited the destination previously, effectively crowdsourcing the risk data.

[0025] The method 100 then determines whether the user has input information for all destinations in the itinerary, at 1 16. If there are one or more destinations remaining to be added to the itinerary, then the method 100 prompts the user to include the remaining destinations. When all destinations have been included in the itinerary, risk information including an overview of the fieldtrip risk assessment is generated based on all the risk assessments of all the individual destinations, at 1 18. The fieldtrip overview risk assessment includes a list of all the unique risks from the combination of sites (e.g. if there is a slips, trips risk at each site only one is included in the overview). Where two or more risks occur at different sites that are identical apart from the probability, effect and risk rating, the highest risk item is included in the overview assessment. The overview and the individual destination risk assessments are then provided to ail participants of the trip, at 120. The individual site risk assessments are provided so that attendees know what specific personal protective equipment (PPE) is needed at each locality and are aware of the specific risks at that site (e.g. a traffic risk may only be present at 1 out of 10 sites. The overview assessments may indicate that attendees bring a high visibility jacket on the trip to mitigate the risk, but they may not need to bring it into the field each day or to visit every ⁷ site)

[0026] The fieldtrip risk assessment overview may be downloaded or otherwise provided on portable electronic devices, e.g., tablet computers (e.g., including e-book readers), mobile devices (e.g., a smartphone or PDA), or any other portable data processing device having appropriate processor, memory, and communications capabilities. These portable electronic devices may be carried by each individual field participant on the fieldtrip. The portable electronic device of each user may include the risk assessment software application. In other examples, a mobile version of the risk assessment software application configured to monitor for risks when on the field may be included in the portable electronic device.

[0027] FIG. 3 is a flowchart of a method 300 of providing field participants with risk alerts when on the field, according to embodiments disclosed. As mentioned above, the method 300 (or at least a portion thereof) may be performed using one or more portable electronic devices. The risk alerts may be based on the fieldtrip risk assessment overview and the individual destination risk assessments created using the method 100 discussed above. The method 300 may be initiated when the user (field participant) is in the field, at 302. The risk assessment software application may monitor the risk information in the fieldtrip risk assessment overview using the location of the user (for example, obtained via GPS) and risk related data obtained from external data resources, at 304. The external data resources (for example, government agencies or other private or public resources) may be checked for updates related to the risk information, at 306. The checks may be performed at or near real time and risk assessments may be dynamically updated with any new risk information. In the event there is any change in the risks or the risk information, an alert may be generated on the portable electronic device for the user, at 308. For instance, risks related to severe weather events (tornadoes), storm surges, lightening, sandstorms, wildfires, etc. may develop in a relatively short period of time. The software application may monitor the external resources (e.g., data from the National Weather Service) for updates in the conditions that cause the risks and generate an alert to the user if these conditions have changed at the destination.

[0028] In an embodiment, the alerts may be provided if a certain risk criteria included in the risk assessment overview is sati sfied. For instance, if the temperature at the destination drops below a predetermined value or goes above a predetermined value, an alert may be generated. According to embodiments, in addition to monitoring and updating the risks, the software application may also update the information on the nearest emergency service facility (e.g., hospital, ER’s), Emergency Services (Fire, Coast Guard, EMS, Law Enforcement Agency), Embassy, and Local Authorities This may be performed based on the risks presently or anticipated to be encountered so that the appropriate emergency service may be available, is required.

[0029] According to embodiments disclosed, the method 300 may permit the user to manually update the risk assessment in the event new risks are observed, at 310. For example, the user may manually update the risk assessment when the new risks are not automatically detectable. For instance, while on a fieldtrip, a user notices that the cliff section of the path has become unstable (which may not be automatically detectable) and is unsafe to pass, the user may mark the location on a map as unsafe and suggest an alternative route, which may be provided as an alert to the other participants. As another example, the fieldtrip leader may be able to send an alert or notice to the other participants in the event the field conditions become dangerous and work has to be stopped. At 312, the system may send regular reminders to the user about the risks at each destination so as the keep the user aware of the various risks from the risk assessment overview that may be encountered. These reminders may ensure that the user is mindful of the risks (for instance, of time dependent risks (such as high tide times)) and is made aware of the risks prior to occurrence of the risks so that adequate time may be available to take necessary corrective actions. The corrective action may be an action specified in the risk assessment. It should be noted that, any new risks encountered or manually updated may be stored in a database for future reference (e.g., when crowdsourcing data).

[0030] In order to be able to plan the trip in the most effective manner, utilize crowd sourcing of risk assessments, share information with other participants, and to utilize dynamic updating and push notification, the methods 100 and 300, according to embodiments disclosed, may be implemented in an internet-based environment. In this regard, the planning phase may be carried out on a website where a map interface may allow effective fieldtrip itinerary planning and information from one or more other resources. In this environment users can make use of crowd sourced risk assessments. Once the trip plan is complete it can then be“pushed” to the mobile application executing on the portable electronic devices of the fi eldtrip participants so that all participants and their host institutions have access to the plan and risk assessment at all times. Dynamic updating, as discussed above, may utilize the GPS functionality and mobile data connections of the portable electronic devices and all alerts may be provided by the mobile application.

[0031] Provided below are some example risk assessment forms generated for different risk parameters. These risk assessments are provided as just a few examples of a variety of risk assessments using the principles disclosed herein.

[0032] FIG. 4 illustrates an example risk assessment form 400 for a single parameter, infectious diseases, in three separate countries. As an example, once a user adds a destination, the application will receive information on the range of infectious diseases present in the country or region being visited. In an example, the information in columns 402 (e.g., endemic infectious diseases, probability of exposure to disease, and effect of the disease) related to the infectious disease in each country may be automatically populated during the initial phase of planning, prior to going into the field. For instance, this information may he obtained from different travel advisories issued by the government based on the country. The information column 404 may be automatically calculated based on the probability and effect columns 402. The information in the columns 406 may be input by the user when preparing the itinerary, or the information may be chosen from a drop down menu option. Alternatively, the information may be auto- populated (for instance, based on the country and infectious diseases in that country (column 402). By compiling this one parameter, infectious diseases, with all other parameters (e.g., natural hazards, terrorism, wildlife, and road safety) considered during the fieldtrip, an overall risk assessment may be obtained.

[0033] FIG. 5 illustrates an example risk assessment form 500 for a single parameter, tidal range, in three different locations. As an example, once a user adds a destination, the application will be able to identify that it is situated on the coast. Based on this information, an unmitigated risk associated with the tidal range at that location will be calculated, along with the

consequences of the threat and a suggested mitigation procedure, as illustrated in FIG. 5 In an example, the information in the columns 502 may be automatically populated during the initial phase of planning, prior to going into the field. For instance, this information may be obtained from the National Weather Service or other online resources and API’s). The information in column 504 may be automatically calculated based on the probability and effect columns 502. The information in columns 506 may be provided by the user, or the information may be chosen from a drop down menu option. Alternatively, the information may be auto-populated (for instance, based on the risk type and/or the tidal range (column 502). By compiling this one parameter, tidal range, with all other parameters (e.g., proximity to roads, average swell conditions, proximity to natural hazards (e.g. active volcanoes)) considered during the fieldtrip, an overall risk assessment may be obtained.

[0034] Embodiments disclosed provide numerous advantages over the prior art. For instance, by providing a dynamic risk assessment, fieldtrip participants and host institutions may be made aware of risks in advance or in near real time and are therefore provided with more opportunities to mitigate the risks. Also, by considering prior information about risks from prior risk assessments, the overall knowledge about the fieldtrip risks may be increased and trip participants may be better informed prior to beginning the trip. By considering the risks from a wide variety of parameters, make the risk assessments more robust, dynamic and informative. [0035] The risk assessment may be performed based on other parameters relating to travel requirements associated with the fiekltrip (e.g. visas) and permit requirements (e.g. permits necessary to visit individual destinations or take geological samples). Although embodiments are described with reference to improving the safety of field geologists, embodiments may also be used for other activities. These include activities where it is necessary to lead a group of individuals outside (e.g. scouts groups, school trips) or by non-led outdoor users (e.g. lone hikers, hiking groups, back packers), drill rig site workers, construction or site investigations, and the like, without departing from the scope of the disclosure. Embodiments disclosed may also be used to track and share the location of all fieldtrip participants, and, if needed, send this information to a centralized location, e.g., a site office or head office, when used within a professional field work capacity, e.g., site investigations

[0036] As discussed herein, different approaches can be implemented in various

environments in accordance with the described embodiments. For example, FIG. 6 illustrates an example network environment 600 in which a system for providing field participants with risk alerts when on the field may be implemented in accordance with one or more embodiments. As will be appreciated, although a client-server based network environment is used for purposes of explanation, different network environments may be used, as appropriate, to implement various embodiments. The network environment 600 includes a client device, which can be an electronic device 602 and which can include any appropriate device operable to send and receive requests, messages or information over an appropriate network 604 and convey information back to a user of the electronic device 602. Examples of such an electronic device 602 may include, for example, a personal computer, a mobile device, a tablet device, a laptop computer, and the like.

[0037] The network 604 can include any appropriate network, including an intranet, the Internet, a cellular network, a local area network, a public network, a private network, or any other such network or combination thereof. The network 604 could be a "push" network, a "pull" network, or a combination thereof. In a "push" network, one or more of the servers push out data to the client device. In a "pull" network, one or more of the servers send data to the client device upon request for the data by the client device. Components used for such a system can depend at least in part upon the type of network and/or environment selected. Computing over the network 604 can be enabled via wired or wireless connections and combinations thereof. In this example, the network includes the Internet, as the environment includes a server 606 representing off-site computing facilities for receiving requests and serving content in response thereto, although for other networks, an alternative device serving a similar purpose could be used.

[0038] The server 606 typically will include an operating system that provides executable program instructions for the general administration and operation of that server and typically will include computer-readable medium storing instructions that, when executed by a processor of the server, allow the server to perform its intended functions. The network environment 600 in one or more embodiments is a distributed computing environment utilizing several computer systems and components that are interconnected via computing links, using one or more computer networks or direct connections. However, the depiction of the network en vironment 600 in FIG. 6 should be taken as being illustrative in nature and not limiting to the scope of the disclosure.

[0039] Storage media and other non-transitory computer readable media for containing code, or portions of code, can include any appropriate storage media used in the art, such as but not limited to volatile and non-volatile, removable and non-removable media implemented in any method or technology for storage of information such as computer readable instructions, data structures, program modules, or other data, including RAM, ROM, EEPROM, flash memory or other memory technology, CD-ROM, digital versatile disk (DVD) or other optical storage, magnetic cassettes, magnetic tape, magnetic disk storage or other magnetic storage devices, or any other medium which can be used to store the desired information and which can be accessed by the electronic device 602 and/or the server 606.

[0040] The process of providing field participants with risk alerts when on the field may be implemented by one or more (one shown) electronic devices 602 and/or the server 606. The electronic device 602 may execute a software application for providing field participants with risk alerts when on the field. The application may be installed locally on the electronic device 602 or may be an internet-based application, such as a web application or a mobile application, and a user may access/interact with the software application via a user interface provided by the electronic device 602, such as a web browser.

[0041] FIG. 7 illustrates a schematic diagram of a set of general components of an example computing device 700. In this example, the computing device 700 includes a processor 702 for executing a risk assessment software application 706 (or a mobile version thereof) stored in one or more memory devices 704 (one shown) communicably coupled to the processor 702. The risk assessment software application 706 may generally be a computer-readable program code that may create an execution environment for implementing the methods 100 and 300. The computing device 700 can include many types of memory, data storage, or non-transitory computer-readable storage media, such as a first data storage for program i structions for execution by the processor 702, a separate storage for images or data, a removable memory for sharing information with other devices, etc.

[0042] In order to load the risk assessment software application 706 in the memory device 704, the computing device 700 may include one or more input/output modules 710 (one shown) via which the risk assessment software application 706 may be loaded into the memory device 704. Example input/output modules 710 include data ports such as USB ports. The input/output module 710 is configured to connect to a communications module 712. Example

communications modules 712 include networking interface cards, such as Ethernet cards, modems, and communication interface elements for communicating over various networks, such as a Wi-Fi, Bluetooth, RF, wired, or wireless communication systems. The computing device 700 further includes a data storage device 718 such as a magnetic disk or optical disk for storing information and instructions.

[0043] The computing device 700 typically may include some type of output device 716 that may be a display element, such as a touch screen or liquid crystal display (LCD). As discussed, the computing device 700 in many embodiments will include at least one input device 714 that receives conventional input from a user. This conventional input can include, for example, a push button, touch pad, touch screen, wheel, joystick, keyboard, mouse, keypad, or any other such device or element whereby a user can input a command to the device. In some

embodiments, however, such the computing device 700 might not include any buttons at all, and might be controll ed only through a combination of vi sual and audio commands, such that a user can control the computing device 700 without having to be in contact with the computing device 700. The computing device 700 in many embodiments can communicate with a network, such as the Internet, and may be able to communicate with other such computing devices. All components of the computing device 700 may be coupled to each other via a system bus 701.

[0044] Embodiments disclosed herein include: [0045] Embodiment A. A computer-implemented method, comprising: generating an itinerary for a geological fieldtrip including a destination, generating a risk assessment including a plurality of risk elements at the destination, wherein the risk assessment is provided to fieldtrip participants and includes risk information of each risk element at the destination, the ri sk information including one or more actions that are performed to address each risk element; obtaining data from one or more external resources at the destination, the data obtained pertaining to the plurality of risks at the destination, updating the risk information of one or more risks based on the data, and thereby obtain an updated risk information; and providing the updated risk information to the trip participants when the trip participants are at the destination in order for the trip participants to perform one or more actions needed to address a corresponding risk element based on the updated risk information.

[0046] Embodiment B. A system, comprising: a processor; and a memory device including instructions that, when executed by the processor, cause the processor to: generate an itinerary for a geological fieldtrip including a destination; generate a risk assessment including a plurality of risk elements at the destination, wherein the risk assessment is provided to trip participants and includes risk information of each risk element at the destination, the risk information including one or more actions that are performed to address each risk element; obtain data from one or more external resources at the destination, the data obtained pertaining to the plurality of risks at the destination; update the risk information of one or more risks based on the data, and thereby obtain an updated risk information; and provide the updated risk information to the trip participants when the trip participants are at the destination in order for the trip participants to perform one or more actions needed to address a corresponding risk element based on the updated risk information.

[0047] Embodiment C. A non-transitory computer-readable medium including instructions stored therein that, when executed by at least one computing device, cause the at least one computing device to: generate an itinerary for a geological fieldtrip including a destination; generate a risk assessment including a plurality of risk elements at the destination, wherein the risk assessment is provided to trip participants and includes risk information of each risk element at the destination, the risk information including one or more actions that are performed to address each risk element, obtain data from one or more external resources at the destination, the data obtained pertaining to the plurality of risks at the destination; update the risk information of one or more risks based on the data, and thereby obtain an updated risk information; and provide the updated risk information to the trip participants when the trip participants are at the destination in order for the trip participants to perform one or more actions needed to address a corresponding risk element based on the updated risk information.

[0048] Each of embodiments A, B, and C may have one or more of the following additional elements in any combination. Element 1 : further comprising auto-populating the risk information of at least one risk element in the risk assessment using a previously generated risk assessment for a previous trip including the same destination. Element 2: further comprising manually updating the risk information during the trip based on a new risk element encountered at the destination. Element 3: further comprising providing the manually updated risk information to the trip participants via an alert to the trip participant. Element 4: wherein generating the risk assessment includes generating the risk assessment including risk information from an existing risk assessment that was generated for a previous trip including the same destination. Element 5: further comprising providing reminders at predetermined intervals to the trip participants about the risks at the destination.

[0049] Element 6; wherein the instructions further cause the processor to: auto-populate the risk information of at least one risk element in the risk assessment using a previously generated risk assessment for a previous trip including the same destination Element 7: wherein the instructions further cause the processor to: manually update the risk information during the trip based on a new risk element encountered at the destination. Element 8: wherein the instructions further cause the processor to: provide the manually updated risk information to the trip participants via an alert to the trip participants. Element 9: wherein the instructions further cause the processor to: generate the risk assessment including risk information from an existing risk assessment that was generated for a previous trip including the same destination. Element 10: wherein the instructions further cause the processor to: provide reminders at predetermined intervals to the trip participants about the risks at the destination.

[0050] Element 1 1 : wherein executing the instructions further causes the at least one computing device to: auto-populate the risk information of at least one risk element in the risk assessment using a previously generated risk assessment for a previous trip including the same destination. Element 12: wherein executing the instructions further causes the at least one computing device to: receive manual updates to the risk information during the trip based on a new risk element encountered at the destination. Element 13: wherein executing the instructions further causes the at least one computing device to: provide the manually updated risk information to the trip participants via an alert to the trip participant. Element 14: wherein executing the instructions further causes the at least one computing device to: generate the risk assessment including risk information from an existing risk assessment that was generated for a previous trip including the same destination. Element 15: wherein executing the instructions further causes the at least one computing device to: provide reminders at predetermined intervals to the trip participants about the risks at the destination.

[0051] By way of non-limiting example, exemplary combinations applicable to embodiments A, B, and C include: Element 2 with Element 3; Element 7 with Element 8; and Element 12 with Element 13.

[0052] A reference to an element in the singular is not intended to mean one and only one unless specifically so stated, but rather one or more. For example,“a” module may refer to one or more modules. An element proceeded by“a,”“an,”“the,” or“said” does not without further constraints, preclude the existence of additional same elements.

[0053] Headings and subheadings, if any, are used for convenience only and do not limit the disclosure. The word exemplary is used to mean serving as an example or illustration. To the extent that the term include, have, or the like is used, such term is intended to be inclusive in a manner similar to the term comprise as comprise is interpreted when employed as a transitional word in a claim. Relational terms such as first and second and the like may be used to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between such entities or actions.

[0054] Phrases such as an aspect, the aspect, another aspect, some aspects, one or more aspects, an implementation, the implementation, another implementation, some implementations, one or more implementations, an embodiment, the embodiment, another embodiment, some embodiments, one or more embodiments, a configuration, the configuration, another

configuration, some configurations, one or more configurations, the subject technology, the disclosure, the present disclosure, other variations thereof and alike are for convenience and do not imply that a disclosure relating to such phrase(s) is essential to the subject technology or that such disclosure applies to all configurations of the subject technology. A disclosure relating to such phrase(s) may apply to ail configurations, or one or more configurations. A disclosure

5 relating to such phrase(s) may provide one or more examples. A phrase such as an aspect or some aspects may refer to one or more aspects and vice versa, and this applies similarly to other foregoing phrases.

[0055] As used herein, the phrase“at least one of’ preceding a series of items, with the terms “and” or“or” to separate any of the items, modifies the list as a whole, rather than each member of the list (i.e., each item). The phrase“at least one of’ does not require selection of at least one item, rather, the phrase allows a meaning that includes at least one of any one of the items, and/or at least one of any combination of the items, and/or at least one of each of the items. By way of example, the phrases“at least one of A, B, and C” or“at least one of A, B, or C” each refer to only A, only B, or only C; any combination of A, B, and C; and/or at least one of each of A, B, and C

[0056] To the extent that the term“include,”“have,” or the like is used in the description or the claims, such term is intended to be inclusive in a manner similar to the term“comprise” as “comprise” is interpreted when employed as a transitional word in a claim.

[0057] The word“exemplar} _' ” is used herein to mean“serving as an example, instance, or illustration.” Any embodiment described herein as“exemplary'” is not necessarily to be construed as preferred or advantageous over other embodiments. Phrases such as an aspect, the aspect, another aspect, some aspects, one or more aspects, an implementation, the

implementation, another implementation, some implementations, one or more implementations, an embodiment, the embodiment, another embodiment, some embodiments, one or more embodiments, a configuration, the configuration, another configuration, some configurations, one or more configurations, the subject technology, the disclosure, the present disclosure, other variations thereof and alike are for convenience and do not imply that a disclosure relating to such phrase(s) is essential to the subject technology or that such disclosure applies to ail configurations of the subject technology A disclosure relating to such phrase(s) may apply to all configurations, or one or more configurations. A disclosure relating to such phrase(s) may provide one or more examples. A phrase such as an aspect or some aspects may refer to one or more aspects and vice versa, and this applies similarly to other foregoing phrases.

[0058] A reference to an element in the singular is not intended to mean“one and only one” unless specifically stated, but rather“one or more.” The term“some” refers to one or more. Underlined and/or italicized headings and subheadings are used for convenience only, do not limit the subject technology, and are not referred to in connection with the interpretation of the description of the subject technology. Relational terms such as first and second and the like may be used to distinguish one entity or action from another without necessarily requiring or implying any actual such relationship or order between such entities or actions. All structural and functional equivalents to the elements of the various configurations described throughout this disclosure that are known or later come to be known to those of ordinary skill in the art are expressly incorporated herein by reference and intended to be encompassed by the subject technology. Moreover, nothing disclosed herein is intended to be dedicated to the public regardless of whether such disclosure is explicitly recited in the above description. No claim element is to be construed under the provisions of 35 U.S.C. §112, sixth paragraph, unless the element is expressly recited using the phrase“means for’ or, in the case of a method claim, the element is recited using the phrase“step for”.

[0059] While this specification contains many specifics, these should not be construed as limitations on the scope of what may be claimed, but rather as descriptions of particular implementations of the subject matter. Certain features that are described in this specification in the context of separate embodiments can also be implemented in combination in a single embodiment. Conversely, various features that are described in the context of a single embodiment can also be implemented in multiple embodiments separately or in any suitable subcombination. Moreover, although features may be described above as acting in certain combinations and even initially claimed as such, one or more features from a claimed combination can in some cases be excised from the combination, and the claimed combination may be directed to a subcombination or variation of a subcombination.

[0060] The subject mater of this specification has been described in terms of particular aspects, but other aspects can be implemented and are within the scope of the following claims. For example, while operations are depicted in the drawings in a particular order, this should not be understood as requiring that such operations be performed in the particular order shown or in sequential order, or that all illustrated operations be performed, to achieve desirable results. The actions recited in the claims can be performed in a different order and still achieve desirable results. As one example, the processes depicted in the accompanying figures do not necessarily require the particular order shown, or sequential order, to achieve desirable results. In certain circumstances, multitasking and parallel processing may be advantageous. Moreover, the separation of various system components in the aspects described above should not be understood as requiring such separation in all aspects, and it should be understood that the described program components and systems can generally be integrated together in a single software product or packaged into multiple software products.

[0061] The title, background, brief description of the drawings, abstract, and drawings are hereby incorporated into the disclosure and are provided as illustrative examples of the disclosure, not as restrictive descriptions. It is submitted with the understanding that they will not be used to limit the scope or meaning of the claims. In addition, in the detailed description, it can be seen that the description provides illustrative examples and the various features are grouped together in various implementations for the purpose of streamlining the disclosure. The method of disclosure is not to be interpreted as reflecting an intention that the claimed subject matter requires more features than are expressly recited in each claim. Rather, as the claims reflect, inventive subject matter lies in less than all features of a single disclosed configuration or operation. The claims are hereby incorporated into the detailed description, with each claim standing on its own as a separately claimed subject matter.

[0062] The claims are not intended to be limited to the aspects described herein, but are to be accorded the full scope consistent with the language claims and to encompass all legal equivalents. Notwithstanding, none of the claims are intended to embrace subject matter that fails to satisfy the requirements of the applicable patent law, nor should they be interpreted in such a way.