Hearing Hearings — Hearing Record ✉
← All hearings

Oversight of PASSPort

Committee on Contracts

Meeting overview

The Contracts Committee held a wide-ranging oversight hearing on PASSPort, the City's procurement and contracting platform, alongside consideration of four pieces of legislation and a resolution aimed at reforming small capital project delivery. The hearing featured testimony from city officials including the MOCS director, a DDC commissioner, and public witnesses from the procurement reform space and the Human Services Council. The committee, led by Chair Restler, probed PASSPort's costs, staffing, system performance, user experience, and future direction with more rigor than is typical of oversight hearings, while also pushing on capital project inefficiencies through the legislative agenda.

On PASSPort, the picture that emerged was of a system that processes an enormous volume of city contracting activity, roughly $40-45 billion annually, at a cost of around $10 million per year in vendor contracts, but which remains deeply frustrating for end users, particularly nonprofits. The MOCS director was candid about gaps and turbulence caused by rapid system changes, and acknowledged a very long internal wish list of improvements that the agency cannot fully fund or implement. The committee focused heavily on the experience of nonprofit providers, with Chair Restler describing firsthand a visit to a local nonprofit where a single invoice submission took a staff member half a day, requiring manual transcription of dozens of fields from spreadsheets into PASSPort with no bulk upload functionality, no recognition of prior data, and inconsistent field layouts across agencies. Council Member Brewer reinforced this, noting that some providers are so frustrated they simply choose not to work with the city, potentially excluding high-quality organizations. Release Seven of PASSPort, due in early 2027 at a cost of $6.5 million, was highlighted as a critical near-term fix, particularly for the longstanding bug that blocks invoice submission while a budget modification is pending. The Human Services Council testified that this particular flaw is not a policy decision but a system quirk that has trapped nonprofits in impossible cash-flow situations for years, with some owed retroactive COLAs and indirect cost rate adjustments. The MOCS director confirmed the scope of the problem, noting that 10,000 budget modifications occurred in the last fiscal year, each blocking invoicing for an average of five days.

Structural questions about PASSPort's future were among the more substantive moments of the hearing. The committee raised the issue of capital eligibility: because the city licenses rather than owns PASSPort, improvements cannot be capitalized, making sustained investment harder to justify in budget terms. The MOCS director floated two conceptual options: purchasing the intellectual property outright from software vendor InValue, which has built city-specific customizations on top of its platform, or eventually commissioning a city-owned system built by city technologists. Both were acknowledged as very early-stage ideas. The committee also questioned why OTI, the city's central technology office, is not more directly involved in day-to-day PASSPort management, given that the system processes tens of billions of dollars and has over 123,000 agency users. The MOCS director said OTI's involvement has recently increased at a strategic level and that deeper involvement would be welcomed. On the question of DOE procuring its own separate system rather than adopting PASSPort, the MOCS director said she was unaware of those conversations having included MOCS, which the committee found unsatisfying.

The legislative agenda covered four bills and a resolution on small capital projects. On Intro 1064, which would impose timeframes on agency approvals and change orders, a DDC official acknowledged that the main delay is not paperwork but the back-and-forth with contractors over whether something constitutes a change order at all, which can take four to five months before any formal clock starts. He expressed willingness to set timelines once agreement is reached, noting the formal process takes roughly two months. On Intro 1065, which would require cost benchmarks for small recurring capital projects, the official expressed comfort with publishing historical contract data but concern about forward-looking cost benchmarks given construction cost escalation running at around 8% annually and market volatility driven by factors like data center construction absorbing raw materials. On Intro 0991, which would require a catalog of standard designs, he drew a distinction between standard designs, which he opposed as too inflexible given site-specific infrastructure requirements, and design guidelines, which he strongly endorsed, citing five Parks Department bathrooms being delivered in 18 months at $3.6 million each using strict guidelines. A resolution calling on the state to lower the threshold for design-build was also on the agenda, with design-build flagged as a best-value procurement method that avoids lowest-bidder problems. Public witness Charles Diamond argued for more investment in procurement infrastructure overall and urged a yes vote on Ballot Question Two, which would allow the Mayor to delegate approval of non-competitively bid contracts over $5 million to agency chief contracting officers and make permanent the public comment period in place of a public hearing. The MOCS director supported both elements of the ballot question.

The record

Numbers
  • PASSPort processes approximately $40-45 billion in city contracting transactions annually.
  • The city has spent at least $120 million on PASSPort since its inception in 2016, including $9.7 million with software vendor InValue and over $20 million with Accenture.
  • The current steady-state annual cost of PASSPort is approximately $10 million: $2.5 million per year to InValue for software licenses and $7.5 million per year to Accenture as systems integrator.
  • Release Seven of PASSPort, due in early 2027, is budgeted at $6.5 million.
  • Both the InValue and Accenture contracts are set to expire in April 2027 with no renewal option, requiring a new procurement or negotiated acquisition.
  • Approximately 32 to 40 MOCS technology staff support PASSPort, representing roughly 20-30% or more of MOCS total operational headcount.
  • MOCS headcount is approximately 170 positions below its authorized level.
  • PASSPort currently has 34,000 registered vendors and 123,000 active agency users; approximately 87,000 used the system in the last fiscal year.
  • To date, PASSPort has processed 35,330 registered contracts and 22,605 amendments with a combined value of $187 billion; 472,000 invoices have been dispersed.
  • In fiscal year 2026, 135,000 invoices were created in PASSPort, a 12% increase over the prior year.
  • PASSPort system uptime was approximately 99.1% or higher in the review period.
  • There are approximately $1 billion in unpaid invoices currently visible in the PASSPort queue, though not all are late.
  • Average invoice payment time has fallen from 41 days to approximately 22 days, below the 30-day Procurement Policy Board benchmark.
  • In fiscal year 2026, 69% of contracts were registered on time; in FY25 approximately 28% were registered after their start date (72% late by one reading of the data, though the committee sought written clarification).
  • The median cycle time for competitive sealed proposals rose from 386 days in FY25 to 527 days in FY26; the median for competitive sealed bids declined year over year.
  • There were approximately 10,000 budget modifications in the last fiscal year, each blocking invoice submission in PASSPort for an average of five days.
  • Five Parks Department bathrooms built under design guidelines cost $3.6 million each and are being delivered in approximately 18 months, roughly twice as fast as traditional design timelines.
  • Construction cost escalation is running at approximately 8% per year, driven in part by data center construction absorbing steel and concrete supply.
  • A new bathroom at Kissena Park in Flushing requires approximately half a mile of deep sewer and electrical infrastructure to connect to the street, a major driver of costs.
  • The Ballot Question Two reform package was estimated by the Charter Revision Commission to save one to two weeks on approvals for non-competitive contracts over $5 million, and up to 30 days overall on a procurement.
  • Public hearings on contracts, which the ballot question would replace with public comment periods, are held less than once a month, primarily for shelter contracts.
  • MOCS annual budget allocation for PASSPort maintenance is approximately $14 million this year, down from $22 million the prior year, representing 0.025% of annual contract spend.
Action Points
  • MOCS to provide the committee in writing with a precise count of full-time employee equivalents dedicated to PASSPort support.
  • MOCS to rerun and share updated data on unregistered contracts and unpaid invoice backlog, as the Comptroller's April 2025 report is now over a year old.
  • MOCS to provide written FY26 indicators on contract registration timeliness and invoice payment cycle times for comparison with prior years.
  • MOCS to follow up with the committee on the number of non-competitively bid contracts over $5 million to give a more precise estimate of the scope of Ballot Question Two's delegation provision.
  • MOCS to estimate the cost of adding simultaneous OMB and Law Department review functionality to PASSPort and report back to the committee.
  • MOCS to take back the question of whether PASSPort and PIP currently communicate effectively and report to the committee.
  • MOCS to engage OTI more directly in PASSPort management, with Chair Restler indicating he would raise greater OTI involvement with the relevant city technology leadership.
  • MOCS to share its internal post-Release Seven roadmap options, including deprecation of functionality and potential acquisition of intellectual property, with the committee once Release Seven is delivered.
  • MOCS to engage with the Comptroller's office and the Law Department on capital eligibility for PASSPort improvements, with Chair Restler offering to help facilitate those conversations.
  • MOCS to work with Council Finance on contingency protections for discretionary grant pilot participants at risk of losing funding due to paperwork failures rather than non-performance.
  • MOCS to investigate whether contractor-controlled or wrap-up insurance programs used in construction contexts could be adapted to reduce insurance burdens on nonprofit human services providers.
  • DDC to share information from the restarted Capital Reform Task Force with the committee once finalized, including any internal deadlines agencies have set for change order processing.
  • DDC to develop more proactive capital planning communication with elected officials so that budget gaps between initial estimates and scoped project costs are surfaced earlier and not attributed to the agency or elected official after funding has been committed.
  • MOCS and the committee to convene a joint session with nonprofit and vendor stakeholders post-Release Seven to identify priority reforms to PASSPort from the user perspective.
  • MOCS to confirm in writing whether any mayoral agencies continue to operate legacy procurement systems in parallel with PASSPort.
  • Human Services Council to continue engagement with the committee on Release Seven rollout and its effect on the budget-mod invoice-blocking issue.
Download .txt
Full Transcript

(00:28:54)

Passport should be doing what it should be doing, because my pushback is always that we know we need a system that is working, and it is not about just blaming Passport. It is about thinking, if this is not working, then what are we doing to make it work? But specifically, I know one of the things I have heard often is that they will go and look into Passport, and in the space where it says that the contract is, it is not. So even that function, sometimes it is difficult to find out where they are at in the process. So what are some of the things you guys are doing to improve that, so that providers could use it in a functional way? Vice Chair

(00:29:31)

Stephens, thank you so much, and thank you so much for recognizing that large procurement that we did on Compass. It really was an all-hands effort. The preparing agency really rolled up their sleeves, and we were happy to support that, because it meant after school for a lot of kids who did not previously have after school. That was a Herculean

(00:29:59)

effort. Absolutely. I gave them so many kudos, which I never do. They have been amazing. So yes, I

(00:30:04)

wanted to give you your kudos as well, because you played a part in that as well. Thank you, thank you. So, to answer your question, there are gaps. I'm going to be very upfront: there are gaps. We have tried very hard, through technology solutions, to solve for many problems and answer to many people. As we evolve the project, it really is about taking a moment and seeing how far we've come, but then also seeing where we are falling short, on some of our providers, our nonprofit

(00:30:13)

partners. And what is that gap attributable to? Is it the technology? Is it change management? Or is it something else? You are not the first to lift up and raise that there are user experience issues. It is a very common issue that is brought up, and it is something that, in this moment where we are with the project, system stability, along with payment predictability and contracting predictability, those are our north stars. And the system stability, you

(00:30:47)

