clifford
    • Create new note
    • Create a note from template
      • Sharing URL Link copied
      • /edit
      • View mode
        • Edit mode
        • View mode
        • Book mode
        • Slide mode
        Edit mode View mode Book mode Slide mode
      • Customize slides
      • Note Permission
      • Read
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Write
        • Only me
        • Signed-in users
        • Everyone
        Only me Signed-in users Everyone
      • Engagement control Commenting, Suggest edit, Emoji Reply
    • Invite by email
      Invitee

      This note has no invitees

    • Publish Note

      Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

      Your note will be visible on your profile and discoverable by anyone.
      Your note is now live.
      This note is visible on your profile and discoverable online.
      Everyone on the web can find and read all notes of this public team.
      See published notes
      Unpublish note
      Please check the box to agree to the Community Guidelines.
      View profile
    • Commenting
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
      • Everyone
    • Suggest edit
      Permission
      Disabled Forbidden Owners Signed-in users Everyone
    • Enable
    • Permission
      • Forbidden
      • Owners
      • Signed-in users
    • Emoji Reply
    • Enable
    • Versions and GitHub Sync
    • Note settings
    • Note Insights New
    • Engagement control
    • Make a copy
    • Transfer ownership
    • Delete this note
    • Save as template
    • Insert from template
    • Import from
      • Dropbox
      • Google Drive
      • Gist
      • Clipboard
    • Export to
      • Dropbox
      • Google Drive
      • Gist
    • Download
      • Markdown
      • HTML
      • Raw HTML
Menu Note settings Note Insights Versions and GitHub Sync Sharing URL Create Help
Create Create new note Create a note from template
Menu
Options
Engagement control Make a copy Transfer ownership Delete this note
Import from
Dropbox Google Drive Gist Clipboard
Export to
Dropbox Google Drive Gist
Download
Markdown HTML Raw HTML
Back
Sharing URL Link copied
/edit
View mode
  • Edit mode
  • View mode
  • Book mode
  • Slide mode
Edit mode View mode Book mode Slide mode
Customize slides
Note Permission
Read
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Write
Only me
  • Only me
  • Signed-in users
  • Everyone
