I3MS_User_Stories_Investigation_1.docx

Incident & Investigation Information Management System Modernization (I3MS) Investigation User Stories

Investigation Requirements (Internal View)

As a BSEE Investigator/Reviewer I want to search for incident or oil spill follow-up information reports so that I can select a report to view, enter, and/or update investigation data for the report.

Acceptance Criteria:

· Note: This is the internal view of the application for a BSEE Investigator/Reviewer to view, add, and edit investigation data for a selected incident report or selected oil spill follow-up information report, separate from that of the review process.

· For incident reports, by default, display the reports for which the Reviewer/Investigator has been assigned a Review or that need BSEE’s review first, including those with the following statuses: Submitted, In Review, Resubmitted, and Withdrawal Pending. Also, by default, display all reports from the last 90 days, based on the Date of Incident; however, the Reviewer can expand the date criteria incrementally, up to and including all reports. Reports should be easily filtered by District (including multiselect and ‘All Districts’), Region (including multiselect and ‘All Regions’), Facility Type (including multiselect and ‘All Facility Types’), and Status (including multiselect and ‘All Statuses’); Date Range; and distinguishable by Report Type (Oil & Gas Incident Report, Renewable Energy Incident Report, Oil Spill Follow-Up Information Report) (including multiselect and ‘All Report Types’). See below for metadata fields to display.

· For oil spill follow-up information reports, by default, display the reports that the BSEE Investigator/Reviewer has been assigned or that need their attention first.

· Also display options from which the BSEE Investigator/Reviewer can search, filter, and sort reports. Note that the specified meta data fields will be displayed for each appropriate Report Type, as well as additional fields provided by the Product Owner and/or SMEs.

· For an Oil & Gas Incident Report, include Company, Contractor(s), Incident Date (MM/DD/YYYY), Incident Time, Surface Area, Surface Block, Surface Lease, District, Region, Facility Type (Platform, Rig, Pipeline, Platform/Rig, Platform/Pipeline), Platform Name, Rig Name, API Number, General Activity(ies), Operation(s), Incident Type(s), Tier, District Investigation Report, Panel Investigation Report, Status, Status Date, and Follow-Up Due Date.

· For an Oil Spill Follow-up Information Report, include the same meta data fields used for an Oil & Gas Incident Report.

· For a Renewable Energy Incident Report, include Company, Contractor(s), Incident Date (MM/DD/YYYY), Incident Time, Surface Area, Surface Block, Lease, Renewable Project Name, District, Region, Facility Type (Facility, Vessel, Cable, Facility/Vessel, Facility/Cable, Vessel/Cable), Facility Name, Vessel Name, Vessel Number, REN Work Process, REN Incident Area, Status, Status Date, and Follow-Up Due Date.

· The Follow-Up Due Date should be color-coded based on the length of time since the Incident Date: Black if today’s date is 0-10 days after the Incident Date, Orange if today’s date is 11-15 days after the Incident Date, and Red if today’s date is 15+ days after the Incident Date.

· From the default and/or filtered search results, the BSEE Reviewer or Investigator can select a report and they will be brought to the respective incident report.

· From this dashboard, the BSEE Reviewer or Investigator can also select to view a PDF of the incident report in its current status. Note: The content of the data to include in the PDF report will be provided by the Product Owner and/or SMEs.

As a BSEE Investigator/Reviewer I want to easily navigate between the external view of an incident report and the internal view of the investigation part of the incident report so that I can view and edit information about my investigation in a straightforward and seamless manner.

Acceptance Criteria:

· From within the internal review of the incident report, the BSEE Investigator/Reviewer can directly navigate to the Investigation functions of the incident record where they can enter information about their investigation once the incident report is submitted. These functions should not be visible to the Lessee or Operator representative.

· From within the investigation view of the incident report, the BSEE Investigator/Reviewer can directly navigate to the review process of the incident report where they can view and conduct a review of the incident report once it is submitted. These functions should not be visible to the Lessee or Operator representative.

· If applicable, the BSEE Investigator/Reviewer can navigate to an associated oil spill follow-up information report from the internal incident report or investigation view.

· The BSEE Investigator will be able to view, enter, and edit investigation data once the incident report is created, and continuing after the report is accepted by the BSEE Reviewer.

As a BSEE Investigator I want to view header data for an incident or oil spill follow-up that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can easily reference the data as I provide other information for the incident or oil spill follow-up as part of my investigation.

Acceptance Criteria:

· Display the following header data based on the Report Type of the selected record. These data will be noneditable.

· For an Oil & Gas Incident Report: Operator Name/Number; Region; District; Report Type; record ID; current Status; Date of Incident; Time of Incident; Surface Area Code; Surface Block Number; Surface Lease; Platform Name; Rig Name; Pipeline Segment Number; Incident Type(s), listing all types selected by the Oil & Gas Operator representative, including Evacuation/Injury/Fatality and Other Incident Types; and Follow Up Due Date.

