INTRODUCTION

The disclosure relates to a modular ship system made for reconfiguration of a ship between different capabilities of the ship to carry out predefined tasks. The modular ship system comprises a computer system, a ship with at least one mission docking position configured to receive a mission module, and at least two different mission modules configured to be received in the at least one mission docking position. Each mission module changes the capability of the ship to carry out the predefined task. The disclosure further relates to a ship for the system, a mission module for the system, a module system of mission modules, and a method of configuring a ship.

BACKGROUND

US 2011/0030603 discloses a reconfigurable ocean-going vessel with mission-configurable spaces for receiving mission modules and thereby adjustable to changing requirements.

The disclosed vessel provides flexibility by allowing the spaces to receive different modules.

Safety in operation is essential for ocean-going vessels, and while configurability is typically desired, it may be difficult to ensure reliability and safety in a plurality of different configurations.

To ensure compliance, safety, and efficient configuration, it is established to adopt a practice generally referred to as "widening". According to this principle, all predefined positions are configured to receive the available modules, and the interaction between the positions and modules is proven to work according to acceptable standards. Modularization is therefore reduced to the task of selecting a module and placing it in one of the predefined positions. While this simplifies modularity and potentially increases safety on ocean-going ship, it also limits the ability to optimize space and capability of the ship since each space must be capable of receiving all available modules.

In practice, it is difficult to dispense from the widening principle due to the complexity of ships. A change between two modules may, inter alia, change various capabilities of the ship and a module may define essential prerequisites. As an example, one module may change 2 the weight distribution and thus stability of the ship, and it may require a specific power supply etc.

SUMMARY

It is an object to increase flexibility relative to modular ocean-going vessels and particularly to allow modularization in a fast and safe manner while the ocean-going vessel is in operation, i.e. away from the shipyard or similar manufacturing facility. It is a further object to allow exchange of modules in an autonomous manner without interaction with external help e.g., from a shipyard or repair yard, or without control e.g., from a classification society or a naval rules administration.

For these and other objects, the disclosure provides a modular ship system, a ship, a set of mission modules and a method of configuring a ship with mission modules pertaining to different operations according to the independent claims and with optional features according to the dependent claims.

The modular ship system comprises a ship having at least one mission docking position. The mission docking position could be a specified area where different mission modules can be received. Particularly the mission docking position may be characterized by having a layout.

A layout implies a specific physical layout and an interface.

A specific physical layout could be a fixture for fixing the mission module and/or a specific size, and/or a specific capability related to carrying weight of the mission module.

The interface could be any means of communication between the mission module and the ship which is possible at the mission docking position, e.g., including available wireless communication and available a socket structure for receiving a plug of the mission module for wired communication etc. :

- The communication between the mission module and the ship may relate to signals and/or supply.

Signal communication may include communication with internal ship systems such as Integrated Platform Management Systems (IPMS) and Combat Management Systems (CMS), and it may include weapon systems data and data for controlling purpose etc.

Supply Communication may relate to power, liquids, air, fuel, and/or waste etc. such items may be exchanged between the mission module and the ship via the interface. 3

Typically, the ship may have a plurality of mission docking positions. The mission docking positions may be identical, or each mission docking position may be different from the other mission docking positions, or they could be groupwise identical to mission docking positions in the same group or have similarities with mission docking positions of the same group but be different from other mission docking positions.

The mission docking positions could be on the upper deck, on a shelter deck, or generally anywhere in the ship where one mission module can be exchanged with another mission module.

The mission modules are configured to be received in at least one of the at least one mission docking position, and optionally, they are configured to be received in several different mission docking positions, e.g., in all available mission docking positions. The mission modules may be identical, or each mission module may be different from the other mission modules, or they could be groupwise identical to mission modules in the same group or have similarities with mission modules of the same group but be different from other mission modules.

The ship has a computer system access to access a computer system. In one example, the ship has an onboard computer system, and in another example, it has remote access to cloud computing or to a dedicated computer of a control station. The computer system has access to a database containingmodule data. The module data of the computer system defines a prerequisite for the module to work and thereby be able to provide the intended contribution to the ship for carrying out at least one of the predefined tasks.

A predefined task for the ship may inter alia be to function as a fishery research ship, and the contribution of one mission module may be to provide laboratory setup for marine mammal analysis. For the mission module to provide a contribution to the fishery research, it may need electrical power and fresh water, which are then prerequisites for the mission module to work.

The database of the computer system comprises position data pertaining to each mission docking position. The position data defines a layout of each mission docking position, inter alia available power, liquids, ventilation resources, waste handling and other features available from each mission docking position. A part of the layout may be the interface between the ship and the mission module. The interfaces may include sockets and plugs, and they may be grouped e.g., in a basic interface to be available at all mission docking positions, and optionally one or more specific interfaces.

