SOW Content

IQNavigator – Opening up the SOW Kimono (Part 3) [Plus+]

One way to look at IQNavigator’s SOW capability is as a central hub from which to manage decentralized information, permissioning, and provisioning, which is all related to service provider access, service delivery, payment and vendor compliance. Whereas the system can, for example, enable providers to submit time cards directly or upload lump sum payment requests based on an SOW, it can also act as a provisioning tool such that the consultants (or services providers) not on an active assignment tied to an SOW are not provided with network, building and related access (and/or their permissions are turned on/off as status tied to individual SOWs changes).

IQNavigator – Opening up the SOW Kimono (Part 2) [Plus+]

It’s not surprising that IQNavigator’s statement of work customers are prioritizing a range of different goals and outcomes. On a foundational level, one organization in the financial services industry is using IQNavigator’s SOW capability to manage some $200MM in annual SOW spend, primarily to “track changes and manage approvals for SOW scope, timing, cost and delivery” resources as well as to maintain “full budget and cost controls.” Justifying the business case for SOW, this organization has realized an average of ten change orders for projects lasting a year or more (on a per-year basis).

IQNavigator – Opening up the SOW Kimono (Part 1) [Plus+]

Earlier this year, Spend Matters had the chance to go through the latest demonstration of IQNavigator’s statement of work (SOW) capability. As with other SOW capabilities from fellow providers, the tragedy of what IQNavigator has to offer is not what it’s lacking (it’s one of the most functionally deep and broad SOW enablement solutions out there) but the fact that it isn’t more broadly adopted with the targeted customer base. It’s difficult to fathom that there are any customers in the VMS space that have come close to successfully managing the majority of their contingent labor spend through a toolset (or better) without having adopted an enabling SOW capability as well.