CAISO_CIM_UserGroup011905PublicVersion.ppt

TowardsStandardCIM-basedServices,MRTUProjectExperienceatCAISOStipeFustarKEMAInc.MRTUICC/A&IProgramManager,MRTUReal-Estate,IntegrationChallenge,IntegrateAllSystemsandApplicationsontimeEnsurethatAllNewSystemsandApplicationsare“built-to-integrate”EnforceSOAwhereverappropriateMeetPerformanceandAvailabilityRequirementsOrchestrateServicesEffectively,IntegrationRisks,VendorsAbilitytodeliver(Siemens,Areva,Delinea,Others)OntimeMeetbusinessobjectivesStandard-basedsolutionsIntegrationVendorsabilitytoimplementtheproposedSOA-basedarchitectureICCabilitytocommunicate,educateandenforceeffectivelyacoordinatedapproachbasedonSOAUnclearorChangingRequirements,IntegrationStrategy,DistributeActivitiesImplementService-OrientedArchitecture(SOA)Forceallnewapplicationsandsystemstobe“IntegrationReady”withservice-enabledinterfacesAchieveLooseCouplingDataIntegrationEnterpriseInformationIntegrationasObjectiveBusinessProcessOrchestrationUnlockingofrigidprocessesthroughrun-timeconfigurationasmuchaspossible,Service-OrientedArchitectureThearchitectureofinterfaces,ServiceInterface,ServiceImplementation,Interface,Interfaceproxy,ServiceConsumer,WhatisService?Softwarecomponentthatisabusiness-completelogicalunitofwork,accessibleprogrammaticallyfromindependentlydesignedcontextsviaadirectopenlydocumentedinterface,WhatisSOA?Applicationsoftwaretopologyconsistingofservicesandserviceconsumers(clients)inlooselycoupled1-to-1relationships,NewService,WrappedService,CompositeService,Serviceinterface,Serviceimplementation,Non-SOAapplications,ServiceConsumer,ServiceImplementation:WhatHappensBehindtheInterface,ServiceConsumer,ServiceImplementation,XML/HTTP,SOAP/XML/JMS,SOAP/XML/SMTP,SharedMemory,RMI/Remoting,JMS/MSMQ/MOM,SOAP/XML/HTTP,Interface(WSDL),Generator,AlternativeTransports,ServiceInvocation:WhatHappensontheWire?,SOAPMessagePayload,TheCommonWebServicesArchitecturesupportstwotypesofmessagepayload.PayloadinSOAPBodyPayloadinSOAPAttachment,ServiceOrchestration,DefiningprocessexecutionorderEstablishingconditionalflowpatternsInvokesequenceofexecutionManagemessageroutesManageinterventionpoints,Designtime,Order,Runtime,Flow,Analysis,Design,Development,Testing,IntegrationScopePlan&Schedule,High-LevelDesign,ProjectsDesign,EAIDesign,LegacyDesign,ProjectsDev,EAIDev,LegacyDev,BusinessRequirements,UnitTest,UnitTest,UnitTest,End-to-EndTesting,SequenceDiagramsServiceDefinition,ICCwillfollowRUP,StructuringIntegrationEffort,IntegrationBusinessModelandUseCases,IntegrationTesting,Pre-FAT,SAT,ConceptualArchitecture,FAT,ArchitectureGroup,ArchitectureGroup,IntegrationCenter,ConceptualArchitecture,Stage1ProjectandFirstProductionDeployment,CommonPractice,ProjectTeam,ProjectTeam,ProjectTeam,OrganizingforIntegration,IntegrationCenter,ArchitectureGroup,ProjectTeam,1.PlanandJustify,IntegrationCompetencyCenter(ICC)Structure,ICC,Architecture,DataIntegration,ServiceManagement,IntegrationImplementation,SIBR,IFM/RTN/FNM,DMA,SaMC,MF,Legacy,ProgramManagementTier,CoreIntegrationTier,ProjectsTier,ICC,TestingTeam,ISInfrastructure,TechnicalTeam,CRR,Portal,ServiceDefinitionGuidelines,BPMs-Gatheringandreviewingbusinessprocesses,systems,applications,anddatabasesinformationthatareinvolvedinthescopeofservicesdefinition.UseCasesandSequenceDiagrams-Develop/ElaborateTo-BeserviceorchestrationrequirementsintheformsofUseCasesandSequenceDiagrams.CIM/CMEDevelopcommonsemanticbasedservicepayloaddefinitionintheformoftheUMLdiagram.ExtendtheCIM/CME,wherenecessary,toaccommodateCAISOrequirements.TheextendedCIM/CMEwillbetheCommonSemanticModelfortheMRTUprogram.Payload-CreateCIMbaseandservicepayloadXMLSchemafilesMapsourceandtargetdataformat(s)tothecommonsemanticmodelbasedservicepayloaddefinitions.DocumentanybusinessrulesofservicepayloadandmappingsPayloadTemplate-VerifyandvalidateXMLSchemafiles,andcreatesampleXMLinstancedatafilesforreferenceWSDL-DevelopWSDLservicedefinitionfilesusingaWSDLtemplate,andvalidateWSDLfiles.Documenttheservicedefinitionartifactsinonedocumentforagivenbusinessintegration(interface)area.,Initiate,Model,Design,Manage,ServicesDefinitionandManagementProcess,KickoffPlanGatherReviewAnalyzeArchitectFactModeling,ServicesDefinitionandManagementProcess,BusinessProcessUseCasesCIMExtensionsClassDiagramsSequenceDiagramsSemanticMappingsandBusinessRules,Initiate,Model,Design,Manage,ServicesDefinitionandManagementProcess,XMLSchema(XSD)XMLInstanceWSDLBusinessRulesDesignDocument,Initiate,Model,Design,Manage,ReleaseReviewUpdateApproveManageVersionsChangeRequest,ServicesDefinitionandManagementProcess,Initiate,Model,Design,Manage,Frameworks&Standards,IndustryStandards(XML,XSD,RDF,XSLT,WSDL,SOAP/HTTP,UDDI,WS-I,CIM/CME,IEC61967/61968),CAISOSOAArchitectureSOAPatternsSOAConceptualArchitecturePOC,Service&PayloadDesignMethodsServiceDefinitionMethodologyServiceDefinitionGuidelinesMDIFrameworkWS-I,DesignToolsRationalRoseMDIWorkbenchXMLSuiteWSDLToolsXMLSpyMindReefSOAPScope,ConfigurationManagementDocumentumVSSorClearQuestUDDIRepository,Initiate,Model,Design,Manage,WSDLDefinitionProcess,CreateSequenceDiagramCreateWSDLValidateWSDLStubsCodegenerationbasedonWSDL,Validation,CodeGeneration,SequenceDiagram,WSDL,ServicesClassificationOverview,InterfaceExamples:,SystemA,IntegrationLayer,PI,BITS,MC,broadcastMarketMeterData,WS,retrieveMarketMeterData,WS,broadcastMarketMeterData,WS,retrieveMarketInterchange,WS,receiveMarketMeterData,WS,receiveMarketMeterData,WS,broadcastInvoiceData,WS,broadcastGeneralLedgerData,WS,receiveInvoiceData,WS,receiveGeneralLedgerData,WS,broadcastStatusInvoiceData,WS,VisionOfStandardServices,LeveragesCIMAllpayloadsareforwardengineeredfromCIMStandardServicesWSDL(servesasInterfac