TRENDS ANALYSIS OVERSIGHT Dan Schwartz Development and Operations Science Support/ Technical Support Team 12 January 2004 CXC Users Committee SOT/DAS.

Slides:



Advertisements
Similar presentations
Managing Hardware and Software Assets
Advertisements

Excellence in Causal Analysis Establishing the infrastructure to support high quality causal analysis Frederic Lake/Larry Leavitt Palo Verde Nuclear Power.
Integra Consult A/S January 2006Karachi, Pakistan Severity Classification Scheme.
Succession Planning and Supply Processes
PROJECT RISK MANAGEMENT
PROPOSED PRIORITIES FOR SCIENCE AND COLLABORATION OCTOBER 2012.
A MULTI-STAKEHOLDER APPROACH TO DEVELOPING INDICATORS TO ASSESS AND MONITOR GOVERNANCE IN UGANDA Dorcas Nabukwasi H Statistician Uganda Bureau of Statistics.
Project Selection (Ch 4)
System Safety Concepts Dave Balderston Office of System Safety March 26, 2003.
Brief Overview of New ALCAM
Chandra Calibration Status ACIS 1.Gain corrections for epochs 28 and 29 (Nov – April 2007) were released in CALDB 3.4 on May 16, Gain corrections.
CXC EPHIN Status and Alternatives Michael Juda. CXC EPHIN StatusPage 2 Outline 1.EPHIN description 2.Thermal issues 3.+27V rail anomaly and impacts 4.Operations.
QUALITY MANAGEMENT DEFINITIONS AND CONCEPTS QUALITY MANAGEMENT TOOLS QA / QC PROCESS COMPUTERS AND PROJECT QUALITY.
Project Risk Management
CXC Manager’s Status Report Chandra User Committee Meeting Roger J. Brissenden 25 June 2002.
Chandra Calibration Status Calibration Updates Since Last CUC Meeting ACIS 1. A full set of calibration products for S0, S4 and S5 at T=-120 C, including.
Chandra X-Ray Observatory CXC SOT, FOT, ACIS & MSFC PS October 19, Update on a Proposed Bakeout CXC SOT & FOT, ACIS Instrument Team and CXC SOT.
Section 15-1GLAST Ground System Design Review August 18&19, 2004 ISOC Organization ISOC Manager R Cameron Commanding, H&S Timeline Planning Command Generation.
Tracking Chandra Science Productivity Publication Metrics special thanks to John Bright, Arnold Rots, and Sherry Winkelman (Archive Group) and Mihoko Yukita.
CXC Manager’s Status Report Chandra Users’ Committee Meeting Edward M. Mattison 29 June 2004.
Project Risk Management Risk Mitigation. Risk Management  The prime objective of risk management is to minimize the impact and probability of the occurrence.
Introduction to Network Defense
® IBM Software Group © 2006 IBM Corporation PRJ480 Mastering the Management of Iterative Development v2 Module 3: Phase Management - Inception.
SEC835 Database and Web application security Information Security Architecture.
Chapter 21 Copyright ©2012 by Cengage Learning Inc. All rights reserved 1 Lamb, Hair, McDaniel CHAPTER 21 Customer Relationship Management (CRM)
PRM 702 Project Risk Management Lecture #28
Copyright © 2012 Pearson Education, Inc. Publishing as Prentice Hall 4.1.
14-18 Nov 2005ESWW – SAAPS1 SAAPS Spacecraft Anomaly Analysis and Prediction System ESA Contract 11974/96/NL/JG(SC) Two year project (April 1999 – June.
Project Risk Management. The Importance of Project Risk Management Project risk management is the art and science of identifying, analyzing, and responding.
Risk Management Report to Audit Committee 26 September 2006 Lee Harris Assistant Chief Executive.
N By: Md Rezaul Huda Reza n
The Health Roundtable 4-4c_HRT1215-Session_CLARK_PCHosp_QLD TPCH: Using Data to Improve Performance – The Clinical Dashboard Presenter: Kevin Clark The.
HIT241 - RISK MANAGEMENT Introduction
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Analyze Opportunity Part 1
Risk planning & risk management (RM)
IIA_Tampa_ Beth Breier, City of Tallahassee1 IT Auditing in the Small Audit Shop Beth Breier, CPA, CISA City of Tallahassee
Software Engineering Lecture # 17
Event Management & ITIL V3
Chapter 11: Project Risk Management
Lecture 1: Project Initiation SYS366 Definition of a Project A Project is a sequence of unique, complex, and connected activities having one goal or.
ANALYTICS T H E W O R K F O R C E S T O R Y T E L L E R.
The Quality Colloquium at Harvard University August 27, 2003 Patient Safety Organizational Readiness Assessment Tool Louis H. Diamond, MDBeverly A. Collins,
Formulating a Simulation Project Proposal Chapter3.
INFORMATION SYSTEMS FOR MANAGEMENT. Agenda Information system project Organization analysis.
Agenda Interthink – 2003 Organizational Project Management Baseline Study –Industry Profile –Country Profile –Organization Size –Data On Schedule –Data.
Software Production Chapter 2: Identifying Software Development Activities.
Usability The lack of usability can cost time and effort, and greatly determine the success or failure of a system. In order for a tool to be effective,
11 Mayview Regional Service Area Plan (MRSAP) Tracking: Supporting Individuals in the Community June 18, 2008.
Project Risk Management Planning Stage
Consultant Advance Research Team. Outline UNDERSTANDING M&E DATA NEEDS PEOPLE, PARTNERSHIP AND PLANNING 1.Organizational structures with HIV M&E functions.
Software Project Management
C2d Data flow diagram BCD from SSC Texas SAO Quality Analysis and Improved Calibrated Data Mapping team.
Security Environment Assessment. Outline  Overview  Key Sources and Participants  General Findings  Policy / Procedures  Host Systems  Network Components.
Pertemuan 16 Materi : Buku Wajib & Sumber Materi :
TRAC Software for creation of supplier contract risk profile
ERP and Related Technologies
Chapter Communicating in Times of Crisis C H A P T E R.
Computer Science / Risk Management and Risk Assessment Nathan Singleton.
Dr. Gerry Firmansyah CID Business Continuity and Disaster Recovery Planning for IT (W-XIV)
Information Systems Development. Outline  Information System  Systems Development Project  Systems Development Life Cycle.
Project Evaluation and Programme Management
8 Managing Risk (Premium).
Chapter 4: Project Integration Management
CHAPTER11 Project Risk Management
FMEA PROCESS FLOW Causes/ failure mechanisms Product definition
Recognization and management of RISK in educational projects
CLINICAL INFORMATION SYSTEM
Risk Management Process (Revised)
Succession/Replacement Planning
Presentation transcript:

TRENDS ANALYSIS OVERSIGHT Dan Schwartz Development and Operations Science Support/ Technical Support Team 12 January 2004 CXC Users Committee SOT/DAS

OUTLINE  MISSION STATEMENT  OVERSIGHT ISSUES  IMPLEMENTATION PLANNING 12 January 2004 CXC Users Committee SOT/DAS

MISSION STATEMENT “(7)Monitoring and Trends Analysis – The CUC recommends that the CXC provide a higher level of oversight to the SI performance monitoring and trending analysis program to ensure that appropriate performance quantities are being tracked.” GOAL: Identify ANY changes in instrument performance before they occur. (Walkthrough example: ACIS gain) 12 January 2004 CXC Users Committee SOT/DAS

ISSUES Technical:  Identification of specific, potential, changes  Identification of indicators for each such change  Calculation of quantities to provide the indication (the trended quantity)  Assessment of the sensitivity of the trended quantity to Instrument change  What quantities must be determined more precisely (than currently), so that we are sensitive to any changes? 12 January 2004 CXC Users CommitteeSOT/DAS

ISSUES CONT… Software:  Database review  Report generation  Correlations and predictions Organizational:  Who is the monitor of each quantity?  How does the software get developed?  How do we educate CXC to use the existing tools? 12 January 2004 CXC Users Committee SOT/DAS

IMPLEMENTATION PLAN  Team is drawn from DOSS, CAL, SI IPI teams, FOT, project-wide  Divide by subsystems:  ACIS  HRC  LETG  HETG  HRMA  ACA  Other PCAD (e.g., IRU, fid lights and transfer, mounting stability, FSS  Other spacecraft equipment (e.g., reaction wheels, jitter stability, optical bench, focus and translation, EPHIN)  Other infrastructure (e.g., ACE, GOES, internet connectivity)  List the quantities which may change  Make two rank orders for each subsystem  Likelihood of occurrence  Effect of occurrence  Group assesses what can/must/should be monitored KEY POINT: One person responsible for each identified quantity. 12 January 2004CXC Users Committee SOT/DAS