Examples of specific interfaces may include: 4

- an energy interface defining connection between the mission module and the ship for exchanging energy, e.g., electrical power, fuel, pressurized air, or gas etc.

- an auxiliary interface defining peripheral necessities, e.g., waste water handling or ventilation etc.,

- a weapon interface defining all signal communication necessary between the ship and the mission module for making a weapon system perform as intended, and

- a sensor interface providing communication between the ship and the mission module related to sensor data, e.g., related to sensors in the mission module or related to sensors onboard the ship.

A sensor may e.g. be a radar system, an electro optic / infrared system, CBRN / gas detectors, hydrophones, sonar systems etc. The sensors are providing e.g., situational awareness, detecting and tracking targets. The sensors are also providing target data for weapon systems.

All sensors are communicting with the ship systems via the sensor interface Such sensors may e.g., provide temperature, humidity, gas-content from a gas detector, position e.g., from GPS or similar nautical instruments, roll and yaw data related to the movement of the ship and mission module in waves, or the sensors may relate to various measurements, e.g., fuel content, electrical measurements, voltage, ampere, etc. or it may include signals from radars etc. All such signals may be communicated between the ship and the mission module through a sensor interface.

The layout may e.g., comprise one or more of the following entities:

- size and/or shape of the surface on which the mission module is received; height option, e.g., free height of a deck or under a roof where the mission module is received ;

- temperature variations at the location where the mission module is received

- interfaces (sockets for water, power, signals, waste handling etc.)

- weight options to be carried by the ship where the mission module is received

The database comprises configuration rules defining configuration of the ship with the mission modules. Configuration rules may e.g., specify how the mission module interacts with other systems of the ship, e.g., with a power supply etc. and it may therefore reveal if sufficient power is available. Examples of interaction could be: 5

- related to fresh or sea water supply, e.g., liters/hour;

- related to signal strength, e.g., of a WIFI signal, or dedicated signals, e.g., for weapons etc.

- related to ventilation, e.g., m ³ /hour.

The computer system has a user interface allowing a user, e.g., personnel on the ship, to select of a mission module and to associate the module data of the module with the position data and/or with the configuration rules, and based thereon to determine compliance between a selected mission module and a selected mission docking position. The computer system may thereby detect if a mission module can be received in a specific mission docking position and can function correctly on the ship.

The compliance may include checking for weight of the mission module and weight limits of the mission docking position, checking for supply compliance relative to liquids such as fuel or water, or supply of ventilation air etc. between the mission module and the mission docking position and thus the ship.

Whereas the position data relates to static features of the mission docking position, including available sockets, dimensions, location of the mission docking position etc., the configuration rules may define dynamic compliance, e.g., related to the presently produced and consumed power on the ship, and compliance may be that there is sufficient power for the considered mission module. Accordingly, the configuration rules may be dynamically updated based on present state of the ship or mission modules onboard the ship.

The database may further comprise capability data. Such capability data defines a capability of the ship to carry out the predefined tasks. Examples of different capabilities include, but are not limited to capability to conduct one or more of the functions listed in below table 1, i.e. to function as a:

- Hospital Detention

- Accommodation

- Office

- Workshop

- Laboratory

- Oil Spill Recovery

- Chemical Spill Recovery Fishery research

- Seismic research

- Secret service intelligence 6

Police force Border Control Riverine warfare

- Amphibious warfare

- ASUW - anti surface warfare

- AAW (point and area defense)

MCM Mine Counter Measures

- ASW - Anti Submarine Warfare Minelaying

- Strike (medium range+ long range)

Humanitarian aid operations

- Special operations Helicopter re-fueling

Mothership for unmanned systems (UAV, AAV, AUS, ROV) table 1: Examples of predefined tasks or functions

Each of these functions may constitute predefined tasks. Some of the tasks could be further defined such as

- Laboratories o specific laboratory setup for oil detection analysis; o specific laboratory setup for marine mammal analysis;

Mine Counter Measures o specific weapon capabilities for subsea activities; o specific weapon capabilities for above water activities etc.;

In addition to the compliance validation, the computer system may be configured to change the database to reflect the change in the capability of the ship to carry out the predefined task which is obtained when the mission module is received at a specific mission docking position. Accordingly, the computer system may be configured to dynamically update the database such that it reflects a current status of the ship.

If compliance is not obtained, e.g., if there is not sufficient power to supply a specific mission module, the computer system may be configured to calculate alternatives and thereby to suggest an action that will make the intended mission module compliant. This may, inter alia, include suggestion to remove another power consuming mission module or a suggestion to add a power contributing mission module, e.g., a mission module containing a diesel driven power generator. Accordingly, the computer system may comprise a calculation module configured to compare at least two variables, one representing a necessary element for the mission module, and the other variable representing an availability of this element on the 7 ship. The calculation module may be configured to handle a third variable representing other entities on the ship consuming the element and to suggest reallocation of the element from one of these consumers to the mission module in question.

