BESnet Release Notes August 8, 2014 and
August 13, 2014
Introduction
The list below contains a list of known defects for the August 8, 2014 and August 13 releases of BESnet. Known Defects
Known Defects
ID Area Description Create Entity‐ Submitting Entity Role When creating an ER under section 1 there is an option of YES or NO in regard to if the Submitting entity is the owner of the elements. Once the NO option is selected a search option is displayed to select the owner and choose the submitting entity’s role. If no owner is selected during the search, or if Submitting Entity Role(s) is chosen before the Owner, the selection will revert back to YES. 252 351 ER ‐ details 395 Click on the NO option again. All information (e.g. Submitting Entity Role) will be retained and displayed. When creating a SDN the “primary name” that gets populated in the Section 2 of the Notification gets automatically grabbed from the “From Point Name” field of the Edit Element screen? It would be more No work around needed; will be appropriate and user friendly to utilize either the cleaned up in a future release. “Common Element Name” or the “Circuit ID”. This change has not been consistently applied throughout the UI. Reports The export report Stage column is not showing text in all cases; in some, it is displaying a numerical value. No work around needed at this time; will be cleaned up in a future release. Reports In several reports, Primary voltage and secondary voltage is showing ‘HVDCxxx’ where ‘xxx’ is the actual voltage. For numerical voltages, ignore or trim the HVDC from the front of the value. When the user removes the Associated Entity, the NCR shows up in a pull‐down box. This text should be static. No impact; will be addressed in a future release. 401 414 Work‐Around ER Creation 420 Substantive Review 422 423 The display strips CRLFs from the comments (e.g., if I enter ‘Comment 1 <crlf> comment 2, ‘it retains that when in a text box, but when displayed as ‘label’ text, it displays as ‘Comment1 comment 2’ (all on one line). No work around needed. ER When adding a SOR, when you click back from the entity selection screen, the system takes you to the dashboard‐ Manually go back into the ER not to the ER. ER If the phone number is not filled in correctly, the ER will not save. Enter phone number correctly in the field provided. Initial Review‐
Rejected Once an ER is created and it is rejected by the region, the Initial Review documents cannot be read on the Decision tab (i.e. the hyperlink is disabled) for the Submitting Entity or the Owning Entity. The hyperlink is available to the Lead Region. Initial Review Documents are not available on the Docs tab when the ER is in a Reject status. Submit an Appeal (this sends the ER to Reject‐under appeal) and the docs are then available under the Docs tab. 485 Bug Fixes / Enhancements since the Initial Release into Production
The list below contains the Bug Fixes and Enhancements since the first release of BESnet into Production. Resolved Issues
ID Area 146 ER ‐ Create Description Additional Notes Added a question regarding Black Start service. Challenge Response‐UI When taking an action to approve/disapprove a challenge, the radial button popped up with ‘OK’ and ‘Cancel’ instead of the wording in the question. The pop up has been changed to reflect the following: ‘Are you sure you approve/disapprove the challenge? ‘Ok’ and ‘Cancel’ button TRP ‐ UI Changed label "There are no TRP's that can be assigned to this ER' to 'There are no TRP candidates available to be assigned to this exception Request' 208 267 BESnet Release Notes August 8, 2014 and August 13, 2014 2 286 Dashboard‐next action 329 330 Entity Management BESnet was not allowing Canadian zip codes to be reflected in the application. This issue has been corrected and Canadian zip codes are being reflected in the application. Entity Management Unable to modify entity role (e.g. submitting, BA). This has been corrected. User Management‐
Vetting When adding an entity to a user’s profile, a success message was returned when the check box to add entity is not checked and the Save button is clicked (meaning no entity was selected to be added). A validation rule was added to catch this error. ER‐Create Incorrect text when removing BES Definition Basis. The statement has been updated to reflect the following: ‘Remove BES Definition Basis’ Dashboard The status of an ER (approved or disapproved) is being concatenated to the ‘Stage’ but not to the ‘Status’. Overall changes to clarify state, status, and the use of filters were applied. The ‘back’ button on reports was not working. This has been corrected. SDN NEW FUNCTIONALITY: SDNs cannot be submitted (review completed) by the Region or NERC unless all the elements are in the same state (for regions, accepted or rejected; for NERC concurred or conflicted). In cases where they are not in the same state, a validation rule will tell the user they must split them to make each SDN only contain elements in the same state. SDN NEW FUNCTIONALITY: At the element level there is now a “pass” button next to ‘concur’ or ‘conflict’ to indicate when NERC elects not to review an SDN. The status can now be ‘concur, conflict or pass’. 332 356 368 376 When the next action = ‘Challenge’ is reflected; the date shown is the date for re‐certification. The date has been corrected to reflect the ‘Challenge’ date. Reports 377 378 BESnet Release Notes August 8, 2014 and August 13, 2014 3 379 SDN NEW FUNCTIONALITY: The SDN will drop into SD in NERC review as soon as the region completes their initial review. SDN NEW FUNCTIONALITY: The SDN is considered ‘Archived’ if NERC Concurs (Reject‐Concur) with the regional rejection of the SDN. The term “Archived” has been be replaced with “Terminated.” SDN NEW FUNCTIONALITY: If NERC Passes (Reject‐Pass) on the SDN (by clicking a new ‘Pass’ button within the SDN screen for NERC users), the SDN is considered ‘Archived.’ The term “Archived” has been be replaced with “Terminated.” SDN NEW FUNCTIONALITY: If NERC Conflicts (Reject‐
Conflicted) with the regional rejection of the SDN, the SDN is considered ‘Certified’. SDN NEW FUNCTIONALITY: If NERC Concurs (Accept‐Concur) with the regional acceptance of the SDN, the SDN is considered ‘Certified’. SDN NEW FUNCTIONALITY: If NERC Passes (Accept‐Pass) on the SDN (by clicking a new ‘Pass’ button within the SDN screen for NERC users), the SDN is considered ‘Certified’ SDN NEW FUNCTIONALITY: If NERC Conflicts (Accept‐
Conflicted) with the regional acceptance of the SDN, the SDN is considered ‘Archived.’ The term “Archived” has been be replaced with “Terminated.” SDN NEW FUNCTIONALITY: The system shall have the following Status: NEW RE Review Complete (accepted/rejected); NERC Review Complete + (accepted/rejected, based on concatenation of both RE and NERC review Overall changes to clarify state, status, and the use of filters were applied. SDN NEW FUNCTIONALITY: The system shall have the following Stages: Regional Review, NERC review and <Blank>. Overall changes to clarify state, status, and the use of filters were applied. SDN General clean‐ up of the UI needed to ensure consistency and accuracy‐ the SDN screen still shows ‘Exception Request’ labels. These incorrect references were removed. 380 381 382 383 384 385 386 387 397 BESnet Release Notes August 8, 2014 and August 13, 2014 4 398 400 402 404 405 SDN Regional Review The language under the Elements tag of a SDN was corrected to align with the buttons (the Region Status in the grid should be 'Accepted’ not ‘Approved’. Dashboard The dashboard was changed to include abbreviated types to SDN and ER (SDN‐I and SDN‐E, ER‐I and ER‐E). Reports The 'IsRF’ flag in the export report has been changed to “IsRFC,” and now accurately reflects the status.. Reports The internal and external IDs were added to the Export reports. Reports The ‘Elements’ Report was not displaying the ‘Current BESnet Definition Status’; this has now been fixed. Reports The Excel Export report is only exporting 100 characters for text fields. We have expanded this to allow for more data to be shown. Reports 'Is Rejected' and 'Is Approved' values displaying incorrectly in export report. The report was fixed and data is reflecting as needed. Splits NEW FUNCTIONALITY: The ability to split an SDN in ‘NERC Review’ was enabled. ER, SDN The ‘Elements’ table in the Documents tab was removed. This table was removed as it caused problems for entities including lots of elements in a single submission. Reports An Administrative version of the Element Export report was created for the NERC admin role. SDN Printed Report The primary and secondary voltages reported on the summary were incorrect. This has been corrected to display the correct voltages. Known defect 401 applies; voltage is displayed as HVDCxxx, where xxx is the correct voltage. ER/SDN The Counter used to create the last five digits of the ER identifier was based on record counts, and incorrectly assigned the same number to multiple requests. This resulted in an error display to the user. The counter has been modified to eliminate this problem. Note that if an SDN or ER is returned to draft, when it is resubmitted, it will be assigned a NEW ID. 406 407 408 409 410 411 412 BESnet Release Notes August 8, 2014 and August 13, 2014 5 413 429 Z#619 432 Reports An Administrative version of the ER Export report was added for the NERC Admin role. Element Export (Production Issue) Data reflected in the Element Report was inaccurate. The report has been corrected to ensure the correct data is being displayed. Reports The System Administrator was given access to view the Full data reports from the UI. UI The address on the Help Link in BESnet was changed to reflect: http://www.nerc.com/pa/RAPA/Pages/BESnetHelp.aspx SDN An attempt was made to create a notice of Self Determination for Potomac Electric Company which has a Washington DC address. Drop down menu for states did not contain DC as a selection. The District of Columbia and Canada were added to the drop down menu for address information. Add Element Changes were made to the labels related to ratings. MVA Rating‐ For Element Types, field and optionality was modified as follows: GEN (Gross Nameplate Rating in MVA, Req’d) CKT (Normal Rating in MVA, Req’d DC Conv (Normal Rating in MVA, Req’d) Shunt (Normal Rating in MVAR, Req’d) Network (NA, Not Req’d) Add Element ID‐ For Element Type Circuit, ID (Circuit ID) was changed to be a required field. Terminated filter Incorrect assignment/filtering of a Challenged ER was corrected. Challenge filters The UI was adjusted to make ‘Challenge’ and filter information clear (i.e., show the decisions made during the challenge phase). 433 486 Z# 640 xxx yyy SSF SSF2 BESnet Release Notes August 8, 2014 and August 13, 2014 6