From: Paul Sorenson Sent: Monday, October 06, 2008 11:14 AM To: Gilbert, Greg W. Subject: RE: NITS Application concept - conference call suggestion Greg, conceptually in line with some nuances about what’s where. I’m thinking more along lines of defining the kinds of data exchanges to support in protocol (the way S&CP was approached) rather than doing a full data model then figuring how to exchange that (the way e-tag was approached). So, quick run at what I was thinking – can change the names all we want, but conceptually thinking of what action is conveyed with each exchange type. Also, want to emphasize that we have a “transaction” level that can contain one or more of each of the below “requests”. And, as each request is acted on/approved it ends up being reflected in some queriable structure like your spreadsheet that shows the result of ads/modifies/deletes, etc. Also, reach request and transaction has some sort of “state” hopefully not necessarily all the OASIS states today – minimally like queued (on submit), accepted/denied (by TP), withdrawn/approved(confirmed) (by TC) The “requests” New Application – request for new service from customer – things like customer info, customer attestation, designated agent with start/stop term, term of service start/stop Revise Application – mod any application related data that may be modified – contact info, agent info, maybe request to “renew/extend”, etc. New Resource – request definition of new network resource with one or more possible operating characteristics, etc. – like name of gen, location, Pmax, var stuff (all the base operating junk that may need for NOA/operations). This is different than a designation – could define a bunch of gens that haven’t been designated yet. We even discussed at meeting if definition of resources could cross NITS agreements – like this is base ops data that anyone could refer to that might designate the generation as a resource Revise Resource – mod to resource characteristics Eliminate Resource – effectively delete resource New Load – per gen above, define all the stuff about load – interruptible/non-interuptible, etc.; TP would assign it a unique sink name if required to be forecasted separately for tracking internal transmission constraints to load pockets Revise Load – mod to load characteristics Eliminate Load – remove load from agreement (if in part, would that just be a “revise” load?) Forecast Load – provided by TP assigned sink name (one or more), some think 10-year forecast separate from next week operations forecast; in my mind any data supplied overwrites existing so separate “new” and “revise” not needed? Designate Resource – request to designate named resource with start/stop, MW, type (on/off-system), POR (if off-system), generating CA etc. Should refer to a defined resource, but not required for some type of resources like power sales agreements off a fleet of gens or from external CA. Undesignate (Revise?) Resource – reduce/remove capacity from existing DNR over time. If we use “revise” can you add MWs to resource as well as take away from resource? If temporary undesignation, needs to include “re”-attestation that DNR still valid at end of undesignation. “Indefinite” undesignation could be just special “undesignate resource” to end of term of designation. New PTP – support for submitting ptp request using NITS protocol for “simultaneous undesignated and request for PTP” Revise PTP – allow for “transcust” like updates to PTP submitted via NITS protocol? Some “transactions” Minimal NITS application – Transaction containing just “New Application” request Full NITS app – Transaction containing “New Application”, “New Resource” (0? or more), “New Load” (one or more), Forecast Load (one or more), Designate Resource (one or more) Simultaneous ptp – Transaction containind a “Undesignate Resource” (one or more), and “New PTP” (one or more); evaluate ptp request with simultaneous undesignation like a ptp redirect “Re”- designation of resource – Transaction containing “Undesignate Resource” (one or more) and “Designate Resource” (one or more); evaluate designation with simultaneous undesignation like a ptp redirect I would like to cast all this stuff as a set of web services with XML rather than templates. Might be possible with some csv form, but certainly not easily with the current “fixed in order and number” requirement and no mechanism to have different headers apply to different sections of a message. Paul R. Sorenson Open Access Technology International, Inc. Phone: 612-360-1633 Email: paul.sorenson@oati.net CONFIDENTIAL INFORMATION: This email and any attachment(s) contain confidential and/or proprietary information of Open Access Technology International, Inc. Do not copy or distribute without the prior written consent of OATI. If you are not a named recipient to the message, please notify the sender immediately and do not retain the message in any form, printed or electronic. -------------------------------------------------------------------------------- From: Gilbert, Greg W. [mailto:GGilbert@southernco.com] Sent: Monday, October 06, 2008 9:15 AM To: Paul Sorenson Subject: FW: NITS Application concept - conference call suggestion Paul, A poor man’s prototyping… Gregory W. Gilbert Southern Company Transmission -------------------------------------------------------------------------------- From: Wood, James T. Sent: Monday, October 06, 2008 9:07 AM To: Gilbert, Greg W. Subject: RE: NITS Application concept - conference call suggestion Might want to send Paul the Excel Workbook. Never got the chance to present it to the group. We were more involved in getting the data elements down in the last two meeting. JT ------------------------------------------------------------------------------ From: Gilbert, Greg W. Sent: Monday, October 06, 2008 9:00 AM To: 'Paul Sorenson'; Wood, James T. Subject: RE: NITS Application concept - conference call suggestion Paul, I talked with JT and it seems the first opportunity will be Oct 10 with just you and I participating. I too need to pull my notes and thoughts back together after dealing with other project activities and hopefully the first of the week will allow for this and I can actually get my brain into a NAESB gear. I was wondering if by any chance OATI has already implemented a solution. If so, I am open to reviewing it as a starting point rather than start from the ground up. As a side note, the Excel Workbook JT presented was to represent the NITS as a status query. I agree with you that we need to determine the work flow for capturing the data. Anyway, I’ve blocked off 8-4 CDT on Oct 10 for a conference call to brainstorm ideas. Let me know what time to give you a call or if you need to wait until next week. Greg Gregory W. Gilbert Southern Company Transmission