NITS on webSmart OASIS

NITS on webSmart OASIS Agenda  Company and User Permissions  Electronic Industry Registry requirement  WebSmart OASIS NITS Displays  NAESB WEQ Standards  DEC/DEP OASIS Business Practices – NITS (draft)  NITS Application Requests Organization  Hands On Demo  WebSmart Tag – NITS  NITS Transition

NITS on webSmart OASIS VACAR Demo OASIS

NITS on webSmart OASIS VACAR Demo OASIS WebSmart OASIS login Click Here

NITS on webSmart OASIS Permissions Three sets of permissions must be set in the webSmart OASIS system for a Transmission Customer to fully use NITS.  Doing Business As - These permissions allow OATI to set permissions for an entire entity. These permissions can only be viewed and edited by OATI.  Company - These permissions allow a TC Admin user to enable/disable permissions for their entire entity. Disabling/enabling these permissions disables/enables the permission for each user in that entity regardless of their individual user settings.  User - These permissions allow a TC Admin user to enable/disable permission for each user individually.

NITS on webSmart OASIS Permissions Company and User – set by TC Admin User  Write NITS Application - This permission controls a user’s ability to create and modify NITS Application, NITS Service, NITS Customer, and NITS Agent Requests.  Write NITS Model - This permission controls a user’s ability to create and modify NITS Resource, Generator, and Load Requests.  Write NITS Services - This permission controls a user’s ability to create and modify NITS DNRs, Secondary Requests, and Ancillary Requests.

NITS on webSmart OASIS Permissions Company and User – set by TC Admin User

NITS on webSmart OASIS Permissions EIR Registration NAESB requires Transmission Customers and Agents must be registered in the Electronic Industry Registry to perform NITS business.

NITS on webSmart OASIS NITS Request Summary

NITS on webSmart OASIS NITS Request Summary – filter options

NITS on webSmart OASIS NITS Request Summary - Presubmitted

NITS on webSmart OASIS NITS Request Summary – New Request

NITS on webSmart OASIS NITS Application Summary

NITS on webSmart OASIS NITS Application Summary

NITS on webSmart OASIS NAESB WEQ Standards NITS State Diagram NAESB Copyrighted

NITS on webSmart OASIS NAESB WEQ Standards State Diagram Definitions  PRESUBMITTED - assigned by OASIS prior to submission by the Eligible Customer or Transmission Customer in a workspace to be saved while developing a NITS Application or request for modification of service such that the NITS Application or request for modification of service can be submitted at a later date.  DEFICIENT - assigned by the Transmission Provider to indicate that a correctable deficiency in the NITS Application or request for modification of service, such as missing, incomplete, or inconsistent information.  REEVALUATE - assigned by the Eligible Customer or Transmission Customer during the NITS Application or request for modification of service process indicating that deficiencies have been corrected, and the revised NITS Application or request for modification of service is ready for review.  COMPLETED - assigned by the Transmission Provider to indicate that there are no deficiencies or all deficiencies in the NITS Application or request for modification of service have been met  DECLINED - assigned by the Transmission Provider or Reseller (PTP only) to indicate that the terms and conditions of the request, such as the BID_PRICE, are unacceptable and that negotiations are terminated or that contractual terms have not been met or the Eligible Customer or Transmission Customer has failed to respond to a deficiency within an established time frame. (Final state).  DELETED – assigned by the Eligible Customer or Transmission Customer to permanently remove a PRESUBMITTED request from the Pre-submittal Workspace. (Final state).

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section A. Use of Pre-submittal Workspace  A workspace available to customers to prepare request, prior to QUEUE.  Request can be deleted by customers.  Request will not be validated  Request will not receive a queue time.  Section B. Approval Process for NITS Applications  Required information not submitted, status set to INVALID  Incomplete information that is not required, status set to DEFICIENT  Customer corrected deficiencies set to status of REEVALUATE  When needed and required information is submitted by customer, status to COMPLETED and begin evaluation.

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section C. Add/Modify Agent  Customers can specify one or more agents to act on their behalf. Agent can take any and all actions that a customer can take.  Required Agent template information  Section D. New Application  Customer must contact “network service” person prior to being allowed to submit Application on OASIS.  Off-OASIS information requirements  On-OASIS information requirements  Required Application template information

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section E. Add/Modify Load  Optional Load forms, not used for Load.  Required Load template information.  Section F. Add/Modify Resource  Required Resource template information  Section G. Add/Modify Generation  Optional Generation forms, not used for Generation.  Required Generation template information.

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section H. Add DNR  Replaces DNR form  DNR template accompanied by Resource template.  If Resource is a generator, DNR template also accompanied by Generation template.  Optional Scheduling Rights form not used. If used, status to INVALID.  Optional Auxiliary Transmission form used for Off-System DNR when Resource Title Area is other than DUK (DEC) or CPLE/CPLW (DEP).  Other providers systems and assignment reference numbers.  Requirements of a DNR.  Required DNR template information.

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section I. Terminate DNR  Replaces Undesignation form  Two types of terminations:  Temporary – used when term ends before the end of the DNR (end date/time earlier than that of DNR)  Indefinite – used when term extends to the end of the DNR (same end date/time as the DNR)  Required Terminate DNR template information  Section J. Add Secondary  Required Secondary template information

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section K. Modify Service  Customer wishing to modify duration of service must contact network service person to start service agreement process.  Template used to document modification of the stop time of the NITS service Application.  Rollover – submit prior to one year before end of service for service greater than 5 years.  Early Termination.  Required Modify Service template information.  Section L. Modify Customer  Used to revise/update information about the customer.  Required Modify Customer template information.

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section M. Add Ancillary  Template not used.  Add Ancillary requests set to INVALID.  Section N. DEC/DEP Submission Of Information For The Customer  List the templates DEC/DEP will submit for a customer upon receiving written request to network service person.  Section O. NITS TSR Submittal Timing  Submittal timing of Secondary and DNR request.  Submittal timing of Secondary Termination request.  Section P. NITS TSR Response Timing  Response timing of Secondary and DNR request.  Response timing of Secondary and DNR termination request.