· For Follow Up Due Date, highlight the date in red if the date is more than 15 days from the Date of Incident.

· For a Renewable Energy Incident Report: Lessee, Operator, Contractor Name(s)/Number(s); Region; District; Report Type; record ID; current Status; Date of Incident; Time of Incident; Renewable Project Name; Surface Area Code; Surface Block Number; Surface Lease; Facility ID; Cable Name; Incident Type(s), listing all types selected by the Renewable Energy representative; REN Incident Area; REN Work Process; Vessel Identification; and Follow Up Due Date.

· For Follow Up Due Date, highlight it in red if the date is more than 15 days from the Date of Incident.

· For an Oil Spill Follow-up Information Report: Operator Name/Number, Region, District, Report Type, record ID, current Status, Date of Incident, Time of Incident, Surface Area Code, Surface Block Number, Surface Lease, Platform Name, Rig Name, Pipeline Segment Number, Type of Oil or Other Pollutant, and Volume Determined by BSEE.

As a BSEE Investigator I want to view and enter specific data for an incident that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can review and update the incident data based on my investigation’s findings.

Acceptance Criteria:

· Display a view of the selected incident report which shows the data entered by the Lessee or Operator representative or Internal User (Agent For).

· Note: The BSEE Investigator will not be able to edit the incident report’s data.

· For the data fields of the selected incident report, display options that allow the BSEE Investigator to provide updated information in each field of the report, based on BSEE’s findings during the investigation.

· Each of these fields for investigation will be saved in the appropriate tables of the database as a separate field and prefixed with “BSEE” to distinguish it from the field entered by the Lessee or Operator representative or Internal User (Agent For).

· If the selected report is an Oil & Gas Incident Report, for the Pipeline information also display the departing/crossover/receiving and the platforms that are using that pipeline based on the Pipeline Segment Number that is entered (by the Lessee or Operator representative or Internal User (Agent For)) and information from BSEE’s TIMS table(s).

As a BSEE Investigator/Reviewer I want to associate an incident or oil spill follow-up information report with other incident or oil spill follow-up information reports or other BSEE records and view specified information from the associated report or record so that I can gather the information from various sources I need for my investigation.

Acceptance Criteria:

· The BSEE Investigator/Reviewer can search for and associate incident and/or oil spill follow-up information reports using the following metadata fields: Incident Date, Incident Time, Surface Area Block, Surface Lease, ID, and anything other fields provided by the Product Owner and/or SMEs.

· Reports can be associated with any status.

· The BSEE Investigator/Reviewer can have the option to assign one report to be a Master (parent/primary) report. Display a Master Report value list option with Yes/No values that allows the BSEE Investigator/Reviewer to indicate whether the incident report is the master report.

· The BSEE Investigator/Reviewer can view data from other reports and select to view the associated incident report(s).

· The BSEE Investigator/Reviewer can search for and associate an incident or oil spill follow-up information report with other BSEE records, such as Inspections, Civil Penalties, Pipeline Damage Reports, OSPD Plans, etc.

· The BSEE Investigator/Reviewer can view information associated with those BSEE records, as determined by the Product Owner and/or SMEs.

· Incident and oil spill follow-up reports can be associated with more than one incident or oil spill follow-up information report, or other BSEE record(s).

As a BSEE Investigator I want to input investigation details for an incident that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can provide general information about the incident’s investigation.

Acceptance Criteria:

· Allow the BSEE Investigator to view and update fields in the Investigation once the status of the incident report is Submitted.

· Display options that allow the BSEE Investigator to input the following Investigation Details data.

· Display the BSEE Jurisdiction Flag field as a value list with Yes/No values and Yes as default.

· Display the Investigation Lead Agency field as a value list with values BSEE, USCG, BSEE & USCG, DOT, EPA, NOAA, State, and Other; the default value is BSEE.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Display Incident Category as a value list with Required Incident Report and Other Report.

· The default value is Required Incident Report.

· If the “Other Report” value is selected, display an input field below the value list to provide details.

· Display the Tier Code and Tier Subcategories fields as follows.

· Display Tier Code as a value list with 1, 2, 3, and 4 as values, along with each value’s description in parentheses. The description of each value is as follows.

· 1: BSEE uses minimal resources to verify that all operator reported information is accurate and sufficient to explain the circumstances that resulted in the incident.

· 2: Investigations require efforts beyond those required for Tier One investigations, such as follow up interviews, planned/dedicated trips to offshore facilities, or any additional in-depth efforts.

· 3: Investigations require the completion of a District 2010 Report.

· 4: Investigations require formation of a Panel as determined by specific guidance for Panel investigations.

· For the selected Tier Code, the Investigator will select one or more appropriate Tier Subcategories from a multi-selectable value list with A, B, C, D, E, F, G, H, I, J, K, L, M, N, O, P, Q, and R as values, with the following description.

· A - Fatalities

· B - Injuries that require evacuation

