Digital Transformation • Governance • Government

Transforming Government Procurement and Contract Management

Transforming Government Procurement and Contract Management

This is an audio conversation from the CIO Talk Network podcast. The timestamps in the chapters and transcript below refer to the audio recording.

About this conversation

A CIO Talk Network conversation with Nick Nayak (Department of Homeland Security), Jerry Horton (U.S. Agency for International Development (USAID)), Michael Clark (USAID), hosted by Sanjog Aul.

What the conversation established

The conversation established that reducing waste in government procurement depends less on agency size than on clear requirements and disciplined acquisition planning. Nick Nayak of the Department of Homeland Security noted that government spending grew from $200 billion to $500 billion over 10 years, and that DHS, a top-seven spender at about $19 billion, created a program accountability and risk management organization to review its 500 programs. Jerry Horton of USAID described cutting duplication, citing hundreds of email systems across the government, and gathering requirements directly from USAID’s 85 overseas missions. Michael Clark of USAID argued that teams can design around weak tools but not poor planning, and that statements of objectives let contractors propose solutions. All three tied success to early engagement with industry, continuous competition, and tracking value through to agency missions, with Nick Nayak citing 66 metrics across 1,453 contracting employees.

Host Sanjog Aul talks with Nick Nayak, Chief Procurement Officer at the Department of Homeland Security, Jerry Horton, CIO at USAID, and Michael Clark, Contracting Officer and Division Chief at USAID, about transforming government procurement and contract management. They compare how government buys against private industry and focus on why clear requirements and acquisition planning matter more than size or complexity. Nick Nayak describes DHS oversight of 500 programs and strategic sourcing, Jerry Horton explains cutting duplication and measuring IT value at USAID, and Michael Clark makes the case for statements of objectives and a team approach to contract management. The discussion covers appropriations timing, early engagement with industry, and connecting buyer transactions to agency missions.

Contributors

  • Nick Nayak, Chief Procurement Officer, Department of Homeland Security
  • Jerry Horton, CIO, U.S. Agency for International Development (USAID)
  • Michael Clark, Contracting Officer and Division Chief, Bureau of Management, USAID

Host: Sanjog Aul, Founder and Host, CIO Talk Network

On this page: Key takeaways · Chapters · Explore more · Transcript

Key takeaways

  • Nick Nayak, Chief Procurement Officer at the Department of Homeland Security, says fighting procurement waste starts with oversight tied to program accountability. As government spending rose from $200 billion to $500 billion over 10 years, DHS built a program accountability and risk management organization to review its 500 programs, including 135 major programs with $300 million lifecycles running 5 to 7 years.
  • Jerry Horton, CIO at USAID, argues that much federal cost is duplication rather than outright waste. He points to hundreds of separate email systems across the government and backs moving toward OMB centers of excellence and statements of objectives so vendors can deliver shared commodity services instead of each agency rebuilding them.
  • Michael Clark, Contracting Officer and Division Chief in USAID’s Bureau of Management, says acquisition planning is the one thing a program cannot work around. He explains that teams can design around weak systems or tools but not poor planning, so defining specific objectives and success factors before a buy is what keeps large, complex procurements manageable.
  • Nick Nayak of the Department of Homeland Security says government buyers face time pressures that private buyers do not. One-year appropriations and continuing resolutions often leave agencies about 5 to 6 months to spend most of their funding, yet DHS still completes roughly 100,000 buying transactions a year across 9 contracting organizations and 1,453 contracting employees.
  • Jerry Horton, CIO at USAID, says IT value has to be measured back to the business unit, not just to IT. He can report delivering 99.99% of email within two minutes worldwide, but says the harder task is showing how a tool like an iPad helps a program officer in the field, which takes closer alliances with the bureaus and more transparency.
  • Nick Nayak, Chief Procurement Officer at the Department of Homeland Security, ties good deals to a written strategic plan shared with every buyer. His plan sets 4 priorities, 30 initiatives, and 66 metrics for 1,453 contracting employees, with OMB acquisition stats as a subset, so each buyer can see how daily transactions connect to the agency’s mission.

Chapters

  • 0:00 Introduction: transforming government procurement and contract management
  • 3:45 DHS spending growth and program accountability
  • 7:06 Duplication of services and clearer requirements
  • 9:17 Strategic sourcing and engaging industry early
  • 12:53 Statements of objectives versus statements of work
  • 15:23 Why government acquisition planning faces time pressure
  • 21:05 Gathering requirements from the business units
  • 24:52 Reacting with agility as IT needs change
  • 35:20 A formula for getting a good deal
  • 39:34 Measuring IT value back to the business
  • 47:01 A team approach to contract management
  • 50:03 A strategic plan with priorities and metrics

