Lean Mission Operations Systems Design - Using Agile and Lean Development Principles for Mission Operations Design and Development

The Resource Prospector Mission seeks to rove the lunar surface with an in-situ resource utilization payload in search of volatiles at a polar region. The mission operations system (MOS) will need to perform the short-duration mission while taking advantage of the near real time control that the short one-way light time to the Moon provides. To maximize our use of limited resources for the design and development of the MOS we are utilizing agile and lean methods derived from our previous experience with applying these methods to software. By using methods such as "say it then sim it" we will spend less time in meetings and more time focused on the one outcome that counts - the effective utilization of our assets on the Moon to meet mission objectives

Reinventing User Applications for Mission Control

In 2006, NASA Ames Research Center's (ARC) Intelligent Systems Division, and NASA Johnson Space Centers (JSC) Mission Operations Directorate (MOD) began a collaboration to move user applications for JSC's mission control center to a new software architecture, intended to replace the existing user applications being used for the Space Shuttle and the International Space Station. It must also carry NASA/JSC mission operations forward to the future, meeting the needs for NASA's exploration programs beyond low Earth orbit. Key requirements for the new architecture, called Mission Control Technologies (MCT) are that end users must be able to compose and build their own software displays without the need for programming, or direct support and approval from a platform services organization. Developers must be able to build MCT components using industry standard languages and tools. Each component of MCT must be interoperable with other components, regardless of what organization develops them. For platform service providers and MOD management, MCT must be cost effective, maintainable and evolvable. MCT software is built from components that are presented to users as composable user objects. A user object is an entity that represents a domain object such as a telemetry point, a command, a timeline, an activity, or a step in a procedure. User objects may be composed and reused, for example a telemetry point may be used in a traditional monitoring display, and that same telemetry user object may be composed into a procedure step. In either display, that same telemetry point may be shown in different views, such as a plot, an alpha numeric, or a meta-data view and those views may be changed live and in place. MCT presents users with a single unified user environment that contains all the objects required to perform applicable flight controller tasks, thus users do not have to use multiple applications, the traditional boundaries that exist between multiple heterogeneous applications disappear, leaving open the possibility of new operations concepts that are not constrained by the traditional applications paradigm

Agile

This is based on a previous talk on agile development. Methods for delivering software on a short cycle are described, including interactions with the customer, the affect on the team, and how to be more effective, streamlined and efficient

Mission Control Technologies: Empowering Users

Traditional software is developed as monolithic applications that are typed and create boundaries around their domains. ARC, working with JSC, developed an object oriented user interface that reduced domain boundaries in software. We used agile participatory design to develop a solution with our customer in mission control

LSST Science Book, Version 2.0

A survey that can cover the sky in optical bands over wide fields to faint magnitudes with a fast cadence will enable many of the exciting science opportunities of the next decade. The Large Synoptic Survey Telescope (LSST) will have an effective aperture of 6.7 meters and an imaging camera with field of view of 9.6 deg^2, and will be devoted to a ten-year imaging survey over 20,000 deg^2 south of +15 deg. Each pointing will be imaged 2000 times with fifteen second exposures in six broad bands from 0.35 to 1.1 microns, to a total point-source depth of r~27.5. The LSST Science Book describes the basic parameters of the LSST hardware, software, and observing plans. The book discusses educational and outreach opportunities, then goes on to describe a broad range of science that LSST will revolutionize: mapping the inner and outer Solar System, stellar populations in the Milky Way and nearby galaxies, the structure of the Milky Way disk and halo and other objects in the Local Volume, transient and variable objects both at low and high redshift, and the properties of normal and active galaxies at low and high redshift. It then turns to far-field cosmological topics, exploring properties of supernovae to z~1, strong and weak lensing, the large-scale distribution of galaxies and baryon oscillations, and how these different probes may be combined to constrain cosmological models and the physics of dark energy.Comment: 596 pages. Also available at full resolution at http://www.lsst.org/lsst/sciboo

Interventions to improve system-level coproduction in the Cystic Fibrosis Learning Network

Background Coproduction is defined as patients and clinicians collaborating equally and reciprocally in healthcare and is a crucial concept for quality improvement (QI) of health services. Learning Health Networks (LHNs) provide insights to integrate coproduction with QI efforts from programmes from various health systems.Objective We describe interventions to develop and maintain patient and family partner (PFP) coproduction, measured by PFP-reported and programme-reported scales. We aim to increase percentage of programmes with PFPs reporting active QI work within their programme, while maintaining satisfaction in PFP-clinician relationships.Methods Conducted in the Cystic Fibrosis Learning Network (CFLN), an LHN comprising over 30 cystic fibrosis (CF) programmes, people with CF, caregivers and clinicians cocreated interventions in readiness awareness, inclusive PFP recruitment, onboarding process, partnership development and leadership opportunities. Interventions were adapted by CFLN programmes and summarised in a change package for existing programmes and the orientation of new ones. We collected monthly assessments for PFP and programme perceptions of coproduction and PFP self-rated competency of QI skills and satisfaction with programme QI efforts. We used control charts to analyse coproduction scales and run charts for PFP self-ratings.Results Between 2018 and 2022, the CFLN expanded to 34 programmes with 52% having ≥1 PFP reporting active QI participation. Clinicians from 76% of programmes reported PFPs were actively participating or leading QI efforts. PFPs reported increased QI skills competency (17%–32%) and consistently high satisfaction and feeling valued in their work.Conclusions Implementing system-level programmatic strategies to engage and sustain partnerships between clinicians and patients and families with CF improved perceptions of coproduction to conduct QI work. Key adaptable strategies for programmes included onboarding and QI training, supporting multiple PFPs simultaneously and developing financial recognition processes. Interventions may be applicable in other health conditions beyond CF seeking to foster the practice of coproduction