The capability data may be defined in the database by connected entities of a ship task table and a ship score table. The ship task table may include said functions of table 1. The ship score table may define how well the ship may potentially carry out each task. The score may e.g., be a number, e.g., from 1 to 5 indicating how well the ship can carry out the task. A score of 1 may indicate that the ship is unable to carry out the task, and a score of 5 may indicate that the ship is fully capable of carrying out the task. Optional intermediate scores between 1 and 5 may each indicate a stepwise improved capability of the ship.

The module data may be defined in the database by connected entities of a contribution table comprising different contributions of the mission module to the ship for carrying out the predefined tasks.

If considering a task to be fishery research, a laboratory facility of a mission module with a laboratory may raise a score for that task from 3 to 4. Accordingly, the module data may also include a contribution score table which for each contribution defines a score by which the value of the contribution can be determined.

The position data may be defined in the database by connected entities of a position table comprising identification of different mission docking positions, and a layout table comprising for each identification, a corresponding layout of the corresponding mission docking position. Examples of such layouts may include plug connections for power, signals, and liquids etc.

The configuration rules defining configuration of the ship with the mission modules may define different relations between the mission module and the ship. The mission module may e.g., be consuming power, which it is expected to receive from the ship, or it may consume fluids such as fuel or water which it is considered to receive from the ship. Such dependencies between the ship and the mission modules are defined by the configuration rules.

Particularly, the database of the computer system may contain a complete library with all available mission modules with the associated module data and with configuration rules for all mission modules. The computer system may be configured for regular updates of the library, e.g., each time new mission modules are defined for the ship. 8

The compliance between a mission module and a mission docking position may be determined by comparing the prerequisite in the prerequisite table with a layout in the layout table and with the configuration rules. Based on this comparison, the computer system may be configured to select at least one contribution from the contribution list.

A mission module may, as an example, contain a fish research laboratory which demands ventilation, water, and electrical power. In this case, the comparison may identify if a layout of a specific mission docking position provides the needed facilities. If that turns out to be the case, the laboratory of the mission module may be selected as a contribution of the mission module for the ship to carry out the task of being a fishery research ship.

Alternatively, i.e. if the comparison identifies that the prerequisite is not available, e.g., if the mission docking position has no water supply or no ventilation, the mission module is not identified to contribute for the ship to carry out the task of being a fishery research ship.

The computer system may subsequently update the score table to thereby indicate the obtained change of the capability of the ship to carry out the predefined task, in this case the task of being a fishery research ship.

The computer system may be configured to communicate data with a data storage placed locally in the mission module. The local data storage may inter alia contain the module data thereby defining the prerequisite and the potential contribution of the mission module to help the ship in accomplishing a specific task.

Once the mission module is placed physically in the mission docking position, these module data from the local data storage of the mission module may be transferred to the computer system. In an opposite direction, the computer system may transfer the position data which identifies the layout of the mission docking position to the local data storage of the mission module. In the mission module, such information about the layout of the mission docking position may be utilized e.g., for internal settings. In the example of a laboratory, the setting may relate to ventilation, water pressure, garbage handling, and other necessary interaction between the laboratory in the mission module and the ship via the mission docking position.

Each mission docking position may comprise a socket structure comprising at least one socket group selected from a predefined set of socket groups and each mission module comprises a plug structure comprising at least one plug group selected from a predefined set of plug groups. In this way each plug group may match a corresponding socket group. The groups may be predefined e.g., for specific purpose. A Group A may e.g., indicate communication of inflammable liquids, Group B may indicate communication of toxic waste water, Group C may indicate communication of electrical power of certain characteristics e.g., 9

230V/440V, AC or DC etc. Group D may indicate communication of pressurized air, Group E may indicate communication of signals by a specific bus-structure, or Internet of things (IOT), e.g., via a ship specific secure 5G network etc., or via a wired communication structure operating in parallel with a wireless secured network.

The socket groups which are included in the socket structure of each mission docking position may define at least a part of the position data for the mission docking position. The mission docking position may e.g., include #Socket, A, D, E indicating that the corresponding socket communication groups are available at the specific mission docking position.

In a corresponding manner, plug groups included in a plug structure of each mission module may define at least a part of the module data for the mission module. The module data may e.g., include #Plug, A, D, E indicating that the corresponding plug communication groups are available on the specific mission module.

Compliance between a selected mission module and a selected mission docking position may be evaluated when the mission module is physically in place in the mission docking position. This compliance may be evaluated by the computer system, e.g., via test communication via the defined socket and plug structure. For that purpose, sensors may be provided at each mission docking position or elsewhere on the ship for testing the communication between the plug structure and the socket structure.

