RTN-064
JOR recommendations#
Review recommendations extracted from Jira.
2026-11-17 16:45
Issue key |
Rec# |
Summary |
Report date |
Due Date |
Implementation Status |
Assignee |
Description |
Response |
Implementation Status Description |
|---|---|---|---|---|---|---|---|---|---|
Update Scheduler to Final LSST Survey Configuration and Resolve SV Survey Faults |
CCR2_ORR1_2025 |
2026-12-31 |
In Review |
Leanne Guy |
Update the scheduler to final configuration of LSST survey based upon survey optimization and potential changes in exposure cadence. Resolve any scheduler faults that may have occurred during the SV survey. Complete before the end of CY 26. |
Summit is now updated to v4.5 of rubin_scheduler (prerequesite for deploying v5.3 configuration) and configuration for v5.3 has been pushed to PR. Further testing will occur as we return on sky. |
|||
Finalize Image Quality Optimization with AO Controls Expert |
CCR2_ORR1_2025 |
2026-12-31 |
In Progress |
Sandrine Thomas |
NSF responsibilities: Before the end of CY 26, complete the optimisation of the image quality with the help of an external expert in AO controls (e.g., Marcos Van Dam). |
We have asked Luke Johnson from NSO to review some of our issues. We are also planning to seek help from other AO experts |
Several external people have been invited in to support the AOS development with varying levels of success. JOR response plans with Luke Johnson still in development Full circle of louvers (low/TMA level) should be (approx) complete coming out of the Sept/Oct engineering downtime. Final 2 over Rad door are being installed but with competing resource needs in the downtime. |
||
Finalize Outstanding Science Requirements Validations |
CCR2_ORR1_2025 |
2026-12-31 |
To Do |
Zeljko Ivezic |
NSF and DOE: Complete the outstanding Science Requirements Validations before the end of CY 26. |
It will be addressed once more data are collected and analyzed. |
The validation team will complete the outstanding Science Requirements Validations once we are collecting on-sky data again. |
||
DM-2026:1-1 |
Revisit DR1+ Release Schedule & Cadence |
JOR_2026 |
2027-09-30 |
In Progress |
Zeljko Ivezic |
The Rubin Data Release Board should revisit the data release schedule and cadence beyond DR1, with a clear inputs and procedure defined, and make recommendations to the Rubin Director. [deliver and review before the end of FY27] |
The Head of LSST is working with the Data Release Board to fix the schedule for DR1. Conversations for community input have happened with the SAC and Science Collaboration Chairs and will continue until the new schedule is agreed upon. |
||
DM-2026:1-2 |
Strategic Hardware Procurement Plan |
JOR_2026 |
2027-09-30 |
To Do |
William O’Mullane |
Produce and maintain a strategic hardware procurement plan. [deliver and review before the end of FY27] |
A update of DMTN-135 has been drafted and is in internal review. |
||
DM-2026:1-3 |
Establish Rubin AI Strategy Group |
JOR_2026 |
2027-12-15 |
In Progress |
Phil Marshall |
Establish a Rubin AI Strategy Group to develop a strategic vision and prioritized recommendations for the adoption of artificial intelligence and machine learning across Rubin operations. [group constituted by December 2026; initial vision by June 2027, in time to inform FY29 procurement commitments; full recommendations by December 2027] |
We will do this, using the JOR2026 SC1 report Comment 12 to charge the AI Strategy Group. |
We will do this, using the JOR2026 SC1 report Comment 12 to charge the AI Strategy Group. |
|
DM-2026:1-4 |
Assess Feasibility of Smoothing DM Staffing |
JOR_2026 |
2027-09-30 |
To Do |
William O’Mullane |
Rubin and the agencies should jointly assess the cost and feasibility of smoothing the operations staffing profile through DR1 delivery. [staffing process before the end of FY27] |
DM is working with NL and SLAC managemnt to re prioritise some staff. The larger funding question is between the agencies and Rubin not DM. |
||
DM-2026:1-5 |
Re-baseline Release Schedule vs. Staffing |
JOR_2026 |
2026-12-31 |
To Do |
William O’Mullane |
Rubin should re-baseline the data release schedule against the staffing actually projected to be available. [schedule re-baseline before the end of CY2026] |
DM continues to work on a realistic DR schedule incorporating community needs and project resource. |
||
DM-2026:1-6 |
Discuss DM Staffing/Competencies with NSF & DOE |
JOR_2026 |
2027-09-30 |
In Progress |
Phil Marshall |
Rubin management should discuss current staffing levels and competencies of the DM team with NSF and DOE, to address concerns related to hires and assignments resulting from the NOIRLab and SLAC matrix structure [before the end of FY27] |
We will do this. We accept the key input from the JOR2026 report Comments that “where the Rubin team carries accountability for a deliverable, it should have a defined role in selecting the staff assigned to meet it, including participation in the assessment of candidates put forward by contributing institutions.” We will establish this as our process for staffing open positions. |
We will do this. We accept the key input from the JOR2026 report Comments that “where the Rubin team carries accountability for a deliverable, it should have a defined role in selecting the staff assigned to meet it, including participation in the assessment of candidates put forward by contributing institutions.” We will establish this as our process for staffing open positions. |
|
DM-2026:1-7 |
Engage Developers to Accelerate Code / GPU Transition |
JOR_2026 |
2027-09-30 |
To Do |
William O’Mullane |
Rubin DM should engage additional expert developer(s) to facilitate the acceleration of the most time-consuming codes, including partial transition to GPU’s. [by end FY27] |
It is not clear given budgets that we can accept this reccomentadtion. |
There is no budget to engage new developers to accelerate code. We will try to increase internal effort on optimisation (including GPU) |
|
SO-2026:2-1 |
Resolve Dome Louver Actuator Acquisition |
JOR_2026 |
2026-10-01 |
To Do |
Sandrine Thomas |
If an adequate resolution of the actuator acquisition is not reached by October 1, 2026, Rubin management should convene a review to consider and implement an alternate approach. |
While not yet closed (Victor Krabbendam should own this item or be invited to comment) latest reports are that the funding issues to extend EIE contract (long term software support, etc) has been cleared and details we being worked out. Reil suggests “very soon” as of start of October 2026 |
||
SO-2026:2-3 |
Formalize Issue Escalation To Higher Level Management |
JOR_2026 |
2027-04-01 |
To Do |
Sandrine Thomas |
Rubin management should develop formalized impact thresholds regarding the escalation of the visibility of issues [from the departments] to higher level management. This should include quantitative thresholds based upon cost, FTE effort, and/or impact on observing schedule. Complete by April 1, 2027. |
No progress on this yet. Not urgent as there have not yet been cases where needed. Impacts to observing are always discussed directly with management, the few times we have needed to go off sky for the scale of a night the person in Chile making the call was supported. We will, however, work to formalize as suggested. |
||
SO-2026:2-4 |
Continue Image Quality Improvement Plan |
JOR_2026 |
2027-04-01 |
To Do |
Sandrine Thomas |
Continue to execute the Image Quality Improvement Plan. Support the image quality team at the current strength. Report on progress to the agencies by April 1, 2027. |
After 1-2 weeks back on sky in “survey mode” (late Oct 2026) we will resume the once or twice weekly engineering (part) nights to continue to make progress. |
||
SO-2026:2-5 |
Support AI in CMMS/FRACAS |
JOR_2026 |
2027-08-31 |
To Do |
Holger Drass |
Support the emerging efforts to implement AI capabilities in CMMS/FRACAS to gain additional operational efficiencies. Report on progress at next annual Operation Review. |
Reporting for Holger, I report that we have an intern/student working to set up the needed interfaces to allow AI produced predicted maintenance to be added to CMMS/Jira calendars etc. Actual AI/machine learning analysis still pending but being persued. |
||
ESH-2026:3-2 |
Independent External Review of ES&H Program |
JOR_2026 |
2027-01-31 |
In Progress |
Robert Blum |
The Management Board should commission an independent, external review of a revised ES&H program. Focus the review on organization structure, staffing, coherence of the team and recommend corrective actions. Provide the report of the review to the agencies. - [January 2027] |
Accepted. The due date may need to adjust by a month outward to accommodate schedules for the initial Corrective Action Plan which has an internal review in mid October. |
Following the EHS Corrective Action Plan, the Director will work with the Management Board to set up this review. |
|
BS-2026:4-1 |
Hyper-Focus Meetings on Cost/Risk Opportunities |
JOR_2026 |
2026-09-30 |
In Progress |
Phil Marshall |
The Review Committee strongly encourages the team to engage in scheduled hyper-focus meetings to identify opportunities and to develop proactive strategies to realize potential opportunities. The deliberate, hyper-focus on potential opportunities and cost savings and to reduce risks. (Provide initial results to the funding agencies by September 30, 2026) |
We will do this, starting in the run-up to the start of FY27 as recommended and focusing on opportunities to save on cost, reduce schedule and mitigate risk. |
The first hyper-focus meeting has taken place. The team has not come up with a strategy that can significantly mitigate our expected budget reduction/non-optimal ramp in staffing beyond FY27. We continue to put out resource needs and a small number of these will provide needed effort that will help. We will move the due date out now to report on further progress. |
|
M-2026:5-1 |
Dome Louver Completion Plan |
JOR_2026 |
2026-11-16 |
In Progress |
Victor Krabbendam |
A plan for completion of the louvers should be established by Oct. 1, 2026. If no plan is established by then, a detailed back-up plan (which should be readied now) should be put into motion (by Nov. 15, 2026). |
NSF funding approval has been received. I will be working contract and delivery details over the coming weeks and put updates here. |
||
M-2026:5-2 |
Formalize In-Kind Contributions (IKC) Expansion |
JOR_2026 |
2027-02-01 |
In Progress |
Robert Blum |
Consider formalizing an expansion of In-Kind Contributions (IKC) to address potential mitigation of DM funding and staff shortfalls (by Feb. 1, 2027). |
We accept this recommendation. We will assess the efficacy of new programs with the IPC team and decide how to move forward. |
We have begun discussions with the IPC team to focus on resource needs. |
|
M-2026:5-3 |
Inter-Lab Cybersecurity Task Force |
JOR_2026 |
2027-09-01 |
In Progress |
Robert Blum |
Convene an inter-lab task force to review cybersecurity plans with the intent to harmonize and harden potential security shortfalls. Have a technical review of the above (by September 1, 2027) |
We accept this recommendation. |
The Director will work with Rubin DM management at NOIRLab and SLAC and CISOs at NOIRLab and SLAC to set up this task force. |
|
M-2026:5-4 |
Cybersecurity Tabletop Exercise |
JOR_2026 |
2027-10-01 |
In Progress |
Robert Blum |
All stages involved in the data chain should participate in a cybersecurity-focused tabletop exercise (by October 1, 2027) |
We accept this recommendation. |
The Director will work with the SLAC and NOIRLab CISOs to establish a Table Top exercise. |
Tue Nov 17 16:45:00 UTC 2026