· C - Loss of well control

· D - Fire/Explosion

· E - H2S release

· F - Collision: Damage > $25,000

· G - Structural Damage

· H - Crane or personnel/material handling

· I - Damaged or disabled safety system

· J - Injury: Lost Time Accident

· K - Gas Release

· L - Muster

· M - Other damage > $25,000

· N - Arctic

· O - US Coast Guard

· P - Pollution/Sheen

· Q - Other investigation

· R - Turned over to another agency

· Display the “Is the Incident Occupational?” field as a value list with values Yes/No and Yes as default.

· Display the “Initiate a District Investigation Report (2010)?” field as a value list with Yes/No values.

· The system should notify certain personnel in the Regional or Headquarters offices when this field is selected as Yes. Notification recipients and content of the notification email will be provided by the Product Owner and/or SMEs.

· Display Incident Panel Investigation Formed as a value list with Yes/No as values.

· The system should notify certain personnel in the Regional or Headquarters offices when this field is selected as Yes. Notification recipients and content of the notification email will be provided by the Product Owner and/or SMEs.

· Display Investigation Determination Remarks as an input field.

· Display the Offshore Incident Report field as a value list with Yes/No values.

· Note: This field replaces the Emergency Report field in TIMS Events. It will be just an indicator and will not automatically generate a report.

· Display the “Was Operator Told to Contact Pipeline Section?” field as a value list with Yes/No values.

· Display the Vessel Type and Vessel Name and its accompanying IMO/Registration Number and Vessel Company entry(ies) that the Operator representative provided, if available, for view only.

· Display the following BSEE Vessel information in a table option that allows the Investigator to input additional vessel information if needed.

· Display Vessel Type as a value list with Survey Vessel, Installation Vessel, Crew Transfer Vessel, Offshore Supply Vessel, Cable Lay Vessel, Scour Protection Vessel, Service Operations Vessel, Barge, Diving Support, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Display Vessel as a value list with each value containing a Vessel Name and its accompanying IMO/Registration Number and Vessel Company. Also display an Add icon/option next to the Vessel value list to allow the Investigator to add a new Vessel (including Vessel Name, IMO/Registration Number, Vessel Company) to the value list, if needed.

· Note: The Investigator selects a Vessel Type involved in the incident and then chooses a Vessel related to the selected Vessel Type. One or more Vessel Type entries can be provided.

· Note: The Final Accepted by (Incident Report Approved By), Date, and Time fields in BSEE’s TIMS Events application will be replaced in the new application with the appropriate Created by and Status Date and Time fields, respectively, when the incident record is accepted.

· Display the BSEE Remarks large input field.

· Display the selected value of the Operation Type field provided by the Operator representative as a noneditable field. If “Other” Operation Type is selected, also display its details provided by the Operator representative as a noneditable field.

· Display the Activity at Incident Time Description as a large input field.

· Display the following fields in a separate category named “Initial Notification.”

· Immediate Report Required? field and Immediate Report Received? field as value lists with Yes/No values.

· Manner Initial Notification Received from Operator as a value list with Telephone, I3MS Incident Report, Email, In Person (Onshore), In Person (Offshore), Mail, Text Message, and Fax as values.

· Date Initial Notification Received from Operator as an input field with a calendar and editable in the MM/DD/YYYY format.

· Time Initial Notification Received from Operator as an input field in the 00:00-23:59 format.

· “Initial Notification Received From” as a value list whose First Name & Last Name values are drawn from the contact(s) for the Operator who submitted the incident record.

· “Initial Notification Received By” as a value list whose First Name & Last Name values are drawn from BSEE employees.

· Note: If the “I3MS Incident Report” value is selected from the Manner Initial Notification Received from Operator value list, the Date Initial Notification Received from Operator, Time Initial Notification Received from Operator, Initial Notification Received From, and Initial Notification Received By will be auto populated with the respective incident report fields.

· Initial Notification Remarks as a large input field.

· “Written Report Required?” field as a value list with Yes/No values.

· Any needed validations will be provided by the Product Owner, and user-friendly error messages will be provided for the fields that need validation.

As a BSEE Investigator I want to input data on Loss of Well Control (LWC) or an incident that an Oil & Gas Operator representative or Internal User (Agent For) submitted so that I can attach additional LWC information pertinent to my investigation.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to input the following LWC data.

· Display the API Number, Well Name, Lease Number, and Operation input fields. These fields will be auto populated with the respective data that the Oil & Gas Operator representative or Internal User (Agent For) provided and editable as BSEE fields.

· Display the Simultaneous Operations in Progress? field as a value list option with Yes/No values.

· Display the Evacuation field as a value list option with Yes/No values.

· Display the Sustained Casing Pressure? field as a value list option with Yes, No, NA values.

· If Yes, include a Sustain Casing Pressure Notes text field to provide details.

