The easiest way is to just set up an expression analysis reading the result from the table lookup attribute and set the output to a PI Point attribute.
There could be another way of sending data from a Lookup table to the PI Data Archive.
Generally, PI RDBMS Interface to pull data from a relational database (Oracle, SQL) and write to PI tags.
The method would be to use the RDBMS interface to query the PI OLEDB Enterprise server. To do so, you’d need to follow these steps:
- Create a linked server in SSMS and link the PI OLEDB Enterprise server. KB01143 - How to configure a linked server with PI OLEDB or PI OLEDB Enterprise
- Create a single query tag. OSIsoft: Read RDBMS/SQL data with a Single Tag query [PI RDBMS] - YouTube
This seems really roundabout, you are exposing PI data to read by PI to be sent back to PI. I know some customers use OLEDB to expose data from event frames but I don't think there is a need for any of this overhead in this case. If you take an analytics approach and depending on your versions of things please be aware of this KB.
If the values are timestamped in the table you can just configure a analysis (have to be periodic triggered) to write the values to PI.
This can be achieved even if the source data isn't timestamped but then you can't backfill the changes in time (if the limits change you can't back-trace it by re-calculating)
I haven't tested it but with the new AF server you can use a Analysis formula to set the output time, so if you tie in the time stamp for the change in limit you should be able to output the change to the correct timestamp as well.