Systems and methods for generating incident-related reports

Abstract

A report generator is provided that produces informational reports during an identified event or incident. For example, for a given a declared event, such as a flood warning, relevant data is gathered, such as the event declaration, current and forecast weather, power outages and predictions, news and social media. This data is sent to the report generator for analysis, which is a large language model. A defined or selected area may be used so that the data is relevant to the selected area, which may also be subject to the identified event. Users are able to view the generated reports on a platform or have the reports sent via alerts as soon as they are created. The generation of summaries of discussions in a collaboration forum are also provided. Incident resource analysis techniques provide determinations of, for example, resource-at-risk needs for an event.

Description

SYSTEMS AND METHODS FOR GENERATING INCIDENT-RELATED REPORTSRELATED APPLICATION DATA

[0001] This application claims the benefit of priority of U.S. Provisional Patent Application Serial No. 63 / 563,052, filed March 8, 2024, and titled “Systems and Methods for Incident Management,” which is incorporated by reference herein in its entirety.FIELD OF THE DISCLOSURE

[0002] The present disclosure generally relates to the field of data processing. In particular, the present disclosure is directed to systems and methods for data processing for preparing reports, summaries, and action plans related to an event or incident.BACKGROUND

[0003] Organizations and other responders may need to be informed about, monitor and respond to ongoing incidents, in which case it can be important to make sure all the relevant information related to the situation is accurate and easily available. Current data processing systems tend to be cumbersome or slow in the context of preparing reports, summaries, and action plans for an ongoing event.SUMMARY OF THE DISCLOSURE

[0004] A computer-implemented method for generating a report related to an event includes receiving input from a user defining an area and an event context, the event context including event context terms, receiving data from a plurality of external sources and inputting data into an ETL process to generate current ETL data, comparing the area and event context to the current ETL data, repeating, if the area and event context to the current ETL data do not include a threshold amount of overlap, the receiving data and comparing after a selected time interval, sending, if the area and event context to the current ETL data include the threshold amount of overlap, a request to a report generator module, creating in the report generator module a report shell, wherein the report shell includes an identification associated with the user, the event context, a report date and time, and a plurality of fields, and sending a request from the report generator module to retrieve data from the plurality of external sources. The process further includes preparing a summary based on the data for each of the plurality of external sources by, creating a file for each of the plurality of external sources, associating each file with the report, creating a structured summary file for each file, uploading data from the plurality of external sources to the file associated with a respective one theplurality of external sources, comparing the uploaded data in each file marked as unsearched to the event context terms, adding the extracted data to the structured summary report if the uploaded data matches the event context terms and determining whether unsearched files remain, and if unsearched file remains performing the comparing the uploaded data to the event context terms for the next unsearched file. If the uploaded data does not match the event context terms, it is determined whether unsearched files remain, and if unsearched file remains performing the comparing the uploaded data to the event context terms for the next unsearched file. If no unsearched files remain, each completed summary file is combined to form the report and the report is sent to the user.

[0005] Additionally or alternatively, the method further includes receiving a request from the user after sending the report to the user for additional information, the request being associated with the report and including a plurality of inquiry data, extracting key words or phrases from the plurality of inquiry data, determining whether data received from any of the plurality of external sources matches the key words or phrases, retrieving information from each of the plurality of external sources that included matching key words or phrases, generating a response to the request based on the retrieved information, and sending the response to the user.

[0006] In another aspect, a situational awareness and incident management system includes a processor, including a report generator module and an automated extract, transform, load module in communication with the report generator module, configured to receive input identifying an event kind and a selected area, the event including event context information, receive by the report generator module a command to initiate a report by the automated extract, transform, load module based on the event context information accessed by the automated extract, transform, load module, create in the report generator module a report file associated with the identified event, wherein the report includes parameters for determining when to request information, what types of information to request, and a plurality of fields to be included in the report based on the identified event kind and selected area, and compare the event context information with the selected area to determine whether geospatial or contextual overlap exists. If overlap exists, the report generator module requests and receives data from a plurality of external data sources based on the report parameters. For information received from each of the plurality of external data sources, a plurality of summaries are generated and the plurality of summaries are combined to form a situation awareness summary for the identified event.

