diff --git a/deployment-apps/alert_schedule/bin/README b/deployment-apps/alert_schedule/bin/README
new file mode 100755
index 00000000..9a70db09
--- /dev/null
+++ b/deployment-apps/alert_schedule/bin/README
@@ -0,0 +1 @@
+This is where you put any scripts you want to add to this app.
diff --git a/deployment-apps/alert_schedule/default/app.conf b/deployment-apps/alert_schedule/default/app.conf
new file mode 100644
index 00000000..661ade7b
--- /dev/null
+++ b/deployment-apps/alert_schedule/default/app.conf
@@ -0,0 +1,17 @@
+[default]
+[install]
+is_configured = 0
+
+[launcher]
+description = This app is used to configure when you would like alerts to fire. It is useful for alerting during normal business hours, e.g. when a stock exchange is open. It also supports holidays, maintenance windows, and multiple spans of regular business hours (e.g. Tokyo Stock Exchange).
+version = 0.6
+author = Eric Plett
+
+[package]
+check_for_updates = 1
+id = alert_schedule
+
+[ui]
+label = Alert Schedule for Splunk
+is_visible = 1
+
diff --git a/deployment-apps/alert_schedule/default/data/ui/nav/default.xml b/deployment-apps/alert_schedule/default/data/ui/nav/default.xml
new file mode 100644
index 00000000..5de12112
--- /dev/null
+++ b/deployment-apps/alert_schedule/default/data/ui/nav/default.xml
@@ -0,0 +1,6 @@
+
\ No newline at end of file
diff --git a/deployment-apps/alert_schedule/default/data/ui/views/README b/deployment-apps/alert_schedule/default/data/ui/views/README
new file mode 100644
index 00000000..6cf74f0b
--- /dev/null
+++ b/deployment-apps/alert_schedule/default/data/ui/views/README
@@ -0,0 +1 @@
+Add all the views that your app needs in this directory
diff --git a/deployment-apps/alert_schedule/default/data/ui/views/home.xml b/deployment-apps/alert_schedule/default/data/ui/views/home.xml
new file mode 100644
index 00000000..5cc1fd36
--- /dev/null
+++ b/deployment-apps/alert_schedule/default/data/ui/views/home.xml
@@ -0,0 +1,35 @@
+
+
+
+
+ Welcome to Alert Schedule!
+
+
Overview
+
+ This app gives you the ability to setup alert schedules which include normal working hours, holidays, and maintenance windows
+
+
+ This is done by
+
+
Configuring your alert schedules in the provided lookup files
+
+
Using the included macro, `check_alerting_schedule(my_schedule_id)` at the end of your alert searches
+
Configuring your alert to use a Custom Trigger Condition with the check for alerts_active="true"
+
+ Any bugs, enhancement requests, or general comments please send to Eric Plett
+
+
+
+
\ No newline at end of file
diff --git a/deployment-apps/alert_schedule/default/data/ui/views/lookups.xml b/deployment-apps/alert_schedule/default/data/ui/views/lookups.xml
new file mode 100644
index 00000000..9f7edd6f
--- /dev/null
+++ b/deployment-apps/alert_schedule/default/data/ui/views/lookups.xml
@@ -0,0 +1,56 @@
+
+
+
+
+ Edit Schedules
+
+
schedule_id: can be anything you want it to be as long as it consistent through all of the lookup files. This is the "primary key" which drives all of the functionality. Note: The included default lookups use contry codes because that was what worked for the original use case this was developed for.
+
schedule_description: is a user friendly name for the schedule. This does not drive any functionality and is essentially optional
+
schedule_timezone: is the timezone (format %Z) that will be used to specify times when configuring the schedule. This will be used to translate the "local" time of the user running the alert search to the one specified for the schedule. This allows the schedules to be configured using the local time of where the schedule originates.
+
+ Schedule Hours lookup
+
+
schedule_id: this needs to correspond to one of the schedule_ids specified in the schedules.csv file referenced above
+
calendar_day_of_week: numeric day of the week 0-6 corresponds to Sunday-Saturday. If there are multiple regular work periods on a day (e.g. Tokyo Stock Exchange), this can be supported by including a second row for the corresponding day.
+
start_time: start time of the regualr work day period entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)
+
end_time: end time of the regualr work day period entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)
+
+ Schedule Holidays lookup
+
+
schedule_id: this needs to correspond to one of the schedule_ids specified in the schedules.csv file referenced above
+
holiday_description is a user friendly description of the holiday. This does not drive any functionality and is essentially optional
+
holiday_date: specific date (format %d/%m/%y) the holiday falls on
+
start_time: start time of the holiday entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)
+
end_time: end time of the holiday entered as a 24 Hour value (format %H:%M) in the schedule's Timezone (specified in the schedules.csv)
+
+ Schedule Maintenance Windows lookup
+
+
schedule_id: this needs to correspond to one of the schedule_ids specified in the schedules.csv file referenced above
+
mw_description: is a user friendly description of the maintenance window. This does not drive any functionality and is essentially optional
+
start_time: start date and time of the maintenance window (format %d/%m/%y %H:%M) in the schedule's Timezone (specified in the schedules.csv)
+
end_time: end date and time of the maintenance window (format %d/%m/%y %H:%M) in the schedule's Timezone (specified in the schedules.csv)