We have an area at Ben White for DTS Staff. Ask your supervisor before attempting to work from that location.

DTS Hoteling

• Ben White

• Permitting and Development Center (Public Spaces)

Our Wikis

• DTS Dev

• DTS Knack Operations

• DTS Geospatial

We also have end-user documentation for , Signs & Markings Tracker, the SXSW Command Center, and

Transportation Public Works

TPW Sharepoint - Intranet

TPW Divisions and Offices - Overview of each division's purpose and operations

TPW Org Charts

TPW Branding - style guides, fonts and document templates

Videos

Inside Austin Transportation and Public Works

Walk Bike Roll

Public Websites

• Austin Transportation and Public Works - public-facing department site

• Austin Strategic Mobility Plan - Transportation and Public Works' infrastructure roadmap

Department Newsletters

• Austin Mobility News - Weekly newsletter covering projects and programs related to Austin Transportation and Public Works.

• Get There ATX Newsletter - Monthly newsletter featuring mobility-focused events and ways to convert your car-based commute and other trips to other transportation modes.

• Urban Trail Mix - Quarterly newsletter providing project updates on Austin's urban trails program.

City of Austin

• Org chart

• Open Data Portal

• Open Data Community - Bloomfire

• - Bloomfire

Employee Resources

• CTM Service Request or 512-974-4357 (4-HELP from a City phone) - CoA enterprise IT, see Sharepoint for details on what tech they support

• Official City of Austin holiday schedule

• City Intranet - job postings, policies and procedures, news

• - pay, benefits, training, jobs

• (external site)

• - City of Austin rules regarding employee hiring, promotions, lateral transfers, reduction-in-force, disciplinary actions, and appeals

Staff Training

• City of Austin LinkedIn Learning - free classes available through single-sign-on

• Document templates

• ​DTS Google Drive​ - ​account setup​​

Windows-only File Types

GIS files, Visio documents, and other files that can only be used on a Windows operating system are stored on the ATD departmental network G drive.

Everything Else

Other documents can be stored in Google Drive or our G drive, whichever is most practical for the team and customer.

How to Connect to Network Drives on a Mac

You will need to be either hard-connected to the City network or connected via VPN. From Finder on Mac: Go > Connect to Server then type the address in the Server Address field

• H drive: smb://coacd.org/home/PWDhome/[your username]

• G drive: smb://coacd.org/dfs/ATD

Hardware & Office

• Request necessary hardware from Scott. Do this as soon as possible to ensure he has enough lead time to acquire equipment. Make sure they get a laptop, power supply, monitors, keyboard, mouse, and docking station. Some team members also need a CoA phone.

• Coordinate with Diana to assign their desk and obtain an ergonomic chair.

Network Account & Distribution Lists

If the employee is using city-issued equipment, submit a New Employee Request Form. Otherwise, use submit a Third-Party Remote Access Request Form.

New Employee Request Form

• Submit a New Employee Request Form to create a CoA network account, eAccess PIN/HR Portal, and phone. Under "Network Account Information," write Shared mailbox: transportation.data@austintexas.gov (needs Send-As permission); Distribution lists: ATDDataTechnologyServices@austintexas.gov and TPWEmployees@austintexas.gov.

Third-Party Remote Access Request Form

For a full (18 page) explanation of this process, refer to CTM's Third-Party Remote Access Request Quick Reference Guide. In short:

• Have the employee sign the City of Austin Third-Party Remote Access Connection Acceptable Use Agreement.

• Submit a Third-Party Remote Access Request Form on Service Now, including the acceptable use agreement with

Next Steps

After the network account is created and you have their @austintexas.gov email address:

• Ask Amenity or Diana to add the new team member to 1Password.

• Ask Amenity or Diana to add the new team member to City of Austin Slack.

• Ask Diana or Karo to add the new team member to DTS SharePoint.

• Add them to all relevant Slack channels and introduce the new team member to everyone in the main DTS channel.