Explore more

Transcript

Introduction: transforming government procurement and contract management 0:00

Sanjog Aul [00:01:00]:
Today’s topic is transforming government procurement and contract management. And our guests for today’s show are Nick Nayak, who is the Chief Procurement Officer with the Department of Homeland Security and Acquisitions instructor at Strayer University. Good morning, Nick. How are you?

Sanjog Aul [00:01:39]:
I totally agree with that. We also have Jerry Horton, who’s the CIO with the U.S. Agency for International Development, also known as USAID. Good morning, Jerry. How are you?

Sanjog Aul [00:02:09]:
I totally agree with you. And we have Michael Clark as well, who’s the USAID contracting officer and the division chief, Bureau of Management. Good morning, Mike. How are you?

Sanjog Aul [00:02:39]:
So the reason we wanted to have this conversation today is because we have always heard a lot of different things in terms of how government uses tax dollars to carry on delivering security and other services for the citizens. Now there was not much visibility. There were some initiatives that were put in place, and rather, they’re sometimes even blamed for saying there was a misuse or abuse of tax dollars. So we wanted to bring some clarity. And that’s where the first question I would like to address here is, Nick, this is for you. What do you think could be the reason? We totally understand that there may not be malintent. But since there is proof of the pudding in itself and we know that there have been some cases quoted where there have been some not the best utilization of tax dollars, do you think that could be attributed to perhaps a broken process, the way procurement is conducted, the way people assess their needs, and or how the contracts are managed?

DHS spending growth and program accountability 3:45

Nick Nayak [00:03:45]:
Thanks for the question. Speaking from the DHS perspective, let me back up for a second. Let me speak from the government wide perspective in terms of procurement itself. So in the last 10 years, government spending has gone from $200,000,000,000 to $500,000,000,000. At DHS, we’re one of the top seven spenders in order to provide security for the homeland, and that’s about $19,000,000,000. And so now let’s think about how do you oversee and manage in order to not have waste in government. One of the things that we’ve done, so I’ve been at DHS for about 1.5 years, and under Secretary Napolitano and then specifically my boss, Under Secretary Rafael Borras, who is our Chief Acquisition Officer, we’ve implemented a number of enhancements within acquisition, and contracting is a part of acquisition. One of those that I just want to mention is if you think about security, and every American citizen knows security is important, we can also look at the last several years and know that nothing major has actually occurred. But then the question is what’s the price that you actually have to pay for that, and you have to figure out a balance. At the end of the day, in my role, I have to make sure that we’re getting a good deal for the government and that we don’t have waste in government contracts. So one of the things that Under Secretary Borras championed that we’ve implemented here in DHS is putting together an organization that would oversee all of the major programs that we have in DHS, and then implementing and refining a process for reviewing programs at major points in their life cycle to ensure that things are on track, and certainly contracts are a part of that. In DHS, we have 500 programs. We have 135 major programs, and those are programs with a $300,000,000 lifecycle, being 5 to 7 years. And again, having this organization, which we call program accountability and risk management, ensures that programs are accountable, and of course programs are supported by contracts, and that we have ways for measuring risk of programs so that we can come to the rescue of programs at the right point in their life cycle to ensure that there isn’t any waste going on. So we’ve begun that process. We’re evolving that process. We feel pretty comfortable that it is definitely going to be one of the means with which we ensure that taxpayer dollars are spent well on our contracts that support our programs that deliver our mission to protect the homeland.

Sanjog Aul [00:06:50]:
Now with that said, Jerry, how do you, sitting where you sit in terms of a CIO seat, try to look at possibilities of preventing anyone having a water cooler conversation about $1,000 hammers and $100 nails being procured?

Duplication of services and clearer requirements 7:06

Jerry Horton [00:07:06]:
I think a large part of our problem is there’s a huge duplication of services. So it’s not really so much a matter of waste necessarily. It’s just that we’re all doing the same services in different ways. I’d focus on commodity services. We all have email systems, and we have probably hundreds of email systems across the government. To be able to start to consolidate those, move towards, as OMB is pressing towards, centers of excellence, it will give us an opportunity to start to cut a lot of those costs. And as we focus more and more on reducing our cost on a daily, monthly, yearly basis in order to fund new activities, since our budgets are going to be going down probably, we start to look at ways of having people say, yes, we’re cutting this service or we’re cutting that in order to be able to pay for this new service. So to change the water cooler conversation from the $1,000 hammer to, we’re changing this service or we’re reducing this space and reducing our costs so that we can pay for new services. I think the bigger issue though that we’re dealing with is, let me just start by saying, from a CIO perspective, a lot of procurement, the processes are dictated by laws, rules, regulations, and from my perspective we’re like playing the tennis match. We have to hit the ball in between the lines. So that’s why I rely so heavily on our great procurement staff, Mike and his team, to be able to guide us through that. But the one thing that really impresses upon me is being able to use and implement better requirements to help the contractors deliver better services. Part of our problem is that a lot of times we don’t know what exactly our business units want. So it’s harder for us to be able to say give us X, Y and Z, and then we just say, give us something. And the more that we can give defined requirements, the easier it is for the contractor to be able to meet them, and it’s easier for us to be able to manage them. One of our major emphases, from my perspective, is to be able to use more statements of objectives, that the contractors tell us what’s best. I think in certain areas private industry is more advanced than we are. If you can give us a better help desk, you can give us a better email system, let’s do that. Let’s not try to reinvent the wheel for ourselves every day.

