Multimission Ground Systems & Services MOS 2.0: A View of the Next Generation in Mission Operations Systems Duane L. Bindschadler, Carole A. Boyles, Carlos.

Slides:



Advertisements
Similar presentations
Requirements Engineering Processes – 2
Advertisements

1 Accessibility Forum Projects Bill Hetzner Jim Kindrick.
1 Senn, Information Technology, 3 rd Edition © 2004 Pearson Prentice Hall James A. Senns Information Technology, 3 rd Edition Chapter 7 Enterprise Databases.
Chapter 1: The Database Environment
Requirements Engineering Process
Chapter 27 Software Change.
Chapter 7 System Models.
Requirements Engineering Process
Chapter 24 Quality Management.
Configuration Management
Working with MS-ACCESS IS 240 – Database Management Lecture #2 – Assoc. Prof. M. E. Kabay, PhD, CISSP Norwich University
Chapter 1 The Study of Body Function Image PowerPoint
1 System Engineers Toolbox 1 Compliance Automation, Inc. INCOSE: NM Enchantment Chapter By Cheryl Hill August 12, 2009.
Introduction to Product Family Engineering. 11 Oct 2002 Ver 2.0 ©Copyright 2002 Vortex System Concepts 2 Product Family Engineering Overview Project Engineering.
Task Group Chairman and Technical Contact Responsibilities ASTM International Officers Training Workshop September 2012 Scott Orthey and Steve Mawn 1.
18 Copyright © 2005, Oracle. All rights reserved. Distributing Modular Applications: Introduction to Web Services.
Objectives To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process.
CPIC Training Session: Enterprise Architecture
1 State Wildlife Action Plans Wiki: Business Transformation Tutorial Brand Niemann July 5, 2008
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Determine Eligibility Chapter 4. Determine Eligibility 4-2 Objectives Search for Customer on database Enter application signed date and eligibility determination.
BUILDING THE CAPACITY TO ACHIEVE HEALTH & LEARNING OUTCOMES
FACTORING ax2 + bx + c Think “unfoil” Work down, Show all steps.
Grants 3.0 Departmental Administrator Review January 22, 2014.
Communicating over the Network
Gaining Senior Leadership Support for Continuity of Operations
1 Implementing Internet Web Sites in Counseling and Career Development James P. Sampson, Jr. Florida State University Copyright 2003 by James P. Sampson,
Chapter 7 – Design and Implementation
© Telelogic AB 1 Managing Change From Customer Request to Implementation Jean-Louis Vignaud & Dominic Tavassoli.
Transition from the Long Shutdown to Hot Checkout: Pre-Hot Checkout Steve Suhring Operability Manager 6/6/13.
Configuration management
Software change management
Fact-finding Techniques Transparencies
DOROTHY Design Of customeR dRiven shOes and multi-siTe factorY Product and Production Configuration Method (PPCM) ICE 2009 IMS Workshops Dorothy Parallel.
© 2010 Invensys. All Rights Reserved. The names, logos, and taglines identifying the products and services of Invensys are proprietary marks of Invensys.
Information Systems Today: Managing in the Digital World
PO.DAAC Team 2012 PO.DAAC User Working Group (UWG) Meeting March 7-8, 2012.
OOAD – Dr. A. Alghamdi Mastering Object-Oriented Analysis and Design with UML Module 3: Requirements Overview Module 3 - Requirements Overview.
1 Quality Indicators for Device Demonstrations April 21, 2009 Lisa Kosh Diana Carl.
Campaign Overview Mailers Mailing Lists
1 Web-Enabled Decision Support Systems Access Introduction: Touring Access Prof. Name Position (123) University Name.
1. 2 August Recommendation 9.1 of the Strategic Information Technology Advisory Committee (SITAC) report initiated the effort to create an Administrative.
Legacy Systems Older software systems that remain vital to an organisation.
1 Undirected Breadth First Search F A BCG DE H 2 F A BCG DE H Queue: A get Undiscovered Fringe Finished Active 0 distance from A visit(A)
MANAGING INFORMATION TECHNOLOGY 7th EDITION
Microsoft Office Illustrated Fundamentals Unit C: Getting Started with Unit C: Getting Started with Microsoft Office 2010 Microsoft Office 2010.
VOORBLAD.
1 Breadth First Search s s Undiscovered Discovered Finished Queue: s Top of queue 2 1 Shortest path from s.
IS-700.A: National Incident Management System, An Introduction
©2007 First Wave Consulting, LLC A better way to do business. Period This is definitely NOT your father’s standard operating procedure.
Factor P 16 8(8-5ab) 4(d² + 4) 3rs(2r – s) 15cd(1 + 2cd) 8(4a² + 3b²)
1 Human Factors Course Session 3 Eric Davey Crew Systems Solutions 2007 March 28.
© 2012 National Heart Foundation of Australia. Slide 2.
Lecture plan Outline of DB design process Entity-relationship model
1 Knowledge Transfer Concepts Presented by the Division of Personnel State of Alaska.
Executional Architecture
25 seconds left…...
Module 12 WSP quality assurance tool 1. Module 12 WSP quality assurance tool Session structure Introduction About the tool Using the tool Supporting materials.
Database Administration
PSSA Preparation.
Chapter 11 Component-Level Design
Modeling Main issues: What do we want to build How do we write this down.
From Model-based to Model-driven Design of User Interfaces.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Rational Unified Process Fundamentals Module 4: Disciplines II.
MODEL-BASED SOFTWARE ARCHITECTURES.  Models of software are used in an increasing number of projects to handle the complexity of application domains.
Viewpoint Modeling and Model-Based Media Generation for Systems Engineers Automatic View and Document Generation for Scalable Model- Based Engineering.
Presentation transcript:

Multimission Ground Systems & Services MOS 2.0: A View of the Next Generation in Mission Operations Systems Duane L. Bindschadler, Carole A. Boyles, Carlos Carrion, and Chris L. Delp Jet Propulsion Laboratory, California Inst. Of Technology Pasadena, CA, U.S.A.

Multimission Ground Systems & Services Outline Background Motivation –Why architect and model Example – Process identification & modeling Example – Model-based approach to scenarios Future Work Improving Space Operations WorkshopBindschadler – 2

Multimission Ground Systems & Services Background Multimission Operations –A multi-mission operations capability is engineered so as to require minimal work effort to adapt across the defined range of customers (deep-space robotic missions). This includes consideration across the lifecycle of the customer and of the capability itself. Multiple success 1990 – early 2000s –Range of applicable missions limited –Faster-better-cheaper (not maintainable long term) Competitive pressures motivate search for more efficient methods Operations Revitalization Initiative will help to create those methods –Architected, model-based MOS 2.0 Improving Space Operations WorkshopBindschadler – 3

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 4 MOS in Context

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 5 Why Architect & Model? Systems and enterprises have architectures, whether or not they are explicitly documented and maintained Architectural approaches identify and address stakeholder concerns –Enterprise-wide to very fine-grained –Distinct viewpoints address concerns Model-based approaches enable –More formal, explicit specification –Management of complexity –More evolvable systems

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 6 Why Architect & Model? Right" time to do it. –MBSE/architecture initiatives and interest taking hold at JPL and across NASA –Standards are maturing –Modeling tools are becoming able to support formal, rigorous description of highly complex systems –Piece-meal approaches have not been as effective as anticipated

