We’ve talked about demand project, some of the really nice reporting things. SPM can also help your enterprise architecture group. And as you’re doing your ITAM and ITOM work and getting really good CMDB data and getting your services mapped, that can feed up to the strategic level and start helping your enterprise architects do their technology portfolio management, their application portfolio management. And again, thinking about those conversations with your financial officers, they all want to know TCO (total cost of ownership) all day, every day. And, really that’s one of the big connections between the IT work and all that stuff we do to collect our asset data and understand our services and assets. It starts to connect to SPM, because we do want to know what that costs, and we do want to know how much it’s going to cost to improve it or change it or retire it and start to make those strategic decisions with more information— with a better business case—
as opposed to just saying, “This is the new whiz bang thing. We’re just going to put that in.” You start to become more strategic about how you manage your technology portfolio, your application portfolio, your information portfolio. We also connect out in the DevSecOps space. So the agile module is incredibly powerful for managing scrum-type work to handle epics and stories and to be able to power some of that development work. And the great thing is that, if you’re using a lot of epics, those can come into our SPM consideration space, and we can have our business cases with those and our performance of those, just like we do with our projects.