MUSE KO: MUSE Support at ESO ‘customer’  MUSE Team Created (ESO-customer), contacts with the Consortium and support activities on-going  Budget and Manpower.

Slides:



Advertisements
Similar presentations
Project Quality Plans Gillian Sandilands Director of Quality
Advertisements

Process and Product Quality Assurance (PPQA)
World Bank Financial Management Sector September 2010.
1 PROJECT MANAGEMENT ROLE OF KEY PERSONNEL Bernd Madauss International Space University Strasbourg February, 2011
System Testing 2  Effective March 3, 2014, new requirements for system testing were implemented  State Agencies are now required to provide to FNS:
Área de Instrumentación NAHUAL Mechanical Concept Current Status F. Javier Fuentes Instituto de Astrofísica de Canarias September
Software Engineering 1. Software development – the grand view 2. Requirements engineering.
The decision box represents key management decisions and serve as the GATES which delineate phases. The decision can be to proceed, exit, or recycle. More.
1 Schedule Risk Assessment (SRA) Overview July 2013 NAVY CEVM.
MSD-I Project Review Modular Motion Tracking Sensors 1.
NGAO Team Meeting Management Peter Wizinowich May 26, 2009.
Adjusting EPLC to your Project Colleen Robinson & Teresa Kinley Friday, February 6, 2009.
Introduction to ARA’s Proposal Resources Don Cole
Dominion Radio Astrophysical Observatory DVA-1 Reflector Development Timeline Gary Hovey NRC-HIA Dominion Radio Astrophysical Observaotry.
NGAO Instrumentation Preliminary Design Phase Planning September 2008 Sean Adkins.
Defining the Activities. Documents  Goal Statement defines why helps manage expectations  Statement of Work what gets delivered defines scope  Software.
OPSM 639, C. Akkan1 A Scenario You with your two friends are going to have a one-week vacation at another friend’s house, who will not be at her house.
Chapter 2: Overview of Essentials ISE 443 / ETM 543 Fall 2013.
Conceptual Design Review Design Requirements The Systems Perspective Rob Hubbard Systems Engineering.
Faye Business Systems Group presents: The Top 10 Reasons Why CRM Implementations Fail.
Common PDR Problems ACES Presentation T. Gregory Guzik March 6, 2003.
1 Chapter 2 The Process. 2 Process  What is it?  Who does it?  Why is it important?  What are the steps?  What is the work product?  How to ensure.
Comprehensive Review of the Public Safety Communications Center Phase 2 Report County of Dane, WI February 12, 2009.
August 2 and 3, 2010 Project Cost, Schedule, Risk and Contingency Jay Elias.
How to Get Promoted When Your IT Project Fails Let’s Talk About…….. Ian Koenig PMP Quality IS Projects, Inc.
1 Community-Based Care Readiness Assessment and Peer Review Team Procedures Overview Guide Department of Children and Families And Florida Mental Health.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 8 Slide 1 Software Prototyping l Rapid software development to validate requirements.
Lecture 31 Introduction to System Development Life Cycle - Part 2.
Rev. 0 CONFIDENTIAL Mod.19 02/00 Rev.2 Mobile Terminals S.p.A. Trieste Author: M.Fragiacomo, D.Protti, M.Torelli 31 Project Idea Feasibility.
Software Engineering Saeed Akhtar The University of Lahore Lecture 8 Originally shared for: mashhoood.webs.com.
EGR Anatomy of a Project1 A.M. Ruskin and W.E. Estes (1995) What Every Engineer Should Know About Project Management, New York: Marcel Dekker.
ACCREDITATION Goals: Goals: - Certify to the public and to educational organizations that the school is recognized as an effective institution of learning.
LBTI Program Management Review Phil Hinz S.H. (Hop) Bailey 2 December
Fifth Lecture Hour 9:30 – 10:20 am, September 9, 2001 Framework for a Software Management Process – Life Cycle Phases (Part II, Chapter 5 of Royce’ book)
CAPACITY Composition of the Atmosphere: Progress to Applications in the user CommunITY STUDY OVERVIEW AND LOGIC Michiel van Weele, KNMI Kick Off/ Negotiation.
CLIC Implementation Studies Ph. Lebrun & J. Osborne CERN CLIC Collaboration Meeting addressing the Work Packages CERN, 3-4 November 2011.
Software Product Line Material based on slides and chapter by Linda M. Northrop, SEI.
A global approach to ELT instrument developments J.-G. Cuby for the French ELT WG.
1 CS 501 Spring 2004 CS 501: Software Engineering Lecture 2 Software Processes.
Software Life Cycle The software life cycle is the sequence of activities that occur during software development and maintenance.
Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.
Software Project Management Lecture 5 Software Project Risk Management.
1 Global Design Effort: Controls & LLRF Controls & LLRF Working Group: Tuesday Session (29 May 07) John Carwardine Kay Rehlich.
Yazd University, Electrical and Computer Engineering Department Course Title: Advanced Software Engineering By: Mohammad Ali Zare Chahooki The Project.
Reproduction interdite © ALMA EUROPEAN CONSORTIUM Reproduction forbidden Design, Manufacture, Transport and Integration in Chile of ALMA Antennas Page.
SRR and PDR Charter & Review Team Linda Pacini (GSFC) Review Chair.
1 RBM Workplanning and Budgeting-FAO Managing for results in FAO Module II. Operational Planning ‘Workplanning’
TE-CRG-CE OMP Meeting 06 / 11 / 2014TE-CRG-CE OMP Meeting.
HNSciCloud Project MSc in Project Engineering delivered by Professor Gilles Vallet Oxford Academics for Computing Science Department, University of Chester.
Business Continuity Disaster Planning
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Supplier Management Can’t live with them, Can’t live without them!
Instrument Control Systems Seminar, 20 October 2014 Instrument Development Process Hans Dekker.
Cost and Schedule Paul Weinman Pacific Northwest National Laboratory.
Software Engineering — Software Life Cycle Processes — Maintenance
ITIL SERVICE LIFECYCLE
Software Life Cycle “What happens in the ‘life’ of software”
Business System Development
The value of a project-oriented approach to IT and how we do it in IBM
Defining the Activities
MRL 6 Artifacts (at End of TMRR) Page 1 of 6
Preparations for a Lehman Review
CSCI 577b Tasks and Activities
DOD’S PHASED SYSTEM DEVELOPMENT PROCESS
Integrated Delivery Model
APT – Planning the Next Phase & Resourcing Risk 2 Nov
SVT – SuperB Workshop – Frascati Sept. 2010
Bridging the ITSM Information Gap
Detector Proto-Technical board Sep 30, 2010
Bridging the ITSM Information Gap
Presentation transcript:

