PRB Actions
|
PRB Actions |
| Return to previous page | View Schedule | PRB Decisions | Print this page |
| PRB Meeting Date: 3/4/2025 | |||
| Request Teleconference | Teleconference Phone #: | ||
| Video Teleconference | |||
| 2. Form Date: | 3. Project Manager/Presenter: | 4. Phone Number(s): | 5. Mail Drop: |
| 3/6/2025 9:32:53 AM | Kendra Johnson | , , |
| 6. Project Name/Location: | 7. Type of Work: | 8. CPS Id: | ||||
| Spillman CAD Data Transfer | Create Application Programming Interface (API) | WM1Q | ||||
| 9. District: | 10. Route: | 11. County: | 12. Beg. MP: | 13. TRACS #: | 14. Len. (mi): | 15. Fed ID#: |
| M727501X | ||||||
| 16. Original Program Budget: $0 | 17. Original Program Item #: 105108 |
| Project Budget | Project Budget | Project Budget |
| 18. Current Approved: | 18a. New Project/Change Request: | 18b. Final: |
| $0 | $87,000 (0%) | $87,000 |
| Funding Source(s) | Funding Source(s) | 20. JPA #, Signed, Adot Adv.: |
| 19. Current Approved: | 19a. New Project/Change Request: | |
| $ 87 Item #:78825 ( ) FY:0 FundSRC: Desc: | ||
| Current Approved | New Project/Change Request | |||
| 21. Fiscal Year: | 21a. Fiscal Year: | |||
| 22. Bid Pkg Rdy Date: | 22a. Bid Pkg Rdy Date: | 24. Verified all of the new funding sources | ||
| 23. Bid Adv Date: | 23a. Bid Adv Date: | |||
| 25. DESCRIPTION OF REQUEST |
| Establish a new project |
| 26. JUSTIFICATION |
| The Traffic Operations Center inputs incident data into Spillman CAD as its main system of record. This data is important for platforms like AZ511 and the L101 Integrated Corridor Management (ICM) system. The data needs to be transmitted in realtime/near-real-time, but this is impeded by the current use of SFTP (Secure File Transfer Protocol) and FTP (File Transfer Protocol) transmission methods. FTPs are good for legacy system integration and transferring large files in batches. However, APIs (Application Programming Interface) are better at integrating web and mobile applications as well as transferring small data files in real-time. This project is to identify the best way to transfer Spillman data to other systems by minimizing latency and disseminating it in real-time with an API. This will also help to make the data more easily retrievable for performance measures and after-action reports/analysis. |
| 27. CONCERNS OF THE PROJECT TEAM REGARDING THE REQUEST |
| 28. OTHER ALTERNATIVES CONSIDERED |
| REQUESTED ACTIONS | APPROVED/RECOMMENDED ACTIONS |
| Establish a New Project. | Item(s) Approved. Subject to PPAC Approval. |
| PRB Meeting Date: 2/11/2025 | |||
| Request Teleconference | Teleconference Phone #: | ||
| Video Teleconference | |||
| 2. Form Date: | 3. Project Manager/Presenter: | 4. Phone Number(s): | 5. Mail Drop: |
| 2/27/2025 2:11:32 PM | Kendra Johnson | , , |
| 6. Project Name/Location: | 7. Type of Work: | 8. CPS Id: | ||||
| Spillman CAD API | Create API for Spillman CAD | WM1Q | ||||
| 9. District: | 10. Route: | 11. County: | 12. Beg. MP: | 13. TRACS #: | 14. Len. (mi): | 15. Fed ID#: |
| _ | ||||||
| 16. Original Program Budget: $0 | 17. Original Program Item #: |
| Project Budget | Project Budget | Project Budget |
| 18. Current Approved: | 18a. New Project/Change Request: | 18b. Final: |
| $0 | $87,000 (0%) | $87,000 |
| Funding Source(s) | Funding Source(s) | 20. JPA #, Signed, Adot Adv.: |
| 19. Current Approved: | 19a. New Project/Change Request: | |
| $ 87 Item #:78825 ( ) FY:0 FundSRC: Desc: | ||
| Current Approved | New Project/Change Request | |||
| 21. Fiscal Year: | 21a. Fiscal Year: | |||
| 22. Bid Pkg Rdy Date: | 22a. Bid Pkg Rdy Date: | 24. Verified all of the new funding sources | ||
| 23. Bid Adv Date: | 23a. Bid Adv Date: | |||
| 25. DESCRIPTION OF REQUEST |
| Establish a new project. |
| 26. JUSTIFICATION |
| The Traffic Operations Center inputs data into Spillman CAD as its main system of record. This data is important for platforms like AZ511 and the 101L Integrated Corridor Management (ICM) system. The data needs to be transmitted in real-time/near-real-time, but this is impeded by the current use of SFTP and FTP transmission methods. A project is being set up to identify the best way to transfer Spillman data to other systems by minimizing latency and disseminating it in real-time with a Spillman API. This will also help to make the data more easily retrievable for performance measures and after-action reports/analysis. |
| 27. CONCERNS OF THE PROJECT TEAM REGARDING THE REQUEST |
| 28. OTHER ALTERNATIVES CONSIDERED |
| REQUESTED ACTIONS | APPROVED/RECOMMENDED ACTIONS |
| Establish a New Project. | Request Withdrawn. |
| Arizona Department of Transportation |