[0007] Additionally or alternatively, the plurality of summaries are generated by uploading data received from each of the plurality of external data sources to a plurality of respective files and referencing the plurality of files to search for relevant information based on the event and including the relevant information in a structured summary for each of the plurality of external data sources.

[0008] Additionally or alternatively, the command to initiate a report by the automated extract, transform, load module is received at predetermined time intervals or based on information processed by the automated extract, transform, load module.

[0009] Additionally or alternatively, the report generator module is further configured to receive a request from a user to initiate a report.

[0010] In another aspect, a method for generating discussion summaries includes receiving discussion data from a discussion in a collaboration application, wherein the discussion data includes discussion input from a plurality of contributors, wherein each of the plurality of contributors is associated with a role, storing the discussion data, wherein the discussion data is stored such that the discussion data is associated with a time and date interval, with a contributor from the plurality of contributors, and with a context, the context including an identification of participants from a plurality of participants participating during the time and date interval, retrieving a portion of the discussion data based on a selection of a time and date parameter, a role parameter, a participant parameter, and a contributor parameter, and generating a summary of the retrieved portion of the discussion data based on the role parameter, the participant parameter, and the contributor parameter.

[0011] Additionally or alternatively, the summary is based on the selection of the time and date parameter, the role parameter, and / or the contributor parameter.

[0012] In another aspect, a computer-implemented method for generating summaries of discussions in a collaboration forum includes retrieving discussion data from the discussion forum, the discussion data including content of a discussion, a discussion time and date interval, a list of a plurality of participants that participated in a discussion during the discussion time and date interval, wherein each of the plurality of participants is associated with a role, a list of one or more contributors, wherein each of the one or more contributors is associated with at least some of the content as contributing the at least some of the content and is one of the plurality of participants, and a list of one or more recipients, and wherein each of the one or more recipients is associated with at least some of the content as receiving the at least some of the content and is one of the plurality ofparticipants, saving the discussion data in a temporary file, determining whether a session or time period has ended, and if a session or time period has ended, creating a discussion log file containing the discussion data and associating the discussion log file with the session or time period, and if the session or time period has not ended, continuing saving the discussion data in the temporary file, extracting each entry of a plurality of discussion entries from the discussion data and associating each entry of the plurality of discussion entries with a contributor that contributed the entry from the list of one or more contributors and a role of the contributor, and associating each entry of the plurality of discussion entries with one or more recipients from the list of one or more recipients that received the entry and a role of each of the one or more such recipients, receiving from a user a request for a summary of a discussion, the request including a time and date interval, a role parameter, a participant parameter, a contributor parameter, and a key term, creating a structured summary file for the request, and accessing each of a plurality of discussion log files, including the discussion log file, and determining whether each discussion log file includes entries within the time and date interval. For each discussion log file with entries within the time and date interval, determining whether each discussion log file the role parameter, the participant parameter, the contributor parameter, and the key term. For each discussion log file including the role parameter, the participant parameter, the contributor parameter, and the key term, extracting information from each such discussion log file and adding the information to an associated field in the structured summary file. A structured summary from the structured summary file is sent to the user.

[0013] Additionally or alternatively, the process further includes determining whether an operational period requires a discussion summary, and if so determining whether the operational period has ended, wherein if the operational period is ended, generating a discussion summary for the operational period by, preparing an operational period summary request including a time and date interval, a role parameter, a participant parameter, a contributor parameter, and a key term, creating an operational period structured summary file for the operational period summary request, accessing each of a plurality of discussion log files, including the discussion log file, and determining whether each discussion log file includes entries within the time and date interval. For each discussion log file with entries within the time and date interval, determining whether each discussion log file the role parameter, the participant parameter, the contributor parameter, and the key term. For each discussion log file including the role parameter, the participant parameter, the contributor parameter, and the key term, extracting information from each such discussion log file and adding the information to an associated field in the operational period structured summary file.