MUSE KO: MUSE Support at ESO ‘customer’  MUSE Team Created (ESO-customer), contacts with the Consortium and support activities on-going  Budget and Manpower in the ESO Long Range Plan  SoW and Tec Spec advanced, several iterations took place, within ESO and with the Consortium  Reflective Slicer Prototypes contract (130 K) agreed, supporting the project until contract signature  Reporting to ESO management, governing bodies

MUSE KO: PHASE A Follow-up (Management) 1) Missing Manpower, Staffing: Collaboration with LAOMP  National agency support ? New Key-Personnel ensured (e.g. System Engineer)  Relatively high turnover 2) Contain the Budget: Reflective Image Slicer  Review of some requirements pending (e.g. Cal Unit, PDR) 3) Product Assurance: WP created, responsible individuated, staff trained

Muse KO: Phase A Action Items (Consortium) AI19) Identify Responsible VPHG work (closed) AI21) Identify how PA activities will be carried out (~closed) AI22, AI23) Prepare consolidate and manpower budget (~closed) 8 AI to be closed within the next months! E.G. Space (Electronics on Platform), Specs of detector system, NFM error budget, case for back focal distance..

MUSE KO: Phase A Action Items (ESO) AI25) Add requirements on data analysis in Tec Spec (~Closed) AI26) Specify minimum instrument throughput in Tec Spec (~Closed: values not yet agreed by Consortium) AI27) Include in TecSpec specs access around the Instrument (Closed) 2 Important AI to be closed in the next months (increase of VLT back focal distance, platform vibrations): some work is started AI30) Review AO+LGS: pending (see Hubin presentation)

MUSE KO: Strategic Risk The MUSE project is strictly connected to two R&D projects: AO Deformable Secondary and development of new lasers While an AO-assisted MUSE is clearly the baseline option and ESO will make all reasonable efforts to fulfill this task, a non negligible risk exists that one of these developments cannot be completed and MUSE will have no AO system The MUSE Consortium should consider this scenario, and fully develop a strategy which takes it into account (science cases, review of top instrumental characteristics...)

MUSE KO: Next Milestone PDR: In addition to ‘usual’ analysis a number of AI have been stressed at Phase A Review (Stability during operations, Thermal power budget, Enclosure Integration Plan Europe and Chile, Maintenance concept..) Image Slicer Prototypes fully tested and evaluated, all critical items assessed.