Aimsun software was used for this analysis, which called for the development of several custom software features including specific NYCDOT policies to maintain signal coordination, define vehicle queues and process subsequent TSP calls after servicing the first call in a cycle. The GPI team developed logic specifications representing each of these policies and TSS then created the corresponding custom Application Programming Interface (API) software to model them. Trafficware’s Synchro software was also used to help identify existing traffic problems, evaluate low-cost geometric and striping improvements, and develop optimal signal timings and coordination for the corridor. This effort was found to be critical to maximize the benefits of TSP by alleviating existing traffic problems and providing timing adjustments that facilitate TSP. This set of improvements is referred to as “Passive TSP” since it lays the foundation for TSP success without actual implementation. The Aimsun simulation analyses were conducted in three stages: First GPI created and validated a baseline model of current conditions for each peak period (7:30am to 10:30am, 12:30pm to 3:30pm and 4:00pm to 7:00pm). Secondly the team looked at passive TSP, evaluating the benefits of recommended traffic improvements and Synchro optimal signal timings relative to existing conditions. In the third and final stage, they looked at active TSP, evaluating the effectiveness of all improvements in addition to TSP and then studying and resolving the TSP implementation issues.