[0014] In another aspect, a method for automatically preparing an incident action plan for an incident includes retrieving, on an incident action plan module, incident context information, including a current situation summary, a user-defined declaration of an incident type, a time and location, and situation condition data, accessing pre-existing plans, manuals, or regulatory documents associated with the incident type at the incident action plan module, comparing the accessed pre-existing plans, manuals, or regulatory documents to the incident context information; and determining a set of response information for the incident, including objectives, actions, and resources, based on the comparing.BRIEF DESCRIPTION OF THE DRAWINGS

[0015] For the purpose of illustrating the disclosure, the drawings show aspects of one or more embodiments of the disclosure. However, it should be understood that the present disclosure is not limited to the precise arrangements and instrumentalities shown in the drawings, wherein:FIG. l is a diagram of an overview of components and processes of a report generator in accordance with an embodiment of the present disclosure;FIG. 2 is a process diagram providing an overview of a process for generating reports by the report generator;FIG. 3 is a process diagram providing an overview of a process for extracting and compiling data for the reports;FIG. 4 is a diagram of an overview of a process for preparing an updated summary for an ongoing event in accordance with an embodiment of the present disclosure;FIG. 5 is a diagram of an overview of components and processes for a role-based summary generator in accordance with an embodiment of the present disclosure;FIG. 6 is a process diagram providing an overview of data extraction and file creation for the rolebased summaries;FIG. 7 is a process diagram providing an overview of creating the role-based summaries; andFIG. 8 is a diagram of an overview of components and processes of an incident resource analysis system in accordance with an embodiment of the present disclosure.DETAILED DESCRIPTION

[0016] A report generator, a role-based summary generator, and incident resource analysis module are disclosed that improve data processing and management in various situations, including emergent situations.Report Generator

[0017] A report generator is provided that produces informational reports during an identified event or incident. For example, for a given declared event, such as a flood warning, relevant data is gathered from various sources, such as the event declaration, current and forecast weather, power outages and predictions, news, and social media. This data is sent for analysis to the report generator, which is a large language model. Alternatively or additionally, the data may be based on a defined or selected area so that the data is relevant to the selected area (which may also be subject to the identified event). Users are able to view reports on a platform or have the reports sent via alerts as soon as they are created.

[0018] As outlined in FIG. 1, the report generator receives input pertinent to an identified event and / or a selected area (the event context and area is user-defined, in the case of the area either by drawing a polygon on a map, selecting a point with applicable radius, or uploading a geospatial reference file), which serves as a basis for determining when and / or what data / information to retrieve and include in reports, as well as the format and content included in the report. A report is initiated from an automated extract, transform, load (ETL) module or by a user (for a spot report). Once a request for a report is received, the report generator accesses external data sources to retrieve data relevant to the requested report and delivers or displays the report to selected users. The external data sources may be a set of default sources and or end-user-defined by inputting endpoints and appropriate authentication and query arguments.

[0019] The reports generator compares the defined event context with the area to determine whether there is geospatial or contextual overlap. If so, then a data retrieval step is performed by requesting data from predefined external data sources, e.g., through application programming interfaces, then the reports generator creates summaries for each of the data sources, then combines the summaries together into a single report for situation awareness.

[0020] The summaries are created by uploading each data source as a file to the system, then having the system reference those files to search for relevant information and turn that informationinto a structured summary for each data source. The data sources can also be directly inserted into the system’s input context window, rather than by using retrieval to read files, as an alternative way of providing the same data to the system, in the case of errors or other issues with uploading or reading file.

[0021] Users can also prompt the creation of a spot report for an event or area outside of the automated ETL cycle by manually triggering a report generation through the selection of an event or area to be reported on. Furthermore, users can request additional clarifications by sending a message back to the large language model, which looks up data sources based on the user’s subsequent query, then creates additional summarizations to inform the user based on the query. For example, a subsequent request with the message of “Have any fatalities been reported?” would result in the model determining data sources to check, such as news and social media sources, fetching the relevant data set, and then preparing an answer to the query with data from each data set.

