Process for Procurement of new academic software

Overview

When buying software in an academic environment, it is important to follow a systematic process to ensure the software meets the institution's needs and aligns with the overall IT strategy.

Here is a general outline of the process, along with the roles of IT and users:

Instructions

  1. Identify the Need:

    • Users: Users, such as faculty, administrators, or IT staff, identify the need for new software to address specific academic requirements or operational challenges.
    • IT: IT department collaborates with users to understand their needs, evaluate existing solutions, and determine if new software is necessary.
  2. Requirements Gathering:

    • Users: Users work with IT to define detailed requirements for the software, including functionality, integration capabilities, performance, scalability, security, and user experience.
    • IT: IT department facilitates the requirements gathering process, ensuring that all relevant stakeholders are involved and that requirements are documented accurately.
  3. Market Research and Vendor Evaluation:

    • Users: Users may participate in researching software options, attending demonstrations, and evaluating potential vendors based on their offerings, reputation, customer support, pricing, and compatibility with existing infrastructure.
    • IT: IT department takes the lead in conducting market research, identifying potential software vendors, and evaluating them based on technical requirements, compatibility with the IT ecosystem, reliability, security, and scalability.
  4. Budget and Procurement:

    • Users: Users collaborate with IT and relevant administrative personnel to determine the budget allocated for software procurement and any associated costs, such as licenses, training, implementation, and ongoing support.
    • IT: IT department assists users in estimating costs, preparing a business case, and managing the procurement process, which may involve negotiating contracts, ensuring compliance with purchasing policies, and obtaining necessary approvals.
  5. Pilot Testing and Evaluation:

    • Users: Users participate in pilot testing the shortlisted software options, providing feedback on usability, performance, and suitability for their academic needs.
    • IT: IT department coordinates the pilot testing, sets up test environments, collects user feedback, and assesses the software's compatibility with existing systems and infrastructure.
  6. Deployment and Integration:

    • Users: Users work closely with IT during the deployment phase, providing input on customization, integration requirements with other systems, data migration, and user training.
    • IT: IT department manages the deployment process, including software installation, configuration, data migration, system integration, and user training. They ensure that the software aligns with the institution's IT policies and security standards.
  7. Ongoing Support and Maintenance:

    • Users: Users collaborate with IT to report any issues, provide feedback for improvements, and participate in training sessions or workshops to enhance their understanding and utilization of the software.
    • IT: IT department provides ongoing technical support, troubleshoots issues, applies software updates and patches, manages licenses, and ensures the software remains compatible with the evolving IT infrastructure.

In summary, the users play a crucial role in identifying the need for software, defining requirements, evaluating options, participating in testing, and actively engaging in the deployment and ongoing usage of the software. The IT department supports users throughout the entire process, taking on responsibilities such as market research, vendor evaluation, procurement, deployment, integration, support, and maintenance. It is a collaborative effort between users and IT to ensure that the selected software meets the academic institution's requirements and contributes to its overall success.

 

Still have questions? Request more information.

Details

Article ID: 5933
Created
Tue 6/13/23 2:00 PM
Modified
Tue 6/13/23 3:15 PM