1.
Create trend displaysQuery historical dataPrerequisites
- Tags configured in UNS
- Understanding of data retention needs
- Navigate to Historian → Storage
- Configure database:
Default SQLite (Development):
- Type: SQLite
- Path: Default or custom
- File Size: 1GB per file
- Auto-create: Yes
SQL Server (Production):
- Type: SQL Server
- Server:
SQLServer\Instance
- Database:
FrameworX_History
- Authentication: Windows/SQL
Step 2: Create Historian Tables
- Go to Historian → Historian Tables
- Create tabletables:
Process Data:
- Name:
ProcessData
Type - Save On Change: Continuous

- Storage: 1 second resolution
- Retention: 90 days
- Compression: DeadbandAuto Create:

Production Counters:
- Name:
Production
Type - Save On Change: Counter

- StorageAuto Create: On change
- Retention: 365 days
Step 3:
- Navigate to Historian → Historian Tags
- Add tags to log:
Analog ValueProcess Data:
- Tag:
TankFarm/Tank1_/Temperature
- Table:
ProcessData
- Deadband: 0.5
- RateRateOfChange: 10 seconds
Digital ValueProduction Data:
- Tag:
Motor1_Running
- Table:
ProcessData
- Log: On change only
Production Count:
- Tag:
Units_Produced
- Table:
Production
- Type: Counter/Totalizer
Step 4: Create Trend Display
- Open Displays → New
- Add TrendChart control
- Configure:
Basic Setup:
- Duration: 1 hour
- Update: 1 second
- X-Axis: Time
- Y-Axis: Auto-scale
Add Pens:
- Pen 1:
Tank1_Temperature
(Blue) - Pen 2:
Tank1_Pressure
(Red) - Pen 3:
Motor1_Running
(Green, digital)
Time Navigation:
- Enable pan and zoom
- Add time selector
- Quick ranges: 1hr, 8hr, 24hr, 7 days
Analysis Tools:
- Cursors for value reading
- Min/Max/Average display
- Export to CSV
Step 6: Query Historical Data
Using SQL queries:
sql
SELECT Timestamp, TagName, Value
FROM ProcessData
WHERE TagName = 'Tank1_Temperature'
AND Timestamp > DATEADD(day, -7, GETDATE())
ORDER BY Timestamp
Using Scripts:
csharp
DataTable history = @Historian.GetData(
"Tank1_Temperature",
DateTime.Now.AddDays(-7),
DateTime.Now,
1000 // Max points
);
Step 7: Create Reports
- Reports → New
- Add data source:
- Type: Historian Query
- Tags: Select multiple
- Period: Shift/Day/Month
- Aggregation: Average, Min, Max
Step 8: Storage Management
Configure data management:
Compression:
- Deadband: ±0.5% of range
- Time deadband: 60 seconds
- Compression deviation: 1%
Archiving:
- Archive after: 30 days
- Archive location: Network path
- Compression: ZIP
Purging:
- Auto-purge: After retention period
- Manual purge: By date range
Step 9: -
Production/Production_Count
- Table:
Production
3. Test Historian
- Start Runtime
- Let run for few minutes
- Open trend display
- Verify:
- Data logging active
- Trends updating
- Historical data visible
- Zoom/pan working
- (change tags values manually using PropertyWatch)
- Go to Historian → Historian Monitor
- Add both tags to the trend and see the values based on the time
- Log only necessary tagsUse appropriate deadbands
- Consider table partitioningRegular index maintenancemultiple historian table with distinct triggers
- Monitor disk space
Best Practices
- Plan retention requirements
- Use multiple tables for different data types
- Set appropriate logging rates
- Regular backups
- Document data retention policy
Next Steps
[Create Dashboards] - Historical KPIs[Reports Module] - Automated reports[Datasets Module] - SQL analysis Excerpt Include |
---|
| Historian Module |
---|
| Historian Module |
---|
nopanel | true |
---|
|