This week we released updates across Explore, program event reporting, utility-scale grid asset support, and data ingestion, with something in here for programs teams, operators, and grid engineers alike.
As ever, you can follow along in real time at Release Notes | Texture Docs.
Explore: Saved views and grid hierarchy
Save your Explore configurations and come back to them
Explore the grid from map view now supports saved views. You can save any filter or view configuration and reapply it from a Views dropdown at the top-left of the Explore header: list, apply, save, update, rename, duplicate, delete. This ensures that when you build a useful filter set, navigate away, you have a path back to it.
Navigate the grid hierarchy directly from any element
Grid operators can now step up through a contextual Grid Hierarchy ladder directly from any grid element in the Explore panel. From a meter, you can walk up to its transformer, feeder, substation, and beyond, clicking any rung that navigates the map.
This is a grid and utility operator feature available to SCADA/grid customers. → Reach out to your implementation team to activate SCADA data.
Program event: clearer DR reporting and accurate energy attribution
Event reporting got a meaningful refresh this week with three improvements that make post-event analysis more trustworthy.
- Chronological event actions: Event actions now sort chronologically on the detail view, so the sequence of what happened during a DR event reads in the right order.
- Device participation filtered to command-eligible types: Participation is now scoped to batteries and other command-eligible device types. Historical batches that included ineligible device types are flagged with an "Ineligible - wrong device type" badge for easier cleanup.
- Clearer energy KPIs: The "Energy Delivered" label was relabeled to "Net Grid Energy," and a new "Battery Discharge Energy" tile was added.
Separately, Event Details and Reports views are now unified with a "View report" deep-link, and the "Pending" event badge has been renamed to "Scheduled."
Utility-scale battery support via R-TAC and DNP3
Texture now supports utility-scale batteries through R-TAC and DNP3 integrations. This extends Texture's reach to front-of-the-meter assets and grid DERMS workflows, ingesting 300+ data points per device. These are the large-format batteries that sit on the grid side of the meter, operated at utility scale.
OpenADR 2.0b support
Texture now supports the OpenADR 2.0b standard. For programs and utilities running demand response over OpenADR, this means Texture can participate as a VEN (Virtual End Node) in your existing ADR infrastructure.
Flexible data ingestion: SFTP, S3, SMB
Grid operators and utilities don't all share data the same way, and Texture meets you where you are. We'll ingest SCADA and grid topology data however your systems share it, on whatever cadence makes sense for your operations: every 5 minutes, hourly, daily, or weekly. Polling, streaming, real-time, and snapshot are all supported.
Specifically:
- SFTP: File-based ingestion with handler validation, for teams sharing data via secure file transfer.
- SMB (Windows file share): Grid topology data delivered over SMB is now supported, a common pattern for utility grid teams running Windows-native infrastructure.
- S3: SCADA data ingested directly from S3 buckets.
If you're currently sharing data via one of these paths (or want to), reach out to your implementation team to get it flowing.
If you have questions about a specific integration or want to connect an asset type not yet on the platform, reach out to the Texture Implementation Team or contact us here. You now have promotional access to new style and formatting tools with Gemini in Docs.Explore with higher limits until July 15. Learn more
