A Capability-Driven Dynamic Federal Collaborative ... - ScienceDirect

Available online at www.sciencedirect.com

ScienceDirect Procedia CIRP 60 (2017) 314 – 319

27th CIRP Design 2017

A Capability-Driven Dynamic Federal Collaborative Design Methodology to Support the Inter-enterprise Development of Ordnance Equipment Jun Jia, Wenjun Liub, Jianxin Yanga, Lindong Zhanga,Wei Weic*

b

a Information Center of China North Industries Group Corporation, Beijing 100089, China School of Computer Science & Technology,Beijing Institute of Technology, Beijing 100081, China c School of Mechanical Engineering and Automation, Beihang University, Beijing 100191, China

* Corresponding author. Tel.: +86-010-68961986; fax: +86-010-68963650. E-mail address: [email protected], [email protected]

Abstract Facing the challenge of rapid response to customer personalized demand and developing high quality competitive ordnance equipment, the paper proposes a capability-driven dynamic federal collaborative design methodology to support inter-enterprise development. The core is dynamic constructing collaborative development capability federation (CDCF) by combinatorial optimizing and intelligent disposing various inter-enterprise designing and manufacturing capability. The paper presents the business model and capability models of CDCF and focuses on the capability constraints-based constructing method and requirement-capability matching algorithm of CDCF. Applying service-oriented architecture (SOA)-based integrating method, the inter-enterprise federal collaborative development platform was constructed. Finally, a heavy military vehicle inter-enterprise collaborative design engineering application case validates the effectiveness and feasibility of the method. © Published by Elsevier B.V. B.V. This is an open access article under the CC BY-NC-ND license ©2017 2017The TheAuthors. Authors. Published by Elsevier (http://creativecommons.org/licenses/by-nc-nd/4.0/). Peer-review under responsibility of the scientific committee of the 27th CIRP Design Conference. Peer-review under responsibility of the scientific committee of the 27th CIRP Design Conference Keywords: Inter-enterprise Collaborative Development; Capability-Driven Dynamic Federal Collaborative Design; Collaborative Development Capability Federation; Requirement-Capability Matching Algorithm; Ordnance Equipment

1. Introduction Ordnance equipment, represented by main battle tank, is the strategically foundation of national security. Ordnance equipment development is a highly integrated systematic project and directly reflects comprehensive national strength and scientific might. Facing increasingly intense equipment market competition, current development pattern is difficult to meet the ever-quickening urgent requirements from updating and upgrading of equipment. So, it is an inevitable choice for defense enterprises to applying inter-enterprise collaborative development and building collaborative environment to rapid manufacturing series equipment for various customers. Collaboration thought comes from Synergetics Theory, was built by Hermann Haken [1]. After introduced to product development domain, collaboration thought derives collaborative development pattern and methodology. The

product development pattern has undergone the transform from Sequential Engineering to Concurrent Engineering, and is developing to Collaborative Engineering [2]. With the rapid developing of collaborative technology, collaborative organization has experienced the evolution form Integrated Product Team [3] to Virtual Enterprise [4], and to Collaborative Networks [5]. The widely used of collaborative development technology in defense enterprises promote the profound transform of ordnance equipment developing and producing pattern. Most of the lager defense enterprises, such as Lockheed Martin, Boeing and Airbus, had established global virtual enterprise and constructed web-based collaborative environment, and improved substantially on development capability and the historic breakthrough of development pattern [6-8]. China North Industries Group Corporation has also applied dynamic federal collaboration to realize ordnance equipment inter-enterprise collaborative

2212-8271 © 2017 The Authors. Published by Elsevier B.V. This is an open access article under the CC BY-NC-ND license (http://creativecommons.org/licenses/by-nc-nd/4.0/). Peer-review under responsibility of the scientific committee of the 27th CIRP Design Conference doi:10.1016/j.procir.2017.01.011

315

Jun Ji et al. / Procedia CIRP 60 (2017) 314 – 319

2. Capability-Driven Ordnance Equipment Dynamic Federal Collaborative Design 2.1. Dynamic Federal Collaborative Development Ordnance equipment development is a cross-regional, inter-enterprise and inter-organizational collaborative process. According to the essential features of ordnance equipment developing process, such as various product categories, distributed research organizations, multi-project concurrent development, complicated cooperative relationships and independent design and manufacturing system, dynamic federal collaborative development methodology are usually applied in ordnance equipment developing process [10]. Dynamic federal collaborative development supports multiproject type-product concurrent development by dynamic organizing the collaborative development team and rapid building federal collaborative development environment. The core is constructing the collaborative development federation based on the development requirements, forming development team and allocating development resources dynamically, and building the federal development platform. The dynamic federal collaborative development is an effective method to integrating and optimal disposing various inter-enterprise designing and manufacturing resources. 2.2. Principle of Capability-Driven Ordnance Equipment Dynamic Federal Collaborative Design With the continuous development of battlefields form in the future, product complexity of ordnance equipment will improve constantly. So any individual enterprise cannot complete the ordnance equipment development by oneself. The inter-enterprise collaborative design is absolutely necessary. The key is how to effective gathering and allocating inter-enterprise design resource. The traditional

methods put design resource in the most important place and ignore the essential elements of collaboration -“design capability”. It is difficult to realize the optimal allocating of inter-enterprise design capability. The collaborative efficiency is limited. Considering the importance of design capability, capability-driven ordnance equipment dynamic federal collaborative design method is proposed and shown in Fig. 1. Top-Level Collaborative Development and Multi-Project Control of Ordnance Equipment

The Total Design Tasks of Project A

The Total Design Tasks of Project B

Task Decomposing

Task Decomposing

Design Task 1

Design Task Ċ

Design Task N

Design Task 1

Design Task Ċ

Design Task N

Design Capability Requirement 1

Design Capability Requirement Ċ

Design Capability Requirement N


Design Capability Requirement Ċ


Capability Matching

Capability Pool

development [9]. The key to ordnance equipment collaborative development is constructing appropriate collaborative organization and collaborative environment to realize optimal allocation of developing resources. Design always remains topmost priority in ordnance equipment life cycle. So the collaborative design is one of the most important collaborative businesses in collaborative development process. Aimed at the combinatorial optimizing and intelligent disposing of various design capabilities in ordnance equipment inter-enterprise collaborative design process, the paper proposes the capability-driven dynamic federal collaborative design methodology and aims to solve three critical questions: (1) What is CDCF? For this question, the paper prescribes the business model and capability models of CDCF (see Section 3). (2) How to build CDCF? So the paper presents the capability constraints-based constructing method and collaborative developing capability intelligent disposing algorithm of CDCF (see Section 4). (3) How to realize dynamic federal collaborative design? For this question, the dynamic federal collaborative design platform was constructed to verify and realize the heavy military vehicle inter-enterprise collaborative design engineering application (see Section 5).

Design Capability 1

Capability Unit A

Capability Unit B

Capability Matching

Design Capability 2

Capability Unit C

Design Capability 3

Capability Unit D

Collaborative Development Capability Federation of Project A

Capability Unit E

Design Capability Ċ

Capability Unit F

Design Capability N

Capability Unit Ċ

Capability Unit N

Collaborative Development Capability Federation of Project B

Fig. 1. Capability-Driven Ordnance Equipment Dynamic Federal Collaborative Design Method

The capability-driven ordnance equipment dynamic federal collaborative design applies combination optimization and intelligent matching of inter-enterprise design capability in the capability pool to construct CDCF and effective guarantee various design capability collaborative work. There are three important matter of concern. Firstly, CDCF is a kind of collaborative organization and dynamic formed by a series of capability units, which can realize the inter-enterprise collaborative development of ordnance equipment. CDCF supports geographically distributed multi-enterprise collaborative design executing, collaborative flow controlling and product data sharing. Secondly, capability requirementsdriven means capability requirements are the link between design tasks and design capabilities, and collaborative design process is a continual realization of capability requirements. So driving collaborative process with capability requirements is very useful to realize the dynamic balance and collaborative deployment of the inter-enterprise design resources. Finally, capability pool is a set, includes all of the inter-enterprise developing capability. By capability extracting and polymerizing from whole capability units, the capability pool is formed. Capability pool is the base of constructing CDCF. 3. Collaborative Development Capability Federation of Ordnance Equipment Modelling Method 3.1. Business Model of CDCF The chief issue of applying the capability-driven federal collaborative design is constructing the CDCF. According to the ordnance equipment development characterises and interenterprise collaborative design business requirements, the business model of CDCF is presented and shown in Fig. 2.

316


CI=൛ID,CType ,CFun ,CPerform ,CState ,CAttr ,COrgTyp ,CMemTyp ൟ

Capability Unit P

M

O

bil ity U

M

pa

Collaborative Services

General Unit of CDCF

S

M

bil ity U

O

nit

Ca

P

W

b pa

pa

M

O

Ca

Collaborative Flow

P

Organization W Roles

S

nit yU W ilit

P Product Data M Management Data O

P

M

O

Capability Unit

Fig. 2. The Business Model of CDCF

CDCF is formed by general unit, capability units and federal collaborative environment and presented as follows: CDCF=ሼID,FGU,FCU,FCEሽ

(2)

Where, ID is unique identification of capability instance. CType means classes of capability instance and includes design capability, simulation capability, manufacturing capability, test capability, knowledge capability and other developing capabilities. CFunc means the functional information of capability instance. CPerform means performance information of capability instance and describes the executing time, cost, reliability, security and other performance information. CState means status information of capability instance, there are just occupy and free two kinds of status information, that is, CState =ሼfull,freeሽ . COrgTyp means the capability belonging capability units and describes organization administrative relationship. CMemTyp means capability performance type. Capability Instance Combination is represented as CIሺIset ሻ=CIሺI1 ሻ×CIሺI2 ሻ×‫×ڮ‬CIሺIm ሻ,m>1 . Where CIሺIset ሻ is the new combined capability instance and CIሺIm ሻ is individual capability instance.

Integrated Services

Dynamic Federal Collaborative Environment for Ordnance Equipment

P

Ca

S

W

it Un ity O bil pa Ca P M

nit

S

O

(1)

Where, ID is the unique identification of CDCF. FGU, FCU and FCE respectively denote general unit, capability units, and dynamic federal collaborative environment of CDCF. Generally, a CDCF have one general unit and one or more capability units, FCU=൛fcu1 , fcu2 , ‫ڮ‬, fcui , ‫ڮ‬, fcun ൟ. ݂ܿ‫ݑ‬௜ means one of the capability units. 3.2. Capability Models of CDCF

4.1. Developing Capability Matching of CDCF The precondition of realizing capability-driven dynamic federal collaborative design is constructing an appropriate CDCF, and the essence is find out the accurate design capabilities from unified capability pool to respond design requirements. The core of constructing CDCF is applying constraint-based and adaptive capability matching method to allocate the optimal design capability. The process of constructing the CDCF is matching the optimal design capability instance to corresponding design requirements from capability pool [11]. The CDCF developing capability matching process is shown in Fig. 3. The relationship between capability requirement and capability instance is built by capability model. In interenterprise collaborative design process, developing capability matching is design requirement-design capability matching. The Total Design Capability Requirements of Ordnance Equipment Task Decomposing Design Task 1

Design Task 2

Design Task …

Design Task N



Design Capability Requirement …


Capability Matching Capability Pool

CDCF comes from the extracting, matching and scheduling of series developing capabilities form capability pool and some capability models of CDCF are defined as follows. Capability Extract Model of CDCF, means the capability extracting from general unit and capability units. It denote as CapExSetሺCIሻ=fext ሺfederationሻ. CI is capability instance set. Capability Pool Model of CDCF, means a pubic capability set and all of its capabilities are extracted from capability units. The capability pool is denoted as CapPoolؔሼCI,RelሺCIሻሽ . Where, RelሺCIሻ=CI×CI, represents the relationship set among the capabilities. There are two kinds of capability relationship, the one is administrative relationship, and another is compatibility relationship. Administrative Relationship Model of CapabilityCapability. When SubC൫CIik ,CIjt ൯=൛CIik ęCapPool,CIjt ęCapPool,CIj ęCIik ൟ, CIik and CIjt have administrative relationship. CIik is the upper level capability of CIjt , and CIjt is attached to CIik . Compatibility Relationship Model of CapabilityCapability. When CapR൫CIik ,CIjt ൯=൛CIik ∩CIjt ് ʣൟ, CIik and CIjt have compatibility relationship. Capability Instance, means actually and abstract existing objects of developing capability. It is represented as follows:

4. Capability Constraint-Based Collaborative Development Capability Federation Constructing Method

Design RequirementDesign Capability Matching Rules

Design Capability 1

Design RequirementDesign Capability Matching Model

Design Capability 2

Design RequirementDesign Capability Matching Algorithm

Design Capability …

Design Capability N

Constructing of CDCF

Capability Unit A

Capability Unit B

Capability Unit C

Capability Unit …

Capability Unit N

CDCF of Ordnance Equipment

Fig. 3. CDCF Developing Capability Matching Process

317


4.2. Design Requirement-Design Capability Matching Rules The design requirement and design capability matching process must follow matching rules, represented as follows: SelCapሾkሿ=First൛SortByRul൫ci1 ,ci2 ,…,cii ,…,cin ൯ൟ ,cii ęCap (3) k

Where, SelCapሾkሿ is the set of selected capability instances. k denotes the quantity of selected capability instances. SortByRul() represents sort algorithm function of certain rulebased capability instances. There are five design requirementdesign capability rules. (1) Local-Preference matching rule. if cii .AttrሾLocationሿ=nc.AttrሾRole.Orgሿ then cii .Selected( ) . When the capability instance and task node have the same organization, this rule will take effect. (2) Cost-minimization matching rule. if cii =MinCostሺCapሻ then cii .Selected( ) . When capability instance cost is the minimal in the set, this rule will take effect. (3) Quality-Optimal matching rule. if cii =BestQualityሺCapሻ then cii .Selected( ) . When the capability instance applying quality is the best in the set, this rule will take effect. (4)Most Efficient-Shortest Cycle matching rule. if cii =MinTimeሺCapሻ then cii .Selected( ) . When the capability instance executing time is the shortest in the set, this rule will take effect. (5)Service-Optimal matching rule. if cii =BestServiceሺCapሻ then cii .Selected( ) . When the capability instance resource supporting service is the optimal in the set, this rule will take effect. The priority of these rules is sorted as: (1)> (2) > (3) > (4) > (5). Satisfying any preferential conditions, capability instance will be more confirm the design requirements. If more than one capability instances have same upper priority, further compare will be done at lower priority continuously. 4.3. Design Requirement-Design Capability Matching Model Design requirement-design capability matching model of CDCF is represented as a two-tuples: OTS=൛Ai ,Capi ൟ

(3)

Where, Ai is capability requirements of executory task. Capi is capability instance. OTS is index criterion. There are four types of OTS. (1) Benefit-type, bigger is better, such as operating speed. (2) Cost-type, smaller is better, such as executing time or developing cost. (3) Fixed value-type, the closer to a fixed value is better. (4) Interval-type, the result should in a limited range. And the matching results are divided into three situations and described as follows. For ‫׊‬aęC: (1)Exact Matching. If ‫׌‬cii ęCIPool , cii includes the requirements of a, then, that is exact matching and denotes as Eሺaሻ. (2)Weak Matching. If ‫׌‬cii ęCIPool,cii includes the subrequirements of a, then, that is weak matching and denotes as Wሺaሻ.

(3)Not

Matching.

If

‫׌‬cii ቀcii ęCIPool‫ٿ‬൫b=Eሺaሻ ‫ש‬

b=Wሺaሻ൯ቁ , then, cii and a are not matching, that denotes as Nሺaሻ. Both Eሺaሻ and Wሺaሻ are unified denotes as Mሺaሻ and means find out the matching capability instance. Note, once the task node matching result appears weak matching, decomposing this task node to get the more detailed task node. And then executing the matching calculation again to adjust and optimize the matching result. 4.4. Capability Constraint-Based Design Requirement-Design Capability Matching Algorithm The constructing process of CDCF is the capability constraint-based developing capability matching process. In order to realize capability matching, the concept similarity is introduced to represent the similarity degree of between the capability requirements and capability instances [12]. The concept similarity calculation is represented as follows: ‫ۓ‬ ۖ

0

1 1+Dis൫c1 ,c2 ൯ ܵ݅݉ሺc1 ,c2ሻ= 1 ‫۔‬ ۖ1+δ×Dis൫c1,c2൯

‫ە‬

1

c1 and c2 are not inheritance relationship. The level of c1 is lower than c2 . The level of c1 is higer than c2 . c1 and c2 are same concept.

(4)

Where, c1 and c2 are concepts. δ is customized parameter, value is 1≤δ≤2. The value scope decides semantic similarity degree. Disሺc1 ,c2 ሻ is the concept semantic distance, that is: Ͳ c1 and c2are same concept. ‫ݏ݅ܦ‬ሺc1 ,c2 ሻ= ቐLen× σ Wሺnሻ c1 and c2 are inheritance relationship. ∞ c1 is irrelevant to c2 .

(5)

Where, Len means the path length between c1 and c2 . Wሺnሻ is the path weight value and represented as follows: Wሺnሻ=

1 2n-1

(6)

Where, n means layers number of capability semantic tree. The design task-design capability matching algorithm of CDCF has four sections. Section 1. CType െ CState Matching. It is capability type and status information matching. It used to filter out the irrelevant capabilities and improve matching efficiency. Inputs. Ci Ǥ CType , ߝi and N . For the design task node C , Ci Ǥ CType means type information of the design task node, ߝi means setting type matched-degree, the initial vale is i=1. N is the quantity of capability instances in capability pool. Outputs. CISi and d . CISi means the matched capability set that is the set of extracted capability instances from capability pool. d means corresponding matched-degree set. Steps. Step1. If CPool≠Φ, CI ‫ א‬CPool, calculating the capability type matching of C.CType CI .CType and CI .CType , that is di =Sim൫C.CType ,CIj .CType ൯. If di ൐ ߝi and CIj .CSta =free, then CIS1 =൛CIj ൟĤCIS1 , d=ሼdi ሽĤd.

318


Step2. jൌ൅ͳ, if j൏, then go to Step 1, else go to Step 3. Step3. End. Returning CIS1 and d=ሼd1 ,d2 ,…,dN2 ሽ. Section 2. CFunc Matching. It is the matching of capability inputs and outputs. Inputs. CIS1 , d=ሼd1 ,d2 ,…,dN2 ሽ , ߝiȀ , w, o and p. Where, ߝiȀ is the set threshold value of input-output matching. W is the node sequence number of capability instances in CIS1 , that is, ˄w=1,2,‫ڮ‬,k˅ is the input/output sequence number of task node C . p is the input/output sequence number of capability instance node CIj . Outputs. CIS2 , corresponding matched-degree d' and matched-degree set SS1 . Steps. Step1. For the ith capability instance node in CIS1 , if m