[0022] An overview of a process for generating reports is provided in FIG. 2, in which a user defines and area and an event context for which the user wants to receive reports. These inputs are used as the basis for a standing report inquiry for that user. For each such report inquiry, the defined area and event context are feed into an ETL and it is determined whether the event context and / or area definition overlap with any current data being processed through the ETL. If not, the process repeats at given intervals for each standing report inquiry, which may be modified by the user. If the event context and / or area definition overlap with any current data being processed through the ETL, a report request is sent to the report generator, where a report shell or template is formed and associated with the event context from which the request originated. The report generator then retrieves data from external sources and prepares summaries based on the data received and processed for each data source (described in more detail below). These summaries, which are each associated with the requested report, are then combined into a single report that is also associated with the requested report, and the combined report is sent to the user / user interface that had defined the area and event context that led to the creation of the report.

[0023] In addition to the report generation above, which are based on determining whether a report should be generated based on the area and event context as well as current ETL data, a user may request a spot report from the report generator directly by sending a request for a spot report. This initiates the creation of a spot report in the report generator that is associated with the spot report request, and a spot report is created as described above and sent to the requesting user.

[0024] Further, for any report received by a user, a request for additional information or clarification may be sent from the user to the report generator, which then generates answers / responses for the request. As outlined in FIG. 4, upon receipt of a report, a user may send a request, which is linked to the report of interest via a report identifier for example, to the report generator that includes an inquiry for more information or clarification. The report generator extracts key words or phrases from the request and determines which data sources include data with matches or pertinent matches to the extracted key words or phrases and retrieves information from the matched data sources. A response or answer is then generated for the request based on the information from the matched data sources, and the response is tagged with the report identifier and sent to the requesting user.

[0025] In FIG. 3, an overview of the process for preparing reports is provided in which, upon receipt of a request for a report as described above, data is received from external sources from which relevant information might be gleaned and files are created from each data source and associated with the requested report. A structured summary file for the report is created. Data from each relevant source is uploaded to the corresponding files, and then information in each file is compared to the event context terms (and / or area) defined by the user and associated with the requested report. It is then determined whether the information is a match (e.g., related to or relevant to) for the event context terms. If so, the extracted information is added to the structured summary file for the report. If not, it is determined whether unsearched files remain to be assessed. If yes, the comparing and extracting process continues; if not, the report is compiled.

[0026] When extracted information is added to the structured summary file for the report, it is determined whether unsearched files remain to be assessed. If yes, the comparing and extracting process continues; if not, the report is compiled. Compiling the report includes combining structured summaries generated for each data source used into a single report, which is associated with the report identifier and sent to the appropriate user(s), which is determined by the association between the user (or user account or user’s organization’s account) and the defined event context / area.Role-Based Summaries

[0027] Turning to FIG. 5, a role-based brief generator is provided that allows discussions among users in a collaboration application or similar to be captured and summarized. The system allows users to have channels to converse based on their roles, rather than the individual user. Thisensures conversations are relevant to the topics at hand and easily searchable for context, which is especially useful during shift changes, when the new shift has to be briefed on the prior shift’s tasks and the upcoming shift’s priorities.

[0028] The role-based brief generator accesses prior shifts’ discussions and generates summaries. In this way, less time - or no time - is required to be spent reaching out to individuals for situation awareness about the prior operational period(s). Instead, with all the information already in the system, the role-based brief generator can provide up-to-date information automatically. As shown in FIG. 5, discussions occurring between any number of users is stored, and all content is associated with the role of the user that created the content (as well as, optionally, the role or roles of the recipients of that content). The role based brief generator retrieves that data and generates summaries based on the content of the discussions as well as the roles of the producers and recipients of the content. On a regular cadence, such as before or after operational periods, or upon a request from a user, any communications from any set of roles can be selected and retrieved for summary. Once the data has been gathered, it is uploaded to the system, which creates a summary of the conversation(s) with the most relevant information prominently noted.