The computer system may comprise a repository identifying an available level of consumables. Consumables in this respect may refer to fuel, oil, or fresh water etc., but may also refer to free space e.g., in wastewater tanks, or chemical waste tanks etc.

The mission modules may be pre-classified as a "providing module" or a "consuming module". This classification may be sub-classified to identify what kind of consumable it provides and how much it provides or consumes respectively.

If the mission module is a providing module, the computer system may update the repository to indicate the increase of the specific consumable achieved when receiving the mission module and if the mission module is a consuming module, the computer system may update the repository to indicate the decrease in the available consumable resulting from receiving the mission module.

Examples of different providing modules include, but are not limited to one or more of the examples in below table 2: 10

- AC module with an AC power supply generator Heli-Fuel module with a fuel tank for Heli-Fuel

- Genset module providing electrical power Flydrogen Fuel cell

- Data and data processing (computer power)

- Hydraulic power pack module with pump capability supply

- Crane providing module capable of supplying lifting capability

- Sewage treatment module supplying sewage treatment capability Fresh water production module for producing freshwater

- Battery Power module supplying electrical storage capability

- Cooling

- Standardized tank module, e.g., supplying storage capability for: o Sewage, o drinking water, o diesel, oil and other fuel or chemicals table 2: Examples of providing modules

A mission module may e.g., comprise a fuel oil consuming electrical generator. That would make the module consuming with respect to fuel oil and providing with respect to electrical power.

Examples of different consuming modules include, but are not limited to one or more of the examples in below table 3:

- weapon systems (consuming data communication capability and electrical power)

- sensor systems (consuming data communication capability and electrical power)