Strategic sourcing and engaging industry early 9:17

Nick Nayak [00:09:17]:
And Sanjog Aul, this is Nick. If I could just add to those good points. I want to say a couple of other things that are important with respect to getting a good deal. One is a concept called strategic sourcing, which at its core is leveraging buying power. Government wide, we’re doing it in terms of office supplies, and we’re also headed down that road in terms of wireless devices and services. The other thing I want to point out is about requirements development. That’s a very, very good point. The clearer the government is in defining what it wants, and certainly it is critical that the government interacts with industry far in advance of going out with a procurement so that they can clarify requirements, the better deal that we’re going to get. And frankly, it’s the better deal all the way around. It’s going to be good for companies because only companies who can deliver value will bid on it, therefore reducing the burden for them on bidding on things, which ultimately is passed on to somebody. And then in the government we get exactly what we want. The other thing that I would add to the conversation is, and our other guests could speak to this probably smarter than I could, but in the IT world, things are being transformed. We used to buy them in a particular way and pay for a ton of infrastructure costs, and things like cloud computing are really transforming the way we’re going to buy certain parts of information technology moving forward. It’s evolving very quickly as all IT does. It’ll actually be fascinating to see if something even better comes along, while we think that this is actually the best.

Sanjog Aul [00:11:07]:
So Michael, the question here would be, is the size and complexity which prevents the government to be able to do the job comparable to how the private sector has been able to do with respect to contract and procurement? Given what’s at stake, do you think just because the size and complexity exist, do we jump the gun, and that’s why there is a leakage?

Michael Clark [00:11:29]:
I don’t think so. I think it really does get down to defining the requirements. Properly defining requirements is so critical. And it’s really how you go at it. And in my view, a lot of it comes down to acquisition planning. We really have to have strong acquisition planning, because you can work around a lot of, say, systems or tools that may be challenges, but you can’t really get around poor acquisition planning. You need to have a great emphasis on that. And if you do a good job with that, this size can be managed very well, because that’ll get to the best way to go at the procurement and really flush out the opportunities for success and help you to realize if you are starting to walk into something where the size of it will be a hindrance or not.

Sanjog Aul [00:12:24]:
So Mike, do you think, if you were to go and audit, say, an organization which is doing this procurement for a variety of goods and services, and you were to look across multiple agencies, multiple departments in federal and or state government, what would you see as a common denominator, as the areas where they could use some improvement in order for them to get the best results? Say, take the top two or three areas which really surface.

Statements of objectives versus statements of work 12:53

Michael Clark [00:12:53]:
If I’m understanding the question just in general, it really gets down to, again, defining requirements in advance of the acquisition and defining the specific objectives and success factors for the procurement. You really need to know what you want to get out of it. And very often, we’re so fast to go at what we want to accomplish and get something started, we don’t spend enough time to realize whether we really know what we’re asking for, if that makes sense, in terms of, as Jerry pointed out, a statement of objectives. Are we willing to say, okay, contractor community, tell us how you’re going to do something, and if you give us something we really like, that we didn’t think of, we’re going to let you go ahead and do it. That is a great solution, I think, for the government, the way it can work. The challenge is we have a lot of really intelligent folks on our side working on this, and it can be difficult to separate saying, well, I think you should do it this way, and it needs to do ABC, when we’re trying to say we have the contractor solution, we’re going to let them do it. It’s a difficult balance there, and managing that can be very hard. And part of that’s probably an education process, to shift to say, okay, if we are going to go down the path of statement of objectives, because there’s a lot of good reasons to do that, we really need a full team effort of all the folks involved, the acquisition, technical, and others, to understand what that means. What does it mean to say we’re going through a statement of objectives versus the standard statement of work where we’re telling the contractor exactly what we need? To me, that is the greatest challenge for this to overcome, the understanding of what it means to go to a more open minded thinking, and that doesn’t sound good, but once you say that the best approach is let’s see what industry can do and let’s let them do it, then the emphasis gets focused on the management of the procurement post award, and how do we enforce the performance that they promised that they would do.

