Epics Deployment at Fermilab

TL;DR

This paper describes Fermilab's development of a robust EPICS deployment framework, including CI/CD pipelines and template IOCs, to support PIP-II project needs and modernize legacy control systems.

Contribution

It introduces a new software pipeline and infrastructure for deploying EPICS controls at Fermilab, enabling rapid development and integration for PIP-II.

Findings

Successful deployment of a CI/CD pipeline for EPICS controls

Implementation of template IOCs for quick deployment

Effective integration with legacy control systems

Abstract

Fermilab has traditionally not been an EPICS house; as such expertise in EPICS is limited and scattered. PIP-II will be using EPICS for its control system. When in operation, it will need to interface with the existing, modernized (see ACORN) legacy control system. Treating EPICS controls at Fermilab as a green field, we have developed and deployed a software pipeline which addresses these needs and presents to developers a tested and robust software framework, including template IOCs from which new developers can quickly deploy new front ends, aka IOCs. In this presentation, motivation for this work, implementation of a continuous integration/continuous deployment pipeline, testing, template IOCs, and the deployment of user services/applications will be discussed. This new infrastructure of IOCs and services is being developed and used in the PIP-II cryomodule teststand; our experiences and lessons learned will be also be discussed.