Content deleted Content added
No edit summary Tag: Reverted |
Reverted 1 edit by 190.99.107.218 (talk): Broken english |
||
(11 intermediate revisions by 8 users not shown) | |||
Line 2:
==Purpose==
A theoretical underpinning of an
== Transitioning to employee scheduling software ==
Line 13:
===Magnetic tape===
During the 1960s, the punched card was gradually replaced as the primary means for data storage by magnetic tape, as better, more capable computers became available. [[Mohawk Data Sciences Corporation|Mohawk Data Sciences]] introduced a magnetic tape encoder in 1965, a system marketed as a keypunch replacement which was somewhat successful, but punched cards were still commonly used for data entry and programming until the mid-1980s when the combination of lower cost magnetic disk storage, and affordable interactive terminals on less expensive minicomputers made punched cards obsolete for this role as well.<ref>Aspray (ed.), W. (1990). Computing before Computers. Iowa State University Press. p. 151. {{ISBN|0-8138-0047-1}}.</ref> However, their influence lives on through many standard conventions and file formats.<ref>Lubar, Steven (1993). InfoCulture: The Smithsonian Book of Information Age Inventions. Houghton Mifflin. p. 302. {{ISBN|0-395-57042-5}}.</ref>
===Auto-scheduling and intelligent rostering===
Line 22:
== Complexity ==
Algorithms are used within the employee scheduling software in order to determine not only who is working, but also the specific jobs and tasks required of the workers. The system still must be monitored, and any further issues with assigning of specifics is done manually.<ref name=":3">{{cite journal | last1 = Robidoux | first1 = L. | last2 = Donnelly | first2 = P. | year = 2011 | title = Automated employee scheduling: Welcome to the future | journal = Nursing Management | volume = 42 | issue = 12| pages = 41–43 | doi = 10.1097/01.NUMA.0000407580.30932.ce | pmid = 22124301 | doi-access = free }}</ref> Within the context of roster problems and models, there are three main factors to work out the differences: the integration of days off scheduling with line of work construction and task assignment, roster construction, and demand type.<ref name=":0" /> These complexities thusly require that each and every workplace must optimize employee scheduling software based on their own unique set of rules, issues and needs.<ref name=":3" /> Additionally, it is difficult to determine optimal solution that minimize costs, meet employee preferences, distribute shifts equitably among employees and satisfy all the workplace constraints. In many organizations, the people involved in developing rosters need [[decision support tool]]s to help provide the right employees at the right time and the right cost while achieving a high level of [[employee satisfaction]].<ref name=":0" /> Due to constant change within work environments, new models and algorithms must be created in order to allow for flexibility as needs and demands arise. For example, when a large number of new employees are hired, as in the total workforce is increased, the scheduling software likely will need to be updated in order to allow for such a change.<ref name=":2" />
==Features==
|