Skip to main content

Walkup Service Configuration

For services that are publicly accessible and do not need to be scheduled in advance the resource system supports "Walkup" events. Rather than creating a reservation event these services create a timed record of use. The system creates a "pending" walkup event at the time that use is started and closes out the the event when use is completed by creating an event and order based on the walkup event duration. It is important to note that walkup events do NOT check for collisions when they are created and so overlapping usages can occur.

Unlike scheduled services, Walkup service events cannot be edited after creation. While there is a calendar view for the events this is primarily for user convenience and events cannot be altered from the calendar.

Creating a new service

A new walkup service can be created by clicking the "Create New Service" button located above the service list search box. Walkup services are functionally identical to a scheduled service from a configuration standpoint.  

WalkupService.png

Newly created services will not exist until saved after initial configuration. This means that some functionality that needs an id number such as creating service rates will not be available until the user click the "Save" button to save a newly created service.

ServiceConfig-NewRecord.png

Identifiers

ServiceConfig-Identifiers.png

  • Record ID ID - The system ID number identifying the service
  • Name Name - The display name of the service in question.
  • Type - The type of the service. Defaults to "Scheduled"
  • Parent Group Group  - The group to which this service belongs. Defaults to the currently active group but may be changed to any group that the creating user is listed as a manager for

Visuals

ServiceConfig-Visuals.png

  • Color Color - The color of the button to access the service as it appears in the group services list. This field will accept and valid CSS color in string format. Ex:
    ServiceConfig-ColorDetail.png
  • Display Weight Weight  - How high in the list a service will be displayed. Higher values will display first. Ex: 10 will appear after 50
  • Display Path - For facilities with large numbers of instruments / services it can be helpful to have some additional level of organization. The display path setting allows managers to organize services into folder style nested groupings. The convention follow standard unix pathing conventions. Ex: "/Microscopes/" will display the given service under an expandable section with all other services that have the same configuration.

Contact Information

ServiceConfig-Contacts.png

  • Location Location - The location the service is located at. This field is optional and will display after the service name on the list of services
  • Contact Email Email - The list of email addresses that should be send a notification message. The contact email list can be configured to send emails to any number of addresses. Generally this will be the email of the person or persons responsible for managing the instrument. Email contacts can be configured to receive emails on the following events:
    • All Events - Send a notification for event creation, deletion, and update actions
    • Only Create - Send a notification on event creation
    • Only Update - Send a notification on event update
    • Only Delete - Send a notification on event deletion

The contact email configuration does NOT override the general "Notification Verbosity" setting for the service. If a service is configured to suppress all notification messages then no emails will be sent regardless of the contact email configuration

General Config

ServiceConfig-General.png

  • Enabled - Whether this services is actively in use
    • Yes - Active
    • No - Inactive
    • Archived - Inactive and hidden from search list. (Used for removing services from general use and declutting un-used service records
  • Notification Verbosity - When to send notification emails for actions that occur on the service
    • No Messages - No notifications sent
    • On Create - Only send event creation notifications
    • On Delete Only - Only send event deletion notifications
    • On Create/Delete - Only send notification when an event is created or deleted
    • All Messages - Send notification for all event creation, update, and delete actions
  • Manager Only Only - Controls if service is visible/available to all users of a facility or just facility managers

Tags

ServiceConfig-Tags.png

Tag strings used by the system for categorization and certain actions. No special tags are defined for services at this time.

Scheduler Config

ServiceConfig-Scheduled.png

  • Allow After Hours Access - Controls if the blocked times are treated as "After Hours" or "Blocked"
    • No - Time blocks are not accessible to general users. Administrators and Managers may still schedule in "Blocked" times
    • Yes - Allow users with explicitly granted "After Hours" permissions to schedule during off-hours
    • Yes (All Users) - Allow any user to schedule time during off-hours
    • The recommended setting for after hours access is Yes (All Users) for walkup services.

  • Exclude from Billing - Controls if any orders created on this service are automatically excluded from billing. Useful if a service is provided for free.
  • Lead Time -  Determines how many days in advance a user must schedule. 0 or empty is no lead time.
  • The lead time for walkup services is always ignored

  • Allow Scheduling inside Lead -  Controls if a user may create (but not update or delete) an event inside the lead time. Useful for services that can be scheduled quickly (filling a last minute cancellation) but need special attention on cancellation.
  • Maximum Lead Time -  The maximum number of days in advance a service can be scheduled by a user. Useful for preventing users from "camping" time slots for months in advance that they may not use.
  • This setting has no effect for walkup instrumentation since all walkup events are inside the max lead time.

  • Scheduling Interval -  The minimum "block" size of a scheduled event. Accepts sizes from 1 minute to 1 week.
  • The recommended interval for walkup services is 1 minute

  • Interevent Gap Duration -  The minimum amount of time between service uses. Useful if a service has setup/teardown needs.

Blocked/Off-Hours Times

ServiceConfig-BlockedTimes.png

This section controls what times during the week are treated as Off or Blocked hours during which altered rates may be applied or access may be blocked entirely. Time formats are in 24 hour formats. Defaults to no limits. Common times are 00:00 - 09:00 and 17:00 - 24:00 to give a 9am to 5pm working day.

Custom Data Config

This config section has no effect on Walkup Services

Service Rate Config

ServiceConfig-ScheduledRates.png

Each service can have as many rates as desired. Users will have the option to select these rates in a dropdown when scheduling. Rates for scheduled events have 7 needed configuration options:

  1. Rate Name - The name displayed in the rate dropdown.
  2. Type Type - The type of the rate charge
    • Per Hour - Charge based on the length of the event in question split correspondingly over the on and off hours used
    • Per Run - Charge a flat fee for the event regardless of duration
  3. On Hours Rate Rate  - The rate to charge at for usage that occurs during On Hours as defined in the "Blocked/Off-Hours" configuration section. This rate should be the "At Cost" internal charge rate.
  4. Off Hours Rate Rate  - The rate to charge at for usage that occurs during Off Hours as defined in the "Blocked/Off-Hours" configuration section. This rate should be the "At Cost" internal charge rate.
  5. Commercial On Hours Rate Rate  - The rate to charge at for usage that occurs during On Hours as defined in the "Blocked/Off-Hours" configuration section. This rate can be any rate but should be no less than the internal cost.
  6. Commercial Off Hours Rate Rate  - The rate to charge at for usage that occurs during Off Hours as defined in the "Blocked/Off-Hours" configuration section.  This rate can be any rate but should be no less than the internal cost.
  7. Display Color - The color that any event scheduled at this rate should be appear as when viewed on the calendar. Accepts any valid CSS color string. Can be blank.

All config fields MUST be filled out except the display color regardless of whether you expect to be handling commercial orders on the service. Since users are responsible for selecting their own accounts you cannot control which type of account might be selected for charging the order. If you do not have commercial rates for your services using 2x the internal rate is a safe choice. All fields must ALSO be filled out if you are doing "Per Run" rates.

Service Auto-Charges / Fees Config

Each service can also be configured to automatically attach separate fees for service (apart from the hourly charge) to events created. These charges will be attached at the time that the event is created and can be either Fixed Fees or Duration Linked. In both cases the line item description will be the information provided in the "Fee Description" field.

EventServiceFee.png

  1. Fixed Fee Fee - Fixed Fees are attached to the order as a line item and will remain the same regardless of event duration. This can be used to apply setup fees or other one time charges.
  2. Duration Linked Linked - Duration linked fees are applied to events on the basis of their total duration. The charge will be equal to the Rate * Rate Multiplier * Total Event Duration in hours. This can be used to attach charges for consumables usage.