Copyright Greg Nordstrom PhD, Apr 2001 MAPLANT Status Report MICANTS April 2001.

Slides:



Advertisements
Similar presentations
Software Project Management
Advertisements

CS487 Software Engineering Omar Aldawud
CHAPTER 1 SOFTWARE DEVELOPMENT. 2 Goals of software development Aspects of software quality Development life cycle models Basic concepts of algorithm.
Robert Neches & Pedro Szekely, USC ISI, © 2000 CAMERA, Logistics Working Group CAMERA - MICANT Coordination Robert Neches, Pedro.
Project Management Workshop. Nick Cook  Citigroup Corporate and Investment Bank  European Technology Business Office Manager Edinburgh University April.
DOM 102: Principles of Operations Management Operations Scheduling
CS3773 Software Engineering Lecture 8 Software Planning and Estimation.
1 Marvel Electronics and Home Entertainment e-Commerce System Final Status Report April 12, 2005 (Tuesday)
Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)
These courseware materials are to be used in conjunction with Software Engineering: A Practitioner’s Approach, 6/e and are provided with permission by.
Chapter 15 Design, Coding, and Testing. Copyright © 2005 Pearson Addison-Wesley. All rights reserved Design Document The next step in the Software.
Project Plan The Development Plan The project plan is one of the first formal documents produced by the project team. It describes  How the project will.
Chapter 2 - Overview of the Systems Engineering Design Process1 Aerospace Systems Engineering Chapter 2 - Overview of the Systems Engineering Design Process.
BAE SYSTEMS Overview of Systems Engineering at BAE SYSTEMS & ALENIA MARCONI SYSTEMS 8/10/2015/MS By Leigh Watton Friday 27th July 2001.
LSU 01/18/2005Project Life Cycle1 The Project Life Cycle Project Management Unit, Lecture 2.
SAP HR Systems Applications and products for Data Processing Its an ERP package Its has the biggest market share in the word What is involved in SAP project.
INDOT’s Scheduling / Project Management System (SPMS) Vision & Objectives for Next Generation SPMS Mike Jenkins, Indiana DOT Teresa Franklin, Info Tech,
Chapter 2 The process Process, Methods, and Tools
T Project Review RoadRunners [PP] Iteration
Institute for Software Integrated Systems Vanderbilt University MAPLANT A Decision Support Tool for Aircraft Maintenance Chris van Buskirk June 28 th,
BSBPMG402A Apply Time Management Techniques 1 Apply Time Management Techniques Week 6 Project Time Processes – Part 2 C ertificate IV in Project Management.
Organization and Implementation of a National Regulatory Program for the Control of Radiation Sources Staffing and Training.
Year 11 Info Tech Project Management Overview. Project management overview identifying tasks, resources, people and time scheduling tasks, resources,
MICANTS Scenario & Demo Description “A Day in the Life of VMA-513” Scenario by Russ Currer Presented by Greg Nordstrom.
Software Project Management Lecture # 7. Outline Project Scheduling.
Software Project Management Lecture # 7. What are we studying today? Chapter 24 - Project Scheduling  Effort distribution  Defining task set for the.
Robert Neches & Pedro Szekely, USC ISI, © 2001 CAMERA, CAMERA Coordination and Management Environments for Responsive Agents.
Lecture 6. Review of Lecture 5 Company strategic planning: mission and objective statements and competitive strategy. Planning Methods: Top-down, Bottom-up.
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.
MICANTS Gabor Karsai Benoit Dawant Greg Nordstrom Chris vanBuskirk Karlkim Suwanmongkol Patrick Norris Jonathan Sprinkle (Vanderbilt/ISIS) Jon Doyle Robert.
MICANTS Gabor Karsai Benoit Dawant Chris vanBuskirk Gabor Szokoli Jonathan Sprinkle Karlkim Suwanmongkol (Vanderbilt/ISIS) Jon Doyle Robert Laddaga Vera.
Title of presentation goes here Name of presenter Location/date © 2005 MPA. All rights reserved. Task Management in MS Project Genea Mallow-Jensen President,
MICANTS Gabor Karsai Benoit Dawant Greg Nordstrom Chris vanBuskirk Karlkim Suwanmongkol Patrick Norris Jonathan Sprinkle (Vanderbilt/ISIS) Jon Doyle Robert.
Refined ECSS Software Process Model Elements SD-TN-AI-0570, Issue 5 APPENDIX D.
Copyright Chris van Buskirk, Mar 2001 MAPLANT Status Report MICANTS March 2001.
MICANTS Gabor Karsai Greg Nordstrom Chris vanBuskirk Jon Doyle Vera Ketelboeter George Bloor Russ Currer Vanderbilt/ISIS MIT Boeing Idea Services Benoit.
BSBPMG402A Apply Time Management Techniques Apply Time Management Techniques Project Time Processes – Part 2 C ertificate IV in Project Management
Robotics & Engineering Design Projective Management Chin-Sung Lin Eleanor Roosevelt High School.
An Introduction to Software Engineering
Request for Proposal (RFP)
CSCI 521 Final Exam Review. Why Establish a Standard Process? It is nearly impossible to have a high quality product without a high quality process. Standard.
Presented By Dr. Mohsen Alardhi College of Technological Studies, Kuwait April 19 th,2009.
T Project Review RoadRunners [IM1] Iteration
SNAP-MAPLANT Integration Effort Strategy Meeting – 2 Mar 2001.
Manufacturing Plant maintenance Materials management Quality management.
Phase 3 The Software Requirements Specification. After review of the customer’s System Spec. After educated analysis Preliminary design A technical, software.
Software Project Management (SEWPZG622) BITS-WIPRO Collaborative Programme: MS in Software Engineering SECOND SEMESTER /1/ "The content of this.
CSPC 464 Fall 2014 Son Nguyen. 1. The Process of Software Architecting, Peter Eeles, Peter Cripss 2. Software Architecture for Developers, Simon Brown.
Model Integrated Computing and Autonomous Negotiating Teams for Autonomic Logistics G.Karsai (ISIS) J. Doyle (MIT) G. Bloor (Boeing)
Process Asad Ur Rehman Chief Technology Officer Feditec Enterprise.
PI2134 Software Engineering IT Telkom.  Layered technology  Software Process  Generic Process (by Pressman)  Fundamental activities (by Sommerville)
T Project Review ITSUPS Implementation
Software Development Life Cycle (SDLC)
Team-Based Development ISYS321 Managing the Information Systems Project.
T Project Review RoadMappers I2 Iteration
Slide 1 CS 310 Ch5: Project management What do you think is involved? Proposal writing Project costing Project planning and scheduling Project monitoring.
OUTAGE MANAGEMENT. OUTAGE APPROACH/PHILOSOPHY A) Time based / machine operating hours based concept related to OEM recommendations - More expensive than.
T Iteration Demo BitPlayers PP Iteration
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
6/6/ SOFTWARE LIFE CYCLE OVERVIEW Professor Ron Kenett Tel Aviv University School of Engineering.
Copyright 2000 Management Analytics Programming & Services1 Schedule Analysis 101 The Boring Stuff Is Essential By John F. Krahula Management Analytics.
Development Project Management Jim Kowalkowski. Outline Planning and managing software development – Definitions – Organizing schedule and work (overall.
Request for Proposal (RFP) In response to the RFP – the first step is to prepare a proposal 1. Review Customer Requirements and come up with candidate.
BSBPMG503A Manage Project Time Manage Project Time Project Time Processes Part 2 Diploma of Project Management Qualification Code BSB51507 Unit Code.
AXUG Partner Showcase – Introducing Preactor
Chapter 6: Database Project Management
By Dr. Awad Hanna Ross Umentum
Acquisition Sustainment Tool Kit (ASTK
Request for Proposal (RFP)
Workshop: High Level Reporting
Presentation transcript:

Copyright Greg Nordstrom PhD, Apr 2001 MAPLANT Status Report MICANTS April 2001

Copyright Greg Nordstrom PhD, Apr 2001 MICANTS Timeline April 2001: –SNAP integration –Practice run May 2001: –PI review & customer demonstration Late Summer 2001: –Initial assessment milestone

Copyright Greg Nordstrom PhD, Apr 2001 MAPLANT Context Diagram

Copyright Greg Nordstrom PhD, Apr 2001 Progress to Date Flight schedule driven maintenance scheduling –No longer simulated! Richer, more realistic data sets (XML) –VMA-513 personnel roster Full complement of personnel (202 maintainers) Ranks, quals by workcenter (10 WCs) –Calendar-based maintenance New inspections (7-, 14-, 28-, 56-, 112-, 182-, 364-, 365-, 448-day, 30mo) Mechanic requirements Tool requirements –Tools (tools.xml) Defined schema Code to load/save/manipulate/query Still need accurate counts –Maintenance plan represents typical healthy squadron Architectural, scheduler refinements –Tool-aware constraint generation –Optimization/scaling work (in progress) –Implemented Aircraft Availability Report algorithms

Copyright Greg Nordstrom PhD, Apr 2001 MAPLANT Input Data Flight schedule –A/C type –Sortie times (start, end, duration) –Pit/turn info –Event Priorities –Mission types –Ordnance Maintenance plan –Special inspection types –Side numbers –Due dates –Usage-based inspections Repair manual Inspection manual –Job type –Task breakdowns –Task duration –Equipment requirements –Personnel requirements –Task sequencing requirements New for April (simplified MOS) New for April Expanded for April Improved for April (no sim) Bold = In today’s demo

Copyright Greg Nordstrom PhD, Apr 2001 MAPLANT Input Data (cont.) Guidance –Shift length –Shift start –Holidays –Pit requirements (“extra” ready aircraft) Maintenance schedule –Shift-level (coarse grain) granularity –“Locked” maintenance actions Technical directives Aircraft inventory –Type –BUNO –Side number –Status & EOC codes –Frame number –Engine number –Lifecounts Roster –Manpower, skill level, qualifications, MOS MAFs Support equipment inventory –Type, location Bold = In today’s demo New for April (structure OK, need real data) New for April (partial)

Copyright Greg Nordstrom PhD, Apr 2001 What is being demonstrated Generation of a maintenance look-ahead reflecting: –Flight ops requirements –Aircraft special inspection requirements –1 week’s worth of scheduled inspections –Aircraft type, availability and status (up/down) –6 Night aircraft, 10 Radar aircraft –Maintenance guidance (shift durations, holidays, pit info) Iterative refinement –Phase 1: Shift-level granularity –Phase 2: Tasks scheduled down to the hour (configurable) Integrated MS Project ® -based reporting

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Aircraft Total Aircraft: 16 MC Aircraft: 12 of 16 6 Night, 10 Radar Aircraft

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Personnel Roster size: 202

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Flight Schedule

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Maintenance Plan

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Guidance

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Inspections

Copyright Greg Nordstrom PhD, Apr 2001 Input Data: Tools Total Tools: 225

Copyright Greg Nordstrom PhD, Apr 2001 Output: Maintenance Schedule

Copyright Greg Nordstrom PhD, Apr 2001 Output: Maintenance Schedule

Copyright Greg Nordstrom PhD, Apr 2001 Output: Maintenance Schedule

Copyright Greg Nordstrom PhD, Apr 2001 Output: A/C Availability

Copyright Greg Nordstrom PhD, Apr 2001 Demo

Copyright Greg Nordstrom PhD, Apr 2001 Discussion Points Inspection “alignment” (e.g. 14-, 28-day) Russ: –Is our Maintenance Plan real-world? –Single MOS code per workcenter ok for May? Yuma trip for week of 30 th. Pit, Turn encoding in FlightSchedule (ISIS  ISI)