diff --git a/docs/.gitbook/assets/1.png b/docs/.gitbook/assets/1.png new file mode 100644 index 0000000..1e27a57 Binary files /dev/null and b/docs/.gitbook/assets/1.png differ diff --git a/docs/.gitbook/assets/11.png b/docs/.gitbook/assets/11.png new file mode 100644 index 0000000..07498cc Binary files /dev/null and b/docs/.gitbook/assets/11.png differ diff --git a/docs/.gitbook/assets/12.png b/docs/.gitbook/assets/12.png new file mode 100644 index 0000000..073fee5 Binary files /dev/null and b/docs/.gitbook/assets/12.png differ diff --git a/docs/.gitbook/assets/2.png b/docs/.gitbook/assets/2.png new file mode 100644 index 0000000..f726679 Binary files /dev/null and b/docs/.gitbook/assets/2.png differ diff --git a/docs/.gitbook/assets/21 (1).png b/docs/.gitbook/assets/21 (1).png new file mode 100644 index 0000000..70224bd Binary files /dev/null and b/docs/.gitbook/assets/21 (1).png differ diff --git a/docs/.gitbook/assets/21.png b/docs/.gitbook/assets/21.png new file mode 100644 index 0000000..70224bd Binary files /dev/null and b/docs/.gitbook/assets/21.png differ diff --git a/docs/.gitbook/assets/22.png b/docs/.gitbook/assets/22.png new file mode 100644 index 0000000..5e77dd0 Binary files /dev/null and b/docs/.gitbook/assets/22.png differ diff --git a/docs/.gitbook/assets/3.webp b/docs/.gitbook/assets/3.webp new file mode 100644 index 0000000..5c04a3b Binary files /dev/null and b/docs/.gitbook/assets/3.webp differ diff --git a/docs/.gitbook/assets/4 (1).png b/docs/.gitbook/assets/4 (1).png new file mode 100644 index 0000000..931b7a8 Binary files /dev/null and b/docs/.gitbook/assets/4 (1).png differ diff --git a/docs/.gitbook/assets/4.png b/docs/.gitbook/assets/4.png new file mode 100644 index 0000000..a8a1561 Binary files /dev/null and b/docs/.gitbook/assets/4.png differ diff --git a/docs/.gitbook/assets/6.png b/docs/.gitbook/assets/6.png new file mode 100644 index 0000000..4cb254b Binary files /dev/null and b/docs/.gitbook/assets/6.png differ diff --git a/docs/.gitbook/assets/7.png b/docs/.gitbook/assets/7.png new file mode 100644 index 0000000..0174be7 Binary files /dev/null and b/docs/.gitbook/assets/7.png differ diff --git a/docs/.gitbook/assets/8.png b/docs/.gitbook/assets/8.png new file mode 100644 index 0000000..a94c077 Binary files /dev/null and b/docs/.gitbook/assets/8.png differ diff --git a/docs/.gitbook/assets/AnyConnect-Connected.png b/docs/.gitbook/assets/AnyConnect-Connected.png new file mode 100644 index 0000000..b74a573 Binary files /dev/null and b/docs/.gitbook/assets/AnyConnect-Connected.png differ diff --git a/docs/.gitbook/assets/DTS Website - Product Tiles.png b/docs/.gitbook/assets/DTS Website - Product Tiles.png new file mode 100644 index 0000000..5c34738 Binary files /dev/null and b/docs/.gitbook/assets/DTS Website - Product Tiles.png differ diff --git a/docs/.gitbook/assets/DTS Website - Tiles Components.png b/docs/.gitbook/assets/DTS Website - Tiles Components.png new file mode 100644 index 0000000..d50d391 Binary files /dev/null and b/docs/.gitbook/assets/DTS Website - Tiles Components.png differ diff --git a/docs/.gitbook/assets/Index Tile Components.png b/docs/.gitbook/assets/Index Tile Components.png new file mode 100644 index 0000000..d498fdc Binary files /dev/null and b/docs/.gitbook/assets/Index Tile Components.png differ diff --git a/docs/.gitbook/assets/Mateo-Testing.jpeg b/docs/.gitbook/assets/Mateo-Testing.jpeg new file mode 100644 index 0000000..163ce8d Binary files /dev/null and b/docs/.gitbook/assets/Mateo-Testing.jpeg differ diff --git a/docs/.gitbook/assets/Screen Shot 2020-05-04 at 6.20.10 PM.png b/docs/.gitbook/assets/Screen Shot 2020-05-04 at 6.20.10 PM.png new file mode 100644 index 0000000..70224bd Binary files /dev/null and b/docs/.gitbook/assets/Screen Shot 2020-05-04 at 6.20.10 PM.png differ diff --git a/docs/.gitbook/assets/Screen Shot 2020-05-04 at 6.22.09 PM.png b/docs/.gitbook/assets/Screen Shot 2020-05-04 at 6.22.09 PM.png new file mode 100644 index 0000000..5e77dd0 Binary files /dev/null and b/docs/.gitbook/assets/Screen Shot 2020-05-04 at 6.22.09 PM.png differ diff --git a/docs/.gitbook/assets/Screen Shot 2021-11-01 at 11.20.27 PM.png b/docs/.gitbook/assets/Screen Shot 2021-11-01 at 11.20.27 PM.png new file mode 100644 index 0000000..5c34738 Binary files /dev/null and b/docs/.gitbook/assets/Screen Shot 2021-11-01 at 11.20.27 PM.png differ diff --git a/docs/.gitbook/assets/Screen Shot 2021-11-01 at 7.49.16 PM.png b/docs/.gitbook/assets/Screen Shot 2021-11-01 at 7.49.16 PM.png new file mode 100644 index 0000000..a69baa5 Binary files /dev/null and b/docs/.gitbook/assets/Screen Shot 2021-11-01 at 7.49.16 PM.png differ diff --git a/docs/.gitbook/assets/Screen Shot 2022-05-24 at 10.39.48 AM.png b/docs/.gitbook/assets/Screen Shot 2022-05-24 at 10.39.48 AM.png new file mode 100644 index 0000000..d9bfe97 Binary files /dev/null and b/docs/.gitbook/assets/Screen Shot 2022-05-24 at 10.39.48 AM.png differ diff --git a/docs/.gitbook/assets/WO_ATSD_1407.PNG b/docs/.gitbook/assets/WO_ATSD_1407.PNG new file mode 100644 index 0000000..1ccf0a4 Binary files /dev/null and b/docs/.gitbook/assets/WO_ATSD_1407.PNG differ diff --git a/docs/.gitbook/assets/anyconnect-connected.png b/docs/.gitbook/assets/anyconnect-connected.png new file mode 100644 index 0000000..b74a573 Binary files /dev/null and b/docs/.gitbook/assets/anyconnect-connected.png differ diff --git a/docs/.gitbook/assets/anyconnect-warning.png b/docs/.gitbook/assets/anyconnect-warning.png new file mode 100644 index 0000000..8418b52 Binary files /dev/null and b/docs/.gitbook/assets/anyconnect-warning.png differ diff --git a/docs/.gitbook/assets/avaya-onex-communicator-softphone.docx b/docs/.gitbook/assets/avaya-onex-communicator-softphone.docx new file mode 100644 index 0000000..3e9d0b5 Binary files /dev/null and b/docs/.gitbook/assets/avaya-onex-communicator-softphone.docx differ diff --git a/docs/.gitbook/assets/avaya-unified-messaging-accessing-voicemail-user-guide.pdf b/docs/.gitbook/assets/avaya-unified-messaging-accessing-voicemail-user-guide.pdf new file mode 100644 index 0000000..b30035e Binary files /dev/null and b/docs/.gitbook/assets/avaya-unified-messaging-accessing-voicemail-user-guide.pdf differ diff --git a/docs/.gitbook/assets/clone_complete.png b/docs/.gitbook/assets/clone_complete.png new file mode 100644 index 0000000..dca0796 Binary files /dev/null and b/docs/.gitbook/assets/clone_complete.png differ diff --git a/docs/.gitbook/assets/clone_local_wiki.png b/docs/.gitbook/assets/clone_local_wiki.png new file mode 100644 index 0000000..1dd3d41 Binary files /dev/null and b/docs/.gitbook/assets/clone_local_wiki.png differ diff --git a/docs/.gitbook/assets/complete_install.png b/docs/.gitbook/assets/complete_install.png new file mode 100644 index 0000000..285f212 Binary files /dev/null and b/docs/.gitbook/assets/complete_install.png differ diff --git a/docs/.gitbook/assets/g-drive-connect.png b/docs/.gitbook/assets/g-drive-connect.png new file mode 100644 index 0000000..0174be7 Binary files /dev/null and b/docs/.gitbook/assets/g-drive-connect.png differ diff --git a/docs/.gitbook/assets/g-drive-connected.png b/docs/.gitbook/assets/g-drive-connected.png new file mode 100644 index 0000000..a94c077 Binary files /dev/null and b/docs/.gitbook/assets/g-drive-connected.png differ diff --git a/docs/.gitbook/assets/image (1).png b/docs/.gitbook/assets/image (1).png new file mode 100644 index 0000000..c7e9723 Binary files /dev/null and b/docs/.gitbook/assets/image (1).png differ diff --git a/docs/.gitbook/assets/image (10).png b/docs/.gitbook/assets/image (10).png new file mode 100644 index 0000000..b20a2f6 Binary files /dev/null and b/docs/.gitbook/assets/image (10).png differ diff --git a/docs/.gitbook/assets/image (102).png b/docs/.gitbook/assets/image (102).png new file mode 100644 index 0000000..a828812 Binary files /dev/null and b/docs/.gitbook/assets/image (102).png differ diff --git a/docs/.gitbook/assets/image (103).png b/docs/.gitbook/assets/image (103).png new file mode 100644 index 0000000..a298738 Binary files /dev/null and b/docs/.gitbook/assets/image (103).png differ diff --git a/docs/.gitbook/assets/image (104).png b/docs/.gitbook/assets/image (104).png new file mode 100644 index 0000000..b56c479 Binary files /dev/null and b/docs/.gitbook/assets/image (104).png differ diff --git a/docs/.gitbook/assets/image (107).png b/docs/.gitbook/assets/image (107).png new file mode 100644 index 0000000..98cfb0c Binary files /dev/null and b/docs/.gitbook/assets/image (107).png differ diff --git a/docs/.gitbook/assets/image (11) (1).png b/docs/.gitbook/assets/image (11) (1).png new file mode 100644 index 0000000..8be6070 Binary files /dev/null and b/docs/.gitbook/assets/image (11) (1).png differ diff --git a/docs/.gitbook/assets/image (11).png b/docs/.gitbook/assets/image (11).png new file mode 100644 index 0000000..8be6070 Binary files /dev/null and b/docs/.gitbook/assets/image (11).png differ diff --git a/docs/.gitbook/assets/image (12).png b/docs/.gitbook/assets/image (12).png new file mode 100644 index 0000000..8a2d78b Binary files /dev/null and b/docs/.gitbook/assets/image (12).png differ diff --git a/docs/.gitbook/assets/image (13) (2) (2) (2) (2) (2) (1).png b/docs/.gitbook/assets/image (13) (2) (2) (2) (2) (2) (1).png new file mode 100644 index 0000000..81da3c7 Binary files /dev/null and b/docs/.gitbook/assets/image (13) (2) (2) (2) (2) (2) (1).png differ diff --git a/docs/.gitbook/assets/image (13) (2) (2) (2) (2) (2).png b/docs/.gitbook/assets/image (13) (2) (2) (2) (2) (2).png new file mode 100644 index 0000000..81da3c7 Binary files /dev/null and b/docs/.gitbook/assets/image (13) (2) (2) (2) (2) (2).png differ diff --git a/docs/.gitbook/assets/image (13).png b/docs/.gitbook/assets/image (13).png new file mode 100644 index 0000000..81da3c7 Binary files /dev/null and b/docs/.gitbook/assets/image (13).png differ diff --git a/docs/.gitbook/assets/image (14).png b/docs/.gitbook/assets/image (14).png new file mode 100644 index 0000000..0f0f027 Binary files /dev/null and b/docs/.gitbook/assets/image (14).png differ diff --git a/docs/.gitbook/assets/image (15).png b/docs/.gitbook/assets/image (15).png new file mode 100644 index 0000000..09113bb Binary files /dev/null and b/docs/.gitbook/assets/image (15).png differ diff --git a/docs/.gitbook/assets/image (16).png b/docs/.gitbook/assets/image (16).png new file mode 100644 index 0000000..3debd69 Binary files /dev/null and b/docs/.gitbook/assets/image (16).png differ diff --git a/docs/.gitbook/assets/image (17).png b/docs/.gitbook/assets/image (17).png new file mode 100644 index 0000000..94e8c4a Binary files /dev/null and b/docs/.gitbook/assets/image (17).png differ diff --git a/docs/.gitbook/assets/image (19).png b/docs/.gitbook/assets/image (19).png new file mode 100644 index 0000000..a8bf489 Binary files /dev/null and b/docs/.gitbook/assets/image (19).png differ diff --git a/docs/.gitbook/assets/image (2).png b/docs/.gitbook/assets/image (2).png new file mode 100644 index 0000000..fb9ce5e Binary files /dev/null and b/docs/.gitbook/assets/image (2).png differ diff --git a/docs/.gitbook/assets/image (21).png b/docs/.gitbook/assets/image (21).png new file mode 100644 index 0000000..939e6fb Binary files /dev/null and b/docs/.gitbook/assets/image (21).png differ diff --git a/docs/.gitbook/assets/image (22).png b/docs/.gitbook/assets/image (22).png new file mode 100644 index 0000000..78e995f Binary files /dev/null and b/docs/.gitbook/assets/image (22).png differ diff --git a/docs/.gitbook/assets/image (26).png b/docs/.gitbook/assets/image (26).png new file mode 100644 index 0000000..ee3a667 Binary files /dev/null and b/docs/.gitbook/assets/image (26).png differ diff --git a/docs/.gitbook/assets/image (27).png b/docs/.gitbook/assets/image (27).png new file mode 100644 index 0000000..99ad063 Binary files /dev/null and b/docs/.gitbook/assets/image (27).png differ diff --git a/docs/.gitbook/assets/image (28).png b/docs/.gitbook/assets/image (28).png new file mode 100644 index 0000000..871937c Binary files /dev/null and b/docs/.gitbook/assets/image (28).png differ diff --git a/docs/.gitbook/assets/image (29).png b/docs/.gitbook/assets/image (29).png new file mode 100644 index 0000000..7674228 Binary files /dev/null and b/docs/.gitbook/assets/image (29).png differ diff --git a/docs/.gitbook/assets/image (3) (1).png b/docs/.gitbook/assets/image (3) (1).png new file mode 100644 index 0000000..c7e9723 Binary files /dev/null and b/docs/.gitbook/assets/image (3) (1).png differ diff --git a/docs/.gitbook/assets/image (3).png b/docs/.gitbook/assets/image (3).png new file mode 100644 index 0000000..fb9ce5e Binary files /dev/null and b/docs/.gitbook/assets/image (3).png differ diff --git a/docs/.gitbook/assets/image (31).png b/docs/.gitbook/assets/image (31).png new file mode 100644 index 0000000..4bb424b Binary files /dev/null and b/docs/.gitbook/assets/image (31).png differ diff --git a/docs/.gitbook/assets/image (32).png b/docs/.gitbook/assets/image (32).png new file mode 100644 index 0000000..791d009 Binary files /dev/null and b/docs/.gitbook/assets/image (32).png differ diff --git a/docs/.gitbook/assets/image (33).png b/docs/.gitbook/assets/image (33).png new file mode 100644 index 0000000..3cf53a0 Binary files /dev/null and b/docs/.gitbook/assets/image (33).png differ diff --git a/docs/.gitbook/assets/image (34).png b/docs/.gitbook/assets/image (34).png new file mode 100644 index 0000000..c56c0eb Binary files /dev/null and b/docs/.gitbook/assets/image (34).png differ diff --git a/docs/.gitbook/assets/image (39).png b/docs/.gitbook/assets/image (39).png new file mode 100644 index 0000000..f3b4a60 Binary files /dev/null and b/docs/.gitbook/assets/image (39).png differ diff --git a/docs/.gitbook/assets/image (4).png b/docs/.gitbook/assets/image (4).png new file mode 100644 index 0000000..0ee453c Binary files /dev/null and b/docs/.gitbook/assets/image (4).png differ diff --git a/docs/.gitbook/assets/image (40).png b/docs/.gitbook/assets/image (40).png new file mode 100644 index 0000000..e69eaf8 Binary files /dev/null and b/docs/.gitbook/assets/image (40).png differ diff --git a/docs/.gitbook/assets/image (41).png b/docs/.gitbook/assets/image (41).png new file mode 100644 index 0000000..cac3ec7 Binary files /dev/null and b/docs/.gitbook/assets/image (41).png differ diff --git a/docs/.gitbook/assets/image (42).png b/docs/.gitbook/assets/image (42).png new file mode 100644 index 0000000..ea2d543 Binary files /dev/null and b/docs/.gitbook/assets/image (42).png differ diff --git a/docs/.gitbook/assets/image (43).png b/docs/.gitbook/assets/image (43).png new file mode 100644 index 0000000..05d91fd Binary files /dev/null and b/docs/.gitbook/assets/image (43).png differ diff --git a/docs/.gitbook/assets/image (44).png b/docs/.gitbook/assets/image (44).png new file mode 100644 index 0000000..a5892b8 Binary files /dev/null and b/docs/.gitbook/assets/image (44).png differ diff --git a/docs/.gitbook/assets/image (47).png b/docs/.gitbook/assets/image (47).png new file mode 100644 index 0000000..b52a6ae Binary files /dev/null and b/docs/.gitbook/assets/image (47).png differ diff --git a/docs/.gitbook/assets/image (48).png b/docs/.gitbook/assets/image (48).png new file mode 100644 index 0000000..9c79502 Binary files /dev/null and b/docs/.gitbook/assets/image (48).png differ diff --git a/docs/.gitbook/assets/image (5) (1).png b/docs/.gitbook/assets/image (5) (1).png new file mode 100644 index 0000000..c943f19 Binary files /dev/null and b/docs/.gitbook/assets/image (5) (1).png differ diff --git a/docs/.gitbook/assets/image (5).png b/docs/.gitbook/assets/image (5).png new file mode 100644 index 0000000..c943f19 Binary files /dev/null and b/docs/.gitbook/assets/image (5).png differ diff --git a/docs/.gitbook/assets/image (51).png b/docs/.gitbook/assets/image (51).png new file mode 100644 index 0000000..8cf2994 Binary files /dev/null and b/docs/.gitbook/assets/image (51).png differ diff --git a/docs/.gitbook/assets/image (52).png b/docs/.gitbook/assets/image (52).png new file mode 100644 index 0000000..58e5828 Binary files /dev/null and b/docs/.gitbook/assets/image (52).png differ diff --git a/docs/.gitbook/assets/image (54) (2) (2) (2) (2) (2) (1).png b/docs/.gitbook/assets/image (54) (2) (2) (2) (2) (2) (1).png new file mode 100644 index 0000000..2eb96f0 Binary files /dev/null and b/docs/.gitbook/assets/image (54) (2) (2) (2) (2) (2) (1).png differ diff --git a/docs/.gitbook/assets/image (54) (2) (2) (2) (2) (2).png b/docs/.gitbook/assets/image (54) (2) (2) (2) (2) (2).png new file mode 100644 index 0000000..2eb96f0 Binary files /dev/null and b/docs/.gitbook/assets/image (54) (2) (2) (2) (2) (2).png differ diff --git a/docs/.gitbook/assets/image (54).png b/docs/.gitbook/assets/image (54).png new file mode 100644 index 0000000..2eb96f0 Binary files /dev/null and b/docs/.gitbook/assets/image (54).png differ diff --git a/docs/.gitbook/assets/image (55).png b/docs/.gitbook/assets/image (55).png new file mode 100644 index 0000000..66e5656 Binary files /dev/null and b/docs/.gitbook/assets/image (55).png differ diff --git a/docs/.gitbook/assets/image (56).png b/docs/.gitbook/assets/image (56).png new file mode 100644 index 0000000..efe85ad Binary files /dev/null and b/docs/.gitbook/assets/image (56).png differ diff --git a/docs/.gitbook/assets/image (57) (1).png b/docs/.gitbook/assets/image (57) (1).png new file mode 100644 index 0000000..2622980 Binary files /dev/null and b/docs/.gitbook/assets/image (57) (1).png differ diff --git a/docs/.gitbook/assets/image (57).png b/docs/.gitbook/assets/image (57).png new file mode 100644 index 0000000..2622980 Binary files /dev/null and b/docs/.gitbook/assets/image (57).png differ diff --git a/docs/.gitbook/assets/image (59).png b/docs/.gitbook/assets/image (59).png new file mode 100644 index 0000000..116ad43 Binary files /dev/null and b/docs/.gitbook/assets/image (59).png differ diff --git a/docs/.gitbook/assets/image (6).png b/docs/.gitbook/assets/image (6).png new file mode 100644 index 0000000..240ac5d Binary files /dev/null and b/docs/.gitbook/assets/image (6).png differ diff --git a/docs/.gitbook/assets/image (61).png b/docs/.gitbook/assets/image (61).png new file mode 100644 index 0000000..0d873be Binary files /dev/null and b/docs/.gitbook/assets/image (61).png differ diff --git a/docs/.gitbook/assets/image (62).png b/docs/.gitbook/assets/image (62).png new file mode 100644 index 0000000..0d4bdbc Binary files /dev/null and b/docs/.gitbook/assets/image (62).png differ diff --git a/docs/.gitbook/assets/image (65).png b/docs/.gitbook/assets/image (65).png new file mode 100644 index 0000000..ef011fd Binary files /dev/null and b/docs/.gitbook/assets/image (65).png differ diff --git a/docs/.gitbook/assets/image (69).png b/docs/.gitbook/assets/image (69).png new file mode 100644 index 0000000..435cc8d Binary files /dev/null and b/docs/.gitbook/assets/image (69).png differ diff --git a/docs/.gitbook/assets/image (7) (1) (1) (1).png b/docs/.gitbook/assets/image (7) (1) (1) (1).png new file mode 100644 index 0000000..2e42eca Binary files /dev/null and b/docs/.gitbook/assets/image (7) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (7) (1) (1).png b/docs/.gitbook/assets/image (7) (1) (1).png new file mode 100644 index 0000000..2e42eca Binary files /dev/null and b/docs/.gitbook/assets/image (7) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (7).png b/docs/.gitbook/assets/image (7).png new file mode 100644 index 0000000..3bfba80 Binary files /dev/null and b/docs/.gitbook/assets/image (7).png differ diff --git a/docs/.gitbook/assets/image (72).png b/docs/.gitbook/assets/image (72).png new file mode 100644 index 0000000..cd9dc44 Binary files /dev/null and b/docs/.gitbook/assets/image (72).png differ diff --git a/docs/.gitbook/assets/image (73).png b/docs/.gitbook/assets/image (73).png new file mode 100644 index 0000000..97425fd Binary files /dev/null and b/docs/.gitbook/assets/image (73).png differ diff --git a/docs/.gitbook/assets/image (74).png b/docs/.gitbook/assets/image (74).png new file mode 100644 index 0000000..d39846a Binary files /dev/null and b/docs/.gitbook/assets/image (74).png differ diff --git a/docs/.gitbook/assets/image (75).png b/docs/.gitbook/assets/image (75).png new file mode 100644 index 0000000..02fb3e8 Binary files /dev/null and b/docs/.gitbook/assets/image (75).png differ diff --git a/docs/.gitbook/assets/image (76).png b/docs/.gitbook/assets/image (76).png new file mode 100644 index 0000000..7458904 Binary files /dev/null and b/docs/.gitbook/assets/image (76).png differ diff --git a/docs/.gitbook/assets/image (78).png b/docs/.gitbook/assets/image (78).png new file mode 100644 index 0000000..056f3cb Binary files /dev/null and b/docs/.gitbook/assets/image (78).png differ diff --git a/docs/.gitbook/assets/image (79).png b/docs/.gitbook/assets/image (79).png new file mode 100644 index 0000000..bf3e5c1 Binary files /dev/null and b/docs/.gitbook/assets/image (79).png differ diff --git a/docs/.gitbook/assets/image (8) (1) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (8) (1) (1) (1) (1) (1).png new file mode 100644 index 0000000..1dee427 Binary files /dev/null and b/docs/.gitbook/assets/image (8) (1) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (8) (1) (1) (1) (1).png b/docs/.gitbook/assets/image (8) (1) (1) (1) (1).png new file mode 100644 index 0000000..1dee427 Binary files /dev/null and b/docs/.gitbook/assets/image (8) (1) (1) (1) (1).png differ diff --git a/docs/.gitbook/assets/image (8).png b/docs/.gitbook/assets/image (8).png new file mode 100644 index 0000000..0ee453c Binary files /dev/null and b/docs/.gitbook/assets/image (8).png differ diff --git a/docs/.gitbook/assets/image (82).png b/docs/.gitbook/assets/image (82).png new file mode 100644 index 0000000..164ed5a Binary files /dev/null and b/docs/.gitbook/assets/image (82).png differ diff --git a/docs/.gitbook/assets/image (83).png b/docs/.gitbook/assets/image (83).png new file mode 100644 index 0000000..1badb4f Binary files /dev/null and b/docs/.gitbook/assets/image (83).png differ diff --git a/docs/.gitbook/assets/image (84).png b/docs/.gitbook/assets/image (84).png new file mode 100644 index 0000000..e1957fd Binary files /dev/null and b/docs/.gitbook/assets/image (84).png differ diff --git a/docs/.gitbook/assets/image (88).png b/docs/.gitbook/assets/image (88).png new file mode 100644 index 0000000..4deb859 Binary files /dev/null and b/docs/.gitbook/assets/image (88).png differ diff --git a/docs/.gitbook/assets/image (9) (1).png b/docs/.gitbook/assets/image (9) (1).png new file mode 100644 index 0000000..612c48b Binary files /dev/null and b/docs/.gitbook/assets/image (9) (1).png differ diff --git a/docs/.gitbook/assets/image (9).png b/docs/.gitbook/assets/image (9).png new file mode 100644 index 0000000..612c48b Binary files /dev/null and b/docs/.gitbook/assets/image (9).png differ diff --git a/docs/.gitbook/assets/image (90).png b/docs/.gitbook/assets/image (90).png new file mode 100644 index 0000000..ede6eed Binary files /dev/null and b/docs/.gitbook/assets/image (90).png differ diff --git a/docs/.gitbook/assets/image (92).png b/docs/.gitbook/assets/image (92).png new file mode 100644 index 0000000..a1e8e6d Binary files /dev/null and b/docs/.gitbook/assets/image (92).png differ diff --git a/docs/.gitbook/assets/image (93).png b/docs/.gitbook/assets/image (93).png new file mode 100644 index 0000000..88e799d Binary files /dev/null and b/docs/.gitbook/assets/image (93).png differ diff --git a/docs/.gitbook/assets/image (94).png b/docs/.gitbook/assets/image (94).png new file mode 100644 index 0000000..446be1a Binary files /dev/null and b/docs/.gitbook/assets/image (94).png differ diff --git a/docs/.gitbook/assets/image (95).png b/docs/.gitbook/assets/image (95).png new file mode 100644 index 0000000..ee49bd3 Binary files /dev/null and b/docs/.gitbook/assets/image (95).png differ diff --git a/docs/.gitbook/assets/image (97).png b/docs/.gitbook/assets/image (97).png new file mode 100644 index 0000000..3516478 Binary files /dev/null and b/docs/.gitbook/assets/image (97).png differ diff --git a/docs/.gitbook/assets/image (98).png b/docs/.gitbook/assets/image (98).png new file mode 100644 index 0000000..9242a81 Binary files /dev/null and b/docs/.gitbook/assets/image (98).png differ diff --git a/docs/.gitbook/assets/image.png b/docs/.gitbook/assets/image.png new file mode 100644 index 0000000..cb2ef79 Binary files /dev/null and b/docs/.gitbook/assets/image.png differ diff --git a/docs/.gitbook/assets/ls_wiki.png b/docs/.gitbook/assets/ls_wiki.png new file mode 100644 index 0000000..4bd5016 Binary files /dev/null and b/docs/.gitbook/assets/ls_wiki.png differ diff --git a/docs/.gitbook/assets/screen-shot-2020-03-12-at-3.31.31-pm.png b/docs/.gitbook/assets/screen-shot-2020-03-12-at-3.31.31-pm.png new file mode 100644 index 0000000..1e27a57 Binary files /dev/null and b/docs/.gitbook/assets/screen-shot-2020-03-12-at-3.31.31-pm.png differ diff --git a/docs/.gitbook/assets/screen-shot-2020-03-12-at-6.29.16-pm.png b/docs/.gitbook/assets/screen-shot-2020-03-12-at-6.29.16-pm.png new file mode 100644 index 0000000..a8a1561 Binary files /dev/null and b/docs/.gitbook/assets/screen-shot-2020-03-12-at-6.29.16-pm.png differ diff --git a/docs/.gitbook/assets/screen-shot-2020-03-12-at-6.33.10-pm.png b/docs/.gitbook/assets/screen-shot-2020-03-12-at-6.33.10-pm.png new file mode 100644 index 0000000..4cb254b Binary files /dev/null and b/docs/.gitbook/assets/screen-shot-2020-03-12-at-6.33.10-pm.png differ diff --git a/docs/.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1) (1).png b/docs/.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1) (1).png new file mode 100644 index 0000000..f07c146 Binary files /dev/null and b/docs/.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1) (1).png differ diff --git a/docs/.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1).png b/docs/.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1).png new file mode 100644 index 0000000..f07c146 Binary files /dev/null and b/docs/.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1).png differ diff --git a/docs/.gitbook/assets/screenshot.png b/docs/.gitbook/assets/screenshot.png new file mode 100644 index 0000000..f726679 Binary files /dev/null and b/docs/.gitbook/assets/screenshot.png differ diff --git a/docs/.gitbook/assets/standup.png b/docs/.gitbook/assets/standup.png new file mode 100644 index 0000000..c790b4f Binary files /dev/null and b/docs/.gitbook/assets/standup.png differ diff --git a/docs/.gitbook/assets/telework-policy-and-optional-self-certification-safety-checklist_fillable.pdf b/docs/.gitbook/assets/telework-policy-and-optional-self-certification-safety-checklist_fillable.pdf new file mode 100644 index 0000000..3a663cd Binary files /dev/null and b/docs/.gitbook/assets/telework-policy-and-optional-self-certification-safety-checklist_fillable.pdf differ diff --git a/docs/.gitbook/assets/telework_request_form_fillable.pdf b/docs/.gitbook/assets/telework_request_form_fillable.pdf new file mode 100644 index 0000000..bd99260 Binary files /dev/null and b/docs/.gitbook/assets/telework_request_form_fillable.pdf differ diff --git a/docs/.gitbook/assets/too_many_pages.png b/docs/.gitbook/assets/too_many_pages.png new file mode 100644 index 0000000..9db4e5b Binary files /dev/null and b/docs/.gitbook/assets/too_many_pages.png differ diff --git a/docs/README.md b/docs/README.md new file mode 100644 index 0000000..4aa747c --- /dev/null +++ b/docs/README.md @@ -0,0 +1,36 @@ +# About + +The [Data & Technology Services](https://austinmobility.io/) team at Austin Transportation and Public Works applies user-centered design, agile software delivery, and progressive civic tech values to build impactful solutions with Austin’s mobility planners, engineers, technicians, and staff. + +We use many modern tools and technologies to deliver solutions to our stakeholders. We build enterprise business systems using [Knack](https://www.knack.com/), a no-code workflow management service, and we also have a team of developers who build custom software when out-of-the-box doesn’t cut it. We embrace mature frameworks with an eye toward maintainability and long-term stability. We love [web mapping](https://austin.maps.arcgis.com/home/search.html?restrict=false\&sortField=relevance\&sortOrder=desc\&searchTerm=owner%3A%22ATD\_Publisher%22#content) and champion [open source](https://github.com/orgs/cityofaustin/repositories?language=\&q=atd\&sort=\&type=all) and [open data](https://data.austintexas.gov/browse?Ownership\_Department-name=Austin+Transportation\&q=transportation) across the City of Austin. + +![](.gitbook/assets/Mateo-Testing.jpeg) + +## Our Mission + +We leverage high-quality data and modern technologies to empower Austin Transportation staff to improve operations, make data-informed decisions, and deliver excellent mobility services to the Austin community. We solve real problems for real people. + +## How We Work + +_The principles that guide us as we carry out our work_ + +### Embrace Change + +Business needs change; technologies evolve. We welcome new challenges and improve by adapting to and embracing change. We are stubborn about our goals but flexible in our methods. + +### Users First and Always + +We build only what people need, nothing more. User needs are the driver for all decisions. We build with our users, keeping them involved in our process through ideation, sprint reviews, demos, and usability testing. + +### Empower Great People + +Our work empowers civil servants to discover and cultivate new skills. We aim to provide opportunities for personal and professional growth and to empower the public to engage with their government through open information and collaboration. + +### Default to Open + +The residents of Austin are at the top of our org chart. We share everything we do so that we can collaborate with the public and receive critical feedback. Before restricting access to a line of code, a dataset, a design brief, or an app, we ask, “Why?” + +### Nurture, Include, and Grow Together + +Delivering great tech cannot come at the cost of our wellbeing. We commit to building a safe and inclusive workplace by looking out for each other, listening to each other, and advocating for each other. + diff --git a/docs/SUMMARY.md b/docs/SUMMARY.md new file mode 100644 index 0000000..00624e3 --- /dev/null +++ b/docs/SUMMARY.md @@ -0,0 +1,52 @@ +# Table of contents + +* [About](README.md) +* [Essential Resources & Wikis](resource-index.md) +* [DTS Offices](dts-offices/README.md) + * [Where to Eat Near Cameron Rd](dts-offices/where-to-eat.md) + +## Basics + +* [Working at DTS Basics](basics/timesheets.md) +* [Network Access](basics/network-access.md) +* [Document Storage](basics/document-storage/README.md) + * [Using Google as a City Employee](basics/document-storage/using-google-as-a-city-employee.md) +* [Working Remotely from a Mac](basics/working-remotely-from-a-mac/README.md) + * [Resetting Your Network Password from a Mac](basics/working-remotely-from-a-mac/resetting-your-network-password-from-a-mac.md) + * [Troubleshooting AnyConnect for macOS Catalina](basics/working-remotely-from-a-mac/troubleshooting-anyconnect-for-macos-catalina.md) +* [Slack](basics/slack.md) + +## Onboarding + +* [Welcome to DTS](onboarding/welcome-to-dts.md) +* [Team Lead Checklist for New Employees](onboarding/new-employee-checklist.md) + +## Working at DTS + +## Off boarding + +* [Your Last Day](offboarding/your-last-day.md) +* [Offboarding Checklist](offboarding/off-boarding-checklist.md) + +## Product Ops + +* [Agile Project Management with Github + Zenhub](product-ops/github-project-management.md) +* [Project Delivery Workflow](product-ops/product-delivery-workflow.md) +* [Index Issue Specifications](product-ops/index-issue-specifications.md) +* [DTS Website Management](product-ops/dts-website.md) +* [Release Management Process](product-ops/release-management-process.md) +* [Product Manager Assignments](https://docs.google.com/spreadsheets/d/1BsOklJsJiIIqdlmtNtr9peL3URS7Hdu9RVj4D97701k/edit#gid=1907210355) + +## Developer + +* [Dockless-Mobility](developer/dockless-mobility.md) +* [Docker](developer/docker.md) +* [PostgREST](developer/postgrest/README.md) + * [Pypgrest (Python Client)](developer/postgrest/pypgrest.md) + * [Jobs-API](developer/postgrest/jobs-api.md) +* [Python](developer/python.md) +* [Server Operation](developer/server-operation.md) + +## APPLICATIONS + +* [Application Management](applications/application-management.md) diff --git a/docs/applications/application-management.md b/docs/applications/application-management.md new file mode 100644 index 0000000..79c3fa6 --- /dev/null +++ b/docs/applications/application-management.md @@ -0,0 +1,23 @@ +# Application Management + +We have an [Application Inventory](https://atd-dts.gitbook.io/atd-knack-operations/dts-portal/application-inventory) that we manage on our DTS Portal. This inventory list will show the various applications that our department uses and that we manage. + +Some of the main functions our team does is: + +* **Software Support** + * O365 (ex. SharePoint, Teams, Forms, Planner, Lists, etc..) + * Socrata Open Data Portal +* **Solution Architecture and Configuration** + * Knack, AMANDA, Fulcrum +* **Hardware Support** + * AirWatch - Tablet Management +* **Data Management** + * Database design, creation, maintenance +* **Business Intelligence (BI)** + * Power BI + * CliqSense + * Tableau +* **Service Desk** + * DTS Request forms - triage + * Wiki + * Slack Channel diff --git a/docs/basics/document-storage/README.md b/docs/basics/document-storage/README.md new file mode 100644 index 0000000..8274659 --- /dev/null +++ b/docs/basics/document-storage/README.md @@ -0,0 +1,40 @@ +--- +description: >- + We use our shared Google Drive for most of our work, but there are a few + exceptions. +--- + +# Document Storage + +## DTS Google Drive + +We love Google Drive, Docs, Sheets, and Slides for collaborative document editing and management. Since CTM does not have an enterprise Google subscription, we follow [these procedures](using-google-as-a-city-employee.md) carefully. + +Using Google within these parameters ensures we can fulfill PIRs, follow records-retention policies, and maintain access to employees' work when they leave the City. + +To prevent the proliferation of different versions of multi-editor documents, all collaborative documents are stored in a single location: + +* [Document templates](https://drive.google.com/open?id=1Txqc8xGkwa3h9lrRoXGzGjLlVo0S8DA6) +* ​[DTS Google Drive](https://drive.google.com/drive/folders/1fNmU-czryk5wJsn1gmb4WYUJJdut8Me7)​ - [​account setup](https://github.com/cityofaustin/atd-data-tech/wiki/Using-Google-as-a-City-employee)​​ + +## 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](https://coacd.org/dfs/ATD). + +## Everything Else + +Other documents can be stored in Google Drive or our G drive, whichever is most practical for the team and customer. + +{% hint style="info" %} +Be aware that anything stored on your local drive — the Windows C drive or Mac HD — is not backed up or accessible via other devices. +{% endhint %} + +## **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_](https://atd-dts.gitbook.io/wiki/on-boarding#vpn-and-remote-access)_._ 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` + +![](<../../.gitbook/assets/screen-shot-2020-07-29-at-12.38.07-pm (1) (1).png>) + diff --git a/docs/basics/document-storage/using-google-as-a-city-employee.md b/docs/basics/document-storage/using-google-as-a-city-employee.md new file mode 100644 index 0000000..e61f225 --- /dev/null +++ b/docs/basics/document-storage/using-google-as-a-city-employee.md @@ -0,0 +1,25 @@ +# Using Google as a City Employee + +Using Google within these parameters ensures we comply with CTM's security protocols. We can fulfill PIRs, follow records-retention policies, and maintain access to employees' work when they leave the City. + +## Account creation + +Employees should not use personal Google accounts for City work since all City-related email correspondence must reside in Office 365. So you will need to create a Google account with your `@austintexas.gov` email address that is **not attached to a Gmail account**: + +1. Visit [Create your Google Account](https://accounts.google.com/signup/v2/webcreateaccount?continue=https%3A%2F%2Faccounts.google.com%2FManageAccount\&gmb=exp\&biz=false\&flowName=GlifWebSignIn\&flowEntry=SignUp). + +