[0029] The generation of summaries is performed by converting the discussion logs into a file, uploading the file into the system, then prompting a summary module to create a summary, with user-defined settings to emphasize action items for a particular role or roles if desired. The system then references these files to search for relevant information and turn into a structured summary. The discussion logs can also be directly inserted into the system’s input context window, rather than by using retrieval to read files, as an alternative way of providing the same data to the system, in the case of errors or other issues with uploading or reading files.

[0030] In FIG. 6, an overview of an exemplary process for creating files of discussion logs. Data from the discussion forum is retrieved periodically and saved in a discussion forum log database. It is determined whether a new session, operational period, or designated time interval has started or ended. If not, the retrieval and saving process is continued; if so, the retrieval and saving process is also continued but a file is created for discussion log data and the file is associated with the given session, operational period, or time interval (or combinations thereof). Each participant in the discussion for that session is identified and included in the file for that session, and the role associated for each such participant is also included in the file, wherein the role is the role the participant had during the forum discussion (and so included in and determined from the discussionforum data since participant roles may change or participants may have more than one role). Each discussion entry is then associated with the role of the contributing participant as well as the receiving participant. Each role for each discussion entry is assigned a status for that entry as a contributor or recipient. The discussion log file is then saved with entry content, and the associated information regarding roles and participants.

[0031] In FIG. 7, a process diagram is shown for an exemplary role-based summary generation. A request is received from a user for a role-based summary and from the request, the role-based summary generator extracts the requested time period(s) as well as roles, action items, content, as applicable, to be used in generating the summary. Each role is specified in terms of the described permissions, position description, and the reports / reporting above and below and of those positions’ descriptions. That determines in part the information that the user is expected to know. Additionally, any tasks assigned to the role are taken into account for the context. All such information is stored in structured data, for example roles, tasks, logs. That data is referenced via relational database tables. Discussion logs may also be checked for the presence of mentions to locate any potentially relevant information for reports.

[0032] The forum discussion log files (created as described above in connection with FIG. 6) are accessed and searched to determine whether each file (or a subset of files narrowed based on one or more of the request criteria) contains relevant information. For example, it may be determined whether the file includes logs or discussion entries from the relevant times, whether one or more contributor roles are included in the discussion that were identified in the request, whether one or more recipient roles are included in the discussion that were identified in the request, and whether relevant content or action items are included in the discussion that were identified in the request. It will be noted that the searching may be for one, some, or any combination of these parameters depending on the request.

[0033] When relevant data is found in any such file, it is added to a structured summary file in an appropriate field. Additionally or alternatively, structured summaries may be defined by the large language model prompts, which specify the required structure of the summaries. This process continues until all the files or subset of files are accessed and search, at which point the completed structured summary file and / or a summary based on the structured summary file is sent to the requestor and any other users identified as requiring the summary. In this way, summaries are generated based not just on time, content, and contributor, but also on the roles associated with eachcontributor and recipient in the discussion. As noted, this may allow users starting a new shift to obtain summaries related to the role they are in for that shift.Incident Resource Analysis

[0034] Additionally, an incident resource analysis module is provided that includes functions for assessing deterministic outputs, such as calculating resource-at-risk needs for environmental protection in the case of an offshore oil spill. This allows operators to receive an accurate picture of their resource and action needs quickly, ensuring a timely and well-calibrated response.

[0035] As shown in FIG. 8, the incident analysis module receives information relating to the incident context as well as pre-existing plans, manuals, and regulatory documents. Resource analysis functions are based on the incident context as well as pre-existing plans, manuals, and regulatory documents, and these functions are also incorporated into the incident analysis module, which then performs calculations and analysis based on these inputs and generates plan summaries and structured data for the given incident.

[0036] The creation of an incident action plan begins by retrieving incident context information, including data such as the current situation summary, user-defined declaration of the incident type (such as “Earthquake” or “Oil Spill”), time and location, and data of other conditions regularly fetched and uploaded into the platform, such as weather and power outage information. Once the context data has been gathered, the system checks for user-uploaded files representing pre-existing plans, manuals, and regulatory documents (collectively referred to as “SOPs”), to see if any such files have been uploaded, and if they have relevance to the current situation. If not, the user is prompted to upload file(s) regarding SOP. Then, the system references those files, compares them to the incident context information, and determines a set of mission essential information (MEI) such as objectives, actions, or resources, which are suggested to the user.

