re-index Hardware Portfolio
Build and Deploy Documentation / build-and-deploy (push) Successful in 4s
Build and Deploy Documentation / build-and-deploy (push) Successful in 4s
This commit is contained in:
1 parent
8cb24cd34d
commit
aaf5bf8953
10 files changed
+17
-4
No files matched your search
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
File renamed without changes.
+3
-1
@@ -1,4 +1,6 @@
|
||||
# Motion Hardware Portfolio
|
||||
---
|
||||
title: Motion Hardware Portfolio
|
||||
---
|
||||
|
||||
Here you can find a short description of all hardware that is supported by the Controls section. For related contact information, please consult the "Contacts Support" part off this website.
|
||||
|
||||
+3
-1
@@ -1,4 +1,6 @@
|
||||
# Detector Portfolio
|
||||
---
|
||||
title: Detector Portfolio
|
||||
---
|
||||
|
||||
Here you can find a short description of all hardware that is supported by the Controls section. For related contact information, please consult the "Contacts Support" part off this website.
|
||||
|
||||
@@ -0,0 +1,9 @@
|
||||
Overview: What is the Hardware Portfolio?
|
||||
|
||||
The Hardware Portfolio defines the catalog of physical control, acquisition, motion, detector, and timing hardware platforms supported by the PSI Controls Section across our research facilities.
|
||||
|
||||
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?"
|
||||
|
||||
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.
|
||||
@@ -1,4 +1,4 @@
|
||||
# Projects and Initiatives
|
||||
|
||||
A list of projects and initiatives that Controls is working on.
|
||||
Multi-month/multi-year engineering roadmaps, facility upgrade campaigns, and architectural modernization projects.
|
||||
The detailed subtasks might be found in JIRA.
|
||||
@@ -1,3 +1,3 @@
|
||||
# List of Tools
|
||||
|
||||
List of software tools that Controsl develops and maintains.
|
||||
Software frameworks, graphical operator interfaces, data viewers, deployment utilities, and PSI-born EPICS modules.
|
||||
Reference in new issue
Block a user