Research on Maritime Operations Scheme Making Model Based On Collaboration

With the purpose to improve the ability of collaborative command of maritime, based on systematically analyzing the ways of collaboration to make operations scheme, operations scheme collaboration domain (OSCD) is designed, and relations of its inner elements are analyzed, based on which operations scheme collaboration model (OSCM) is constituted, which will provide foundational underprop for demonstrating and developing intending maritime command and control system.


Introduction
With the development of military information construction, the interconnection and interoperability of marine operations will be greatly enhanced, and the marine information network will provide a good support for system-based advantage. Based on architecture of marine command system in future, a unified decision-making space (UDS) will be gradually established. UDS is a system, which can support the multi command level and the multi operations commanders' integrative collaborative command. In UDS, commanders can share and exchange data, information, knowledge and ideas, and can closely coordinate. Operations scheme is the intuitive result of command of maritime, and is the basis of operations. It is a crucial problem how to make use of UDS to generate the operations scheme in the way of distributed collaboration, so it is necessary to build the collaboration model of generating the marine operations scheme.

Operations scheme generation method
According to whether the operations scheme is broken down in the making process, the collaboration mode of operations scheme generation can be divided into two types.

Unified collaboration
In this mode, operations scheme will not be divided into sections and highly coordination is emphasized. When the commanders are concentrated together, they communicate face to face and formulate the operations scheme with the same interface [1]. When they are in different places, the commanders interact through support terminals and make a unified operations scheme on their support terminals (distributed unified collaboration). In this mode, real-time collaboration will be supported, and all the related factors of operations scheme will be analyzed clearly. But the participants must have global understanding of the operations scheme. It is difficult to realize this collaboration mode

Division of labor and coordination
In this mode, operations scheme will be divided into sections and coordination basing on division of labor is emphasized. First, we divide the task of formulating operations scheme from top to bottom (Top-Down) into sub tasks of formulating operations scheme, and then integrate the sub schemes from bottom to top (Bottom-Up). The collaborators focus on the tasks that they undertake. The sub schemes can be integrated after being completed. The sub schemes can also be integrated periodically or in real time during the formulation of the scheme. This way decomposes complex problems, which is conducive to the simplification of problems. However, when integrating the sub schemes, conflicts may arise and the coordination will be difficult.
In marine operations, command nodes and decision units at all levels have the characteristics of distribution, the command and decision organization has the characteristics of hierarchical structure, and there is a functional division among commanders at all levels. Therefore, the mode of division of labor and cooperation is gonging to be used to formulate the operations scheme [2].

Construction of operations scheme collaboration domain
For a command level in a command decision organization, the commander in charge of making the scheme can divide it into sub schemes and assign the sub schemes to the subordinate commanders to formulate. Thus a relatively autonomous cooperative group is formed.

Operations scheme collaboration domain
The operations scheme collaboration domain (OSCD) is defined as a relatively autonomous collaborative component formed to generate a certain operations scheme in Collaboration with the support of UDS. The architecture model of OSCD, as shown in Figure 1, can be expressed as OSCD= (ID, Cmder, OST, SurSys, Res) Where: ID is the only identification of the OSCD; Cmder is the finite set of collaborative subjects who will formulate the operations scheme; OST is the task to formulate the operations scheme; SurSys is the finite set of the support systems in OSCD; Res is a limited set of combat resources such as warships, submarines, and so on.

Collaborative subject.
A collaborative subject can be expressed as. Cmder= (ID, rank, fun, role) Where: ID represents the unique identity of the collaborative subject; rank represents the grade of the collaborative subject; fun represents the function of the collaborative subject; role represents the role of the collaboration subject in the OSCD, role  {FResp, PResp}. FResp, as a global responsibility role, takes full responsibility for the generation of operations schemes (parent schemes) in the OSCD, and has the right to divide the operations scheme into sub schemes and assign them down; PResp, as a global responsibility role, is responsible for generating the sub scheme. The collaborative subject carrying the global responsibility role is called the full responsibility subject, and the collaborative subject carrying part of the responsibility role is called the sub responsibility subject.
3.1.2 Support system. The support system can be expressed as. SurSys= {SurSchSys, ArgSys, Tools} Where: ArgSys represents a support system for consultation; Tools represents a set of auxiliary tools; SurSchSys represents a distributed collaborative system for generating operations schemes, which includes two types of cooperative nodes and integrated nodes in OSCD. The cooperative node is mainly used to assist the sub responsibility subject to formulate sub schemes. The integrated node is mainly used to assist the full responsibility subject to combine the sub schemes to the parent scheme, and to check and coordinate the conflicts among the sub schemes.

