Business Requirements Specification

Transcription

1 Business s Specification Date Created: 3/19/2013 Doc ID: GNFDMDEHU6BB Page 1 of 18

2 Disclaimer Business s Specification Date Created: 3/19/2013 All information contained in this draft Business s Specification (BRS) as provided by the California Independent System Operator Corporation (ISO) is prepared for discussion and information purposes only. The draft BRS is provided as is without representation or warranty of any kind, including, without limitation, a representation or warranty as to accuracy, completeness, or appropriateness for any particular purpose. The draft BRS shall be revised as the development and review of the business requirements progresses. The ISO assumes no responsibility for the consequences of any errors or omissions. The ISO may revise or withdraw all or part of this information at any time at its discretion without notice. Doc ID: GNFDMDEHU6BB Page 2 of 18

3 Business s Specification Date Created: 3/19/2013 Table of Contents INTRODUCTION PURPOSE REFERENCES DETAILS OF BUSINESS NEED/PROBLEM DESCRIPTION BUSINESS PROCESS IMPACTS HIGH LEVEL BUSINESS PROCESS Description BUSINESS REQUIREMENTS BUSINESS PROCESS: NEW RESOURCE IMPLEMENTATION SECURITY ROLES Business s BUSINESS PROCESS: NEW RESOURCE IMPLEMENTATION INTERNAL INTERFACE Business s BUSINESS PROCESS: NEW RESOURCE IMPLEMENTATION EXTERNAL INTERFACE Business s Doc ID: GNFDMDEHU6BB Page 3 of 18

4 Business s Specification Date Created: 3/19/2013 Introduction 1.1 Purpose The purpose of this document is to capture and record a description of what the Users and Business Stakeholders of the project wish to obtain by providing high-level business requirements. This document establishes the basis for the agreement between the initiators and implementers of the project. The information in this document serves as input to determining the scope of Information Systems projects and to all Business Process Modeling and System s Specifications efforts. The ISO s Interconnection Management processes have evolved to support the growing number of requests throughout the state. While the other modules within have remained in alignment with their associated processes, the generation module has not. As interconnection requests increase, this gap places an increased administrative burden on the units within the ISO that support the generation project processes. These enhancements will streamline the process and improve the internal and external communication on the new and converting generation projects that are connecting to the CAISO grid. Updating the to meet the business needs will provide efficiency gains that will allow the current department to manage the increasing workload while meeting the needs of the market participants. 1.2 References All references represent external requirements documents or stakeholder requests developed and submitted by the Business Units. 1. Project documents are located at: Doc ID: GNFDMDEHU6BB Page 4 of 18

5 Business s Specification Date Created: 3/19/ Details of Business Need/Problem 2.1 Description The New Resource Implementation team receives three main types of generation projects: new CAISO grid connected, new distribution level connected, and Qualifying Facility (QF) conversions. The new CAISO grid connected resources arrive in the group for management after the Interconnection Agreement is executed. The App and Study module has the functionality to create a new project in the module once the project has reached a certain point in the GIA execution process so the NRI team can begin tracking. However, the new distribution level connected and the QF conversions do not enter the group s workload in this manner. Generally, they are received through requests so the team has to manually enter this information into the module. Recently, the group has seen a significant increase in the number of small generation projects that are connected in at the distribution level due to the PTOs efforts to meet the California Energy Commissions goal to increase procurement from renewable energy resources to 33% of total procurement by There are also a large number of QF conversions entering the implementation process because the existing contracts that are signed directly with the PTO are reaching their expiration date. As a result, these resources are required to convert to CAISO participating generators. This involves meeting all CAISO requirements (metering, telemetry, modeling, and contracts) and, therefore, the generator owners need the services of the New Resource Implementation team. There will be a steady flow of these QF conversions happening in the next decade as the contracts continue to expire. The module is an internal-only module of the that was developed several years ago based on the procedures in place at that point. Since then, the implementation processes have evolved and the current module does not support the increasing needs of the business unit. The checklists and responsible groups have changed due to the implementation process changes and reorganizations in the ISO. Therefore, these checklists are no longer an effective means of monitoring the status of each project The desired end state for the module comprises of an external facing component that enables interconnection customers to directly upload and maintain generation project information within, thereby reducing the administrative burden for all business units involved significantly. These enhancements will streamline the process and improve the internal and external communication on the new and converting generation projects that are connecting to the CAISO grid. Without these improvements, Operations is at risk of not being able to support the increasing workload with its current staff level. Doc ID: GNFDMDEHU6BB Page 5 of 18

