PEEK (polyetheretherketone) installation work splits cleanly into three non-overlapping domains: the physical fitting of machined PEEK components into mechanical assemblies, the deployment of software platforms branded "Peek" (SynertyPeek 5.1.12), and the installation of network-monitoring tools named PeekPlus and Omnipeek. Mixing the three causes spec errors, since the assembly rules that govern a PEEK bearing or seal have nothing in common with an MSI installer or a SAVF upload to IBM i.
These anchor every torque, shrink-fit, and creep calculation on the shop floor.
Shrink-Fit and Interference Assembly for Machined PEEK Components
Interference fits on PEEK bushings, seal housings, and linear guide carriers rely on thermal expansion rather than press force, because the polymer's modulus (≈3.6 GPa unreinforced, ≈10 GPa for 30% glass-filled) is too low to sustain heavy press loads without creep relaxation. The standard practice is to heat the PEEK part in air or oil to 150-180°C, mate it to a room-temperature shaft or housing, and let the differential contraction set the interference. [S2]
Hold-down torque on PEEK threaded fasteners is the second most common failure point. Unfilled PEEK threads strip above roughly 0.3-0.5× the equivalent steel torque, and the practical shop rule is to torque a M6 PEEK cap screw to 1.5-2.5 N·m, never above 3 N·m, with a PTFE or molybdenum-disulfide dry-film lubricant on the threads. Over-torque is the root cause of stripped PEEK inserts in chemical pump housings, and the only correct repair is replacement, not thread-restoring epoxy, which fails under the same thermal cycles that drove the failure.
Surface Finish, Flatness, and Bearing Surface Prep Before Installation
Mating surface finish on PEEK hardware is rated in Ra µm, and the polymer's tendency to bed-in means rougher counterfaces accelerate wear during the first 50-100 operating hours. For dynamic sealing faces, specify the steel or ceramic counterface at Ra 0.2-0.4 µm; for static O-ring or gasket grooves, Ra 0.8 µm is acceptable. Flatness on PEEK gasket faces should hold within 0.05 mm per 100 mm of span, otherwise bolt preload will not seat evenly and the joint relaxes within the first thermal cycle. [S1]
Cleaning before installation is non-negotiable in semiconductor and pharmaceutical service, where PEEK is widely used for fluid handling. Wipe all sealing surfaces with isopropyl alcohol (≥99%) and a clean-room wipe, allow full flash-off, and never use shop solvents that leave silicone or hydrocarbon films. The same rule applies to PEEK wear strips in crossed roller guide carriages, where a contaminated sliding surface can score the roller race within hours of commissioning.
SynertyPeek 5.1.12 Software Platform: OS and Dependency Stack
The SynertyPeek platform documentation (readthedocs.io) lists three supported host operating systems as of the 5.1.12 release: Windows, macOS, and RHEL 7. The Windows installation path requires MS .NET Framework 3.5 SP1, Visual C++ Build Tools 2015, Msys Git, PostgreSQL, Python 3.6, and optional Oracle Client and FreeTDS libraries, in that order. RHEL 7 starts from Red Hat Linux Server 7.7 OS, removes the IPv6 localhost entry, installs general prerequisites, optionally installs VMware Tools, and finishes with a source compile of Python 3.9.1 plus PostgreSQL [S1].
The macOS path differs: it sets the terminal shell to Bash, opens "safe files" in Safari, creates the Peek OS user, installs Xcode, then Homebrew, prepares .bash_profile, and installs Python 3.9.1 plus PostgreSQL through Homebrew, with an optional Oracle Client and a separate change to the open file limit on macOS [S1]. Note that Python 3.6 is pinned for Windows while Python 3.9.1 is required on macOS and RHEL 7, so a single image of the runtime does not transfer between host operating systems. The SynertyPeek docs do not advertise support for RHEL 8, RHEL 9, or any Ubuntu LTS, and any deployment onto those platforms is an unsupported fork, not a vendor-validated install.
PeekPlus 3.5 and Omnipeek 22.2: IBM i and Windows Network Tooling
PeekPlus 3.5 by Fortra targets IBM i (iSeries) hosts and the install procedure is anchored on the IBM i side rather than the Windows desktop [S2]. Pre-requisites are V5R3 or higher OS, compatibility with i5/OS V5R3/V5R4 and IBM i 6.1/7.1/7.2, *ALLOBJ authority on the IBM i sign-on, the latest Cumulative PTF, HIPER Group PTF, and Database Group PTF for the OS release, plus a valid license key. The procedure downloads PeekPlus 3.5 into C:\TEMP on a Windows PC, unzips it, opens a DOS FTP session, creates save file QGPL/PP350, binary-uploads the file, signs on to the IBM i with *ALLOBJ, runs RSTOBJ OBJ(*ALL) SAVLIB(QTEMP) DEV(*SAVF) SAVF(QGPL/PP350) followed by QTEMP/PPINSTALL, and reaches the main menu by typing PEEKPLUS/PEEK on the IBM i command line [S2].
Omnipeek 22.2 from LiveAction is a Windows installer that runs an MSI package (Omnipeek_xx.x.x.msi) and the installer removes any previous version during the same transaction [S4]. The product-key step offers two paths: Automatic, which uses the Internet to retrieve a license file, and Manual, which walks the user through a web activation page and license-file import. Once installed, the user can launch Omnipeek directly from the final installer screen or open the Readme first [S4]. The published note is that the LiveAction documentation site is being retired in favour of the BlueCat Documentation Portal, so the 22.2 User Guide PDF download remains the most stable reference for the install steps through the platform transition.
Failure Modes, Acceptance Criteria, and When to Replace Instead of Repair
Three failure modes dominate PEEK hardware commissioning and each has a defined acceptance test. Stripped PEEK threads: replace the insert, do not re-tap to a larger size, because the surrounding bore wall is already damaged. Creep-relaxed interference fit: reheat to 150-180°C and re-mate; if the bore has ovalised beyond 0.1 mm on a 50 mm nominal, scrap the part. Leaking PEEK gasket face: check flatness with a surface plate and feeler stock; if the gap exceeds 0.05 mm per 100 mm, reface the part or replace, because re-torquing will not recover sealing. For SynertyPeek deployments, the acceptance test is the post-install service health check across Peek Logic Service, Storage Service, Field Service, Field App, Office Service, Office App, Worker Service, Agent Service, and Admin App; if any one of the nine does not report healthy, roll back the deploy rather than ship a partial stack [S1].
For PeekPlus 3.5, the acceptance command is PEEKPLUS/PEEK on the IBM i command line returning the main menu without error, and any install error during the RSTOBJ step is a hard stop that requires re-uploading the SAVF from the Windows host [S2]. The Fortra manual is explicit that license keys are required before install, so a missing key should fail the pre-flight check, not surface as a mid-install rollback. Across the three toolchains, the common lesson is that PEEK hardware, SynertyPeek software, and PeekPlus / Omnipeek monitoring all demand a pre-install checklist before any user clicks "next" or applies heat to a part.
Trackable signals through 2026-Q4: the SynertyPeek readthedocs.io changelog for any 5.1.13 release, Fortra's PeekPlus product page for an IBM i 7.5 compatibility update, and the BlueCat Documentation Portal for an Omnipeek 22.3 or 23.x user guide that supersedes the 22.2 PDF. On the PEEK hardware side, the next node to watch is ASTM D792 updates for filled-grade density ranges and any revision to UL 746B continuous-service temperature listings for 30% carbon-fibre PEEK.
For related coverage, see Carton Box Selection for Automotive Parts Logistics: Spec-First Guide.