Software metering

Software metering refers to several areas:

  • Tracking and maintaining software licenses. One needs to make sure that only the allowed number of licenses are in use, and at the same time, that there are enough licenses for everyone using it. This can include monitoring of concurrent usage of software for real-time enforcement of license limits. Such license monitoring usually includes when a license needs to be updated due to version changes or when upgrades or even rebates are possible.[1]
  • Real-time monitoring of all (or selected) applications running on the computers within the organization in order to detect unregistered or unlicensed software and prevent its execution, or limit its execution to within certain hours. The systems administrator can configure the software metering agent on each computer in the organization, for example, to prohibit the execution of games before 5 p.m.
  • Fixed planning to allocate software usage to computers according to the policies a company specifies and to maintain a record of usage and attempted usage. A company can check out and check in licenses for mobile users, and can also keep a record of all licenses in use. This is often used when limited license counts are available to avoid violating strict license controls.
  • A method of software licensing where the licensed software automatically records how many times or for how long one or more functions in the software are used, and the user pays fees based on this actual usage (also known as 'pay-per-use') [2]

Short Explanation of Active / Passive Software Metering

Active software metering occurs when a user is specifically denied use of a metered application. Passive software metering occurs when application use is simply recorded and no control is asserted over maintaining a maximum concurrent usage level.[3]

gollark: I'm pretty sure I meant a Haskell compiler *to* Lua, not *in* Lua.
gollark: That was a "fix" for sandbox escape #124124817298.
gollark: Yes.
gollark: This is actually by LOC the biggest bit of potatOS. I don't actually understand most of the code at this point.
gollark: Do you not like the code?

References
  1. Kruetzfeld, Ron (2003). Pro SMS 2003. Apress. ISBN 1-59059-698-6.
  2. Software Licensing Models - Ultimate Guide (2020) 10duke.com
  3. "Software Metering / SAM terms". OMTCO Operations Management Technology Consulting GmbH. Retrieved 21 May 2013.

See also


This article is issued from Wikipedia. The text is licensed under Creative Commons - Attribution - Sharealike. Additional terms may apply for the media files.