Operations scheme task. The operations scheme task can be expressed as. OST=OpeSchf= (OpeSchz, DFacet)
Where: OpeSchf represents the parent scheme, that is, the operations scheme to be generated in the } represents the set of sub schemes; and DFacet represents the dividing facet used to divide the combat scheme into sub schemes.

The dividing principles
Principle 1 (matching principle): the division of the operations scheme should be matched with the organization structure of the command group and the structure of support system for formulating the operations scheme. Each sub scheme can be allocated to a commander with relevant obligation, and there is a cooperative node to assist the commander. Let OpeSch zi be a sub scheme, cmder j is a commander with relevant obligation, and the relationship between sub scheme and commander is OpeSch zi →cmder j .
Principle 2 (complete principle): the division of the operations scheme plan must be complete, that is, the set of sub schemes can be integrated into a complete parent scheme. Let OpeSch f be a parent scheme whose sub schemes set is {OpeSch z1 ，OpeSch z2 ，…，OpeSch zm }, the completeness of the division of scheme is as follows: OpeSch f =OpeSch z1 ∪OpeSch z2 ∪…∪Principle 3 (independent principle): after the parent scheme is divided into sub schemes, the sub schemes should be independent, that is, the boundary between the sub schemes is clear, and the content of the scheme does not overlap. Let OpeSch zi and OpeSch zj be the sub schemes that belong to the same parent scheme, and j i  , the independence between two sub schemes is as follows: OpeSch zi ∩OpeSch zj =  .

The dividing facets
The division of the operations scheme is the premise that can use the division of labor and coordination to generate the operations scheme. Therefore, many dividing facets are defined as the dividing basis of the operations scheme, and each dividing facet represents a dividing method. Operations facet: according to aspects of operations such as anti-air operation, anti-ship operation and anti-submarine operation, the operations scheme is divided into sub scheme of anti-air operation, sub scheme of anti-ship operation, sub scheme of anti-submarine operation, and so on.
Arms facet: according to the mission tasks, the operational methods and the characteristics of the surface warships, submarines and air forces, the operations scheme is divided into the sub schemes of the surface warships, submarines and air forces. Group facet: the combination of different combat forces is a task group. According to different task groups, the operations scheme is divided into sub schemes of the task groups. Unit facet: according to the different units used, the operations scheme is divided into sub schemes of units.
Target Facet: the forces that strike the same target or many targets in the same area are regarded as a whole, and the operations scheme is divided according to the different targets to be stricken. Space Facet: the forces in the same region are regarded as a whole, and the operations scheme is divided according to the different regions.
Time facets: the operations scheme is divided according to the stage of the operational process. For example, the operations scheme of surface warships attacking ships with missiles can be divided into sub schemes, such as navigation, expansion, attack and withdrawal.
Space-time / time-space facet: mainly embodies the characteristics of the echelon of operational forces, and the operations scheme is divided according to different echelons.
Operational method facet: according to the different methods of operations or different weapons used to divide the operations scheme, for example, the anti-submarine scheme can be divided into torpedo attack scheme and navigation evasion scheme.
In summary, according to the characteristics of the operational task, the granularity and characteristics of the parent scheme and dividing principles, suitable dividing facet should be choose to divide the operations scheme.

Combat resources. [Combat resources]
Res= {OU 1 ，OU 2 ，…，OU n } Combat resources are the set of operational units available in OSCD, and OU represents a operational unit.
OU= (Name, ID, Cap, Sta, Rst) Where: Name represents the name of the operational unit; ID represents the unique identification of the operational unit; Cap represents the ability attribute set of the operational unit, mainly including operational capability, combat object, combat range, endurance, maneuver speed, stealth property, communication capability, etc., and Sta shows the state attributes of the operational unit, mainly including platform damage state, weapon state, position state, task state and so on. Rst represents the use constraint of the operational unit, which mainly describes in what circumstances the operational unit should be used in priority or should not be used. Figure. 2 Internal relations of the OSCD As a whole, the OSCD has a hierarchical structure. The layer of collaborative subjects generates the operations scheme through the support system layer, that is, the use of combat resources is planned. The relationships among key elements within the OSCD are shown in Figure 2. Where: AOSCD represents the finite set of OSCDs; Rel represents the finite set of the collaboration relationship.

Collaboration relation
Collaboration relation can be expressed as Rel= (Relv, Relh) Where: Relv represents the vertical collaboration relations, which are the relations between the upper level OSCD and the lower level OSCD, such as assignment and control; Relh represents the horizontal collaboration relations, which are the relations between the OSCDs of the same layer scheme, such as negotiation and collaboration. They are not only related to each other, but also have certain independence.