Okay, Chair, yeah. Okay, the flags are attacking you. So the system stability is very critical. I'm also not going to be shy about that: the system experienced a little bit of turbulence because of the changes we were making to the system in a very short amount of time. What we have observed, having the benefit of looking back, is that when we change the system, sometimes we shake the system a little bit,

(00:31:28)

and that our users experience it, our nonprofits experience it, our construction firms experience it, our agencies experience it.

(00:31:59)

So one of the things that we are trying to do is focus on Release Seven, which I spoke about in the testimony, but we are also going to really try to be very thoughtful about not introducing new things into the system that affect payment, contract, and predictability. But yes, there is work that we need to do to get in there and hear from the users what it is that they are experiencing, and where their needs are not being met.

(00:32:09)

How are you folks able to give you back that feedback? What is that feedback process like? Because again, it gets really hard, and this is one thing I try to explain to the City: it is really hard for groups to be able to tell providers and people who are giving them money that they are messing up. So what is the expectation, and how is that supported? How are you guys collecting that feedback?

(00:32:36)

Because that is always a struggle for me, because we were like, no, we are working, and I am like, the providers are telling me different stuff, that they are telling you, because they cannot tell you that, because you are giving the money. Yes, it is a fair point. There are a few ways that I think we pick up the signs, and address them. They are not as direct as raising a direct complaint. We look at the tickets, so agencies experiencing an issue on the procurement system and also on Passport, and we are reviewing the tickets and seeing whether there are patterns that we can discern from what we are getting. The other thing we do is proactively survey our vendors on particular pieces of the Passport functionality. Most recently we did it for the vendor reports that we turned on earlier this year, and we are trying to see what we can glean from there. And then also, at certain moments, we will convene particular groups, and we will ask them to tell us how we are doing, and they are not shy about it. They do not hold back. I was supposed to ask some of Lincoln's questions, but obviously that, so, him, thank you so much, thank you for the time. Thank you

(00:32:58)

Thank you, Madam Vice Chair. I will now kick it to Council Member, followed by Council

(00:34:13)

Council Member. Thank you, Chair. My questions are about my two pieces of legislation, starting with Intro 1064, which would require two set time frames for agency approvals and change order determinations. Does the Administration support Intro 1064?

(00:34:19)

I feel like there is a way to pass this bill that is beneficial to both what you're trying to get at and what the agency is trying to do. I will tell you, I get really frustrated with change orders, but the main delay that we see in change orders is not the process itself of putting a change order together and sending it to the Controller for registration. It is agreeing with the contractor that something is a change order. This is what our project managers and engineers do. Essentially, what happens is the contractor says that's outside the contract, change order, because that's automatically where they would go. We then say no, it is definitely within scope, it's within the contract, you should do it, and there is no need for a change order. That back and forth, which is very, very common, unfortunately, is what soaks up the most time, and it is hard to put a clock on that. I am happy to put a clock on when we agreed to a change order. Nothing should be delayed. We usually take about a month internally to put a package together, and then send them to the Controller's Office for registration. The Controller then has a month, so we're talking about a two-month period, which to me sounds pretty reasonable. But it's this back and forth where we spend the most time. Do any agencies currently set internal deadlines for acting on change order requests, other than registering other contract approvals?

(00:34:40)

Yeah, it's a really good question. The last Administration had a Capital Reform Task Force that was looking at a lot of these issues. We're going to be restarting it soon, and we're happy to share that information when we're finalized, but it is something that we can look at. I think we set the cities at times on payments, so invoicing. I don't believe we had an agreement on change order timelines, but I think it's worth the discussion.

(00:36:27)

Sure. And on average, how long does it take to act on a change order request?

(00:36:32)

On a project of this size, when we agree there's a change order, it's usually about a two-month period. Agreeing to the change order, I think, takes the longest time, and sometimes it can take four or five months of just back and forth. I would say, though, that for most of these, the work is continuing, and a change order shouldn't stop the actual construction. There are times when we are discussing change orders for work that will happen nine months from now, just in anticipation of that. So it is frustrating, and we could do better, but it's also our job to make sure that the contractors are doing what they're supposed to be doing.

(00:37:03)

And then for Intro 1065, which is the cost benchmarks, does the Administration support that?

(00:37:10)

I am happy to do anything backward-looking. Essentially, our contracts are public, right? And so whenever we put out a contract for a boiler replacement or replacement, we can absolutely publish that. I am a little worried about putting what we think is the estimate of what a future project would look like, just because the economics of construction change very frequently. For example, right now, construction cost escalation is about 8% a year, and that can change at any given time because of factors outside of New York City. Data centers are soaking up a lot of the raw materials that we would normally use for construction, steel, concrete, and the prices of those materials increase. It would be hard for me to put a benchmark there, and then something like this happens and the numbers are outdated. But I think it's a good idea to have a sort of list of items that we've paid for, for all these small capital projects. So I feel like there's a way to achieve what you're aiming to achieve, and what we feel comfortable with.

(00:37:15)

Does the City have data on the actual total costs of completed small capital projects, and which system does that data come from?

(00:38:28)

Yeah, we definitely have the data. It is something that we look at when we are estimating projects that are upfront in planning. I don't think it's easily available or searchable for somebody in the public, but all our contract data is available together, I think, in the way that you would want it.

(00:38:37)

And would benchmarks under this bill be consistent with the benchmarks in the Mayor's Management Report?

(00:38:57)

Yeah, the MMR has benchmarks, not on cost. They have benchmarks on commitments as a whole. So we essentially have capital commitments that we are aiming for on any given year. We also have timelines, construction timelines, that we include. So if the goal is to be online, I believe we can, right on time. Thank you, Chair.

(00:39:05)

Thanks so much, CM Wilson, and thank you for the thoughtful legislation. Next up.

(00:39:26)

Thank you very much. I was next door at the childcare small business hearing and must admit every other word is contracting, contracting, contracting, so you might as well have been there. They were quite concerned about payment, as you can imagine, so that's just so you know, that's where I've been. And that's this question. Mine had come up in payment, and insurance seemed to be the two issues. Do you get the same insurance even though you're not in charge of insurance? Questions. You're not in charge, but it's a mess. Council Member, thank you. Yes, I am aware of the topic of the hearing. The topic of the hearing is the business of childcare. Yeah, but guess what the real topic is? Yes, yes.

(00:39:32)

Well, no. So you told me, I'm

(00:40:18)

asking just two things, though.

(00:40:19)

Just so you know, that's what was happening. But also, on the insurance, which came up here and everywhere else, does that play into any discussion in terms of the contracting? I know it has something to do with you per se, and it is a state issue, but it is constant. Council Member, if I may, from a construction perspective, we care about insurance all the time. There are two programs that, with the Administration, there is a program called CCIP, which is the Contractor Controlled Insurance Program, that we're using for our entire borough-based jail program. Essentially, what that means is the design-builder has the insurance for everyone working on that project. That means they can negotiate better prices. That means they're not having the burdens of smaller firms trying to get insurance. And then we're also looking at a wrap-up insurance program, which would be the really holding-the-insurance program, to essentially erase those barriers. But it is something that we're working at, because we do hear a lot

(00:40:21)

about that.

(00:41:25)

And could you transfer that

(00:41:27)

all to the nonprofit childcare? Sorry, they are. That's where it's also hit so hard. No, it's a great question that we're happy to send back to her, right? I know what that

(00:41:42)

means in social services. I

(00:41:43)

know what that means. All right. Just, we all need to work on insurance.

(00:41:49)

The question is, my staff, lovely, to do the program with that. You got compliments on it from CM Stevens. Love to have money as a grant, as opposed to blah blah blah blah. Fine.

(00:42:04)

But God forbid the deadline comes and the paperwork isn't there, and they would lose all of their money. Or could they go back into what I would call the traditional contracting process?

(00:42:16)

My staff is hysterical that

(00:42:17)

they would lose all their money. CM Stevens, you're not alone in bringing up this concern. Oh, I'm sorry, CM Brewer. Okay, Cheryl, I'm sorry, she's very cool. That's okay. We do look alike,

(00:42:37)

a little bit. Yeah. Go ahead. Yes, so what about their money? We are very much building this plane and flying it at the same time. We just, it's going to crash if you do this. To make sure that this does not happen, and we are seeing signs that something like this should derail, we will get right in there and work with Council Finance.

(00:43:06)

I just think, I think Lisa's been out front, up front. You are going to lose everything if you don't do. Obviously, you're going to try to get them to help them with the paperwork, and so I got it. But I mean, my staff was like, they would get no money having done the contracts and done the work if in fact they don't know how to do the paperwork. So I'm just saying, I think then they could go back into the regular, so-called, as opposed to the grant, but they shouldn't have to forfeit everything. Is that something that could be written in stone, that they have support and everything, and then kill that plane and start with a new airline? Milkha noted all

(00:43:47)

right. Thank you. And the other question is, you have a lot of 700 unpaid invoices. How much has the, maybe you discussed this, discussed this at, is completely erased in your fines of the backlog? Council Member,

(00:44:07)

the Controller's report, so wow, April 2020, yes, yes, okay. So I am happy to, and I'm happy to sort of rerun the data and share it, because it has been over a year since that Controller report was released. Yes, it is. Yes. So let me start, big picture, contract registrations. We are at the moment, I can keep going. Yes, okay. Listen to the bell. Okay. So for contract, unregistered contracts and unregistered contract amendments, we're currently doing the work to clear out what we're calling it, clear the queue. Okay. And we're asking the agencies to go in and, everything that predates October 1, 2026, okay, we're asking them to identify what roadblock exists, okay, that prevents them from moving those actions to the Controller's Office for review and registration. And if they identify it's an oversight roadblock, whether it's MOCJ, OMB, or Law Department, we're going to help remove those roadblocks. If it's a Passport issue, we will help remove that Passport issue and try to find a workaround. Right now, the numbers are very, very high level, and with me, I can get you the numbers. So that's on unregistered contracts and unregistered contract for invoices that are in the queue. Yeah. As of, there are about a billion unpaid invoices that we can see in Passport. Well, that's what I had here. That does not mean that those are late. That's just what's sitting in the queue. Okay.

For what we count as late, as the invoice has aged 30 days and beyond, and what we are seeing in comparison to last fiscal year is a reduction in the overall cycle time. It used to take agencies on average 41 days to pay an invoice. Now we're seeing about 22 days, under the 30-day benchmark for a procurement and policy board standard, for 30-day prompt

(00:46:30)

payment. Okay. So overall, the numbers are trending in the right direction. I'm happy to do a snapshot of what we are tracking on, because right now what we are doing is performance management of the City agencies on contract registration and payment, and the numbers are in the right

(00:46:47)

direction. Okay. I mean, it sounds, because people have a lot of respect for you, the office is doing the best they can, but it is a constant, at every single hearing about this topic, we have been talking about social services. Dear, we bob, not everything.

(00:47:04)

