A hydrographic survey vessel shows three -dimensional movements (Roll, Pitch and Heave) misalignment with respect to the vessel reference unit (VRU) due to environmental effects, such as wind, current, other vessel wakes, etc. These motions if ignored, cause errors in measured depth and in the positioning of the sounding. Hence the need of a motion sensor and gyroscope. However, the alignment of the multi-beam sonar head to the motion sensor and gyro (Octant) is critical to the accuracy of the determined depths. It is not possible to install the sonar head in perfect alignment with the motion sensor and gyroscope to the accuracy required. The synchronization of the GPS time with the Motion sensor and gyro, the latency of the position, as reported by the GPS as well as the velocity of sound in water are important parameters to account for the misalignment of the motion senor and the multi beam sonar head; this is called the Patch Test. In view of this, a patch test was done to ascertain the mounting angles of EMB 2058 Multi-beam sonar with Octan V installed onboard a survey vessel (Bitam). The result of the Patch test gives a row, pitch and heading value of -1.242˚, -4.92˚, and -0.48˚respectively. The speed of sound in water as measured ranges from; 1531.47m/s to 1531.60m/s within a minimum cast depth of 0.49m and maximum cast depth of 16.00m. The statistical analysis gives and average error of 2.642cm/m2 which was within acceptable standard as define by the International Hydrographic Organization (IHO).

Waste collection system has become a challenging task, occasioned by the overflowing garbage bins littered all over the environment, causing environmental hazard and further leading to incurable diseases which endanger life. The present-day waste collection system has proven to be inefficient, taking into consideration the advancement in the technologies on the rise in recent years as well as the continuous increase in population growth. As a result of this inefficiency observed, this work developed a model for electronic waste collection system in a telecommunication driven environment. In the system's implementation, PIC18F4620 based instrumentation, integrated with proximity sensor for external monitoring and level sensors for internal monitoring was adopted, while the controlling of the opening and closing of the cabins was implemented using a smart switching board. A remote reporting to the waste management authority so as to systematically plan route-map for garbage collection when the waste cabin is fully filled was done by deploying a 900MHz transmitter interfaced with the system’s controller. The result shows that with this model the waste cabin opens only on account of a user approaching the sensing distance of the system and the cabin is not filled. But when the cabin gets filled and a user approaches the sensing distance of the system, it directs the user to use the nearest waste cabin by displaying a message on the LCD (Liquid Crystal Display), while communicating with relevant authority for the evacuation of the cabin via SMS. It was obviously seen that the automation incorporated into the system had zero impact on the success rate of the system or system availability while introducing a latency of 5.6seconds, which is just 28.0% of the maximum allowable latency of this kind of system, while protecting the environment from environmental pollution and spread of diseases. This work highlights the potentials of (EWCS) Electronic Waste Collection System in monitoring and controlling waste disposal for healthy and clean environment.

Modern organizations leverage highly distributed, global deployments to provide high availability and resiliency for cloud-first applications. By hosting these applications across multiple geographic locations and relying on highly available services, organizations can prevent disruption to their business and reduce complexity by employing the scale of infrastructure offered by major cloud providers. Global deployments in the cloud are built on well-known models such as failover, load balancing, and scalability. However, traditional methods used to recover from regional failure—while effective—can be complex. Typical multi-region recovery and high availability system architectures have latency and cost risks that should be considered when facing other limitations such as deployment models in the cloud. This document describes the different traffic management techniques that can be applied to multi-region strategies, focusing on trade-offs and costs. The introduction of new traffic management techniques being applied to the traditional global architectures now allows organizations to adopt cloud services more efficiently. Traffic management is much more straightforward in some environments, while others have started to leverage their traffic management platform via routing. In multi-region deployments, active-active and active-passive are the most common architectural models, allowing organizations to seamlessly handle failover, scalability, and global distribution based on business goals and requirements. However, traffic management for these infrastructures is critical to ensure just data distribution and efficiency, maintaining costs under control and workloads rerouted when necessary. Using the new traffic management techniques will allow organizations to evolve system architectures easily based on business requirements, taking advantage of cost benefits from multiple infrastructures. In these scenarios, traffic management becomes a crucial backbone of success to ensure that traffic is being efficiently and intelligently distributed [1].

Unfortunately, it is not disaster recovery, high availability, or cloud technologies that are inherently difficult to understand, but rather the action of implementing them for software applications that is difficult. The unique method of implementation for a microservices architecture is explored. Regulatory compliance doesn’t stop just because an effective disaster recovery requirement is tough to satisfy for infrastructure unique to sleek microservices. The high-availability location transparency bliss offered by a cloud solution is appealing to a security engineering department. However, the headache starts when the technology presents a handful of undesirable surprises that leak RESTful microservices to the outside world. These are the challenges that post-SOA cloud-resident robustly scalable applications will need to address and overcome. The goal is to explore several popular methods of accomplishing these tough objectives so that engineers can further research the most practical solution. An innovative implementation that leverages Service Bus relays as an elegant disaster recovery solution while enforcing a strict subnet where RESTful microservices solely live will be discussed. The curiosity lies in the atypical experimentation beyond basic gateways and the facility of using such simplicity while still answering day-to-day software development infrastructure challenges for applications we build. Resilient full-service web proxy service crashes and delivery latency switches by harnessing the microservices pod health will also be discussed [1].