Screenshot of Google account creation page with "Use my current email address instead" link circled

+2. Click "Use my current email address instead." +3. Enter your `@austintexas.gov` email address. +4. Check your email, including your junk/spam folder, and confirm your account. + +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](https://www.fbi.gov/services/cjis/cjis-security-policy-resource-center) and [HIPAA](https://www.hhs.gov/hipaa/for-professionals/security/laws-regulations/index.html) data, along with any personally identifiable information about individuals in the community. + diff --git a/docs/basics/network-access.md b/docs/basics/network-access.md new file mode 100644 index 0000000..7321b70 --- /dev/null +++ b/docs/basics/network-access.md @@ -0,0 +1,18 @@ +# Network Access + +### Wifi + +Cameron Road: `coa-atd-secure-wifi` — password in 1password + +### VPN & Remote Access + +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](https://drive.google.com/file/d/1YJFvFCGJIbXhgnl\_omWwTGQR2dpmMyAo/view?usp=sharing) + * [Instructions for installing and configuring to work in OSX Catalina](https://docs.google.com/document/d/1\_RoFPflbpzvWOuSq7g2WbNidgPkbWdTmIoa4Fftf94Q/edit) +* CTM Help Desk [Remote Access Request Form](https://apps.austintexas.gov/helpdesk/remote/) + +### 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. diff --git a/docs/basics/slack.md b/docs/basics/slack.md new file mode 100644 index 0000000..e72ef6c --- /dev/null +++ b/docs/basics/slack.md @@ -0,0 +1,25 @@ +# Slack + +We use Slack to stay in touch with our teammates. Your supervisor will provide you with an invitation to the [City of Austin Slack](https://austininnovation.slack.com/signup). + +Please join Austin Transportation channels, prepended with `atd.` These include: + +* **atd** +* **atd-data-tech** - open to all City employees, default for team discussions +* **atd-data-tech-real-talk** - private channel for sensitive information/conversations or those completely irrelevant to anyone else, e.g. "Turn in your timesheets" +* **atd-dev​** +* **atd-product​** +* **atd-standup** - everyone on the DTS team posts a daily standup here + +## Daily Stand Up + +We keep each other up to date on our progress and blockers by posting in [#atd-standup](https://app.slack.com/client/T04KZA1MB/CHXHA8YAU) 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. + +![](../.gitbook/assets/standup.png) + diff --git a/docs/basics/timesheets.md b/docs/basics/timesheets.md new file mode 100644 index 0000000..d5c323c --- /dev/null +++ b/docs/basics/timesheets.md @@ -0,0 +1,51 @@ +# Working at DTS Basics + +### Municipal Civil Service + +The [Municipal Civil Service (MCS) ](https://www.austintexas.gov/department/municipal-civil-service-rules)rules govern the process for employee hiring, promotions, lateral transfers, reduction-in-force, disciplinary actions, and appeals. If any supplemental information included here conflicts with the official MCS rules, those rules take precedence. + +### Work Schedule + +[Official City of Austin holiday schedule](http://www.austintexas.gov/department/official-city-holidays) + +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) + +{% hint style="info" %} +You'll have to fill out a paper timesheet during your first two weeks. Your supervisor will help you get one from HR. +{% endhint %} + +\ +​[E-Timesheet Training (On-Network)](https://sites.google.com/site/pwuclass/etimekeeping)​ + +* Part 1: [eTimekeeping](https://www4.austintexas.gov/eTimekeeping12b-01)​ +* Part 2: [Task Orders](https://www4.austintexas.gov/eTimekeeping12b-02)​ +* Part 3: [Leave Requests](https://www4.austintexas.gov/eTimekeeping12b-03)​ +* Part 4: [Overtime Requests](https://www4.austintexas.gov/eTimekeeping12b-04)​ +* Part 5: [Deadlines and Tests](https://www4.austintexas.gov/eTimekeeping12b-05) + +Your timesheet must be submitted in the [eTimesheet](https://pwdweb.austintexas.gov/timesheet/pwd.cfm) system every Thursday by 10am. + +Learn how to submit your timesheet with the [E-Timesheet Training Guide](http://coaspweb1/sites/PWD/PWU/SitePages/ATDLearn.aspx) (on-network) and [timesheet code](https://cityofaustin.sharepoint.com/sites/ATD/Administration/SitePages/Earn%20Codes.aspx) reference. + diff --git a/docs/basics/working-remotely-from-a-mac/README.md b/docs/basics/working-remotely-from-a-mac/README.md new file mode 100644 index 0000000..bd87db4 --- /dev/null +++ b/docs/basics/working-remotely-from-a-mac/README.md @@ -0,0 +1,88 @@ +--- +description: >- + There are a few special procedures and applications for City of Austin staff + who want to work remotely using a Mac. +--- + +# Working Remotely from a Mac + +## Antivirus Software + +Per the [City of Austin Anti-Virus Policy](https://cityofaustin.sharepoint.com/sites/COATeleworkInstructions/Shared%20Documents/Forms/AllItems.aspx?id=%2Fsites%2FCOATeleworkInstructions%2FShared%20Documents%2FCOA%20Anti%20Virus%20Policy%2Epdf\&parent=%2Fsites%2FCOATeleworkInstructions%2FShared%20Documents\&p=true\&originalPath=aHR0cHM6Ly9jaXR5b2ZhdXN0aW4uc2hhcmVwb2ludC5jb20vOmI6L3MvQ09BVGVsZXdvcmtJbnN0cnVjdGlvbnMvRWMxelktZ2JZcDFFbWFVQzNXeWhSQWdCOWwzZ2R4M2ZGaHhFTVhlajlJWG1oUT9ydGltZT1McElKQXFUUjEwZw), all City-owned computers must have up-to-date virus protection installed and active. + +The TrendMicro website has Mac installers and installation instructions [here](https://esupport.trendmicro.com/en-us/home/pages/technical-support/antivirus-for-mac/1060983.aspx). You will need the serial number in CTM's [_Anti-Virus for Non-COA Computers_](https://cityofaustin.sharepoint.com/sites/COATeleworkInstructions/Shared%20Documents/Anti-Virus%20for%20Non%20COA%20Computers.pdf) doc. + +## Network Access with 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 AnyConnect to connect to the City's Virtual Private Network (VPN) when working remotely. + +### Installing AnyConnect + +1\. Download the installer [here](https://drive.google.com/drive/u/0/folders/114rRG9OvTCWTXYqVg-AHaZgnrv\_PCvEE). + +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 AnyConnect Secure Mobility Client** to open the application. + +{% hint style="info" %} +If you are running OSX Catalina, you may need to [take another step](broken-reference) to complete the configuration. +{% endhint %} + +### Using AnyConnect + +1\. Open the application. In the empty field below "Ready to Connect," enter the IP address of the City's VPN server. + +{% hint style="info" %} +The IP address is sensitive information. Get it directly from your supervisor or another Mac user. +{% endhint %} + +2\. Click the "Connect" button. + +![](../../.gitbook/assets/2.png) + +2\. A warning will appear. Do _**not**_ check the "Always trust..." option and click "Connect Anyway." + +![](../../.gitbook/assets/3.webp) + +3\. A window asking for your username and password will appear. Use your City of Austin email address and Network password to log in. + +![](<../../.gitbook/assets/4 (1).png>) + +4\. The same window may reappear, just for fun. 🙃 Again, click "Connect Anyway" and leave the "Always trust..." option unchecked. + +At this point, there may be a bit of a hang while the connection is made. Once the green checkbox appears, you are connected and ready to access network resources. + +![](../../.gitbook/assets/AnyConnect-Connected.png) + +{% hint style="info" %} +Streaming video or audio while connected to the City network will negatively impact the speed with which other employees can access shared drives, SharePoint, and the City’s intranet. +{% endhint %} + +### 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](./#using-anyconnect). + +1\. From the Finder menu, select **Go** > **Connect to Server.** + +![](../../.gitbook/assets/6.png) + +2\. Enter `smb://coacd.org/dfs/ATD` in the **Server Address** field and click "Connect." + +![](../../.gitbook/assets/7.png) + +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. + + + diff --git a/docs/basics/working-remotely-from-a-mac/resetting-your-network-password-from-a-mac.md b/docs/basics/working-remotely-from-a-mac/resetting-your-network-password-from-a-mac.md new file mode 100644 index 0000000..157df9d --- /dev/null +++ b/docs/basics/working-remotely-from-a-mac/resetting-your-network-password-from-a-mac.md @@ -0,0 +1,24 @@ +--- +description: >- + Learn how to reset your City of Austin Network password remotely from a Mac + using Citrix AnyConnect. +--- + +# Resetting Your Network Password from a Mac + +1. **Get set up with a PC assigned to your Citrix profile.** You may have to contact Scott Reedy for assistance with this step, but you'll need a PC assigned to your Citrix profile. +2. Connect to the VPN [via Cisco AnyConnect](./#using-anyconnect). +3. Log in to [Citrix Store Front](https://coastore.austintexas.gov/Citrix/COASTOREWeb/) using your CoA username and password.\ + **URL:** [https://coastore.austintexas.gov/Citrix/COASTOREWeb/](https://coastore.austintexas.gov/Citrix/COASTOREWeb/)\ + **Username:** `coacd\` + your last name and first initial. Ex: coacd\clarkem\ + **Password:** your CoA Network password (same as Outlook) +4. Click the Settings ⚙️ icon in the top right, then "Account Settings." + +
+ +5. Click "Change password." + +
+ +6. Fill out the Change Password form and click "OK." +7. Once you change your password in Citrix, **immediately log out of AnyConnect.** It is possible to lock yourself out because you are logged into AnyConnect with the old password at that time. You can reach out to Scott Reedy to unlock you if that happens. diff --git a/docs/basics/working-remotely-from-a-mac/troubleshooting-anyconnect-for-macos-catalina.md b/docs/basics/working-remotely-from-a-mac/troubleshooting-anyconnect-for-macos-catalina.md new file mode 100644 index 0000000..15d1103 --- /dev/null +++ b/docs/basics/working-remotely-from-a-mac/troubleshooting-anyconnect-for-macos-catalina.md @@ -0,0 +1,24 @@ +--- +description: If you come across that one bug. +--- + +# Troubleshooting AnyConnect for macOS Catalina + +1\. In Finder, open **Applications/Utilities** and open Terminal. + +Type `cd /opt/cisco/AnyConnect` and press **Enter**. + +2\. Type `cd /opt/cisco/AnyConnect` and press **Enter**. + +3\. Type `sudo nano AnyConnectLocalPolicy.xml` and press **Enter**. + +4\. Type your admin password (the one you use to log on to your computer) and press **Enter.** + +
+ +5\. Change the highlighted text from `false` to `true`. + +
+ +6\. Press **ctrl+x** to exit.\ +7\. Press **Y** to save changes when prompted. diff --git a/docs/developer/docker.md b/docs/developer/docker.md new file mode 100644 index 0000000..9629ac0 --- /dev/null +++ b/docs/developer/docker.md @@ -0,0 +1,62 @@ +# Docker + +We use [Docker](http://docker.com) to manage runtime environments. Our Docker Hub is [https://hub.docker.com/u/atddocker](https://hub.docker.com/u/atddocker). + +## Useful Commands + +Start docker engine + +```text +sudo systemctl start docker +``` + +View all images + +```text +sudo docker images +``` + +Show running containers + +```text +sudo docker ps +``` + +Show all containers + +```text +sudo docker ps -a +``` + +Build image from Dockerfile + +```text +docker build --no-cache -t my-docker-image-name . +``` + +Run docker container in interactive mode and mount local volume inside container: + +```text +sudo docker run -it -v /home/liangz:/app --rm -w /app/transportation-data-deploy atddocker/tdp bash +``` + +Start docker with [docker-compose](https://docs.docker.com/compose/): + +```text +sudo `which docker-compose` restart +``` + +## 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`: + +```bash +docker build --no-cache -t atddocker/my-image:2.0.1 . +``` + +1. Push to Docker Hub: + +```bash +docker push atddocker/my-image +``` + diff --git a/docs/developer/dockless-mobility.md b/docs/developer/dockless-mobility.md new file mode 100644 index 0000000..0dae8fe --- /dev/null +++ b/docs/developer/dockless-mobility.md @@ -0,0 +1,75 @@ +# Dockless-Mobility + +This page contains technical details related to our management of dockless mobility data \(e-scooters, bicycles, etc\). + +## Mobility Data Specification \(MDS\) + +We require dockless mobility operators to provide us with real-time trip reporting feeds in compliance with the [mobility data specification](https://github.com/CityOfLosAngeles/mobility-data-specification). + +## Data Capture + +We collect dockless trip records from each provider using a [Python mds client](dockless-mobility.md) which stores processed data in a [Postgrest](http://postgrest.org) database. + +* [transportation-dockless-processing](https://github.com/cityofaustin/transportation-dockless-processing) +* [MDS Provider Client](https://github.com/cityofaustin/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](https://data.austintexas.gov/Transportation-and-Mobility/Dockless-Vehicle-Trips/7d8e-dm7r/). + +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](https://datasmart.ash.harvard.edu/news/article/civic-analytics-network-dockless-mobility-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](http://transportation.austintexas.io/dockless-data/) + +This is a public website that pulls directly from our public datasets. [Here's the source code](https://github.com/cityofaustin/transportation-datahub). + +## 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](http://dockless.austintexas.io). + +## Open Source + +The source code for our dockless mobility tools is freely available in five repositories \(and counting\): + +* [Dockless Data Processing](https://github.com/cityofaustin/transportation-dockless-processing) +* [Transportation Datahub](https://github.com/cityofaustin/transportation-datahub) +* [Dockless API](https://github.com/cityofaustin/transportation-dockless-api) +* [Dockless Dataviz](https://github.com/cityofaustin/transportation-dockless-dataviz) +* [MDS Provider Client](https://github.com/cityofaustin/mds-provider-client) + +## Reporting Queries + +Here are some handy queries for fetching dockless data summaries from the [Open Data Portal](http://data.austintexas.gov) + +### Scooter and Bike trips by Month/Year\* + +```text +https://data.austintexas.gov/resource/7d8e-dm7r.json?$query=select avg(trip_duration)/60 as avg_duration_minutes, sum(trip_distance) * 0.000621371 as total_miles, avg(trip_distance) * 0.000621371 as avg_miles, count(trip_id) as total_trips, date_extract_m(start_time) as month, date_extract_y(start_time) as year where trip_distance * 0.000621371 >= 0.1 and trip_distance * 0.000621371 < 500 and trip_duration < 86400 group by year, month +``` + +### Dockless Trips by vehicle type and month/year\* + +```text +https://data.austintexas.gov/resource/7d8e-dm7r.json?$query=select vehicle_type, avg(trip_duration)/60 as avg_duration_minutes, sum(trip_distance) * 0.000621371 as total_miles, avg(trip_distance) * 0.000621371 as avg_miles, count(trip_id) as total_trips, date_extract_m(start_time) as month, date_extract_y(start_time) as year where trip_distance * 0.000621371 >= 0.1 and trip_distance * 0.000621371 < 500 and trip_duration < 86400 group by vehicle_type, year, month +``` + +\*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` + +```text +https://data.austintexas.gov/resource/7d8e-dm7r.json?$query=select vehicle_type, avg(trip_duration)/60 as avg_duration_minutes, sum(trip_distance) * 0.000621371 as total_miles, avg(trip_distance) * 0.000621371 as avg_miles, count(trip_id) as total_trips, date_trunc_ymd(start_time) as date_ where trip_distance * 0.000621371 >= 0.1 and trip_distance * 0.000621371 < 500 and trip_duration < 86400 and date_extract_m(start_time) in (2, 3) and date_extract_y(start_time) = 2019 group by vehicle_type, date_trunc_ymd(start_time) +``` + diff --git a/docs/developer/postgrest/README.md b/docs/developer/postgrest/README.md new file mode 100644 index 0000000..10f723a --- /dev/null +++ b/docs/developer/postgrest/README.md @@ -0,0 +1,9 @@ +# PostgREST + +We use [PostgREST](https://github.com/PostgREST/postgrest) to generate APIs for our PostgreSQL databases. + +* [Waze CCP Feed Incident Archive](https://github.com/cityofaustin/atd-data-waze-archive) +* [Job History](https://github.com/cityofaustin/atd-data-tech/wiki/PostgREST%3A-Jobs-API) +* [Micromobility Data](https://github.com/cityofaustin/atd-dockless-processing) +* \[CoA Public Safety Traffic Incident Reports\)\[[https://data.austintexas.gov/Transportation-and-Mobility/Real-Time-Traffic-Incident-Reports/dx9v-zd7x](https://data.austintexas.gov/Transportation-and-Mobility/Real-Time-Traffic-Incident-Reports/dx9v-zd7x)\] + diff --git a/docs/developer/postgrest/jobs-api.md b/docs/developer/postgrest/jobs-api.md new file mode 100644 index 0000000..1bd124b --- /dev/null +++ b/docs/developer/postgrest/jobs-api.md @@ -0,0 +1,111 @@ +# Jobs-API + +The Jobs API is a tool for logging the outcome of ETL scripting jobs. It is designed to support the task of "incremental" data loads—i.e., loading only new or updated records from a source database to a destination database. + +The typical ETL workflow using the Job API is: + +1. At the beginning of your ETL job, query the Job API to retrieve the timestamp of the last time your job ran successfully. +2. Use this timestamp as a temporal filter to extract new/modifed records from the source database. +3. At the completion of your ETL job, register the successful outcome with the Job API. + +## Querying the API + +The test instance is available at [http://transportation-data-test.austintexas.io/jobs](http://transportation-data-test.austintexas.io/jobs), and it can be queried using any PostGREST route, as described in the [PostgREST documentation](http://postgrest.org/en/v5.0/api.html). + +## Field Definitions: + +| Fieldname | Field Type | Description | +| :--- | :--- | :--- | +| `id` | SERIAL PRIMARY KEY | System-generated incremental ID | +| `name` | TEXT NOT NULL | Name descriptor of the job which uniquely identifies the ETL job | +| `start_date` | TIMESTAMP WITH TIME ZONE NOT NULL | The job's start datetime | +| `end_date` | TIMESTAMP WITH TIME ZONE | The job's end datetime | +| `message` | TEXT | Optional message | +| `status` | TEXT NOT NULL | The status of the ETL job. Use 'in\_progress', 'success', or 'error' | +| `records_processed` | INTEGER | The number of records processed by the job. | +| `source` | TEXT NOT NULL | The name source database of the ETL job. | +| `destination` | TEXT NOT NULL | The name of the destination database of the ETL job | + +## Python Example + +We've written a Python utility to interact with the jobs interface. It's included in our [transportation-data-utils \(tdutils\)](http://github.com/cityofaustin/transportation-data-utils) 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: + +```python +>>> from tdutils import jobutil + +>>> job = jobutil.Job( + name='my_etl_job', + url='http://transportation-data-test.austintexas.io/jobs', + source='inventory_system', + destination='data_warehouse', + auth='secret-json-web-token-issued-by-admin') +``` + +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: + +```python +>>> job.most_recent() +1529252405 +# 2018-06-17T16:20:05+00:00 +``` + +Register your new job with `job.start()`. The API returns a JSON representation of newly created job record: + +```python +>>> job.start() + +{'destination': 'data_warehouse', + 'end_date': None, + 'id': 31801, + 'message': None, + 'name': 'my_etl_job', + 'records_processed': None, + 'source': 'inventory_system', + 'start_date': '2018-06-17T17:18:53+00:00', + 'status': 'in_progress'} +``` + +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`: + +```python +>>> job.most_recent() +1529252405 +# 2018-06-17T16:20:05+00:00 +``` + +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: + +```python +>>> job.result('success', records_processed=503) # records_processed is optional, but preferred + +{'destination': 'data_warehouse', + 'end_date': '2018-06-17T17:35:08+00:00', + 'id': 31801, + 'message': None, + 'name': 'my_etl_job', + 'records_processed': 503, + 'source': 'inventory_system', + 'start_date': '2018-06-17T17:18:53+00:00', + 'status': 'success'} +``` + +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: + +```python +>>> job.most_recent() +1529256005 +# 2018-06-17T17:18:53+00:00' +``` + +You should also register job failures. The `errror` result is availabe for such purposes: + +```python +try: + # do ETL stuff + +except psycopg2.DatabaseError as e: + job.result('error', records_processed=0, message='A database error occured.') +``` + diff --git a/docs/developer/postgrest/pypgrest.md b/docs/developer/postgrest/pypgrest.md new file mode 100644 index 0000000..501bbe5 --- /dev/null +++ b/docs/developer/postgrest/pypgrest.md @@ -0,0 +1,4 @@ +# Pypgrest \(Python Client\) + +We've created a Python client, [Pypgrest](https://github.com/cityofaustin/pypgrest), for interacting with the Postgrest API. + diff --git a/docs/developer/python.md b/docs/developer/python.md new file mode 100644 index 0000000..d17564b --- /dev/null +++ b/docs/developer/python.md @@ -0,0 +1,35 @@ +# Python + +## Install package in editable mode + +From parent directory of package: + +```bash +$ pip install -e +``` + +## Updating and Publishing Packages to PyPi: + +See [Packaging Python Projects \(`python.org`\)](https://packaging.python.org/tutorials/packaging-projects/) + +1. Your python envrionment will require the following pacakges: + + ```text + python=3 + setuptools + twine + ``` + +2. Update the [semantic version](https://semver.org/) number in the package's `setup.py`. +3. From the same directory as `setup.py` build the new version: + + ```bash + $ python setup.py bdist_wheel --universal + ``` + +4. Upload the new version to [PyPi](http://pypi.org). \(You'll be prompted to enter your username/password\): + + ```bash + $ twine upload dist/* + ``` + diff --git a/docs/developer/server-operation.md b/docs/developer/server-operation.md new file mode 100644 index 0000000..ddfe175 --- /dev/null +++ b/docs/developer/server-operation.md @@ -0,0 +1,78 @@ +# Server Operation + +## Script Management + +### [Data Publication Log](http://transportation.austintexas.io/publisher/) shows an active job status log. + +It's very important that the job server keeps from timing out. + +### [knack-proxy](https://github.com/cityofaustin/knack-proxy) is a flask app. + +This app takes 311 service requests from CTM ESB \(Enterprise Service Bus\). It acts as proxy for the Knack API since certificates don't work with ESB 🤷‍♂. + +⚠️ If it goes down it will break the 311 integration with the data tracker which our TMC \(Traffic Management Center\) relies on. The flask app has never had issues \(_knocks on wood_\) but sometimes the ESB to proxy integration goes down. CTM handles the reboot. In this case, the TMC will say that they aren't getting updated Service Requests in data tracker. Omar at CTM is the person to talk to if ESB is having errors. + +Data path: 311 SRs \(Motorola\) -> Enterprise Service Bus \(CTM\) -> knack-proxy \(ATD\) -> Knack \(ATD instance\) + +### [cctv-service](https://github.com/cityofaustin/atd-cctv-service/) is a sanic app. + +Since we converted this code into an async [Sanic](https://github.com/huge-success/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: + + ```bash + $ df -h + ``` + +2. Check the free available space in the Volume group + + ```bash + $ vgdisplay /dev/mapper/root_vg + ``` + +3. Extend the volume \(here, adding 8GB\) + + ```bash + $ lvextend -L +8G /dev/mapper/root_vg-var_lv + ``` + +4. Expand the volume: + + ```bash + $ sudo xfs_growfs /dev/mapper/root_vg-var_lv + ``` + +5. All done. + +### Miscellaneous: + +run all shell scripts inside a folder + +```text +for shfile in *.sh; do sudo bash ./$shfile; done +``` + +scp transfer files from local to remote directory: + +```text +scp /Users/ZWL/Documents/GitHub/transportation-data-publishing/transportation-data-publishing/config/secrets.py liangz@atdatmsscript:transportation-data-publishing/transportation-data-publishing/config/ +``` + +### Amazon AWS + +connect to instance + +```text +ssh -i "" ec2-user@ +``` + diff --git a/docs/dts-offices/README.md b/docs/dts-offices/README.md new file mode 100644 index 0000000..f05f654 --- /dev/null +++ b/docs/dts-offices/README.md @@ -0,0 +1,22 @@ +# DTS Offices + +## 8700 Cameron Road + +_Aka "8700", "Cameron"_ + +Data & Technology Services is located at Transportation Public Works' Cameron Road location. Our offices are in 8700 Cameron Road, alongside Arterial Management offices and the Mobility Management Center. + +## Barton Oaks + +## Bergstrom Tech + +## DTS Hoteling + +### Ben White + +### Permitting and Development Center + + + + + diff --git a/docs/dts-offices/where-to-eat.md b/docs/dts-offices/where-to-eat.md new file mode 100644 index 0000000..9512b65 --- /dev/null +++ b/docs/dts-offices/where-to-eat.md @@ -0,0 +1,12 @@ +# Where to Eat Near Cameron Rd + + + +The Data & Technology Services office is at [8700 Cameron Road, Austin TX](https://goo.gl/maps/GSKtFEHpx585fJkN6). + +## Nearby Lunch Options + +We have [a map for that](https://www.google.com/maps/d/u/0/viewer?mid=1OFKA1JVEpysc7Kh2lbPPx\_moMzEPGhBJ\&ll=30.34970295660435%2C-97.69603670420717\&z=12). 🙂 + +![](<../.gitbook/assets/image (7).png>) + diff --git a/docs/offboarding/off-boarding-checklist.md b/docs/offboarding/off-boarding-checklist.md new file mode 100644 index 0000000..2c9d288 --- /dev/null +++ b/docs/offboarding/off-boarding-checklist.md @@ -0,0 +1,49 @@ +# Offboarding Checklist + +## IT Permissions and Access + +| To Do | Notes | +| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- | -------------------------------------------- | +| [1Password](https://my.1password.com/people) | Amenity, Chia, Diana, or Frank must complete | +| [Slack](https://austininnovation.slack.com/admin/settings) | | +| [Miro](https://miro.com/app/settings/company/3074457355174023970/users/) | Amenity or Diana must complete | +| Vision Zero Editor | | +| Moped | | +| Knack Applications | Apps Team member must complete | +| [Transportation GitHub organization](https://github.com/orgs/cityofaustin/teams/transportation/members) | | +| Reassign [open Github issues](https://github.com/cityofaustin/atd-data-tech/issues) | | +| [Zenhub](https://app.zenhub.com/settings/o/cityofaustin/users) | | +| Google Drive | | +| Fill out [Separated Employee Request Form (SERF)](https://atx.servicenowservices.com/sp?id=sc\_category\&sys\_id=9ab907eedb596f80c56254f9489619df\&catalog\_id=e0d08b13c3330100c8b837659bba8fb4) | Supervisor must complete | +| DTS email distribution list | Remove after SERF is processed | +| [About Us page](https://github.com/cityofaustin/atd-product/blob/main/pages/about/index.js) | | +| [DTS Team Slide](https://docs.google.com/presentation/d/1tHKTfUgQ-uAXdRBkEdXqR7ryBo\_LTU86IzQxo1gJoeA/edit#slide=id.gc64f254bde\_0\_91) | | +| [DTS Orientation Slides](https://docs.google.com/presentation/d/1ByRWXmjHut88cTiPVOTgkwTJ2V5\_m1Y\_0j46FP\_kdYw/edit#slide=id.gfd25a7f266\_1\_382) | | +| [DTS Knowledge Base triage information](https://app.gitbook.com/o/-LzDQOVGhTudbKRDGpUA/s/-M4LYhVrPWLmbRD1Xv0p/) | | + +## Recover organization assets + +Review Equipment Checkout form submitted + +| Name | Type | +| ------------------------ | ---------------- | +| Badge access | General access | +| Parking sticker | General access | +| Laptop | Hardware | +| Docking station | Hardware | +| Monitors (if applicable) | Hardware | +| Desk riser | Office equipment | +| Chair | Office equipment | + +## 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 diff --git a/docs/offboarding/your-last-day.md b/docs/offboarding/your-last-day.md new file mode 100644 index 0000000..48d61a5 --- /dev/null +++ b/docs/offboarding/your-last-day.md @@ -0,0 +1,5 @@ +# Your Last Day + +1. Complete exit interview +2. Turn in all hardware issued from Austin Transportation back to IT Hardware DTS Staff +3. diff --git a/docs/onboarding/new-employee-checklist.md b/docs/onboarding/new-employee-checklist.md new file mode 100644 index 0000000..6d3d8a6 --- /dev/null +++ b/docs/onboarding/new-employee-checklist.md @@ -0,0 +1,77 @@ +# Team Lead Checklist for New Employees + +{% hint style="info" %} +Team leads are responsible for tracking new team members' onboarding in Github: + +Create an epic "Onboard \[Name]" with two issues: + +* "Perform \[Name] onboarding tasks \[Team Lead]," assigned to yourself and the new team member's supervisor—i.e. the person who will sign their timesheets. Copy and paste the checklist from this page into the issue body. +* "Perform DTS onboarding tasks \[\[Name]]." You won't be able to assign this to the new team member until they have a Github username, but in the meantime you can direct them to the [Welcome to DTS](welcome-to-dts.md) Gitbook page. Copy and paste the checklist from that page into the issue body. +{% endhint %} + +## **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** + +### **Regular and Temporary Employees** + +* [ ] Submit a [CTM New Employee Request Form](https://atx.servicenowservices.com/sp?id=sc\_cat\_item\_guide\&sys\_id=b714eb12db7a3f0021ccef92ca961972) for a COA network account, eAccess PIN/HR Portal, and phone. \ + \ + Under "Network Account Information," write `Shared mailbox: transportation.data@austintexas.gov; Distribution lists: ATDDataTechnologyServices@austintexas.gov and TPWEmployees@austintexas.gov`. + +### **Contractors** + +* [ ] Submit a [Third-Party Remote Access Request Form](https://atx.servicenowservices.com/sp?id=sc\_cat\_item\&sys\_id=30f9aa09dba4a8106d0171f2399619a2) instead of a NERF. See [this guide ](https://cityofaustin.sharepoint.com/sites/ServiceNowFullfillerLearningResources/Final%20Quick%20Reference%20Guides/KB0011192.pdf)for more info. \ + \ + This will require the vendor to sign a third-party remote access acceptable use agreement. Find the latest version of the agreement form embedded in the service now request. This must be submitted with the ServiceNow request. + +## 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](https://my.1password.com/people). +* [ ] Ask Amenity or Diana to add the new team member to [City of Austin Slack](https://austininnovation.slack.com/admin). +* [ ] 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 [agenda for the next team meeting](https://docs.google.com/document/d/1s8rl928FM0fKPEvsgkVSmkUghPgUmEgMEhZr4bmsJWc/edit). +* [ ] 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. + +After they've created their Google and Github accounts: + +* [ ] Share the [DTS Google Drive](https://drive.google.com/drive/u/0/folders/1fNmU-czryk5wJsn1gmb4WYUJJdut8Me7) with the new team member. +* [ ] Add the new team member to the City of Austin [Transportation Github team](https://github.com/orgs/cityofaustin/teams/transportation/members). This should automatically add them to the [City of Austin Github organization](https://github.com/orgs/cityofaustin/people). +* [ ] Invite the new team member to the [City of Austin Zenhub organization](https://app.zenhub.com/settings/o/cityofaustin/users). +* [ ] Add the new team member to [Gitbook](https://app.gitbook.com/@atd-dts/spaces). + +Once they've uploaded their [headshot](https://drive.google.com/drive/folders/1y\_yhkZQE5uSRhLZAHJn2kFuXPBixVJ2G): + +* [ ] Add them to the [DTS Orientation presentation team slide](https://docs.google.com/presentation/d/1ByRWXmjHut88cTiPVOTgkwTJ2V5\_m1Y\_0j46FP\_kdYw/edit#slide=id.gfd25a7f266\_1\_173) and the slide for the team they are joining. +* [ ] [Open an issue](https://github.com/cityofaustin/atd-data-tech/issues/new) to add the team member to the team website. The issue should include link to the headshot, new employee's title for the site and pronouns. Assign the issue to Chia. + + Once they've received notice from CTM that their Miro account was created: + +* [ ] Add them to [the Austin Transportation Miro Team](https://miro.com/app/settings/team/3074457347846964301/users/). + +Once HR has added them to the UKG timekeeping system, their supervisor—Peggy, Amenity, or Diana— must: + +* [ ] Set up their schedule plan. + + + +
+ + + + + +
+ +\ diff --git a/docs/onboarding/welcome-to-dts.md b/docs/onboarding/welcome-to-dts.md new file mode 100644 index 0000000..898d14f --- /dev/null +++ b/docs/onboarding/welcome-to-dts.md @@ -0,0 +1,65 @@ +--- +description: >- + We are so happy to have you here. Let's configure some tools and ensure you + have access to all the resources needed to hit the ground running. 💪👟⚡ +--- + +# Welcome to DTS + +## Day 1 🐣 + +These are the high priority tasks. Let your supervisor know if you have any issues completing them on your first day. + +* [ ] [Log in to your City of Austin email](https://outlook.office365.com/). +* [ ] [Install the Microsoft Authenticator app](https://atx.servicenowservices.com/sp?id=kb\_article\&sys\_id=b46a964d1b5a35d0e8dfc844604bcb01) on your phone. Moving forward, you should only log in to City of Austin Microsoft services via 2 factor authentication. +* [ ] You should have a 1Password invitation in your email. If not, email/Slack Diana to request one and then accept the invitation. Diana or Amenity will then confirm your account. Then follow [this guide](https://support.1password.com/explore/get-started/) to set up 1Password for use on your City computer and any mobile devices you use for work. + +{% hint style="danger" %} +All your passwords relating to work should be stored 1Password and _only_ in 1Password. +{% endhint %} + +* [ ] If you don't have one already, [create a Github account](https://github.com/join) with your CoA email and then ask Amenity or Frank to add you to the City of Austin [Transportation Github Team](https://github.com/orgs/cityofaustin/teams/transportation/members). +* [ ] Enable [two-factor authentication for your Github account](https://docs.github.com/en/authentication/securing-your-account-with-two-factor-authentication-2fa). +* [ ] Install Slack desktop client — [Windows](https://slack.com/downloads/windows) | [Mac](https://slack.com/downloads/mac). +* [ ] [Set up your email signature](https://docs.google.com/document/d/1OAoBll9rIl6XZq2uOShm5HCbHJboOt0SLP\_wK6tjkEE/edit). +* [ ] [Update your Slack profile](https://slack.com/help/articles/204092246-Edit-your-profile) with a photo and your title. +* [ ] Post your [daily standup in Slack](https://atd-dts.gitbook.io/wiki/slack#daily-stand-up). +* [ ] [Create a Google account for your austintexas.gov email address](../basics/document-storage/using-google-as-a-city-employee.md) and verify that you have access to the [DTS Google Drive](https://drive.google.com/drive/u/0/folders/1fNmU-czryk5wJsn1gmb4WYUJJdut8Me7). + +## Week 1 🐥 + +Let your supervisor know if you are not able to finish any of these during your first week. + +* [ ] [Set yourself up for remote work](https://atd-dts.gitbook.io/atd-staff-resources/working-remotely/getting-started). +* [ ] [Set up Cameron Road printer](https://app.gitbook.com/@atd-dts/s/dts-service-desk-knowledge-base/onboarding/printer-information). +* [ ] Set up docking station — [Windows](https://www.dell.com/support/home/us/en/04/product-support/product/dell-universal-dock-d6000/drivers) | [Mac](https://www.synaptics.com/products/displaylink-graphics/downloads/macos). (See [here](https://support.displaylink.com/knowledgebase/articles/1188004-macos-10-13-or-10-14-video-functionality-not-enab) if you're having issues on Mac. If you have an M1, grant screen recording permissions as detailed [here](https://m1displays.com/).) +* [ ] Upload a headshot [here](https://drive.google.com/drive/folders/1y\_yhkZQE5uSRhLZAHJn2kFuXPBixVJ2G). +* [ ] Install [Zenhub Browser Extension](https://www.zenhub.com/). +* [ ] [Create a Github issue](https://github.com/cityofaustin/atd-data-tech/issues/new) to add yourself to the [DTS "About Us" webpage](https://austinmobility.io/about):\ + \- 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 +* [ ] Email Adan S. to request a paper timesheet. +* [ ] [Open a service request ](https://atx.servicenowservices.com/sp?id=sc\_cat\_item\&sys\_id=02e490c6db7f1300a314e1c2ca9619e6)with Communications and Technology Management (CTM, the City's internal enterprise IT department) to request a Miro account. +* [ ] Familiarize yourself with the [DTS Resource Index](https://github.com/wiki/resource-index) and our [document storage policies](../basics/document-storage/). + +## 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 this one. + +* [ ] Complete the [Telework Request Form](https://atd.knack.com/hr#new-telework-request/). +* [ ] Record any City hardware you have in the [Take-Home Equipment Tracker](https://atd.knack.com/dts#my-equipment/). + + + +Ask questions! Be a sponge and absorb it all! 🧽💦🌈 + +Bonus: [Update this wiki](https://app.gitbook.com/@atd-dts/s/wiki/) if you find broken links or missing information! 😉 + + + diff --git a/docs/product-ops/dts-website.md b/docs/product-ops/dts-website.md new file mode 100644 index 0000000..71d1a58 --- /dev/null +++ b/docs/product-ops/dts-website.md @@ -0,0 +1,50 @@ +--- +description: >- + We use the Data & Technology Services website, Austinmobility.io, to showcase + our work and communicate with stakeholders. The content is driven by Github, + Zenhub, and the DTS Portal. +--- + +# DTS Website Management + +## Basics + +An issue will appear on the [_Projects_](https://austinmobility.io/projects) or [_Products_](https://austinmobility.io/products) pages if it: + +* Has a "Product: xyz" or "Project: xyz" name +* Has the "Product Index" or "Project Index" label + +## Tiles + +Each project or product is rendered as a tile using content from the index issue: + +

Various Github content is used for the project/product "tiles"

+ + + +## Issues and activity + +All issues with the `Product:` label for a given product will be rendered on the **Issues** tab ([example](https://austinmobility.io/products/145?tab=issues)) and all comments on the project/product Index issue itself will show on the **Activity** tab ([example](https://austinmobility.io/products/145?tab=activity)). + +## Evaluation + +In order for the **Evaluation** tab ([example](https://austinmobility.io/projects/307?tab=evaluation)) to render correctly, the project must have an evaluation completed in the [DTS Portal](https://atd.knack.com/dts#project-evaluation/). + +Once an issue is labeled `Project Index`, it will automatically be added as a [project in the DTS Portal](https://atd.knack.com/dts#project-evaluation/). + +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. + +![You can manually create a project if your project is not listed](<../.gitbook/assets/Screen Shot 2021-11-01 at 7.49.16 PM.png>) + +### 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](https://docs.google.com/document/d/1SA3iEyfiBlnxgx2miYn5EncVeUrQyOtUfAk-93574z8/edit#heading=h.o10gj6a8so5p) so that the Product team can review it as a group and determine a score together. + + + + + diff --git a/docs/product-ops/github-project-management.md b/docs/product-ops/github-project-management.md new file mode 100644 index 0000000..c66380a --- /dev/null +++ b/docs/product-ops/github-project-management.md @@ -0,0 +1,119 @@ +--- +description: >- + The Data and Technology Services team is using Github and ZenHub for agile + project management. This is an overview of our process. +--- + +# Github Project Management + +## Set up + +1. [Create a Github account](https://github.com/join) if you don't have one already. +2. Have someone on the DTS team add you to the [City of Austin](https://github.com/cityofaustin) organization and the [Transportation](https://github.com/orgs/cityofaustin/teams/transportation) team as a Maintainer. +3. Add the [ZenHub extension](https://www.zenhub.com/extension) to your browser. +4. Log into the [ZenHub web app](http://app.zenhub.com/) using your normal GitHub credentials to activate your account. + +## Pipelines + +The Zenhub board uses a [Kanban](https://en.wikipedia.org/wiki/Kanban\_board)-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](https://github.com/cityofaustin/atd-data-tech/issues) or our [Zenhub board](https://github.com/cityofaustin/atd-data-tech#zenhub). + +![Screenshot of the Issues page with the "New issue" button circled. ](https://github.com/cityofaustin/atd-data-tech/raw/master/images/Create-new-issue.png?raw=true) + +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 + +It is best practice for issue titles to **begin with a verb** and **summarize** the work to be completed. This convention improves readability and helps keep our tasks action-oriented and unambiguous. + +Here are some examples: + +| Use this | Not this | +| --------------------------------------------------------------- | --------------------------------------------------------- | +| Replace the council district dataset used in Vision Zero Viewer | Outdated/inaccurate council district AGOL resource in VZV | +| Implement new work activity fields in the Moped editor UI | AMD not tracking funding information | +| Publish new CCTV camera thumbnails | CCTV map issues | + +## Labels + +You can apply labels when looking at an individual issue by clicking the "Labels" heading in the right-hand sidebar. You can also [apply labels in bulk from on our ZenHub board](https://www.zenhub.com/blog/task-board-bulk-actions/). + +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. + +All to say: It's important to ensure issues are properly labeled. + +### Required labels + +* [**Workgroup**](https://github.com/cityofaustin/atd-data-tech/labels?q=Workgroup%3A+) — the customer we're serving; `Workgroup: DTS` for internal work and `Workgroup: ATD` for department-wide work +* [**Service**](https://github.com/cityofaustin/atd-data-tech/labels?q=Service%3A+) — The DTS service team the work will be handled by +* **Project** and/or **Product** labels + * [**Projects**](https://github.com/cityofaustin/atd-data-tech/labels?q=Project%3A) refer to a substantial scope of related work that will reach a state of relative completion, such as the [AGOL Audit](https://github.com/cityofaustin/atd-data-tech/issues/253) + * [**Products**](https://github.com/cityofaustin/atd-data-tech/labels?q=Product%3A+) are solutions that we continue to support over time, including all in-house applications, such as the Vision Zero Crash Data System + * Often, a major feature or enhancement to an existing product will require enough resources and coordination that it qualifies as a project. [Warehouse Inventory](https://github.com/cityofaustin/atd-data-tech/issues/20), for example, was a major set of features and enhancements to AMD Data Tracker and the Finance and Inventory App, so it needed both **Product** and **Project** labels + +### Optional labels + +A DTS team or individual product manager may find these additional label categories helpful + +* [**Type**](https://github.com/cityofaustin/atd-data-tech/labels?q=Type%3A) — The type of request or task +* [**Impact**](https://github.com/cityofaustin/atd-data-tech/labels?q=Impact%3A+) — 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 +* [**Need**](https://github.com/cityofaustin/atd-data-tech/labels?q=Need%3A) — 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 + * `Impact: 3-Minor` — Deteriorates TPW service delivery + * `Impact: 4-None` — Does not affect TPW service delivery +* [**Provider**](https://github.com/cityofaustin/atd-data-tech/labels?q=Provider%3A) — The external team or vendor executing the issue + +## Estimates + +Estimates are how we track the level of effort of issues. This is 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](https://www.zenhub.com/blog/track-your-speed-of-work-with-agile-velocity-charts/), which helps us predict the likelihood we can complete things by a given date + +[This is a good article](https://help.zenhub.com/support/solutions/articles/43000010347-estimate-work-using-story-points) about the hows and whys of estimates with ZenHub. + +![Estimates (1-5) align with shirt sizes (XS-XXL). Complexity, uncertainty, and time increase as numbers/sizes increase](https://github.com/cityofaustin/atd-data-tech/raw/master/images/Relative-estimates.png) + +## 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](https://www.zenhub.com/blog/working-with-epics-in-github/). Here[ is an example](https://github.com/cityofaustin/techstack/issues/1215) 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](https://github.com/cityofaustin/atd-geospatial/issues/4) 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. + +Ultimately, epics can group whatever makes sense for you and your collaborators. Some people prefer [issues with task lists inside them](https://github.com/cityofaustin/techstack/issues/616). That's fine as long as the issue doesn't require more effort than we can represent in our [estimate scale](https://github.com/cityofaustin/atd-data-tech/wiki/Project-Management:-Github-and-ZenHub-Basics#estimates) for a single issue. + +## 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. + +## Learning More + +Here are some additional guides for some of our most relied-upon Zenhub functionality: + +* [Filtering the Board](https://help.zenhub.com/support/solutions/articles/43000498508--filtering-the-board) +* "Use multi-action to make bulk Issue updates" on [this page](https://help.zenhub.com/support/solutions/articles/43000031098-get-to-know-board-features-and-functionality) + +The [Zenhub docs](https://help.zenhub.com/support/home) are super-solid, and we encourage you to peruse them at your leisure. Remember that some functionality—renaming and reordering pipelines, 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, talk about it with a Product Manager or share it in the `#atd-product` Slack channel! diff --git a/docs/product-ops/index-issue-specifications.md b/docs/product-ops/index-issue-specifications.md new file mode 100644 index 0000000..8cf5637 --- /dev/null +++ b/docs/product-ops/index-issue-specifications.md @@ -0,0 +1,77 @@ +# Index Issue Specifications + +We use "index" Github issues to centralize information about each of our projects and products. It is critical that these issues follow a standard labeling scheme and content format so that [DTS' project data](https://data.austintexas.gov/Transportation-and-Mobility/ATD-Data-Tech-Services-Issues/rzwg-fyv8/) is accurate, team members work is coordinated and efficiently tracked, and we have an accessible, high-level view of the project/product on the [DTS Website](https://product.austinmobility.io). + +{% hint style="info" %} +Create a new Project or Product Index by selecting the [appropriate issue template](https://github.com/cityofaustin/atd-data-tech/issues/new/choose) from the `atd-data-tech`Github repository. +{% endhint %} + +## Project Index + +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](https://github.com/cityofaustin/atd-data-tech/labels?q=project) +* `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**](https://github.com/cityofaustin/atd-data-tech/issues/new?assignees=\&labels=Project+Index\&template=-all-purpose--project-index.md\&title=Project%3A+%5BYour+Project+Name+in+Title+Case%5D) issue template. + +### Image + +See [#index-issue-images](index-issue-specifications.md#index-issue-images "mention") 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](https://github.com/cityofaustin/atd-data-tech/labels?q=product) +* `Workgroup: xyz` — the workgroup(s) of the product's primary users + +### Assignee + +The product manager. + +### Issue description + +Follow the [**Product Index**](https://github.com/cityofaustin/atd-data-tech/issues/new?assignees=\&labels=Product+Index\&template=-all-purpose--product-index.md\&title=Product%3A+%5BProduct+Name+in+Title+Case%5D) issue template. + +### Image + +See [#index-issue-images](index-issue-specifications.md#index-issue-images "mention") 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**](https://austinmobility.io/projects/638) or other [**visualization**](https://austinmobility.io/projects/9876) of the data generated in the app +* **Photos** of the project/product's [**end users at work**](https://austinmobility.io/products/251) or the related [**hardware**](https://austinmobility.io/projects/1540)**/**[**service**](https://austinmobility.io/products/1192); the [TPW Flickr feed](https://www.flickr.com/photos/atxmobility/) is a fantastic source for these +* A [**close-up screenshot** of a unique part of the UI](https://austinmobility.io/projects/4611) +* For mobile-focused apps, we have a [template](https://docs.google.com/presentation/d/11W8P7kb8mt3FNehyG-\_UiNlv4gBn-uWT\_WZTKyJc\_kY/edit#slide=id.gf792707f70\_0\_0) to show off [**the application on different devices**](https://austinmobility.io/products/145)​ + +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](https://github.com/cityofaustin/atd-data-tech/issues/13684) 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](https://croppola.com/) makes it easy to crop/resize as needed. + +
diff --git a/docs/product-ops/product-delivery-workflow.md b/docs/product-ops/product-delivery-workflow.md new file mode 100644 index 0000000..97674b1 --- /dev/null +++ b/docs/product-ops/product-delivery-workflow.md @@ -0,0 +1,77 @@ +# Project Delivery Workflow + +[**Products**](https://austinmobility.io/products) are the solutions we build for our customers, including Knack apps, AMANDA apps, custom software, and data systems. We improve and extend our products over time so that they deliver continuous value to Austin Transportation as business needs evolve. + +[**Projects**](https://austinmobility.io/projects) are time-boxed endeavors. They accomplish a singular goal and have a defined completion date. Examples include: + +* [Recommending an off-the-shelf externally-supported solution](https://github.com/cityofaustin/atd-data-tech/issues/65) +* Delivering the first iteration (MVP) of a new DTS product +* [Building a major feature for an existing DTS project](https://github.com/cityofaustin/atd-data-tech/issues/533) +* [Refactoring a dataset](https://github.com/cityofaustin/atd-data-tech/issues/254) +* [Delivering a complex map](https://github.com/cityofaustin/atd-data-tech/issues/1911). + +## 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](https://austinmobility.io/projects/4199), [a technical refactor of the Vision Zero Database](https://austinmobility.io/projects/10430), or [migrating our CCTV image service from a local server to the cloud](https://austinmobility.io/projects/1046). + +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](https://github.com/cityofaustin/atd-data-tech/issues/new?assignees=\&labels=Project+Index\&projects=\&template=-all-purpose--project-index.md\&title=Project%3A+%5BYour+Project+Name+in+Title+Case%5D) or convert the existing issue to match the [project index template](https://github.com/cityofaustin/atd-data-tech/issues/new?assignees=\&labels=Project+Index\&projects=\&template=-all-purpose--project-index.md\&title=Project%3A+%5BYour+Project+Name+in+Title+Case%5D). 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. + +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](https://docs.google.com/document/d/1AcjxHv6XCEutSAIzNebnxNR9EL8CORiHrVfNlQuChII/edit#heading=h.f4j2i9aovme). +* 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](https://docs.google.com/document/d/1hWzg-qluRBrTetEGjg\_eHrR9qT4IqenaUgk6FR6APbU/edit) to discuss. +* Prepare a summary of request. Here's an [example done as a presentation deck](https://docs.google.com/presentation/d/1brqKe0IfavZ4K8Dp2jv1QBW\_Kfa7umDROOiQ2lHc67I/edit#slide=id.p) ([template](https://docs.google.com/presentation/d/1i9rcEEsEIWtHLJd\_e0foQpNX9bQkffj4zHkzRsguW60/edit?usp=sharing)). +* At the meeting, discuss the recommended approach and fill out the "Effort" section of the [project evaluation in the DTS Portal](https://atd.knack.com/dts#project-evaluation/). + +{% hint style="info" %} +Sometimes we realize that the request isn't actually project-sized during the intake meeting or the builder huddle. No worries, we had a good opportunity to learn more about our customers' work. Might make sense to organize this work as an [epic](github-project-management.md#epics), once the time comes. +{% endhint %} + +## Product Sync + +After assessing effort with the builders, it's time to assess value with the product team. + +* Add to [DTS Product Sync agenda](https://docs.google.com/document/d/1SA3iEyfiBlnxgx2miYn5EncVeUrQyOtUfAk-93574z8/edit) 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](https://docs.google.com/document/d/1hWzg-qluRBrTetEGjg\_eHrR9qT4IqenaUgk6FR6APbU/edit) instead. +* As a group, fill out the "Value" section of the [project evaluation in the DTS Portal](https://atd.knack.com/dts#project-evaluation/). + +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](https://austinmobility.io/projects?status=backlog\&view=chart). + +Move the index issue into the "Backlog" pipeline. + +## 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. + +As you create and assign issues, make sure they all have the `Project:` label so that they render on the projects' page on the website and are easy to surface on Zenhub. You may also wish to convert the project index into an epic so that all issues are visible from the index without having to look at the Zenhub board. + +It's also critical that all issues have an estimate when they are assigned so that we can track our velocity and report on our work volume. If the issue is complex, bring it to backlog refinement before bringing to sprint planning so that the team can align on an approach and estimate. If the estimate changes while the issue is in progress, simply update it. We want the estimates on all of our closed issues to accurately reflect the effort they required. + +## Completion + +A project is considered complete when the minimum viable product (captured in the "Scope and Deliverables" section of the issue's [**Project Index**](https://github.com/cityofaustin/atd-data-tech/issues/new?assignees=\&labels=Project+Index\&template=-all-purpose--project-index.md\&title=Project%3A+%5BYour+Project+Name+in+Title+Case%5D)) is delivered to users. + +Often, there are still issues in the backlog, but these are not actually must-haves. Simply 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. + +For complex projects, you might consider making an "Onboarding and Stabilization" epic in the project to capture any critical bugs or enhancements that surface during roll out. After closing all those issues, the project is complete. + +![](<../.gitbook/assets/Screen Shot 2022-05-24 at 10.39.48 AM.png>) + + + diff --git a/docs/product-ops/release-management-process.md b/docs/product-ops/release-management-process.md new file mode 100644 index 0000000..4e050d0 --- /dev/null +++ b/docs/product-ops/release-management-process.md @@ -0,0 +1,14 @@ +# Release Management Process + +Below are the steps needed to successfully release new code to production: + +* Plan Release: The Product Manager & Dev Lead collaboratively plan what issues will be included in the release +* The Dev team completes all issues in the planned release +* The Dev Lead creates a pull request that includes the scope of the release. Example: [https://github.com/cityofaustin/atd-vz-data/pull/496](https://github.com/cityofaustin/atd-vz-data/pull/496) +* The Product Manager QAs the updates that are included in the pull request. The QA should occur in the Stage environment. Product Manager should visually QA all of the changes that are part of the release. +* The Product Manager should also complete smoke tests of that aim to ensure that the most important functions of the product or feature work as expected. Product Managers should have a list of smoke tests per product/project. +* Merge pull request \(Product Manager\) +* Notify \#atd-dev that the pull request has been tested, approved, and merged \(Product Manager\) +* QA updates and smoke tests on Production environment \(Product Manager\) +* Send Release Notes to Stakeholders/Customers \(Product Manager\) Example: [https://github.com/cityofaustin/atd-vz-data/releases/](https://github.com/cityofaustin/atd-vz-data/releases/) + diff --git a/docs/resource-index.md b/docs/resource-index.md new file mode 100644 index 0000000..2150a7c --- /dev/null +++ b/docs/resource-index.md @@ -0,0 +1,72 @@ +--- +description: >- + ​Welcome to the Austin Transportation Data & Technology Services team! + 👋Here's a bevy of links to get you started.​ +--- + +# Essential Resources & Wikis + +## Data & Technology Services + +* [Austinmobility.io](https://austinmobility.io/) — Data & Technology Services and our work +* [Data and Performance Hub](http://transportation.austintexas.io/) — Austin Transportation dashboards we build and maintain +* [DTS Portal](http://atd.knack.com/dts) — Service Requests, Data Inventory, Technician Equipment Tracker +* [Google Drive](https://drive.google.com/drive/folders/1fNmU-czryk5wJsn1gmb4WYUJJdut8Me7) +* [Document templates](https://drive.google.com/open?id=1Txqc8xGkwa3h9lrRoXGzGjLlVo0S8DA6) + * [Slides template](https://docs.google.com/presentation/d/1VNhW2JrTdSky9Z0KaOlz6DijRHjcC\_6d1gYiZWRgnno/edit?usp=drive\_link) + * [Docs template](https://docs.google.com/document/d/1DoT8kbC2eSrhkNXhGwAY2DhQHBjdfXrsHgQgx7wqjPs/edit?usp=drive\_link) + * [Email signature template](https://docs.google.com/document/d/1OAoBll9rIl6XZq2uOShm5HCbHJboOt0SLP\_wK6tjkEE/edit) +* [Division intranet](https://cityofaustin.sharepoint.com/sites/ATDDTS) - SharePoint site +* [Private GitBook page](https://app.gitbook.com/@atd-dts/s/dts-service-desk-knowledge-base/onboarding/general) - a handful of info that is too sensitive to include in this public wiki + +### Our Wikis + +* [DTS Dev](https://atd-dts.gitbook.io/atd-dev/) +* [DTS Knack Operations](https://atd-dts.gitbook.io/atd-knack-operations/) +* [DTS Geospatial](https://atd-dts.gitbook.io/atd-geospatial/) +* [DTS Open Data](https://atd-dts.gitbook.io/open-data/) +* [DTS Service Desk Knowledge Base (private)](https://app.gitbook.com/@atd-dts/s/dts-service-desk-knowledge-base/) + +We also have end-user documentation for [Moped](https://app.gitbook.com/o/-LzDQOVGhTudbKRDGpUA/s/-MIQvl\_rKnZ\_-wHRdp4J/), [Signs & Markings Tracker](https://atd-dts.gitbook.io/signs-and-markings-tracker-help-guides/), the [SXSW Command Center](https://atd-dts.gitbook.io/command-center-resources/), and [TDS Operations](https://app.gitbook.com/o/-LzDQOVGhTudbKRDGpUA/s/-Mdw\_HGhQRPU5N26oPGn/) + +## Transportation Public Works + +### Videos + +These were all produced before the Transportation and Public Works departmental merger + +* [Inside Austin Transportation](https://www.youtube.com/watch?v=ERinYUmx9V0) +* [Public Works Vimeo](https://vimeo.com/austinpublicworks) +* [Walk Bike Roll](https://vimeo.com/586077566) + +### Websites + +* [Austin Transportation and Public Works](http://www.austintexas.gov/department/transportation) - public-facing department site +* [Austin Strategic Mobility Plan](https://www.austintexas.gov/department/austin-strategic-mobility-plan) - Transportation and Public Works' infrastructure roadmap +* [Department intranet](https://cityofaustin.sharepoint.com/sites/ATDHub) - SharePoint site + +## City of Austin + +* [Org chart](https://www.austintexas.gov/service/city-organizational-and-department-chart) +* [Open Data Portal](https://data.austintexas.gov/) +* [Open Data Community](https://opendata.bloomfire.com/) - Bloomfire +* [GIS Community ](https://austingis.bloomfire.com/)- Bloomfire + +## Employee Resources + +* [CTM service request form](https://atx.servicenowservices.com/sp) — or 512-974-4357 (4-HELP from a City phone) +* [Official City of Austin holiday schedule](http://www.austintexas.gov/department/official-city-holidays) +* [City Intranet](https://cityspace.austintexas.gov/Home) + * [Benefits ](https://cityspace.austintexas.gov/Benefits) + * [Policies and Procedures](https://cityspace.austintexas.gov/Policies-Procedures) + * [Technology Resources](https://cityspace.austintexas.gov/Technology-Resources) + * [Healthy Connections](http://cityspace.ci.austin.tx.us/services/healthyconnections) - includes PE classes +* [HR Portal](https://hrdcfprod.coacd.org/) — pay stubs, benefits, PE registration +* [Employee benefits](http://www.austintexas.gov/department/active-employee-benefits/) (external site) +* [Online Earnings Statement](https://www.ci.austin.tx.us/eaccess/default.cfm) +* [Municipal Civil Service rules](https://www.austintexas.gov/department/municipal-civil-service-rules) - City of Austin rules regarding employee hiring, promotions, lateral transfers, reduction-in-force, disciplinary actions, and appeals + +### Training + +* [City of Austin LinkedIn Learning](https://www.linkedin.com/learning/?accountId=55898036\&u=55898036\&success=true\&authUUID=fzCyYwylTz6M1VC59AmApQ%3D%3D) - available through single-sign-on +* [CoA HR's Career Development & Training Resources](https://cityspace.austintexas.gov/Career-Development-Training)