Cover Image

Not for Sale



View/Hide Left Panel
Click for next page ( 78


The National Academies | 500 Fifth St. N.W. | Washington, D.C. 20001
Copyright © National Academy of Sciences. All rights reserved.
Terms of Use and Privacy Statement



Below are the first 10 and last 10 pages of uncorrected machine-read text (when available) of this chapter, followed by the top 30 algorithmically extracted key phrases from the chapter as a whole.
Intended to provide our own search engines and external engines with highly rich, chapter-representative searchable text on the opening pages of each chapter. Because it is UNCORRECTED material, please consider the following text as a useful but insufficient proxy for the authoritative book pages.

Do not use for reproduction, copying, pasting, or reading; exclusively for search engines.

OCR for page 77
Architecture, Strategies, Technologies, and Contracts 77 Enterprise Software Agreement In enterprise agreements, the purchaser of the software is the licensee, and if the purchase is based on a large number of users, an airport should have greater leverage to control and negotiate lower rates and more favorable terms for the license agreement. Because these application instal- lations are at an enterprise level, hardware, infrastructure, and an implementation plan are nor- mally included in the agreement. Enterprise software agreements should detail every aspect of the implementation and installation of the software, and these aspects should be negotiated into the contract. Because of the complexity of the solution, a phased approach using phased agreements might be considered. When purchasing enterprise-level software solutions, open architecture or specific data integration extraction technologies should also be negotiated into the agreements.