But I don't know how you get the word out that you're actually getting somewhere. But something, just a suggestion: that people feel hopeful about getting the contract registered, signed off. I don't know, but

(00:47:17)

Thank you very much, and I know that you're working on the past. When we get people all day long who can't do Passport, a lot of time working them through it. Oh, but thank you, thank you.

(00:47:28)

Member, thank you very much.

(00:47:31)

CM Brewer. I want to just begin with a couple questions for the, that are kind of either for the Commissioner, for both of you, and then I'll jump in more on the Passport stuff. The hearing we had six months ago, where, if I recall correctly, basically what was explained was that we're not effectively tracking capital projects. We're not tracking capital projects in Passport, that we're not tracking spend and understanding how we're doing through that system. And that was the goal of the system, was for it to do that. I think in previous testimonies, and Alex was here for all of the hearings, so he knows, previously testified to that being the goal. One that we still have not achieved: does that remain the goal? We have a timeline to accomplish it? Is this something that is on our, that isn't an objective with a timeline associated? And if you think I'm misrepresenting, please, no, I think that has been the case. I don't see Passport as a project management, as a construction project management system. It is a procurement system, but for tracking spend, right? And so we're processing some of the payments through Passport, not all the payments, right?

(00:48:49)

And so now I don't, I think that if I misstated that, I don't mean it as a project management tool, but I think it's a tool for effectively tracking our spend, and when we're severely over budget, it's a way for us to know that and see that and be able to course correct or adjust.

(00:49:02)

Accordingly, you wouldn't be able to see the over-budget because the way that we see that, we take on projects. So say the Parks Department has, let's call it, the replacement of a rec center. They give us a project. They say, and I'm making up the numbers, I'm not picking on the Parks Department, they think it's a $5 million project. When we go through the front-end planning process, we look at everything and say, well, yes, the roof is at the end of its life, its useful life, but then there's also the HVAC that sits on the roof, which is at the end of its original life. So we're recommending that we do both. So what started as a $5 million project ends up as an $8 million project. But that's not a cost overrun. That is just a proper scoping of a project. So we won't take the cost increases to PASSPort. We already have the full funding, and so the only thing is, you'd be able to track our potential change orders on any given project, but not the cost increases. I think in the way that people think about cost increases, because that happens on the front end, to make sure that we're lining up with one actual construction costs and two, proper scoping of projects.

(00:50:18)

Projects. So, and just to... I do want to dig in a little bit further, but I wanted to cite this appropriately. We have the MOCS February 2022 roadmap for PASSPort, which included bringing capital project management into the PASSPort system. This was, according to then-Director Flores's testimony from four years ago. So, is that no longer an ambition that you all share? A viable kind of utilization of PASSPort?

(00:50:48)

PASSPort. No, we are looking. Listen, construction project management systems are incredibly important, and we are actually looking at updating our construction project management system, one that includes planning, tracking costs, tracking timelines, tracking steps. But that would be done inside, ideally, an off-the-shelf solution, so that we can better utilize the technology already out there. And by the way, every other capital delivery agency uses the same type of construction project management system. Does it? Does it, right?

(00:51:24)

And then there was this, and I thought that the report that Comptroller Lander put out, I think before he shut the lights off last year, his critique was that there was a lack of a comprehensive project management tool to track projects, and that it was happening in multiple places. I believe this is what you testified to six months ago as well. We're relying on multiple systems to track things, which is just unacceptable, right? And has to change. And if PASSPort isn't the solution, and PASSPort, I don't know, I mean, it's clunky, right? Then understanding what is the solution, I think, is really important. Yes. One of the first things I've done, as commissioner, was looking at all our technology systems. You are correct, Councilmember, that we have a project management system, we have an invoice system, and we have a timeline system. There's no reason for that. So we are looking. We do have a really good technology roadmap to update all those systems into one that makes sense, and that's easily useful for the project manager, but also for the contractor, and eventually for the public, if we want to do that.

(00:52:06)

And if I was following you, a moment ago, I feel like I totally appreciate you have said to me several times over these six months, you know, the agency will anticipate the cost of something is X, and then when they actually look under the hood, cost is X plus Y plus C. But what I'm concerned about, and I think that's going to happen once the architects and engineers analyze something, costs are going to be different than whatever city agency might have anticipated. But what I would want to make sure of is that when we have an estimate on a project, that we know, to spend, is happening, that we're staying within budget. I think what we really raised at that hearing six months ago is that I think too many vendors get away with submitting a bid at a lower price, and then making adjustments along the way and submitting mods that don't end up being that lowest price, and we could have gone with a better vendor that has a better track record, and we get sucked into those bad decisions. So we continue to want to see reforms in these areas. I'll give you a second if you want to respond.

(00:52:31)

Yeah, it drives me crazy too. We have seen that sometimes the lowest bidder, we don't feel like they can do the job that they're bidding on. So what we're doing is a couple of things. The thresholds for finding them not responsive or not responsible are pretty high, understandably. But what we're doing is a culture of evaluations, to make sure they're writing fair and true evaluations of every single contractor, because the evaluation, this is actually what the City determines as a basis for potentially finding them not responsive or not responsible. And I don't think historically the agency was taking that seriously. So that's one piece. The other piece, alternative delivery doesn't bound us by the lowest bidder. It is the best value, and that does not obviously account for just cost, but we also look at experience, we also look at the type of quality that they've delivered, and the teams that they're putting together. To me, the best value ends up cheaper in the long run than just following lowest-bid contracting. I agree. Those are reforms I think we should pursue together. I'm happy to hear you reference a plan to kind of revisit the Capital Reform Project Task Force that Director Solomon led, with then-Mayor Adams, some four years ago. We hope the Council will be a partner in that, and we look forward to more information and updates on that.

(00:53:32)

I have one more question for you, which is, relating to CM Banks' legislation. I understand that we need flexibility, that every project is different, and at the same time, I would think that standardization could improve timelines and reduce costs. So I think that you were testifying against it today, although you were diplomatic and nice. Could you just give a little more?

(00:54:29)

To me, there's a difference between standard designs, which the bill is asking for, and design guidelines. I'm a huge fan of design guidelines. For example, we were doing five bathrooms for the Parks Department with very strict and clear design guidelines. Do you want to tell us how much they each cost? $3.6 million each. Yes, $3.6 million. They're going to be done in a total of about 18 months, two times faster than they would have been done on their traditional design. But I do want to address that, because it's not just a structure. For example, we were at Cacino Park in Flushing yesterday, and the bathroom that we're building is in the middle of the park. There is no sewer connection, there's no electricity connection in the middle of the park. So I know the price tag can sometimes be daunting if you're just looking at the face value, but there's a lot of work that needs to happen for that building to be actually functional. And from the park, from the bathroom where we are building to the right public, right away, that's about half a mile of deep sewer and electricity infrastructure that we have to build. So those tend to drive up the cost significantly.

(00:55:02)

But how close is it to the velodrome?

(00:55:29)

It's actually very close. Okay, good. Yeah. It's right next to it. It's beautiful. Did you know about the velodrome and kissing the park? No, it's cool. It's very cool. Queens, you know, there you go.

(00:56:14)

I know I'm Brooklyn, but this, that you should know about, you see, my video next is a week. But you're really popping those out. How many videos a week are you doing? The type of infrastructure that a new bathroom inside a park requires is pretty significant. I do think it's important for them to understand, so that they know why the costs are so high. Okay.

(00:56:20)

One more question for a chair, for Commissioner Chohan. Okay, go ahead.

(00:56:27)

Thank you, Chair. When you talk about the infrastructure issues, is there a space where Parks has those capital plans laid out, so that we know what these costs are going to be before they happen? School Construction Authority, to where there's no real forethought, and sometimes agencies can become in their bubble, and our goals are very different. We want to say, hey, we have the funding, we want to do X, Y, and Z, and then you have your goals and what the funding actually looks like, and there's a huge disparity between the two. So was there anything that we can do to kind of do, which is not something that the City does, which is proactive work? Yeah.

(00:56:35)

Just a little bit, because then we wouldn't be here, right? Borough of Parks, and we have tons of parks and whatever.

(00:56:38)

But it would be great if there would be some sort of, certain parks and spaces and capital projects that we know that we're going to have to do. That, yes. A chair costs a million dollars, and no one understands. And I see the guys who work for the City nodding their heads, of course, you have to. But I think that there is a space where we must have some of the same language and some proactive work, so we're not daunted. Because what ends up happening is that we will say, this is what we want to do as elected officials. We ask you, you come back with something, but we get blamed. I don't want to get blamed anymore. Here with us, and it's not just an issue, it's a library issue, where an elected official will give $2 million. What, let's call it NYPL or BPL, or plus things, is a $2 million project. We take it, it turns out to be a $3.5 million project, and then the library system will go back to you and say it's a $3.5 million project. But by the time you add the other 1.5, it's been one fiscal year. Until then, when they give us the 3.5, it's now actually 4.22. So it's really, really frustrating.

(00:56:40)

But we do have a pretty good solution in the works. It's called the Bands Capital Planning, and what that means is we're going to be sending inspectors to all city-owned buildings and a couple of cultural institutions to do a full assessment. It's like Ames on steroids, a full assessment of the building to see what they need and what they will need in the next five, two, ten years, so that the agencies can do better planning ahead of time. So we're going to go in and say, the facade looks okay, but we think you're going to have to replace it in the next five years. The boiler looks okay, we need to replace it in the next three years. What do you think it will cost to do the assessment per building? We're going to, it's going to be about a two-week assessment per building. Right now it's about a three-hour assessment, so it's a much deeper assessment of the buildings. This was something that was partially funded a few plans ago that were rolling. We're almost done with the application, and it's going to be great, because then it'll allow sponsor agencies to be able to ask for money if they need it, but to just do better capital planning to make sure that doesn't happen. Okay.

(00:56:43)

Thank you, Chair. Well, I think that's unusually nice. Dismissed, Commissioner Ochoa. Um, so I just hope this is remembered in the future.

(00:56:48)

Back, and you know, you could stay all afternoon and not have to remember it. But I, you know, I'm just kidding. Thank you. Thank you for joining us today. We really appreciate it. The last chance, Council Members, if you have anything for the commissioner. I just want to say, as great as you are, the library doesn't like you. They don't like it. It's not that they dislike Paul particularly. Right. But we were in charge. I like you, but I like the libraries, but you all don't get along. We had a large meeting yesterday with the that she hosted with the cultural institutions and the libraries, all systems. I think we've made a ton of progress over the last six months. I think we are doing better, and a lot of it was just communication, and making sure that they understand our expectations, their expectations, and then involving them in the process. So I think we're doing much better. You should check with Iris to see what she says.

(00:56:51)

Always listen to Iris. Thank you. I want to say thank you very much, Commissioner and team, and I just want to say we appreciate your reference to Ames on steroids. We look forward to advancing our aims legislatively, as cooperative as we are in that endeavor. Nice to see you.