- different kind of modules for missions (typically consuming electrical power, or water etc. table 3: Examples of consuming modules

The computer system may thus update the repository to indicate the consequence on the fuel oil level and power level of the ship. Such data may be communicated to other systems of the ship, inter alia to calculate a new operational range of the ship etc.

A mission module may e.g., comprise heli-fuel for helicopter operation. That would make the module a providing module with respect to heli-fuel. The computer system may thus update the repository to indicate the consequence on the added heli-fuel storage. Such data may be communicated to a flight command system of the ship, inter alia to calculate an expected helicopter operation performance. 11

The module data may define weight of the mission module. Such information may be valuable for the operation of the ship. The computer system may be configured to communicate the weight and a specific location of a mission docking position in which the mission module is located to a stability calculation system. In that way, the ship stability calculations can be updated whenever a new mission module is considered or physically received in a specific mission docking position.

The module data may define an operative component which is associated with the mission module, e.g., a sensor, an actuator, a pump or other equipment in the mission module. This operative component may interact with an external operative component outside the mission module. A temperature sensor in the mission module may e.g., communicate with a fire protection system outside the mission module. A pump in the mission module may communicate with a recipient of a liquid substance outside the mission module etc.

Communication between the operative component in the mission module and operative components outside the mission module may include the use of operative commands. A command may e.g., start a pump in the mission module when a recipient of the liquid in question commands the pumping.

The computer system may be configured to communicate the operative commands with a computer command system of the ship. Examples of such command systems include Integrated Platform Management Systems (IPMS) e.g., for handling ship related processes and Combat Management System (CMS) for handling combat processes and weapon system data etc. Such systems may pass sensor information, e.g., from radars to weapon systems, e.g., for missile launching based on the radar signal etc.

The computer system may also provide data to other computers of the ship, e.g., for calculating stability, magnetic degaussing, and other data needed for optimal operation of the ship.

The module data may define an operative skill level required for personnel to operate the mission module. This may inter alia be a required certificate for handling flammable or toxic liquids, certificates for operating weapon systems, or for using laboratory equipment etc.

The computer system may comprise a predefined skill-level data set representing predefined skills of personnel on the ship. In this case, the computer system may be configured to determine compliance between a mission module and the predefined skill-level data set. This may e.g., indicate that one mission module may physically be received in a specific mission docking position, but there would be no persons available for the operation of the mission module. 12

If non-compliance is determined by the computer system, the system may be configured to determine a reconfiguration of the ship which enables compliance. The computer system may e.g., determine that a specific mission module has an electric power consumption exceeding the available power supply of the ship. In this case, the computer system may identify other power consuming mission modules and suggest these to be either deactivated or removed from the ship. If there is an available mission docking position, the computer system may also suggest adding a mission module with a battery, fuel-cell, or an electrical generator which can supply electrical power to the ship.

Particularly, the reconfiguration may be calculated by the computer system by replacing each mission modules on the ship with other mission modules or by removing mission modules one at a time based e.g., on cause of non-compliance. If the non-compliance is caused by insufficient power supply, the computer system may sort the mission modules based on their ability to provide power or the consumption of power and suggest removal or addition or further mission modules until compliance is achieved.

For this purpose, the computer system may have a ranking of the mission modules identifying the importance of the mission module. The ranking could e.g., be 1-5 where 1 identifies that the mission module is dispensable and 5 indicates that the mission module is indispensable. Such a ranking may facilitate the suggestion of removal of a mission module to make another mission module comply with the ship.

The computer system may be configured to communicate a non-compliance signal when non- compliance is determined. In case of non-compliance, e.g., a temporary issue with lack of electrical power for a short period of time, the computer system may indicate the non- compliance and yet allow the user to deliberately overrule the system and continue with installation and operation of a module.

The computer system may be configured, during operation of the mission module, to continuously or intermittently provide a warning to the user until compliance is established, or the mission module is removed.

If the situation improves during operation of the module, i.e. if missing cooling water, mission power supply, or other prerequisites is established, the mission module status can be updated in the computer system.

One mission module may interact good or less good with another mission module. In one example, a heli-fuel storage tank may, for safety purpose, not be located near a work-shop mission module equipped for welding activities. The computer system may be configured to provide inter-module-compatibility by comparing module data for one mission module with 13 module data of another mission module and by determining compliance between two mission modules based on the comparison. In one example, inter-module-compatibility is a scale, e.g., between 1 and 3 where 1 is no compliance, and five is good match between two mission modules. 1 could be defined as legal issues or regulations preventing both mission modules on the ship on the same time, 2 could be: "restrictions apply", 3 could be: "depends on presence of another module for the two modules to co-exist on the same ship etc.

The ability of the computer system to provide inter-module-compatibility may be based on position data from which the computer system is configured to calculate a distance between two modules. Subsequently, the computer system can determine the compatibility based on the distance. Additionally, or alternatively, the computer system may use position data to determine other kinds of separation between two mission docking positions, e.g. separation by bulkheads etc., and to calculate a separation factor. Subsequently, the computer system may use the separation factor to determine compatibility between two modules when placed in the corresponding mission docking positions.

The computer system may further compare the location of the mission docking positions relative to each other and check for compliance between two mission modules based on a specific location of the two mission modules on the ship.

In a second aspect, a ship is provided for a modular ship system according to the first aspect.

The ship comprises at least one mission docking position configured to receive a mission module having computer system access to a computer system comprising a database containing:

- capability data defining a capability of the ship to carry out the predefined tasks, module data for each mission module, the module data defining a prerequisite for the module to provide a contribution to the ship for carrying out at least one of the predefined tasks,

- position data pertaining to each mission docking position and defining a layout of each mission docking position, and

- configuration rules defining configuration of the ship with the mission modules, wherein the computer system is configured to: 14

- allow a user to select of a mission module and to associate the module data of with the position data and configuration rules and based thereon to determine compliance between a selected mission module and a selected mission docking position, and

- change the capability of the ship to carry out the predefined task based on the selected mission module and the selected mission docking position.

In a third aspect, the disclosure provides a mission module for a modular ship system according to the first aspect. The mission module comprises a data storage defining the module data and thereby enables the mission modules to communicate the module data to the ship and to the computer system when taken onboard.

In a fourth aspect, the disclosure provides a module system of mission modules for a modular ship according to the first aspect of the disclosure.

The module system comprises at least two different mission modules configured to be received in a mission docking position of a ship, wherein each mission module is configured to change a capability of the ship to carry out the predefined tasks, the system further comprising a computer system with a database containing:

- capability data defining a capability of the ship to carry out the predefined tasks, module data for each mission module, the module data defining a prerequisite for the module to provide a contribution to the ship for carrying out at least one of the predefined tasks,

- position data pertaining to each mission docking position and defining a layout of each mission docking position, and

- configuration rules defining configuration of the ship with the mission modules, wherein the computer system is configured to:

- allow a user to: o select a ship o select a mission module and a mission docking position of the selected ship and, o associate the module data of the mission module with the position data of the mission docking position and configuration rules and based thereon to determine compliance between the selected mission module and the selected mission docking position. 15

The computer system main be configured to determine modifications of the modular ship or mission modules on the ship until compliance can be determined, and/or to generate a non- compliance signal if a mission module is placed in, or is considered to be placed in a mission docking position without compliance.

The computer system may be configured to change the capability of the selected ship to carry out the predefined task based on the selected mission module and the selected mission docking position.

The module system may comprise a computer adapter module configured to convert a signal related to the mission module to an intermediate signal format, and to convert a signal from an external administrative data system to the intermediate signal. This may allow communication between different systems, i.e. systems internally on the ship and external systems.

A mission module may, as an example, communicate with an integrated power management system (IPMS) system. The mission module may communicate with the IPMS through an adapter and or a gateway software. The adapter translates signals and protocols between the mission module and various systems of the ship.

As an example, by converting a 24 volt signal to a 0. 1-1.0 volt signal i.e, when the IPMS initiates a certain function in the mission module, it transmits a 0.4 volt signal to the computer adapter. The computer adapter may then utilize the configuration database and thereby knowledge about the mission module in which the function is to be triggered. Therefore, the 0,4 volt signal is converted to a 18 volt signal which is dispatched to the mission module.

In a fifth aspect, the disclosure provides a method of configuring a ship according to the first aspect of the disclosure.

The method comprises:

- providing a computer system with a database comprising: o capability data defining a capability of the ship to carry out the predefined tasks, o module data for each mission module, the module data defining a prerequisite for the module to provide a contribution to the ship for carrying out at least one of the predefined tasks, 16 o position data pertaining to each mission docking position and defining a layout of each mission docking position, and configuration rules defining configuration of the ship with the mission modules,

- selecting a mission docking position of the ship in a computer system;

- selecting a mission module from a library of mission modules in the computer system; and using the computer system for selection of a mission module and a mission docking position, and association of the module data of the mission module with the position data of the mission docking position and based thereon for determining compliance between a selected mission module and the mission docking position.

The computer system may be used for changing the capability of the selected ship to carry out the predefined task based on the selected mission module and the selected mission docking position, and the determined capability of the ship may be communicated with an external computer system not being on the ship. The external computer system may e.g., be a land-based commando system configured to control a plurality of ships in a mutual mission.

The external computer system may e.g., be configured for simulation and onshore mission/taskforce operations planning. In that case, the method may comprise the step of carrying out simulation of use of multiple ships for a common operation based on capabilities received from each ship.

LIST OF DRAWING

Further details will be disclosed with reference to the drawing in which Fig. 1 illustrates a ship system;

Fig. 2 illustrates a mission module;

Fig. 3 illustrates loading of a mission module on a ship;

Fig. 4 illustrates a ship with different mission docking positions;

Fig. 5 illustrates a primary socket for connecting a mission module to a mission docking position;

Figs.6-11 illustrate different socket groups, 17

Fig. 12 illustrates a user interface,

Fig. 13 illustrates schematically configuration between the ship and two mission modules, Fig. 14 illustrates module classification, i.e. groups of modules,

Fig. 15 illustrates mission docking position classification, i.e. groups of mission docking positions, and

Fig. 16 illustrates interaction between the computer system and other computer systems of the ship.

DETAILED DESCRIPTION OF EMBODIMENTS

Fig. 1 illustrates a modular ship system 1 comprising a ship 2, a computer system 3 and a plurality of mission modules 4-8.

The ship comprises mission docking position located at different locations on the ship. Each mission docking position is configured to receive one or more of the mission modules and once a mission module is received and interfaced, the ship achieves a new capability to perform a specific task.

The illustrated ship is a modular mission payload system configurable for multiple roles e.g., as a war vessel or an inspection vessel.

Each mission module is made for a specific purpose and thereby configured to change a capability of the ship to carry out the predefined tasks.

Each module is housed e.g., in a container or fitted with a transport chassis allowing easy allocation of the module. The modules have interfaces towards the ship which allows modularity, e.g., by allowing multiple mission modules to be placed in the same mission docking position. In one example, each module comprises connectors ensuring that the module accurately mates up with connections e.g., for power, ventilation, communications, water, and data.

Different sensor systems or weapon systems may be included in the mission module e.g., enclosed in a container or placed on the roof of the mission module. Machinery, electronics, and supporting equipment could be encapsulated within the mission module. Flowever, some weapon and sensor mission modules are not appropriate to fit into a container and will 18 mounted directly on dedicated seats. Connections to IPMS and CMS will be like the normal procedures for container based mission modules.

The mission modules could be placed in the mission docking positions by use of on-board cranes, e.g., small cranes configured to handle e.g., 15 tons.

A mission module can be placed or replaced within a very short time frame, e.g., less than an hour, and a subsequent testing by the computer system may be completed to verify compliance, including verifying that electrical signals, power, and water etc. is interfaced correctly. The ship can therefore be ready with new capabilities within a short time frame, e.g., within a few hours.

The illustrated computer system is an onboard computer system which is accessible by the local command of the ship, and it is connected to other ship computer systems.

The onboard computer system is linked to an onshore computer system providing the fleet commander an overview of the capability of the entire task force and each of the ships engaged in the operation. The onshore computer system provides a simulation function of the task force's capability with the various use of the available mission modules (e.g., across NATO countries) or is providing the task force commander with an online status of mission modules per ship or the status of the entire task force.

The computer system comprises a user interface allowing a user to communicate a desired mission module and a desired mission docking position. The computer system has access to, or contains a database containing data related to the capability of the ship to carry out the predefined tasks of the ship. These data are referred to as capability data. The capability data may in a simple implementation acknowledge or deny the capability to carry out a certain mission. The ship may either be used for Antisubmarine Warfare (ASW) missions or it may not be used for ASW. In a more advanced implementation, each task is defined not only as a task, but defined based on sub tasks. In this case, the ability to carry out the mission may be defined with a score explaining how well the task can be carried out. The ASW task may e.g., be defined in complexity of the hunt of submarine, e.g., the ability to detect an object with a negligible underwater radiated noise which require a silent ship with low acoustic signature. The score is thus also dependent on a silent propulsion with the use of e.g., fuels cells in mission modules - see the ASW capability score table below:

Score Required mission modules

1 No sonar systems (the basic ship) 19

2 Hull Mounted sonar HMS (HMS mission module mounted)

3 Quite propulsion (Optimized propeller curve for minimal cavitation)

4 Towed array sonar (Combination of HMS and ASW mode propulsion)

5 Silent operation (fully electrical propulsion / fuel cells etc.)

The computer system further comprises information related to each module. Herein, this is referred to as module data. The database may particularly be configured to identify each available mission module, e.g., not only those mission modules being present on the ship but also other mission modules which could potentially be taken onboard. The database may thereby constitute a library of mission modules, and for each mission module, the module data may define the prerequisites, i.e. the conditions which must be available for the mission module to work.

The module data may in a simple implementation provide a list of elements being prerequisite for the module to carry out a task. In case of a diving module, the list could be:

- oil free compressed air (for dive tank filling),

- decompression equipment (for emergency treatment of divers),

- electrical power, 230V ac,

These prerequisites may simply be marked as prerequisites meaning that if they are not available, the diving module is not considered to contribute in diving operations and thereby does not add any tasks capabilities to the ship.

In a more advanced implementation, each prerequisite is defined based on a level of importance.

In this case, the ability of the mission module to contribute depends on a number of prerequisites being available, or each prerequisite may have a level indicator by which the importance is judged.

In the above example, the oil free compressed air for tank filling may be an indispensable prerequisite - no diving can be made without tank filling, whereas the availability of decompression equipment may be dispensable for diving under certain conditions, e.g., for diving down to a certain depth. 20

The position data provides a layout of each mission docking position, and particularly provides availability of sockets are available for communication of signals, power, and water etc. It further provides a capability of the mission docking position to carry weight, shape and area of contact surface between the ship and the mission module, and optionally features e.g., related to fixing of the mission module to the ship etc.

The computer is configured to associate the module data of with the position data and based thereon to determine compliance between a selected mission module and a selected mission docking position.

The module data may be sorted in different data categories, e.g., power, waste, auxiliary. The below tables 4 and 5 illustrate examples of module data and position data and indicates compliance table 4: Example of module data 21 table 5: Example of position data

In the above example, the association of the module data with the position data indicates compliance and the computer system can change the capability of the ship by adding the task of deep-sea diving to the capability data. The Module data includes: Operative skill: diving certificate A+ and Maintenance skill: education level 5.

This defines a predefined operative skill level required for personnel in order operate the mission module. This information is not compared with the position data but can be used, e.g., in combination with a predefined skill-level data set of the ship. Such a skill-level data set may define skills of personnel being presently on the ship.

The computer system may be configured to use the predefined skill-level, e.g., in a subsequent comparison routine in which compliance can be determined between a mission module and the personnel being available. As a result, the ship command may know that the deep-sea diving module 001 can be placed in mission docking position 001, and the maintenance skills are not presently available on the ship.

The weight of 9500 kg. and the location of the mission docking position could be transmitted to computer system configured for stability calculation system. Such a system may instantaneously define the consequence of arranging the specific module on the specific location for ensuring the stability of the ship. In table 5, the position data includes a level of importance. Since, however, the selected mission docking position facilitated all prerequisites, the level of importance is inessential. If the mission docking position did not support the one of the prerequisites, e.g., if the mission docking position did not have supply of fresh water, then the information that the level of importance of 2 for fresh water could be used by the computer system to calculate a score 22 for the task of deep-sea diving, e.g., that it may be possible but not according to the highest obtainable scores.

The database may be a distributed database, e.g., where the mission module identifiers are stored in a centralized database sector which is reachable from many ships. In that way, developers of mission modules may register new mission modules in the centralized database, and the ship may always have access to the latest available library of mission modules with the associated module data.

Fig. 2 illustrates a specific mission module 20 with a diesel driven combustion engine 21 driving a power generator 22. The combustion exhaust must be ventilated via the pipe 23. This mission module is a supplying mission module with respect to electrical power and a consuming mission module with respect to fuel, and a consuming mission module with respect to ventilation resources from the mission docking position. I.e. the mission docking position must be capable of receiving the weight and size of the mission module, and it must be capable of supplying fuel and ventilation, and to receive electrical power.

The mission module comprises an internal computer control unit 24. This unit communicates with the computer system and exchanges operative data. The communication may include the module data and/or the position data. Particularly, the unit may comprise the module data, and it may therefore be able to communicate the prerequisite. Further, the unit or the ship may contain sensors configured to verify the necessary connections between the mission module and the ship.

Fig. 3 illustrates the module 20 ready to be received in mission docking positions 30 on the ship. The mission module 20 is replacing an existing mission module, and the computer system makes the necessary update of the capability data defining the new capability of the ship to carry out tasks.

Fig. 4 illustrates schematically the ship 2, with indicated locations of different mission docking positions. The mission docking positions are grouped in several different groups of positions. These groups could be: sensor positions, energy positions, special mission positions, weapon positions, and underwater mission positions. The below table 6 indicates the position data for different groups. The mission docking position groups could differ related to the physical layout, a layout of the interfaces, and the position on the ship. In one example, one mission docking position group could be named "general", and it may contain all available interfaces and have a size allowing it to receive any of the predefined mission modules. In another example, one mission docking position group could be named "energy", and it may contain interfaces suitable for exchanging energy with the mission module, e.g., an interface for 23 delivering fuel oil and receiving electrical power to a mission module containing a diesel driven power generator.

In Fig. 4, the following positions are indicated:

41: mission position, 42: weapon position, 43: Energy position, 44/45: Multiple purpose positions x and y, 46: UXV position (Unmanned vehicle), 47: Sensor position, 48: example of storage/hospital/laboratory/tank module, 49: Energy supply, e.g., a battery.

In the below table 6, the interface type refers to the interfaces illustrated in Figs. 5-11, and the missions are explained by the predefined tasks of the ship to which the mission module contributes when the prerequisites are available. 24 table 6: Examples of mission docking position groups 25

Fig. 5 illustrates a master socket structure, and Figs. 6-11 illustrates different predefined socket groups for different predefined purpose. Each mission module comprises a plug structure which is complementary to one of the sockets. The socket may be defined in the position data and the plug may be defined in the module data.

Fig. 12 illustrates a user interface 120 of the computer system. The user interface depicts the ship in a viewer field 121. The ship is illustrated with different mission docking positions 122. These mission docking positions can be grouped in different groups of mission docking positions having similarities or being identical. Some are in a group referred to as "general" and has standard interfaces for multiple purpose. Others are in a group referred to as "sensor" and has interfaces configured for interfacing a sensor.

The viewer field 123 allows the user to select a mission module and a mission docking position. This field utilize predefined database entities defining all the available mission modules and all the available mission docking positions and the user may therefore select the desired mission module and mission docking position in a pull-down menu.

The viewer field 123 allows the user to view different entities related to the mission module and the mission docking position.

Fig. 13 illustrates a P8d diagram. In this diagram, the interface between the ship and a mission module is indicated by the interface 130. On the left side of the interface, mission modules 131, 132 are indicated - in this case from two different suppliers. On the right side of the border, internal systems 133 of the ship are indicated. The configuration rules define the connectivity between the ship and the mission module and thereby allows the computer system to determine compliance.

Fig. 14 illustrates module classification, i.e. grouping of mission modules in predefined groups based on overlapping features - e.g., two identical or partly identical mission modules are grouped in the same group. In Fig. 14, group: 1 is Data, 2 is Cooling, 3 is energy, 4 is liquid, 5 is weapon, 6 is UXV and 7 is auxiliary. Group 3 is subdivided into 3.1. storage and 3.2 generation.

Fig. 15 illustrates interface classification and thereby classification of the mission docking positions, i.e. grouping of mission docking positions in predefined groups based on overlapping features - e.g., two identical or partly identical mission docking positions are grouped in the same group. In Fig. 15, group: 1 is basic, 2 is auxiliary, 3 is energy, 4 is weapon. 26

Fig. 16 illustrates relations between the computer system 160 and other computer systems of the ship. Particularly, it illustrates that the computer system manages configuration between the ship and the mission modules by comparing the module data with the position data and the configuration rules. Once compliance between a mission module and a mission docking position is determined, the computer system may provide data e.g., to a combat management system (CMS) 161. The data exchanged with the combat management system could relate to sensors and weapon systems, and the CMS system may manage all combat related processes on board the ship, the computer system may also provide data e.g., to an Integrated Platform Management System (IPMS) 162. The data exchanged with the IPMS could relate to consumer and supplier modules, e.g., related to the availability of electrical power or fuel in view of the received mission modules, and the IPMS may manage all ship related (non-combat) processes on board the ship.