· Display the Fluid Type in Well field as a value list with Condensate, Diesel, Gas & Condensate, Seawater, Oil Based Mud, Water Based Mud, Synthetic Based Mud, Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Display the Weight input field in PPG.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· Display options that allow the Investigator to provide other related data as follows.

· In the BOP Stack option, display the BOP Stack Configuration input field, followed by the associated input fields: Size in inches, Press Rating in PSI, and Pressure in PSI. Also display the “BOP Stack - Last Test Date Prior to Incident” input field with a calendar and editable in the MM/DD/YYYY format.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Casing option, display the Last Casing String Set input field in feet and the associated Size input field in inches.

· Also display the Size of Drilling/Workover String in Hole input field in inches.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Well Control option, display the Kick Size input field in BBLs.

· Display the Fluid Kill Weight input field in PPG.

· Display the Initial S.I.C.P. and the S.I.C.P./W.S.P input fields in PSI.

· Display the Prior Hole Problems? field as a value list with Yes/No values.

· Display the LWC Duration input field in minutes.

· Display the Well Control Equipment Initially Activated field as a multi-selectable value list with values, Annular BOP, Pipe, Blind, Blind Shear, SCSSV, SSV, and Other. Also display the Other Notes input field if the “Other” value is selected from the value list to provide more details.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Diverter System option, display the Valve Size input field, the Line Size input field, the Spool field as a value list with Single and Dual as values, and “Was Well Diverted?” field as a value list with Yes/No values.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Other Info option, display the Bottom Hole Assembly input field.

· Also display Drilling Depth as two input fields, one input field in TVD and the other in MD.

· Display the Date Last Formation Integrity Test input field with a calendar and editable in the MM/DD/YYYY format.

· Display the SSV Type input field and the associated Date Last Tested input field with a calendar and editable in the MM/DD/YYYY format.

· Display the Tree field as a value list with On and Off values.

· Display the Surface Safety Equipment in Service? field as a value list with Yes/No values.

· Display Well TD as two input fields, one input field in TVD and the other in MD.

· Display the Open Perf? field as a value list with Yes/No values.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

As a BSEE Investigator I want to input other information for a Renewable Energy incident that a Renewable Energy representative or Internal User (Agent For) submitted so that I can provide additional information for the incident as part of my investigation.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to input the following Renewable Energy data. Note that these options will be displayed only for a Renewable Energy Incident Report.

· Display a BSEE Other Incidents Involving Significant Environmental Damage, or Harm entry which is editable and will be initially auto populated with the entry that the Operator representative provided.

· Display an Add BSEE Other Incidents Involving Significant Environmental Damage, or Harm option which allows the Investigator to provide one or more entries for this item.

· For this option, display a BSEE Other Incidents Involving Significant Environmental Damage, or Harm value list with Marine Mammals, Threatened and Endangered Species, Designated Critical Habitat, Archaeological Resources, Essential Fish Habitats, and Other as values. Also display an Other Notes input field to provide details if the “Other” value is selected.

· Display options that allow the Investigator to view, edit, and remove the BSEE Other Incidents Involving Significant Environmental Damage, or Harm entry with “BSEE Other Incidents Involving Significant Environmental Damage, or Harm” and “Other Notes” as the respective headings.

· Display the BSEE Other Incidents Involving Significant Environmental Damage, or Harm Remarks input field.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· Display an option for BSEE personnel to list any Terms and Conditions that apply to the effected resource as an input field.

As a BSEE Investigator I want to add investigation activity information to an associated incident record so that I can document onsite investigation and other investigation activities for the incident.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to input the following Investigation Activities data.

· Display an Add BSEE Investigation Team Member option which allows the Investigator to include personnel data for each member of the investigation team, followed by an Add Existing Other Investigation Team Member option and an Add New Other Investigation Team Member option to include members who are not BSEE personnel, such as those in the Coast Guard.

· For the Add BSEE Investigation Team Member option, display the Investigation Team Member Name field as a value list with the first and last names of BSEE employees, as well as their primary email and phone, as values.

· Note: The value list will be populated with BSEE personnel data.

· For the Add Existing Other Investigation Team Member option, display a value list with the first and last names and, in parenthesis, the associated agency of individuals who are not BSEE personnel.

· Note: The value list will be populated with the respective data from an “Other Investigation Members” table to be created for this purpose.

· For the Add New Other Investigation Team Member option, display the following input fields: First Name, Last Name, Position, Agency, Primary Email, and Phone.

· Note: The data will be saved to a new “Other Investigation Members” table.

· Display options that allow the Investigator to view, edit, and remove the selected BSEE Investigation Team Member and Other Investigation Team Member data with Investigation Team Member Name, Primary Email, and Phone as headings.

· Note: For a BSEE member, the Investigation Team Member Name entry is comprised of the member’s first and last names. For an “Other” member, the Investigation Team Member Name entry includes the member’s first and last names and, in parenthesis, their agency.

· Display an Add Date of Onsite Investigation option that allows the Investigator to provide a Date of Onsite Investigation entry. Multiple entries are allowed for this field.