(00:56:52)

Director, we will now dig in to PASSPort. So our review found that the City has spent about a hundred and at least a hundred and twenty million dollars on PASSPort since its inception and design back in 2016, including 9.7 million with in-house on creation and updates, and $20 million plus with Accenture.

(00:57:01)

Could you just give us a very quick overview of the costs and the services that are provided under the IV value contract and the Accenture contract? Chair would be happy to. So, our number is actually a little higher than the number that we like to, the price tag we put on the PASSPort project so far. And the other price tag that's readily handy is the release seven work, which is six and a half million. But just to, again, take a step back, and I'll go into the weeds a little bit, so please indulge me. So two contractors, two contracts. We've got IV, IV is the software provider. We have a number of licenses, and we pay around two and a half million dollars per year for that license. We also have a relationship with Accenture. Accenture is what we call, for shorthand, our systems integrator, and we pay about seven and a half million dollars per year. So PASSPort as a system, per year, as a steady state,

(00:57:18)

The cost will go up, or you will see costs go up year to year if there are changes to the functionality, which we call releases, or there are upgrades to the system. So that is when you will see peaks of increased funding over the life of the contracts, and over the life of the project. Thank you. And so, just so I understand, those contracts, what is the renewal timeline on those contracts? The current contracts are set to expire April 2027.

(00:57:23)

And then you have a renewal option on them. We do not...

(00:57:25)

Oh, so does that mean you'd have to put out a new solicitation at that point?

(00:58:10)

Or what are your options? We could, and we did earlier this year. We did not see that through. Most likely we will do what we call a negotiated acquisition. And did they kind of to both of them?

(00:58:13)

Well, okay, fair enough. Um, how many staff positions at MOCS are focused on PASSPort?

(00:58:20)

You know, it's an interesting question. When we try to parse out how much of our budget goes to the PASSPort project. And I wanted to go back to just sort of your prior question for a moment. This extends beyond just the PASSPort project. This extends to all vendors who have a relationship with the City of New York. IV and Accenture are our partners in providing this citywide enterprise system. They've been our partners for ten-plus years now. Downs in our relationship with our vendors, and I hope that going forward, in our negotiations, we are a value partner to them, just as we are entering into those negotiations. But on your question around how many of our team members support PASSPort, it's hard to really parse out. And I'll give you a little bit of an anecdote or example. We have a team called our Procurement Operations team. Our Procurement Operations team maintains a relationship with our city agencies. For example, Commissioner Iko was here at MOCS. There is a MOCS member assigned to DDC, and so is DDC. It is moving its procurement contracts and payments through PASSPort. They will work with their MOCS Procurement Operations liaison, so that person is over helping them project plan their procurement, helping them advising them which procurement method is best. And then from time to time, if there are PASSPort issues, they will help on PASSPort. So, is that person designated to the PASSPort project?

It's hard to say a portion of their time is designated to it, but it's not a clean one-to-one. That person is assigned to the PASSPort project.

(00:58:21)

Do you have any way of kind of thinking about full-time employee equivalents, or anything that could give us some sense of scale?

(00:59:34)

Or do you have a way of how, if I mean, like, how would, yeah, how would you think about it? If we could certainly parse it out. Good. No, I'm maybe a less exact answer. Could you give us like a ballpark sense? Let's see. I would want to give you a precise response, Chair. I really would. So if I could, I'd take this one back. All right. Or maybe a different thing would be, like, how many folks are just on the technical side of managing the VALUE and Accenture contracts, that just like you have on a team there.

(01:00:42)

On our technology team. It's interesting, because we also have what we call our MAC Service Desk team. And our MOCK Service Desk team, in some, IT owns the relationship with our vendors, and so they are helping our vendors move through City contracting and procurement, and PASSPort is a part of their responsibility. So roughly maybe 32 to 40 people. But again, I would really want to come back to you on that number, right? Because your headcount total is a few hundred, 70 less than it should be, but we should talk. But so it's a significant portion of your headcount is focused on this, and a significant portion of MOCS's operations are dedicated to this technology management. Yes. Roughly, roughly could be as high as 20 or 30%, even higher, potentially. Just articulate, how is he involved in managing

(01:00:58)

PASSPort? Are they directly engaged in the day-to-day here?

(01:01:05)

Appreciate it. The last chance, Council Members, if you have anything for the... Commissioner, I just want to say as great as you are, the library doesn't like you.

(01:01:09)

They don't like it. It's not that they dislike Paul.

(01:01:18)

Particularly right. But we were in charge. I like you, but I like the libraries, but you all don't get along. We had a large meeting yesterday with the one that she hosted with the cultural institutions and the libraries, all systems. I think we've made a ton of progress over the last six months. I think we are doing better, and a lot of it was just communication and making sure that they understand our expectations, their expectations, and then involving them in the process. So I think we're doing much better. You should check with Iris and see what she says.

(01:01:51)

Always listen to Iris. Thank you. I, um, thank you very much, Commissioner, and team. I just want to say we appreciate your reference to Ames on steroids. We look forward to advancing our aims legislatively, as cooperative as we are in that endeavor. Nice to see you.

(01:02:13)

Director, we will now dig in to PASSPORT. Our review found that the city has spent about a hundred and at least a hundred and twenty million dollars on PASSPORT since its inception, and kind of design, back in 2016, including nine million, seven hundred thousand with in-value on creation and updates, and twenty million plus with Accenture.

(01:02:36)

Could you just give us a...

(01:02:39)

Kind of very quick, very quick overview of the costs and the services that are provided under the InValue contract and the Accenture contract? Chair would be happy to. So, are...

(01:02:51)

Number is actually a little higher than the number that we like to, the price tag we put on the PASSPORT project so far. The other price tag that's readily handy is the Release Seven work, which is six and a half million. Um, but just to again take a step back, I'll go into the weeds a little bit, so please indulge me. Two contractors, two contracts. We've got InValue, which is the software provider.

(01:03:31)

The one of new licenses, licenses up, and we pay around two and a half million dollars per year for that license. We also have a relationship with Accenture. Accenture is what we call, for shorthand, our systems integrator, and we pay about seven and a half million dollars per year. So PASSPORT as a system, per year, as a steady state.

(01:04:02)

The cost will go up, or you will see costs go up year to year if there are changes to the functionality, which we call releases, or they're upgrades to the system. So that is when you will see peaks of increased funding over the life of the contracts and over the life of the project. Thank you. So, just so I... those contracts, what is the renewal timeline on those contracts? The current contracts are set to expire April 2027.

(01:04:29)

And then you have a renewal option on them. We do not...

(01:04:44)

Oh, so does that mean you'd have to put out a new solicitation at that point?

(01:04:48)

Or what are your options? We could, and we did earlier this year. We did not see that through. Most likely we will do what we call a negotiated acquisition, and did they kind of do both of them?

(01:04:52)

Well, okay, fair enough. Um, how many staff positions at MOCK are focused on PASSPORT?

(01:05:12)

You know, it's an interesting question. When we try to parse out how much of our budget goes to the PASSPORT project... um, and I wanted to go back to just sort of your prior question for a moment. This extends beyond just the PASSPORT project. This extends to all vendors who have a relationship with the City of New York. InValue and Accenture are our partners in providing this citywide enterprise system. They've been our partners for ten plus years now. Downs in our relationship with our vendors, and I hope that going forward in our negotiations, we are a value partner to them, just as we are entering into those negotiations. But on your question around how many of our team members support PASSPORT, um, it's hard to really parse out, because I'll give you a little bit of an anecdote or example. We have a team called our procurement operations team. Our procurement operations team maintains a relationship with our city agencies. For example, Commissioner Iko was here at MOCK's. There is a MOCK member assigned to DDC, and DDC is moving its procurement contracts and payments through PASSPORT. They will work with their MOCK procurement operations liaison, so that person is over helping them project plan their procurement, helping them advising them which procurement method is best. And then from time to time, if there are PASSPORT issues, they will help on PASSPORTs. So, is that person designated to the PASSPORT project?

It's hard to say a portion of their time is designated to it, but it's not a clean one-to-one. That person is assigned to the PASSPORT project.

(01:05:22)

Do you have any way of kind of thinking about... full-time employee equivalents or anything that could give us some sense of scale?

(01:07:22)

Or do you have a way of how... if I mean, like, how would... yeah, how would you think about it if we could certainly, um, parse it out? Good. No, I'm not... maybe a less exact answer. Could you give us, like, a ballpark sense? Let's see. I would want to give you a precise response, Chair. I really would. So if I could, I'd take this one back. All right. Or maybe a different thing would be, like, how many folks are just on the technical side of managing the InValue and Accenture contracts, that just like you have on the... on a team there?

(01:07:31)

On our technology team. It's interesting because we also have what we call our MAC service desk team, and our MOCK service desk team. In some IT, it owns the relationship with our vendors, and so they are helping our vendors move through city contracting and procurement, and PASSPORT is a part of their responsibility. So roughly maybe 32 to 40 people. But again, I would really want to come back to you on that number, right? Because your headcount total is a few hundred, 70 less than it should be. But we should talk. So it's a significant portion of your headcount focused on this, and a significant portion of MOCK's operations are dedicated to this technology management. Yes. Um, roughly, roughly could be as high as 20 or 30%, even higher potentially. Just articulate. His involved in managing...

(01:07:51)

PASSPORT. Are they directly engaged in the day-to-day here?

(01:08:06)

Team there.

(01:08:06)

On our technology team, it is interesting because we also

(01:08:11)

have what we call our MAC service desk team and our MOC service desk team, and in some ways IT owns the relationship with our vendors. So they are helping our vendors move through City contracting and procurement, and part of their responsibility is PASSPort. So roughly maybe 32 to 40 people, but again I would really want to come back to you on that number, right, because your headcount total is a few hundred... 170 less than it should be. But we should talk. So it is a significant portion of your headcount that is focused on this, and a significant portion of MOC's operations are dedicated to this technology management. Yes, roughly — it could be as high as 20 or 30%, even higher potentially. Just to articulate how involved they are in managing

(01:09:10)

PASSPort — are they directly engaged in the day-to-day here?

(01:09:14)

Thank you, thank you, Chair, for the question. We are, you know, our involvement in the PASSPort project has ebbed and flowed. Initially, at the inception of the project, it was a project through the passage of time, there have been handoffs from OTI to Mocs. Mocs will always be the business owner of this project.

We are the procurement subject matter experts. More recently, we have asked to come into have some more strategic conversations about PASSPort, some of which you mentioned at the top, Chair, around what is the future of PASSPort, what is the future of e-procurement, how do we improve the user experience. So more recently we were having conversations with, in that team, on those bigger and larger questions, not on the day-to-day, so to speak.

(01:10:09)

Okay. Um, should they be more involved? I mean, I think generally OTI is pretty directly involved in most