• Schedule time to give them their computer and show them around the office.

• Add "Welcome (name)" to the .

• Schedule a one-hour DTS Team Orientation. It should include Peggy and all team leads.

• Ask Amenity to schedule DTS Product Ops training.

• Schedule Biweekly 1x1s.

• Forward biweekly Sprint calendar events.

• Invite new team member to relevant agile ceremonies — Planning, Backlog Refinement, Retro.

• Invite new team member to other regular meetings — DTS Team Meetings, Syncs, Show & Tell.

• Ask Diana or Karo to schedule Service Desk training.

After they've created their Google and Github accounts:

• Share the DTS Google Drive with the new team member.

• Ask Amenity or Frank to add the new team member to the City of Austin Transportation Github team. This should automatically add them to the City of Austin Github organization.

• Invite the new team member to the City of Austin Zenhub organization.

• Add the new team member to .

After they notify you that they've uploaded their headshot:

• Add them to the DTS Orientation presentation team slide and the slide for the team they are joining.

After they notify you that their Miro account was created:

• Add them to the Austin Transportation and Public Works Miro team.

Once HR has added regular/temp employees to the UKG timekeeping system, their supervisor—Peggy, Amenity, or Diana— must:

• Set up their schedule plan.

• If you don't have one already, create a Github account with your CoA email and then ask Amenity or Frank to add you to the City of Austin Transportation Github Team.

• Enable two-factor authentication for your Github account.

• Install Slack desktop client — Windows | Mac.

• .

• with a photo and your title.

• Post your .

• and verify that you have access to the .

Week 1 🐥

Let your supervisor know if you are unable to finish any of these during your first week.

• Set yourself up for remote work.

• Set up Cameron Road printer.