Affiliation relation
≤ represents the binary affiliation relation between OSCDs, ≤  AOSCD  AOSCD, which has characteristics of reflexivity, transitivity and boundness. Reflexivity: < represents the strict binary affiliation relation between OSCDs: OSCD i , OSCD j  AOSCD,  Represents the direct binary affiliation relation between OSCDs:

Equal cooperation relation
   Represents the binary equal cooperation relation between OSCDs, which has characteristics of reflexivity, transitivity, boundness and symmetry. Symmetry:  Represents the strict binary equal cooperation relation between OSCDs:  OSCD i ,  Represents the direct binary equal cooperation relation between OSCDs: OSCD i , OSCD j , Based on the above two binary relations, the vertical collaboration and horizontal collaboration can be expressed as:

Assignment relation
Let ACmder is the finite set of the commanders who participate in the formation of the operations scheme, and AOpeSch is the finite set of the sub schemes which the operations scheme is divided into.
Commander hierarchy relation: CH  ACmder  ACmder,〈cmder i , cmder j 〉  CH represents that cmder i is the superior cmder j ，cmder i can assign scheme task to cmder j . Scheme hierarchy relation: SH  AOpeSch  AOpeSch, 〈OpeSch i ，OpeSch j 〉 SH represents that OpeSch i is the parent scheme of OpeSch j , and there is a containing relation between them.
Scheme charge relation: SC  ACmder  AOpeSch, 〈 cmder i ， OpeSch i 〉  SC represents that collaborative subject cmder i is responsible for generating operations scheme OpeSch i ; SC  AOSCD  AOpeSch, 〈OSCD i ，OpeSch i 〉  SC represents that OSCD i is responsible for generating operations scheme OpeSch i . OpeSch i is the operations scheme that the full responsibility subject is responsible for, namely, the operaton scheme task OST i of the OSCD i . The assignment relation can be expressed as AR= (SAR, RAR) Where: SAR represents the task assignment relations among OSCDs; RAR represents the resource allocation relations among OSCDs.
This indicates that OSCD i assigns the task of formulating sub scheme OpeSch j to OSCD j , and limits the OSCD j assignment depth Dep j to the subprogram. The assignment depth Dep j represents the number of layers that can be assigned down. Dep j =0 indicates that it cannot be assigned down anymore. The default value indicates that there is no restriction. If the upper OSCD i is limited to Dep i , the Dep j of lower OSCD j should be less than Dep i -1, which is Dep j Dep i -1.
This indicates that OSCD i limits the range of combat resources that OSCD j can choose during formulating OpeSch j .
The principle of assignment relations among collaborative subjects is the same as above. In addition to the limitation of assignment depth, the assignment of operations scheme tasks should be limited to the following rules, (1) If the operations scheme can be formulated independently in an OSCD, that is, the sub responsibility subjects of the OSCD can generate the sub schemes independently and conveniently, and they do not need to be divided and assigned.
(2) If the sub responsibility subjects of the OSCD cannot formulate the sub schemes independently, the sub schemes should be further divided into lower sub schemes, and new OSCDs in lower layer should be organized. The lower sub schemes should be assigned to the new OSCDs in lower layer. The sub responsibility subjects will become the full responsibility subjects of the new OSCDs in lower layer.
(3) If the new OSCDs in lower layer can formulate the lower sub schemes independently, the lower sub schemes do not need to be divided and assigned. Otherwise, they need to be divided and assigned by hierarchical recursion.

Structure of OSCM
The structure of OSCM is based on OSCD as the basic component, and the top layer OSCD of the marine operations as the beginning point. According to the collaboration relation and the assignment relation, the hierarchical recursive extension is made, and the network nested model structure, as shown in Figure 3, is formed. In the structure, there is a dynamic clientage between collaboration subjects, which is adaptable; the division of the operations scheme is driven by the actual demand, which is flexible; the formulation of the operations scheme is supported by the support system of UDS, which is very efficient; the combat resources cover all the units involved in the marine operations, which are shared well. The impact of dynamic change of combat resources is generated from bottom to top according to the level of OSCDs, which can respond as soon as possible and weaken the interference of global collaboration.

Conclusion
The naval equipment informatization and integration is to provide strong information assurance for maritime operations and form information superiority. However, in the process of maritime operations, it is essential to transform information superiority into decision-making superiority, and then form striking superiority. The cooperation of combat helps to generate striking superiority, while the cooperation of the combat needs to rely on the collaboration of decision-making. The key part is to formulate a "high coordinated decision plan" in a collaborative way. In view of this, based on division of labor and coordination, the article focuses on collaboration method of formulation of marine operations scheme, and establishes a collaboration model. The model is scalable, adaptable, efficient and easy to share, which can provide a basic support for the argumentation and development of command system of maritime operations in future.