6 Business s Specification Date Created: 3/19/ Business Process Impacts 3.1 High Level Business Process Description New Resource Implementation is the project management process required to implement all new and converting generation into the California ISO market. The New Resource Implementation team receives three main types of generation projects: new CAISO grid connected, new distribution level connected, and Qualifying Facility (QF) conversions. After an interconnection agreement is executed, the project managers guide the generation owners through the various requirements related to regulatory contracts, metering, telemetry, and network modeling in order to grant final approval to synchronize to the grid and to declare commercial operations. 4. Business s The sections below describe the Business Processes and the associated Business s involved in the project. These may represent high level functional, non-functional, reporting and/or infrastructure requirements. These business requirements directly relate to the high level scope items determined for the project. 4.1 Business Process: New Resource Implementation Security Roles Business s Doc ID: GNFDMDEHU6BB Page 6 of 18

7 Business s Specification Date Created: 3/19/2013 BRQ001 The security roles within the module must be revisited. Currently, users are granted access/rights on a user by user basis. This process must be eliminated and replaced by the following new consolidated roles: Admin Role Power User (Interconnection PM) Internal Read/Write Internal Read Only External User Interconnection Customer External User PTO BRQ002 The Admin Role must be the only user that can make changes to the Project templates, checklists, notifications, data fields, and contacts. All configuration changes shall be effective in real time for all projects created from that time forward. BRQ033 The module must provide user access for the interconnection customers (ICs) and Participating Transmission Owners (PTO). The user access must be granted based on both the entity and the specific user. The access permission processes shall be modeled after those already defined in the App & Study and Transmission modules. 4.2 Business Process: New Resource Implementation Internal Interface Business s Doc ID: GNFDMDEHU6BB Page 7 of 18

8 Business s Specification Date Created: 3/19/2013 BRQ003 The module must assign a unique Project Number to each generation project. The Project Number must be automatically assigned for each project when the project is created and must be displayed on the dashboard. BRQ046 In the module, Interconnection PM shall have the ability to accept and reject the automatically created project from the A&S project. User will review how to incorporate the project in the., App & Study BRQ004 The module must provide a configurable drop-down list of numeric values of Model Release Numbers for Interconnection PMs to select and associate a generation project to a specific model release (e.g. database build 58) The initial configuration must be set to show numbers from N/A must also be an option if modeling is not needed. BRQ005 The module must provide a consolidated set of checklists that are relevant for the business procedures today. As a result of this consolidation, outdated checklists may be removed or merged into relevant checklists. New System Operations and Queue Management checklists must be provided. BRQ006 The module checklists shall be made configurable so the internal Admin Role can update them in the future as the implementation process advances. The updates will only be applicable for future projects. Doc ID: GNFDMDEHU6BB Page 8 of 18

9 Business s Specification Date Created: 3/19/2013 BRQ007 The module checklists shall contain a contact for the responsible internal or external party. The contacts will be pre-established at the project template level. The internal Admin Role must have the capability to change the contact listed in the template for future projects. For current active projects, the Interconnection Project Manager role must have the ability to change the contact listed for each specific checklist. BRQ008 The Project level dashboard must be updated to give accurate high level project status based on the internal checklists. This dashboard must be visible on the external and internal interfaces. The project status must show where a project is in the New Resource Implementation process based off the defined bucket deadlines. The deadline dates shall be automatically generated based of the targeted initial synchronization date and commercial operation date for the project as given by the IC in the Resource Summary. s under each internal checklist will be associated with a bucket deadline date. This detail will be provided in the SRS. The algorithm for computing the project status percentages will be provided in the SRS. BRQ009 The requirements for each bucket deadline and project status percentages, as described in BRQ008, must be made configurable by the internal Admin Role. Doc ID: GNFDMDEHU6BB Page 9 of 18