· For the Add Date of Onsite Investigation option, display the Date of Onsite Investigation input field with a calendar and editable in the MM/DD/YYYY format.

· Display options that allow the BSEE Investigator to view, edit, and remove the selected entry with Date of Onsite Investigation as the column heading.

· For each Date of Onsite Investigation, provide an option to add an Investigation Team Member or other BSEE personnel.

· Display the Pictures Taken field as a value list with Yes/No values.

· Display the Statements Taken field as a value list with Yes/No values.

· For the Inspection data, the system should automatically display recent Inspection data for the relevant facility and/or facilities involved in the incident, using with BSEE’s Inspection data from the appropriate Inspection table in BSEE’s NCIS database – based on the Complex ID, Rig ID, Facility ID, Pipeline Segment Number, and/or Vessel ID.

· Display a list of the last five Inspection reports for the relevant facility and/or facilities involved in the incident and certain data about the Inspection, such as Inspection Number, District, Start Date, End Date, Area Code, Block Number, Complex ID, Rig ID, Facility ID, and other possible fields as provided by the Product Owner and/or SMEs.

· Display an option that allows the BSEE Investigator to select an Inspection report and view information about the Inspection, as provided by the Product Owner and/or SMEs.

· Display an option that allows the BSEE Investigator to associate an incident report directly to one or more Inspection reports if the Inspection was directly related to the incident/investigation, such as one or more Incident Follow-Up Inspection.

· Also display an option that allows the BSEE Investigator to disassociate an Inspection report with a prompt before disassociating.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

As a BSEE Investigator I want to input information from my investigation’s findings for an incident that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can document the findings for the incident’s investigation.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to input the Investigation Findings data in the following order and entitled “Summary,” “Causes & Recommendations,” and “Environmental Conditions,” respectively.

· All fields in the Investigation can be completed regardless of whether a District Investigation Report is selected.

· In the Summary option, display the following fields.

· Incident Summary, Sequence of Key Events, and BSEE Investigation fields as large input fields that allow the Investigator to provide as much respective narrative as needed.

· Property Damaged, Nature of Damage, and Estimated Amount (Total) as input fields.

· Additional Investigation Information as a large input field.

· Note: This is the same field currently in BSEE’s TIMS Events application called Additional Information.

· Validation of specified fields (TBD by the Product Owner by the Product Owner) will be carried out when saved.

· In the Causes & Recommendations option, display the following items.

· An Add Probable Cause option which allows the Investigator to enter data for a probable cause of the incident.

· Display the following fields for this option: Probable Cause as a value list with values from the Cause category/subcategory table, Other Cause as an input field if the “Other” value is selected from the Probable Cause value list, and Cause Description as a large input field.

· Note: The Cause category/subcategory table is a new table to be created for the new system.

· Additional Cause category/subcategory values may be provided by the Product Owner and/or SMEs.

· Display options that allow the Investigator to view, edit, and remove the Probable Cause entry with Probable Cause(s), Other Cause, and Cause Description as the respective headings.

· An Add Possible Contributing Cause option which allows the Investigator to enter data for a possible contributing cause of the incident.

· Display the following fields for this option: Possible Contributing Cause as a value list with values from the Cause category/subcategory table, Other Cause as an input field if the “Other” value is selected from the Probable Cause value list, and Cause Description as a large input field.

· Display options that allow the Investigator to view, edit, and remove the Possible Contributing Cause entry with Possible Contributing Cause(s), Other Cause, and Cause Description as the respective headings.

· An Add Contributing Factor option which allows the Investigator to enter data for a contributing factor of the incident.

· Display the following fields for this option: Contributing Factor as a value list with values from the Cause category/subcategory table, Other Cause as an input field if the “Other” value is selected from the Probable Cause value list, and Cause Description as a large input field.

· Display options that allow the Investigator to view, edit, and remove the Contributing Factor entry with Contributing Factor(s), Other Cause, and Cause Description as the respective headings.

· Recommendations to BSEE to Prevent Recurrence? as a value list option with Yes/No as values.

· The system should notify certain personnel in the Regional or Headquarters offices when this field is selected as Yes. Notification recipients and content of the notification email will be provided by the Product Owner and/or SMEs.

· Recommendations to BSEE to Prevent Recurrence Narrative as a large input field.

· Note: This field should be required if Recommendations to BSEE to Prevent Recurrence? is “Yes.”

· Recommendations to Industry to Prevent Recurrence Narrative as a large input field.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Environmental Conditions option, display the following fields.

· Wind Direction field as a value list with values E, ENE, ESE, N, NE, NNE, NNW, NW, S, SE, SSE, SSW, SW, W, WNW, and WSW.

· Wind Speed input field in MPH, with a conversion calculator that the Investigator can use to convert knots to miles per hour (MPH) if needed.

· Current Direction field as a value list with values E, ENE, ESE, N, NE, NNE, NNW, NW, S, SE, SSE, SSW, SW, W, WNW, and WSW.

