Description: This award supports applicant organizations in their efforts to initially implement or upgrade basic technology infrastructure. Only organizations with networks may apply for this award.
The Foundation supports the following:
- Off-the-shelf software acquisition, installation and integration (with the exception of electronic health records or other types of emerging software for which no underlying de facto or formal technical or data standards exist) where the business case clearly shows that purchase makes more economic sense than "renting" through an application service provider (ASP).
- Basic infrastructure such as desktop and laptop computers, servers, routers, hubs, peripherals, and in special business process-related circumstances only, enterprise roll outs of mobile computing devices (e.g., smart phones, pocket pc)
- Operating system and desktop productivity software
- Telephone system (with the exception of VoIP, see below)
- Multifunction enterprise copier, fax, scan units
The Foundation does not support the following:
- Custom software development projects
- Web site development or enhancements
- Wireless network acquisition or implementations
- Voice over IP (VoIP) acquisition or implementations
- Ongoing operating costs such as service contracts, annual software maintenance fees, or extended warranties.
Note: Because the Foundation expects applicant organizations to "own" its technology including replacement, the Foundation is not generally inclined to support applications that request support for replacement of project components it has previously funded. Should it fund infrastructure a second time, the Foundation expects the applicant to invest the proceeds of its board designated replacement fund to support the large majority of the project.
- Complete and submit the Technology Request Checklist
- Specific identification of any elements for which replacement of infrastructure previously funded by the Foundation is sought
- Confirmation that the organization has established a board designated replacement fund for the project elements described in the submitted application
Project - specific
- Project plan, timeline and resume of project manager
- Vendor documentation for specifications and pricing of all proposed equipment, including all nonprofit discounts
- Description of any training components associated with the project
- For larger enterprise projects (especially software implementations), descriptive "before" and "after" overview of business process(es) to be impacted
- Business requirements document used as basis for enterprise software selection
- A defined governance / operations plan describing organizational roles, responsibilities, and protocols for working successfully with the proposed application / database and data
- If applicable, statement on how the process changes were determined (internally, with external assistance, or both) and by whom
- For larger enterprise projects (especially software implementations), submission of an associated change management plan
- Description of current technology governance (who determines and evolves strategy and policy) and operations (who oversees technology on a day to day basis) models
- Submission of a formally adopted technology strategy
- Submission of the organization's technology plan, and policies and procedures documents
- If the organization is subject to any regulatory requirements such as Health Information Portability and Accountability Act (HIPAA), summary of how the organization has successfully planned for and met these requirements both culturally and procedurally
- Include both a current and future logical network diagram (as opposed to a floor plan) and full IT hardware and software asset inventory
- Copies of scope of service and service level documents illustrating how service is provided within your environment
- Resume of daily service providers / technology coordinator
Sustainability / responsibility
- Description of the organization's process (and budgeting) for disposal of old equipment
NOTE: A technology strategy articulates from a business perspective why the organization needs technology and what it hopes to accomplish with it. It is "the process of determining how an organization can best use technology to further its mission." A technology plan spells out the details of making the strategy happen and involves assessing existing resources, defining needs, and exploring solutions. A written technology plan outlines the phases of technology development, and can also be used as a key tool to advocate for funding.