GB∕T27758.2-2015工业自动化系统与集成诊断、能力评估以及维护应用集成第2部分应用领域矩阵元素描述与定义.pdf

ICS 25.040.40 11 10 中华人民=H工不日国国家标准GB/T 27758.2-20 15/ISO 18435-2: 2012 工业自动化系统与集成诊断、能力评估以及维护应用集成第2部分:应用领域矩阵元素描述与定义Indu喝trialautomation system啤andintegration-Diagnostics, capability assessment and maintenance applications integration-Part 2 : Descriptions and definitions of application domain matrix elements (lSO 18435-2: 2012, lDT) 2015-12-10发布中华人民共和国国家质量监督检验检疫总局中国国家标准化管理委员会2016-07-01实施发布GB/ T 27758.2- 2015/ISO 18435-2 :2012 目次lla言. .nr 引言.IV l 范围12 规范性引用文件.1 3 术语与定义4 缩略i吾.2 5 应用交互短阵元素(AIME)和应用领域短阵元紫(ADME)概述.电，.2 5.1 AIME和ADME的概念25.2 资源之间的信息交换.3 6 应用交互炬|等元素(AIME). .,. . 4 6.1 AIME概念.46.2 AIME形式结构.吨.，.4 6.2.1 通贝IJ. 4 6.2.2 AIME筷板首部. 4 6.2.3 AIME槟板语挠部分.,. . 5 6.2.4 AIME槟扳传递部分. .，. 5 6.3 AIM阁解表示. . J . 6 6.4 集成应用lAIM目的.7 7 应用领域短陈元索(ADME). 7 7.1 ADME概念. r ,.7 7.2 ADME结构87.2.1 通则. . . . . . . . . ， . . . . . . . . . . . . . . . . . . . . . . . . . 8 7.2.2 ADME板板首部f. .8 7.2.3 ADME筷板语槐部分. . .8 7.2.4 ADME模板传递部分.9 7.2.5 ADME图形表达. . 10 8构建AIME和ADM.12 9 一致性和符合性.14 9.1 -致性方面.14 9.2符合性方面.14 附录A(规范性附录形式ADME/AIMEschema . 15 附录B(资料性附录信息交换示例.25 参考文献.33 G/ T 27758.2-2015/150 18435-2,2012 前言GS/T 27758工业自动化系统.Lj成诊断、能力评估以及维护应ffJ成E拟分为虫11下几部分:一-第l部分:综述与通用要求:一一货2部分:应用领域矩阵元素描述与定义;-一第3部分:应用集成描述方法.本部分为GB/T27758的第2部分.本部分按照GB/T1.1-29纷似的规则起.本部分使用翻译法等同采用IS018435-2，2012(工业自动化系统与集成珍断、能力评估以及维护应用集成第2部分2应用领域矩陈元素描述与定义).与本部分中规范性引用的同际文件i-激性对应关系的J2国文件如下z-GB/T 27758.1-2011工业n，y，化系统与集成诊断能力评价以及饿妒应用集成第1部分:综述与通用擦求(ISO18435-1 ,2009, IDT) 一-GB/T19659.1一2005工业1)动化系统与集成开放系统应用然成很织第1部分:通翔的参考描述3-29 MEregiSlry AJME的注册名T ndusUy. specific_reg is try _ na me 6.2.3 AIME模饭语境部分AIME!吾挠部分定义了表2所示的属性.褒2AIME语境部分部分描述月亏例domnSection 源应用程序贮存处的峨串串识As坦l_He.hh._Assessm四t_domain目标应用程序贮存处的峨标识ASsel_ H eahh_Assessmenl_domain applic.ationSection 对应源应用程序的应用标识Heahh_assessm制对应目标应用程序的应用标识Prognostics 叩p1 ica tionRelat ions hi pSe: tion 应用程序峨的具体语搅CondjtioTl_Monitoring_O:mt胆tproc崎sSection与源资源有关的活埋标识Current 与目标资源有关的选理标识Fulure_h剧Ilh_grade_eval ualion 资源包名称PL1 re回urceSection-同回urce.P削k资源名称MotionOrive 资源中叮获得或所计划的能力专规ClP_ ISO_15745_prolile 6.2.4 AIME模饭传递部分AIME传递部分定义了如表3所示的属性.表3AIME传递部分部分描述月可例informationType 交换iB息的类型Ca vitationInlormationR吨U四troleType 列举囱特定俗息交换参与者展示的PumpConlrolRole 能力Ca vita tionDetectionRole relalionshipType 识)lIJ应用角也类型2是行为Ca vita tionDetection2PumpControl parlicipanlType f自息交换合作方的类型Ca vita tionDetection channelType 参与者之间的信息项交换点ClP FTLD channel 5 GB/T 27758.2- 2015/ ISO 18435-2 :2012 6.3 AIME图解表示AIME的图解表示如图5、图6和阁7所示.这些因遵循ISO/IEC29500-2描述的约定.M创rixEJ刷clttHca阳l，1:ttrixcmC旧时y因5AIME矩阵元素首部和矩阵元素主体啊lli刷nDnal.o刷刷刷lipN:m1. 图6AIME语境部分6 GB/T 27758.2- 2015/ ISO 18435-2 :2012 Conftyanc.:!_Seclion El -酣F巳EEg二Gh-fzEEEe=惆-em-队W= -曲=由阳=咽削=-= 俨4、1.四panicipan厅y严吨td-eL-y-w-m-FA电1.曲图7A邸E传递部分形式AIME筷板结构应该如附A所定义。6.4 集成应用中AIME目的AIME的目的是为了表达应用中资源的信息交换能力.AIME能促进验证任务的实施，剧l验证应用的资源是否能支持与另一应用中的特定资源集逃行特定信息交换.7 应用领域矩陈元素(ADME)7.1 ADME概念ADME的目的在于描述应用所僻的互操作性和集成要求，如图8所示.应用X应用Yr- 信息交换信息交焕L_ 图8ADME目的7 GB/ T 27758.2-2015/ISO 18435-2 :2012 在AIME中识别出的能力基础上，ADME支持应用之间的信息交换.应用间的信息交换将以路径捎述方法进行捎述.路径tr，述综合应该由ADME和相应专规表达.此描述方法区别于源实体、描述实体以及交换的其他属性，例如约束、交换类型和接口类型。AIME的完全集表示的是实现两个应用间互操作的信息交换需求，AIME的完全集应该包括ADME.如GB/T27758.1-2011的困7所示，每个应用中的一些资源涉及应用间的信息交换.与另-个应用进行信息交换的时候，每个应用均相互协调。7.2 ADME结构7.2.1 通则ADME元索表示涉及信息记聚集的信息传递，这在源实体和目标实体间的ADME筷板中进行定义.使用schema米组织内容，该schema表示图表和关系中的元索.ADME的结构应该包括两个部分:首部和主体。主体包括语挠、传递和内容部分。每个部分可表达为一个XMLschema片段.7.2.2 ADME模饭首都ADME首部部分定义了虫表4所示的属性.表4ADME模饭首都属性属性捎述j( 例MEidenlilicalion AD陆3识;!jllISO ADME MErevision ADME的版本V01.01.01a MEname ADME的描述性名称D.2.2.Ay_D.2.2Az MEsource ADME开发者的识别AOMEsrc MEclassID AD附:类的识;SIIAIP MEdale ADME该版本的发布日期200H3-29 MEregisly AD伍的注册名Tndusl，y_srecilic_reg附try_name7.2.3 ADME模饭语境部分ADME语挠部分定义了虫表5所示的属性。袋5ADME模板语镜部分部分捕述刀亏例domnSection 源应用程序贮存处的城识;!jllAsset Heahh Assessment domain 目标应用程序贮存处的城识别Asset Heahh Assessment domain 叩plicationSection对应源应用程序的应用识别Heahh，.assessm制对应目标应用程序的应用识别Prognostics a pp 1 ica tionRelat ions hi pSet.: tion 应用域的具体说境Robol_ Conlrol_ Conlexl proc田sSection与源的资源有关的进程识别Current_heallh_grade_evalualion 与目标资源有关的进程识别FUlure_heallh,.grade_evalualion 8 GB/ T 27758.2- 2015/ISO 18435-2 :2012 部分resourceSect ion-resou rcePac k 7.2.4 ADME模板传递部分资额包的名称资源名称表5(续)描述资源中可获得或者所计划的能力(;.规ADME传递部分定义了如表6所示的属性.表6ADME模饭传递部分部分捎述inlormationType 交换信息的类型roleT ype 列举信息交换参与者J.ii出的能力行为通过接口，取得参与者的基本交互relationshipType 识!l1角也类型租行为participantType 信息交换合作方的类型channelType 对两个角色类型问信息交换媒介的描述 ADME模饭馆息交缺部分ADME信息交换部分定义了如表7所示的属性.表7ADME模饭馆息交换部分部分指述Name 信息交换的各称relationship 信息交换的羡系类型variableOelinitions 用于信息交换的变1il:定义 ADME模饭交互部分ADME交互部分定义了表8所示的属性.表8ADME模板交互部分属性部分销迷Name 交互的名称exchange f自息交换交互的2在本单元send/ receive 2t送/接收在交换中通过变盐定义的每个行动的信息示例PL1 MotionDrive CIP _ISO_15745_prolile j( 例Ca vitationInlormationR明U回tPumpControlRole CavitationDetectionRole Ca vitationDetection2PumpControl Ca vitationDetection CIP F1LD channel 月亏例SmartPumpInlormationExchange PU mpContro12Cavit ationOetect ion DiagR明uestCa vDetect ionResponse j( 例ca vt8tionlnorm时ionElicit8tionCa vita tionTnfonnationR吨u制9 GB/T 27758.2- 2015/ ISO 18435-2 :2012 7.2.5 ADME图 形表达ADME图形表达如图9-阁1 3所示.这些因遵循lSO/IEC29500-2描述的约定.这些图说明了表5-玉是8.以及A.2l的XMLsch ema. iII MEdenticHon M时rixEl创利entH抽dcrConle:d Sectioll MAlrixElcm相IB耐vCo伯vCy3n，四_SectionC()n1阳1S饵IIOnI+l 图9ADME短路元素首都和矩陈元素主体dOlllainSoutceHalldle dom:tn$CI.tou dlnainDes.jnlllionHr叫le1: .PicationSourcdfandle I appJicmio!山四tnntionJiandJeConlXI Soclion I applicali阳OomainR.lliOnShipName图10ADME语境部分10 E圳、1巳阴阳-玩世i啊，Con陡峭Sti刷G/T 27758.2-2015/L回18435-2，2012relollOnstupT阳间rucip.-tnlT)l:te I时1. .0。CEEFG如-SZE)1.抽，.-、1毗Tym J阁11ADME传递部分，言-.，f-dcsnp鼠侧EL_J nfWttl3tlonE、clll I.&I!l荆J. 阁12ADME内容部分11 GB/T 27758.2- 2015/150 18435-2:2012 . fonno嗣nE回wl8己EEEE二毛3一;二Ild-晴-阳-m-4回13ADME信息交担起形式AOME摸扳结构应该如附录A所示.8构nAfME和ADME构illAIME和ADME的通用过和!应该如下所示:8) 定义应用;b) 分配域集成回袭-纷AOID取回/设定城号码sc) 识别资产和资源，然后分配给应用$d) 定义信息交换3e) 根据GB/T19659模板识别所箭的缺口.以引用相应专嫂$0 为每-个被描述的应用填写AIME;g) 使用AIME构建AOME.这些ADME体现了应用之间的互操作性需求.来例，在回14中.为了识别集成应州必需的AIME.集成涉及的资源被分为两tIl，执行应州的资源和应用维妒和操作的资源.其余资源不予考虑.一且将资源分尖.)f识别出角也租参与情况，应则便与这则细资源街关.创14i且明了如何识别特定集成场景下必需的AIME和ADME.黄乐例a)7 G 1 3/T 2228J J主义的激黯采集(DA) 、激tlH靠你(DM)和状态检测。D)JJi.HI之r， (11交互.1 2 企业层mp.层114层民3层民2层Rl层RO图14集成场景示0tJGB/ T 27758.2-2015/ISO 18435-2 :2012 资源执行应用机籍人指鹉始数字控制精RC!NC监测(状事监测操作斥在护贸源百卫兵w | 机床必需的AOME在表9中标记为X飞在此集成场朱中，识;!jll了三个不同类型的应用根据GB!T22281, OA、OM和50)，以及三个不同类型机器人控制都(RC)、数字控制能(NC)和状态监测(CM)的相关资源.在此集成场朱中，总共有4个AOME，即下列每项均需要有一个AOME，-一-RC正在执行的OA至CM正在执行的OM，m一RC正在执行的OM至CM正在执行的50，由一NC正在执行的OA至CM正在执行的OM，由一NC正在执行的OM至CM正在执行的50.袋9说明7从横徘源至竖列目标的信息流.例如，回14中RO到R4层与GB!T27758.1-2011图5的AOTO图装有关.表9属成必需的ADME资源目标RC NC CM l 应用OA OM 50 OA 01.1 50 01.1 50 OA X RC OM X 50 OA X NC OM X 50 OM CM 50 此集成场景必衔的AIME集在表10中标记为X.资额RC到CM必需有-个AIME集合，资饭NC到CM必铺有另-个AIME集合.RC至CM应用 的AIME如AOME示例在附录B.13 GB/ T 27758.2-2015/ISO 18435-2 :2012 表10集成必霜的AIME资源RC NC CM RC X NC X CM 9 -致性和符合性9.1 一致性方面应该由执行提供者根据以下指雨声明与GB/T27758的本部分保搏一数: -致性声明应该阐明在特定执行中引用本部分的意条:b) 如果本部分有意条得要按组执行，那么这些意条集在特定执行中应该校组引用;c) 本部分中依照UML约定构建的某些因袭，应该根据需接构成一致性声明的一部分.9.2 符合性方面应该由规范提供者根据以下指南声明 与GB/T27758阔本部分符合:a) 符合性芦明的目的应该阐明在特定规范中引用本部分的意条;b) 如果本部分有意条吉普要按组引用，那么这些i;持集在特定规范中应该按组引用;c) 本部分中根据UML约定构建的某些因袭，应该根据古需要构成符合性声明的一部分.14 G/ T 27758.2-2015/L回18435-2:2012附录A(规范性附录形式ADME/AIME schema A. l AlME schema A1ME的形式定义如下:(? xal vers ion = 1.0 encod i，可=utf-8?) (schetla皿1ns:aiae = /aiaee1ea四tForaDefault= q崎lifiedtarget抛翩espace= http:/./aiaeXII1ns = http:/. . 司.。均/2001/XM凶chetla勺(e1ement naee = 150 AIME) (complexType) (sequence) (elem ent nam e = MatrixElementHeader) (complexType) (sequence) (el阻四tna脏=MEidentificationtype = string / ) (elem四tn缸回=MErevisi。type=飞tr卫鸡/) (e1曲曲tna睡=-MElllIetype = str扫宵/) (el回回tna嗣=.限sourcetype=string/) (el回回tna鹏=HEclass10type. string /) (e1ement na脏=MEdatetype = tring/) (el四entna脏=MEregstr矿句pe= anyURI / ) (/seque胆创(/complexType) (/el创ent)(el刨entn制e= MatrixElelllentBody) ( complexType) (s饲U回ce)(e1eaent ref = aiae，Conte咐_Section/) (e1eaent ref= aiae，Conveyance_臼ction/) (/sequ臼x:e)(/colllplexType) (/el创ent)/s句uence) (element ref = aime :applicat ionRelat ionshipSect ion / (elem ent ref = aim e : processSection / (elem ent ref = aim e : resourceSec ti/ (/s甸回nce(/ complexType (/element (element n副ne= Conveyance_Sect ion (complexType 16 (sequence (elem ent minOccurs = Onam e = description气ype= string / (elem ent m axOccurs = unboundednam e = inform ationType (complexType (sequence (elem ent mir记ccurs= Oname = descriptiontype =句string/(/sequence (attribute name z name气ype.l stringuse optional / (attribute name = typetype = st ringuse optional / (/complexType (/el四ent(elem ent maxOccurs = unbndedname = roleType ( complexType (sequence (element mir白ccurs= Oname = descript iontype = string/ (element mir白ccurs= Qname 11: behavior) (complexType (sequence (elem ent minOccurs萄Onarnez descriptiontype string户，/ (/sequence (attribute name = nametype = stringuse = opt ional / (attribute nallle = interfacetype = anyURIuse = optional / (/complexType (/elem ent (/ sequence (attribute name = nametype = st ringuse = opt ional / (/complexType (/el四ent(elem ent minOccurs = OmaxOccurs = unboundedname = relationshipType ( complexType (sequence (element mir白ccurs= O name = descript iontype = string / (element m臼 (complexType G/T 27758.2-2015/150 18435-2,2012 (attrwute nJIe -typeReftype= stringuse = -optional/) lcomplex巧pe)lel ement) (/complexType (/element) (/sequence (attribute name = nametype= strir旷uses optonal /) lele脏nt)(el臼脏、t皿呈xOccurs =-boundednJIe = -channe1Type) (comp!e叮ype)(se回ce)(el ement lIinOccurs Oname = descripti。type= string/) (attribute name =勺lametype. tringuse = optional/ (attribute name = typety归.stringuse = optional/ (/com plexType (/c悼plexType(element ref = ame :domainSourcetlandle / (elem ent ref = aime: domainDestnationtlandle /) (/sequence) (/com plexType (/element) (element name = applicati。略目tion)(c帽plexType)居qu刨出11 GB/T 27758.2- 2015/15018435-2:2012 (eletlent ref = Jaiae:appli臼tionSourceHandle/)(eletlent ref = uaiae:appli曰副主DestinationHandle/)(/ sequence) (/complexType (/elcmcnt (clcmcnt name = applicationRelationshipScction (complexType) (sequence) (el刨刨tma缸xO臼ccu臼=(/se句qu臼lCe(/c帽plexType)(/eleaent) (elellent name = pr四sSection)(compl缸Type(sequence maxOccurs = . unbounded (elem ent ref =飞ime:processSourceHandlel(clcm ent ref = aim e : processDcstinationHandle 1 (/s饲uence(/complexType (/eleJll凹的(el阻四tnaae = -resourceSection) (c佣plex句pe)提quencemaxOccurs 5 Junbounded) (element ref = aille: resourcePack 1) (/ s吨uence(/complexType (/clcmcnt (clcm cnt name = res。田cePack(complexType (s吨U四ce)(el阻四tname = resourceNuetype = str ing1 (el锢四tnaae = -resourceProfiletype = ManyURI 1 (/ s饲uence(attribute name = Jnametype e飞tringl(1mplexType (/element (elem ent name = domainSourceHandletype . string 1 (elem ent name = domainDestinationHandletype = . stringl (elcm cnt name = applicationSourceH andletype =飞tringl(elcmcnt na.m e = applicationDestinationHandletype =飞tring1 (eleaent name = applicationD。旧inRelationshipNametype= string 1 (elea四tnaJle = appl皿atio.nProfileIDtype= strJ宵1(el倒四tn描e=-proc臼sSourceHaJ回letype= Mstring 1 1 8 G/ T 27758.2-2015/L回18435-2:2012(element naae = pr臼sDestinationHandletype= string /) (/sche.a) A.2 ADME schema ADME的形式定义如下:(? xml version = l.Oencodir啕=utf-8?) (schema XlIllns: adme = http:/www ./admeel四entFormDefault雪、国lifiedtarget阳JIlespace= / admelIlIllns = http:/www.w3.。均/2001/XM凶ch四a)(el回回tname = ISO AIME) (co.plexType) 捷。lence)(element name = HatrixElement Header) (compl exType) (sequence) (element na肥=MEidentificationtype = stJ:ing /) (elem ent na阴=MErevisiontype = string户.，/ (element na胆=MEnam.etype = strir旷/)(el阻四tna皿=HEsource type = string /) (el阻四tna盹=HEclass1Dtype =飞tdJ可/)(element na酣军-HEdatetype= str扫宵/) (elem回tnlle . -HEregistrytype = .抓JR1/) (/s町uence)(/complexType) (/el四ent)(element n四e= HatrixElementBOdY) (complexType) (sequence) (element ref =飞伽e，Context_S田tion/)(el ement ref =、dme: Conveyance _部ction/) (el四entref =、e，Content_Section/) (element ref = adme:resourceSection/ (/sequence (/com plexType (/elem ent (elem ent name. Conveyance_Section (complexType 20 (sequence (elem ent minOccurs = Oname = descriptiontype = string / (elem ent maxOccurs = unbndedname = informatiType ( complexType (sequence (element mir白ccurs= Oname = descript iontype = string/ (attribute name = nametype = stringuse = opt iQnal / (attribute name. typetype. stringuse optiOJlal / (/complexType (/el回ent(element maxOccurs = unboundedname = roleType (com plexType (sequence (elem ent minOccurs = Onam e = desoo;，iption气ype= ( string户/(elem ent mir也ccurs= Onam e = ,bcllavior) (complexType (sequence (elem ent minOccurs =峰。岱酬e= descriptiontype = string / (/sequence (attribute name. 咽ne气ypez string户use.optional / (attribute name z interface气ype=anyURIuse = opt ional/ (/comple刘ype (/complexType (/el倒ent(element maxOccurs = unbndedname = relat ionshipType (com plexType (sequence elem ent minOccurs z lOnam e z descriptiontype. string户/(elem ent m axOccurs z unboundedname. roleType) (complexType (attribute n酬e=typeReftype= strir旷use= optional / (/com plexType GB/T 27758.2- 2015/ ISO 18435-2 :2012 (/element (/sequence (attribute阻me= nametype = strir旷use= optional / (/compl阻Type(/elem ent (elem ent maxOccurs . unboundedname. participantType (complexType (seque胆创(element minOccurs = On酬e= descriptiontype = string / (element minOccurs = On酬e=气。leType(complexType (attribute name= tYJ;暗Ref气ype= ( string回e骂optional/(/complexType (/elem ent (/sequence attribute nam e z nam etype. stri鸣use OPtional / (/complexType (/element (element maxOccurs = ;unboundedname = channelType。(com plexType (seque町的(elem ent minOccurs = Onam e = desoription气ype= ( string户/(/sequence (attribute name = nametype = stri吨use= opt ional / (attribute name = typetype = st ri吨use= opt ional / (/compl阻Type(/elem ent (/ sequence (/ complexType (/element (elem ent n缸ne= Content_S何tio旷.，(com plexType (s甸回nce(elem ent minOccurs = Onam e = description) (complexType (s impleContent (extension base = string (attribute name= typetype = stringuse = optional / (/ extens ion (/simpleContent (/complexType (/elem ent (elem ent maxOccurs = unb。回dedname= infor旧tionExchange21 GB/T 27758.2- 2015/ISO 18435-2 :2012 22 (comp1exType (seque胆的(e1em ent minOccurs = On酬e= descriptiontype = string / (e1em ent minOccurs = Oname = re1at ionship (com p1exType (attribute nam ez type气ypez string户use.optiona1 / (/comp1exType (/e1ement (e1ement minOccurs = Oname = variab1eDefinitior四(comp1exType (sequence (elem ent minOccurs = O maxOccurs = unboun岱dname= variab1e (c佣p1exType(sequence (e1em ent minOccurs = Oname = fesc;ript iontype = string / (/sequence (attribute name. nametype (attribute name = ;channe1Typetype = string因e= opt iona1 / (attribute name = ro1eTypestype = stringuse = opt iona1 / (attribute n酬e= infor晒t坦白ypetype= strir旷use=optio阻1/(/comp1exType (/elem ent (/ sequence (/comp1exType (/e1ement (sequence (e1em ent maxOccurs . Wlboundedname. interaction (comp1exType (sequence (e1ement minOccurs = Oname = d臼criptitype= string / (e1ement lIinOccurs = On缸ne= participate。(comp1exType (attribute name = relationship功庐type= striI唱回e= optional/ (attribute name = fr阴阳1elYpeReftype= strir唱回e= optional/ (attribute name =气。由。1Ei功peReftype = s tring因e= opti，。旧1/(/comp1exType (/e1em ent (e1em ent minOccurs = OmaxOccurs = unbound创name= exchange ( comp1exType (sequence (el倒四tm inOccurs = Oname = descriptity陪=string / (e1em ent mir也ccurs= n缸ne= send (comp1exType GB/T 27758.2- 2015/ISO 18435-2 :2012 (attribute name = variabletYJ;电=stringuse= opt ional / (/complexType (/elem ent (el回LentminOccurs = On酬e=receive) ( complexType (attribute name -variabletype . string户use-optional/ (/complexType (/elem ent (/sequence (attribute nam e = name tYJ;暗=( stringuse = optional / (attribute nam e = infor咽tionType type= string户use= optional/ (attribute name = actiontype = stringuse = optional / (/mplexType (/elem ent (/sequence (attribute name = name气ype= string户use= opt ional / (attribute name = 。严rationtype= s t,ringuse = opt ional / (attribute name = channelVariabletype = stringuse = optional / (/com plexType (/elem ent (/ sequence (/sequence (attribute name = nametype = string回e= optional / (/ com plexType (/elem ent (/ sequence (/complexTy时(/elem ent (elem ent name= d。旧inSec tion(complexType (sequence (elem ent ref = adme :domainSourceHandle/ (elem ent ref = adme : domainD est inationHandle / (/sequence (/complexType (/elem ent (elem ent n副ne= appl icat ionSect ion (com plexType (sequence (elem ent ref = adme :applicationSourceHandle / (elem ent ref = adme : applicationD estinationHandle / (/sequence (/com plexType 23 GB/T 27758.2- 2015/15018435-2:2012 eleaent naae = applicationRelationsbipSecti勺complexType) 盹quence)(element旧xOccurs= unbndedref = adme:applicatiOJ、DomainRelationshipName/)lsequence) lcomplexType) le1ement) e1ement name = pr四sS四tion) 就坷ue町emaxOccurs = unbou，叫 1 sequence) lcomplexType) lelement) (elem ent nam e = resourceSection) (complexType) (sequence maxOccurs = unbounded) el阻四tref =飞dme:resourcePack/) complexType) (sequence) (elem ent n棚e= resourceNametype string 1) (elem ent name =气esourceProfiltypc= anyURI 1) ls甸回nce)(attribute name = nametype ,. string 1) (element name = applicationProfileIDtype = strir宵/)(elcm cnt nam e = processSourceHar咄。typc=气tring户/)(elem ent name = ;processDestinationHand1etype = . string 1) (ISO_AIME xrnlns = http:/www.iso叫/ailne削ns:xsd=http:/www.w3叫/2001/XMISc阳的nstanc的(MatrixEl田lentHeader(MEidentificationexam pleA IME(/MEidentification (MErevi sionla(/MErevi sion (MEname O.1.2.Ay_O.1.lAx(/MEname (MEsource lSO(/MEsource (M EclassIOAIP(/MEclassIO (MEdate 2010-09-14( /MEdate 8.2 25 GB/ T 27758.2-2015/ISO 18435-2 :2012 (MEregistryIndustry_speci fic_registry_name_ISO_13774_DM(/MEregistry (/MatrixElementHeader (MatrixEl回LentBody26 (Context_Section (dom ainSection (domainSourceHandleDl.l(/dom ainSourceHandle (domainDest inat ionHandle (/domainDest inat ionHandle (/domainSection (applicationSection (applicationSourceHandleR蚀。tControl(/applicationSourceHandle(applicationDestinationHandle (/applicationDestinationHa ndle (/applicationSection (appl icat ionRelationshipSection (applicat ionDomainRelationshipName Robot DM Context (/applicationDomainRelationshipN am e (/applicationRelationshipSection (processSection (processSourceHandleMotionControl(/processSourceHandle (processDestinatiHandle (/processDestinationHandle (/processSection (resourceSection (resourcePack nam e = PLC (resrceNameControlLogix02(/resourceName (resrceProfilePLCiso15745profile(/resourceProfile (/resourcePack (resourcePack nam e . Kinetix (resourceNameKinetixDriveOl(resourceProfi leKinet ixiso15745profi1e(/resourceProfi le (/resourcePack 付出。urcepack n缸ne=x协120(resrceNameXM-120_03(/resourceName (resourceProfileXM120iso15745profile(/resourceProfile (/resourcePack (/r臼。urceSection(/Context_Section (Conveyance_Section (descripti RobotControl to Diagnostics Example(/description ( information巧penam e . Vi blnfoRequestType type. tViblnfoRequ臼t(d臼criptionViblnfoRequestMsg w ill request robot tool vibration information (/ description (/ informatiType GB/ T 27758.2-2015/ISO 18435-2 :2012 (informat ionType name = Vi b1nfoResponseType type = tVi b1nfoResponse (d臼criptionVi b1nfoResponseMsg will have degree of robot tool vi bration (/ description (/informationType (roleType name z RobotControlRole (d臼criptionRolefor Robot Cont rol(/descript ion (behavior n副盹=;RobotDM interface = RobotDMResponseSvc。(descriptionBehavior for providing R仙。tDM i nformation(/description (/behavior (/roleType (participant巧pename = RobotM otionCtrl (d臼criptionRobotCont rol Par t icipant(/descript ion (roleType typeRef = tns:R蚀。tControlRole/(/participantType (channel Type name RobotMon拭目拢。botControltype IS0 15745 _ ENet_ CommNet _Pro-file (d臼criptionRobot Cont rol to Diagnostics Channel. TYJ.:电Et hernet/IP channel based on IS0 15745-2 Comm Profile (/ description (/channelType (/Conveyance_Section (/MatrixElem entBody (/IS0 _ A1ME B.3 CM 的AIME本示例tr，述第8章中CM 的AIME.(? xml vers ion = l.Oencodir可=utf-8? (ISO_AIME xmlns = http:/ j aimexmlns : xsd = http:/www.w3 .org/2001/XMLSc阳na-instanc的(MatrixElementHeader (MEide的ificationexampleA1ME(/MEide的ification(MErevi sionla(/MErevi sion (MEnameD.1.2 .Ay_D.1.1Ax(/MEname (MEsourceIS0(/MEsource (MEclass1DAIP(/MEclass1D (MEdate Z010-09-14 (/MEdate (MEregistry Industry_specific_registry_name_IS0_13374_SD( /MEregistry (/MatrixElem entHeader (MatrixEl田lentBody(Context Section (domainSection (d创lainSourceHandle(/domainSrceHandle 27 GB/ T 27758.2-2015/ISO 18435-2 :2012 28 (domainDestinationHandleDl.2 (/d。旧inDestinationHandle(/domainSection (applicationSection (applicat ionSourceHandle (/applicat ionSourceHandle (applicationD臼tinationHandleConditionMonitoring(/applicationD estinationHandle (/appl icationSection (applicationRelationshipSecti(applicat ionDomainRelationshipN ameRobot _SD_Context (/applicationD。阻inRelationshipName(/applicationRelationshipSection (processSection (processSourceHandle (/processSourceHandle (processDestinat ionHandleRobotConditionMonitoring(/processDestinat ionHandle (/processSection (resourceSection (resourcePack name. PLC (resourceNameControlLogixOl(/res。山ceName(resourceProfi lePLCiso15745profi le(/resourceProfi le (/resourcePack (/r筒。urceSection(/Context_Section (Conveyance_Section (descriptionRobot Monitoring Example/description (informationType name = ViblnfoRequest:lypetype = tViblnfoRequ臼t(d出criptionVi blnfoRequestMsg w ill request robot tool vi bration inform ation (/description (/informationType (informationType name = ;ViblnfoResponseTypetype = tViblnfoResponse (d出criptionViblnfoResponSeMsg will have degree of robot tool vibration (/description (/inform ationType (roleType name = RobotMonitorRole (d臼criptionRolefor Robot Monitoring(/description (behavior name = RobotSD interface = RobotDM RequestSvc (descriptionBehavior for requesting Robot DM infor町lation(/description (/behavior (/ roleType (participant巧pename = tns : RobotMonit饵(d出criptionRobotMonitorParticipant(/description (roleType typeRef = tns: Rob。恼。nitorRole/GB/ T 27758.2-2015/ISO 18435-2 :2012 (/part icipantType (channelType name = RobotMoni tor 2RobotCont rol type = IS0 15745_ENet_CommNet _Profile (d出cription协助tMonitor to Robot Control Channel Type Et hernet/1P channel based on IS0 15745-2 Comm Profile (/description (/channelType (/Conveyance_Sect ion (/MatrixElem entBody (/IS0_A1ME 8.4 集成RC的ADME本示例描述表9中(RC上的DM到CM上的S凹的集成RC应用。(? xml vers ion =气。encodir可=ut f-8? (ISO_AI:ME xmlns . /admexmlns :xsd / 2001/XMLSchema-instance (MatrixEl田lentHeaderMEident i f icat ionexampleADME/MEidentificat ion MErevi sionla/MErevi sion (MEn酬eD.1.2 且y_D.1.1Ax(/MEn酬e(MEsourceIS0(/MEsource (MEclass1DAIP(/肥classID(MEdate 2010-09-14 (/MEdate MEregi stry Industry_specific_regis try_n咽e_IS0_13374_DM_SD/MEregis try/Mat rixElementHeader (MatrixEl回LentBody(Context_Section (domai nSection (domainSourceHandleD1.1(jdomainSrceHandle D1.2 /d。旧inDestinationHandle/domainSection (applicationSection (applicationSourceHandleRobotControl(japplicationSourceHandle (applicationDestinationHandleConditionMonitoring(/applicationDestinationHandle /appl icat ionSect ion appl icat ionRelat ionshipSection (applicationDomainRelationshipNameRobot _DM_Context (/applicationD。阻inRelationshipName(applicationDomai nRelationshi pNam eRobot _SD_Context (japplicationDomai nRelationshi pNam e /appl icat ionRelat ionshi pSection (/roleType (relationshipType n酬e= Rob。悦。nitor2RobotControl (roleType typeRef = tns: RobotMonitorRole / (roleType typeRef z tns: RobotControlRole/ (/relationshipType (part icipantType name = ;tns : RobotMonit饵(descriptiRobot Monitor Participant(/d臼cription(roleType typeRef = tns: RobotMonitorRole / (/participa的Type(participantType nam e = RobotMotionCtrl (descriptionRobot Control Participant(/d臼cription(roleType typeRef = tns: RobotCont rolRole / (/participantType (channel Type name = RobotMonitor2RobotControlCh田neltype. 150 15745_ENet_CommNet_Profile (descriptionRobot Control to Diagnostics Challnel Type Ethernet/1P channel based on 1SO 15745-2 C佣mProfile (/descripti(/ channelType (/Conveyance_Section (Content Section (inform ationExchange nam e = intRobotInform ationExchange (description1nt勾ratedRobot Monitor/Cont rol 1nformation Exchange(/description (relat ionship type = tns: RobotM。且itor2Robo