· Current Speed input field in MPH, with a conversion calculator that the Investigator can use to convert knots to miles per hour (MPH) if needed.

· For a Renewable Energy incident, also allow Current Speed to be displayed and saved in meters per second. It is a working metric for turbine, lifting, turbine limitations, etc.

· Also display the Sustained (required) and Gusting Winds (optional) input fields.

· Sea State Height input field in feet, with a conversion calculator that the Investigator can use to convert meter to feet if needed.

· Weather Conditions as a value list with Clear, Fog, Rain, Snow, Ice, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Additional optional Environmental Conditions:

· Visibility in mile or tenths of miles

· Air Temperature

· Water Temperature

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

As a BSEE Investigator I want to input disposition data for an incident that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can provide the investigation’s reviewing official and possible OCS violations related to the incident.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to input the following Investigation Disposition data.

· Display the Possible OCS Violations Related to Incident field as a value list with Yes/No values.

· Display Specify Violations Directly or Indirectly Contributing Narrative as a large input field.

· Display the Operator Report on File field as a value list with Yes/No values.

· Display the OCS Report as an input field.

· Display the Reviewing Official as a value list whose First and Last Names values are drawn from the BSEE employee data, along with the associated Approved Date input field with a calendar and editable in the MM/DD/YYYY format.

· Among others, there will need to be a Reviewing Official role.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

As a BSEE Investigator I want to input data on injury, fatality, and witness for an incident that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can document the injury, fatality, and witness information for Operator, Contractor, and other personnel involved in the incident as part of my investigation.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to input the following Injury/Fatality/Witness data.

· Display an Add Personnel option which allows the Investigator to provide one or more entries.

· Display the following fields for this option.

· A Representative field as a value list with Operator, Contractor, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· An Injury/Fatality/Witness field as a multi-selectable value list with the following values: Injury, Fatality, Direct Witness, and Indirect Witness.

· Add Existing Name option that opens a window to allow the Investigator to select a Name from a value list of personnel data.

· Add New Name option that opens a window to allow the Investigator to add a new Name (first, MI, and last names).

· Alternative Address as an input field.

· City as an input field.

· State as a value list with the two-letter State Abbreviations as values.

· Work Phone as an input field with an (XXX) XXX-XXXX format.

· Total Offshore Experience as an input field in years.

· Total Facility Experience as an input field in years.

· Total Vessel Experience as an input field in years or months.

· Position as an input field.

· Employed by as an input field. Also display the “Employed by” company’s Business Address, Business City, Business State, and Business Zip Code as input fields.

· Injury/Fatality/Witness Remarks as an input field.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· Display options that allow the Investigator to view, edit, and remove the Personnel entry with Representative, Other Representative, Injury/Fatality/Witness, Name, Alternative Address, City, State, Work Phone, Total Offshore Experience, Total Facility Experience, Position, Employed by, Business Address, Business City, Business State, Business Zip Code, and Injury/Fatality/Witness Remarks as the respective headings.

· Note: For Injury/Fatality/Witness, display multiple selections with commas.

As a BSEE Investigator I want to input data on crane and other lifting device for an incident that a Lessee or Operator representative or Internal User (Agent For) submitted so that I can attach additional crane and other lifting device information relevant to my investigation.

Acceptance Criteria:

· Display options that allow the BSEE Investigator to provide the following Crane & Other Lifting Device data.

· For view only, display the Crane, Other Lifting Device, Personnel Lift, and Attached to Seabed entries if provided by the Operator representative.

· Display Crane & Lifting Device Facility as a value list with Platform Fixed, Platform Floating, Platform Rig, MODU, Motor Vessel, Jack Up, Lift Boat, Barge Survey Vessel, Installation Vessel, Crew Transfer Vessel, Offshore Supply Vessel, Cable Lay Vessel, Scour Protection Vessel, Service Operations Vessel as values.

· Display Crane & Lifting Device Facility Location as a multi-selectable value list option with N, NE, NW, S, SE, SW, E, W, Port, Starboard, Forward, Aft, Middle, and Rig Floor as values.

· For a Renewable Energy incident, add Transition Piece, Tower, Sump, Nacelle, and Substation as locations to the Crane & Lifting Device Facility Location value list.

· If the selected location is a Substation, display the name of the Deck Roof, Utility, Main, and Cable.

· Also display an Other REN Location input field for other locations for all Renewable facilities.

· Note: If Platform Fixed, Platform Floating, or Platform Rig is chosen from the Crane & Lifting Device Facility value list, then N, NE, NW, S, SE, SW, E, W, Middle, or Rig Floor should be selected.

· Note: If MODU or Motor Vessel is chosen from the Crane & Lifting Device Facility value list, then Port, Starboard, Forward, Aft, Middle, or Rig Floor should be selected.

· Lift Type as a multi-selectable value list with Onboard, Offboard, Static, Dynamic, and Subsea as values.

