Update Report on the Power Project

1. Update Reporton thePower Project NEPTUNE Review December 12, 2001 Monterey, CA Harold Kirkham NEPTUNE Power Project Manager

2. Presentation Overview • Philosophy and Approach • How will we do the work? • How will we keep on track? • Organization • Work Breakdown • Management • Documentation • Present Status • Future work

3. Philosophy and Approach How will we do the work? • Assemble a team of specialists • Worry about what can go wrong, and design for it • Simulate everything, software and hardware • Test Components and systems, dry, to destruction • Test systems, dry and wet

4. Philosophy and Approach How will we do the work? • Assemble a team of specialists • power systems • Harold Kirkham, JPL • Chen-Ching Liu, UW • power electronics • Vatche Vorperian, JPL • Mohamed El-Sharkawi, UW • ocean engineering • Bruce Howe, UW • Tim McGinnis, UW • Ed Mellinger, MBARI • reliability • Paul Bowerman, JPL • George Fox, JPL

5. Philosophy and Approach How will we do the work? • Worry about what can go wrong, and design for it • Node: Internal Faults • Component Failures • Overload • Node: External Faults • Cable Faults • Shore Station Faults • System • Stability • Control • Protection

6. Philosophy and Approach How will we do the work? • Simulate everything • Pspice • Converter Operation • Transients • Matlab • Load Flow • PSLF • Load Flow • ATP (EMTP) • Transients • Load Flow

7. Philosophy and Approach How will we do the work? • Test Components and systems, dry, to destruction • Test systems, dry and wet • Test Plan started, still being written

8. Philosophy and Approach How will we keep on track? • Project Team Coordination • Telecons • Meetings • Reports • Reviews • Configuration Management • Cost Containment Approach • Reserve Application • Descope

9. Philosophy and Approach How will we keep on track? TeleconFrequencyPurposeCommunicated Via Power Group Weekly Technical Coordination and Planning Web SIte Major Team Decisions Power Mgmt Team Daily Short Term Coordination As needed Long range planning Subsystem Design Teams As needed Technical Coordination Power Group Memo • Project Team Coordination • Telecons

10. Philosophy and Approach How will we keep on track? MeetingFrequencyPurposeCommunicated via Power Group Quarterly Technical Coordination Web Site Progress Monitoring • Project Team Coordination • Meetings

11. Philosophy and Approach How will we keep on track? ReportFrequencyPurposeUserTo Telecon Minutes Weekly Technical/Programmatic Power Group Web Site Highlights and Forecast Project Status Monthly Technical Status/Forecast JPL NEPTUNE NEPTUNE Mgr Schedule status Manager Financial status Project Status Quarterly Technical highlights/Forecast JPL NEPTUNE NEPTUNE Mgr Schedule update Manager Financial status • Project Team Coordination • Reports

12. Philosophy and Approach How will we keep on track? • Quarterly Status - Beginning in 2002? • JPL and appropriate industry partners • Technical and programmatic status and forecast • Metrics ?? • Preliminary Non-Advocate Review - to be set • Preliminary Design Reviews • Multiple informal peer reviews - Completed 11/01 • Formal Project Level Review (PDR) - to be set • Critical Design Review (CDR)- to be set • Test Readiness Review - to be set • Preshipment Review - to be set • Operations Readiness Review - to be set • Deployment Readiness Review - to be set • Reviews

13. Philosophy and Approach How will we keep on track? • Configuration Management • Objective • Document and control NEPTUNE power system configuration via low cost configuration management procedures • Empower development teams by establishing CM responsibility at the lowest reasonable level • Policy • Identify and document a baseline functional & physical description of hardware and software • Control changes to those characteristics • Record and report change processing and implementation status • Authority • Final authority is the Power Group Change Board (PGCB) • Consists of Power Management Team plus ???? • Chaired by Project Manager or designee

14. Philosophy and Approach How will we keep on track? • Configuration Management (continued) • Form, fit and function changes: • Project or System requirements or interface control documents are affected • Design control documents requiring ECR are affected • Change affects Integration, Test, or other Deliverable milestone • Safety is affected by a potentially hazardous condition • Change could result in costs not covered in current allocations • Applicable to these changes: • Configuration identification • Change control • Status accounting • Verification • Waivers

15. Philosophy and Approach How will we keep on track?

16. Philosophy and Approach How will we keep on track? • Configuration Management (continued) • Complete sequence to be followed if: • Change not totally within the power system and cannot be resolved at the power system manager level • Change affects milestones that appear on NEPTUNE master schedule • Change would result in modification to released document • Change is JPL imposed, or NEPTUNE Project imposed • Change affects approved Safety considerations • Change affects any part of project design after the CDR • Change has a cost impact of greater than $50 k

17. Philosophy and Approach How will we keep on track? • Realistic objectives • Preliminary design seems reasonable • Scope is not inflating • Team Qualifications • Qualified in the right fields • Talented • Committed • Early technology choices • Diode/Breaker as node input configuration • Vacuum breakers with n.o. default • 200 V modules in converter • Hall Effect current sensing • Early cost estimation tailored to NSF rather than task • Reserve small • Descope difficult

