CAISO_CIM_UserGroup011905PublicVersion

KEMA,INC.TowardsStandardCIM-basedServicesMRTUProjectExperienceatCAISOStipeFustarKEMAInc.MRTUICC/A&IProgramManagerKEMA,INC.2MRTUReal-EstatePTRCRRDMASettlementsIFM/RTNODSFNMMCMFADSSIBRSLICEMSBITSIntegratorPIPortalOASISComplianceKEMA,INC.3IntegrationChallengeIntegrateAllSystemsandApplicationsontimeEnsurethatAllNewSystemsandApplicationsare“built-to-integrate”EnforceSOAwhereverappropriateMeetPerformanceandAvailabilityRequirementsOrchestrateServicesEffectivelyKEMA,INC.4IntegrationRisksVendorsAbilitytodeliver(Siemens,Areva,Delinea,Others)OntimeMeetbusinessobjectivesStandard-basedsolutionsIntegrationVendor’sabilitytoimplementtheproposedSOA-basedarchitectureICCabilitytocommunicate,educateandenforceeffectivelyacoordinatedapproachbasedonSOAUnclearorChangingRequirementsKEMA,INC.5IntegrationStrategyDistributeActivitiesImplementService-OrientedArchitecture(SOA)Forceallnewapplicationsandsystemstobe“IntegrationReady”withservice-enabledinterfacesAchieveLooseCouplingDataIntegrationEnterpriseInformationIntegrationasObjectiveBusinessProcessOrchestrationUnlockingofrigidprocessesthroughrun-timeconfigurationasmuchaspossibleKEMA,INC.6Service-OrientedArchitectureThearchitectureofinterfacesServiceInterfaceServiceImplementationInterfaceInterfaceproxyServiceConsumerWhatisService?Softwarecomponentthatisabusiness-completelogicalunitofwork,accessibleprogrammaticallyfromindependentlydesignedcontextsviaadirectopenlydocumentedinterfaceWhatisSOA?Applicationsoftwaretopologyconsistingofservicesandserviceconsumers(clients)inlooselycoupled1-to-1relationshipsKEMA,INC.7NewServiceWrappedServiceCompositeServiceServiceinterfaceServiceimplementationNon-SOAapplicationsServiceConsumerServiceImplementation:WhatHappensBehindtheInterfaceKEMA,INC.8ServiceConsumerServiceImplementationXML/HTTPSOAP/XML/JMSSOAP/XML/SMTPSharedMemoryRMI/RemotingJMS/MSMQ/MOMSOAP/XML/HTTPInterface(WSDL)GeneratorAlternativeTransportsServiceInvocation:WhatHappensontheWire?KEMA,INC.9SOAPMessagePayloadPayloadsTheCommonWebServicesArchitecturesupportstwotypesofmessagepayload.PayloadinSOAPBodyPayloadinSOAPAttachmentKEMA,INC.10ServiceOrchestrationDefiningprocessexecutionorderEstablishingconditionalflowpatternsInvokesequenceofexecutionManagemessageroutesManageinterventionpointsDesigntimeOrderRuntimeFlowKEMA,INC.11AnalysisDesignDevelopmentTestingIntegrationScopePlan&ScheduleHigh-LevelDesignProjectsDesignEAIDesignLegacyDesignProjectsDevEAIDevLegacyDevBusinessRequirementsUnitTestUnitTestUnitTestEnd-to-EndTestingSequenceDiagramsServiceDefinitionICCwillfollowRUPStructuringIntegrationEffortIntegrationBusinessModelandUseCasesIntegrationTestingPre-FATSATConceptualArchitectureFATKEMA,INC.122.Stage13.Stage2ArchitectureGroupArchitectureGroupIntegrationCenterConceptualArchitectureStage1ProjectandFirstProductionDeploymentCommonPracticeProjectTeamProjectTeamProjectTeamOrganizingforIntegrationIntegrationCenterArchitectureGroupProjectTeam1.PlanandJustifyKEMA,INC.13IntegrationCompetencyCenter(ICC)StructureICCArchitectureDataIntegrationServiceManagementIntegrationImplementationSIBRIFM/RTN/FNMDMASaMCMFLegacyProgramManagementTierCoreIntegrationTierProjects’TierICCTestingTeamISInfrastructureTechnicalTeamCRRPortalKEMA,INC.14ServiceDefinitionGuidelines1.BPMs-Gatheringandreviewingbusinessprocesses,systems,applications,anddatabasesinformationthatareinvolvedinthescopeofservicesdefinition.2.UseCasesandSequenceDiagrams-Develop/ElaborateTo-BeserviceorchestrationrequirementsintheformsofUseCasesandSequenceDiagrams.3.CIM/CME–DevelopcommonsemanticbasedservicepayloaddefinitionintheformoftheUMLdiagram.ExtendtheCIM/CME,wherenecessary,toaccommodateCAISOrequirements.TheextendedCIM/CMEwillbetheCommonSemanticModelfortheMRTUprogram.4.Payload-CreateCIMbaseandservicepayloadXMLSchemafiles1.Mapsourceandtargetdataformat(s)tothecommonsemanticmodelbasedservicepayloaddefinitions.Documentanybusinessrulesofservicepayloadandmappings5.PayloadTemplate-VerifyandvalidateXMLSchemafiles,andcreatesampleXMLinstancedatafilesforreference6.WSDL-DevelopWSDLservicedefinitionfilesusingaWSDLtemplate,andvalidateWSDLfiles.7.Documenttheservicedefinitionartifactsinonedocumentforagivenbusinessintegration(interface)area.KEMA,INC.15InitiateModelDesignManageServicesDefinitionandManagementProcess•Kickoff•Plan•Gather•Review•Analyze•Architect•FactModelingKEMA,INC.16ServicesDefinitionandManagementProcess•BusinessProcess•UseCases•CIMExtensions•ClassDiagrams•SequenceDiagrams•SemanticMappingsandBusinessRulesInitiateModelDesignManageKEMA,INC.17ServicesDefinitionandManagementProcess•XMLSchema(XSD)•XMLInstance•WSDL•BusinessRules•DesignDocumentInitiateModelDesignManageKEMA,INC.18•Release•Review•Update•Approve•ManageVersions•ChangeRequestServicesDefinitionandManagementProcessInitiateModelDesignManageKEMA,INC.19Frameworks&StandardsIndustryStandards(XML,XSD,RDF,XSLT,WSDL,SOAP/HTTP,UDDI,WS-I,CIM/CME,IEC61967/61968)CAISOSOAArchitecture•SOAPatterns•SOAConceptualArchitecture•POCService&PayloadDesignMethods•ServiceDefinitionMethodology•ServiceDefinitionGu