· Equipment Type as a value list with Crane, Other Lifting Device, and Rigging Hardware as values.

· Equipment Type Description as a value list with Fixed Crane (Permanent) and Rental Crane (Temporary/Movable) as values.

· Object Lifted as a value list with Material Handling, Pipe Handling, Non-lifting, and Personnel Handling as values.

· Object Description as an input field.

· Dropped Object as a value list with Onboard, Overboard – Recovered, Overboard – Unrecovered, and N/A as values.

· Dropped Object Zone as a list of values: Green, Yellow, Red.

· Failure of Critical Mechanical Components? as a value list with Yes, No, Unknown, and N/A as values.

· If “Yes” to Failure of Critical Mechanical Components?, display Failed Critical Mechanical Components as a multi-selectable value list with Brake linkage control system; Hoist and slewing brake system; Drums, shafts, overrunning clutches, and gears of hoisting and slewing systems; Swing circle assembly; and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Failure of Critical Structural Components? as a value list with Yes, No, Unknown, and N/A as values.

· If “Yes” to Failure of Critical Structural Components?, display Failed Critical Structural Components Structural Components as a multi-selectable value list with Fasteners in the critical load path of all critical components; Boom chord members; Boom section connection components; Boom heel pins; Boom jib section and connection components; Primary load members of gantries, masts and A-frames; Load transfer members of the rotating upper structure including fasteners; Kingposts; Pedestals and swing-circle transition pieces; and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Failure of Critical Rigging Components? as a value list with Yes, No, Unknown, and N/A as values.

· If “Yes” to Failure of Critical Rigging Components?, display Failed Critical Rigging Components as a multi-selectable value list with Running wire ropes in hoist systems; Standing wire ropes in load restraint and support systems; Hook block assembly; Overhaul ball or weight assembly; Wire rope dead-end connection devices; Bridle assemblies; Wire line sheaves and sheave shafts; Anti-Two Block; and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Failure of Load? as a value list with Yes, No, Unknown, and N/A as values.

· If “Yes” to Failure of Load?, display Failed Load as a multi-selectable value list with Shackles, Master Links, Slings, Wire Rope, Turnbuckles, Clevis, Pad Eyes/Lifting Eyes, Personnel Transfer Basket, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Overloaded? as a value list with Yes/No values.

· Failure of Lift Process? as a value list with Yes, No, Unknown, and N/A as values.

· If “Yes” to Failure of Lift Process?, display Failed Lift Process as multi-selectable value list with Planning, Safety Analysis, Pre-Use Inspection, Rigging, Lift Off, Lift Path, Set Down, Detachment, Non-Lift Movement, Weather/Sea State Assessment, Weight/Capacity Assessment, Load Position, Communication, SIMOPS, Vessel Motion, Cable Dynamics Assessment, Visibility, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Other values may be provided by the Product Owner and/or SMEs.

· Lift Path Issue as a value list with Line of Fire (Personnel), Lift Path Obstruction(s), Lift Path Pinch Point(s), and N/A as values.

· Also display the following note: “For additional input on causes and factors to this incident, please refer to the incident record’s Causes & Recommendations subtab of the Investigation Findings tab.”

· Crane Injured Person as a value list with Rigger, Personnel on Transfer Basket, Bystander, Flagger/Signalman, Crane Operator, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· Display options that allow the Investigator to provide other related data in the following order.

· In the Crane Information option, display the following fields.

· Display Crane Boom Type as a value list with Box Boom, Lattice Boom, Knuckle Boom, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Display Crane Type as a value list with Mechanical/Friction, Non-Mechanical Diesel – Hydraulic, Non-Mechanical Electric – Hydraulic, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Display Crane Classification Society Certificate as a value list with ABS, DNV, None, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Display Crane Standard as a multi-selectable value list with API Spec 2C Monogram Crane, ABS Rules, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Lift option, display the following fields.

· Boom Angle as an input field in degrees.

· Boon Radius as an input field in feet.

· Load Limit as an input field.

· Load Limit at Boom Angle during the Lift

· Line Type as value list with values Load (Main) Line, Fast (Aux) Line, Whip Line (to be used only if crane has three line types) and Both.

· Line Used as value list with values Load (Main) Line, Fast (Aux) Line, Whip Line (to be used only if crane has three line types) and Both.

· Load Block Configuration as an input field in part.

· Pre-use Inspection as a value list with Yes/No values.

· Pre-use Inspection by as a value list with Qualified Operator and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Pre-use Description input field.

· Max Static Lift Capacity and Max Dynamic Lift Capacity as input fields. Note that both fields are integers.

· Tag Line as a value list with Yes/No values.

· Sling/Loose Gear Program as a value list with Yes, No, and NA as values.

· Display Lift Plan/Permit as a value list with values Lift Plan, Lift Permit, Lift Plan and Lift Permit, and None.

· Display Lift Plan/Permit Deviation as a value list with Yes/No values.

