[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: OBIX Use cases
During our last conference call, we discussed creating a list of use cases and actors (users and providers). Here is a list to start the discussion. Glossary: Enterprise - Corporate wide enterprise that could include multiple buildings in multiple locations. Facility - A single building or campus location. - Enterprise financial manager - Responsible for allocating costs to the responsible parties within the enterprise. The responsible parties could be buildings, departments, production lines, machines, or many other methods of allocating energy costs. - Facility engineer - Responsible for managing energy consumption and the reduction thereof. - Facility staff - Responsible for monitoring particular loads within a facility. Will need access to raw energy usage data. Is not concerned with dollar costs. - Contractor - Financial services - Similar to Enterprise financial manager but is external to the enterprise so there are additional security concerns. - Contractor - Facility engineer - Similar to facility engineer but is external to the enterprise so there are additional security concerns. - Contractor - Facility staff - Similar to facility staff but is external to the enterprise so there are additional security concerns. - Energy meter - Individual meter producing energy metering data. Some of these may produce XML out of the box, others may need a Energy Software System to collect the data and convert to XML. - Energy Software System - Collects data from many Energy meters and offers the data up to the next level, the Energy Collection system. At this level, there could be some aggregation of meter data performed. - Energy Collection System - Collects data from the Energy Software Systems and individual Energy meters. The data is then processed, aggregated, and made available to the Energy Reporting system. - Energy Reporting System - Presents the data from the Energy collection system to the data users(actors at the top of the list) in a secure, usable format for their job function. I hope this starts the discussion. Thanks, Charles Watson (Chuck) CEM CMVP tel: 724-779-5937 http://www.eatonelectrical.com -----Original Message----- From: Doug Ransom [mailto:Doug.Ransom@pwrm.com] Sent: Thursday, August 26, 2004 11:42 AM To: obix@lists.oasis-open.org Subject: RE: [obix] SAML and oBIX I would prefer we enumerate the use cases, then select technologies. You just mentioned "expose tenant functions" under obix. Have you thought about adding some use cases? Doug Ransom Considine, Toby (Facilities Technology Office) wrote: > It is quite likely that SAML will be critical to exposing > tenant functions under oBIX. But what functionality do we > need? Will we be able to develop clear guidelines as to what > data to expose, and how, and to whom withing the oBIX implimentation > guidelines? > > With these thoughts in mind, I direct your attentions to: > > --------------------------------------------------------------------- > > Public Review of SAML v2.0 Begins > > The OASIS Security Services TC has recently approved the > Security Assertion Markup Language (SAML) v2.0 specification > as a Committee Draft and voted to submit the specification > documents for public review. SAML is an XML framework for > exchanging authentication and authorization information. > Comments are solicited from all interested parties and may be > submitted to the TC via a web form found at > http://www.oasis-open.org/committees/security. The public > review period will end on 19 Sept. > > http://lists.oasis-open.org/archives/members/200408/msg00004.html > > http://xml.coverpages.org/ni2004-08-19-a.html > > --------------------------------------------------------------------- Doug Ransom Energy Analytics Domain Expert Power Measurement 2195 Keating Cross Road Saanichton, BC, Canada V8M 2A5 Tel: (250) 652-7100 ext. 7558 Fax: (250) 652-0411 E-Mail: mailto:doug.ransom@pwrm.com Website: http://www.pwrm.com ION(r) smart energy everywhere(tm)
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]