[0037] Various modifications and additions can be made without departing from the spirit and scope of this disclosure. Features of each of the various embodiments described above may be combined with features of other described embodiments as appropriate in order to provide a multiplicity of feature combinations in associated new embodiments. Furthermore, while the foregoing describes a number of separate embodiments, what has been described herein is merely illustrative of the application of the principles of the present disclosure. Additionally, although particular methods herein may be illustrated and / or described as being performed in a specific order,the ordering is highly variable within ordinary skill to achieve aspects of the present disclosure. Accordingly, this description is meant to be taken only by way of example, and not to otherwise limit the scope of this disclosure.

[0038] Exemplary embodiments have been disclosed above and illustrated in the accompanying drawings. It will be understood by those skilled in the art that various changes, omissions and additions may be made to that which is specifically disclosed herein without departing from the spirit and scope of the present disclosure.

Claims

What is claimed is:1 . A computer-implemented method for generating a report related to an event, the method comprising: receiving input from a user defining an area and an event context, the event context including event context terms; receiving data from a plurality of external sources and inputting data into an ETL process to generate current ETL data; comparing the area and event context to the current ETL data; repeating, if the area and event context to the current ETL data do not include a threshold amount of overlap, the receiving data and comparing after a selected time interval; sending, if the area and event context to the current ETL data include the threshold amount of overlap, a request to a report generator module; creating in the report generator module a report shell, wherein the report shell includes an identification associated with the user, the event context, a report date and time, and a plurality of fields; sending a request from the report generator module to retrieve data from the plurality of external sources; preparing a summary based on the data for each of the plurality of external sources by: creating a file for each of the plurality of external sources; associating each file with the report; creating a structured summary file for each file; uploading data from the plurality of external sources to the file associated with a respective one the plurality of external sources; comparing the uploaded data in each file marked as unsearched to the event context terms; adding the extracted data to the structured summary report if the uploaded data matches the event context terms and determining whether unsearched files remain, and if unsearched file remains performing the comparing the uploaded data to the event context terms for the next unsearched file;if the uploaded data does not match the event context terms, determining whether unsearched files remain, and if unsearched file remains performing the comparing the uploaded data to the event context terms for the next unsearched file; if no unsearched files remain, combining each completed summary file to form the report; and sending the report to the user .

2. The method of claim 1, further including: receiving a request from the user after sending the report to the user for additional information, the request being associated with the report and including a plurality of inquiry data; extracting key words or phrases from the plurality of inquiry data; determining whether data received from any of the plurality of external sources matches the key words or phrases; retrieving information from each of the plurality of external sources that included matching key words or phrases; generating a response to the request based on the retrieved information; and sending the response to the user.

3. A situational awareness and incident management system comprising: a processor, including a report generator module and an automated extract, transform, load module in communication with the report generator module, configured to: receive input identifying an event kind and a selected area, the event including event context information; receive by the report generator module a command to initiate a report by the automated extract, transform, load module based on the event context information accessed by the automated extract, transform, load module; create in the report generator module a report file associated with the identified event, wherein the report includes parameters for determining when to request information, what types of information to request, and a plurality of fields to be included in the report based on the identified event kind and selected area;compare the event context information with the selected area to determine whether geospatial or contextual overlap exists; if overlap exists, request and receive, by the report generator module, data from a plurality of external data sources based on the report parameters; generate, for information received from each of the plurality of external data sources, a plurality of summaries; and combine the plurality of summaries to form a situation awareness summary for the identified event.

4. The system of claim 3, wherein the plurality of summaries are generated by uploading data received from each of the plurality of external data sources to a plurality of respective files and referencing the plurality of files to search for relevant information based on the event and including the relevant information in a structured summary for each of the plurality of external data sources.

