Data Ingestion Guide
Last updated: November 20, 2026
Tell us which systems hold your data and how you'd like to connect each one.
Before we can bring your data into Texture, we need to know two things: which systems your data lives in, and how you'd like to connect them. Copy the questionnaire below into an email reply, fill in your answers, and send it to your implementation team. Your answers let us set up the right connection for each system from the start, so you only send each file once.
How to fill it in. Mark the options that apply (change ☐ to ☒) and type your answers after each question. Skip any section that doesn't apply. "Not sure" is a fine answer, and your implementation team will help you fill in the gaps on your kickoff call.
How you can connect
Every system uses one of three methods. You can mix them: for example, SFTP for meter and GIS files and a cloud-to-cloud connection for your device manufacturers.
Method | How it works | Best for |
|---|---|---|
SFTP | Texture generates SFTP credentials specific to your organization and sends them to you. Your IT team pushes files to your Texture SFTP location, and Texture picks them up automatically. | Almost everything: ongoing updates, meter data, GIS, topology and SCADA. It's the easiest to set up, because your IT team only needs to push files. |
File upload | You export a file from your system and upload it from inside Texture. Each export is a separate delivery. See Sending Files with File Exchange. | Small, one-off files when you don't need anything repeated. |
Cloud to cloud | Texture connects directly to the other system's API using credentials you authorize. No files to export. | Systems that offer an API, such as device manufacturers (OEMs). Your credentials or API keys are required. |
About you
Question | Your answer |
|---|---|
Organization | |
Your name and role | |
Email and phone | |
IT contact who will receive the SFTP credentials | |
Date completed |
1. MDM (and CIS)
Customer and account records, as opposed to meter identity or interval usage. For what to export at each level of detail, see How to Send Us Your MDM/CIS Data.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which system? | ☐ NISC ☐ Meridian ☐ Star Energy/Pyxis ☐ Other: ________ |
How much customer detail can you share? | ☐ Level 1: location only (coordinates and account number, no personal information) ☐ Level 2: location plus customer name ☐ Level 3: full detail linked to a specific meter ☐ Not sure |
How would you like to send this data? | ☐ SFTP (recommended) ☐ File upload ☐ Cloud to cloud ☐ Not sure |
One-time or ongoing? | ☐ One-time file ☐ Scheduled updates ☐ Both ☐ Not sure |
Can your account numbers be matched to meter IDs in your AMI data? | ☐ Yes ☐ No ☐ Not sure |
Anything else we should know? |
2. AMI (meter data)
Meter locations, meter details, and interval usage. For what to export, see How to Send Us Your AMI Data.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which system? | ☐ Aclara ☐ Itron ☐ Landis + Gyr ☐ Other: ________ |
Approximately how many meters? | |
Interval length | ☐ 5 min ☐ 15 min ☐ 30 min ☐ 60 min ☐ Mixed |
How far back should history go? | |
Do you already receive a file from your head-end? | ☐ Yes ☐ No ☐ Not sure |
How would you like to send this data? | ☐ SFTP (recommended) ☐ File upload ☐ Cloud to cloud ☐ Not sure |
One-time or ongoing? | ☐ One-time file ☐ Scheduled updates ☐ Both ☐ Not sure |
Anything else we should know? |
TIP If Itron already sends you a file, the fastest route is to duplicate it. Have your utility copy the same file it receives from Itron and push it to your Texture SFTP location. That avoids building an MDM integration or asking Itron to set up another tunnel, which Itron charges for. Texture can also be the originating point for the Itron file and help you pass it on to your other systems, such as your MDM, after Texture receives it. |
3. GIS and grid topology
The map of your grid and how its parts connect. For what to export, see How to Send Us Your GIS + Mapping Data. If you also need to share your service territory outline, see Exporting Boundary Shapes for Territory Mapping.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which GIS or mapping system? | ☐ Esri ☐ EDD/DEW ☐ OSI ☐ Other: ________ |
Which system holds how your grid connects? | ☐ Milsoft ☐ WindMil ☐ Other: ________ |
Which asset layers can you export? | ☐ Meters ☐ Transformers ☐ Lines ☐ Poles ☐ Switches ☐ Reclosers and fuses ☐ Substations ☐ Not sure |
Can you tell us which transformer each meter sits on? | ☐ Yes ☐ No ☐ Not sure |
Do you have feeder and substation relationships? | ☐ Yes ☐ No ☐ Not sure |
How would you like to send this data? | ☐ SFTP (recommended) ☐ File upload ☐ Cloud to cloud ☐ Not sure |
One-time or ongoing? | ☐ One-time file ☐ Scheduled updates ☐ Both ☐ Not sure |
Anything else we should know? |
4. SCADA
Operational data from your control system. Once it's connected, you can see it in SCADA one-line diagrams.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which system? | ☐ Survalent ☐ OSI ☐ Other: ________ |
How often does it update? | |
Can it deliver files to an SFTP location on that schedule? | ☐ Yes ☐ No ☐ Not sure |
How would you like to send this data? | ☐ SFTP (recommended) ☐ File upload ☐ Cloud to cloud ☐ Not sure |
One-time or ongoing? | ☐ One-time file ☐ Scheduled updates ☐ Both ☐ Not sure |
Anything else we should know? |
5. Sensors
Grid sensors that report voltage or other readings.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which system? | ☐ EdgeZero ☐ Other: ________ |
Approximately how many sensors? | |
How would you like to send this data? | ☐ SFTP (recommended) ☐ File upload ☐ Cloud to cloud ☐ Not sure |
One-time or ongoing? | ☐ One-time file ☐ Scheduled updates ☐ Both ☐ Not sure |
Anything else we should know? |
6. DERs (distributed energy resources)
Devices in your programs, such as thermostats, batteries, solar, and EV chargers. If your members will connect their own devices, see Creating a Connect Link. If you're setting up smart thermostats through Renew Home, see Getting Started with Renew Home via NRTC DERMS.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which device types? | ☐ Thermostat ☐ Battery ☐ Solar ☐ EV ☐ EV charger (EVSE) ☐ Other: ________ |
Which manufacturers (for example Tesla, Enphase, ecobee)? | |
Approximately how many devices? | |
Do you have manufacturer API credentials? | ☐ Yes ☐ No ☐ Not sure |
Do you have a list of device serial numbers to load in bulk? | ☐ Yes ☐ No ☐ Not sure |
Anything else we should know? |
7. Utility batteries
Utility-scale storage you operate or control.
Question | Your answer |
|---|---|
Do you have a system for this? | ☐ Yes ☐ No / not applicable ☐ Not sure |
Which provider? | ☐ KORE ☐ Fluence ☐ PowerSecure ☐ Tesla ☐ Other: ________ |
Approximately how many sites? | |
Anything else we should know? |
IT and security
Texture generates your SFTP credentials and sends them to you, so setup on your side is mostly a matter of having the right person receive them and push files.
Question | Your answer |
|---|---|
Who on your IT team will push files to Texture? | |
Can your systems send files to an SFTP location on a schedule? | ☐ Yes ☐ No, someone will push them by hand ☐ Not sure |
Do you have network or security requirements we should follow? | ☐ IP allow-list ☐ Credential rotation ☐ VPN tunnel ☐ None ☐ Not sure |
Who should have access to files that contain customer information? |
Send it back
Email your completed questionnaire to your implementation team, or bring it to your kickoff call. We'll confirm the best connection for each system, send your SFTP credentials, and share export instructions for the systems you named. If you'd rather not use email, you can also send it through your support portal.
What happens next
Your data arrives and is mapped. Your implementation team loads and maps what you send and keeps you updated through your kickoff and follow-up calls.
You explore it in Texture. See Finding and adjusting Explore map layers and Viewing transformer loading.
You set up your programs. Start with the Utility & Co-op Program Implementation Guide, then use a design template: Thermostat, Battery, or EV charging.
Good to know
Your SFTP credentials are yours alone. Texture creates them for your organization, so your files stay separate from every other customer's.
Start small. A single file per system is enough to get going. You can move to scheduled deliveries later.
Connection options vary by system. Your implementation team will confirm the best route for each system you name, including whether a direct API integration exists.
Customer information is sensitive. Files with names, emails, or phone numbers should travel the same secure route as the rest of your onboarding data, with access limited to the people who need it.
Corrections are new deliveries. If a file needs fixing, send a corrected version instead of replacing the original.
Related articles
How to Send Us Your AMI Data — what to export for meter locations and interval usage.
How to Send Us Your MDM/CIS Data — customer and account information at three levels of detail.
How to Send Us Your GIS + Mapping Data — what to export so your grid maps correctly.
Sending Files with File Exchange — uploading files directly from Texture.
Getting Started with Renew Home via NRTC DERMS — matching your territory for Energy Shift Capacity.
Onboarding member utilities under a G&T or muni — if you're onboarding member utilities.
Start here: your first weeks with Texture — what to expect during onboarding.