· If Lift Plan/Permit Deviation is checked, display a Lift Plan/Permit Deviation Description input field to provide details.

· Lifting Equipment Remarks as an input field.

· Lift Category as a value list with Routine Lift and Non-Routine Lift as values.

· Lift Subcategory as a value list with Simple, Complicated, and Complex/Critical as values.

· Crane Operations Standard as a value list with API RP 2D 6th Edition, API RP 2D 8th Edition, None, and Other as values.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Line of Sight as a value list with Full, Partially Obstructed, and Blind as values.

· Lift Description as an input field.

· Heavy Lift field a value list with Yes/No values.

· Communication System as a value list with Hand Signal, Radio/VHF, Relay, and None as values.

· Was a Deck Supervisor/Designated Lift Authority Part of the Lift? as a value list with Yes/No values.

· Weight of Dropped Object as an input field in lbs.

· Closest Person to Dropped Object as an input field in ft.

· Dropped Object in Red Zone/Controlled Area as a value list with Yes/No values.

· Dropped Object Description as an input field.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Inspection/Maintenance option, display the following fields.

· Crane Usage as a value list with High, Infrequent, and Moderate as values.

· Last Inspection Date as an input field with a calendar and editable in the MM/DD/YY format.

· “Inspected by - Type” as a value list with Qualified Crane Inspector, Qualified Crane Operator, and Classification Surveyor as values.

· Inspected by as an input field.

· Inspection Type as a value list with In-house and Third Party as values.

· Inspector Qlfy by as an input field.

· Deficiency Description and Failure Description as input fields.

· Heavy Lift Test as a value list with Yes/No values.

· Test Type as a value list with Load Test and Pull Test as values.

· Pull Test Date and Load Test Date as input fields, both with a calendar and editable in the MM/DD/YY format.

· Test Results as a value list with Pass and Fail as values.

· Test Remarks as an input field.

· Test Boom Angle as an input field in degrees.

· Test Boom Radius as an input field in feet.

· Maintenance Date as an input field with a calendar and editable in the MM/DD/YY format.

· Maintenance Performed by as an input field.

· Maintenance Type as a value list with In-house and Third Party as values.

· Maintenance Description and Lifting Inspection/Maintenance Remarks as input fields.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Equipment option, display the following fields.

· Installation Date and Manufacture Date as input fields, both with a calendar and editable in the MM/DD/YY format.

· Manufacturer, Make, and Model as input fields.

· Also display an Add Equipment Modifications option which opens a window to allow the Investigator to enter lifting equipment modifications information. Multiple entries are allowed.

· In the Add Equipment Modifications window, display the following input fields: Modification Date with a calendar and editable in the MM/DD/YY format, Modification Description, and Lifting Equipment Modifications Remarks.

· Below the Add Equipment Modifications option, display the entry in a table with Modification Date, Modification Description, and Lifting Equipment Modifications Remarks as column headings, respectively. For the entry, include Edit/Remove icons/options.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Load Information option, display the following fields.

· Load Weight as an input field and associated Operable Weight Indicator and Correct Weight Identified as value lists with Yes/No values.

· Load Height, Load Width, and Load Length as input fields in feet. Display a conversion calculator for each of these fields to convert inches, yards, or meters to feet.

· Rigging Configuration as a value list with Wire Rope Sling Pattern, 4-Part Shackle, D-Rings, Padeyes, and Other.

· If the “Other” value is selected, display an input field below the value list to provide details.

· Personnel Riding Apparatus as an input field.

· Safety Harness as a value list with N, NA, and Y as values.

· Lifeline as a value list with N, NA, and Y as values.

· Also display an Add Equipment Property Lost option which opens a window to allow the Investigator to enter equipment property lost information. Multiple entries are allowed.

· In the Add Equipment Property Lost window, display the Item Description and Equipment Property Lost Remarks input fields.

· Below the Add Equipment Property Lost option, display the entry in a table with Item Description and Equipment Property Lost Remarks as column headings, respectively. For the entry, include Edit/Remove icons/options.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Other Device option, display the following fields.

· Operator Trained as a value list with Yes/No values.

· Years of Experience as an input field.

· Equipment Inspected as a value list with Yes/No values.

· Manufacture's Inspection Recommendation as an input field.

· Other Material Handling Equipment Remarks as an input field.

· Validation of specified fields (TBD by the Product Owner) will be carried out when saved.

· In the Crane Operator/Rigger option, display the following two options for it.

· In the Crane Operator option, display the following fields.

· Duty Hours and Sleep Time as input fields.

· Medicated, Drug Tested, Eye Assistance, Eye Assistance Used, Hearing Aid, and Hearing Aid Used as value lists with Yes/No values.

· Crane Operator Remarks as an input field.

· Operator Qualified as a value list with Yes/No values, along with the associated Years Experience, Months Experience, and Training Dates as input fields.

· Crane Operator Competency Assessment…