(01:10:17)

technology management, most management of most critical technology infrastructure for the City.

(01:10:21)

I'm a little surprised that they're less involved here. What do you think they could be? An asset. Do you think it could free up Mocs' capacity, potentially?

(01:10:28)

Other important work. If they were more involved, I would welcome it. I would welcome it. It's a big project, it's a big undertaking, and having those who have something to contribute and offer is welcomed. Yeah.

(01:10:46)

I mean, it's just worth remembering, it's a system that moves tens of billions of dollars annually, has tens of thousands of users and hundreds of thousands of transactions, right? I mean, it's a big, complex technology endeavor. You would think that in IT. So maybe that's a future thing for us to raise with Katherine and Rodella Rosa.

(01:11:09)

And our friends at OTI, which is based in District 33. Just noting, um, adoption of PASSPort. So, um, I do want to just dig a little further here.

(01:11:21)

One other thing that has been made a bugaboo of mine: capital eligibility of PASSPort improvements. Could you just help us understand why improvements, the kind of updated releases and improvements that PASSPort are not capital eligible? And, I guess relatedly, is there any mechanism that we could take over this system and have it be City-owned?

(01:11:48)

Council Member, thank you for raising this. This is something that also frustrates our Mocs finance team. The way that the PASSPort project is structured, the way the contracts are set up, as I mentioned, we are licensing a software. So essentially we rent, we do not own, and so for capital eligibility that makes it a nonstarter under the Controller's directives. I think, my, I know this very, very generally, not deeply. My understanding is that the Controller has revisited the capital eligibility on software. I do not control the Controller, this Controller, or—

(01:12:31)

No, don't hold me to—

(01:12:32)

—that, that might have been the last time I will say that. I don't believe it will ever be backwards-looking. It will likely be forwards-looking around capital eligibility. Okay, so you don't think there's any way to get it into—there is one idea, and this is a very conceptual idea, and it would take a lot

(01:12:55)

of folks to buy in. We could purchase the intellectual property. The off-the-shelf solution, we have customized and configured the solution to serve specifically the City of New York. All of that work is owned by a valuable seller, or we are a willing buyer. We are very early. That is just one of the myriad of options. Now, if we were in a blue-sky or whiteboard exercise, you could have a new e-procurement system that is owned by the City of New York, built by City of New York technologists and City of New York coders. They build a system, and we would—but that is far out. That's a new system, right? That would be, yeah, that's if we're moving on.

(01:14:00)

Okay. Look, that's all.

(01:14:01)

Interesting and helpful. I think that if there are any conversations for us to try to have with the Controller's team, and in them, and try to help push, as well as with Law, and I think, I imagine, you know, there's an interplay between some of the ideas that you just laid out and the expiration of the

(01:14:26)

contract, and so we're

(01:14:27)

thinking about all these things together, and I appreciate you laying out some of the moving parts that you're considering. I just, you know, kind of rollout of PASSPort, I think delayed by COVID, nature just accelerator, finally kind of incorporated back in 2024. Just a couple of years, accelerator should take. Was finally 2024. Are there any stages of the procurement process or certain contracts that are processed outside of PASSPort at this point? Anyone we should be aware of? There are bits and pieces, but certainly all the mayoral agencies are in. The non-mayoral agencies are not in. Organizations such as the Department of Education, among the mayoral agents, among them mayoral agencies. There are some folks who are out, but for the most part, everybody is in. Okay. Yeah. Is it so that there's nothing that comes to mind that you would highlight or flag for us of folks that are continuing to operate outside of the system? No.

(01:15:45)

Um, among mayoral agencies.

(01:15:46)

I did. Are there any—the 2022 nonprofit task force, kind of getting, I think it was like getting nonprofits paid or something like that.

(01:15:58)

Um, referencing other old contract legacy systems at certain agencies forcing users to enter duplicative information. Are there any of these legacy systems still in use to your knowledge among the mayoral agencies? Not to my knowledge. That's not to say that it doesn't exist, and it might be underground, but for the most part, you know, we have to make sure that everybody's in—

(01:16:24)

—go. Um, how much is still

(01:16:30)

happening via email and not captured in PASSPort? For example, we've heard the need to adjust budgets because of indirect costs and COLAs, and contracts that need to be amended because of new needs that are handled entirely by email, and PASSPort would not actually reflect—

(01:16:44)

—those issues. Is that a common practice? Yet that's hard to quantify. I would say it's hard to quantify. The idea is that if you have everything in one system and there's one source of truth, it provides the visibility and provides all the advantages of everything being in one place.

(01:17:05)

I am sure that there are some processes that are happening as a result of just, you know, ease, necessity. It's hard for me to quantify that offline activity. Um, and this is something we've heard from the Controller's team over the past year. Could you help explain to me the interface between PIP and PASSPort, and have there been conversations to more closely link these systems, or integrate these systems, or having the Controller be a user of PASSPort? Is any of that stuff on the table right now? Certainly there have been prior conversations around the relationship of PIP and PASSPort, and you worked in the Comptroller's—

(01:17:53)

Office. I did. So you have

(01:17:54)

seen. Years ago, both sides of this. I have, yes. So most recently, with 2024, I believe, a portion of PIP was decommissioned, and a piece of functionality was stood up in PASSPort, and this is around the subcontracting. PIP still exists. However, it exists. It's jointly owned by the Mayoralty and the Comptroller. It involves the City vendors needing to disclose information so that they can effectively be paid electronically. Um, those are some that would be quite the lift if we were to ever completely subsume PIP into PASSPort. But so, though some of those conversations are not on the horizon, better linking or integrating the systems, I know it is something that we should be thinking about, because did the system talk effectively to one another today? That I would have to take back, and certainly, I'll have to take that one back. Okay. Okay. Okay. I think

(01:18:46)

Mocs testified back in 2019, when Justin Brennan chaired the Contracts Committee, that Release Two would be the final major release on PASSPort, so I don't know—

(01:19:12)

Well, know, well, there, we—

(01:19:23)

You can thank Alex. He was here and asked Alex to, and asked Justin to ask the question back then. Seven years later, we're on Release Seven. Um—

(01:19:24)

Could you explain? I know you did your testimony, but just once again, succinctly, the functions that will be added through Release Seven, and in particular, nonprofits will now be able to submit invoices while budget mods and budget approvals are still pending.

(01:19:36)

Council Member, you said—it, okay, that last part. I can add, I can give you a sense of scale. So last fiscal year, we counted 10,000 budget modifications.

(01:19:51)

So during the pendency of those 10,000 budget modifications, which on average, um, for five days, so 10,000 times for those five days, there was an inability to submit an invoice into PASSPort for review for payment. Um, but fast forward, we hope for everybody to have a smooth delivery of Release Seven, that will no longer be a stop. A pending budget modification will not stop an invoice submission.

(01:20:04)

Great. I will say, I think this is probably the number one complaint we've heard about PASSPort, and so it's really great that that's being fixed. It's not the only complaint we hear about PASSPort, but I know that my Vice Chair and my colleague do often get a lot of PASSPort complaints, so I'd be interested if they have other items on their

(01:20:37)

list of needed PASSPort changes. I think that, and just to confirm, you continue to be on track for an early 2027 release? Yes. Great. Do you keep a running list of kind of reforms requests, of reforms or improvements, modifications that agencies, nonprofits, your own staff have identified? Kind of like a wish list of changes to PASSPort? We do. It's very long. We cannot do all of it. Okay. All of it? No. It's good to know it exists, because I mean, look, as far as I understand it, and the Vice Chair can clarify, but I think the Council really pushed for paying for these, really, seven changes, and we continue to want to be a strong partner in advocating for updates if this is the system we're using. Um, have you done a cost analysis of the changes on this list? On this list, is there any more you can share?

(01:20:38)

So, Chair, in any thinking about this and what is the right approach about this going forward, there is an instinct to say that let's change the system to make it better, but there's also, there are other options, unless not change the system, and maybe let's, I think, think about maybe could take out of this system, to deprecate pieces of the system to make the experience better. Hmm. I'm not saying that that's where we are, but we are in a—after our seven, when we catch our breath, going to take a moment and pause and think through what does make sense. Does it make sense to continue to build it? Doesn't make sense to stay the course. Doesn't make sense to maybe take out pieces of functionality and have them

(01:20:59)

somewhere else. Those are the types of conversations that we will be having, you know, soon. Our seven is our priority, but sometimes it is underappreciated. It's, what's the saying, addition by subtraction. So we're open to exploring that as a potential path forward. Also, okay, any short list of potential modifications, additions by subtraction, or just updates that you want, you might share, that you think are some of the priority things to consider post Release Seven? So, CM L, we will have to confront: what is the technology solution for the grant pilot? What are the technology solutions for the code initiatives? Should they pass Election Day? Those are things that we have to grapple with, that we have to do versus what we want to do. So those are things that I would love to come to you in partnership and think through how we solution that. I think that in a while, I'd love to join you to have some conversations with stakeholders of like, what are they thinking, and create an opportunity for some constructive, as you kind of move beyond Release Seven. So maybe for next year, I—

(01:21:01)

I was struck. My chief of staff, Molly, and I, I didn't recognize Molly. I didn't recognize you in my opening remarks. I forgot to do that. I want to just take a moment to thank Molly, who's the best, belatedly, but Molly is the brains of our operation, and I'm grateful all the time for the opportunity to work with her.

(01:22:52)

Molly, Molly, and I chance to sit down with a local nonprofit in our district earlier this week, and there are medium-sized nonprofits, competent, and they told us it takes their staff member half a day to submit an invoice in, um, in PASSPort. And I don't know if that's similar to the kinds of things that you both hear from nonprofits in your communities.

(01:24:36)

Does that shock you? Um, should it? I mean, I don't, you know, like, what, how do you respond to that? It should not be the case, and I have heard it before, and it goes to what I spoke of earlier, that we do know that there is room, there's some room for improvement, and there's some gaps.

(01:24:57)

And anecdotally, I think there could be a spectrum of reasons why it is taking that amount of time. It could be that there is a system issue, there really could be a system issue. It also could be we've got to do a better job training the users. It could be that there are members who are in the system for periods of time, and once you're in the system for a period of time, you sort of know where to go, how to navigate, and then once you step away from the system and you haven't been in the system for a bit, a little bit of that muscle memory has been lost. Um, but yes, I have heard other providers share that there's an expectation of how long tasks take, and PASSPort is beyond what it is. It's longer than they hoped for. I just want to share, when we sat with them, they explained to us and showed us, they have all the information neatly organized in an Excel spreadsheet.