Only me Signed-in users Everyone
Engagement control Commenting, Suggest edit, Emoji Reply
  • Invite by email
    Invitee

    This note has no invitees

  • Publish Note

    Share your work with the world Congratulations! 🎉 Your note is out in the world Publish Note

    Your note will be visible on your profile and discoverable by anyone.
    Your note is now live.
    This note is visible on your profile and discoverable online.
    Everyone on the web can find and read all notes of this public team.
    See published notes
    Unpublish note
    Please check the box to agree to the Community Guidelines.
    View profile
    Engagement control
    Commenting
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    • Everyone
    Suggest edit
    Permission
    Disabled Forbidden Owners Signed-in users Everyone
    Enable
    Permission
    • Forbidden
    • Owners
    • Signed-in users
    Emoji Reply
    Enable
    Import from Dropbox Google Drive Gist Clipboard
       Owned this note    Owned this note      
    Published Linked with GitHub
    • Any changes
      Be notified of any changes
    • Mention me
      Be notified of mention me
    • Unsubscribe
    # comp6841 f13a week2 ## agenda what was cool from lectures something awesome open learning permissions case study extension activities ## Case Study The us presentdent have asked you to inequire about the deep water disaster you have been asked to consider the main lesson s to be learned from the dfisaster to produce a shjort list of reommendatoons tfor actions to be taken to prevent future disasters Government, public and oil industry all support the inquiry and will give rsources for investigation give 5 recommendatioons from theis presidental inquirey for actions to be taken to prevent future disasters justify recommendation and justify your ranking, decreasing order ## Class top 5 1. Group 1 + Group 2's number 1 (regulation by someone) 2. Group 3's number 1 (automation of systems for detecting errors?) Current - group 1's number 3 (training, procedures that must be followed) ### Group 1 Inquiry (What went wrong?) Recommendations 1. Introduction of a communications officer for on-job issues - When issues occur, they communicate directly to all related parties to assess for any safety issues that need to be fixed before the job can continue. The role is government managed to ensure that a manager's self interest is not prioritised. 2. The government in conjunction with petroleum companies develop regulations related to construction (i.e. materials, equipment, etc), maintenance, and testing procedures. Companies which violate these regulations have the drilling licence for that rig cancelled. Continued violations can lead to all their drilling licences being revoked. All oil rigs are subject to random and regular inspection. 3. The petroleum companies develop their own training and safety procedures that are then approved by the government. These procedures should aim to prioritise safety over meeting deadlines and are subject to regular review and after all accidents. All employees (including executives) need to have completed the training to be allowed on oil rigs. Executives cannot make decisions regarding the operation of the oil rig if they have not completed the training and safety procedures. As part of the procedure, if an important issue is discovered, the details must be recorded immediately to better inform the executives or workers who are changing shifts so the issue can be resolved without delay. 4. All oil rigs need to pay a tax that is added to a fund to be used to pay for disaster cleanups and safety R&D (i.e. research on safety flaws, developing foolproof equipment, etc) with no patents. This will also be used to pay for government operations related to the regulation of the oil rigs. Note: this does not remove a company's liability for a disaster. They will still have to bear the main cost of a cleanup program as well be subject to severe fines as well as paying for the investigations. 5. If safer equipment that is compatible with the rig is developed then the oil rig should receive a (very low) temporary tax break for implementing it within a specified time period. Notes - Stricter standards i.e. safety, communication - Regular 3rd party audits to prevent bias - let engineers have the final say - There were some problems with testing - Maintenence is a top priority - Communication issues need to be fixed for transparency - Used nitrogen to harden cement faster which caused - ethics training for managers / processes for doing something - actually review reports - foolproof equipment - safety > profit - have crews actually do their jobs - properly report errors - actual chain of command - regular safety/maintenance tests (FEEL FREE TO DELETE THAT MY BAD) ---- ### Group 2 Reccomendations thanks 1. Regulatory body created for current and future oil rigs and its parts - needs to be deeply seated?seeded? in the whole process from planning to creation to drilling. Provide inspections of operations and shut down production if drilling cannot be made at a safe level. 1. Regulatory will enable more control of what is allowed and also force industry giants to abide by the rules via inspection 2. Crew management needs to be improved and up to a certain standard. Training for managers and more frequent communnications between maangers -daily meetings 2. because a lot of problems stemmed from this, prevent breakdown of communication 3. Documentation for passing between companies/teams. Have teams be responsible for all of these things - avoid discrepencies for certain issues 4. Agreements need to be made before drilling starts. Who makes decisions, who makes the final decision (conflict resolution) - eliminate finger pointing after accidents 5. Legal responsibility, fines that make an actual impact from failing to follow regulations. Penalties to ensure things are enforced every time something goes wrong or is found to be wrong. - need incentive to prevent these from happening 7. FOLLOW THE PLANNED PROCEDURES THAT WERE TESTED AND TALKED ABOUT 2. Change in plans must be communicated and agreed on 3. Regular maintenance on machines, especially on emergency devices - sheer triggered early causing it to fail as the fail-safe 4. Don't rush things? Upper managedment wanted to go faster to save money. Have incentives to go slower - to make sure things are doing things right? 5. An issues board which registers all the issues including closed issues and issues to follow up - Regulatory body to regulate all of these negligent behaviours - If regulations are not met, prevent anything from ocurring - need to stop them - - Swapping teams meant info was lost on all the problems that are going wrong - Nursing, hospital staff. How do they share info when swapping people? - Have documentation on exactly one thing - Conflict resolution - third party comes in that gets involved - - SENG - what do they do to share info when swapping people - Have documentation - More preventative measures for human errors - One button push caused huge errors - Warantee like seals for things that should not be tampered with - Control pod was broken but they tested it remotely??? did they actually test it - Regulations needed to be implemented BEFORE things go wrong - Sea water and mud the gas and o-il went up the risers - They were too lax about the last line of defence (which was it) - When problems happened with it, they should have immediately do something about it - The crew just left when things were going wrong - Evacuation didn't occur when things went wrong - Break down in communications - Three companies involved - communication nightmare? and even more - Lots of communications - Cut a lot of corners and turned a blind eye - There was no overarching commanding over what should be happening - All the problems from all the companies needed to be reported somewhere - A lot of things that were never approved or sanctioned, - Whistleblower protection (BP fired the snitches) - REgulations basically didn't exist and the government didn't do anything when they did get informed about it - NEED TO PREVENT ALL THE NEGLIGENCE THAT'S BEEN - - let engineers have the final say - There were some problems with testing - Maintenence is a top priority - Communication issues need to be fixed for transparency - Used nitrogen to harden cement faster which caused - Transocean manager vs BP manager. Trans said to use mud, bp said yeah nah pass and caused all this stuff probably - ---- ### Group 3 **Discussion Points:** Significant errors: - Disagreement btw rig operator and BP on method of extraction (communication error) - There were earlier problems not dealt with properly - Disregarding signs of problems e.g "Yeah there is nothing to worry about" - Wrong chemicals arriving adding to confusion - Parts of drill equiptment to centralize the pipes was not installed - No real standard to perform negative pressure test - Lots of pressure to be productive - Blame game - Designs were not approved before manufacturing - Evacuation procedure was not followed **Recommendations** 0. No more oil drilling, solar power everywhere (hahaha) 1. Design better error detections systems to detect errors e.g fractures, faults - more automation 2. A more careful planning phase before the operation so that when there are problems everyone are better equipped to know what to do. e.g warning signs, actions, planning critical operation decisions early and avoid disagreement during critical stressful period 3. Having union member focussed on safety supervising process to prevent workers and managers from disregarding potential problems 4. More relevant and stringent training for operators, workers, managers including communication, dealing with pressure and stressful situation, communicating problems 5. Reintroduce safety restrictions/regulations (that were relaxed), testings on rigs, safety inspectors disregarded due to no incidents ---- ### Group 4 ---- ### All Recommendations #### Group 1 Introduction of a communications officer for on-job issues - When issues occur, they communicate directly to all related parties to assess for any safety issues that need to be fixed before the job can continue. The role is government managed to ensure that a manager's self interest is not prioritised. #### Group 2 Regulatory body created for current and future oil rigs and its parts - needs to be deeply seated in the whole process from planning to creation to drilling. Provide inspections of operations and shut down production if drilling cannot be made at a safe level. Allows workers with safety concerns to notify body if upper management rejects their concerns. Why? Regulatory will enable more control of what is allowed and also force industry giants to abide by the rules via inspection

    Import from clipboard

    Paste your markdown or webpage here...

    Advanced permission required

    Your current role can only read. Ask the system administrator to acquire write and comment permission.

    This team is disabled

    Sorry, this team is disabled. You can't edit this note.

    This note is locked

    Sorry, only owner can edit this note.

    Reach the limit

    Sorry, you've reached the max length this note can be.
    Please reduce the content or divide it to more notes, thank you!

    Import from Gist

    Import from Snippet

    or

    Export to Snippet

    Are you sure?

    Do you really want to delete this note?
    All users will lose their connection.

    Create a note from template

    Create a note from template

    Oops...
    This template has been removed or transferred.
    Upgrade
    All
    • All
    • Team
    No template.

    Create a template

    Upgrade

    Delete template

    Do you really want to delete this template?
    Turn this template into a regular note and keep its content, versions, and comments.

    This page need refresh

    You have an incompatible client version.
    Refresh to update.
    New version available!
    See releases notes here
    Refresh to enjoy new features.
    Your user state has changed.
    Refresh to load new user state.

    Sign in

    Forgot password

    or

    By clicking below, you agree to our terms of service.

    Sign in via Facebook Sign in via Twitter Sign in via GitHub Sign in via Dropbox Sign in with Wallet
    Wallet ( )
    Connect another wallet

    New to HackMD? Sign up

    Help

    • English
    • 中文
    • Français
    • Deutsch
    • 日本語
    • Español
    • Català
    • Ελληνικά
    • Português
    • italiano
    • Türkçe
    • Русский
    • Nederlands
    • hrvatski jezik
    • język polski
    • Українська
    • हिन्दी
    • svenska
    • Esperanto
    • dansk

    Documents

    Help & Tutorial

    How to use Book mode

    Slide Example

    API Docs

    Edit in VSCode

    Install browser extension

    Contacts

    Feedback

    Discord

    Send us email

    Resources

    Releases

    Pricing

    Blog

    Policy

    Terms

    Privacy

    Cheatsheet

    Syntax Example Reference
    # Header Header 基本排版
    - Unordered List
    • Unordered List
    1. Ordered List
    1. Ordered List
    - [ ] Todo List
    • Todo List
    > Blockquote
    Blockquote
    **Bold font** Bold font
    *Italics font* Italics font
    ~~Strikethrough~~ Strikethrough
    19^th^ 19th
    H~2~O H2O
    ++Inserted text++ Inserted text
    ==Marked text== Marked text
    [link text](https:// "title") Link
    ![image alt](https:// "title") Image
    `Code` Code 在筆記中貼入程式碼
    ```javascript
    var i = 0;
    ```
    var i = 0;
    :smile: :smile: Emoji list
    {%youtube youtube_id %} Externals
    $L^aT_eX$ LaTeX
    :::info
    This is a alert area.
    :::

    This is a alert area.

    Versions and GitHub Sync
    Get Full History Access

    • Edit version name
    • Delete

    revision author avatar     named on  

    More Less

    Note content is identical to the latest version.
    Compare
      Choose a version
      No search result
      Version not found
    Sign in to link this note to GitHub
    Learn more
    This note is not linked with GitHub
     

    Feedback

    Submission failed, please try again

    Thanks for your support.

    On a scale of 0-10, how likely is it that you would recommend HackMD to your friends, family or business associates?

    Please give us some advice and help us improve HackMD.

     

    Thanks for your feedback

    Remove version name

    Do you want to remove this version name and description?

    Transfer ownership

    Transfer to
      Warning: is a public team. If you transfer note to this team, everyone on the web can find and read this note.

        Link with GitHub

        Please authorize HackMD on GitHub
        • Please sign in to GitHub and install the HackMD app on your GitHub repo.
        • HackMD links with GitHub through a GitHub App. You can choose which repo to install our App.
        Learn more  Sign in to GitHub

        Push the note to GitHub Push to GitHub Pull a file from GitHub

          Authorize again
         

        Choose which file to push to

        Select repo
        Refresh Authorize more repos
        Select branch
        Select file
        Select branch
        Choose version(s) to push
        • Save a new version and push
        • Choose from existing versions
        Include title and tags
        Available push count

        Pull from GitHub

         
        File from GitHub
        File from HackMD

        GitHub Link Settings

        File linked

        Linked by
        File path
        Last synced branch
        Available push count

        Danger Zone

        Unlink
        You will no longer receive notification when GitHub file changes after unlink.

        Syncing

        Push failed

        Push successfully