diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/01_ecmc.md b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/01_ecmc.md similarity index 100% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Motion/01_ecmc.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/01_ecmc.md diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/02_schneider.md b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/02_schneider.md similarity index 100% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Motion/02_schneider.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/02_schneider.md diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/03_acs.md b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/03_acs.md similarity index 100% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Motion/03_acs.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/03_acs.md diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/04_aerotech.md b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/04_aerotech.md similarity index 100% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Motion/04_aerotech.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/04_aerotech.md diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/05_deltatau.md b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/05_deltatau.md similarity index 100% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Motion/05_deltatau.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/05_deltatau.md diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/index.md b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/index.md similarity index 82% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Motion/index.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/index.md index 4a01c22..20176f0 100644 --- a/docs/2._Services_Portfolio/Hardware_Portfolio/Motion/index.md +++ b/docs/2._Services_Portfolio/Hardware_Portfolio/01_motion/index.md @@ -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. diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/Detectors/index.md b/docs/2._Services_Portfolio/Hardware_Portfolio/02_detectors/index.md similarity index 85% rename from docs/2._Services_Portfolio/Hardware_Portfolio/Detectors/index.md rename to docs/2._Services_Portfolio/Hardware_Portfolio/02_detectors/index.md index f11479f..f9b49d3 100644 --- a/docs/2._Services_Portfolio/Hardware_Portfolio/Detectors/index.md +++ b/docs/2._Services_Portfolio/Hardware_Portfolio/02_detectors/index.md @@ -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. diff --git a/docs/2._Services_Portfolio/Hardware_Portfolio/index.md b/docs/2._Services_Portfolio/Hardware_Portfolio/index.md index e69de29..e372432 100644 --- a/docs/2._Services_Portfolio/Hardware_Portfolio/index.md +++ b/docs/2._Services_Portfolio/Hardware_Portfolio/index.md @@ -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. diff --git a/docs/2._Services_Portfolio/projects.md b/docs/2._Services_Portfolio/projects.md index 1a9fd18..e82b765 100644 --- a/docs/2._Services_Portfolio/projects.md +++ b/docs/2._Services_Portfolio/projects.md @@ -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. diff --git a/docs/2._Services_Portfolio/tools.md b/docs/2._Services_Portfolio/tools.md index dbddfe1..3eb9bc6 100644 --- a/docs/2._Services_Portfolio/tools.md +++ b/docs/2._Services_Portfolio/tools.md @@ -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.