Why government acquisition planning faces time pressure 15:23

Nick Nayak [00:15:23]:
I’d like to just add to that in terms of challenges with acquisition planning. So let’s relate this to a private industry buyer and a government buyer. Both would like to have all the time in the world to plan out a buy. And if you have all the time in the world, you are certainly going to go and do market research, you are going to connect with industry, you are going to ask them what’s the best solution to your statement of objectives. So we’re equivalent there in our intent. But here’s what happens on the government side of the fence. Number one, appropriations law. Most of our money that we get to fund our contracts that support our programs is one year money. And so that immediately puts you in a time crunch where you have to begin spending that money. The second thing is all of us have been for years now operating in these continuing resolutions where we don’t even get our annual funding for a particular agency until we’re about 5 or 6 months into our fiscal year, which means we have about 5 or 6 months to spend the predominance of our funding, therefore chipping away at our ability to do all the things that we wanted to do in terms of acquisition planning. However, I will say this, despite those circumstances that private buyers never have to be concerned about, and I’m not saying they don’t have their own time pressures, but we face these time pressures year after year after year. We still get it done. And far and away, when you look at the statistics and the buys that are made in government, for instance DHS, we have 100,000 buying transactions that occur a year. Most of them, if not all of them, go extremely well with these challenges that we face. The last one I’m going to mention in terms of acquisition planning is simply people. If spending rose from $200,000,000,000 to $500,000,000,000, and certainly it’s risen for all of us federal agencies a little bit, you’ve got to have people. This is still a people business. You can’t automate your way out of contracting. Deals are struck by people. They’re struck by people even in the private sector. And so the good news for us is we’ve been in DHS, we have been hiring, we have been developing, we’ve had tremendous support and leadership around acquisition in our agency, and it shows over time that it does take a little bit of time.

Sanjog Aul [00:18:03]:
And when we come back, Jerry, the question is where the requirement definition, if you will, on what the agency and or the buyer wants. How do you take that information and go for your due diligence? And how do you sift through what is really important versus not? How do you weight the value of each purchase that would be made? What would be the ROI? Literally thinking running government like a business and acquisition like a regular business. To what degree can leveraging IT, we can bring this to a reality?

Sanjog Aul [00:20:29]:
So Jerry, based on what we discussed in the first segment, it looks like the requirement definition and the planning, the time available for planning, and the very planning on how you would go about doing due diligence could be some of the most important elements, which if not handled properly, would result in potential leakage. So if you were to look at the systems that are being built in your agency as well as others, what is it that is being done in particular to remove these problems? Or have you been given the funding, or specific projects have been kicked off, to eventually plug the holes?

Gathering requirements from the business units 21:05

Jerry Horton [00:21:05]:
I think from a CIO perspective, not so much from a procurement one, you’re never funded to do 100% of what you want to do. So understanding that you have a limited fund set, and this is true in private industry. When I was out on the private side, you still had to focus on the priorities, and from my perspective the priorities are what the business units, the bureaus in our case at AID, need to do. And since we’re primarily overseas, we have 85 missions around the world. What they’re doing on a daily basis as far as providing development activities around the world should be the driving force for the activities we want to do here. So as we start to define our processes internally to CIO, it’s around gathering the requirements from the business units, what do you need to do, and then being able to validate them. We started about 1.5 years ago on a project where we actually went out, talked to eight missions, got their requirements, came back, designed the system using some very quick turnaround tools, got it back out, started to validate it, walked through the process with them to see what changes they would make, and now we’re in the second iteration. But the tool sets are changing so rapidly, and one of the great things about IT is it does change every 5 seconds. But it gives us the opportunity to do rapid prototyping to see, does this really meet your requirements. From the CIO perspective again, since everything that we do on the procurement side is guided through laws, rules, regulations, and again you’re trying to stay within the lines of the tennis courts, what we look at is can we start with a small system and scale up as opposed to trying to develop a huge new system. When I was out in private industry, we were with a very large corporation that walked away from a $60,000,000 implementation of an ERP system because it was the right thing to do. In government that’s a lot harder to do, as Nick said, because of the funding timing, the funding sources. But the flip side is you have to be able to walk through those requirements, and if you start small, scale up over time, and let your business units help drive those requirements, it makes it a lot easier for us. A lot of times the CIOs too are strung out in no man’s land, because if the business unit doesn’t know what they really need, then it’s much, much harder for us to be able to find the requirements, and that’s one of the situations that I try to stay away from. It’s like, we don’t have clear requirements, let’s push this off. Let’s talk to somebody else. Let’s try to figure out what is the end goal and be very outcome centric. From the IT side we know very well what we do, but it’s hard to translate that into the outcomes we want to see, and a lot of times those metrics are very, very different. And then you look two or three years down the road, I’m very fond of saying that 5 years ago we didn’t know what an iPhone was, 4 years ago we didn’t know what an Android was, we didn’t know what an iPad was. Look where we are today with the rapid rise of consumerization. So things are changing so rapidly around us in a very good way, but we have to be both open to the change and help our business units through it, as long as they understand as well what they need out of it.

