OPH status meeting with Garth

Date: 2026 01-January 29

Garth build a chat bot to know the ovation docs

It looks like 161 is running and 160 is not

Generate a history trend from January, 1 2025 to January, 1 2026

Drop 160: 192.168.2.160
Drop 161, iDrac: 169.254.0.2

• Call Ovation, get Garth on the

• We need a roll back plan, to get us back to where we are

• Garth will work on an RCA template

  • What steps are taken to resolve issue
  • What steps are being taken to prevent it from happening again
  • There should be alerts or alarms associated with the OPH dropping offline

• Are any active alarms associated with the OPH

• Notification / Alert / Alarm resolution / analysis / dilution

• How will we stabilize documentation, such as the RCA plan

  • SASS tools for stability.
  • Atlassian spaces
  • It must be driven by leadership

The ball is rolling with SharePoint

Define a clear folder structure.

Have people with authority.

A folder structure that is based on process.

Take advantage of a SASS solution.
We need a governance team, to develop and steer the standards.
We are a Microsoft shoft
Power Platform.
Power Apps is baked in and IT will be much happier with it.
Have a Power App that deploys a folder structure to SharePoint for me. And it should easier than SPFx.

When including other people - use the low code for stability.

Henry has an expectation that WIMS will be the equivalent of a Historian. The Hach WIMS has no expectation of that. WIMS is not a regulatory reporting tool, but it can be used that way.

My scripts will have access to the Hach WIMS SQL server.