130 likes | 321 Views
Base Case Change Control Methodology in the Base Case Coordination System. Pre-Bid Conference Salt Lake City, Utah September 9, 2010. Base Case Coordination System - Basic Structure. System Data in various formats. Time-stamped project definitions. Future facilities Generator Data
E N D
Base Case Change Control Methodology in theBase Case Coordination System Pre-Bid Conference Salt Lake City, Utah September 9, 2010
Base Case Coordination System - Basic Structure System Data in various formats Time-stamped project definitions • Future facilities • Generator Data • Short Circuit data • Load Forecasts BCCS Database • Database Contents: • 15-years • 4 seasons • Heavy and Light • Committed Projects • Proposed Projects • Generic Generators • Capabilities: • Data entry • Case change • Solution engine • Audit & Check • Notifications • Confidentiality • Case Creation: • Select year/season • Select Loading • Select scenario • Solve and validate • Posted WECC Cases • User-specified Cases
Base Case Creation Process BCCS Database • Case description • Year/season • Loading scenario • AS-OF date • Rating table • Device status table • Path Definitions • Project files • Load & Resource Tables • Load scenario • Generation • Save/recall info User Selection • Following user selections and settings • Retrieve specified data into BCCS system topology • Apply time-stamped project definitions • Save result with the BCCS database • Optionally, output standard-format flat file base case data Assemble Base Case Solve and validate • Post WECC Cases • User-specified Cases
BCC Methodology Functions • Specify Projects (various uses) • Validate topology, load, and generation • Produce reports • Verify changes • Check data • Maintain system data • Add, modify, delete • Define scenario or stress cases
BCC Functionality • BCC files will not replace • in-run code • Application-specific functionality • EPCL, Python • Users should be able to write code to process BCC files outside the BCCS • non-WECC users • Consultants
Example BCC File Procedure • Check for existence of a specific line • If present, then write a comment to a log-file • If not in the data, then add the line • After making a few modifications, solve the system to lessen iteration difficulty • Place the result in a flat file for validation
Corresponding BCC File Syntax IF EXIST BRANCH from=102 to=104 ckt=2: WRITE file=“%userspace\test1.log” “Branch 102-104 is there”; ELSE: BRANCH new from=102 to=104 ckt=2 [R=0.004 X=0.013 B=0.02 meterbus= from status= ON; ENDIF . . . . other statements . . . . SOLVE iter=2; SAVE name=“testcase1”;
Example BCC File #2 OPEN READ “LoadInfo.dat”; While TRUE: READLINE BusNum, MW, MVAR; LOAD Bus=BusNum P=MW Q=MVAR; END; CLOSE “LoadInfo.dat”
Project File Created Manually Project file
Project File from Case Comparison Case One Compare Cases Project file Case Two