Update docs/2._Services_Portfolio/Hardware_Portfolio/index.md
Build and Deploy Documentation / build-and-deploy (push) Successful in 3s
Build and Deploy Documentation / build-and-deploy (push) Successful in 3s
This commit is contained in:
1 parent
bd78fb736a
commit
e486869e74
1 file changed
+1
-1
@@ -4,6 +4,6 @@ The Hardware Portfolio defines the catalog of physical control, acquisition, mot
|
||||
|
||||
Whereas our Services section describes our ongoing operational infrastructure and engineering workflows (such as computing infrastructure, data archiving, and commissioning workflows), the Hardware Portfolio answers a concrete question for beamline scientists, instrument designers, and engineers:
|
||||
|
||||
"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?"
|
||||
> *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 end user, with Controls providing integration via community drivers or configuration-only support.
|
||||
Reference in new issue
Block a user