There's no mechanism for a bulk upload of an Excel file or kind of recognition of prior information, so they have to find the right contract, mid-seven, kind of nearly identical entries in the same contract, to create a new invoice, upload the budget again even though it hasn't changed, then go through each line item entering the same service dates, and every one of them entering the invoice amount, the quantity, price, dozens of fields that have to be transcribed from existing documents into the right boxes, all in PASSPort, and each contract is different, agencies flip what info goes where, and it's just easy to make errors as a result. And so it just, it was surprising to me how unfriendly the user experience is, and it's like, you know, these are nonprofits that are thin and trying to do their best, and it just, I was like, really empathetic to just the challenge that that staff is dealing with to get this information submitted, and submitted correctly. So, you know, I think that, I know that, you know, Mondo is here to offer technical assistance, and you guys have a help desk to try and help people through this stuff, but it's just struck me that this is a lot harder than it should be. So please—

(01:25:24)

I just want to add to that. I didn't want to go through, because I know this is a topic that Chair would have brought up, but it's just tons of emails to that effect. And I don't know how to address it, but it doesn't help people who want to work with the City. And I have a horrible feeling some groups say, I don't want to work with the City, I'll just stay in a private, and they could be some of the best programs. So I don't know how to, like I said, I don't know how to do it, but they don't know whether their submissions are complete. That seems to be a big issue. As an example of something specific, they don't know whether it's user error or technical issues. It's very opaque. So, and I don't know whether you have, do you have like a 24-hour, I assume some people do this off hours. We do have some off hours. You have some phones. Okay, that's great, but all of that is still not addressing this problem. Thank you.

(01:25:48)

Thank you so much, Cosima, Myra Brewer, as always, for just kind of having her finger on the pulse of the issues. How is the system supposed to work for frequent documents like budget docs or insurance forms? I don't remember, but I think CM One created the legislation on the document vault, and it sounded really good to me. It doesn't sound like it's working as maybe envisioned. If I could, you speak a little bit to, like, that we hear from different, from like vendors, from nonprofits, of like, we have to submit different insurance forms with different agencies for every single contract, because every agency wants the name of their agency on the contract, not just the City of New York, and that we have to resubmit the same documents all the time, and it's just frustrating, and as explained, it's just kind of a slow process. Is there, I guess the question I'm trying to ask is, like, how are, how or should things work with documents that need to be submitted time and again? Chair, E—

(01:25:52)

There could be a spectrum of reasons why it is taking that amount of time. It could be that there could be a system issue. There really could be a system issue.

It also could be that we have got to do a better job training the users. It could be that there are members who are in the system for periods of time, and once you are in the system for a period of time you sort of know where to go and how to navigate. Then once you step away from the system and you have not been in the system for a bit, a little bit of that muscle memory has been lost.

But yes, I have heard other providers share that there is an expectation of how long these tasks take, and PASSPORT is beyond what it is. It is longer than they hoped for. I just want to share, when we sat with them, they explained to us and showed us that they have all the information neatly organized in an Excel spreadsheet. There is no mechanism for a bulk upload of an Excel file or kind of recognition of prior information. So they have to find the right contract, mid-seven kind of nearly identical entries in the same contract, to create a new invoice, upload the budget again even though it has not changed. Then they go through each line item entering the same service dates, and every one of them entering the invoice amount, the quantity, the price. Dozens of fields have to be transcribed from existing documents into the right boxes, all in PASSPORT. Each contract is different, agencies flip what info goes where, and it is just easy to make errors as a result.

So it was surprising to me how unfriendly the user experience is. These are nonprofits that are thin and trying to do their best, and I was really empathetic to just the challenge that staff are dealing with to get this information submitted, and submitted correctly. I know that Montes is here to offer technical assistance, and you all have a help desk to try and help people through this stuff. But it just struck me that this is a lot harder than it should be. So please—

(01:28:26)

I just want to add to that. I did not want to go through it because I know this is a topic that the chair would have brought up, but it is just tons of emails to that effect.

I do not know how to address it, but it does not help people who want to work with the City. I have a horrible feeling some groups say, "I do not want to work with the City, I will just stay in the private sector," and they could be some of the best programs. So I do not know how to do it. As I said, I do not know how to do it, but they do not know whether their submissions are complete. That seems to be a big issue. As an example of something specific, they do not know whether it is user error or technical issues. It is very opaque.

I do not know whether you have a 24-hour line. I assume some people do this off-hours. We do have some off-hours. You have some phones. Okay, that is great, but all of that is still not addressing this problem. Thank you.

(01:29:29)

Thank you so much, CM Gale Brewer, as always, for having her finger on the pulse of the issues. How is the system supposed to work for frequent documents like budget docs or insurance forms? I do not remember, but I think CM Won created the legislation on the document vault, and it sounded really good to me. It does not sound like it is working as maybe envisioned.

If I could, could you speak a little bit to what we hear from vendors and from nonprofits? We have to submit different insurance forms with different agencies for every single contract, because every agency wants the name of their agency on the contract, not just the City of New York. And we have to resubmit the same documents all the time, and it is just frustrating. As explained, it is just a slow process.

Is there—I guess the question I am trying to ask is, how should things work with documents that need to be submitted time and again? Chair—

(01:30:42)

There are two issues. There is the variability around what agency is expecting from the providers, and from the providers' perspective it likely can seem a little bit like whiplash, or getting bounced back and forth, when they are potentially providing the same services or the same insurance coverage documentation. So there is that issue. Yes, there is a need to standardize, to the extent that we can, the document requirements that the city agencies are putting on our providers. The other thing around the technology on the document itself, and I would like to explain, document vault is like a Google Drive. It is supposed to be a vault, somewhere where you upload your documents and you are able to readily retrieve them. I do know that there have been issues throughout the time that we have introduced Document Vault into PASSPort. I will say that over the Indigenous Day weekend we did do an unnecessary upgrade to the document vaults that Council One legislated around. That was a necessary upgrade. We were a little bit behind on doing that, but we are on the other side of that. And I have learned in overseeing this technology project, even though I am not a technologist, that a quiet upgrade is actually a good upgrade. We don't want to hear about an upgrade. So we are on the other side of that. Yes.

(01:32:23)

Thank you. That's helpful. The help desk. I think you testified today to a reduction in average response times on the help desk, a significant reduction, which is great. Could you just elaborate a little about prioritization

(01:32:41)

for urgent requests and how you do that? I am more than happy to do that. We are talking a lot about technology today, but really, when it comes down to it, we rely on our people to do this. We rely on our people to identify the priorities and actually prioritize the work.

(01:33:04)

We have a really great leadership team overseeing the service desk. She leads this organization, and one of the things that will help prioritize how the work gets triaged and what gets worked on first. For example, you mentioned there is some anxiety at the City Council around the discretionary grant process and whether or not all of the agreements are going to get into the pilot, as we are hoping. I am going to be very transparent about it. There was an issue with PASSPort around uploading some documents to the prequalified list, and because we know that the discretionary grant pilot is a strategic project of ours, we were observing in PASSPort, and resolution of those issues was prioritized because we know we are in a short window to get this right. I can share about how we prioritize the service desk work. I will pick on Commissioner Hawa again, because he was here. Let's say he has a bid that is set to close tomorrow, on Friday, because we know that those who are interested in competing for that opportunity are in the system, and there is a time sensitivity around getting their bids in. We will prioritize the issues that those who are interested in competing for DCAS did so. Those are some examples of how we prioritize the work. That's helpful. We've heard a healthy amount of feedback from agencies on changes they want to see in PASSPort. I'm sure you're keeping that list. I'm sure their input is on your list. My favorite division in the Law Department.

I'm not supposed to have favorites.

(01:35:11)

But is the Contracts and

(01:35:13)

Real Estate Division. They're my favorite. They're great. There are just so many smart people over the years that I admire so much, like Steve Stein, Cushman, and Howard Friedman. And I'm

(01:35:20)

Rita, like.

(01:35:21)

Just a very impressive group of folks. No disrespect to the other divisions in the Law Department, but we all have favorites.

(01:35:30)

Something we've heard

(01:35:32)

from them is that they would love to have simultaneous OMB and Law review in PASSPort. Is this something that is on your radar? Do you think it's something that we could consider incorporating into a future release? How could we make our friends in the Contracts Division at the Law Department happy? Yes, it's something that is on our radar. There is a particular set of things that they would like to see in PASSPort. We have identified it, we've tagged it, we've cataloged it. Yes, I'm open to having those

(01:36:07)

conversations. Do you have any sense of

(01:36:09)

I'm sure there are other reforms they would want to see as well, but is it possible to even provide a ballpark sense of cost for us to try to make a change like that?

(01:36:16)

I do not believe we've estimated the cost, but I will take that back. Okay. Cool. Some questions just on metrics and performance. The 2026 Citywide Indicators Report showed that the median invoice processing payment was 14 days in 2019. The invoice payment timeline in the accelerator was reportedly six days. Is there any ability to identify as this more of a platform issue or an agency user issue? Any ability to help diagnose the cause of those delays? If the data points I'm using, if I'm comparing apples to apples—

(01:36:25)

Some questions just on metrics and performance. In the Citywide Performance Indicators report for 2026, it showed that the median invoice processing payment time was 14 days in 2019, and the invoice payment timeline in the accelerator was reportedly six days. Is there any ability to identify whether this is more of a platform issue or an agency user issue? Any ability to help diagnose the cause of those delays? If the data points I'm using are... if I'm comparing apples to apples...

(01:37:07)

Look, yeah, you don't have the 2019 accelerator data tattooed into your brain.

(01:37:14)

That's fair, but if it is accurate, and a guess for why we're looking at that, or is 14 days as a median invoice payment, is that kind of a reasonable timeframe?

(01:37:27)

At a very high level, I see that the scale of city contracting and nonprofit contracting in particular has grown exponentially over the COVID years. That could, and this is tied to a piece of legislation that you've introduced, the procurement, and also agency staffing capacity has not kept up. Open question, something worthwhile for us to look at.

(01:37:56)

Fair. That's why we introduced it. I think we were looking forward to having a hearing on it. The—

(01:38:06)

Share of contracts registered in 2026 that were registered after their start date. Do you know that data

(01:38:15)

point? We have the FY25 data. Just wondering if you have updated. We do have the FY26 indicators. I want to say that we have some room to improve. I believe, just off memory, on-time registration was 69%. Hereunder with 6:00 hamburgers, because I thought what I was looking at for FY25 was that 72% were registered after the start date.

(01:38:45)

But we can begin. If it's something we could follow up on in writing, I think that would be helpful, just to have the 2026 indicators on how we're comparing to previous years.

(01:39:01)

Okay. I wanted to ask about the median cycle time for look-back, since Alex was highlighting 2019 City Council Contracts Committee hearings. We did look back to what Dan Simon said then when this question was asked, and he basically said that the number of days doesn't really matter. There are apps for bids, so they could start the RFP process two years before the contract is going to begin, or nine months, or whatever, and what actually matters is if someone's getting paid on July 1 when the contract starts. That was his argument. You should tell me if that's the same argument that you would make. But the data on the timeline for the competitive sealed

(01:39:47)