Sanjog Aul [00:24:10]:
So Nick, the question here is, the theme is that we have not enough funding perhaps for the IT systems which could potentially help do what you want to do. Then the buyers are not planning their own acquisition properly, and then perhaps the empowerment is missing at the contract and procurement departments or your groups. So that you can say, until the time I do not have a standard for the requirements that I need, if you do not have that standard, we cannot jump the gun and get the cart ahead of the horse and then just do the procurement, because at the end of the day the taxpayers are the ones who are left holding the bag.

Reacting with agility as IT needs change 24:52

Nick Nayak [00:24:52]:
Out of necessity, and because it’s really the right thing to do, so procurement organizations, and we’re just going to give the audience a little bit of specificity with respect to DHS, for instance. So we have 9 contracting or procurement organizations in DHS. A couple of them report directly to me, and they buy all of the things we need to run headquarters DHS, and then we have 7 additional ones. They’re embedded in what we call components, or you would know them as federal agencies like Coast Guard, TSA, CBP, ICE, FEMA, Secret Service and FLETC. And then we have one organization that does our classified procurements, 1,453 contracting people. Now, each one of those contracting organizations have multiple customers. The CIO is always a big one, and very critical for a number of reasons. IT is needed for everything and feels like it’s a part of everything. We are very closely aligned. Our heads of contracting or procurement are closely aligned with the CIOs throughout the department. And so there is no disconnect. The challenge is, and by the way, procurement people don’t go out and do procurements for no reason. They do procurements based on serving a customer, the CIO being a big customer. And so as the world of the customer changes, very much like Jerry described for his customers, you have to react to that, and you react to it together. So just an example would be, let’s say there’s a contract for something, the world of IT changes as it is and we need to change to something else. We can do that, and contractually we can do that. So we can end contracts and start new contracts, but there is that little thing called planning that actually has to occur before you transition off to something else, and remember, things are constantly changing. So one of the things that we’re working with the CIO community on, and frankly, it’s not just the CIO community but all communities, is the concept of doing things with agility, just recognizing that things are constantly changing out there and that we would have to stop old contracts and start new contracts. This concept of agility is something that we’re working through. One other point I wanted to just share in terms of acquisition planning and communicating with industry, oftentimes we communicate with industry around specific procurements, and that is good, it is necessary, and to the extent that we have lots of time before a particular procurement, we want to take multiple steps to connect with industry. It’s also good to create forms outside of procurements, because procurements have a lot of stiffness to them and rules that have to be followed, otherwise those could be tripwires later when you finally get to a contract award. Creating forms for communicating with industry outside the procurement process, which is something that industry is interested in, and what’s the goal? The goal is to learn capabilities. There are so many companies out there in America doing great work, small businesses, midsize, large businesses. We need them all to fulfill our mission. But how do we know what they’re doing, what their capabilities are? So for instance, in our space, it’s to protect the country, and you go to various places where we’re doing great work to protect the country, and you want the people on the front lines, ultimately program manager types, to know what all is out there in terms of capabilities. Now despite the numerous challenges we face on a daily basis that would make doing something like this seem difficult, because you’re doing 100,000 transactions and that in and of itself is a huge task, how do you find time to do something like this? Well, you’ve got to find time. You’ve got to find a way to have more and more of our program community throughout government connect with industry outside of the procurement process. Again, it’s like market research, but it’s really just understanding capabilities that are out there. Now how is that going to help? Because ultimately, that’s going to help shape future requirements, again, making them extremely clear. And look, the clearer you are before you are about to negotiate a deal, the better deal you’re going to get, and really that’s the essence of our chat today, which is how do you get a good deal and minimize waste.

Sanjog Aul [00:29:55]:
So Michael, the question for you is, based on what Nick just said, okay, these guys give us good requirements, then everything will be good. If you were to sit in a buyer’s shoes, what is preventing them? Are they simply not privy to what it takes to build a good requirement? Is that a training issue? Is that an intent issue? Is that a lack of planning? So every time they are doing it at the eleventh hour, and that’s why they do not seem to have the time. And the dollar amount attached to it seems to be mighty high. And even though that amount is pretty high, the corresponding seriousness that’s allocated to it doesn’t seem to be there. What do you think you can attribute this to if you were sitting as a buyer? What’s their concern? What is a buyer’s challenge here? Why are they not able to give you what you need to get the job done properly?