18. Philosophy and Approach How will we keep on track? • Each Subsystem Manager expects to solve self-contained problems within their baseline budget • A $.3M uncommitted reserve is held by the UW PI • Reserve application strategy • Up to 1/3 obligated between PDR and CDR for unforeseen events • Up to 1/3 additional obligated between CDR and Deployment for unforeseen events • 1/3 held for impacts of major events outside the project’s control • Descopes will be discussed as necessary to maintain risk level

19. Philosophy and Approach How will we keep on track? • Descope defined: Reduce future effort or objectives to contain cost • Approaches (prioritized) • Quality reduction (eg simplify protection modes) • Minor loss of capability (eg accept reduced power level) • Risk increase (eg less redundancy, reduced testing) • Descope plan emphasizes decreased quality and capability rather than increased risk because of impact on future costs • Descopes have not yet been identified • Descopes will be identified and implemented only if all other cost containment options have been expended, consistent with our reserve depletion plan

20. Organization Work Breakdown NEPTUNE POWER Bruce Howe, Principal Investigator Harold Kirkham, Project Manager SCIENCE REQUIREMENTS SAFETY REQUIREMENTS Will Wilcock TBD 1. SHORE STATION 2. CABLE 3. NODE 4. SYSTEM Bruce Howe Bruce Howe Harold Kirkham Harold Kirkham 1. AC switchgear 1. Cable properties 1. Backbone DC switchgear 1. Data acq & comm Harold Kirkham Tim McGinnis Mohamed El-Sharkawi Tim McGinnis 2. UPS 2. Cable selection 2. Converter design 2. Power system control Tim McGinnis Bruce Howe Vatche Vorperian Chen-Ching Liu 3. AC surge arrestors 3. Cable simulators 3. Startup 3. Protection Mohamed El-Sharkawi Mohmaed El-Sharkawi Vatche Vorperian Chen-Ching Liu 4. Converter design 4. Direct current measurement 4. Restoration Mohamed El-Sharkawi Vatche Vorperian Chen-Ching Liu 5. DC switchgear 5. Output DC switchgear 5. "Slow" models and analysis Mohamed El-Sharkawi Tim McGinnis Chen-Ching Liu 6. Shore Station Control 6. Node power controller 6. Transient models and analysis Chen-Ching Liu Tim McGinnis Mohamed El-Sharkawi 7. Grounding electrodes 7. Quality assurance and testing Tim McGinnis George Fox 8. Common system parts 8. Design reliability Tim McGinnis George Fox 9. Integration and prototype Tim McGinnis

21. Organization Management

22. Organization Documentation Observatory Observatory Science Education Observatory Observatory Science Education Program Project Program Project Success Need Utilization and Public Success Need Utilization and Public Plan Plan Plan Plan Criteria Statement Policies Outreach Criteria Statement Policies Outreach Science Science Requirements Requirements Document Document Facility Observatory Project Configuration Facility Observatory Project Configuration Requirements Assurance Documentation Management Requirements Assurance Documentation Management Document Plan Plan Plan Document Plan Plan Plan Facility System Observatory Observatory Facility System Observatory Observatory System System Operations Verification Deployment Description Operations Verification Deployment Description ICD ICD Concept Doc. Plan Vessel ICD Document Concept Doc. Plan Vessel ICD Document Level 1 Level 2 Level 3 NEPTUNE Program Documentation

23. Organization Documentation Configuration Management Plan Project Verification Plan Documentation Plan Configuration Management Plan Reports and Minutes System Description Documents Deployment Vessel ICD Operations Concept Doc Test Plan ICD System Description Documents Power Project History Level 3 Level 4 NEPTUNE Power System Documentation

24. Present Status • Technology: tackling “tall tentpoles” first • Shore station • COTS Source • Node • DC/DC converter • DC circuit breaker implementation • System aspects • stability • protection • transients • Management: writing plans • Verification • Documentation • Configuration Management • Concept of Operations

25. Present Status Technology: Shore Station • COTS sources identified, priced • Is final supply the best for our development? • What test facilities do we require?

26. Present Status Technology: Node • DC/DC converter • designed in principle • simulated (Pspice)

27. Present Status Technology: Node • DC circuit breaker implementation • designed in principle • simulated (ATP)

28. Present Status Technology: Node • DC circuit breaker implementation • simulated (hardware) • vacuum breaker chosen in principle 10 kV 25A rating 25 kV 30A rating

29. Present Status Technology: System Aspects • Stability • Addresses peak power question • Operation simulated in PSLF • Operation simulated in Matlab (twice)

30. Present Status Technology: System Aspects • Protection • crucial to operation • altogether a major set of tasks • complicated design, layers and zones • putting together concepts, requirements • distance relaying • differential relaying • time of arrival relaying • zones, overlaps • autonomous operation • human interface • impact on C2 system

31. Present Status Technology: System Aspects • Transients • well-understood in principle • simulated (ATP)

32. Present Status • Management: writing plans etc • Statement of Work • draft available • Verification Plan • not started • Documentation Plan • draft available • Configuration Management Plan • diagram exists • Concept of Operations • draft available