proposals rose from 386 days in FY25 to 527 days in FY26. To be fair, the median length of time for competitive sealed bids declined year over year, but just wondering, any further, is Dan's explanation of this the right explanation? Do you think this is an irrelevant data

(01:40:11)

point that we shouldn't worry about, and that that is when people are getting paid, not how many years an agency plans preparing for an RFP? I think multiple things can be true at once, and I think the context will matter. I do understand, I do understand Dan's point. When it's really about predictability, and if the provider is expecting July 1, let's say 2027, to have a contract in place, and it's in place, I'm not sure how impactful it is that the agency and their planning activities initiated it maybe 18 months ago. So from that perspective, that justification does continue to resonate, and I think that's fair. I do want

(01:41:12)

to drill down on something that we've discussed a bit over the course of the year, which is PASSPort as a management tool. I think one of the most promising elements of PASSPort from a decade ago was that it would serve as this management tool that would help us improve cycle times and identify and track specific issues that are causing delays. It seems to me like the reporting capabilities of PASSPort are very clunky and hard for us to benefit from. Could you explain the reporting capabilities of PASSPort, if that isn't too broad a question? And then, do the agencies have access to those functions, or is that just a Mock? Is that just Max's purview? So on the reporting front, the amount of data that is in the system is vast, and with so much activity happening in the system, being able to extract what you need and have a report to either tell you a compelling story or provide operational support, there is a whole discipline around reporting and developing reporting, and what you want to do with those reports. Are they to provide early insight, or are they to prompt action? That practice requires a lot. There is

(01:42:59)

a lot of reporting capability in PASSPort, and there are a lot of things that Mock itself has pulled out of date, pulled out of PASSPort, and we've prepared our own reports. I value Accenture to make some reports readily accessible in PASSPort. So there's a lot to unpack there. But from the Council's perspective, one of the things I would lift up is that we do have PASSPort Public, which is a database open to the public. We also have, for those who are interested, and I'll lift up the Controller's Office Checkbook database, which provides a lot of information. For the agencies themselves, we do work with them to develop reporting tools that will move their work that are appropriate for the agency's work, not appropriate for public consumption. I recall from conversations with Roman and the leadership team at DCAS that they had worked with you all to pull some reports on spending on master contracts, and my recollection was that it took a few months to pull it. Could you help us understand, and my recollection from them at the time of the conversation was that they had not been able to get a report like this previously, so I imagine it was a relatively heavy lift on your all's part. It took months. Not an easy thing to do, but important. Could you do that? I guess you've spoken to this a little further on, like why it's so hard to get these reports out of PASSPort. Do you know if the data that was ultimately provided to DCAS was helpful in understanding master contracts?

Were there insights that have helped shape better policy as a

(01:45:09)

result? I am familiar with that particular DCAS request for a report and information pulled from PASSPort. I'll have to just, again, based on memory. So big picture, DCAS is responsible for lots of required reporting from a variety of counseling. Required reporting is a batch of them. We also produce a lot of reports on not just procurement, but on spending, and also on MWBE utilization. So we do prioritize our legally required reports that we have to do. For ad hoc requests, sometimes they fall into a queue, and I'm not saying for sure, but just generally speaking, sometimes that attributes to the delay on how fast we can turn around and report. I remember seeing that PASSPort, that particular report. What is beneficial for reports in that particular instance, and in others, is when you can see patterns emerge from the data. Because there was enough information in that particular report, that pattern was very informative, but the pattern is also informative too, maybe predictive in how we move forward. So that's my memory on that one. Without going too deeply into that one, I think

(01:46:58)

Is there, does PASSPort allow for real-time tracking of key metrics that are priorities for you, like contract registration, budget modification approvals, invoice payments? Does PASSPort serve as an effective tool for you to be able to run reports and get good answers on how efficiently you are processing these things and getting this work done? In part, certainly the information is there. The data is there. We do rely on some supplemental tools to help us do what you're describing. Also, that's very common. There's a tool, Power BI. Power BI is a very well-known tool for taking a lot of data and visualizing it in a certain way that's very easy to consume. So from time to time, we do use Power BI reports. Okay. Um, more topics, and we can call it a day.

(01:48:08)

I'm just interested in how

(01:48:13)

you evaluate PASSPort, especially as you think about looking ahead to a contract deadline. Are there ways, did they evaluate an eccentric contract, have performance metrics connected to them, where performance component? Are there metrics for PASSPort as a whole that you evaluate the system's functionality on? It's a great question. It's a great question.

(01:48:45)

That is worth continuing to evolve our thinking around. Certainly, some of the things that we focus on at a very rudimentary level is we want the system to be up. When I try to log into it, it's up, and you can log into it. In preparing for this, we took a look back. The system was up, I want to say, it was up 99.1% of the time, or even more than that.

(01:49:15)

So the system wasn't

(01:49:18)

out. It wasn't down. So that's certainly positive. The other thing that we track, and that's on the technology itself, is, you know, I'll rattle off some stops. To date, the number of registered contracts is 35,330. The number of amendments is 22,605, and those $187 billion for the amendment value, $27 billion. The number of invoices dispersed is 472,000. For fiscal year 26, the number of invoices created is 135,000, and that's a 12% increase over 25. So we certainly see that the workload of the City of New York is being supported in the system. We're also tracking the number of vendors who are in the system, the number of agencies who are in the system. The number of vendors is about 34,000. The number of active agency users is 123,000, and we see that the traffic in the system, about 87,000, used the system last year. So those are some of the metrics, and those are around the technology itself. I will say percent. What is more important to me is that some of the things we were speaking about earlier, on-time contract registration, on-time payment, and the technology should be supportive of the business. That's

(01:51:06)

helpful. I mean, I think broadly, the system works. We're processing a phenomenal amount of activity through it. It's just, I think, the question of what does it work as efficiently as it should, and does it meet our multiplicity of needs as efficiently as it should? But I appreciate that it is effective, and we are executing on the things that we need to as a city. And the data points that you just referenced are quite remarkable. Just briefly on DOE, we kind of announcing a new procurement system. Did they consult with you and the Mock's team on this decision to procure a separate contract, rather than finally adopting PASSPort or becoming a PASSPort user? I certainly was unaware of those conversations. There were some prior conversations in the last administration of potentially having come into PASSPort. At that time, there were some governance questions that we— There will always continue to be government conversations around the technology solution serving the mayoral agencies versus DOE, and we did not resolve those governance issues. I do understand, or do have knowledge of that. There's some space to modernize the procurement and contracting systems at DOE.

(01:52:43)

Yeah, I just.

(01:52:45)

I just wish that we were all working together on the same page. On there, the biggest agency in the city, and it just, if they're going to be taking a whole new direction, did it make sense for the city as a whole to take a direction with them, or are they going to continue to kind of operate on their own silo? And then I just briefly would like to ask about the ballot question, since they feel timely.

(01:53:09)

A valid question. Several procurement policy boards set the contents of the vendor questionnaire and allow certain vendors, like small businesses, to file less paperwork. Good thing. Can you expand on what impact this would have on vendors, and if approved, how would MOCS implement this? So Chair, thank you for raising this, because election day is around the corner, and early voting is already opened. So on this particular question, have yet, I have not voted yet. I am waiting to get my sticker on actual election day. All right, have not, doing more research onto the ballot questions. That's not the— Outstanding. I'm going to follow all the social media. Okay, well, maybe your testimony today will help educate people about Question Two and whether they should support it.

(01:53:43)

Waiting to get my sticker on actual election day. All right, having not done more research on the ballot questions, that's not the... Outstanding. I'm going to follow all the social media. Okay, well, maybe your testimony today will help educate people about Question Two and whether they should support it.

(01:53:59)

Yes, yes. So on that, overall, the procurement rules and the policies, it's been a collection and layer upon layer, and often what happens is something bad will happen in the contracting space and then the procurement space, and folks, with well-intentioned... will put a policy in place that served a purpose for a particular set of circumstances and a particular era. However, what the government and we all struggle with is doing a look back and asking, does that still serve us? Something that was put in place 10 years ago, 20 years ago, 30 years ago. I want to say that the VENDEX, or the vendor questionnaire, the principle questionnaire, that's probably been around for 30 years, if not more. So it is time for us to take another look. It just makes sense that we are not a one-size-fits-all approach. There are lots of different organizations that contract with the City of New York, and it does make sense to have a little bit more of a tailored approach and different risk allocation measures for what we're seeing in the contracting activity. The proposal would allow the Mayor to delegate to agency chief contracting officers the approval of contracts over $5 million that are awarded without competitive bidding,

(01:55:23)

which the Mayor cannot delegate today. The Commission estimated that the delegation could save one to two weeks on a procurement.

(01:55:26)

Do you have an estimate of how many contracts this would impact, like how many contracts we're looking at that are over $5 million without a competitive process? And if approval is delegated to an agency chief contracting officer, what role would MOCS play in reviewing those contracts? I can come back with the number. The number is not great, it's not large. I think it's in the thousands. Oh, you think thousands of contracts over $5 million without a competitive process?

(01:55:32)

Process, maybe, depending on the year, but we can provide some numbers. We can provide some look back and...

(01:55:59)

Provide some. I would have guessed a smaller... what did you guess? I guess it was Molly. What did you think? Molly doesn't... know. I would have guessed a couple...

(01:56:05)

Couple hundred. Couple hundred. You...

(01:56:11)

Be...

(01:56:13)

Closer. But yeah, yes. And when we're confronted with this question around delegations, and this applies to question number two but then even beyond, delegation is not abdication. Delegation is a controlled tool to allow some things to move based upon the circumstances. We will still retain oversight, and we will still try to... the accountability. We will do spot checks. And the other thing is we always want to improve our agency chief contracting officers, and we do that through professional development, and we will still maintain that. The proposal would also make permanent the use of a public comment period in place of a public hearing for contract awards, and would allow the Procurement Policy Board to raise the contract value that requires public comment...

(01:56:14)

Beginning in 2030, the Commission estimated that the proposal's reforms together could save up to 30 days on a procurement. Do you agree with that estimate, and how often are hearings currently held?

(01:57:12)

Now, I do agree with it. Was it your... estimate? No, it was not my estimate.

(01:57:25)

I appreciate that, though.

(01:57:32)

I also, going back to my earlier point about procurement being this collection of things that have evolved over the passage of time, public hearing and public comment have had their moment in time. And so much of what we do now, putting information publicly available on the website, sort of C-sheets, the public notice, and so doing away with some of the more rigid requirements that exist in the Charter, those are all welcomed evolution of and modernizing procurement and contracting. Just tell me again, how often are these hearings held? Is it more than once a month? I think it's less than once a month. Oh, so really it's less than once a... believable. Will it ever come? Yes.

(01:57:35)

It depends. It depends.

(01:58:21)

Mostly for the shelter.

(01:58:22)