Michael Clark [00:30:50]:
On the technical, on the requirements definition side?

Sanjog Aul [00:31:00]:
The way I’m asking this question is that we said the buyers don’t give us requirements properly. They are also, I’m sure, responsible for making sure that they buy the things timely and, of course, get a good quality and at the best price. So what prevents them? What can we attribute it to, if you were a buyer today and you were to go ahead and try to define a requirement, what prevents them from being able to define that properly?

Michael Clark [00:31:26]:
Excellent question. It could be a couple of things. One is the time that Nick touched on. It is often difficult to have the time that you really want to have to let that develop, to let the requirements develop and to provide those to vendors, to allow enough time, if it were available, for more wide open forums to let the vendors contribute to the development of, not the requirements per se, but in terms of how the agency could go at it, and get vendors’ input as you develop the requirements, it can be very helpful. So if you have more time, more resources, that would be a great thing to have. The communication side of it to the vendors, it depends how you do it. As Nick mentioned, you do your research, do your due diligence. And we do that. And IT ironically brings a lot of that to us, where we can do a lot of market research we couldn’t do years ago, now, to learn about some of the capabilities that are out there. One thing we’ve done is you can post at some of the government-wide portals to have firms tell you their capabilities, and you can use that as a tool as well. But a lot of it, it does come down to the time. You certainly do the best you can every time to provide the best requirements to the widest audience that you can to fit the procurement, because that’s always going to benefit the government. The more resources, the more sources that can contribute to the solution, and the more that you can open it up, is going to benefit the government. So we certainly intend to provide good requirements to a broad audience wherever possible.

A formula for getting a good deal 35:20

Nick Nayak [00:35:20]:
Okay, so you had mentioned earlier that if you had a good requirement, everything would be good. And I think that having a good requirement is very helpful for a specific procurement to get a good deal and ultimately also get what the agency needs to meet its mission. So some additional points. Number one, requirements are not written by buyers. They’re written by people in agencies who actually need something, and typically they’re people who need something to deliver a program. So ultimately, contract award is only an enabler to program success, or it’s a part of program success. So I wanted to show that first. So for me as the chief buyer at Homeland Security, what would I say is the formula for getting a good deal while we buy things that are needed to protect the country. Overarchingly it would be something like this. One, you’ve got to hire highly qualified contracting professionals, and if you’re talking about the acquisition workforce, which is essentially everyone who would have a role starting with the person who writes the requirement, it would be hiring highly qualified contracting professionals, program managers, and things that we call contracting officers, technical representatives. That’s the acquisition workforce, all the people who, for the most part, touch a buy or an acquisition, a buying being a subset of acquisition. We’ve got to train them all to be the best in class. We have to strategically source as much as possible, which is essentially leveraging your buying power within a department. And if you can do it government wide like we have with office supplies and we’re going to be doing with wireless devices, definitely do that. As we’ve been talking about, you’ve got to foster an acquisition process that encourages early engagement with industry, again, to help us establish clear requirements while reducing bidding burden on companies. We’ve got to maximize competition. That’s oftentimes how we get a good deal, having continuous competition, selecting the appropriate contract type, which is something we do in the contracting community, and then ultimately, and you mentioned it, once you have a contract award, it’s about successful program management, and a subset of that would be contract management. At the end of the day, if you had to face the American taxpayer, you would want to be able to say, depending on your agency mission, and in our case we want to say we’re doing things to protect our country, our great country. And we are doing it, and we are getting the best deal that we possibly can while we are buying cutting edge items that are evolving every day to match the evolving threats that we face. So that’s the story that I just wanted to share some more around. The good requirement is one piece. There’s a lot that we’re all working on across the government in order to ensure we get a good deal while doing the actual thing that we were asked to do as public servants.

Sanjog Aul [00:38:39]:
Now with that said, Jerry, if you were to look at the whole value chain, which means when somebody expresses a need, with that getting defined and then handed over to the procurement and contracts, and then something is procured, and then finally it gets utilized and some usage monitoring is conducted, and finally an ROI is delivered and or reported. This whole process somehow needs to have the continuity in terms of the information flow as well as how it changes hands and how people are held accountable for their respective functions. If you were to take this and map it to the systems that are being put in place, maybe in your agencies and others, where do you see things have been done phenomenally well, and where do you see we still have a lot of scope of improvement? Jerry, did you get the question?

Measuring IT value back to the business 39:34