10 Business s Specification Date Created: 3/19/2013 BRQ010 The Resource Summary page in the module must be updated to collect the appropriate project information from the IC that aligns with the current business processes. The fields on this page must be made configurable so the internal Admin Role can update them in the future as the implementation process advances. The changes in fields will only be applicable for future projects. The Interconnection PM will be able to manually configure the fields on current projects. BRQ011 The internal Interconnection Project Manager (PM) must have the rights to enter and edit the fields in the Resource Summary page. The generation module must keep an audit log of all changes to data fields visible to the Interconnection PM. The log will collect the data field changed, data changed, timestamp, and user. BRQ012 The module must contain project templates that are used after an initial web form has been completed by the IC. The templates shall contain all the same fields on the resource summary, except certain fields will be not applicable depending on the template chosen. The templates shall contain all the same fields on the checklists, except certain fields in the checklists will be automatically deemed Not Applicable depending on the template chosen. The Interconnection Project Manager must have the ability to override the fields declared Not Applicable. The templates must be made configurable by the Admin Role. Doc ID: GNFDMDEHU6BB Page 10 of 18

11 Business s Specification Date Created: 3/19/2013 BRQ013 The module must provide a mechanism for both internal and external users to upload file attachments to a specific generation project. Users (internal and external) must also have the ability to download these files from the module. Each project must have its own area to upload files specific to that project alone. module must support the capability to upload files of the following type: Word (.doc or.docx), Excel (.xls or.xlsx), PDF (.pdf), and Drawings (.dwg). Typical files are around 500 KB and each generation project generally has at least 50 documents. The module must track the timestamp and user by which each document was uploaded to a project. Note: Eventually want documentation to be cross referenced in all 3 s; however, this is out of scope for 4.5. BRQ014 Each generation project must have an area to hold the attachments that are available to both external and internal users. Upon uploading the user will assign metadata to each attachment. The specific metadata fields will be defined in the System s Specification. Both internal and external users must have the capability to filter by the various metadata fields within each project. BRQ015 The attachment metadata elements must be made configurable so the internal Admin Role can update them in the future as the implementation process advances and aligns with other business processes. Doc ID: GNFDMDEHU6BB Page 11 of 18

12 Business s Specification Date Created: 3/19/2013 BRQ016 The module must have the functionality for the Interconnection Project Manager to delete unwanted documents from a project. The Interconnection PM must be able to view a deletion log for audit purposes (file name, timestamp of deletion, and user). BRQ017 The module must be able to accommodate generation projects that have multiple Resource IDs. BRQ018 The module must be able to accommodate projects that have multiple Interconnection Agreements signed with the CAISO (more than one ISO Queue #). The module must be able to accommodate projects that share the same Interconnection Agreement (same ISO Queue #) with another generation project in. App & Study BRQ047 The module must be able to indicate if ISO Transmission is required for generation projects that are connected at the distribution level. BRQ019 The module must be able to associate generation projects with related transmission projects in the transmission module. This must accommodate the various ratios (multiple gen projects to multiple transmission projects). The module must be able to associate generation projects with related app and study projects in the App & Study module. This must accommodate the various ratios (multiple gen projects to multiple app and study projects). Transmission App & Study Linkage between these modules will remain out of scope for 4.5. Doc ID: GNFDMDEHU6BB Page 12 of 18

13 Business s Specification Date Created: 3/19/2013 BRQ020 The module must be able to accommodate and track generation projects that are implementing in multiple phases. Each phase will require at a minimum to collect the MW capacity, Synchronization Date, and Commercial Operation Date per each. Each phase will also need a free form text box for comments. The phasing information will be accessible to the IC and PTO users as well. module must be able to accommodate projects up to 100 different phase. These phases can be added at any point until the project reaches full commercial operation. Linkage between phases and the other two modules shall remain out of scope for 4.5. Additional phasing requirements will be incorporated in 5. BRQ021 The module must be able to maintain information for resources that want to participate in the PIRP Program, Station Power Program, Use-Limited Resource, Multi-Stage, and/or the Resource Adequacy Program. This tracking will be kept on the Resource Summary screen. Changes in attributes do not need to be tracked for auditing purposes. BRQ022 The module must be able to track generation projects that have telemetry or metering exemptions in place. The application must track the expiration dates of the exemptions and the application must have the ability to store comments regarding the details of the exemption. The application must send notifications to both the external IC and internal interconnection PM in advance of any of the dates and on the date when the exemption has expired. The dates by which the notifications are sent must be made configurable. Doc ID: GNFDMDEHU6BB Page 13 of 18

14 Business s Specification Date Created: 3/19/2013 BRQ023 The module must have the ability to send automated notifications to specific internal users when changes are made to a generation project (i.e. when a generation project is created by an IC, when fields in the resource summary are updated by an IC, and when documentation is attached to the project by an IC). Specifics of these notifications will be outlined in the SRS. The notifications must be made configurable so the Admin Role can change timing of notifications, recipients of notifications, and details in notification. BRQ024 The module must send notifications to the IC when bucket deadlines are approaching and their requirements have not been met to date (status is not at 100 percent complete). The notifications must be made configurable so the Admin Role can change timing of notifications, recipients of notifications, and details in notification. BRQ025 The module must provide the capability to send a status report (all fields on the interconnection customer checklist) via to the IC and the interconnection PM for a particular project, upon user submission of a request (e.g. upon click of a send-report button). There must be capability for the Interconnection PM to enter free-form text comments and include that in the report that is ed to the interconnection customer. The text-comments must be stored along with the report metadata (requesting user, time at which the report was generated/sent and the recipient address) for audit purposes. Doc ID: GNFDMDEHU6BB Page 14 of 18

15 Business s Specification Date Created: 3/19/2013 BRQ026 The module must provide the capability for an internal user to send a notification to another internal user assigned to a particular project, upon user submission of a request (e.g. upon click of a send-notification button in each internal checklist). There must be capability for the user to enter freeform text comments in the notification that is sent. The text-comments must be stored along with the report metadata (requesting user, time at which the report was generated/sent and the recipient address) for audit purposes. BRQ027 The module must have a capability for the Interconnection Project Manager to delete unwanted projects. Such projects must be maintained within the database for audit purposes but must not be displayed on the user interface. The Interconnection Project Manager should have the ability to view deleted projects. BRQ028 The module must display the following default project level fields and provide the corresponding filter criteria on the generation module dashboard: a) Unique Project Number (new field) b) Project Name c) Estimated Synchronization Date (ability to filter by range of dates) d) MW Capacity e) Fuel f) Model Release Number g) PTO Area h) Qualifying Facility (Yes/No Indicator) The module must permit multiple filters to be applied at once. The module must contain a clear all filters button. Doc ID: GNFDMDEHU6BB Page 15 of 18

