1. SRWG Activity Report (as presented) March 21-23, TSS Meeting #160 WECC Offices Salt Lake City, Utah Mark Graham, SRWG Chair/David Franklin TSS Chair

2. Project Status Update
On December 30, 2011, WECC and Siemens PTI finalized the BCCS contract negotiations. The development of the BCCS will occur in stages throughout 2012, with the final product to be delivered in December 2012.  WECC will coordinate training in the first quarter 2013. 

3. Project Status Update (con’t)
The BCCS will be a web-accessible, centralized database that automates existing processes. It will also provide a central location for maintaining base case information. This will increase the accuracy and timeliness of base case development. The BCCS will also provide a mechanism for supporting other WECC functions. The BCCS offers the following features and benefits:

4. Project Status Update (con’t)
Features
PSLF/PSSE platform compatibility
Change tracking
Automated error checking
Secure Web interface
Interchange coordination
Database flexibility

5. Project KEY Information should include:
Description label contents
Company, date
Interconnection Queue number
ISD, OSD, Phases
Project Status Milestones,
See next slide
Data Status Type
Location by State or Province
Dependencies (Project sequence)
Need input forms for populating this information
Page 2 of 15

6. Project Model data Rating updates are placed in Profiles
Transactions, firm transfers and generation schedules will be balanced within BCCS
These power schedules are placed in Net schedule Interchange Profiles
Page 4 of 15

7. Develop Data Specifications
Consider Data Submission Schedules
annually or monthly
Profiles for designated seasons and years
Structure to store TPL Contingency lists
within BCCS
Control Access?
To improve program automation
Do we need this
Page 7 of 15

8. Features needed for robust model solutions
Solution capability within BCCS
There is concern that overall solutions will be more difficult
Voltage profiles
for seasonal starting points
By area
If/when needed:
Develop extended models
generator groups, reactive groups, branch groups
Consider specialized features
distributed slack
coordinated voltage and VAr control
Page 10 of 15

9. Develop “BCCS implementation plan”
Determine Master Base Case time frame (tentatively 2012 HS)
Create Change file to 2012 case to create 2018 base
EPC, IDEV, EPCL, PYTHON, PRJ
Need out-service and in-service (verify) but is capable with the project file builder
PSSE currently does not have out of service dates. PSLF has this capability in-service and out-service dates that should be converted in the project files.
Place Joe Smith on July 2012 SRWG meeting.
Page 11 of 15

10. Develop “BCCS implementation plan” (con’t)
Project Naming, Structure
NERC compliance acronym_areano_projname (E.G., project name in annual progress report)
For example: Sce_24_dcr.prj
Submit a project description or translation file within the project files

11. Develop “BCCS implementation plan” (con’t)
Validate Master Base Case data
Define user responsibilities and access settings
Define file-naming specifications as needed
Define Project Naming specifications
Schedule training after contract closure
Obtain vendor tools for building data
Start developing Project Files
Steady State and Dynamic data are separate
Develop Seasonal Profile data
Bus-Load-Generation (including losses)
Net schedule and Interchange data
Device control
Develop rating files
Begin using BCCS

12. Data Submittal Process
Set schedule for base case compilation
Individual Contributors
Input Projects and Profiles
Validate accuracy
Area Coordinators review and approve data submittals
Page 13 of 15