Hi Chad, We did an application like this several years ago but started it from Asset Management, rather than a Service Request.
The application was for managing scheduled and unscheduled asset outages. For each asset or class of assets, the user would specify the frequency and when the asset should come off-line for maintenance, who was responsible for the asset outage, and the template to be used. Frequency could be daily, weekly, semi-monthly, monthly, quarterly or annually. For example, you could say the asset should come off-line the 2nd Sunday of the quarter at 2PM. Then, using the template specified, our ActionProgram Manager Plus would calculate a schedule using the 2nd Sunday of the Quarter at 2PM as the "target date." Some tasks in the template need to be performed before the target date and some after the target date. A week before the first task was to be performed, the person responsible would be notified so that he or she could assign people to the tasks. The assignments would be in the person's to-do list / console. The work schedule would be during prime shift but the work could be done at any time. The person would work the task, status the task, enter their time against the task (optionally) and update the related asset record. All of the tasks would be on the relationship tab of the asset record so you could see the work done against the asset. If they were capturing time, the hours could be multiplied by a rate so you could see the labor cost against each asset. This approach gives you a more complete Total Cost of Ownership of each asset. It was very cool. Of course, all of this could be done from a Service Request or Change or some other form. It's a major benefit of being Remedy-based. Please give me a call off-line if you want to talk more about this. Thanks. Stan st...@projectremedies.com w. 310-230-1722. c. 310-428-5748. -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG] On Behalf Of Chad Wilhelm Sent: Friday, March 13, 2015 11:33 AM To: arslist@ARSLIST.ORG Subject: Service Request Scheduler Design Happy Friday Everyone, Looking for feedback on a project kicking off soon. Any documentation or examples is welcome as well. Background: This is a non ITSM environment. ARS 7.6.04 We have a requirement to retire a ootb java based application which automates the scheduling of SR's. Basically it creates the SR with fields requester, category, description, etc. SR is a option on the form on the ticket form. The current application design 1. Ability to schedule a starting date. 2. A repeat interval of Hourly, Daily, Weekly, Monthly, Yearly. All of these have options. The days during the week are all (Mon-Sun). Hourly You can specify how many hours the SR is occurs(For example generate every 2 hours) and on what days during the week it is allowed to run. Minimum 1 hr value. Daily You can specify how many days the SR occurs(For example generate every 2 days) and on what days during the week it is allowed to run. Weekly You can specify how many weeks the SR occurs(For example generate every 2 weeks) Monthly You can specify how many months the SR occurs(For example generate every 2 months), on what days during the week it is allowed to run, and what week it is allowed to run (1st,2nd, 3rd, 4th, and Last) Yearly You can specify how many years the SR occurs(For example generate every 2 years) 3. Ending Date You can specify a end date to the schedule, no end date, end after occurrences. 4. Requester Information Nothing out of the ordinary. In experimenting, I was able to calculate the next run time on the options of Weekly and Yearly based upon the SR occurrence. This is based off Starting Date using DATEADD function. I have two fields using this Last Run Date and Next Run Date. I believe in order to correctly process, at least one table will need to be added. Rows in the table will be next run date, last run date, Integer Field to hold day of week using WEEKDAY function. Then walk the table to the next run date check the int value against what is allowed for that day. For the ending date, a counter that would hold occurrences if used to decrement if End After x occurrences was used. End Result would be a push fields to the ticket form. Thanks, Chad Wilhelm _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years" ----- No virus found in this message. Checked by AVG - www.avg.com Version: 2015.0.5751 / Virus Database: 4306/9292 - Release Date: 03/13/15 _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org "Where the Answers Are, and have been for 20 years"