Jerry Horton [00:39:34]:
I’d like to jump around a little bit on the scope of the question, because I think it hits a couple of different points. One is, on the value chain around CIO activities on IT, you’ve really got both back office activities as well as front office. And when I say front office, I mean more the information management piece. So on the IT side, you’ve got the technology, the computers, the networks, all the stuff that people don’t see on a daily basis. And on the front office side, you’ve got information, which is intangible. So a lot of times the things that we do aren’t immediately visible. It’s not like building a building or building a highway. So a lot of times we have to be able to justify what we do in our decisions around these tools that give people better access to information, better information stores so they can make decisions, and be able to use that to give the users who are actually creating the value for the agency, in our case people out in the field actually doing development activities, better information. So that’s really the drive from our perspective. So that’s our metric. From the perspective of doing this on a regular basis, in the federal government we have the CPIC process. It can be a little unwieldy at times, but the process comes around to, or gives us the opportunity to be able to, look at our investments, build a business case, look at an ROI upfront, do the implementation and then review it again at the back end to see did we do a good job. But a lot of times we don’t invest well with the business units so that we actually see what their ROI is. It’s harder for me to see if I have a program officer in Uganda how that person uses an iPad, for example, to do work outside the facility, and how does that make him more functional or her more functional. So a lot of times that ROI is strictly IT related when in reality it’s very much a business unit function. We’re just here to support them, we’re like the old commercial, we don’t do this, we just make it better. So from that perspective a lot of what we need to do is be much more integrated with the business side, with in our case the bureaus, to be able to say, this really works for you. The other aspect of the value chain from our perspective is, as things are changing so rapidly, as Nick pointed out very well, if we have to face a taxpayer and I have to say I have spent $1,000,000 of your money, how did that affect us? We have to be able to face them on a daily basis and say, yes, we spent this money very, very well. The more transparency we have, at least on the CIO perspective on the IT side, it gives us the ability to justify our actions. In our case I can show people our activities on the ground around the world that’s having a defined impact, and that makes it a lot easier to say, well, we put this money to support them, we put this money to give them wireless networks in embassies and missions around the world, we spend money on technology. Now we’re spending a lot of money on managing our information better, starting to link our systems together. So from that perspective we have to have the transparency to be able to show people, and the numbers behind it, to be able to say, this really had an impact.

Sanjog Aul [00:42:47]:
Now what all you just mentioned here, if suppose you were to compare this whole spending and contract procurement, the government itself, to a business, do you think today we are at a point where you could offer an agency a dashboard where what all things were to be purchased and how they moved all the way from being procured to being consumed, and the value created. How far from that Star Trek version of dashboard that you could offer to an agency, or across agencies? Is the technology even available, or has that whole information system even been put together, or even been contemplated for that matter?

Jerry Horton [00:43:25]:
This is Jerry. Let me just add one thing there, is that yes, the technology is there. There are some really cool ways to show it. But the problem that we have, at least on the CIO side and maybe a little bit on the procurement side as well, is that integration back with the business side. Nick touched on it earlier, is that you’ve got to have close alliances with the people that are actually defining the requirements, actually doing the work on the ground. And that’s where it’s really hard for us to be able to say, well, this affected your people by X percent, whereas I can say easily, we delivered every email, or say 99.99% of our email within two minutes worldwide. I can say our server utilization is X. It’s harder for me to be able to say what is the actual impact on your business side without having those closer alliances.

Sanjog Aul [00:44:11]:
And Michael, when we come back, would like to further ask the question, what do you think you’re measured on, for that matter? When you get your promotions and or you get your paycheck, how are you expected to earn your paycheck? What all areas are you expected to deliver? And what’s the benchmark that has been set for you? And are you able to, with what all has been offered to you as a support system, able to consistently do that? And if not, what external parameters prevent you from being able to do your job effectively today?

Sanjog Aul [00:46:33]:
So, Michael, the question is, where we are trying to figure out, if you are trying to do your job, what prevents you from being most effective?

Sanjog Aul [00:46:49]:
I would like you to appeal to all the entities and environmental factors which would help me help you. That’s what I’m trying to get out of this.

A team approach to contract management 47:01

