Controls/gitea-pages
0
2 Fork 3
Code Pull Requests Actions Activity

Update docs/2._Services_Portfolio/Hardware_Portfolio/index.md
Build and Deploy Documentation / build-and-deploy (push) Successful in 3s
Details

Browse Source
This commit is contained in:
acerbo_a committed 2026-11-03 21:41:04 +01:00
1 parent fe42d13d48
commit bd78fb736a
1 file changed
+1 -1
Download Patch File Download Diff File Expand all files Collapse all files
docs/2._Services_Portfolio/Hardware_Portfolio/index.md
+1 -1
View File
@@ -6,4 +6,4 @@ Whereas our Services section describes our ongoing operational infrastructure an
"If I select Hardware Platform X for my beamline or accelerator subsystem, what exact level of hardware, software driver, UI, and operational support will the Controls Section provide?"
Not all hardware connected to EPICS receives the same level of institutional support. Choosing a Tier 1 (Turnkey Standard) platform guarantees that Controls stocks spare parts on-site, builds and tests the crate, actively develops or maintains the EPICS driver, provides ready-to-use caQtDM screens, and supports hardware swaps during 24/7 Pikett shifts. Conversely, choosing specialized third-party or legacy hardware places spare-part stocking and physical diagnostics on the instrument group, with Controls providing integration via community drivers or configuration-only support.
Not all hardware connected to EPICS receives the same level of institutional support. Choosing a Tier 1 (Turnkey Standard) platform guarantees that Controls stocks spare parts on-site, builds and tests the crate, actively develops or maintains the EPICS driver, provides ready-to-use caQtDM screens, and supports hardware swaps during 24/7 Pikett shifts. Conversely, choosing specialized third-party or legacy hardware places spare-part stocking and physical diagnostics on the end user, with Controls providing integration via community drivers or configuration-only support.