Planning “Science Operations” tasks for the PD phase NGAO PD Phase D. Le Mignant W. M. Keck Observatory 08/19/2008.

Slides:



Advertisements
Similar presentations
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Advertisements

RAMIRI2 Prague 2012 Project management and the RI Life Cycle.
NGAO Construction Project Cost Estimation: Initial Thoughts Richard Dekany NGAO Team Meeting #12 December 13, 2007.
ClosingExecuting/ Controlling ControllingPlanningInitiatingOpportunityAssessment Client AcceptancePlanning ApprovalInitiating ApprovalOpportunity Assessment.
Science Group: Status, Plans, and Issues Claire Max Liz McGrath August 19, 2008.
Project Change Management
NGAO Controls Team Meeting August 29, 2008 Erik Johansson.
NGAO System Design Review Response Peter Wizinowich, Rich Dekany, Don Gavel, Claire Max for NGAO Team SSC Meeting June 18, 2008.
NGAO System Design Phase Update Peter Wizinowich, Rich Dekany, Don Gavel, Claire Max, Sean Adkins for NGAO Team SSC Meeting February 20, 2008.
NGAO Instrumentation Overview September 2008 Updated Sean Adkins.
Build to Cost Meeting: Goals, Agenda & New Directions Peter Wizinowich NGAO Team Meeting September 11-12, 2008.
Development Processes UML just is a modeling technique, yet for using it we need to know: »what do we model in an analysis model? »what do we model in.
1 NGAO Instrumentation Studies Overview By Sean Adkins November 14, 2006.
Trying to connect WBSs with people and phases Relevant questions to my work: How the realistic NGAO strategies will/should affect the work in progress?
NGAO Control Systems Group Status, Plans & Issues NGAO Team Meeting August 19, 2008 Erik Johansson Jimmy Johnson, Doug Morrison, Ed Wetherell.
Observing Operations Concept Document Elizabeth McGrath NGAO PD Team Meeting #6 March 19, 2009.
NGAO System Design: AO System (WBS 3.2) & Laser Facility (WBS 3.3) Design Inputs & Outputs Peter Wizinowich NGAO Team Meeting #9 August 24, 2007.
Science Operations Update NGAO - Meeting 11 D. Le Mignant, E. McGrath & C. Max W. M. Keck Observatory 11/05/2007.
Chapter 5: Project Scope Management
Build to Cost Directions & Guidelines Peter Wizinowich SSC Meeting November 3, 2008.
NGAO Meeting #3 Introduction NGAO Meeting #3 Peter Wizinowich December 13, 2006.
WBS & AO Controls Jason Chin, Don Gavel, Erik Johansson, Mark Reinig Design Meeting (Team meeting #10) Sept 17 th, 2007.
NGAO Management Update Peter Wizinowich NGAO Meeting #11 November 5, 2007.
Science Operations Replan NGAO - Meeting 6 D. Le Mignant W. M. Keck Observatory 04/25/2007.
NGAO System Design Phase Management Report - Replan NGAO Meeting #6 Peter Wizinowich April 25, 2007.
Science Operations Plan NGAO - Meeting 10 D. Le Mignant W. M. Keck Observatory 09/17/2007.
NGAO interface control documents: Christopher Neyman W. M. Keck Observatory Keck NGAO PD phase Meeting #6 March 19, 2007 Videoconference.
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
NGAO System Design Phase System & Functional Requirements Documents NGAO Meeting #6 Peter Wizinowich April 25, 2007.
Design Team Report: AO Operational Tools (aka Acquisition and Diagnostics) Christopher Neyman W. M. Keck Observatory (for the Operational tools team) Keck.
Encouraging “System Level” Thinking Christopher Neyman, Erik Johansson, David Le Mignant W. M. Keck Observatory Viswa Velur California Institute of Technology.
System Architecture WBS 3.1 Mid-Year Replan Richard Dekany NGAO Team Meeting #6 April 25-26, 2007 UCSC.
Chapter 5: Project Scope Management
NGAO Instrumentation WBS Replan By Sean Adkins April 25, 2007.
NGAO Meeting #5 Introduction NGAO Meeting #5 Peter Wizinowich March 7, 2007.
NGAO Instrumentation Preliminary Design Phase Planning September 2008 Sean Adkins.
Functional Requirements for NGAO Christopher Neyman W. M. Keck Observatory NGAO Team Meeting #9 August 24, 2007.
Trying to connect WBSs with people and phases Relevant questions to my work: How the re 8 -planning will affect the work in progress? Priorities to capture.
Design Team Report: AO Operational Tools (aka Acquisition and Diagnostics) Christopher Neyman W. M. Keck Observatory (for the Operational tools team) Keck.
NGAO Controls Team Kickoff Meeting August 5, 2008 Erik Johansson.
Development plan and quality plan for your Project
Project Scope Management
LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.
What is Business Analysis Planning & Monitoring?
How to integrate the parts of your project to achieve success.
Ivan Dontsov, Andy Phenix, Maureen Rottschaefer. Project Outline “The primary objective of this OMSE 2012 Practicum Project is to extend and refine the.
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
1 SPSRB Decision Brief on Declaring a Product Operational Instructions / Guidance This template will be used by NESDIS personnel to recommend to the SPSRB.
ISM 5316 Week 3 Learning Objectives You should be able to: u Define and list issues and steps in Project Integration u List and describe the components.
OOI CI LCA REVIEW August 2010 Ocean Observatories Initiative OOI Cyberinfrastructure Architecture Overview Michael Meisinger Life Cycle Architecture Review.
Doug Tody E2E Perspective EVLA Advisory Committee Meeting December 14-15, 2004 EVLA Software E2E Perspective.
Ch 4 - Learning Objectives Scope Management You should be able to: n Discuss the relationship between scope and project failure n Describe how strategic.
I n t e g r i t y - S e r v i c e - E x c e l l e n c e Business & Enterprise Systems The Integrated Master Plan (IMP) and the Integrated Master Schedule.
11/24/2015Dr. SASTRY-PROJ SOFTWARE PROJECT MANAGEMENT By Dr. M V S PERI SASTRY. B.E,Ph.D.
Project Scope Management 1. 2 Learning Objectives Understand the elements that make good project scope management important. Explain the scope planning.
What is project management?
Project Management.
Unit – I Presentation. Unit – 1 (Introduction to Software Project management) Definition:-  Software project management is the art and science of planning.
Keck Next Generation AO Next Generation Adaptive Optics Meeting #2 Caltech November 14, 2006 P. Wizinowich for NGAO Executive Committee.
Software Production ( ) Lecture 3: Dr. Samer Odeh Hanna (PhD) office: 318.
Development Project Management Jim Kowalkowski. Outline Planning and managing software development – Definitions – Organizing schedule and work (overall.
IT-301 Project Management I: Unit 4: Cost Management.
Project Scope Management Pantelis Ipsilandis- Dimitrios Tselios.
Project Management PTM721S
An Overview of Requirements Engineering Tools and Methodologies*
Scope Planning.
GLAST Large Area Telescope:
IEEE Std 1074: Standard for Software Lifecycle
NGAO System Design Project Plans and Schedule
Software Development Process
Presentation transcript:

Planning “Science Operations” tasks for the PD phase NGAO PD Phase D. Le Mignant W. M. Keck Observatory 08/19/2008

2 Outline 1.“Science Operations” during PD phase 1.Narrative 2. Schematic 3.Work in progress 2.Proposed Priorities 1.High 2.Low 3.Discussion / comments

3 Science Operations during the PD phase Narrative WBS 3.2 Requirements –WBS 3.2.1: Observing Operations Concept Document (OOCD) “Example observations”, including simulations of quantitative science output from NGAO + science instrument Uses cases, leading to operations sequences and science tools WBS 3.4 System architecture –WBS 3.4.4: NGAO Sequences Definitions Document (SDD) WBS 3.6 Science Ops Tools Design –WBS Multi-system Command Sequencer (MCS) –WBS User Interfaces –WBS Pre and post-observing science support tools –WBS Data server WBS 3.9 Operations Transitions –WBS Ops Plans –WBS Ops Handover

4 NGAO sequences definitions document OOCD document: Keck standard Example observations Planning User System Observing User System Post-observing Uses cases Use case 1 User System Use case 2 User System WBS 3.2 WBS 3.4.4: Science observing planning, simulation and execution User Interfaces design WBS WBS WBS Science requirements WBS 3.1 Re-planning (phased) approach? (New) performance budgets WBS users inputs documentactivityWBS name WBS SDM (KAON 511)

5 OOCD document: Keck standard Example observations Planning User System Observing User System Post-observing Uses cases Use case 1 User System Use case 2 User System NGAO sequences definitions document WBS 3.2 WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS documentactivityWBS name The detailed sequences will be documented In the NGAO SDD. The context will be provided in the OOCD

6 NGAO sequences definitions document WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS NGAO software architecture document WBS External ICD WBS 3.5 Internal ICD WBS 3.6 Coordination with general software effort!! OOCD document: Keck standard Example observations Planning User System Observing User System Post-observing Uses cases Use case 1 User System Use case 2 User System WBS 3.2 documentactivityWBS name

7 NGAO sequences definitions document WBS 3.4.4: MCS sequences WBS WBS WBS User Interfaces WBS WBS WBS NGAO software architecture document WBS External ICD WBS 3.5 Internal ICD WBS 3.6 documentactivityWBS name MCS infrastructure document WBS 6.1.1: UI infrastructure document WBS 6.2.1: Data server infrastructure WBS 6.4.1: WSPS/outline for the deliverables - Operations concept? - Software Interface?

8 Science Operations during the PD phase Work in progress… Plan the deliverables: Outline/standard for the document Plan for release(s) and content update Lead person per document / section How to include (realistic) science instruments for quantitative estimates for the example observations Phase the effort (under the assumption there will be a learning curve on the science instruments)…

9 Priorities HIGH… OOCD Outline for release 1: Get buy-in and include suggestions / comments How do we include a case for the wide fov science? (assumptions, assumptions…) Sequences Definitions Document Outline and start of release 1 [Not a perfect flow-down..] Sci ops architecture Release 1 for system infrastructure (MCS)

10 Priorities low… Science operations support tools Release 1 in support of working on observing scenarios (i.e., narrow-field science:OSIRIS, VIS/NIR-IMGR) Keep it descriptive for d-IFS for instance?? User Interface (release 1 - tbd) Observing sequences control Science observing sequences Awaiting progress on science instrument [e.g., fine centering with coronagraph] Troubleshooting & alarm handling? Operations Transitions (100h for DLM) Outline for document (~ 20h or less)

11 Comments and discussion Questions about priorities? High and low “Build to cost paradigm”, can be seen as: Opportunity to deliver an integrated science machine Driven by the science instruments requirements:  Review science case to cost-benefit  Include design/build of science instruments  Focus on science instruments rather than details on science operations and observing sequences, e.g, who cares about 5% observing efficiency when you don’t know whether there will be 0, 3 or 6 d-IFS Outstanding science instruments are key to AO success!