Michael Clark [00:47:01]:
I do think that, while it’s a common theme and not to continue it necessarily, but the resources is a big part of it. You do have to manage, there’s a lot of great opportunities in the IT world, and supporting the IT office from a procurement perspective is interesting and rewarding. And you really want to maximize your ability to get the best deal as you can for the government and ultimately for the taxpayer. So you want good contracts doing great work, and you want, of course, fair reasonable prices, and you want to ensure that the work that’s being done is being done as well as it can. So to me, to the extent that we can have an across the board understanding of the differences between, say, contract management and project management, which is project execution, is very helpful, and to have an organizational behavior that understands that and implements that. And a continuation to emphasize performance based contracting, focus on metrics and quality assurance. And the reason I point that out is because so much of the day can be spent on contractual matters, making sure the work that was agreed to gets done right, or talking to a contractor about problems that are happening. And our ability to manage the contracts, and by management I mean not just from the contracting office, we do the administrative side of it, but at the project execution level, is critical. And you really need, it almost takes a village approach, where you have a team of folks all working together for the same end and all understanding. So there’s a little bit of a cross training that can occur, an understanding across the office, just what the contract management includes, because it goes beyond the contracting office. And in this office specifically, the recent restructuring, we’re trying to get there, and I think we’re going to get there in terms of having a centralized program management office on the administrative side that manages everything from a high level and ensures that all of the players on a project, which include technical and the contractual staff, are working together. And that’s the biggest thing, is having the team approach in the technical and contract side, of everybody understanding what each other is doing to get the job done. Because that cuts down on a lot of issues that come up, and that’s really probably the one area I’d say we want to try to improve on.

A strategic plan with priorities and metrics 50:03

Nick Nayak [00:50:03]:
And Sanjog Aul, this is Nick. I’d like to add to that very good information and just speak from a cabinet level perspective about contracting and procurement, and how would all of the people who are in that field know exactly what to do, what are the goals, how are they measured, and so forth and so on. So again, just for everybody who’s listening, we have 9 contracting organizations, 1,453 contracting folks, 100,000 contracting actions that occur every year, $19,000,000,000 spent in DHS. What I have for all of the 1,453 contracting employees is a strategic plan. The strategic plan has 4 priorities. They are quality people, you’ve got to have quality people in order to do good contracting. Quality contracting, there’s a lot of things you have to do in order to have quality contracts. Quality program support, because we’re not in the business of awarding contracts. We award contracts to enable programs to do things that protect the nation. And the last one is quality interaction between government and industry. Again, going back to the point that we spoke about, which is effective interaction with industry and clear requirements ultimately will help you get a better deal. 4 priorities, 30 initiatives within the priorities, and 66 metrics, and we slice and dice the metrics so that we can tell how efficient we are, effective we are, how good we are with customer satisfaction. There’s a number of other organizations that ask us to have particular metrics, for instance, the Office of Management and Budget for all contracting organizations has something they call acquisition stats. And so those are a subset of our 66. This is all put into a strategic plan, which is sent directly to the 1,453 contract employees so that they can see themselves as part of the big picture. So that on a day to day basis when buyers are involved in all of the buying transactions, they can see the big picture. And then these metrics get driven down into folks’ performance plans and through the heads of contracting that we have, the 9 contracting officers. So it’s really important for all of the buyers to see themselves as one. In our case, we have a lot of things to support the secretary’s initiative of One DHS, and within contracting, this is one of our ways of doing that. And then, what’s very nice here is, above me, the Under Secretary for Management who wears the cap of Chief Acquisition Officer also has a dashboard for all of the Chiefs that work under him, the Chief Officers, and I’m one of them, the Chief Procurement Officer. So it’s a real nice tie to the health of the cabinet level agency, Homeland Security, the health of management, and then in my particular world, the health of contracting, which then ultimately lets the people who are doing the hard work on a day to day basis know that they’re part of a bigger picture, and lets them know specifically what the major initiatives are and what they should do to help us push the metrics in the right direction.

Sanjog Aul [00:53:23]:
On behalf of the show and our listeners, I’d really like to thank you, Nick, Jerry, and Michael for sharing your thoughts. It seems like we are really taking very, very good steps and very promising steps to transform government procurement and contract management. Yes, there might be some gaps in terms of how timely and quality wise we collect the requirement from the buyers, but it seems like we’re getting there.

Contributors

Nick Nayak

Nick Nayak, Chief Procurement Officer, Department of Homeland Security (DHS), and Acquisitions instructor, Strayer University

Nick Nayak has over 24 years of senior private, public and academic leadership experience. He has been a dynamic figure in the field of federal acquisition – helping to professionalize the federal acquisition workforce; implement methods ... More   View all posts
Michael Clark

Michael Clark, USAID Contracting Officer Division Chief, The Bureau of Management

Michael Clark currently serves as USAID Contracting Officer Division Chief in the Bureau of Management. He oversees negotiation of contractracts to procure IT systems, developing and/or modifying procurement strategies, administering comple... More   View all posts
Jerry Horton

Jerry Horton, CIO, US Agency for International Development (AID)

Jerry Horton joined the US Agency for International Development as the Chief Information Officer (CIO) in February 2009. As CIO, Mr. Horton is responsible for information management. business services, infrastructire operations, and cyber s... More   View all posts
Add Comment
Click here to post a comment

Advertisement

TECHM - DNA - MPU01 - 300x250
Nick Nayak