|
|
|
|
|
|
|
|
|
|
|
|
|
|
This page shows all the libraries, lists, discussion boards, and surveys in this Web site. Click the name of a library or list to view its contents. The Recycle Bin contains deleted items. To create a new library or list, click Create.
|
 |
|
| |
Name |
Description |
Items |
Last Modified |
Discussion Boards
|
|
Team Discussion
|
Team Leader: Terry Mohn (MMohn@Semprautilities.com)
This business-oriented team will normalize existing and new use cases by putting them into a standard template (based on IEC 61968 interface reference model) .
Over time, the goal is to incrementally build up a set of generic use cases that are expressed in similar format for the scope of AMIent. However, as each utility member has limited available bandwidth, each member will focus on a subset of use cases most relevant to its current work for a given increment. An increment is the amount of work a utility member can accomplish between AMIent meetings. Each utility will notify the team leader of the list of use cases it plans to cover in the current increment. The team leader will maintain a master list so that utilities can collaborate with other utilities working on the same use cases.
For a given utility’s subset of use cases, the first step is for its representatives to review existing use cases to see if they are fit for purpose for its business processes. For ones that are fit, it will recast the use case into the new template and extend/modify it as necessary to cover its requirements. For each business process that is not currently captured in a use case, the utility will create a new use case.
Each utility will have a directory where it will post its generic use cases. In addition to being used by the Service Definitions Team, fellow team members will be invited to review them to identify significant differences in practice and/or areas of concern.
|
0
|
15 years ago
|
|
|
|
|
|
|
|
|