16 Business s Specification Date Created: 3/19/2013 BRQ029 The module dashboard must sort projects by the following default criteria: a) Date Added (descending) b) Project Name Users must be able to click on any field on the dashboard title row and sort projects by that field, with an option to revert to the default sort criteria mentioned above. BRQ030 Each internal user must be able to define and save multiple preferences for their dashboard fields and sort order to match their individual business needs. (BRQ028 and BRQ029 list the default settings). There will be a defined set of data fields by which the internal user can chose from to place in their dashboard. BRQ031 The module must have the capability to export the contents of the dashboard as filtered into an excel workbook (i.e. all generation projects with Model Release Number = 58). 4.3 Business Process: New Resource Implementation External Interface Business s Doc ID: GNFDMDEHU6BB Page 16 of 18

17 Business s Specification Date Created: 3/19/2013 BRQ032 The module must have a webbased interface for external interconnection customers (IC) and Participating Transmission Owners (PTO). IC s must be able to use this application to access the status of their specific project through the implementation process and to share project documentation with the CAISO. PTO s must be able to use this application to access the high level status of the generation projects that are assigned to their PTO in the Interconnection Agreement. BRQ034 The module must allow IC s to create their generation project in the database by entering an initial web form. The initial form shall collect basic details such as project name, MW capacity, fuel type, connection type (grid or distribution level), Qualifying Facility (QF) status, etc. The IC input into these fields shall determine which pre-established template will be used for the project. The templates are further discussed in BRQ012. App & Study Interconnection PM must have the ability to accept or reject the creation of any new generation project. BRQ035 The external interface of the module shall provide an overview of each project status to the appropriate IC and PTO. The status shall be given in percentage complete at each bucket deadline. The percentages shall be determined using the checklists in the CAISO internal interface. External IC and PTO read/write permissions shall be developed for each internal checklist field and internal comment field. These permissions shall be made configurable by the Admin Role. Doc ID: GNFDMDEHU6BB Page 17 of 18

18 Business s Specification Date Created: 3/19/2013 BRQ036 The IC shall use the external interface to enter all project information into the resource summary fields. This information may be changed at any point by the IC while the project status is still active. The generation module must keep an audit log of all changes to data fields visible to the Interconnection PM. The log will collect the data field changed, data changed, timestamp, and user. BRQ037 The IC s must be able to upload documentation to the module into a specific project for internal parties to review. The IC s must be able to assign metadata to each document uploaded. The metadata is discussed further in BRQ014. Doc ID: GNFDMDEHU6BB Page 18 of 18