Western Oregon Service Unit Laboratory Interface Software Upgrade

Page 1 of 8 Data Innovations Instrument Manager (IM) Software Standard Upgrade and IM Core Training Western Oregon Service Unit (WOSU) Portland Area Indian Health Service April 2026 -- 1 of 8 -- Page 2 of 8 1. Purpose and Objectives 1.1 Purpose The purpose of this requirement is to obtain contractor services to upgrade the existing laboratory instrument middleware, Data Innovations Instrument Manager (IM), to a current supported version and to ensure continued operability in the Government’s target computing environment, including support for transition away from end-of-support Windows 10 host platforms. 1.2 Objectives The contractor shall: • Plan and execute a standard upgrade of the Government’s existing Data Innovations Instrument Manager (IM) environment (including applicable test/non-production and production instances used to support laboratory instrument interfaces). • The Government will provide the target hosting environment (VDI and/or server-based) that meets vendor minimum requirements. • The contractor shall validate compatibility of the target environment with the supported IM version and document any platform constraints or risks prior to production upgrade. • Provide implementation documentation, cutover/rollback planning, and post-upgrade knowledge transfer. • Deliver Instrument Manager (IM) Core Training to designated Government staff. 2. Background WOSU uses laboratory instrument interface middleware to support the quality delivery of patient laboratory results and to reduce manual result entry errors that may impact patient care outcomes. The current Instrument Manager environment requires an upgrade to remain supported and to enable modernization of the hosting environment. This requirement supports sustainment and standard upgrade of an existing CPIC-governed laboratory middleware system and does not introduce new system functionality or expand system scope. 3. Scope of Work The scope of work includes contractor labor and expertise to: • Perform a standard upgrade implementation for Data Innovations Instrument Manager (IM), inclusive of planning, installation, configuration migration as applicable, testing support, production deployment/cutover support, and limited post-deployment support. • Provide IM Core Training to Government personnel. -- 2 of 8 -- Page 3 of 8 4. Period of Performance 4.1 Period The period of performance (PoP) shall be up to 15 months, starting from the date of award. The extended period of performance is intended to accommodate Government scheduling, hosting readiness, and operational constraints; active upgrade execution is expected to occur within a shorter window. 5. Place of Performance Work may be performed remotely and/or on-site as required and approved by the Contracting Officer’s Representative (COR). Primary Government site: Western Oregon Service Unit, 3750 Chemawa Rd NE, Salem, OR 97305. 6. General Requirements 6.1 Non-personal Services The contractor shall provide non-personal services. Contractor personnel shall not supervise Government personnel and shall not represent themselves as Government employees. 6.2 Project Management The contractor shall provide project management sufficient to plan, execute, and control the upgrade effort. At a minimum, the contractor shall: • Identify a primary point of contact. • Conduct a kickoff meeting within 15 business days of award (or as mutually agreed). • Maintain an agreed project schedule, action item log, and risk/issue tracking. • Conduct periodic status meetings (e.g., weekly) during active phases. 6.3 Coordination and Change Control The contractor shall: • Coordinate with Government IT stakeholders for connectivity, accounts, access approvals, and maintenance windows. • Document proposed changes that affect scope, schedule, risk, or downtime. Any changes beyond scope require COR approval and, if applicable, contract modification. • Not implement production changes without documented Government approval of the change and approved scheduling. -- 3 of 8 -- Page 4 of 8 7. Performance Requirements and Tasks 7.1 Task 1 - Discovery and Current-State Assessment The contractor shall: • Review the current IM environment, including version/build, licensing status as applicable, server/desktop topology, and interface inventory. • Identify prerequisites and dependencies for operating IM in the Government’s target environment (including virtual desktop/virtual server environments as applicable). 7.2 Task 2 - Upgrade/Migration Planning (including Cutover and Rollback) The contractor shall develop an Upgrade Implementation Plan that includes: • Planned upgrade path and version target. • Required Government actions (e.g., server/VDI provisioning, firewall rules, accounts, certificates if applicable). • Testing strategy, success criteria, and go/no-go criteria. • Cutover plan including planned downtime window(s). • Rollback plan to restore prior operations if go-live criteria are not met. Performance standard: Plan is complete, actionable, and minimizes operational risk. Acceptance: COR approval of Deliverable D-2 prior to production changes. 7.3 Task 3 - Test/Non-production Upgrade and Configuration Migration The contractor shall: • Install and configure the upgraded IM software in a test/non-production environment (if available/required by the Government). • Migrate or recreate configuration elements necessary to validate functionality consistent with current operations (e.g., instrument connections, routing, interface definitions, rules, drivers/config sets, as applicable). • Support Government staff during test execution and document results. Performance standard: Test environment upgraded successfully; test results demonstrate readiness for production. Acceptance: COR acceptance of Deliverable D-3. 7.4 Task 4 - Production Upgrade and Go-Live Support The contractor shall: • Perform the production upgrade during an approved maintenance window. • Execute the cutover pl…