The document outlines the duties and responsibilities of the Officer of the Watch (OOW) according to STCW regulations. The OOW is primarily responsible for the safe navigation of the ship and compliance with collision regulations. Key duties include maintaining a proper lookout, navigating the ship according to the passage plan, using all navigational equipment, communicating via radio, and notifying the master immediately of any issues or hazards. The OOW must execute their duties safely and in accordance with international regulations.
A presentation on 'The International Convention for Preventing Collisions at Sea 1972' (COLREG 72) to the LLM Maritime Law students at University of Southampton.
A presentation on 'The International Convention for Preventing Collisions at Sea 1972' (COLREG 72) to the LLM Maritime Law students at University of Southampton.
Presentation on maneuvering and collision avoidance with special focus on large tonnage vessels.
Maneuverability limits and last moment maneuver are thoroughly shown in this material.
Presentation on maneuvering and collision avoidance with special focus on large tonnage vessels.
Maneuverability limits and last moment maneuver are thoroughly shown in this material.
Curso impartido por el autor en la Dirección Provincial de Gijón del Instituto Social de la Marina, para la obtención del certificado de Oficial de Marinero Pescador. Año 2013.
GraphRAG is All You need? LLM & Knowledge GraphGuy Korland
Guy Korland, CEO and Co-founder of FalkorDB, will review two articles on the integration of language models with knowledge graphs.
1. Unifying Large Language Models and Knowledge Graphs: A Roadmap.
https://arxiv.org/abs/2306.08302
2. Microsoft Research's GraphRAG paper and a review paper on various uses of knowledge graphs:
https://www.microsoft.com/en-us/research/blog/graphrag-unlocking-llm-discovery-on-narrative-private-data/
PHP Frameworks: I want to break free (IPC Berlin 2024)Ralf Eggert
In this presentation, we examine the challenges and limitations of relying too heavily on PHP frameworks in web development. We discuss the history of PHP and its frameworks to understand how this dependence has evolved. The focus will be on providing concrete tips and strategies to reduce reliance on these frameworks, based on real-world examples and practical considerations. The goal is to equip developers with the skills and knowledge to create more flexible and future-proof web applications. We'll explore the importance of maintaining autonomy in a rapidly changing tech landscape and how to make informed decisions in PHP development.
This talk is aimed at encouraging a more independent approach to using PHP frameworks, moving towards a more flexible and future-proof approach to PHP development.
Smart TV Buyer Insights Survey 2024 by 91mobiles.pdf91mobiles
91mobiles recently conducted a Smart TV Buyer Insights Survey in which we asked over 3,000 respondents about the TV they own, aspects they look at on a new TV, and their TV buying preferences.
GDG Cloud Southlake #33: Boule & Rebala: Effective AppSec in SDLC using Deplo...James Anderson
Effective Application Security in Software Delivery lifecycle using Deployment Firewall and DBOM
The modern software delivery process (or the CI/CD process) includes many tools, distributed teams, open-source code, and cloud platforms. Constant focus on speed to release software to market, along with the traditional slow and manual security checks has caused gaps in continuous security as an important piece in the software supply chain. Today organizations feel more susceptible to external and internal cyber threats due to the vast attack surface in their applications supply chain and the lack of end-to-end governance and risk management.
The software team must secure its software delivery process to avoid vulnerability and security breaches. This needs to be achieved with existing tool chains and without extensive rework of the delivery processes. This talk will present strategies and techniques for providing visibility into the true risk of the existing vulnerabilities, preventing the introduction of security issues in the software, resolving vulnerabilities in production environments quickly, and capturing the deployment bill of materials (DBOM).
Speakers:
Bob Boule
Robert Boule is a technology enthusiast with PASSION for technology and making things work along with a knack for helping others understand how things work. He comes with around 20 years of solution engineering experience in application security, software continuous delivery, and SaaS platforms. He is known for his dynamic presentations in CI/CD and application security integrated in software delivery lifecycle.
Gopinath Rebala
Gopinath Rebala is the CTO of OpsMx, where he has overall responsibility for the machine learning and data processing architectures for Secure Software Delivery. Gopi also has a strong connection with our customers, leading design and architecture for strategic implementations. Gopi is a frequent speaker and well-known leader in continuous delivery and integrating security into software delivery.
Kubernetes & AI - Beauty and the Beast !?! @KCD Istanbul 2024Tobias Schneck
As AI technology is pushing into IT I was wondering myself, as an “infrastructure container kubernetes guy”, how get this fancy AI technology get managed from an infrastructure operational view? Is it possible to apply our lovely cloud native principals as well? What benefit’s both technologies could bring to each other?
Let me take this questions and provide you a short journey through existing deployment models and use cases for AI software. On practical examples, we discuss what cloud/on-premise strategy we may need for applying it to our own infrastructure to get it to work from an enterprise perspective. I want to give an overview about infrastructure requirements and technologies, what could be beneficial or limiting your AI use cases in an enterprise environment. An interactive Demo will give you some insides, what approaches I got already working for real.
UiPath Test Automation using UiPath Test Suite series, part 4DianaGray10
Welcome to UiPath Test Automation using UiPath Test Suite series part 4. In this session, we will cover Test Manager overview along with SAP heatmap.
The UiPath Test Manager overview with SAP heatmap webinar offers a concise yet comprehensive exploration of the role of a Test Manager within SAP environments, coupled with the utilization of heatmaps for effective testing strategies.
Participants will gain insights into the responsibilities, challenges, and best practices associated with test management in SAP projects. Additionally, the webinar delves into the significance of heatmaps as a visual aid for identifying testing priorities, areas of risk, and resource allocation within SAP landscapes. Through this session, attendees can expect to enhance their understanding of test management principles while learning practical approaches to optimize testing processes in SAP environments using heatmap visualization techniques
What will you get from this session?
1. Insights into SAP testing best practices
2. Heatmap utilization for testing
3. Optimization of testing processes
4. Demo
Topics covered:
Execution from the test manager
Orchestrator execution result
Defect reporting
SAP heatmap example with demo
Speaker:
Deepak Rai, Automation Practice Lead, Boundaryless Group and UiPath MVP
Search and Society: Reimagining Information Access for Radical FuturesBhaskar Mitra
The field of Information retrieval (IR) is currently undergoing a transformative shift, at least partly due to the emerging applications of generative AI to information access. In this talk, we will deliberate on the sociotechnical implications of generative AI for information access. We will argue that there is both a critical necessity and an exciting opportunity for the IR community to re-center our research agendas on societal needs while dismantling the artificial separation between the work on fairness, accountability, transparency, and ethics in IR and the rest of IR research. Instead of adopting a reactionary strategy of trying to mitigate potential social harms from emerging technologies, the community should aim to proactively set the research agenda for the kinds of systems we should build inspired by diverse explicitly stated sociotechnical imaginaries. The sociotechnical imaginaries that underpin the design and development of information access technologies needs to be explicitly articulated, and we need to develop theories of change in context of these diverse perspectives. Our guiding future imaginaries must be informed by other academic fields, such as democratic theory and critical theory, and should be co-developed with social science scholars, legal scholars, civil rights and social justice activists, and artists, among others.
The Art of the Pitch: WordPress Relationships and SalesLaura Byrne
Clients don’t know what they don’t know. What web solutions are right for them? How does WordPress come into the picture? How do you make sure you understand scope and timeline? What do you do if sometime changes?
All these questions and more will be explored as we talk about matching clients’ needs with what your agency offers without pulling teeth or pulling your hair out. Practical tips, and strategies for successful relationship building that leads to closing the deal.
Connector Corner: Automate dynamic content and events by pushing a buttonDianaGray10
Here is something new! In our next Connector Corner webinar, we will demonstrate how you can use a single workflow to:
Create a campaign using Mailchimp with merge tags/fields
Send an interactive Slack channel message (using buttons)
Have the message received by managers and peers along with a test email for review
But there’s more:
In a second workflow supporting the same use case, you’ll see:
Your campaign sent to target colleagues for approval
If the “Approve” button is clicked, a Jira/Zendesk ticket is created for the marketing design team
But—if the “Reject” button is pushed, colleagues will be alerted via Slack message
Join us to learn more about this new, human-in-the-loop capability, brought to you by Integration Service connectors.
And...
Speakers:
Akshay Agnihotri, Product Manager
Charlie Greenberg, Host
Neuro-symbolic is not enough, we need neuro-*semantic*Frank van Harmelen
Neuro-symbolic (NeSy) AI is on the rise. However, simply machine learning on just any symbolic structure is not sufficient to really harvest the gains of NeSy. These will only be gained when the symbolic structures have an actual semantics. I give an operational definition of semantics as “predictable inference”.
All of this illustrated with link prediction over knowledge graphs, but the argument is general.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...Ramesh Iyer
In today's fast-changing business world, Companies that adapt and embrace new ideas often need help to keep up with the competition. However, fostering a culture of innovation takes much work. It takes vision, leadership and willingness to take risks in the right proportion. Sachin Dev Duggal, co-founder of Builder.ai, has perfected the art of this balance, creating a company culture where creativity and growth are nurtured at each stage.
Builder.ai Founder Sachin Dev Duggal's Strategic Approach to Create an Innova...
Responsibilities of the oow lrg
1. Grunt Productions 2003
DUTIES AND RESPONSIBILITIES OF THE
OFFICER IN CHARGE OF A NAVIGATIONAL
WATCH
A Brief By Lance Grindley
2. Grunt Productions 2003
DUTIES AND RESPONSIBILITIES OF THE OFFICER IN
CHARGE OFA NAVIGATIONAL WATCH
STCW Code states that the Officer of the Watch
(OOW) is the master's representative and is primarily
responsible at all times for the safe navigation of the ship
and for complying with the COLREG.
3. Grunt Productions 2003
PRIMARY DUTIES OF THE OOW
• 1. Watchkeeping.
The watchkeeping duties of the OOW include maintaining a lookout and
general surveillance of the ship, collision avoidance in compliance with
the COLREG, recording bridge activities and making periodic checks on
the navigational equipment in use. Procedures for handing over the watch
and calling for support on the bridge should be in place and understood by
the OOW.
4. Grunt Productions 2003
PRIMARY DUTIES OF THE OOW
• 2. Navigation
The navigational duties of the OOW are based upon the need
to execute the passage plan safely, and monitor the progress of
the ship against that plan.
5. Grunt Productions 2003
PRIMARY DUTIES OF THE OOW
• 3. Radio Communications
With the introduction of the GMDSS, radio
communications have now become important
elements in the functions of the OOW, who
will be responsible for maintaining a
continuous radio watch at sea. During distress
incidents, one of the qualified radio personnel
(master and any deck officers) should be
designated to have primary responsibility for
radio communications. On passenger ships,
that person can have no other duties during a
distress situation.
6. Grunt Productions 2003
The OOW needs to be conversant with means and best practices of controlling
the speed and direction of the ship, handling characteristics and stopping
distances. The OOW should not hesitate to use helm, engines or sound
signaling apparatus at any time.
The OOW also needs to be fully conversant with shipboard obligations with
regards to pollution prevention, reporting and emergency situations. The
OOW should know the location of all the safety equipment on the bridge and
how to operate that equipment.
The OOW should not leave the bridge unattended. However, in a ship with a
separate chartroom, the OOW may visit that room for short periods of time to
carry out necessary navigation duties after first ensuring that it is safe to do
so.
7. Grunt Productions 2003
The Master's appearance on the bridge does not relieve the OOW of
his responsibilities. The officer on duty is still in charge of the watch
until the Master formally takes charge. It must be made clear
immediately who is in charge of the watch. To avoid any confusion,
the officer on duty must assume he is in charge of the watch unless
formally relieved by the master and entered in the logbook the time
the Master took over the conn.
8. Grunt Productions 2003
THE PRINCIPLES TO BE OBSERVED IN KEEPING A
NAVIGATIONAL WATCH (NO PILOT ON BOARD)
The OOW shall:
1.
a) keep his watch on the bridge;
b) in no circumstances leave the bridge until properly relieved;
c) continue to be responsible for the safe navigation of the ship, despite
the presence of the master on the bridge, until the master informs him
specifically that he has assumed that responsibility and this is mutually
understood; and
d) notify the master when in doubt as to what action to take in the
interest of safety.
Navigational Duties and Responsibilities
9. Grunt Productions 2003
2. During the watch, the course steered, position, and speed shall be checked at
sufficiently frequent intervals, using any available navigational aids necessary
to ensure that the ship follows the planned course.
3. The OOW shall have full knowledge of the location and operation of all
safety and navigational
equipment on board the ship and shall
be aware and take account of the operating
limitations of such equipment.
10. Grunt Productions 2003
4. The OOW shall not be assigned or undertake any duties which would
interfere with the safe navigation of the ship.
5. OOWs shall make the most effective use of all navigational equipment
at their disposal.
6. When using radar, the OOW shall bear in mind the necessity to comply at all times
with the provisions on the use of radar contained in the International Regulations for
Preventing Collision at Sea in force.
7. In cases of need, the OOW shall not hesitate to use the helm, engines, and sound
signaling apparatus. However, timely notice of intended variations of engine speed
shall be given where possible or effective use made of UMS (Unmanned Machinery
Space) engine controls provided on the bridge in accordance with the applicable
procedures. .
8. OOWs shall know the handling characteristics of their ship including its stopping
distances and should appreciate that other ships may have different handling
characteristics.
11. Grunt Productions 2003
9. Proper record shall be kept during the watch of the movements and
activities relating to the navigation of the ship.
10. It is of special importance that at all times the OOW ensures that a proper
look-out is maintained. In a ship with a separate chartroom, the OOW may
visit the chartroom, when essential, for a short period for the necessary
performance of navigational duties, but shall first ensure that it is safe to do so
and that proper look-out is maintained.
11. Operational test of shipboard navigational watch equipment shall be
carried out at sea as frequently as practicable and as circumstances permit, in
particular before hazardous conditions affecting navigation are expected.
Whenever appropriate, these tests shall be recorded. Such tests shall also be
carried out prior to port arrival and departure.
12. Grunt Productions 2003
12. The OOW shall make regular checks to ensure that:
a) the person steering the ship or the automatic pilot is steering the
correct course;
b) the standard compass error is determined at least once a watch
and, when possible, after any major alteration of course. The
standard gyro compasses are frequently compared and
repeaters are synchronized with their master compass;
c) the automatic pilot is tested manually at least once a watch;
d) the navigation and signal lights and other navigational
equipment are functioning properly;
e) the radio equipment is functioning properly; and
f) the UMS controls, alarms and indicators are functioning
properly.
13. Grunt Productions 2003
13. The OOW shall bear in mind the necessity to comply at all times with the
requirements in force of the International Convention for Safety of Life At Sea
(SOLAS), 1974. The OOW shall take into account:
a) the need to station a person to steer the ship and to put the steering
onto manual control in good time to allow any potentially hazardous situation
to be dealt with in a safe manner; and
b) that with a ship under automatic steering it is highly dangerous to
allow a situation to develop to the point where the OOW is without assistance
and has to break the continuity of the look-out in order to take emergency
action.
14. Grunt Productions 2003
14. The OOW shall be thoroughly familiar with the use of all electronic
navigational aids carried, including their capabilities and limitations, and
shall use each of these aids carried, including their capabilities and
limitations, and shall use each of these aids when appropriate and shall bear
in mind that the echo sounder is a valuable navigational aid.
15. The OOW shall use the radar whenever restricted visibility is encountered
or expected, and at all times in congested waters, having due regard for its
limitations.
16. The OOW shall ensure that range scales employed are changed at
sufficiently frequent intervals so that echoes are detected as early as possible.
It shall be borne in mind that small or poor echoes may escape detection.
17. Whenever radar is in use, the OOW shall select an appropriate range
scale, observes the display carefully, and shall ensure that plotting or
systematic analysis is commenced in ample time.
15. Grunt Productions 2003
18. The OOW shall notify the master immediately:
a) restricted visibility
b) heavy traffic conditions
c) difficulty in maintaining course
d) failure to sight land, marks or to obtain soundings by
the expected time;
e) if, unexpectedly, a land or a navigation mark is sighted or a change in
sounding occurs;
f) on breakdown of the engines, propulsion machinery remote control, steering
gear or any essential navigational equipment
g) if the radio equipment malfunctions
h) in heavy weather; if in any doubt about the possibility of weather
damage;
i) if the ship meets any hazard to navigation, such as ice or a derelict; and
j) in any other emergency or if in any doubt.
16. Grunt Productions 2003
19. Despite the requirement to notify the master immediately in the
foregoing circumstances, the OOW shall in addition not hesitate to
take immediate action for the safety of the ship, where circumstances
so require.
20. The OOW shall give watchkeeping personnel all appropriate
instructions and information which will ensure the keeping of a safe
watch, including a proper look-out.