• Set up docking station — Windows | Mac. (See here if you're having issues on Mac. If you have an M1, grant screen recording permissions as detailed here.)

• Upload a headshot and notify your supervisor so they can add you to the DTS orientation deck.

• Install .

• to add yourself to the : - Title: Add [First name] [First initial of last name] to DTS website - Labels: Service: Dev, Type: Communications, Product: DTS Website - Assignee: Chia Berry - Include: - Link to your photo in Google Drive - Full preferred name - Title - Preferred pronouns

• Familiarize yourself with the and our .

Week 3 🐓

Unless you are a contractor, you have a few last to-dos! The HR and DTS Portals are updated every 2 weeks with employee information from the City's enterprise HR system, so wait until week 3 for these ones.

• Complete the Telework Request Form.

• Record any City hardware you have in the Take-Home Equipment Tracker.

Ask questions! Be a sponge and absorb it all! 🧽💦🌈

Bonus: Update this wiki if you find broken links or missing information! 😉

Per the City of Austin Anti-Virus Policy, all City-owned computers must have up-to-date virus protection installed and active.

The TrendMicro website has Mac installers and installation instructions here. You will need the serial number in CTM's Anti-Virus for Non-COA Computers doc.

Network Access with Cisco Secure Client VPN (formerly Anyconnect)

You need to be on the City of Austin's internal network to access resources such as shared network drives, the HR Portal, and enterprise web applications like eCombs and eCapris. You can use Cisco Secure Client (formerly AnyConnect) to connect to the City's Virtual Private Network (VPN) when working remotely.

Installing AnyConnect

1. Download the installer by visiting https://coa-vpngw.austintexas.gov/connectsso.

2. Double-click the downloaded file to open the disk image, then double-click on AnyConnect.pkg.

3. When the installer opens, click "Continue," "Agree," and leave the defaults on for the installation type:

4. When prompted, provide the password you use to log in to your computer, and the installation will begin. It will take a few minutes to run.

5. Once told the installation has been completed successfully, click "Move to Trash" to delete the installer.

6. You should now see a Cisco folder in your Applications folder. Double-click on the Cisco Secure Client to open the application.

Using Secure Client

1. Open the application. In the empty field below "Ready to Connect," enter the IP address of the City's VPN server.

2. Click the "Connect" button.

2. A warning will appear. Do not check the "Always trust..." option and click "Connect Anyway."

1. A new browser window/tab will open and you will be prompted to login to the City of Austin SSO portal. Once complete, the browser window will close and your VP

Uninstalling AnyConnect

When troubleshooting your VPN connection, you may want to wipe all installs of AnyConnect and start fresh. You can use Uninstall AnyConnect, located in the Cisco folder in Applications.

Shared Drive Access

You must access the G Drive from the City of Austin Network. If you don't have a wired connection, use AnyConnect.

1. From the Finder menu, select Go > Connect to Server.

2. Enter smb://coacd.org/dfs/ATD in the Server Address field and click "Connect."

3. You will be prompted for your City of Austin Network Username and Password. Once submitted, a Finder window will open to the G Drive.

Official City of Austin holiday schedule

All Austin Transportation Department employees are required to work 8.5 hours/day. That includes a mandatory 30-minute lunch. You can take a longer lunch but can’t count it as work time. You can work through lunch but still need to put in 8.5 hours.

Your start time can range between 8am and 9:30am. We ask that you work the same schedule consistently and post your daily stand-up when you log on.

When meetings get scheduled outside your regular work hours, you’re expected to attend them. Let your team lead know in advance when you cannot attend a meeting that requires your attendance.

Flexing Hours

You can occasionally flex your hours to accommodate doctor appointments, errands, etc.; give your team lead a heads-up in advance. We understand that unexpected absences can come up.

“Non-exempt,” aka "hourly" employees, can flex hours within a single work week (Sunday-Saturday), so long as you reach 40 total hours. "Exempt" employees can flex hours across the two-week pay period, so long as your hours total 80.

Leave Time

If you can’t or don’t want to flex, you can use sick time for doctor appointments and personal time (vacation, personal holiday hours, comp time, etc.) for anything else. You may also use leave without pay (LWP), but LWP requires pre-approval and should be discussed with your supervisor at least two weeks in advance.

Non-exempt employees can earn overtime and comp time, which require advance approval from your supervisor.

If you are a new regular employee, you, unfortunately, can’t use vacation or personal holiday leave during your six-month probation period. If you need to take time off during probation, you have three options: flex hours, use sick time, or take leave without pay.

Regardless of the leave you use, you must submit a leave request in advance through the eTimesheet system (see below).

Timesheets (Needs to be updated for UKG)

​E-Timesheet Training (On-Network)​

• Part 1: eTimekeeping​

• Part 2: Task Orders​

• Part 3: Leave Requests​

• Part 4: ​

• Part 5:

Your timesheet must be submitted in the eTimesheet system every Thursday by 10am.

Learn how to submit your timesheet with the E-Timesheet Training Guide (on-network) and timesheet code reference.

You need to be on the City of Austin internal network to access various resources such as shared network drives, the HR Portal, the original CitySpace, and many City of Austin Sharepoint sites.

• Cisco AnyConnect VPN is the client we use to remotely connect to the City network from a Mac.

  • Installer

  • Instructions for installing and configuring to work in OSX Catalina

• CTM Help Desk

Use of Personal Devices on the City Network

If you use your personal computer for work at the any CoA office be advised that you should never directly connect to the CoA Ethernet network. You can connect to the CoA internal network via VPN when necessary. CTM runs occasional security scans for devices that shouldn't be on the network and if they discover your personal computer, they reserve the right to take your computer, run scans, and review files.

Daily Stand Up

We keep each other up to date on our progress and blockers by posting in #atd-standup every day:

• What did you do yesterday?

• What are you doing today?

• Any blockers?

It's helpful to cite specific Github issues you're working on.

Recover organization assets

Review Equipment Checkout form submitted

Exit Interview

1. Schedule exit interview

2. Complete exit interview

3. Analyze interview and retrieve insights

Transfer of Ownership

1. Make sure stakeholders know who to contact, that projects and products have been re-assigned

2. Give stakeholders status report of all ongoing projects

3. Gather list of outstanding tasks

4. Know where important files, documents, resources are located

5. Inform Diana and Karo to update the Service Desk documentation and calendar.

Application-specific versions of this process are written as issues so they can be tracked collaboratively for each release. Example: https://github.com/cityofaustin/atd-data-tech/issues/16094

Show all containers

Build image from Dockerfile

Run docker container in interactive mode and mount local volume inside container:

Start docker with docker-compose:

Update Docker Image on Docker Hub

1. Build the new image and tag with a new version number. Suppose your image name is atddocker/my-image:

1. Push to Docker Hub:

Have someone on the DTS team add you to the City of Austin organization and the Transportation team as a Maintainer.

Pipelines

The Zenhub board uses a Kanban-like format where issues are represented as cards and move across the board as they enter various stages of completion. Our workspace pipelines are:

• New Issues - Awaiting triage by Level I Support or Product.

• Icebox - Recorded and understood, but not committed to. Lack of evidence of overall value or applicability. We don't want to delete these and create a cycle of raising duplicate issues, so we keep them in our icebox with just enough information attached that we can pick it up sometime in the future — if and when we choose to do so.

• Needs Scoping - Potential projects or features that require clarification or exploration before presenting to builders for estimation and prioritizing.

• Backlog - Issues that are ready to be tackled by the team when the time comes. This pipeline is prioritized: the higher an issue is on this list, the higher the priority.

• On Deck - Slated for work in the current sprint. During Sprint Planning, we pull all issues that we intend to work on during the sprint into On Deck.

• Blocked - Issues that cannot be completed — often waiting on CTM or user feedback.

• In Progress - This one is self-explanatory. Each Issue in this pipeline should have an assigned owner who is responsible for its completion.

• Ongoing - Continually supported products and activities.

• Review/QA - Proposed as complete but awaiting approval — code review and/or acceptance testing — before closure.

• Ready to Deploy - Code or configuration that is ready to be deployed to production.

• Closed - Done! 🙌

Issues

Tracking our work in issues not only helps us stay organized, it gives us data on where we're spending our time. To create an issue, click the green "New issue" button in the upper right corner of the "Issues" page or our Zenhub board.

You will see a list of our custom issue templates. These are handy for creating bug reports, meetings, etc. with boilerplate information and structure.

Issue Titles

Issue titles should begin with a verb* and summarize the work to be completed. This convention improves data readability and helps keep our tasks action-oriented and unambiguous. Since you'll be using Product: and Type: labels, you don't need to spell out application names or issue types.

*Consider Update, Implement, Add, Remove, Review, Discuss, Troubleshoot...

Labels

You can apply labels by clicking the "Labels" heading in an issue's right-hand sidebar and beginning to type the label name.

You can also apply labels in bulk from on our Zenhub board.

The importance of labels

Accurate labeling is necessary for several reasons:

• Labels allow us to view related issues across the Zenhub pipelines. For example, during Apps Team Sprint Planning, we filter down to Service: Apps and during our periodic meetings with AMD we use the Workgroup: AMD label to look at all the work — across teams, of all sizes — that we're doing for them.

• Labels are also used to populate content on the DTS website.

• Finally, labels are critical to the service delivery data that we use to track, analyze, and improve our work.

Required labels

• Workgroup — the customer we're serving; Workgroup: DTS for internal work and Workgroup: TPW for department-wide work. Every issue should have one, and only one, Workgroup: label.

• Service — The DTS service team who will be doing the work. If there are two teams working on the same thing, copy the issue so there's one for each team. Every issue should have one, and only one, Service: label

• — The type of request or task. Every issue should have one, and only one, Type: label

• Project and/or Product labels, if applicable

  • refer to a substantial scope of related work that will reach a state of relative completion, such as the

  • are solutions that we continue to support over time, including all in-house applications, such as the Vision Zero Crash Data System

Optional labels

A DTS team or individual product manager may find these additional label categories helpful

• Impact — The effect of a bug, infrastructure failure, etc.

  • Impact: 1-Severe — Severely impacts TPW service delivery

  • Impact: 2-Major — Causes a major interruption of TPW service delivery

  • Impact: 3-Minor — Deteriorates TPW service delivery

  • Impact: 4-None — Does not affect TPW service delivery

• — To designate priority of a potential feature or enhancement

  • Impact: 1-Severe — Severely impacts TPW service delivery

  • Impact: 2-Major — Causes a major interruption of TPW service delivery

• — The external team or vendor executing the issue

Estimates

Estimates are how we track the level of effort of issues. Every issue should have an estimate once it is pulled on deck or into progress, and estimates can be adjusted as needed. Check estimates for accuracy whenever you close an issue. Use 0 estimates for duplicates and other issues we don't work on.

Like labels, estimates are required because they are a critical component of the service delivery data we use to track, analyze, and improve our work. Estimates are also useful for

• Sprint planning — to see when a person or team has too many issues (or too few!) issues assigned to them

• Stakeholder discussions when prioritizing features — being able to show stakeholders easily that we can accomplish, say, three small tasks, two medium, or one large

• Velocity tracking — i.e. predicting the likelihood we can complete a project by a given date

This is a good article about the hows and whys of estimates with ZenHub.

Assignees

An issue should be assigned to the person/people who will tackle it. This enables team members to filter down to issues they are responsible for easily.

Epics

Epics are a powerful feature that Zenhub adds to Github. They allow you to group related tasks and easily track them from one place. Here is a solid guide to how they work. Here is an example from another City of Austin project.

For ongoing tasks such as a recurring meeting, it may help to create an epic and put the individual instances of the tasks inside it. Here is an example of that type of usage for a task performed for a customer regularly.

Epics do not need estimates assigned to them manually. Instead, the effort is represented by the total of all the story points in the epic's issues. That said, you can add estimates to the epic issue to represent the effort used to managing the sub tasks, i.e. meetings with stakeholders as the work progresses.

Ultimately, epics can group whatever makes sense for you and your collaborators. Some people prefer issues with task lists inside them. That's fine as long as the issue doesn't require more effort than we can represent in our estimate scale for a single issue.

Learning More

Here are some additional guides for some of our most relied-upon Zenhub functionality:

• Filtering the Board

• "Use multi-action to make bulk Issue updates" on this page

The Zenhub docs are super-solid, and we encourage you to peruse them at your leisure. Remember that some functionality—renaming and reordering pipelines themselves, for example—will affect the workspace for the whole team. We're always looking for ways to improve our process, so if you come across an approach or functionality you think is promising, add it to the agenda for our weekly Product Sync or share it in the #atd-product Slack channel!

Project Initiation

Oftentimes, our customers initiate a project by submitting a DTS service request that is notably large and/or important.

A DTS team member may also create a project when there is significant work to be done on an internal product—such as updating Austinmobility.io, a technical refactor of the Vision Zero Database, or migrating our CCTV image service from a local server to the cloud.

In either case, we begin by verifying that all our DTS project prerequisites are met:

• Dedicated product owner to support requirements gathering, user research, and user onboarding

• Division Manager sponsor to champion the project at the executive level

• A commitment from the customer to collaborate in DTS's iterative, user-centered development process

Then either create a new project index issue or convert the existing issue to match the project index template. Either way, make sure that the 'Project Index' label is on the issue so that an evaluation record for the project is added to the DTS Portal and it appears on the website.

Move the issue to the "Needs Scoping" Zenhub pipeline.

Scoping

• PM schedules an intake meeting. Ideally, this will include actual users as well as the workgroup manager.

• Prepare Intake Meeting Agenda.

• Meet and take notes; photos/recording may also be helpful.

• Add notes/photos/recording to Github issue.

• If necessary, update issue description to ensure it clearly summarizes request.

Builder Huddle

• PM sets up meeting with potential builders, e.g. Dev for a Vision Zero Viewer project, Apps for a ROW Portal project. If we aren't sure which route we'll go or the solution will require both, add to the Dev/Product Sync agenda to discuss.

• Prepare a summary of request. Here's an example done as a presentation deck (template).

• At the meeting, discuss the recommended approach and fill out the "Effort" section of the project evaluation in the DTS Portal.

Product Sync

After assessing effort with the builders, it's time to assess value with the product team.

• Add to DTS Product Sync agenda for a "Refinement-week", i.e. the second Wednesday in a sprint. If feedback is needed sooner, or the project was initiated internally (like work on our technical infrastructure), bring it to Dev + Product Sync instead.

• As a group, fill out the "Value" section of the project evaluation in the DTS Portal.

After the evaluation is complete, the Austinmobility.io script will pick them up and you will be able to see the project in relation to other projects in our backlog using the prioritization matrix.

Move the index issue into the "Backlog" pipeline.

Prioritization

Project Prioritization Process as of 5/24

Google presentation used for Product Ops onboarding and TPW Executive communications.

Working docs

• Project Prioritization workflow

• DTS + OPM workflow

Activation

Once the time comes to work on the project:

• Move the issue to the "In Progress" pipeline.

• If you don't already have regular Sprint Reviews with the project's stakeholders, set up recurring meetings for the duration of the project so that you can demo work and get feedback.

• Create a folder in the Projects/Products DTS Drive.

• . Fill out the "Description" field and use the hex code #3D3D3D for "Color." Use this label for all issues moving forward so that they render on the projects' website page and are easy to surface on Zenhub/Github.

• Fill out the rest of the project index including background, outcomes, timeline, etc. Add these headings to the issue:

• Convert the project index issue into an epic and assign future issues to the epic moving forward. Zenhub allows you to nest epics or assign issues to multiple epics, so feel free to use that functionality if you find it helpful.

• Ensure that everyone who has stake in the project, from potentially impacted staff to interested executives, is aware the project is moving forward. Invite stakeholders to come to sprint reviews and/or participate in user research. Ask them who else should be included.

• Optionally, hold a kick-off meeting with your stakeholders.

Delivery

• Perform requirements gathering with users. We often begin with user interviews and store requirements either as user stories for in-house applications or in a software comparison matrix for off-the-shelf solutions.

• Document bugs, feature requests, and enhancements as Github issues. You may want to encourage your users to contribute using the DTS Service Request.

• Work with the team lead—via Github comments or in a planning/refinement/sync meeting—to assign an estimate to each issue. Zenhub's Planning Poker is also a fun way to estimate asynchronously.

• Bring complex issues to Backlog Refinement (Apps | Dev) to discuss with builders. Break them up into smaller issues as necessary, document the agreed-upon approach, and align on an estimate.

• Prioritize work with stakeholders during Sprint Reviews.

• If practical, versions of an application on a regular basis.

• Perform usability testing to surface improvements to the user experience. Since we don't have dedicated user researchers at DTS, we love for its simplicity and depth of insight. we've done. It's handy to record sessions on Teams so that you can expand on your notes, embed screenshots/clips in issues, etc.

Completion

A project is considered complete when the minimum viable product—captured in the "Scope and Deliverables" section of the issue's project index—is delivered to users.

• Often, there are still issues in the backlog that are not actually must-haves. Remove the project label, remove them from the epic, and review them the next time you meet with stakeholders so they can prioritize those against any of their other ongoing requests.

• Retire the project label by adding "[Archive]" to the "Description" field and update the hex code to #B8B8B7.

• Write a final update as a comment on the index issue and close the issue.

• By default, completed projects show on "Complete" tab on the “Projects" page of the website, but you can apply the Archived Project label to prevent that. We like to curate this page to showcase our most compelling, impactful, and well-documented work.

We collect dockless trip records from each provider using a Python mds client which stores processed data in a Postgrest database.

• transportation-dockless-processing

• MDS Provider Client

Public Trip Records and Privacy

We believe strongly that we do our best work when we work openly. It’s why we’ve built all of our reporting infrastructure on top of open data, and we’re continuing that practice with dockless mobility data.

We publish anonymized dockless trip records to our open data portal on an hourly basis. The dataset is here.

We have been very thoughtful about how we are approaching the release of this data. We are following the recommendations outlined in the Civic Analytics Network’s recent open letter, which was signed by Chief Data Officers and industry experts across the country.

Specifically, our trip records:

• Do not include any vendor-provided identifiers. The trip IDs and device IDs in our dataset are completely arbitrary and cannot be traced to a specific operator.

• Have start and end times rounded to the nearest 15 minutes.

• Use latitude and longitude values rounded to three decimal degrees (roughly the area of a city block).

Reporting Dashboard

You can view monthly dockless trip summaries here

This is a public website that pulls directly from our public datasets. Here's the source code.

Trip Explorer

We have built an interactive web map which visualizes where dockless trips are starting and ending. We’re calling it the Dockless Data Explorer, available at dockless.austintexas.io.

Open Source

The source code for our dockless mobility tools is freely available in five repositories (and counting):

• Dockless Data Processing

• Transportation Datahub

• Dockless API

Reporting Queries

Here are some handy queries for fetching dockless data summaries from the Open Data Portal

Scooter and Bike trips by Month/Year*

Dockless Trips by vehicle type and month/year*

*Denotes that the query includes a filter for min/max distance (.1 miles / 500 miles) and max time (24 hours)

Dockless Trips by Day

The where clause can be modified to specify year and month. This selects february and march 2019 date_extract_m(start_time) in (2, 3) and date_extract_y(start_time) = 2019

Tiles

Each project or product is rendered as a tile using content from the index issue:

Issues and activity

All issues with the Product: label for a given product will be rendered on the Issues tab (example) and all comments on the project/product Index issue itself will show on the Activity tab (example).

Evaluation

In order for the Evaluation tab (example) to render correctly, the project must have an evaluation completed in the DTS Portal.

Once an issue is labeled Project Index, it will automatically be added as a project in the DTS Portal.

If your project is not listed in Knack, the ETL may not yet have run. You can manually create a new entry in Knack, just make sure you provide the correct github issue # when creating the entry. The ETL will overwrite any project name you supply manually.

Evaluating effort

Product Managers work with builders—the Apps, Dev, Data Science, or Geo teams—to assess the level of effort for a project.

Evaluating value

A project's predicted value is added to the Product Sync agenda so that the Product team can review it as a group and determine a score together.

Remember, never add a Gmail address to this account! It's against City policy and creates a permissions headache for your supervisor.

Permissions

All your documents should be saved within a folder owned by a shared resource account, coaatdamd@austintexas.gov. This means we can all search and access each other's files, even if someone is out of the office or leaves the team.

Sensitive information

Under no circumstances should sensitive information be stored in Google Drive. This includes CJIS and HIPAA data, along with any personally identifiable information about individuals in the community.

See Packaging Python Projects (python.org)

1. Your python envrionment will require the following pacakges:

   Copy

    python=3
    setuptools
    twine

2. Update the semantic version number in the package's setup.py.

3. From the same directory as setup.py build the new version:

4. Upload the new version to . (You'll be prompted to enter your username/password):

All projects which have been scoped require a project index issue to be placed in the appropriate Zenhub pipeline. The issue title, description, and labels should follow the below guidelines.

Title

The issue title should be prefixed with Project: . For example, Project: Warehouse Inventory Management.

Labels

• Project Index

• Project: xzy — A project-specific label that you will create, following our project label conventions

• Workgroup: xyz — the project stakeholder workgroups

Assignees

All DTS team members who contributed substantially to the project, including at least one product manager or team lead.

Description

Follow the Project Index issue template.

Image

See Index Issue Images below.

Product Index

All products require a product index issue to be placed in the appropriate Zenhub pipeline. Once a product has been released, it should be placed in the Ongoing pipeline indefinitely until it is removed from service. The issue title, description, and labels should follow the below guidelines.

Title

The issue title should be prefixed with Product: . For example, Product: Data Tracker

Labels

• Product Index

• Product: xzy — A product-specific label that you will create, following our product label conventions

• Workgroup: xyz — the workgroup(s) of the product's primary users

Assignee

The product manager.

Issue description

Follow the Product Index issue template.

Image

See Index Issue Images below.

Index Issue Images

All projects and products should have at least one image so that missing thumbnails don't disrupt the website design. We prefer these thumbnails options:

• A map or other visualization of the data generated in the app

• Photos of the project/product's end users at work or the related hardware/service; the TPW Flickr feed is a fantastic source for these. We also have a stash of nice photos you can add to or use.

• A close-up screenshot of a unique part of the UI

• For mobile-focused apps, we have a to show off ​

Please avoid using

• Full-screen screenshots or large diagrams as the first image - these don't render well in tiles. Include these later on in the issue if they are helpful way to communicate the work.

• Vendor logos - these doesn't give any information about the platform or use case and promote a commercial companies

The image should be at least 1000px wide, with a 3:2 aspect ratio. This tool makes it easy to crop/resize as needed.

knack-proxy was a flask app, but has been taken down.

Its functionality was no longer needed after Boomi replaced the Enterprise Service Bus (ESB). Boomi is able to communicate directly with Knack. The change-over occurred in January, 2026.

cctv-service is a sanic app.

Since we converted this code into an async Sanic app we haven't had issues with it failing. But we did previously with Flask and never really got to understand the root issues.

If it goes down, log into atd-data01 via ssh and restart the containerized app with docker restart cctv-service.

atd-data01 is our main/production data publishing server.

If atd-data01 crashes, it would just need to be restarted. Insert bash command sudo reboot. All of the data scripts are on cron jobs and will restart at various times. The two service app in docker containers on atd-data01 do need to be restarted manually. Those restart scripts live in their respective Github READMEs.

Bash Commands

Allocate Disk Space

1. List volumes and usage:

2. Check the free available space in the Volume group

3. Extend the volume (here, adding 8GB)

4. Expand the volume:

5. All done.

Miscellaneous:

run all shell scripts inside a folder

scp transfer files from local to remote directory:

Amazon AWS

connect to instance

Querying the API

The postgREST-provided jobs API is available at https://atd-postgrest.austinmobility.io/legacy-scripts/jobs, and it can be queried using, as described in the PostgREST documentation. VPN access is required. You can also query the api.jobs table directly from our Postgres read replica.

Field Definitions:

Python Example

We've written a Python utility to interact with the jobs interface. It's included in our transportation-data-utils (tdutils) pacakge. tdutils requires Python 3 and can be installed with $ pip install tdutils.

Begin by importing the jobutil library and creating a new job instance:

Assuming you've run this job successfully in the past, you can use the most_recent method to return a unix timestamp from the last successful job run:

Register your new job with job.start(). The API returns a JSON representation of newly created job record:

We have successfuly registered a new job. Note that the status was automatically set to in_progress. If we were to call job.most_recent() again, the results are the same as before, because the status of current job is not success:

From here, continue your ETL process as needed. When your ETL is complete, use job.result() to update your job status accordingly. Again, a JSON representation of the job record is returned:

Note that the end_date was populated automatically. Because the job was successful, calling job.most_recent() now returns the timestamp of our current job:

You should also register job failures. The errror result is availabe for such purposes: