Open System Architecture for Condition- Based Main

Page1of122AppliedResearchLaboratoryTECHNICALMEMORANDUMOpenSystemArchitectureforCondition-BasedMaintenance:OverviewandTrainingMaterialAUTHORSMitchellS.Lebold,KarlM.Reichard,DanielFerullo,DavidBoylanTechnicalMemorandumFileNo.03-04028March2003CopyNo._____FinalReportPreparedforOfficeofNavelResearch(ONR)AppliedResearchLaboratoryP.O.Box30StateCollege,PA16804Page2of122AbstractAcommunicationsframeworkfornext-generationmachinerymonitoringanddiagnosticsystemshasbeenaddressedthroughtheOSA-CBMdevelopmentteam.Thisframeworkemploystheuseofanopensystemarchitecturestandardutilizingadistributedsoftwaremodelapproach.Adistributedsoftwaremodelwasselectedduetotherecentemergenceofenablingsoftwaretechnologiesandthebenefitsoftheapproach.Inparticular,theavailabilityofnetworkconnectivityprovidesareadyhardwarebackboneoverwhichthesoftwaresystemmaybedistributed.TheimplementationofaCBMsystemusuallyrequirestheintegrationofavarietyofhardwareandsoftwarecomponents.Therefore,acompleteCBMsystemmaybecomposedofanumberoffunctionalblocksorcapabilities:sensinganddataacquisition,datamanipulation,conditionmonitoring,healthassessment/diagnostics,prognostics,anddecisionreasoning.Inaddition,someformofaHumanSystemInterface(HSI)isrequiredtoprovideameansofdisplayingvitalinformationandprovideuseraccesstothesystem.AcrossthespectrumofmilitaryandindustrialapplicationsofCBM,thereisabroadrangeofsystemlevelrequirementsthatinclude:communicationandintegrationwithlegacysystems,protectionofproprietarydataandalgorithms,needforupgradeability,andreductionofengineeringdesigntimeandcosts.Therefore,anopenCBMcommunicationsarchitectureshouldprovideafunctionalplatformthatcanmeetthesedesignrequirementsandbeflexibletosuitabroadrangeofapplications.StandardizationofanetworkingprotocolwithinthecommunityofCBMdevelopersanduserswill,ideally,driveCBMsupplierstoproduceinterchangeablehardwareandsoftwarecomponents.Awidelyadoptednon-proprietarystandardwillresultinafreermarketforsuchCBMcomponents.Thepotentialbenefitsofarobustnon-proprietarystandardincludeimprovedeaseofupgradingforsystemcomponents,abroadersuppliercommunityresultinginmoretechnologychoices,morerapidtechnologydevelopment,andreducedprices.TheOSA-CBMdevelopmentteaminvestigatedseveraldifferentgroupsofmiddlewaretechnologies.TheteamdefineddatamodelsusingUMLandgeneratedlanguage-independentmodels,calledAbstractIDL.TheseAbstractIDLmodelswerethenportedtospecificmiddlewaretechnologygroups.ThefollowingthreetechnologygroupswhereofmainfocusfortheteamandIDL/Schemasareprovidedforeachtechnology:CORBA(CommonObjectRequestBrokerArchitecture),COM/DCOM(DistributedComponentObjectModel),XMLoverHTTP.OthertechnologiessuchasJAVARMI(RemoteMethodInvocation),.NETanddirectC++havebeendevelopedbygroupmembersbutwillnotbediscussedinthisdocument.ThispaperprovidesanoverviewoftheCBM,OSA-CBMandcurrentmiddlewaretechnologiesfordistributedapplicationsaswellasinsightintotheOSA-CBMmodels.VariousguidelinesarealsoprovidedfordevelopingsimpleskeletonOSA-CBMmodulesusingacoupledifferentdistributedtechnologies.Page3of122TableofContentsListofFigures..............................................................................................................................6ListofTables...............................................................................................................................7ListofListings.............................................................................................................................81.0Introduction......................................................................................................................91.1WhatisCondition-BasedMaintenance?......................................................................91.1.1CBM:CostandReadiness.................................................................................111.2CBMArchitecture......................................................................................................141.3OpenSystemsandStandards.....................................................................................171.4EvolvingInterfaceStandards.....................................................................................181.5MiddlewareTechnologies..........................................................................................191.5.1WhatisMiddleware?.........................................................................................191.5.2MiddlewareTechnologyGroups.......................................................................201.5.2.1CORBA..........................................................................................................201.5.2.1.1Real-TimeCORBA..................................................................................211.5.2.2COM/DCOM.................................................................................................231.5.2.3XML...............................................................................................................241.5.2.3.1XMLSchemas:AMeansofValidatingData...................