Please ensure Javascript is enabled for purposes of website accessibility
Powered by Zoomin Software. For more details please contactZoomin

OMF with PI Web API

Recommended specifications

  • Last UpdatedSep 04, 2025
  • 1 minute read

The performance of OMF is affected by the software and hardware used in your installation. Use the following recommendations as the minimum guidelines to achieve optimal performance. Performance may vary depending on setup and other factors. For more information, see Performance optimization.

  • Windows Server 2016 or later

  • Separate machines for PI Web API and PI Asset Framework/Data Archive

  • PI Web API installed on a server with:

    • 16GB RAM

    • 100GB HDD

    • 8 cores

    • (optional) PI Buffer Subsystem to buffer events before going to Data Archive

      Note: We recommend that you use PI Buffer Subsystem in conjunction with OMF.

  • PI Server 2018 SP3 or later (PI AF/Data Archive) on a server with:

    • 8GB RAM

    • 100GB HDD

    • 4 cores

Optional specifications

OMF can be used with a PI collective.

Note: Initial data values may not be written to secondary Data Archives in a collective immediately after PI point creation. Secondary Data Archives will discard data that is received for a PI point before the PI point creation is replicated from the primary collective member. For this reason, we recommend that you implement a small delay between creating PI points in a PI collective and writing data to those PI points. If the collective is in good health, a delay of 5 - 10 seconds should be sufficient. For information on determining the health of a collective, see Check collective health.

TitleResults for “How to create a CRG?”Also Available in