What’UP Damage control
What’UP is an automated self discovering damage control system. The What’UP damage control regulates, processes and analyses the impact of all selected operational functions and assesses any function suffering outages. Based on predefined scenarios What’UP effectively distributes tasks, alarms and warnings. It also controls messages to the responsible staff. Effective business continuity after a disaster is guaranteed with the What’UP messaging system. This is made possible by the automatic replication of the fail-over systems.
Impact scenarios form the basis of the What’UP messaging procedural recovery plans and damage reporting. What’UP stores automatic damage reporting procedures and disturbances in small disaster follow-up procedures (workflow). Small scale problems are parental owners to large disasters.
A typical impact scenario like a (small) fire will most likely encompass some critical operational functions, resulting in the worst potential outcome from such a potential threat. Damage control and procedures to attack such disturbances are critical to ensure proper business operations. What’UP’s extensive inter-operability ensures the communication between different operational systems. The secure fault tolerant and resilient, fail-over operation of What’UP ensures that operational systems are kept up to date to counter any disturbance and/or emergency.
WCMS PBX Application
The WCMS system is built on a Linux CentOS operating system using open source Asterisk software. Asterisk is a feature rich telecommunications platform (PBX), which serves as the basis for an enterprise-grade IP PBX. This platform provides tested reliability of critical functions and features and can be tailored for specific applications. The WCMS system builds on this platform to add naval functions.
Meru Wireless Network
The wireless network is based upon Meru equipment and software. The Meru system consists of a Virtual Controller and Access Points to create a virtualized wireless LAN, which connects the handhelds and other wireless hardware for seamless mobility. The Meru controller will manage the Access Points in such a way that the handheld device will only connect to one virtual Access Point. Normally when a device is out of range of a fixed Access Point, it will need to connect to another Access Point and all connections will need to be restarted during the handover. This takes time and resources and is inconvenient for streaming applications such as a phone conversation. With the Meru Access Point system all connections are moved seamlessly from one Access Point to another in range, meaning that the handheld user will not even realize that the handheld’s association was moved to another Access Point.
End station users such as handhelds, laptops, tablet PC’s and/or other similar devices are able to connect via the Access Points based on 802.11g, 802.11n or 802.11ac. The Meru controller software. It is also possible to create a virtual LAN (VLAN) for data to be exchanged with hardware such as tablets.
The basic function of the Meru controller is a single point of configuration for the entire wireless network. The Access Points are controlled and configured by the Meru Controller. During the session lifetime of a wireless device, the Meru controller will define upon which Access Point the session will exist. The virtual server needs the following minimum specifications: 3 x 3 GHz AMD or Intel x86 quad core processor, 2 GB memory and 2 GB disk space (min 150 IOPS).
The virtual machines come on an external hard drive. After installation the configuration can be imported into the system. The Meru Controller is the heart of the WCMS system and controls every connection to a wireless device on the Ship. The Meru Network solution utilises virtualisation technology to create an intelligent and self-monitoring wireless network. Where normal handover or roaming occurs with wireless communication, the Meru Controller defines when a device is transferred from one Access Point to another without the need for handover or roaming. The Meru Controller executes load balancing. For example: five users are connected to one Access Point and four users are busy on a phone conversation. If user number five then starts a phone call, the Meru Controller can move two users to another Access Point.
The Meru Network provides single channel Wi-Fi architecture. This means that all Access Points (AP) are on the same channel, making Radio Frequency configuration and management easier. Furthermore, since one ‘network’ resides on one channel, you can actually layer multiple channels or networks to improve throughput and capacity, as well as separate applications and/or users on different physical networks/channels. By using this logic the Meru Controller defines when a device is transferred to another AP and not the client, because the client ‘thinks’ that there is only one AP. Since the client only sees one big access point, it will never be triggered to roam. The roaming decision is no longer taken by one component in the network, but by the controller which has the complete overview of the network. Roaming decisions are thus based upon AP load, AP throughput, number of clients, client signal strength, packet error and packet retries. The roaming itself happens in less than 2.5ms, regardless of the type of security used. This means that it is seamless for the client and guarantees overall seamless use over the network of voice, streaming video and real-time data.
The Wireless Communication System is implemented with Wireless Access Points granting access to users the RADIUS protocol (remote user authentication and accounting). A separate virtual port is created for each device on the network. From a system administrator perspective, the Meru Controller is configurable from a single point. Instead of configuring all devices all over the Ship, one configuration is created and all devices are attached to that configuration. The Meru Controller uses the data link Layer 2 to communicate with the devices. No IP addresses are used in this protocol and the Meru AP will sign up with every Meru Controller they find in the network. The Meru Controller will apply RADIUS based MAC filtering, whereby device MAC addresses are set up and managed by a remote RADIUS Server. When a new device attempts to join the network, the Meru Controller queries the RADIUS server with the MAC address to determine whether the client is permitted or not.
There are two MERU Controllers necessary for redundancy and both are hosted in the network. The MERU Controllers will failover if one MERU Controller goes offline or is unusable, ensuring uninterrupted service. The rest of the MERU Controller equipment consists of access points.