DoD ESI Celebrates its 10th AnniversaryMore than $3 billion in cost avoidance achieved by ESI in first decadeBy Chris PanaroWhen the <strong>Department</strong> <strong>of</strong> Defense EnterpriseS<strong>of</strong>tware Initiative (ESI) working group met forthe first time in the fall <strong>of</strong> 1998, little did theyknow that 10 years later they would beresponsible for more than $3 billion incost avoidance for the DoD. In acknowledgment<strong>of</strong> its 10th anniversary, the ESIworking group went back to some <strong>of</strong> thoseearly ESI visionaries and some current usersto get their thoughts on the initiative overthe years.ESI began as a collaborative effort amongthe DoD chief information <strong>of</strong>ficers (CIOs), butit has turned into an award-winning, DoD-wideinitiative with more than 75 enterprise s<strong>of</strong>tware agreements(ESAs) with more than 50 s<strong>of</strong>tware publishers for thousands <strong>of</strong>s<strong>of</strong>tware products and services.“ESI changed how the entire department acquires andlicenses commercial s<strong>of</strong>tware,” said Dave Wennergren, DeputyCIO for DoD. “Without ESI, we would never have leveraged ourbuying power, understood our department-wide requirements,significantly reduced the labor required to manage s<strong>of</strong>twarelicenses, or have achieved the dramatic reduction in costs <strong>of</strong>several billion dollars. I applaud the ESI team for its success andcontributions over the past 10 years.”During the first DoD CIO conference in July 1998, CIOsfrom across the military departments and defense agenciesdiscussed ways to reduce the amount spent across the departmenton commercial s<strong>of</strong>tware. At this meeting, the CIOs madea commitment to acquire and manage commercial s<strong>of</strong>tware asan enterprise asset, consolidate requirements, coordinate acquisitionsand present a unified front to the s<strong>of</strong>tware industry.Figure 1 on the next page illustrates the ESI timeline from itsinception.Four core goals were established to guide the ESI mission:Obtain buy-in for DoD enterprise-wide s<strong>of</strong>tware agreements;Reduce the acquisition and support costs <strong>of</strong> s<strong>of</strong>tware byleveraging DoD buying power;Provide the best, most flexible suites <strong>of</strong> Joint TechnicalArchitecture-conforming s<strong>of</strong>tware to the DoD enterprise; andCreate a funding mechanism that incentivizes the use <strong>of</strong>DoD-wide s<strong>of</strong>tware initiatives.To guide ESI efforts, a governance structure was establishedto include a steering group and the ESI working group. Thesteering group established operating principles for ESI, and theworking group carried out the ESI mission on a daily basis.“Our core operating principles allowed us to make progressquickly and focus on tangible results rather than bureaucraticissues,” said Rex Bolton, the first chairman <strong>of</strong> the ESI workinggroup and former team leader in the CommercialIT Policies Directorate, Deputy CIO Staff,in the Office <strong>of</strong> the Assistant Secretary <strong>of</strong> Defensefor Networks and <strong>Information</strong> Integration(ASD (NII)).“Our mission was clear — we needed tosave money on commercial s<strong>of</strong>tware, and wecould all do it better if we worked together.From day one, we fostered a collaborativeatmosphere on the team to overcome biasesand preferences and avoid duplicative effort.Good culture and teamwork were our top priorities.It was hard going at first, but with perseveranceand enlightened leadership, it paid <strong>of</strong>f.”“The first ESA we signed was in 1999,” noted Floyd Groce,current co-chair <strong>of</strong> the ESI, team lead for enterprise IM/IT planningfor the <strong>Department</strong> <strong>of</strong> the <strong>Navy</strong> CIO and part <strong>of</strong> the ESIworking group since 1998.“This set in motion our process to identify, acquire and manageenterprise s<strong>of</strong>tware licenses and maintenance agreementson behalf <strong>of</strong> the entire DoD. Since the start, we’ve relied onexpertise and resources contributed from across the militarydepartments and defense agencies to serve on the virtual ESInegotiation and management team.”To help guide its effort, ESI commissioned a study to identifythe best practices for the acquisition and management <strong>of</strong>enterprise s<strong>of</strong>tware agreements within the DoD and industry.The 23 best practices yielded from this research have beenused throughout the ESI tenure, guiding each negotiation andacquisition."In the early stages <strong>of</strong> ESI, product categories were assignedto a s<strong>of</strong>tware product manager (SPM), who would be familiarwith all the products and associated licensing practices withinthat category, such as databases," Bolton recalled. "The SPMwould advise customers and help them negotiate more effectivelyfor all products in that category. As we grew our inventory<strong>of</strong> enterprise agreements, the role <strong>of</strong> the SPM has becomeless specialized, as they manage agreements that include allassigned s<strong>of</strong>tware companies' products, rather than just s<strong>of</strong>twarein product categories."Licensing experts and dedicated SPMs ensure that ESI agreementscontinue to provide best value to customers.“Our best practice research dictates that we only useexperienced and knowledgeable license experts in negotiatingenterprise licenses,” Groce said. “Our team <strong>of</strong> SPMs staysin constant contact with each other through regular teammeetings to share information and lessons learned and discusstrends. They’ve established templates for ESAs and checklistsand guides for negotiation with s<strong>of</strong>tware publishers. To stay ontop <strong>of</strong> industry trends and practices, our team regularly meetswith technology providers and third party analysts.”54 CHIPS www.chips.navy.mil Dedicated to Sharing <strong>Information</strong> - Technology - Experience
Figure 1. The ESI Timeline.Many DoD programs have come to rely on more than 75 pre-negotiated s<strong>of</strong>tware and service agreements, aswell as an inventory <strong>of</strong> licenses, all available on the ESI Web site (www.esi.mil).Using ESI Saves Time and MoneyMany DoD programs have come to rely on more than 75pre-negotiated s<strong>of</strong>tware and service agreements, as well as aninventory <strong>of</strong> licenses, all available on the ESI Web site (www.esi.mil). The ESAs provide favorable terms and conditions for thedepartment as an enterprise — not just as a one-time buyer.Most ESAs allow licenses to be transferred between users withinthe DoD component, and many also permit transfer <strong>of</strong> licensesacross the DoD.Almost all ESI agreements include the right to deploy neededs<strong>of</strong>tware during a period <strong>of</strong> national emergency for a specifiedperiod <strong>of</strong> time at no extra cost. The ESA requirement fors<strong>of</strong>tware publishers to regularly report their sales under the ESIallows DoD to identify the s<strong>of</strong>tware it licensed through the ESA.“Managing license inventory is the result <strong>of</strong> ESI’s initial s<strong>of</strong>twareasset management effort,” said Jim Clausen, co-chair <strong>of</strong>ESI and the IT specialist for ASD (NII). “Over the years, our effortbroadened to all IT assets through our ITAM (IT Asset Management)program, identifying and making available licenses andother IT assets that have been paid for but are not being used.Managing this inventory wisely through IT asset managementhelps satisfy requirements and avoid duplicative, wastefulpurchases.”ESI leverages the DoD’s Working Capital Fund to secureshort-term bridge funding for purchases on a reimbursablebasis. This enables a larger number <strong>of</strong> participants to take advantage<strong>of</strong> scheduled purchases, even if funds are not immediatelyavailable to that program. This facilitates more rationalbuying behaviors during the fiscal year and makes scheduledbuying the norm rather than the exception.Richard Cromley, director <strong>of</strong> the Contracting Services Officefor the Defense Logistics Agency, has used ESI agreementsrepeatedly for both s<strong>of</strong>tware and systems integration serviceacquisition. “The orders placed against ESI contractual instrumentshave definitely saved DLA dollars through reducedproduct prices and labor rates,” Cromley said.ESI negotiates an initial discount <strong>of</strong>f General Services Administration(GSA) schedule pricing as a starting-point pricelevel. Individual customers and program <strong>of</strong>fices that use anESI vehicle are encouraged to seek further discounts basedon transactions and cumulative volume size, as well as marketconditions and timing.“The use <strong>of</strong> the ESI contractual vehicles saves time andeffort <strong>of</strong> contracting personnel and reduces the procurementlead-time to acquire needed products and services,” Cromleysaid. “The major benefit is having both pricing and usage termsCHIPS October – December 2008 55