5. The system of claim 3, wherein the command to initiate a report by the automated extract, transform, load module is received at predetermined time intervals or based on information processed by the automated extract, transform, load module.

6. The system of claim 5, wherein the report generator module is further configured to receive a request from a user to initiate a report.

7. A method for generating discussion summaries comprising: receiving discussion data from a discussion in a collaboration application, wherein the discussion data includes discussion input from a plurality of contributors, wherein each of the plurality of contributors is associated with a role; storing the discussion data, wherein the discussion data is stored such that the discussion data is associated with a time and date interval, with a contributor from the plurality of contributors, and with a context, the context including an identification of participants from a plurality of participants participating during the time and date interval; retrieving a portion of the discussion data based on a selection of a time and date parameter, a role parameter, a participant parameter, and a contributor parameter; and generating a summary of the retrieved portion of the discussion data based on the role parameter, the participant parameter, and the contributor parameter.

8. The method of claim 7, wherein the summary is based on the selection of the time and date parameter, the role parameter, and / or the contributor parameter.

9. A computer-implemented method for generating summaries of discussions in a collaboration forum comprising: retrieving discussion data from the discussion forum, the discussion data including content of a discussion, a discussion time and date interval, a list of a plurality of participants that participated in a discussion during the discussion time and date interval, wherein each of the plurality of participants is associated with a role, a list of one or more contributors, wherein each of the one or more contributors is associated with at least some of the content as contributing the at least some of the content and is one of the plurality of participants, and a list of one or more recipients, wherein each of the one or more recipients is associated with at least some of the content as receiving the at least some of the content and is one of the plurality of participants; saving the discussion data in a temporary file; determining whether a session or time period has ended, and if a session or time period has ended, creating a discussion log file containing the discussion data and associating the discussion log file with the session or time period, and if the session or time period has not ended, continuing saving the discussion data in the temporary file; extracting each entry of a plurality of discussion entries from the discussion data and associating each entry of the plurality of discussion entries with a contributor that contributed the entry from the list of one or more contributors and a role of the contributor, and associating each entry of the plurality of discussion entries with one or more recipients from the list of one or more recipients that received the entry and a role of each of the one or more such recipients; receiving from a user a request for a summary of a discussion, the request including a time and date interval, a role parameter, a participant parameter, a contributor parameter, and a key term; creating a structured summary file for the request; accessing each of a plurality of discussion log files, including the discussion log file, and determining whether each discussion log file includes entries within the time and date interval;for each discussion log file with entries within the time and date interval, determining whether each discussion log file the role parameter, the participant parameter, the contributor parameter, and the key term; for each discussion log file including the role parameter, the participant parameter, the contributor parameter, and the key term, extracting information from each such discussion log file and adding the information to an associated field in the structured summary file; and sending a structured summary from the structured summary file to the user.

10. The method of claim 9, further including: determining whether an operational period requires a discussion summary, and if so determining whether the operational period has ended, wherein if the operational period is ended, generating a discussion summary for the operational period by: preparing an operational period summary request including a time and date interval, a role parameter, a participant parameter, a contributor parameter, and a key term; creating an operational period structured summary file for the operational period summary request; accessing each of a plurality of discussion log files, including the discussion log file, and determining whether each discussion log file includes entries within the time and date interval; for each discussion log file with entries within the time and date interval, determining whether each discussion log file the role parameter, the participant parameter, the contributor parameter, and the key term; and for each discussion log file including the role parameter, the participant parameter, the contributor parameter, and the key term, extracting information from each such discussion log file and adding the information to an associated field in the operational period structured summary file.

11. A method for automatically preparing an incident action plan for an incident, comprising: retrieving, on an incident action plan module, incident context information, including a current situation summary, a user-defined declaration of an incident type, a time and location, and situation condition data;accessing pre-existing plans, manuals, or regulatory documents associated with the incident type at the incident action plan module; comparing the accessed pre-existing plans, manuals, or regulatory documents to the incident context information; and determining a set of response information for the incident, including objectives, actions, and resources, based on the comparing.

Images