Overview of Environmental Data Platform - Data Setup Guidance

See Understanding the Environmental Data Platform for a broader overview on the EDP

Mapistry's Environmental Data Platform (EDP) allows users to track data logging requirements, perform calculations and aggregations on the data, and download data as .xlsx files. This guide will walk you through the different log setup components and how to set up a log in the EDP

Environmental Data Platform - Data Setup (Settings)

Note: Organizational Admins are the only users who have the ability to create, edit, and manage logs. Site admins and site contributors have the ability to submit and manage submitted data.

Select 'Data Setup' in the navigation bar on the left of your screen. You will see 3 different tabs:

• Logs - Create the fields (columns) for the data you need to track over time
• Resources - Resources Types are categories that can be created within the Environmental Data Platform, making it possible to keep track of all your Resources within a Log. Generators are an example of a Resource Type, with generator-1, generator-2, and generator-3 all being Resources. See guide on Resources
• Workflows - join data sources together, perform aggregations, create formulas
• Once a log is added to a site, site-specific settings like frequencies and "Reports" can be set within the site-log page

EDP Logs - Typical Order of Operations

The following chart and flow description is intended to help users follow the best order of operations, depending on their data logging needs:

1. Do you need to the same type of information for multiple items (materials, equipment, products)?

   Especially when each of the items has its own respective properties (emission factors, categories, manufacturer) you may want to reference later

   Examples: Recording “usage” for each paint; Recording “runtime” for each generator; Recording “throughput” for each piece of equipment

   1. If Yes - Create a Resource for that group of items. Resources represent the library of items that information will be logged for (ex: Paints, Generators). Create Resource fields (columns) for the necessary properties (ex: emission factors, manufacturer)
      
      1. Determine whether the Resource should be site-associated
         1. Examples of Site-associated resources: physical generators; site specific lists of paints; discharge locations
            
         2. Examples of non-site-associated resources: global library of paints, materials, or parameters
            
      2. Add / Upload Resources to populate the list/ library
         
      3. When a Resource field type is used in a log, uploaded Resources appear like a single select drop-down list with the Names to choose from when entering log data (ex: which Paint used). When site-associated resource is used, the specific site will only be able to pick from resources associated to that site
         
   2. If No, move on to step 2
2. Create a Log
   1. If your log uses a Resource, add a “Resource” field to the log that references the Resource Type you created
      
      1. When a Resource field type is used in a log, uploaded Resources appear like a single select drop-down list with the Names to choose from when entering log data (ex: which Paint)  
         
   2. Add remaining Log field(s) (ex: Amount Used  - Numeric Field - gallons)
      
      1. Log Date/Time will always be a required field (already defaulted in by Mapistry). The Date entered to this field represents the date the data represents (ex: the month the paint was used)
         
      2. The Log fields are the format of the data collection/log
         
      3. Each log field becomes a “column” in the log in Mapistry
         
      4. Use numeric fields & assign “units” when applicable to use in Formulas/calculations. Mapistry formulas have unit-awareness built in
         
   3. Turn on the Log for each applicable site
      1. In the “Sites” page of the Log setup, create a frequency requirement for each site that will use the log
         
      2. In the “Data Setup” - Log page - “Publish” the log
         
      3. Sites can now add raw log data
         
3. Create a Workflow - Connects data together & provides the base dataset to build formulas/ calcs, and aggregations on top of - using log fields, linked resource fields, and/or existing formulas. Workflows can be used to create many different datasets to satisfy various use cases. The basic workflow setup is outlined below. If you have questions on using more complicated workflow setup, please contact Mapistry 
   
   1. Start with the Log as the first “Data Source”
      
   2. If your log uses a Resource, connect the Resource via a “Connect” step
      
   3. Create formulas and/or aggregations in the workflow to create required calculations
      
4. Create Reports for each Site-within each site's log page (NOT in the "Data Setup" page). Reports can set site-specific permit aggregation requirements or rolling totals; setting permit limits for alerts
   
   1. On the site’s Log page - Create a Report with the Workflow as the datasource
   2. Use query steps to build necessary aggregations, rolling calculations, and set limits
      
      1. Typical order of operations within a Report is (0) filters (if applicable); (1) aggregations (if not already performed in the workflow); (2) rolling calculations; (3) limit steps
   3. When a Report is saved, you can hide, change the order of, and/or rename columns as necessary