Yes, it's for the shelter.

(01:58:25)

Contracts. People show up in less for other stuff, or particular procurement that happens to be controversial, as much as that happens.

(01:58:26)

Because I felt like when I was involved in shelter settings, people would have those contracts on their radars in a way where they could just go and scream about something that they didn't... like a little bit of NIMBY happening. Yes, yeah. Okay, okay. Um, are you okay? I think that covers all of our questions for the day. Thank you for making yourself available and for your thoughtful answers, and I think the informative conversation, we really appreciate it. So thank you so much.

(01:58:36)

Director Yu. Oh, what? Oh, yeah.

(01:58:47)

Okay, thank you so much. I really appreciate it. I'm good. Thank you. I have to now read something out loud that says, in advance of a public comment period, I just need to find my notes here. We go. I now open the hearing for public testimony. I remind members of the public this is a formal government proceeding, and decorum should be observed at all times. As such, members of the public shall remain silent at all times. The witness table for people who wish to testify, no video recording of such views from the witness table for the members of the public not present. Audio-video recordings of this testimony, but submit transcripts of such recordings to the Sergeant at Arms for inclusion in the hearing record. If you wish to speak at today's hearing, please fill out a speaker card with the Sergeant at Arms and wait to be recognized. Once recognized, you will have three minutes to speak on today's hearing topic. Have you written a statement or additional written testimony you wish to submit for the record? Please provide a copy of that testimony to the Sergeant at Arms. You may also email written testimony to testimony@council.nyc.gov within 72 hours of this hearing. Audio and video recordings will not be accepted. We will now call up the first panel, which involves Charles Diamond, and online we have somebody else. Thank you both. We'll start with Diamond and then go online. Hello, good afternoon.

(01:59:00)

Chair of the entire Council. How are you?

(01:59:09)

Doing. I'm going to repeat a stat you proved you saved many times before, but regarding how much we're spending on PASSPort, and given what we're doing, we talk about, I think, $400 million, $40 billion annually is a good estimate. This year, with the report that was just released from 36 years before that, we're closer to 45. $40 billion annually, and our benchmark is 10 million for maintenance, that's 0.025% of the total OTP spending. For MOCS, the only agency responsible for any of the spending on passports, is 14 this year. That's down from 2.2 million the year before. As I said before, we're not going to get better procurement outcomes unless we invest in it and we actually care about it. I think Director, you spoke incredibly honestly and powerfully about maintaining the system and the importance of doing that, but you also mentioned the list, which I think we've all seen at various different times, and it's very long. We know what to do. I would really urge the Council to get the administration to take this more seriously, where they're going to put the money, not just into MOCS but also to the staffing at the different agencies, into more dynamic standardization and the change of management that requires. Not just spending on PASSPort. So really, I just wanted to point out once again the disparity between what we're asking the system to do, which is $40 billion a year of transactions, and what we're willing to spend to maintain it.

So I think we need to be realistic about that, in particular when we talk about these persistent problems that have not gone away. I want to bring up a couple of things that came up. You mentioned the DO collaboration. Of course, we've been going through a kind of 2019 history. The Comptroller's office, there was an agreement made based off of some scandals that DO would work closely with MOCS and basically take a lot of MOCS's advice, and do things like that, send some money to MOCS to observe. That's even before the potential incorporation into PASSPort. Those efforts are clearly no longer there. And I think when we see it, do again, saying we're bringing every resource to bear, we're going to create a new system. These are problems that we've known about for a very, very long time. So I do think connecting the issues of how much are we spending to support procurement versus what's going on is very important. It would be scary if they end up spending $25 million on a solution when we're not willing to spend that on something. That's the whole thing. Um, ballot proposal number two. Briefly, I would mention with the public hearings process, I was part of the team that made that happen back in the day. We got public comment on less than 1% of all contracts. That was the official line. My estimate, which you testified to the State Legislature many, many years ago, was 25 days that we saved by going to online notice and comment compared to the old process. But it's what we're doing right now.

We have to do it. I certainly think everyone should vote yes on both of these fantastic proposals across the board. I would note, Chair Louis, on the idea of the approvals for those contracts over $5 million, as I've mentioned, another hearing as well, that's a bit of a red herring that all frankly can all be done. The really, really most fantastic thing, I think, is a mandate for meetings for the Procurement Policy Board, which will really make sure that we can't ignore reform. Thank you.

(01:59:18)

Thank you. I will note for the record that it's up to the administration and

(01:59:27)

choose to have as many Procurement Policy Board hearings as they want. They don't need a ballot amendment or a Charter amendment to have quarterly meetings, but mandating it is a welcome thing. And with that, I will kick it to Jesse Fei Parrot.

(02:00:21)

Online, welcome Jesse. You begin. Chair and members of the community, thank you so much.

(02:00:23)

For having me today. My name is Jessie Fay Parrot, and I'm a policy analyst at the Human Services Council. We are a membership organization representing over 180 human services providers across the state. HSC serves as an advocate and intermediary between the sector and the government. We take on this work so that our members can focus on providing critical direct support for New Yorkers. The process has been rife for nonprofits, with chronic delays that cause significant time and money. PASSPort is no different, with chronic delays at every step of the process. PASSPort has an inaccessible user interface, and many providers report preferring Accelerator for its accessibility and design and partnership with the sector. The nonprofit provider is the end user of PASSPort and should be part of the conversation in fixing it. There is no centralized city policy on agency use of PASSPort and information management. Some agencies use other systems in addition to PASSPorts, such as the ICD Connect. Doubling document submission time is a significant burden on providers who are already stretched very thin when they have to work in more than one online platform. Issues with PASSPort also put financial strain on nonprofit providers. In PASSPort, once you submit a budget mod, you cannot submit invoices until the mod is approved. I know that Dr. you spoke about this earlier, and I really appreciate the upcoming release of PASSPort Seven.

However, this is not a city procurement policy but a quirk of PASSPort. Providers are put in impossible positions, having to choose when to submit budget mods, as that will directly impact their cash flow, since they are not able to invoice for however long the budget mod approval takes. These delays pile up, and providers can be owed years of retroactive budget adds, like the COLA and indirect cost rates. The city has promised to fix this issue and has yet to roll out a solution, but

(02:01:38)

hopefully soon. I will be

(02:01:47)

corrected. Late payments to providers are not an accounting hiccup. When reimbursement lags by months or even years, providers cannot respond to crises and end up in crisis themselves, as providers take on debt to meet needs when the city doesn't pay. Staff burnout and programs close. Although the city has taken on reform efforts to address the procurement challenges that nonprofits face, the primary technological infrastructure in the procurement process is inaccessible, inefficient, and contributes to massive delays. Thank you for providing me with this opportunity to testify. I am looking forward to working further with you to support our lifesaving, essential human services providers, and I'm happy to take any questions. Thank you.

(02:02:17)

I really appreciate you both taking the time to testify today and share your insights and expertise. It is greatly appreciated, and I wish we had a few more people here to share their opinions about PASSPort, but I really appreciate each of yours. So, thank you both for taking the time today. I hope you both have a great afternoon, and

(02:02:23)

These are problems that we have known about for a very, very, very long time. So I do think connecting the issues of how much are we spending to support procurement versus what is going on is very important. It would be scary if they end up spending $25 million on a solution when we are not willing to spend that on something. That is the whole thing. Um, ballot proposal.

(02:02:41)

Number two, briefly, I would mention with the public hearings process, I was part of the team that made that happen. Back in the day, we got public comment on less than 1% of all contracts. That was the official line. At my estimate, which you testified to the state legislature many, many years ago, was 25 days that we saved by going to online notice and comment compared to the old

(02:03:02)

process. But it is what we are doing right now. We have to do it. I certainly think everyone should vote yes on two. Their fantastic proposals across the board. I would note, Chair, on the idea of the approvals, I would... of those contracts over $5 million. As I have mentioned, another hearings as well. That is a bit of a red herring that all, frankly, can all be done. The really, really most fantastic thing I think is a... meetings for the Procurement Policy Board, which will really make sure that we cannot ignore reform. Thank you.

(02:03:28)

Thank you. I will note the record that it is up to the administration and

(02:03:33)

choose to have as many Procurement Policy Board hearings as they want. They do not need a ballot amendment to charter a charter amendment to have quarterly meetings, but mandating it is a welcome thing. And with that, I will kick it to Jessie Fay Parrot.

(02:03:47)

Online, welcome. Jessie, you begin. Chair and members of the Council, thank you so much.

(02:03:54)

For having me today. My name is Jessie Fay Parrot, and I am a policy analyst at the Human Services Council. We are a membership organization representing over 180 human services providers across the state. HSC serves as an advocate and intermediary between the sector and the government. We take on this work so that our members can focus on providing critical direct support for New Yorkers. The process has been rife for nonprofits, with chronic delays that caused significant time and money. PASSPORT is no different, with chronic delays at every step of the process. PASSPORT has an inaccessible user interface, and many providers report preferring Accelerator for its accessibility and design and partnership with the sector. The nonprofit provider is the end user of PASSPORT and should be part of the conversation in fixing it. There is no centralized city policy on agency use of PASSPORT and information management. Some agencies use other systems in addition to PASSPORT, such as the ICD Connect. Doubling document submission time is a significant burden on providers who are already stretched very thin when they have to work in more than one online platform. Issues with PASSPORT also put financial strain on nonprofit providers. In PASSPORT, once you submit a budget mod, you can no longer submit invoices until the mod is approved. I know that Dr. you spoke about this earlier, and I really appreciate the upcoming release of PASSPORT seven.

However, this is not a city procurement policy but a quirk of PASSPORT. Providers are put in impossible positions, having to choose when to submit budget mods, as that will directly impact their cash flow, since they are not able to invoice for however long the budget mod approval takes. These delays pile up, and providers can be owed years of retroactive budget add, like the COLA and indirect cost rates. The city has promised to fix this issue and has yet to roll out a solution. But

(02:05:42)

hopefully soon, I will be

(02:05:45)

corrected. Late payments to providers are not an accounting hiccup. When reimbursement lags by months or even years, providers cannot respond to crises and end up in crisis themselves, as providers take on debt to meet needs. When the city does not pay, staff burnout and programs close. Although the city has taken on reform efforts to address the procurement challenges that nonprofits face, the primary technological infrastructure in the procurement process is inaccessible, inefficient, and contributes to massive delays. Thank you for providing me with this opportunity to testify. I am looking forward to working further with you to support our lifesaving, essential human services providers, and I am happy to take any questions. Thank you.

(02:06:25)

I really appreciate you both taking the time to testify today and share your insights and expertise. It is greatly appreciated, and I wish we had a few more people here to share their opinions about PASSPORT, but I really appreciate each of yours. Thank you both for taking the time today. I hope you both have a great afternoon.

AI-generated summaries and transcripts. Errors are possible.
Verify against the linked video and send corrections via email.