• Software Procedures 

    Central Dauphin School District Procedure for Software Acquisition and Use

    Software which enhances the teaching process can be a very creative, important, and a productive part of an educational program.  The use and development of software in teaching should be encouraged.  Administrative software must also be current and effective in its support of district activities and teacher functions.

    1. The following provisions are to apply to the introduction and use of both administrative and academic software under the overall coordination of the Director of IT Services.  As a general rule of operation for the use of both individual and departmental software, the appropriate administrative or academic coordinator should be consulted prior to purchase to consider any insights, knowledge or experience which may exist for the software under consideration.  Among the things, this consultation should:
      • Eliminate the possibility of duplication.
      • Determine the degree of support available.
      • Determine if there is another viable solution.
      • Determine if the software is compatible with the district network, if appropriate.
      • Determine if there are any known potential problems.
      • Determine if any upgrades are needed (hardware & software). 
      • Software for the labs will be district standard software.
    2. Software acquisitions should follow these steps:
      • Software under consideration for purchase should be discussed with the Dept. Chair or immediate Supervisor.
        1. They will contact the Director of Technology Services for approval after submitting a software request form (found on cdnet).
      • Departments should plan for their own departmental and individual needs and request funds in their departmental supply budgets as appropriate.
      • Funds for major software purchases should be requested and justified though the annual budget process to be reviewed and approved by the appropriate academic or administrative computer subcommittee established and charged with this function.
    3. After software is acquired, the following action should be taken with the appropriate administrative or academic coordinator:
      • Software should be turned over to the Technology Department for deployment.
      • Departments and individuals should plan on a grace period of at least two weeks once the software is received by the Technology Department.
      • You may be required to identify an Administrator who will be responsible for the overall operations of the software.
      • If there are any questions about this type of procedure, individuals should check with their appropriate computer technician or the Director of Technology Services.
    4. In order to provide for flexibility, innovation and experimentation, a fund, in an appropriate amount, for the development of software use will be established under the budget and control of the Director of IT Services.  The purpose of this fund will be to promote and encourage experimentation and trial of new and innovative software for educational or administrative purposes.  Departments or individuals should present ideas and recommendations to the Director of the IT Services.
    5. Software that is purchased by an individual is not recommended or supported. 
    6. These guidelines apply to all software including but not limited to, textbooks, grant funding, free (Shareware), pilot, demo, websites, co-op purchases, and all upgrades.
      • Software upgrades are coordinated through the Technology Department.
        • Upgrades are usually done once or twice a year.


    In accordance with Board Policy 815,
    Acceptable use of the Computers, Network, Internet, Electronic Communications, and Information Policy.