NITS on webSmart OASIS Business Practices – Network Integration Transmission Service (NITS)  Section Q. Rollover of NITS Service  Network customer service must be 5 years or greater.  Request for rollover of Application must be communicated prior to 1 year to end date of NITSA.  Customers must contact network service person.  Extensions of service will be documented on OASIS with the Modify Service template.  Extensions of DNR will be documented on OASIS with the DNR template setting DNR Action to “Designate Extension”.  Rollover only applies to POR, POD, and MW capacity of existing long-term contract.

NITS on webSmart OASIS NITS Request Structure Application Load(s)Resource(s) Generator(s) DNR(s)Secondary Network(s) Termination(s) Application organization Customer Agent(s)

NITS on webSmart OASIS NITS Templates Hands on  Application  Load  Resource  Generator  DNR  Terminate DNR (Undesignation)  Secondary  Add/Modify Agent

NITS on webSmart OASIS OATI SmartOASIS HELP Video’s  Application  Load  Resource  Generator  DNR  Generic video’s and do not adhere to any TP’s Business Practices  Transactions NITS

NITS on webSmart OASIS Special Requests  Concomitant  EX. Allows Terminate request only if PTP request is accepted.  SAMTS  Performed from the Add DNR template.  Set CG Status field to PROPOSED.  Add Other TP information to Auxiliary Transmission section as available.  Available by right clicking on Add DNR template, then checking Auxiliary Transmission button.

NITS on webSmart Tag NITS Tagging Source: Sink: Must match sink in NITS Load template Owner: Must match Customer or Agent code in NITS Application OASIS: DNR – NITS Application reference number Secondary – OASIS Assignment reference number NITS Resource:DNR – Must match Resource Name in NITS DNR template Secondary – blank MW:Must be equal to or less than MW capacity designated in NITS DNR or Secondary template

QUESTIONS

NITS on webSmart OASIS NITS Transition  Customer by Customer phased IN approach  Duke to enter Application, Load, Generators, and Resource templates into PRESUBMITTED state  Transmission Customers to QUEUE request  One for one DNR/Secondary changeout  Enter new NITS request  Related Ref field to point to existing PTP assignment reference (Aref) number  Recall old PTP reservation (TP action)  Tagging changeout  IN Process PTP Network request (RECEIVED/ACCEPTED/STUDY) go to CONFIRMED  Hard Deadline of July 25, 2016