> For the complete documentation index, see [llms.txt](https://atd-dts.gitbook.io/atd-knack-operations/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://atd-dts.gitbook.io/atd-knack-operations/data-tracker/performance-measures.md).

# Performance Measures

How to manage performance measures

<http://transportation.austintexas.io/data-tracker/#home/performance-measures/>

## Object Tables defined

Performance measures are tracked in these objects:

* `performance_measures`

Contains core information about the performance measure, such as the ID, name, and division.

* `performance_measures_fiscal`

Contains information about the performance measure for the given fiscal year. This is the object that needs to be updated on an annual basis, and it contains formulas that roll up the **monthly/quarterly/fiscal** reporting. Performance measures reporting frequency (monthly/quarterly/annually) can change from year to year, so that information is also captured here. Relationship: Many performance\_measures\_fiscal relate to one performance\_measure.

* `performance_measures_monthly`

User-submitted entries which provide the actual reported values for each performance measure. Many performance\_measures\_monthly relates to one performance\_measures\_fiscal.

* `performance_measures_quarterly`

User-submitted entries which provide the actual reported values for each performance measure. Many performance\_measures\_monthly relates to one performance\_measures\_fiscal.

* `performance_measures_annually`

User-submitted entries which provide the actual reported values for each performance measure. Many performance\_measures\_monthly relates to one performance\_measures\_fiscal.

## Annual Updates

The `performance_measures_fiscal` must be created on an annual basis so that end-users can append monthly/quarterly/annual reports to them. This is accomplished via batch import to Knack.

By following these steps you will import the performance measure data to meet the current fiscal year needs.

| Activity Code | Frequency | Measure ID | Measure Name                                                                   | Measure Goal | Measure Division                   | Measure Type | If the measure is new? | Fiscal Year |
| ------------- | --------- | ---------- | ------------------------------------------------------------------------------ | ------------ | ---------------------------------- | ------------ | ---------------------- | ----------- |
| 32TP          | Annually  | 9195       | Percent of affordable housing available within 1/2 mile of transit and bicycle | 91           | Transportation Systems Development | Average      | New                    | 2021        |

* Ask Finance to send the performance measures for the current fiscal year in the format specified above. Check if these fields are needed -&#x20;

  `REPORT_STATUS`, `PROPOSED`, and `AMENDED`.
* Also ask Finance if any new division names need to be added, or if current measures have been moved to different divisions.

### Organizing Data

* Filter out the measures that are new and have been added to the current fiscal year.
* Add the new measures to the `performance_measures` object first.&#x20;
  * You can do this by **Adding a Record** if there are not too many.
* Add a column to the spreadsheet sent by Finance. Name this field `Import_ID.`
* Calculate the entries in the Import ID field by concatenating `Measure ID,"$,Fiscal Year`
* You might also need to update all the entries under **Fiscal Year** (Enter current year)
* Open the `performance_measures fiscal` object in the Records view

### Import Steps

* Click **Import**&#x20;
* Select or Drag & drop **csv file**
* **Define Headers** - *Does the first row of your data contain column headers?* **Yes**
* Click **Next**
* **Update Records** - *Do you want to update existing performance\_measures\_fiscal records with this import?* **No, insert each row as a new record**

{% hint style="warning" %}
Most importantly, the **MEASURE\_ID** field must map to the **MEASURE\_ID** on the related **\`**&#x70;erformance\_measures object\`
{% endhint %}

Map Columns:

* **Import ID -** Import ID
* **Fiscal Year** - Fiscal Year
* **Measure ID** - Measure ID>Measure ID
* **Frequency** - Frequency
* **Measure Name** - Measure ID>Measure Name
* **Measure Type** - Measure ID>Measure>Measure Type
* Click `Next` button
* For default fields, select **Created By** (your name), **Created Date** (today's date). (This will help keep track of which records get added).
* Let the process run.&#x20;

### At the End

* Do some QA/QC to make sure the right number of records got added, that there are no duplicates.
* Update the view "Performance Measures" which displays performance measures to the end-user.&#x20;
  * Located at [`https://builder.knack.com/atd/amd/pages/scene_565/views/view_1735/table`](https://builder.knack.com/atd/amd/pages/scene_565/views/view_1735/table). &#x20;
* From the builder, navigate to the page views and modify the table **Source** filter to the current fiscal year. This ensures that end-users will only see/modify current fiscal year measures.
  * Update the Fiscal Year filters for the three eCombs reports.&#x20;
    * Here is the link to the scene - [`https://builder.knack.com/atd/amd/pages/scene_833`](https://builder.knack.com/atd/amd/pages/scene_833)

You're done!
