Home

System Data Exchange (SDX) Users Manual

1. N re A by X NM A LF A i NERC gi SS 6 6LUmUmle NORTH AMERICAN ELECTRIC RELIABILITY CORPORATION P K A _ FT NYJ T t N Cas 7 x D B S a i Vi yH AAN Zf j H i WY 8 DRWY Sh T i m Data Exchange Manual Revision 8 steer e f bul July 2008 0 amp 116 390 Village Blvd Princeton NJ 08540 609 452 8060 609 452 9550 fax www nerc com System Data Exchange SDX Users Manual Table of Contents Record OL REVISIONS aterscosten ss scnactateres tenet acs a dawn ment dances aadaen 3 General PAI OM MAU OM sasies a aaa a 4 MENOU LOCION Saanen cutis ad tates lista etd Poaceae ie eee acti ales 4 Web User Interface Specifications c cccccscsscssssssssssessecssesseessesessessseeseesseseesesnsateess 4 PONT MOCHIMCA ODDO openan 4 NERO AGmMminiS Wann S sosina aaa emeieuactine 4 Data Flow And iming Diagram xa ccnesciarcssa sen sexsnavivei east ddavectenssuntaastweresinnsinedidauemeteenniaie 5 SDA ADPICATIGM ay OUT armana hud taaticanmeniendinet dais 6 User IVAN OI ANG E crsa cae ee cca vena adien eter Dn edcrers laus dee eee 7 Requesting an Individual User ACCOUNL c cccccsscscscsssssssrsssssscecesrsirsrsersersee i Requesting an Automated Access Account cccccsccsssssrssrsssserssr
2. This field must read MRID On the lines below this field the future NERC Master Resource Identifier MRID will be up to a 32 byte glo bally unique identifier This will be implemented in the future and is an optional field until then C 8 Control Area Transmission Data TRANSMISSION OUTAGES This field must read TRANSMISSION OUTAGES and will be on a line of itself This field indicates the start of the transmission data for the Control Area that the SDX data is being submitted FR TLINE This field must read FR TLINE On the lines below this field one of the 18 character transmission bus identifiers for transmission line should be inserted This identifier shall include the 12 characters of the PSSE BUS Name along with the appended 6 digit KV Level of the transmission bus such that the field is 18 characters long and has a character in the 18th place holder i e 6COWANS2 230 00 or 6MORN ST 230 00 FR TLINE PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the FR TLINE FR TLINE data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV l nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE
3. 12 31 2075 23 59 overlaps with the date range 12 31 2007 23 59 12 31 2075 23 59 Entries combined and accepted 01 07 2005 11 19 25 Warning IMO IMO CSV Warning For BECK1 G613 8 1 the date range 01 03 2005 03 00 01 07 2005 18 00 overlaps with the date range 01 07 2005 10 34 01 07 2005 18 00 Entries combined and accepted 01 07 2005 11 19 25 Warning IMO IMO CSV Warning For BECK2G1313 8 2 the date range 08 09 2004 13 15 03 05 2005 18 00 overlaps with the date range 01 07 2005 10 34 03 05 2005 18 00 Entries combined and accepted vent LO Back Search Today s Date 1 7 2005 Event TYPE rp ouput Process O FTP XML Input Process Model Upload Process ORCIS Output Process Results 14 records found Date _ Severity Event Text 10 15 2004 07 57 57 Informative Case 200410tr8 V28 30 was brought online 10 15 2004 07 57 57 Informative Case 200410tr8p1 27 was brought offline 10 14 2004 18 21 00 Informative Case file load completed in 04 21 37 The file contained 183288 lines vento Back Search Today s Date 1 7 2005 Event Type From z005 YP O FTP output Process O FTP XML Input Process ems oe seve ciie Results 3 records found Date Event Text 01 07 2005 09 40 09 Informative Forced Outage sent to NERC RCIS 6BUCKHEA 230 6LINDBRG 230 ID 1 Bus ID 16034 16337 01 07 2005 09 40 08 Informative Forced Outage sent to NERC RCIS 6BOULVRD 230 6LINDBRG 230 ID 1 Bus ID 16033 16337 01 07 2005 09 19 08 I
4. setGeneratorOutage All other fields are optional If no other fields are provided this allows the client to remove all outages for a control area To save an outage the following items are required Plant GeneratorSeq BeginDate Page 40 Revision 8 SDX Users Manual Appendix B XML Processing Required Fields Notes SetLoad RC TZ CA Timelnc EffectiveDate SetTransformerCommonName IBusName JBusName KBusName CircuitID SetTransformerOutage Page 41 and OutageType MW Each upload will fully replace the existing generator outage data except for the logic applied for overlapping outages NetMW OpResMW PeakMW and Hour are optional The Hour element should be supplied for Daily or Hourly data CommonName and PostToRCIS are optional If the PostToRCIS is True then the common name is required If the required fields are provided and no CommonName is provided the CommonName will be deleted All other fields are optional If no other fields are provided this allows the client to remove all outages for a control area To save an outage the following items are required IBus JBus KBus CircuitSeq BeginDate and OutageType Each upload will fully replace the existing transformer outage data except for the logic applied for overlapping outages Revision 8 SDX Users Manual Appendix B XML Processing B4 0 Error management General Errors The web service will return a lt GeneralError gt if the i
5. 161 kV Nantahala F STUCKASE 161 11173 SWEBSTER 161 11174 1 161 0000 Tuckasegee Webster 161 kV Nantahala d 5WESTS M 161 11171 5TUCKASE 161 11173 1 161 0000 Wests Mill Tuckasegee 161 kV Nantahala oO Selecting download will retrieve the results in a cn formatted file Sample cn File Format CONTROL AREA DUK BEGIN GENERATOR Case ID Generator Bus Name Unit ID New Common Name Post to RCIS 87 1BEARCRK 4 1600 1 BEAR CREEK HYDRO 4 16 kV 0 87 1BUZZHYD 4 1600 1 BUZZARD ROOST HYDRO 4 16 kV UNIT 1 0 CONTROL AREA DUK BEGIN BRANCH Case ID From Bus Name To Bus Name Circuit ID New Common Name Post to RCIS 87 BCATAWBA 230 00 6NEWPORT 230 00 1 Catawba Newport 230 kV Newport B 0 87 6CLIFSID 230 00 6PACOLET 230 00 1 Cliffside Pacolet 230 kV Goucha B 0 CONTROL AREA DUK BEGIN TRANSFORMER Case ID I Bus Name J Bus Name K Bus Name Circuit ID New Common Name Post to RCIS 87 3WATRE 115 00 WATEREE 100 00 1 Wateree 115 100 kV 0 Page 32 Revision 8 SDX Users Manual Appendix B XML Processing B1 0 Considerations for Automated XML Processing B1 1 Summary of automated processing Each company must build a process to send the desired outages to the SDX This process must review known outages on their system and decide whether or not to send the outage and establish a start end
6. 200401tr c 4 Ls Control Area lt Search All gt Ky 500 a k PMAX O Only elements with no common name Include Branches CJ Inctude Generators Cinctude Transformers Search Bus Names and or Circuit Unit ID s that exist in Case A that were not present in Case B Generators buses with a Pmax variation between the two cases will not appear in these results Page 17 Revision 8 System Data Exchange SDX Users Manual 7 3 View Changes by Control Area CA Changes Modifications to outage schedules are tracked and can be viewed for all control areas To view modified outages click on CA Changes in the Reporting menu The default will show changes made within the past 48 hours but ule can be ee to any a digit whole number lif Today s Date 1 7 2005 Branch Modifications Generator Modifications Transformer Modifications lt P 5 4 IMO 530 420 a 953 If any a detailed list of schedule changes for a Control Area for the time period specified can be viewed by clicking on the Control Area link Resulting outage schedules can only be modified for your local Control Areas with which you have control Modified Outages for Control Area IMO during the last 48 hours Today s Date 1 7 2005 k 953 Records found Bus Circuit ID Common Name KV Status End Date MANBY E 118 RUNYMK12 118 1 K12W 118 118 Out of Service 7 WILTS H2 118 RUNYMK12 118 1 K12W 118 118 Out of Servi
7. 39035 1 138 flee tee beotnenenatred Out of Service lf there are currently outages entered for the element they will be displayed for the element selected To modify select the appropriate outage schedule by clicking on the From Bus link To delete the outage click on the red X To add a new outage for the selected element click on New Branch Save Back Delete Today s Date 1 7 2005 From Bus Name NED 138 138 39020 To Bus Name LAN 138 138 39035 Circuit ID 1 Common Name KV 138 Begin Date and Time HH24 MM ELLIE EE End Date and Time HH24 MM EH EE Initial Status Out of Service Outage Type Out of Service Inserted p a A Last Updated Once complete click on Save A2 1 Entering Outages for Branches that are Tie Lines If the From Bus is modeled in a different control area as the To Bus the branch is designated as a tie line When an outage for a tie line is entered into the system the system designates which control area has ownership of the outage entry If the user that is logged into the system has editable rights to only one of the control areas the control area that the user has editable rights to is designated as the owner If the user that is logged into the system has editable rights to both control areas the user must select which control area is designated as the owner Outage entries for tie lines that have been made by a control area for which the user does not have editab
8. BUS Name MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications TO TLINE This field must read TO TLINE On the lines below this field one of the 18 character transmission bus identifiers for transmission line should be inserted This identifier shall include the 12 characters of the PSSE BUS Name along with the appended 6 digit KV Level of the transmission bus such that the field is 18 characters long and has a character in the 18th place holder i e 6COWANS2 230 00 or 6MORN ST 230 00 TO TLINE PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the TO TLINE TO TLINE data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE BUS Name MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications ID This field must read ID On the lines below this field the 1 2 character transmission line circuit identifier should be inserted This identifier shall include the PSSE Circuit Id that represents the transmission line being entered i e 4
9. Bus 2 Circuit ID 1 is required when the Post To RCIS option is selected Failure Template_AddUpdate_ActualTransformer Failure Template_AddUpdate_ActualTransformer pLoad_ProcessTransformer Line X Entry for Tie Line _Bus J_Bus 1 has already been made by CA This CA cannot alter this entry WARNING All existing outages will be removed for CA Failure RC does not have control for the CA control area Error There is no online case Line X Element _Bus J_Bus 1 WARNING Outage in the past will not be loaded Line X Element _Bus J_Bus 1 INVALID Begin Date Begin Date must be a valid date and cannot be less than or equal to the End Date Line X Element _Bus J_Bus 1 INVALID OUTAGE Line X Element _Bus J_Bus 1 was not found in control area CA Line X Element _Bus J_Bus K_Bus 1 was not found in control area CA Line X _Bus J_Bus 1 was not found in control area CA Line X _Bus J_Bus K_Bus 1 was not found in control area CA Failure Template_AddUpdate_ActualGenerator Failure Template_AddUpdate_ActualGenerator pLoad_ProcessGenerator Failure RC does not have control for the CA control area Error Invalid Begin Date for Plan Line cannot be processed Error Invalid End Date for Plant 1 Line cannot be processed End Date cannot be the same as the Begin Date Error Invalid End Date for Plant 1 Line cannot be processed Error Invalid End Date for Plant 1 Line cannot be p
10. Control Areas list and click the lt button e Toaddacontrol area to your Home Page select it in the Available Control Areas list and Click the gt button e Tochange the order in which the Control Areas appear on the Home Page click on the Control Area in the Selected Control Areas column to highlight the Control Area then poke the up or down arrow as desired to move the Control Area up or down the list e When you are done click Save NERC System Data Exchange Change Timezone Save Current Timezone Eastern Daylight Saving Time EDT New Time Zone Eastern Daylight Saving Time EDT Control Areas Available Control Areas Selected Control Areas Use Cir Left Mouse Click or Shi Left Mouse Click to multi select 5 2 Selecting Outage Data to be Displayed Home Page Search Today s Date 1 7 2005 End Date 1 7 2005 ME Outage Type All E sortBy bus Name kvmw Beginning On Ending On O Active During Change Control Area List ALTE ALTW AMRN CPLE DUK FES IMO ISNE MEC MHEB NSP OKGE PJM SoCo BERBER BRBRBRB BRB RBBB RB eee ii BEB eee eee eee o tinegin Date 1 7 2005 fe End Date 1 8 2005 e O Beginning On Ending On amp Active During e Selecting Beginning On will cause the Home Page to display all outages which have a begin date that occur on the selected date e Selecting Ending On will cause the Home Page to display all outages which have an end date
11. STATUS This field must read STATUS On the lines below this field one of the following options must be chosen where each status indicates the element is O Out Of Service for the time stated I In Service for the time states P Derated to a level less than its maximum These additional status options are available to further clarify the status of the generator These will provide additional information to the SDX users about the type of generation outage F Forced Out of Service for the time stated and is then communicated to the RCIS SF Offline but can be brought on line in 1 2 hours Standby Fast SS Offline but can be brought on line in 3 or more hours Standby Slow PS Pumping and is acting like a load for the time stated SVC Is out of service for the time stated and is a Static Var Compensator COMMON NAME This field must read COMMON NAME On the lines below this field any 50 character identifier can be entered This is generally used so that the user can understand what element is being represented with the SDX entry MISCINFO This field must read MISCINFO On the lines below this field an optional 16 alohanumeric character identifier can be entered This is a miscellaneous field and is not used by the IDC and SDX application However it can be used for internal communication of information at the user s discretion MRID Page 48 Revision 8 SDX Users Manual Appendix C CSV Output File Format
12. begin date of an outage that has already started Changing the status of an outage that has already started with set the end date of the existing entry to now and create a new entry with a begin date of now with the new status To set the piece of equipment back to its base case status change the end date of the entry to now Deleting an outage that has a begin date before the current date will set the end date to the current date and time Deleting an outage that occurs entirely in the future will remove the outage from the system Note Wildcard character can be used to search for partial Bus Common Names Branch Search Today s Date 1 7 2005 Contral Area From Bus Name mo TopusName o y Common Name Outage Type Search All gt ey Oe cece a Denotes that a branch has outages 19 Records found EE EE ee eee ee NED 138 138 39020 LAN 138 138 aoa 138 NED 138 138 39020 POT 138 138 39030 1 138 NFL 138 138 39175 AVIATION 138 39677 1 138 NFL 138 138 39175 EST 138 138 39197 1 138 NERC System Data Exchange Today s Date 12 7 2007 0 Outages found lf an element is selected that has not outages currently defined the resulting screen will be blank Selcted New to enter a new outage for the element Page 28 Revision 8 SDX Users Manual Appendix A User Interface NED 138 138 39020 Today s Date 1 7 2005 1 Outage found Say gy E Begin Date 0 LAN 138 138
13. match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications 1D This field must read ID On the lines below this field the 1 2 character generating unit identifier should be inserted This identifier shall include the PSSE Unit Id that represents the unit being entered i e 4 or HL START DATE This field must read START DATE On the lines below this field the date in which the SDX entry is to start to take effect should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to start to take effect should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STOP DATE This field must read STOP DATE On the lines below this field the date in which the SDX entry is to end should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to end should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STATUS This field must read STATUS On the lines below this field one of the following options must be chosen where each status indica
14. menu after logging in After selecting the new time zone click Save The system stores all dates and times in the UTC time zone and converts them to the time zone your account specifies NOTE All dates and times in the SDX Output Files will be in the EST time zone Change Timezone Back Save Current Timezone Central Daylight Saving Time CDT New Time Zone Central Daylight Saving Time CDT Control Areas Available Control Areas Selected Control Areas E Use Ci Left Mouse Chk or SAHT Left Mouse Clot fo mulf seect You will need to change your time zone manually to reflect daylight savings changes Upon logging in the system will notify you of the upcoming daylight savings day two days in advance You should make this change prior to entering any data after the time change NERC System Data Exchange Remember to change your time zone on 10 26 2003 Page 11 Revision 8 System Data Exchange SDX Users Manual 5 0 Customizing Home Page Setup After logging in you will first arrive in your Home Page The menu is generated based on approval rights of the user Not all users will have the same menu options The data displayed on the Home Page can be personalized for each user Control Area data on the Home Page may be expanded or collapsed as desired The system will save the state of the Home Page so that the Control Areas are in the same expanded collapsed state the next time the user logins
15. that occur on the selected date Page 13 Revision 8 System Data Exchange SDX Users Manual e Selecting Active During will filter the results to display outages that occur in any part of the date range e The Outage Type option will cause the Home Page to display only outages that have the selected outage type e The Sort By option causes the Home Page to sort the data displayed by either Bus Name or KV MW e Clicking on a control area link at the top of the Home Page will navigate directly to the control area s data on the page e The options selected will be remembered the next time you login 5 3 Accessing Data from the Home Page For each control area listed these sections will be displayed Branches Generators Transformers Element Groups Daily Load If the data is editable a link will appear The user account must have security access to edit any data in the system Also no data that occurs in the past may be edited If an entry occurs entirely in the future a red X will appear which will allow the user to delete the entry Branches From Bus K NMA138 1 138 Fas WAU 138 138 Generators To Bus COL 136 136 SAL 138 138 Circuit ID Common Name i Out of Service 138 Out of Service Begin Date End Date 01 02 2005 08 00 01 28 2005 18 00 O1 04 2005 08 00 01 14 2005 18 00 Bus K sFL6412 4 Transformers Capability Unit ID Common Name 0 PMAX Status Begin Date End Date Forced Outag
16. their information is being used by their neighbors and so that they understand the source of the information that is received from its neighbors In many cases the data submitted to the SDX is coordinated between neighbors through joint operating agreements Should each submittal include all outages or only changes from the previous upload The outages submitted for an element type at any given time through the XML will be the ONLY outages present for that element type therefore all expected outages must be sent in each XML upload If only the incremental changes are sent that limited set of outages will be the ONLY outages in the system for that element type What is the interaction between the XML uploads and GUI A user should not normally use a combination of the XML process and the GUI to manage their outages If a user has an automated XML process any outages submitted in the GUI will be overwritten by the next XML upload However if there is a problem with a user s XML process the GUI can be used to manage the current set of outages until that automated process is restored How to change the start time of an expected outage The start time of an outage is assigned based on the specific data in each XML upload If the expected start time of the outage has changed and the new start time is included in the next XML upload that new start time will overwrite the previous start time The history of the uploads for any particular item can b
17. 0 kV nnn nn e 10kV lt Bus kV lt 100 kV nn nnn e Bus kV lt 10kV n nnnn Revision 8 B1 3 B1 4 B1 5 SDX Users Manual Appendix B XML Processing Overlapping outages In general outages with overlapping times should not be sent to SDX The user should pre process their outage data so that these overlapping outages are not submitted However there is some logic contained in the SDX to rank certain outage types e For any outages of different types where the End Time of one outage equals the Start Time of another outage the End Time will adjusted back by one minute since the Start and End of two different outage types cannot be equal Note if they were of the same outage type the outages would appear to be merged into one longer outage e fan outage of type F overlaps with any other outage type the outage type F will be taken as submitted and the start stop time of the other outage type will be adjusted accordingly If the type F is in the middle of the other outage there will be three resulting outages e fan outage of type O overlaps with an outage of type P or HT the outage of type O will be taken as submitted and the start stop time of the other outage will be adjusted accordingly e On generation only if two outages of type P are overlapping with a different MW value all conflicting outages will be ignored and there will be no outage recorded for that timeframe Outages for
18. 2fo6 2007 Branch Outage delete function was selected From user interface The outage For 6WILLIGM 23012011 13 13 00 Corson 15 30 18 13 BCHARITY 2300135003 Circuit ID 1 Begin date 12 11 2007 14 15 End date 12 11 2007 15 30 was deleted 12 05 2007 System 12 10 2007 12 05 2007 6CLIFFDA 230 6P1 Fay 230 Bus ID 103860 103871 Circuit ID 99 end date was changed with the 18 07 14 Operator 22 30 23 15 begin date of 11 28 2007 20 40 12 04 2007 Derek Elele 12 06 2007 12 05 2007 Branch Outage delete function was selected From user interface The outage For 6WATEREE 230i 12002 23 08 00 Y 22 00 04 08 BOL IND 230612204 Circuit ID 1 Begin date 12 06 2007 13 00 End date 12 06 2007 22 00 was deleted 12 03 2007 System 12 05 2007 12042007 SROCKY M 115 SBTLEBRO 115 Bus ID 102230 14554 Circuit ID 1 end date was changed with the 22142155 Operator 01 00 04 00 begin date of 12 03 2007 18 38 6 2 Event Log SDX Event Logs can viewed in the Web UI There are four categories of events FTP Output Process FTP XML Input Process Model Upload Process and RCIS Output Process The date range selected is by default the prior 15 minutes The Event Log page will automatically refresh every five minutes Pf ventbog O OOOO S O Back Search Today s Date 1 7 2005 laew Event Type From 1 7 2005 SE 11 13 YPE FTP Output Process RC ISNE g O FTP XML Input Process To 1 7 2005 z 11 29 O Model Upload Process Severity All ORCIS Outpu
19. AK MW NET I C OP RES MW HOURLY DATA PEAK MW HREND NET I C OP RES MW GENERATOR OUTAGES PLANT ID MW START DATE TIME STOP DATE TIME STATUS COMMON NAME MISCINFO MRID TRANSMISSION OUTAGES FR TLINE TO TLINE ID START DATE TIME STOP DATE TIME STATUS COMMON NAME MISCINFO MRID Page 24 Revision 8 System Data Exchange SDX Users Manual PAR TAPS FR BUS TO BUS ID TAP START DATE TIME STOP DATE TIME COMMON NAME MISCINFO MRID ELEMENT GROUPS ELEMENT GROUP ID START DATE TIME STOP DATE TIME STATUS COMMON NAME MISCINFO MRID THREE WINDING XFMERS yk ID START DATE TIME STOP DATE TIME STATUS COMMON NAME MISCINFO MRID The above format is repeated for each Control Area that is being reported in a csv file If the Control Area has no entries for a section of the file the headings for the section are included in the file along with the placeholder for the field with no data beneath them Appendix C contains a breakdown of each section of the file into its individual fields for more clarification A sample file that is populated with data can also be found in Appendix C Page 25 Revision 8 SDX Users Manual Appendix A User Interface This appendix describes how to enter data into the SDX using the User Interface A1 0 Entering Load Data To enter Load data selec
20. Branches that are Tie Lines lf the From Bus is modeled in a different control area as the To Bus the branch is designated as a tie line When an outage for a tie line is entered into the system the system designates which control area has ownership of the outage entry If the user that is logged into the system has editable rights to only one of the control areas the control area that the user has editable rights to is designated as the owner If the user that is logged into the system has editable rights to both control areas the user must select which control area is designated as the owner Outage entries for tie lines that have been made by a control area for which the user does not have editable rights can be viewed but are not editable Data sent to Reliability Coordinator Information System RCIS A subset of the outages submitted to the SDX are passed on to the RCIS The outages meeting the following criteria are sent to the RCIS If the type of the outage is F on transmission elements 220kV and above and generators 300MW and above e And the start time of the outage is more than 5 minutes in the past then the outage will NOT be sent to the RCIS e And the start time of the outage is 5 minutes or less in the past then the outage WILL be sent to the RCIS e And the start time of the outage is MORE THAN ONE HOUR in the future then the outage will NOT be sent to the RCIS Page 36 Revision 8 SDX Users Manual Appendix B XML
21. E This field must read STOP DATE On the lines below this field the date in which the SDX entry is to end should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to end should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 Page 51 Revision 8 SDX Users Manual Appendix C CSV Output File Format COMMON NAME This field must read COMMON NAME On the lines below this field any 50 character identifier can be entered This is generally used so that the user can understand what element is being represented with the SDX entry MISCINFO This field must read MISCINFO On the lines below this field an optional 16 alphanumeric character identifier can be entered This is a miscellaneous field and is not used by the IDC and SDX application However it can be used for internal communication of information at the user s discretion MRID This field must read MRID On the lines below this field the future NERC Master Resource Identifier MRID will be up to a 32 byte globally unique identifier This will be implemented in the future and is an optional field until then C 10 SDX Element Group Data The Element Group section of the file is used to communicate SDX information about multiple power system el
22. IDC and SDX application However it can be used for internal communication of information at the user s discretion MRID This field must read MRID On the lines below this field the future NERC Master Resource Identifier MRID will be up to a 32 byte globally unique identifier This will be implemented in the future and is an optional field until then C 11 Three Winding Transformer Data THREE WINDING XFMERS This field must read THREE WINDING XFMERS and will be on a line of itself This field indicates the start of the Three Winding Transformer data for the Control Area that the SDX data is being submitted T This field must read I On the lines below this field the PSSE BUS NAME identifier for the first winding of the transformer should be inserted l PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the field Data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 l nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE BUS NAME MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications J This field must read J On the lines below this fi
23. ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21 2008 3 05 52 PM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 07 00 20086 05 00 4 21 2008 2 05 52 PM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 006 07 00 006 05 00 4 21 2008 1 05 50 PM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 0r 00 008 05 00 4 21 2008 12 05 54 PM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 07 00 2008 05 00 4 21 2008 11 06 06 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 008 05 00 4 21 2008 10 05 44 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 07 00 008 05 00 4 21 2005 9 05 59 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 008 05 00 4 21 2006 6 05 56 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21 2008 7 05 59 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21 2008 6 05 49 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21 2008 5 05 49 AM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 Page 19 Revision 8 System Data Exchange SDX Users Manual 7 5 Regional Coordination Report This feature allows a report to be created where users can easily view outages in another control ar
24. Processing e And the start time of the outage is ONE HOUR OR LESS in the future then the outage WILL be sent to the RCIS Notes Page 37 1 Reducing excessive RCIS entries If an outage has been repeatedly submitted with a status of F such that the first time the outage was submitted was MORE THAN ONE HOUR in the future that outage WILL NOT be sent to the RCIS when the start time of the outage moves within the one hour window This ensures that only short term issues are reported to the RCIS Repeated RCIS entries If an element is submitted repeatedly with a different start time and each submittal of that outage is within one hour of the Start Time that element will be sent to the RCIS will each file upload For example if a process exists where EMS data is compared to an outage scheduler system and discrepancies are submitted with type F and a start time of the current time that element will be reported to the RCIS with each upload since the Start Time is unique with each upload and falls within the defined parameters Multiple apparent RCIS entries The RCIS displays the common name on the element outages sent from the SDX If the user has defined multiple SDX elements to have the same common name it can appear that duplicate SDX outages were sent to the RCIS To avoid this it is recommended that the exact same common name not be used for multiple SDX elements Revision 8 SDX Users Manual Appendix B XML Process
25. SE Base KV in the 18th position of the TO BUS TO BUS data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV l nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE BUS Name MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications 1D This field must read ID On the lines below this field the 1 2 character Phase Shifter circuit identifier should be inserted This identifier shall include the PSSE Circuit Id that represents the Phase Shifter being entered i e 4 or lg TAP This field must read TAP On the lines below this field the tap position of the Phase Shifter for the SDX entry will be inserted This should be a 1 3 digit value that can be negative START DATE This field must read START DATE On the lines below this field the date in which the SDX entry is to start to take effect should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to start to take effect should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STOP DAT
26. SNE DUPONT 115 AMES ST 115 1 D 911 Add Equipment ISNE PONT18 7 115 AMTRK18 115 1 1187 1 Add Equipment ISNE PONT188 115 AMTRK188 115 1 188 1 Add Equipment ISNE SCOB 345 345 AMHST345 345 1 380 Add Equipment ISNE VTYNK345 345 AMHST345 345 1 379 Add access to elements To provide access to other control areas selected Assign Remove RC and select the RCs that should be granted access to this element Page 21 Revision 8 System Data Exchange SDX Users Manual NERC System Data Exchange Back Save Print Today s Date 3 25 2008 Facilities List Name pa New o RC E Dist ECEN Result View Ocrid csy XML a_i a Sales Read Access for the following RC l Remove Equipment ISNE DUPONT 115 AMES ST 115 D 911 ISNE Assign Remove RC RC List Cancel Save Page 22 Revision 8 System Data Exchange SDX Users Manual 7 9 2 Running the Report When a user wants to view the outages from other areas they select Regional Coord Rpt enter the desired date range and select the desire report from the Facility View dropdown list All outage that they have permission to view that are active in the selected timeframe will be displayed Search Regional Coordination Report Search Filters Control Area Dates W FE L T FH Facility view Beginning On Ending On Active During Result View Grid coy xm Today s Date 3 25 200 Print NERC System Data Exchange Region
27. US Name along with the appended 6 digit KV Level of the bus such that the field is 18 characters long and has a character in the 18th place holder i e 6MORN ST 230 00 or 8MCGUIRE 500 00 FR BUS PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the FR BUS FR BUS data submissions need to be 18 character ABCDEFGHIJKLnnnn n Page 50 Revision 8 SDX Users Manual Appendix C CSV Output File Format Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 l nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE BUS Name MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications TO BUS This field must read TO BUS On the lines below this field one of the 18 character bus identifiers for the Phase Shifter should be inserted This identifier shall include the 12 characters of the PSSE BUS Name along with the appended 6 digit KV Level of the bus such that the field is 18 characters long and has a character in the 18th place holder i e 6MORN ST 230 00 or 8MCGUIRE 500 00 TO BUS PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PS
28. a Maintenance menu Use the search criteria to limit your results by case control area common name bus name KV or only elements with no common name Choose branch generators or transformers Selecting search will display the results to the user In the results page the common name can be modified Page 31 Revision 8 SDX Users Manual Appendix A User Interface for each element Additionally you may set the element to notify the NERC RCIS tool if an outage is entered Elements marked to send to the NERC RCIS tool must have a common name entered Common Name Maintenance 10 Records Found Back Save Print Download Branches SLAKEMRY 161 11170 SWEBSTER 161 11174 1 161 0000 Lake Murray Webster 161 kV Nantahala g 5LAKEMRY 161 11170 5WESTS M 161 11171 1 161 0000 Lake Murray Wests Mill 161 kV Nantahala o SNANTAHA 161 11084 SROBBINS 161 11172 1 161 0000 Nantahala Hydro Robbinsville 161 kV Nanthala _ d SNANTAHA 161 11084 5WEBSTER 161 11174 1 161 0000 Nantahala Hydro Webster 161 kV Nantahala o SNANTAHA 161 11084 5WESTS M 161 11171 1 161 0000 Nantahala Hydro Wests Mill 161 kV Nantahala O SROBBINS 161 11172 SSANTEET 161 18040 1 161 0000 Robbinsville DUKE Santeetah TVA 161 kV Tie STHORPE 161 11085 2CEDARCL66 0 11188 1 161 0000 Thorpe Hydro Cedar Cliff Hydro 161 66 kV XFMR Nz O STHORPE 161 11085 STUCKASE 161 11173 1 161 0000 Thorpe Hydro Tuckasegee
29. al Coordination Report Tokay E Date T 7 5 3 Model Updates As long as the bus names of the items in the Facility List exist in the next model the Facility List will be maintained If the bus name does not exist in the next model upload that item will be removed from the Facility List Page 23 Revision 8 System Data Exchange SDX Users Manual 7 6 Output Files The FTP automated data exchange process was retired in March of 2007 and was replaced by the current XML process However there are some entities that have internal processes that require outage data in the old comma separated value format associated with the FTP automated data exchange process Outage data is still available in this format for users requiring it The output files section contains links to csv files on an RC basis These files are updated every 10 minutes and can be downloaded by clicking on the RC link shown NERC System Data Exchange The basic csv data file without any data is comprised of eleven sections and is comma separated with quotation marks enclosing each data field as shown below The information between the comma separated fields will be limited to printable alohanumeric characters excluding the double quotation mark RELIABILITY COORDINATOR RC Acronym CONTROL AREA CA Acronym TIME ZONE TZ Acronym DAILY DATA PEAK MW HREND NET I C OP RES MW WEEKLY DATA PEAK MW NET I C OP RES MW MONTHLY DATA PE
30. ard Time EDT Eastern Daylight Saving Time EST Eastern Standard Time MDT Mountain Daylight Saving Time MST Mountain Standard Time PDT Pacific Daylight Saving Time PST Pacific Standard Time UTC Coordinated Universal Time C 3 Control Area Daily Load and Interchange Data DAILY DATA This field must read DAILY DATA and indicates the start of the Control Area load and interchange data This section of data starts with a title line with the appropriate data following beneath The date depicting the day that the Control Area load data is being submitted for will be directly underneath this field The date will be in the following format MM DD YYYY i e 02 24 2002 Per the NERC RC Reference Document Section A 4 The Daily table will contain 7 days of data beginning with current day PEAK MW This field must read PEAK MW On the lines below this field the Control Area peak load MW for the associated day should be inserted i e 1500 HREND Page 45 Revision 8 SDX Users Manual Appendix C CSV Output File Format This field must read HREND On the lines below this field the hour that indicates the hour ending that the Control Area peak load MW is being reported for This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 NET I C This field must read NET I C On the lines below this field the proj
31. aseeseesaseesereas 20 OUT OUTIRIES sxsseincstarsese tay scnendavatas O E 24 Appendix A User Interface AppendixB XML Processing AppendixC CSV Output File Format Page 2 Revision 8 System Data Exchange SDX Users Manual 1 0 Record of Revisions Revision Date Description Number Effective 7 e Modified formatting to add section numbers e Added Record of Revision section e Modified Section 3 for changes to password management e Modified Section 4 for GUI enhancements to the Home Page Rearranged layout of User s Guide Added description of new features e Data Submission Report e Regional Coordination Report e Updates to User Maintenance e XML setup and processinc a FJ Page 3 Revision 8 System Data Exchange SDX Users Manual 2 0 General Information 2 1 Internet Locations Web User Interface Production https sdx nerc mcqware com Training https training mcgware com sdx XML Production https sdx nerc mcgware com SDXXML asmx https sdx nerc mcgware com SDX xsd Testing https training mcgware com sdx SDXXML asmx httos training mcgware com sdx SDX xsd schema information https sdx nerc mcgware com schemahelp sdxschema html 2 2 Web User Interface Specifications The web based application is compatible with Microsoft Internet Explorer versions 5 0 and higher and Netscape Navigator versions 4 0 and higher The web based application is optimized for Microsoft Internet Explorer version 6 0 ru
32. ce MERIVALE 220 NEPEAN 220 1 M32S 220 220 Out of Service MINDEN 220 OTTCKID2 220 1 D2M 220 220 Out of Service OTT CRK 220 OTTCKID2 220 1 D2M 220 220 Out of Service DES JOAC 220 OTTCKID2 220 1 D2M 220 220 Out of Service HORNIM27 220 HORN M27 220 1 M27B 220 220 Out of Service Page 18 Revision 8 System Data Exchange SDX Users Manual 7 4 Data Submission Report The data submitted through the XML process are tracked and can be viewed for all control areas including the timestamp of when the outage was uploaded To view the historical information the fields can be selected to filter the data presented For example if the same outage was submitted once an hour for every hour of a day that information could be filtered as shown below Search Today s Date 4 71 2700 Filters Control Grea lisne Dates Joos L he aj Timezone EST Equipment Type Generator Equipment Mame GULF outage Type Case Name 200804tr5p0 Case Online YES Expand All Collapse All ISME ISME LoadTS Bus Capability Unit ID Common Name PMAX Status BeginDate EndDate 4 21 2008 7 05 47 PM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21 2008 6 06 11 PM GULF ISL 115 32 1 328 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21f2008 5 05 52 PM GULF ISL 115 32 1 326 GULF ISLAND COMPOSITE 34 Partial Generation 008 OF 00 2008 05 00 4 21 2008 4 06 02 PM GULF
33. ch and transformer data returned from this function mimics the PSS E Raw D file format where e Branch includes branches tie lines and 2 winding transformers e Transformer includes 2 and 3 winding transformers SetBranchCommonName This function will update the common name for branches tie lines and 2 winding transformers setBranchOutage This function will save outages to the SDX database for branches tie lines and 2 winding transformers Page 38 Revision 8 SDX Users Manual Appendix B XML Processing Function Ci escription O setGeneratorCcommonName This function will update the common name for generators setGeneratorOutage This function will save outages to the SDX database for generators setLoad This function will save the load data for an RC to the SDX database setTransformerCommonName This function will update the common name for 3 winding transformers setTransformerOutage This function will save outages to the SDX database for 3 winding transformers Page 39 Revision 8 SDX Users Manual Appendix B XML Processing B3 0 Element Definitions and Required Fields Required Fields Notes sama et RC ShowBranches ShowGenerators ShowTransformers CA and BusName are optional but at least one should be supplied If none of the above are supplied no data will be returned RC and CA are optional but at least one should be supplied If neither are supplied an error message will be returned GetLoad Be
34. count Save First Last EMail Phone Number Marketing Entity L Company North American Electric Reliabi g Site Main Office w Note A separate request must be made for both the production and training instances of the application 4 2 Requesting an Automated Access Account Automated Access accounts are assigned on a company basis and are used for automated processes that upload and or download data to and from the SDX server Access restrictions are in place to prevent Automated Access Accounts from being used for logging in to the SDX and making data changes via the GUI Automated Access Accounts exist as XML Accounts FTP Accounts were permanently disabled as of March 2007 Contact a NERC administrator to obtain an Automated Access account Page 7 Revision 8 System Data Exchange SDX Users Manual 4 3 Reviewing Users User information can be viewed by selecting the Users option under the Data Maintenance menu You can filter by RC by Company or by Firstname and or Last name The State filter was intended to display Users that reside in a particular state i e Minnesota New York North Carolina etc However the User database is not populated with State information so this filter does not work There is also a radio button to filter by active or inactive accounts Once the filtering options are chosen poke search to view the user list The list disp
35. e All valid data uploaded Bus1 to Bus2 was not found in control area CA All valid data uploaded WARNING Outage in the past will not be loaded CA CA All valid data uploaded Bus1 to Bus2 was not found in control area CA All valid data uploaded e Invalid case id e No data uploaded e Invalid Bus Name e All valid data uploaded e You do not have sufficient privileges to edit Bus CircuitlD 1 e All valid data uploaded e You do not have sufficient privileges to control area e No data uploaded for that CA e ACommon Name for Bus 1 to Bus 2 Circuit ID 1 is required e All valid data uploaded when the Post To RCIS option is selected SetLoad Control Area CA has duplicate Daily Load data Data will not be saved Control Area CA has duplicate Weekly Load data Data will not be saved Control Area CA has duplicate Monthly Load data Data will not be saved Control Area CA has duplicate Hourly Load data Data will not be saved SetBranch Outage SetGenerator CommonName Page 42 Revision 8 SDX Users Manual Appendix B XML Processing Function Error Message Impact on Upload Request Failure RC does not have control for the CA control area e No data uploaded for that CA SetTransformer e Invalid case id e No data uploaded CommonName e Invalid J or K Bus Name e All valid data uploaded SetTransformer Outage SetGenerator Outage Page 43 You do not have sufficient privileges to edit Bus 1 to Bus 2 CircuitlD 1 A Common Name for Bus 1 to
36. e 10 05 2004 15 15 05 01 2005 08 00 I Bus Ho current outages Element Groups J Bus K Bus Circuit ID Common Name Status Begin Date End Date Element Group No current outages Daily No load data Net Interchange MW Reserve MW Peak MW Peak Hour The Begin Date and End Date of an outage will be colored red if the outage occurs entirely in the past Transformers I Bus O5TIDD 345 OIBOONES 230 X SICKER 69 0 HOLMSBRG69 0 Page 14 J Bus OSTIDD 138 DIBOONES 135 SICKLER 230 HOLMSBRG 138 Circuit ID Name E 2 1 KY Status 345 135 Out of Service 230 136 Forced Outage 69 230 Gut of Service 69 138 Outof Service Begin Date End Date 10 19 2004 15 40 13 31 2019 23 00 10 19 2004 15 40 08 31 2005 21 38 08 20 2004 08 18 11 11 2011 10 11 01 03 2005 05 00 01 07 2005 05 00 Revision 8 System Data Exchange SDX Users Manual 6 0 Audit Logs 6 1 Change Log SDX Change Logs can be viewed in the Web UI to display the changes made to outages and data through the Web UI Changes made through the automated upload processes will not be captured in this change log ee O Today s Date 12 7 2007 cram 11 5 2007 FSi po o0 ra 127 2007 Ea 23 59 Table Branch User Name lt Search All gt a SEAT es 12M0S 2007 35TA 14 115 35TA 53 115 Bus ID 129080 1291567 Circuit ID 1 end date was changed with the 22 00 22 00 begin date of 12 03 2007 08 00 L2 o6 2007 Cindy t2fif200F i
37. e seen in the Data Submission Report What to do when an outage ends earlier than expected If an outage ends earlier than expected and the element is back in service there are two options for the next SDX upload Revision 8 Page 35 A SDX Users Manual Appendix B XML Processing Do not include the outage in the next file upload RESULT the element will be assumed to back at its default status if the record is not included in the upload Update the end time of the outage to be just after the next upload will occur an end time cannot be in the past RESULT the end time of the outage will pass shortly after the upload and at that time the element will be set back to its default status 7 What to do when an expected outage is delayed Most companies maintain both the expected start time and actual start time of the outage but the SDX has only one start time Each company must consider how to manage the start time sent to the SDX when that start time is in the imminent future or in the recent past Since the IDC TLR process typically kicks off at 25 minutes past the hour it is ideal to ensure any adjustments to the start time are submitted before that time However that is not always feasible and the following are options that can be used in these conditions some approaches and their consequences are listed below A If the expected start of an outage is in the past but the actual start of the outa
38. ea on elements that are of interest The JOA Maintenance area is used to create and maintain the reports These reports are created by a particular user and contain a list of elements and which control areas have access to each of these elements Once these reports are created a user can run these reports as desired in the GUI under the Regional Cord Rpt menu item 7 0 1 Maintaining Facility Lists The user must first create the name of Facility List Once that list is created the user must open the newly created list to add the desired elements to the list The same process is used to edit an existing facility list To remove an existing facility list click on JOA Maintenance then on Remove List only the Control Area that created the list can remove it Create Facility List Select the JOA Maintenance menu item To create a new facility list for use in future reports click Add to show the screen below NERC System Data Exchange JOA Facilities Lists i Add Today s Date 3 25 2004 Facilities List Name E ISNE NPCC 200802tr3p1 ISNE Remove List junkisne 200802tr3p1 ISNE Remove List MISO IESO 200802tr3p1 MISO Victest 200802tr3p1 ACS Enter the desired name of the list and click Save NERC System Data Exchange Update Facilit Facilities List Name Case Name 200802tr3p1 Re ISE Save Add elements to list User will be returned to the JOA Facilities List page Select the Facility List into which you
39. ected net interchange of the Control Area for the hour ending HREND should be inserted A positive value indicates the Control Area is exporting and a negative value indicates the Control Area is importing OP RES MW This field must read OP RES MW On the lines below this field the projected operating reserves of the Control Area for the hour ending HREND should be inserted C 4 Control Area Weekly Load and Interchange Data WEEKLY DATA This field must read WEEKLY DATA and indicates the start of the weekly Control Area load and interchange data This section of data starts with a title line with the appropriate data following beneath The date depicting the Monday of the week that the Control Area load data is being submitted for will be directly underneath this field The date will be in the following format MM DD YYYY i e 02 24 2002 Per the NERC RC Reference Document Section A 4 The Weekly table will contain 4 weeks of data beginning with current week starting on Monday PEAK MW This field must read PEAK MW On the lines below this field the Control Area peak load MW for the associated week should be inserted i e 7500 NET I C This field must read NET I C On the lines below this field the projected net export of the Control Area for the week should be inserted A positive value indicates the Control Area is exporting and a negative value indicates the Control Area is importing OP RES MW This f
40. eld the PSSE BUS NAME identifier for the second winding of the transformer should be inserted J PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the J field Data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV i nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE BUS NAME MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications Page 53 Revision 8 SDX Users Manual Appendix C CSV Output File Format K This field must read K On the lines below this field the PSSE BUS NAME identifier for the third winding of the transformer should be inserted K PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the K field Data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV nn nnn Bus kV lt 10 kV n nnnn Please note that the PSSE BUS Number MUST
41. ements using one name or identifier The element groups must be set up in the NERC SDX application database prior to using this section of the file The SDX application will recognize the element group and communicate the appropriate element information to the NERC IDC ELEMENT GROUPS This field must read ELEMENT GROUPS and will be on a line of itself This field indicates the start of the Element Group data for the Control Area that the SDX data is being submitted Note the Element Groups listed in this section MUST be identified in the NERC SDX database prior to entering the data into this file If they are not they will create an error for the SDX file and the data will be ignored ELEMENT GROUP This field must read ELEMENT GROUP On the lines below this field SDX Element Group acronym must be entered START DATE This field must read START DATE On the lines below this field the date in which the SDX entry is to start to take effect should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to start to take effect should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STOP DATE This field must read STOP DATE On the lines below this field the date in which the SDX entry is to end should be
42. entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to end should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STATUS This field must read STATUS On the lines below this field one of the following options must be chosen where each status indicates the element is O Out Of Service for the time stated I In Service for the time states These additional status options are available to further clarify the status of the element group These will provide additional information to the SDX users about the type of power system element entry Page 52 Revision 8 SDX Users Manual Appendix C CSV Output File Format F Forced Out of Service for the time stated and is communicated to the RCIS HT Is work that is taking place on the element while it is in service i e Hot Line Work COMMON NAME This field must read COMMON NAME On the lines below this field any 50 character identifier can be entered This is generally used so that the user can understand what element is being represented with the SDX entry MISCINFO This field must read MISCINFO On the lines below this field an optional 16 alphanumeric character identifier can be entered This is a miscellaneous field and is not used by the
43. ers to view equipment definition for other t View Equipment areas t Compare Models Compare Models Allows users to compare the detailed model information Other Outages between basecases t CA Changes t Data Submission Rpt Other Outages Allows users to view current outages in other Reliability Regional Cord Rpt Coordinator areas t Output Files CA Changes Allows users to view changes made to outages by Control Area t Log Out Data Submission Provides a history of changes made to each element Report Regional Coordination Allows users to produce outage reports they are pre Report assigned to view from other areas Output files Allows users to download csv files that are formatted according to the old FTP file standard Page 6 Revision 8 System Data Exchange SDX Users Manual 4 0 User Maintenance 4 1 Requesting an Individual User Account Individual User accounts are assigned to individual users for manual log in to the SDX via the Graphical User interface GUI Individual accounts can have read only or full access rights e Choose New Account from the initial page of the web application e Fill in the required information Be sure that you have access to the email address you supply If your company does not exist in the list contact a NERC administrator e Click Save A NERC administrator will review your request and contact you within three business days New Account Request New Ac
44. ge is still null outage was supposed to start at 8 00 but it is now 8 05 and the actual start of the outage has not yet been entered change the SDX Start time to some incremental time in the future until the actual start is not null RESULT this will provide the more accurate information to the SDX Note that if status is Forced this may result in multiple postings to the RCIS Continue to send the old start time as if the outage did occur RESULT this unfortunately indicates the outage began when it did not Continue to send the old start time as if the outage did occur until actual start is filled in then update the start time of the outage RESULT this will look like the outage has occurred as expected until the actual start is known If the outage is still valid while the expected start of an outage is in the past but the actual start of the outage is still null do not send the outage RESULT this unfortunately looks like the outage is not expected to occur at all and is not recommended 8 What is the syntax of the SDX busnames The SDX busname is comprised of the PSSE BUS Name 12 Characters left justified and the PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the field For example ABCDEFGHIJKLnnnn n Extended bus name for voltage e Bus kV gt 1 000 nnnn n e 100 kV lt Bus kV lt 1 00
45. ginDate EndDate Timelnc None GetRCCurrentOutages OutputFilelID and RC are optional If neither of these are supplied the function will return the outage information for all RCs To return outage data for a single RC supply either OutputFilelD or RC Using GetRCList function will present the list of RCs and their associated OutputFilelD GetRCList Active and OutputFilelD are optional parameters GetSystemState RC ShowBranches ShowGenerators and CA ShowTransformers are optional but at least one should be supplied If none of the above are included no data will be returned setBranchCommonName FromBusName CommonName and PostToRCIS are optional If the ToBusName PostToRCIS is True then the common name is CircuitID required If the required fields are provided and no CommonName is provided the CommonName will be deleted setBranchOutage All other fields are optional If no other fields are provided this allows the client to remove all outages for a control area To save an outage the following items are required IBus JBus CircuitSeq BeginDate and OutageType Each upload will fully replace the existing branch outage date except for the logic applied for overlapping outages setGeneratorCcommonName BusName CommonName and PostToRCIS are optional If the CircuitlD PostToRCIS is True then the common name is required If the required fields are provided and no CommonName is provided the CommonName will be deleted
46. ield must read OP RES MW On the lines below this field the projected weekly operating reserves of the Control Area should be inserted C 5 Control Area Monthly Load and Interchange Data MONTHLY DATA This field must read MONTHLY DATA and indicates the start of the monthly Control Area load and interchange data This section of data starts with a title line with the appropriate data following beneath The date depicting the first day of the month that the Control Area load data is being submitted for will be directly underneath this field The date will be in the following format MM DD YYYY i e 2 1 2002 Per the NERC RC Reference Document Section A 4 the Monthly table will contain 12 months of data beginning with the current month starting on day 1 of month PEAK MW This field must read PEAK MW On the lines below this field the Control Area peak load MW for the associated month should be inserted i e 7500 NET I C This field must read NET I C On the lines below this field the projected net export of the Control Area for the month should be inserted A positive value indicates the Control Area is exporting and a negative value indicates the Control Area is importing Page 46 Revision 8 SDX Users Manual Appendix C CSV Output File Format OP RES MW This field must read OP RES MW On the lines below this field the projected monthly operating reserves of the Control Area should be inserted C 6 Contro
47. in e To collapse the Control Area data click on the minus sign beside the Control Area abbreviation e To expand the Control Area data click on the plus sign beside the Control Area abbreviation e The user can expand or collapse all Control Area data via the Expand AIF and Collapse Alf buttons in the search criteria header NERC System Data Exchange Search Begin Date 5 12 2006 EE End Date 5 13 2006 a Beginning On C Ending Gn Active Curing Today s Date 5 12 2006 7 SortBy Bus Name KV MW SZ Branches From Bus To Bus Circuit ID Common Name KV Status Begin Date End Date No current outages Bus Capability Unit ID ommon Nane PMAX Status Begin Date End Date No current outages I Bus J Bus K Bus Circuit ID Common Name EV Status Begin Date End Date No current outages Element Group Status Begin Date End Date No current outages Daily Net Interchange MW Reserve MW Peak MW Peak Hour No load data w l i a a i Ww i i i 7 B From Bus Circuit ID Common Name KV Page 12 Revision 8 System Data Exchange SDX Users Manual 5 1 Selecting Control Areas to be Displayed By default the list of control areas displayed is determined by the company to which the user is associated with This list may be modified by clicking on the Change Control Area List link on the Home Page e To remove a control area from your Home Page select it in the Selected
48. in No data uploaded for that CA the CA control area Error There is no online case Data will not be saved Line X Unable to find Gen Unit 1 All valid data uploaded Line X Generator Gen 1 was not found in Control Area CA All valid data uploaded Line X Invalid Outage Code for Generator Gen Unit 1 All valid data uploaded Outage Status X Warning Line X Generator Gen 1 an End date was not All valid data uploaded provied Page 44 Revision 8 SDX Users Manual Appendix C CSV Output File Format C CSV Output File Format Details C 1 Reliability Coordinator Designation RELIABILITY COORDINATOR This field must read RELIABILITY COORDINATOR and indicates the start of a data set for a Control Area RC Acronym This field must contain the NERC Registered acronym for the Reliability Coordinator submitting the data set for the Control Area C 2 Control Area and Time Zone Designation CONTROL AREA This field must read CONTROL AREA CA Acronym This field must contain the NERC Registered acronym for the Control Area that contains the power system elements in which data is being provided for TIME ZONE This field must read TIME ZONE TZ Acronym This field must contain one of the following options and indicate the time zone in which all start and end times are submitted in ADT Atlantic Daylight Saving Time AST Atlantic Standard Time CDT Central Daylight Saving Time CST Central Stand
49. ing B2 0 Element Descriptions GetEquipment Returns a list of equipment devices in an RC This function will return branches transformers and generator from an IDC case model The branch and transformer data returned from this function mimics the PSS E Raw D file format where e Branch includes branches tie lines and 2 winding transformers e Transformer includes 2 and 3 winding transformers GetLoad Returns the current Load data for an RC GetRCCurrentOutages Return the current output data for an RC this function is the replacement for the previous FTP output file The outage data returned form this function is from the current day and into the future This function returns the following data Daily Weekly Monthly and Hourly Load data Generator outages Transformer outages which includes branches tie lines and 2 winding transformers Par tap outage Element group outages 3 Winding transformer outages which includes only3 winding transformers GetRCList This function returns a list of the current output RCs GetSystemState This function returns the outage information for a desired RC on a given date The client may choose to have one or more of following device types returned Branches Generators and Transformers The data returned from this function is for all outages active during the requested date The start and end dates provided in the response are those associated with the submitted outage The bran
50. ing unit identifier should be inserted This identifier shall include the PSSE Unit Id that represents the unit being entered i e 4 or HL MW This field must read MW On the lines below this field the MW capability of the unit should be entered If the SDX entry is for an outage of the unit then the MW field should read zero 0 If the SDX entry is for a partially limited generator the field should be filled in with the capability of the unit or the MWs the generator can run START DATE This field must read START DATE On the lines below this field the date in which the SDX entry is to start to take effect should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to start to take effect should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STOP DATE This field must read STOP DATE On the lines below this field the date in which the SDX entry is to end should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to end should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900
51. isting generation and transformer outages are unchanged Valid Outage Data e The start time of an outage can be in the future or in the past e The end time of an outage can only be in the future e Any element can have multiple outages submitted in a given upload e Outages of different types should not overlap see separate section on overlapping outages Page 33 Revision 8 SDX Users Manual Appendix B XML Processing B1 2 Frequently Asked Questions Page 34 1 How is the SDX data used Different entities use the SDX data in different ways For some neighboring entities this SDX application is used to exchange the load forecast and expected system topology for inputs into their own analysis such as Total Transfer Capability Available Transfer Capability and Available Flowgate Capability The results of these analyses can impact the transmission service available to customers This information is also passed to the Interchange Distribution Calculator which evaluates Transmission Load Relief requests in accordance with NERC and NAESB standards which can result in the possible tag adjustments for the current and next hour Therefore it is important to send the most accurate information available What outage statuses should be sent to the SDX The NERC Operating Manual describes the valid outage types in the SDX The outage status each user submits should be discussed with their neighboring systems so that each user understands how
52. l Area Hourly Load and Interchange Data HOURLY DATA This field must read HOURLY DATA and indicates the start of the Control Area hourly load and interchange data This section of data starts with a title line with the appropriate data following beneath The date depicting the day that the Control Area load data is being submitted for will be directly underneath this field The date will be in the following format MM DD YYYY i e 02 24 2002 This section is now mandatory as of June 1 2004 It is recommended that 24 hours of daily data be provided PEAK MW This field must read PEAK MW On the lines below this field the Control Area peak load MW for the associated day should be inserted i e 1500 HREND This field must read HREND On the lines below this field the hour that indicates the hour ending that the Control Area peak load MW is being reported for This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 NET I C This field must read NET I C On the lines below this field the projected net export of the Control Area for the hour ending HREND should be inserted A positive value indicates the Control Area is exporting and a negative value indicates the Control Area is importing OP RES MW This field must read OP RES MW On the lines below this field the projected operating reserves of the Control Area for
53. lays the following information for the Users e Name Company E mail Phone number RC Active inactive Role hyperlink that brings up a new window detailing the specific User permissions for that Role Each User is assigned a role A User s role determines the User s permissions The following table describes the User roles available in the SDX Role Type Functions o O Reliability Coordinator e View all GUI displays data and reports e Submit and modify data for all Control Areas mapped to that Reliability Coordinator Read Only e View all GUI displays data and reports e View all GUI displays data and reports e Submit and modify data for their Control Area e Ability to upload and download data e No access to GUI except to change password e Ability to download data e No access to GUI except to change password 4 4 Managing Passwords In an effort to comply with NERC Cyber Security Standard 1200 users of the System Data Exchange SDX tool are required to change passwords on a predetermined timeframe Upon logging into the application for the first time it is highly recommended that you change your password e Individual User Account passwords must be changed every 90 days e Automated Access Account passwords must be changed every 180 days Page 8 Revision 8 System Data Exchange SDX Users Manual Password Change Process OT o tivity Comments S O 30 days before the password expiration date NERC will
54. le rights can be viewed but are not editable Page 29 Revision 8 SDX Users Manual Appendix A User Interface A3 0 Element Groups A3 1 Element Group Maintenance To enter Element Group data select Element Groups from the Data Maintenance menu The purpose of element groups is to facilitate the ability to quickly and accurately enter outages and query equipment for common outage events and or dependent equipment Power system elements can be in one or more element groups Element Group Search Back New Today s Date 1 7 2005 Control Area lt Search All gt M Element Group Name Active O InActive Oall 15 Records found Element Group Description gt ControlArea Adie Allen 3 DUK Yes DUK Yes DUK Yes Soco Yes d len af To create a new Element Group click on New To modify an existing Element Group enter search criteria to limit the search results Click on the appropriate Element Group link to begin modification To create a new Element Group enter the required information Element Group name Element Group acronym Control Area Add Branch Add Generator Add Transformer and change the active status for Element Group Name an Element Group ugnen The Element Group acronym is a M used in the entries FTP Input Files and XML HTTP templates Save You will not be able to create an outage for an inactive Element Group Add Branch to group Allen 3 Today s Date 1 7 2005 Bu
55. ncoming XML is invalid There are no perdefinded errors as these types of errors are set by the Microsoft XML parser Error Message Impact on Upload Request Function GetEquipment e One of ReliabilityCoordinatorAcronym or ControlAreaAcronym e No data provided e Invalid case id e No data provided e One of ReliabilityCoordinatorAcronym or ControlAreaAcronym is required GetRCCurrent e None ee p ee OMS e Unable to find a valid case for OutageDate e No data provided SetBranch e Invalid case id e No data uploaded CommonName e Invalid From Bus Name e All valid data uploaded Invalid To Bus Name e All valid data uploaded You do not have sufficient privileges to edit Bus 1 to Bus 2 e All valid data uploaded CircuitID 1 You do not have sufficient privileges to control area All valid data uploaded A Common Name for Bus 1 to Bus 2 Circuit ID 1 is required when the Post To RCIS option is selected All valid data uploaded Failure oXML_SetBranchOutage Fatal error contact vendor Failure pXML_SetBranchOutage Fatal error contact vendor pLoad_ProcessNonTransformerBranch Failure RC does not have control for the CA control area Data will not be saved Error There is no online case Data will not be saved WARNING All existing outages will be removed for CA File processed Invalid Begin Date Begin Date must be a valid date and All valid data uploaded cannot be less than or equal to the End Date Invalid End Date All valid data uploaded Invalid OutageTyp
56. nformative Forced Outage sent to NERC RCIS TIDD_AEP A P XFORMER ID B Bus ID 22623 24657 Page 16 Revision 8 System Data Exchange SDX Users Manual 7 0 Reporting Features 7 1 View Equipment Power system elements contained in the current SDX model can be viewed for any control area by invoking the View Equipment option in the Reporting menu In order to limit search results enter a combination of the available search criteria The current SDX model will be the default for the Case criteria The results can be presented on the screen or in CSV or XML format iew Equipment Report Case Online 200712r1p4 gt RC lse o Control Area hse o s i wpa o PMIN pmax oo Bus Mame Common Mame SS al Only elements with no common name Today s Date 12 7 200T M Include Branches T Include Generators T Include Transformers Results View Grid cay SML 7 2 Comparing Models Power system elements of a particular SDX model can be compared with other SDX models as available This can be accomplished by clicking on the Compare Models link in the Reporting menu In order to obtain the desired results enter a combination of the available search criteria The current SDX model will be the default for Case A and the previous SDX model default for Case B criteria The results of the comparison will show Compare Models Report Case A Online 200408tr6p3 Case B
57. nning at a minimum screen resolution of 1024x768 2 3 24x7 Technical Support Technical support should be contacted if there are technical questions or errors that cannot be resolved by the users Please note that MCG Technical Support is unable to supply usernames and or passwords to any system resource Please contact a NERC System Administrator for assistance in these matters Email support mcgware com primary method Phone 1 866 MCG WARE secondary method 2 4 NERC Administrators NERC Administrators should be contacted for questions concerning user accounts system access or NERC policies procedures Brian Nolan brian nolan nerc net Shaun Streeter shaun streeter nerc net NERC Phone Number 609 452 8060 Page 4 Revision 8 System Data Exchange SDX Users Manual 2 5 Data Flow and Timing Diagram XML Web Service for Automated data entry NERC SDX XML Web Services and CSV File Outputs Manual data entry through Web Interface e Inputs to the SDX are updated on a frequency determined by the submitter e The CSV Output Files are available from the User Interface and are generated at 10 minute intervals e The XML Web Service output contains outages and load data for all RCs and is generated at 10 minute intervals e The NERC IDC utilized the above XML Web Services output as needed Page 5 Revision 8 System Data Exchange SDX Users Manual 3 0 SDX Application Layout Below is a listing
58. of the menu items in the GUI of the SDX application and a corresponding descpription of each of the items Home Change Password Change Timezone Data Maintenance Companies Users Element Groups Returns user to Home page displaying current outages Allows user to change password Allow user to select timezone for displaying dates Lists the companies registered in the SDX application Lists the users registered in the SDX application Allows users to manage the definition of Element Groups in the GUI Common Name Allows users to manage Common Name information in the GUI JOA Maintenance Allows users to manage the outage data displayed the Regional Coordination Reports Home t Change Password t Change Timezone Data Maintenance e Companies t Users t Element Groups t Common Name F JOA Maintenance Network Load Load Outages Branches Generators Transformers Allows manual entry of load data Allows manual entry of branch outages Allows manual entry of generation outages Allows manual entry of three winding transformer outages Allows manual entry of element groups Element Groups Js Change Log t Branches e Generators t Transformers t Element Groups m This shows an audit log of changes made to outages through the GUI Event Log This shows an audit log of various events that occur in the application inputs model uploads ogs t Change Log t Event Log Reporting Reporting View Equipment Allows us
59. or 4 START DATE Page 49 Revision 8 SDX Users Manual Appendix C CSV Output File Format This field must read START DATE On the lines below this field the date in which the SDX entry is to start to take effect should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to start to take effect should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STOP DATE This field must read STOP DATE On the lines below this field the date in which the SDX entry is to end should be entered The format should be MM DD YYYY i e 02 24 2002 TIME This field must read TIME On the lines below this field the time that the SDX entry is to end should be entered This should be a 3 4 digit value represented in the TIME ZONE listed in the second line of the SDX file The format should be HH24MM i e 2300 or 0900 STATUS This field must read STATUS On the lines below this field one of the following options must be chosen where each status indicates the element is O Out Of Service for the time stated In Service for the time states These additional status options are available to further clarify the status of the transmission line These will provide additional information to the SDX u
60. rocessed End Date cannot be less than the Begin Date WARNING All existing outages will be removed for CA Error Line X Invalid Outage Code for Generator Unit Outage Status WARNING Outage in the past will not be loaded Line X Generator X 1 in Control Area CA Error Line X Invalid Derate duplicate derates found with differing MWs Generator Unit 1 Outage Status WARNING Line X Invalid Derate derate is within a F O outage record this record will be ignored Generator Unit Outage Status Error Invalid MW Output for Gen 1 Line cannot be processed All valid data uploaded All valid data uploaded Fatel error contact vendor Fatel error contact vendor All valid data uploaded File processed Data will not be saved Data will not be saved All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded Fatel error contact vendor Fatel error contact vendor Data will not be saved All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded File processed All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded All valid data uploaded Revision 8 SDX Users Manual Appendix B XML Processing Function Error Message Impact on Upload Request Error INVALID RC does not have access to change data
61. s Name kv 261 Common Name Search E Branches Add From Bus Name To Bus Name Circuit ID Common Name KV C SLAKEMRY 161 SWEBSTER 161 1 161 0000 C SLAKEMRY 161 5WESTS M 161 1 161 0000 To add a piece of equipment to an element group click the appropriate Add button Page 30 Revision 8 SDX Users Manual Appendix A User Interface To remove a piece of equipment from an element group click the check box s next to the piece of equipment and click Save A3 2 Element Group Outage Entry The status of an element group can be modified in the same manner as branches generators or transformers Creating an outage for an element group automatically creates an outage for each piece of equipment associated with the element group Allen 3 Outage Back Save Today s Date 1 7 2005 Element Group Name Allen 3 Begin Date and Time HH24 MM a End Date and Time HH24 MM Outage Type In Service lid Branches From Bus Name To Bus Name CircuitID Common Name KV Generators Bus Name PMAX Unit ID Common Name KV ALLEN 3 16 0 149 000 3 16 ALLEN 3 16 0 122 000 L 16 Transformers I Bus Name Circuit ID Common Name A4 0 Common Name Maintenance Common Name Maintenance Back Download Case Online 200501tr5p3 Control Area CPLE Common Name Bus Name 5 Cl Only elements with no common name Branches Generators Transformers ee eee To manually edit a Common Name click on Common Name from the Dat
62. send an e mail to the addresses associated with the User Accounts Users will not be notified to change their password when logging in to the SDX If an operations employee is re assigned elsewhere within the Company to a bulk power marketing function for example it is the Company s responsibility to ensure that the Individual User Account has been terminated Another notification will be sent at 15 days and 5 days and daily beyond 5 days prior to the password expiration date if the password has not yet been successfully changed Users for both Individual Accounts and Automated Access Accounts will then log in to the SDX GUI and submit a password change request by selecting the Change Password menu item Enter and confirm your new password and click Save Change Password N New Password L Confirm Password The SDX system will then send an e mail requiring users to click on a link to confirm the password change This will activate the new password The password change made via the GUI is not effective until the user clicks the link shown in the confirmation e mail If the password is changed but the new password is not confirmed the password will still expire Page 9 This e mail notification password change methodology is designed to ensure that Individual Account owners are still employed with the organization that allowed them to have the account It is highly recommended that the e mail addre
63. sers about the type of SDX transmission entry F Forced Out of Service for the time stated and is communicated to the RCIS HT Is work that is taking place on the element while it is in service i e Hot Line Work COMMON NAME This field must read COMMON NAME On the lines below this field any 50 character identifier can be entered This is generally used so that the user can understand what element is being represented with the SDX entry MISCINFO This field must read MISCINFO On the lines below this field an optional 16 alohanumeric character identifier can be entered This is a miscellaneous field and is not used by the IDC and SDX application However it can be used for internal communication of information at the user s discretion MRID This field must read MRID On the lines below this field the future NERC Master Resource Identifier MRID will be up to a 32 byte globally unique identifier This will be implemented in the future and is an optional field until then C 9 Phase Shifter Tap Data PAR TAPS This field must read PAR TAPS and will be on a line of itself This field indicates the start of the Phase Shifter Tap position data for the Control Area that the SDX data is being submitted FR BUS This field must read FR BUS On the lines below this field one of the 18 character bus identifiers for the Phase Shifter should be inserted This identifier shall include the 12 characters of the PSSE B
64. serscesesrsrsrsrserseess 7 MOVIEWNO USCIS iictacdatueetalesi2etetaetsaustaddca ted cautnents a a a 8 Managing ASS WONOS eminere T 8 Forgotten PassWord S vi stsatceresessevolevsetacdsesieamit 10 TIMEZONG ensani a N mesuundaaus 11 Customizing Home Page Setup ccccccssscsssssssssesssscsssscesssssssecssessseesaseesaseesasersatersasenss 12 selecting Control Areas to be Displayed eecessssscsscssessesssessessessesseseesssseseesersateass 13 Selecting Outage Data to be Displayed ccccssecssssssessssesssesssseessserseseesesersasersaserses 13 Accessing Data from the Home Page cscesessssssssscssscscsserserssecsscssersersersrsersarsasens 14 AUA LOGS esaa a ener cnrre rrr ere tee rerr cere ret an ence rer rer ame treme ener ee 15 Ence oul Eoo EEEE er metre E EE een E rennet eee E ene nae eee Cree 15 EVENT EO smanun sas tengtnciat byanaustutenenaceg ita N E 15 FACDOMING IC AUN OS is esterase ctu de r Adutendamsansnadskavendey 17 VIGW EQUIDIMGNE cscs uubasnniebl entity hates Mis Muhieaniivll baile daealeliatuataaedin 17 COMPAN VOCS S alae cce nates acersesecine nna coset eceeeseas aes stants angoeiieasen en deeata acescteads 17 View Changes by Control Area CA Change s ccccccscscssesssssssssssesssesssessessessrsesatens 18 Dala SUBMISSION REDON aa cseiitena clon eoadiaten Re ueteceda se tesapacet ea gaceitat alate gas lec ese nla tents 19 Regional Coordination REDOrt cccccccssessssssssssserssssscssssseceseesaecesersaes
65. ss associated with the Automated Access Account be a group e mail address If the User has not changed and confirmed their password by the expiration date the account will be disabled at 8 00am CST on the next business day ePasswords must be between 6 and 15 characters long ePasswords are not case sensitive ePasswords cannot be repeated for a minimum of 3 iterations Password changes will be automatically propagated to the training servers The password expiration clock is reset when the password is successfully changed Revision 8 System Data Exchange SDX Users Manual 4 5 Forgotten Passwords If you forgot your username and or password you can request from the Login page that the system send your account information to the email address associated with your account If you no longer have access to the email address associated with your account you must contact a NERC system administrator during regular business hours or 8 AM to 5 PM or MCG Technical Support outside of the normal business hours Or enter your email address Your password will be emailed to the email address associated Page 10 Revision 8 System Data Exchange SDX Users Manual 4 6 Time Zones New user accounts will default to EST You can select the time zone in which you would like your application to display all dates and time in the system To change your time zone select Change Time Zone from the left
66. t Load from the Network Load menu A list of the control areas to which user has edit rights will be displayed Each control area will have a link to hourly daily weekly and monthly load entry screens Load data in the past cannot be modified Today s Date 1 7 2005 EP Hourly Daily Weekly Monthly LTE Hourly Daily Weekly Monthly LTW Hourly Daily Weekly Monthly m Hourly Daily Weekly Monthly PLE Hourly Daily Weekly Monthly ee A Hourly Daily Weekly Monthly Selecting the desired timeframe will open a window to enter to load data Hourly Load for 1 7 2005 Back Save Today s Date 1 7 2005 Note Import Export 1 7 2005 1 8 2005 1 9 2005 Effective Date Net Interchange MW Operating Reserve MW Peak Load MW 1 7 2005 00 00 1 7 2005 01 00 1 7 2005 02 00 1 7 2005 03 00 1 7 2005 04 00 1 7 2005 05 00 1 7 2005 06 00 1 7 2005 07 00 Hourly Load Data may be entered for the current day plus three days into the future Page 26 Revision 8 SDX Users Manual Appendix A User Interface Daily Load for January 2005 Back Save Today s Date 1 7 2005 Note Import Export Peak Hour HH24 MM Daily Load Data may be entered for the current day plus twenty seven days into the future Weekly Load for January 2005 Back Save Toda
67. t Process Results 6 records found 01 07 2005 11 25 08 Informative OutputFile isne csv written to FTP Server sdx test nerc com 01 07 2005 11 25 07 Informative OutputFile isne csv written to FTP Server ftp mcgware com 01 07 2005 11 20 14 Informative OutputFile isne csv written to FTP Server ftp mcqware com 01 07 2005 11 20 14 Informative OutputFile isne csv written to FTP Server sdx test nerc com 01 07 2005 11 15 10 Informative OutputFile isne csv written to FTP Server sdx test nerc com 01 07 2005 11 15 09 Informative OutputFile isne csv written to FTP Server ftp mcgware com Page 15 Revision 8 System Data Exchange SDX Users Manual OT EVENE LO Back Search Today s Date 1 7 2005 CA Event Type YPE O FTP Output Process Reme p FTP XML Input Process CO V Model Upload Process ORCIS Output Process Results 108 records found 01 07 2005 11 19 39 Informative IMO imo_load csv load completed in 00 00 03 The file contained 835 lines 01 07 2005 11 19 35 Informative IMO IMO CSV load completed in 00 00 24 The file contained 780 lines 01 07 2005 11 19 35 Informative IMO imo_load csv Load started 01 07 2005 11 19 25 Warning IMO IMO CSV Warning For ATIKOKAN18 0 1 the date range 05 01 2008 00 00 06 26 2008 23 59 overlaps with the date range 12 31 2007 23 59 06 26 2008 23 59 Entries combined and accepted 01 07 2005 11 19 25 Warning IMO IMO CSV Warning For ATIKOKAN18 0 1 the date range 06 26 2008 23 59
68. tes the element is O Out Of Service for the time stated I In Service for the time states These additional status options are available to further clarify the status of the three winding transformer These will provide additional information to the SDX users about the type of generation outage F Forced Out of Service for the time stated and is then communicated to the RCIS HT Is work that is taking place on the element while it is in service i e Hot Line Work COMMON NAME This field must read COMMON NAME On the lines below this field any 50 character identifier can be entered This is generally used so that the user can understand what element is being represented with the SDX entry MISCINFO Page 54 Revision 8 SDX Users Manual Appendix C CSV Output File Format This field must read MISCINFO On the lines below this field an optional 16 alohanumeric character identifier can be entered This is a miscellaneous field and is not used by the IDC and SDX application However it can be used for internal communication of information at the user s discretion MRID This field must read MRID On the lines below this field the future NERC Master Resource Identifier MRID will be up to a 32 byte globally unique identifier This will be implemented in the future and is an optional field until then Page 55 Revision 8
69. the hour ending HREND should be inserted C 7 Control Area Generation Data GENERATOR OUTAGES This field must read GENERATOR OUTAGES and will be on a line of itself This field indicates the start of the generation data for the Control Area that the data is being submitted PLANT This field must read PLANT On the lines below this field the 18 character generator identifier should be inserted This identifier shall include the 12 characters of the PSSE BUS Name along with the appended 6 digit KV Level of the generator such that the field is 18 characters long and has a character in the 18th placeholder i e CLIFSID2 13 200 or MCGUIRE1 24 000 PLANT PSSE BUS Name 12 Characters PSSE Base KV Exactly 6 Characters right justified space filled with the last character of the PSSE Base KV in the 18th position of the PLANT PLANT data submissions need to be 18 character ABCDEFGHIJKLnnnn n Where ABCDEFGHIJKL is the BUSNAME and nnnn n is the BUSKV Extended bus name for voltage Bus kV gt 1 000 nnnn n 100 kV lt Bus kV lt 1 000 kV nnn nn 10 kV lt Bus kV lt 100 kV l nn nnn Bus kV lt 10 kV i n nnnn Page 47 Revision 8 SDX Users Manual Appendix C CSV Output File Format Please note that the PSSE BUS Name MUST match the current IDC SDX Base Case in order for the entry to be accepted into the SDX and IDC applications 1D This field must read ID On the lines below this field the 1 2 character generat
70. time for that outage The logic of how to establish those outages may be different for every company However the processing of that data in the SDX will be the same for every file submitted The XML processes can be used to upload the following SDX data e Load data e Branch Generator Transformer outages e Branch Generator Transformer common names The XML processes can be used to download the following SDX data e Model data e Load data e Branch Generator Transformer outages by Reliability Coordinator Element Default Status e The default status of each element in service or out of service is included in the base SDX model and assumed to be the status of the element unless an outage record is submitted e lf the default status of an element is in service an outage is noted in the XML upload with an outage type other than in service elf the default status of an element is out of service an the element will be in service that would be considered outage of type in service the XML upload Full Outage Sets Required e Every outage in every XML upload is treated basically like a new outage e Every upload for any Control Area must contain all outaged elements If only the incremental outages are submitted those few outages will be the only outages present in the model e Since each element type is submitted separately they have no impact on each other For example if only SetBranchOutage is utilized all ex
71. want to add elements Each element must be added using the same pattern described above e Click on the Search radio button to add an element e Select the desired CA from the dropdown e Select the desired Equipment type Page 20 Revision 8 System Data Exchange SDX Users Manual e Enter the equipment name to limit the amount of options presented e Click Search Update Facilit Back Save Print Facilities List Name ISNENewo Case Name zo0s02trap1 sid tera ooo S ist Oi Search Result view Ocrid coy YML CA A Equipment Type Equipment Name Search After adding each element user is sent back to the list of the elements in the current facility list That element can be removed from the list by selecting Remove Equipment From the list of elements presented to the user select Add Equipment on the element to be added This element will be added to the Facility List and the process will need to be repeated for each element to be added NERC System Data Exchange Back Save Print Today s Date 3 25 2008 Facilities List Name psen New o RC S List Search Result View OGrid csy xXmL CA ISNE Equipment Type Branch z Equipment Name fam Search eE KAU 6 Add Equipment ISNE SCRNR34 115 AMHRST 5 115 1134 2 Add Equipment ISNE AMHRST N 115 MONTAGUE 115 1 1044 Add Equipment ISNE 4MTRK188 115 KILVERTS 115 1 1188 5 Add Equipment ISNE DRUMROCK 115 AMTRK187 115 1 1187 5 Add Equipment I
72. y s Date 1 7 2005 ote Import Export Net Interchange MW Operating Reserve MW Peak Load MW 1 3 2005 1 10 2005 1 17 2005 i Zz 1 24 2005 1 31 2005 2 7 2005 Weekly Load Data may be entered for the current day plus five weeks into the future Previous weeks in the month will be displayed however you will not be allowed to change data that is in the past Back Save Today s Date 1 7 2005 ote Import Export LTE 1 1 2005 0 1086 2226 2 1 2005 0 1428 2104 3 1 2005 0 1133 2053 4 1 2005 0 1378 1935 5 1 2005 0 967 1986 Monthly Load Data may be entered for the current month on a rolling one year basis A2 0 Branch Generator and Transformer Outages To enter an outage select the desired element type from the Outages menu You must first search for the equipment for which you wish to enter the outage Use the search criteria to limit the search results by Control Area bus name s KV common name or outage status Click on the link for the equipment for which you wish to enter an outage in the search results When creating a new outage or editing an existing future outage you will be able to enter the begin date and time end date and time and outage status type The start and end time of the outage Page 27 Revision 8 SDX Users Manual Appendix A User Interface must be in the future You will not be able to change the

System Data Exchange (SDX) Users Manual

Contents

Download Pdf Manuals

Related Search

Related Contents