Multimission Ground Systems & Services Advantages Less work effort in documenting –Less time in Word or Powerpoint Increased focus on engineering design work Improved ability to make accurate predictions about the impact of changes Ability to model even complex processes Clearer path for automation Improving Space Operations WorkshopBindschadler – 7

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 8 Layered Reconciled MOSProcess Example

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 9 Activity Model – high level

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 10 Activity Model – next level

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 11 Assess requirements completeness Assist in identifying missing requirements Validate requirement intent Identify operational (process) and software interfaces Identify constraints on mission operations and assess operability Identify any outstanding issues Concept and Technology Development Phase Example: Scenarios

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 12 Why Build Scenarios? Documenting Science Goals Identifying Mission Operations Phases Identify Flight System and Ground System Constraints Baselines Science and Mission Capabilities Used in Support of Proposal and Cost efforts Preliminary Design and Technology Completion Phase

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 13 Scenario Process

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 14 Managing the Scenario Process-- The scenario tool was designed with the intent to support the process owner in facilitating the operations scenario process. The attributes specific to managing the Scenario Process are: –Status –Automatic –Electronic Signatures –Action Items –Revision Capability –Copy Capability –Attachments –Search capability on any field Scenario Tool Attributes

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 15 Scenario Tool Attributes Scenario Accessibility -- Scenarios are maintained in a web accessible environment that provides a structured set of scenario fields. Online Collaboration -- The scenario tool allows for collaboration through the use of a comments field. The comment is instantly visible.

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 16 Scenario Tool Attributes Interleaving Requirements -- The scenario tool has the ability to embed requirements into the scenario description. Linking to Interfaces -- Operational Interface Agreements (OIAs) are created to communicate agreements between teams. With the Advanced Multi-Mission Operations System (AMMOS) at JPL, the OIAs are maintained in a web based tool similar to the scenario tool.

Multimission Ground Systems & Services Improving Space Operations Workshop Bindschadler – 17 Requirements in Context

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 18 Scenario Tool Attributes Copy a Scenario – The tool allows key fields of a scenario be copied and stored for use on other missions. Revise a Scenario – Revision Capability helps supports the lifecycle of a scenario by finalizing the scenario at each key decision point in the lifecycle then assigning a revision naming convention and moving forward key fields.

Multimission Ground Systems & Services Next Steps Full lifecycle architecture for MOS 2.0 –Development (~Phase A – D) –Deployment (transition from Development to Ops) –Operations (Phase E) –Continuous improvement and maintenance Flow-down of system level to development of composable services –Mission Planning & Sequencing –Mission Control –Other services follow Coordinate & unify with software-focused architectural effort Improving Space Operations WorkshopBindschadler – 19

Multimission Ground Systems & Services Backup Material

Multimission Ground Systems & Services MOS & AMMOS Improving Space Operations WorkshopBindschadler – 21

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 22 MOS Functional View

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 23 Goals and Objectives

Multimission Ground Systems & Services Common Business Architecture Consist of –Business Process –High-level Information Architecture Related Products –Unified information concepts (timeline) –Uncover essential, unstated needs (reconciliation) –Documented common conceptual processes Improving Space Operations WorkshopBindschadler – 24

Multimission Ground Systems & Services Sustainability & Maintainability Information stored in a database, not individual files or documents (Word, PowerPoint, Visio, Excel, etc.) –Leverage non-proprietary standards –Multimission information in single source –Less re-inventing the wheel Utilize models to impact and assess changes –Allow for evolution of the system & its components –Assess & impact changes needed for specific missions Improving Space Operations WorkshopBindschadler – 25

Multimission Ground Systems & Services Ease of Adaptation Compose services at right level of granularity Make explicit relationships between software and processes/procedures Create and maintain standard interface descriptions –Facilitate creation of new or (when needed) mission- unique capabilities Improving Space Operations WorkshopBindschadler – 26

Multimission Ground Systems & Services Effective Capture of Knowledge Base Have already captured wealth of information via operational scenarios –See Delp & Carrion presentation 1500 Thurs in Interoperability session As-Is portions of Architectural model Improving Space Operations WorkshopBindschadler– 27

Multimission Ground Systems & Services System-Level Products AMMOS system-level Operations Requirements & Scenarios AMMOS Process Architecture and Design –Team Charters and Functions (components) –System-level process designs (components) –Interface definitions (connections) –AMMOS Operational Standards (constraints). –Training standards and materials (constraints). Improving Space Operations WorkshopBindschadler – 28

Multimission Ground Systems & Services Team-Level Products Team-level Ops requirements & scenarios Team Design Descriptions –Team Processes, Procedures –Operational Interface Agreements (OIAs) Team Management Plans Team Training Materials and Certification criteria. Designed with Project adaptation in mind. Improving Space Operations WorkshopBindschadler – 29

Multimission Ground Systems & Services Improving Space Operations WorkshopBindschadler – 30 Proposed AMMOS Functionality