1 / 14

CIM Test Development Process Status Meeting - Weekly Updates

This weekly status and planning meeting discusses progress, issues, stakeholder expectations, and action items for CIM test development. It covers tasks completed, requirements, and expected work output for the next week.

lisagriffin
Download Presentation

CIM Test Development Process Status Meeting - Weekly Updates

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Project 071103 CIM Test Development Process John Simmins Weekly Status and Planning Meeting2/1/2011

  2. Agenda • Progress since last meeting • Issues arising during the previous week • Verify progress against stakeholder expectations • General issues discussion • Action items for individuals • Expected work output during next week

  3. Progress Since Last Call • Reviewed and updated sample abstract test case • Walked through with group 1/18/2011 • Awaiting comments from Margaret Goodrich • Updated sample test procedure per comments received • Documenting Virtual Lab procedures to connect systems at lab sites (e.g. MDMS at Site A & CIS at Site B) • Consumers Site Support Guide initiated January 21 • EPRI and other utilities (if desired) next • Vender Site Support Guides started • Entering Test Case documentation in Enterprise Architect

  4. Virtual Lab Environment Tests conducted anytime, anywhere

  5. Enterprise Architect Test Model

  6. Issues Arising During the Past Week • Need reference set of interoperability requirements • OpenSG Integration Requirements & Integration Sequence Diagrams • SCE Use Cases • Suggested Part-9 Reference Interface Requirements • Need multiple venders to dry run procedures

  7. AMI-ENT Integration Requirements

  8. AMI-ENT Integration Sequence Diagrams B1S1 shown

  9. EPRI CIM Interoperability Test Plan / Test Cases and Interoperability Requirements

  10. Progress Against Stakeholder’s Expectations • Task 3: Complete Mapping and Report for Extensions: • The deliverable includes a mapping spreadsheet and a report describing the use cases, extensions and implementation profiles. • For each OpenSG domain the tasks in support of the harmonization include: • Review and analyze all gaps between domain artifacts and the CIM. • Document proposed mapping and CIM extensions. • Implement the CIM extensions in UML. • Generate the profiles and other artifacts required for testing. • Create use cases (if they don’t already exist) to clarify the need for the extensions.

  11. Progress Against Stakeholder’s Expectations • Task 5: IOP these service definitions. List may not all be feasible: • CustomerMeterDataSet • EndDeviceAsset • EndDeviceControl • EndDeviceEvent • EndDeviceResponses • EndDeviceResponse • GetDeviceStatus • GetMeterReadings • MeterReadingSchedule • MeterReadings • MeterReading • MeterAssetConfig

  12. Action Item Review

  13. Action Item Review (continued)

  14. Expected Work Output During the Next Week • Complete Site Support Guides • Consumers • EPRI • Initial vender • Identify additional participants and schedule dry run of procedures

More Related