1 / 29

Best Practices for Documenting Software Licensing Compliance

Best Practices for Documenting Software Licensing Compliance. Presented By Mike Ludwig and Peggy Fish. Software Licensing Compliance. Assigning and Defining Responsibility Collecting and Maintaining Documentation Surveying Departmental PC’s

vernon
Download Presentation

Best Practices for Documenting Software Licensing Compliance

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Best Practices for Documenting Software Licensing Compliance Presented By Mike Ludwig and Peggy Fish

  2. Software Licensing Compliance • Assigning and Defining Responsibility • Collecting and Maintaining Documentation • Surveying Departmental PC’s • Reconciling Survey Results to Authorized Use Records • GASP Software

  3. Assigning and Defining Responsibility

  4. Assigning Responsibility • The Department or Unit Head is responsible for assuring the proper use and documentation of all software within their respective area. • He or she may choose to accomplish this by appointing a Compliance Coordinator.

  5. Defining the Responsibility:Communicate Communicate to all staff: • The importance of authorized use of software. • The procedures for collecting current documentation and reporting their future software acquisitions.

  6. Defining the Responsibility:Document • Collect and maintain documentation supporting the authorized use of software to the appropriate person(s) or network.

  7. Defining the Responsibility:Survey • Survey all PC’s at least annually and reconcile the results to the documentation supporting authorized use of software.

  8. Collecting and Maintaining Documentation

  9. Collect and Maintain Documentation • Collecting and maintaining data supporting the authorized use of software is the most difficult, yet most important aspect of software compliance.

  10. Establish Procedures • Each department or unit needs to establish procedures for gathering and maintaining software documentation. • Procedures may vary for downloaded software.

  11. Tracking Software • The Department/Unit Head and the Compliance Coordinator should decide whether software will be tracked by individual PC or in total across the department. • We are recommending that you track the data elements listed on the document entitled, “Software Compliance Information Tracking.”

  12. Tracking Software on a LAN • In areas where most of the department PC’s are connected through a LAN, we suggest that the tracking of software be done on a departmental basis.

  13. Tracking Software on a LAN • Tracking software across the entire department makes the maintenance of the documentation easier because one need not be concerned with the software location.

  14. Tracking Software • In areas where most of the department PC’s are not connected through a LAN, it will be necessary to track the software by individual PC’s.

  15. Tracking Software • Tracking software by individual PC requires more data to be collected such as the location and inventory number of each PC. However, it does make the reconciliation process easier, especially if the majority of the PC’s within the department are not connected to the LAN.

  16. Purchase of Software • Any transaction involving the purchase of software (including software bundled on hardware) should be reported to the Compliance Coordinator. Internal processes will need to be established to facilitate this information exchange.

  17. Software Acquired from Other Sources • Internal processes would need to be established regarding the communication of software acquired through the Internet, personal funds, site licenses, etc. If individuals are maintaining a file, it is not necessary to collect the same data in a central location within the department.

  18. Surveying Departmental PC’s

  19. Surveying Departmental PC’s • A survey of all PC’s within the department should be completed at least annually. The Department/Unit Head and the Compliance Coordinator should decide on the timing of the survey.

  20. Reconciling Survey Results to Authorized Use Records • The process for reconciling will depend on whether the department chooses to track software by individual PC or across the department. • Documentation of the reconciliation should be maintained for six years.

  21. Departmental Compliance • Reconcile the total number of each software package identified to the total number of authorized uses in the database.

  22. Individual PC Compliance • Reconcile the software identified on each individual PC to the software records for each PC.

  23. GASP Software • The University has entered into a license agreement for the use of a product called GASP. This product is both a surveying and a tracking tool.

  24. Using GASP as a Tool • The GASP software has the capability to survey workstations over a LAN or independently. • GASP recognizes over 9,000 software applications.

  25. Using GASP to Collect and Maintain Documentation • The GASP software includes a database function for collecting and maintaining data about software usage. • By utilizing user-defined fields, all of the data elements identified in the document entitled “Software Compliance Information Tracking” can be recorded.

  26. Using GASP to Survey • The GASP software includes a tool for surveying PC’s. It is especially effective for surveying PC’s through a LAN so that individual workstations are not disturbed. • This tool surveys and identifies software but cannot access file content.

  27. Using GASP to Reconcile • GASP can do the reconciliation if you are using it to keep the records and perform the survey. However, GASP does not identify 100% of software through the surveying process. Since most of what GASP does not identify would present little risk to the department, it is at the department’s discretion how much effort to expend to try and reconcile the “unknown software.”

  28. Use of GASP • While it is the responsibility of each school, department or division to ensure that all PC software is adequately documented for legal use, the use of GASP to achieve this objective is optional.

  29. Questions!

More Related