Work Management System (WMS) aka Computerized Maintenance Management - PowerPoint PPT Presentation

Work Management System (WMS) aka Computerized Maintenance Management System (CMMS) Michael Rodriguez Systems Engineering Project Community Workshop August 14 th 2018 #lsst2018 #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 1

What is a WMS/CMMS? - There 1,440 minutes in a day. For the next 12ish years, each minute inside the dome should be allocated for and assigned to someone, on at least a weekly basis. • Account for time to stage large equipment, adjust environmental conditions for tests, order parts, etc. • There will inevitably be a backlog so we will never run out of tasks to fill the schedule. - Coordination of schedules for Planned Maintenance (Astronomers, Operators, Engineers, Safety, Maintenance Technicians, Contractors) - Interface to Issue Management System for handling Unplanned Maintenance . - Interface to Inventory Management system for parts and materials ordering. - Monitor trends, generate daily reports and ad-hoc alarms as needed. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 2

Needs for a Work Management System - Commissioning and Operations work on weekly and daily timescales needs to be planned. - Multiple Inputs: • Planned Work - Integration - Verification/Commissioning - Engineering - Maintenance - Calibration - Observing Unplanned Work • - Repairs - Issue Resolution - Priorities will change sometimes from day-to-day based on real time events. - A common, agile tool is needed to manage all of these inputs and plan work in a coherent and safe manner. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 3

Inputs and Outputs #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 4

What is the project deliverable? LSE-30 OS-REQ-0077 04 Maintenance Activity Support Specification: In support of all maintenance activity, both predictive and preventive, the LSST Observatory shall implement the following systems: - Comprehensive problem reporting, tracking, and management system - Work order driven preventive maintenance support system (usually known as CMMS for Computerized Maintenance Management System). - Warehouse inventory and property control - Document control center - Analysis tools for supporting predictive maintenance. Message box example for short highlighted messages. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 5

One Subsystem… LSE-61 TLS-REQ-0136 Telescope and Site Activity Support, Tracking and Reporting The Telescope and Site shall implement the following systems: Specification same as LSE-30, plus: The Telescope and Site shall maintain a permanent record of the description and time required to recover from all maintenance events. A set of automatic reports based on engineering telemetry shall be generated on a daily basis. NOTE: This requirement corresponds mostly to the OCS domain. T&S shall provide the necessary information to OCS for the maintenance management. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 6

What is a Work Order? Work Order = Task + Resources - Tasks include: replacing coolant, updating software, cleaning glass, etc. - Resources include: skilled people, procedures, facilities, consumables, parts, tools, power equipment, etc. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 7

Work Order Components #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 8

One Sample Task Implementation #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 9

Varieties of CMMS Implementation SAP-like Excel + Excellence • Large amount of effort and resources • Heavily dependent on individual people, Typically team of 30+ members for a year • representing a single point of failure and long or more ramp up for replacements or supplements. Large cost • Little or no integration of tools, requiring other • • Significant ongoing maintenance cost SMEs for different types of tools. • Significant cost of implementing change Large training effort involved • LSST (AURA)-Hybrid • Reduced initial cost due to use of existing tools and processes. Reduced ongoing maintenance costs due to use • of existing tools and contracts. • Challenges include the population of data and integration of systems. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 10

Subsystem View #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 11

A Common Tool for the Life of LSST - LSST will develop a single tool that meets the Work Management needs during Commissioning and Operations. System Level Verification Plans Scheduled Maintenance Scientifically Motivated Performance Daily Characterization Tasks Technical Optimization of System In-situ Issue Operations Resolution Emergent Technical Issues Workflow Inputs for Commissioning Plan of the Day Workflow for Operations #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 12

Challenges - Deliverable description (capability of system) - Development, verification and control of the BOM, as well as the many maintenance and safety procedures. - Population and control of parts lists - Procurement pipeline and supply chain • Some parts and materials take longer to reach Chile • Some materials have restrictions #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 13

Road Map Clarify project expectations. • • What is the deliverable? Processes, Tools, Procedures, Infrastructure, etc. • Specification/Requirements development and approval. Tool design and review, procurement, planning, resource allocation • • Implementation, population and verification Plan for maintenance of the system (updates, process implementation an • changes in tool). #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 14

A Recommended Implementation with Existing Tools #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 15

Verification in WMS #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 16

Verification in WMS – MagicDraw MBSE Tool Source of all project-controlled • requirements (specifications & ICDs) Source of all Verification Plans • Source of data for Verification Matrices • #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 17

Verification in WMS – Syndeia Inter-Tool Element Transformations Auto-generates Verification Tickets in JIRA from MagicDraw VerificationPlan elements • and attributes • Two-way synchronization Feeds verification results to MagicDraw to generate final verification matrices (VM-F) • • Verification is a component of Maintenance and has parallel and interlinking processes. #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 18

Maintenance in WMS • Map Maintenance Plans to Maintenance Tasks (test cases) Generate Maintenance Steps (scripts) for each Task • (Plan) Sequence Tasks into Maintenance Worklists • Execute Worklists • • Address failures with issue tickets • Sync results back to MagicDraw #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 19

JIRA Workflow for Maintenance Tickets - System Maintenance Team (SysMT) responsible for upfront planning SysMT SysMT • Generation of Maintenance Plans Mapping to Acceptance and • Closeout Events (Tasks) Definition of Closeout Events • ● SysMT works with the Systems Scientist and Shift Lead to Schedule activities SysMT ● Tickets get assigned to individuals + Systems Scientist responsible for the work. SysMT executes the Closeout Events and Analyzes Results CCT ● SysMT Reviews the results and makes the determination on the sufficiency of the results to close out the Closeout Event ● SysMT tracks closeout progress #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 20

Prototype Tool - <<Insert Video>> #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 21

Considerations During Implementation • Cross agency (observatories) cooperation . Similar activities, process, maintenance procedures, safety, quality processes and engineering tools are currently independently developed and “uniquely” implemented. Effort (and other resources) expended to develop and refine working processes and tools • may be shared . Preserve this organizational (AURA-wide) legacy for ongoing and future projects • • Mandatory Organizational Processes and Tools to be developed, purchased…or shared . • Management/Planning/Scheduling/Budgeting • Maintenance, Repairs and Issues Quality, Manufacturing and Procurement Processes, Safety Policies and Implementation • Configuration Management (Mission critical documentation, Drawings, Software, etc. • Resource Coordination (specialized equipment staging, calibrations, etc.) • #lsst2018 LSST Project and Community Workshop 2018 • Tucson • August 13 - 17 22