Security Domain Requirements
OCF Security crews have unique requirements to support their operations.Scheduling
Security crews require the system maintain data about the schedules of each security crew including :- The days worked by the crew
- Many External Security crews have folks working Thursday-Sunday and Friday-Sunday. The Friday-Sunday ones end up working Sweep and show up on the sweep log mentioned above This mechanism is not great. An earlier version of the current Security app had check boxes for days worked. Jon S liked this better but it didn't handle Julie's crew which contains shifts around the clock. Really need mechanisms for both.
- The number of bodies. The number of bodies limits the number of positions that can be filled on the crew by the crew leader on their page.
- The hours worked on each day. The hours worked information can be recorded as the duration between the start-stop times OR as a fixed number of hours. Fixed hours are used because some positions like supervisors work a certain number of hours but not at fixed times.
- Start and stop time of the shift.
- JR - Seems to make sense to use descriptive subgroup names - for example
- Internal ->
- Watergate ->
- 2:00 PM - 7:00PM
- 7:00 PM - Midnight
- Midnight – 6:00 AM
- Watergate ->
- Start and stop time of the shift.
- Number of vouchers per shift.
Food Voucher Distribution
Security crews require the system maintain data about the distribution of food vouchers to crew members. OCF Policy is that food vouchers are allocated at "one per hour" . The data maintained includes- The number of food vouchers allocated to the crew each day.
- An indication of whether the food vouchers are distributed to the crew by the crew leader (bundled ) or if individual crew members pick up their own vouchers.
Crisis Training
Security crews require the system maintain data about who has received crisis training Shows date of last crisis/path rove training, or "Needs" if out of date.Meeting Schedule
Security crews require a way to maintain information about meetings, where to check-in, and miscellaneous notes that their crew leaders enter so that it gets passed to any Teen Crew assigned to them. - General Info Content Management page.Security Reports
- Stickers to put on bundles of tee shirts listing the crew, crew leader, and number of each size of shirt. Used for counting and distribution.
- Sweep log. This is a External Security only form of people who work sweep.
- Working SOP shirt list. This is a list of who has paid for what size shirt. Note that while this is crew business, it's non-Fair inventory.
- Food voucher stickers. The allocated voucher number ranges are entered and stickers are generated for each bundle of vouchers including crew name, leader name, number of vouchers, start and end serial numbers.
- Log books. Day-by-day crew-by-crew log sheets listing people on crews, number of food vouchers, serial numbers, place to sign for them. Note that the crew listing includes anyone assigned to the crew from Teen Crew. There is an area on the page that allows the coordinator to set the format of the log book. This is pretty primitive.
- Vehicle sticker tags. Serial number ranges are entered and stickers are generated that can go on the back of the vehicle stickers to simplify distribution
- Vehicle sticker list. Same info as the tags above but includes a place to sign.
- Crisis Training - Electronic Report for displaying who needs crisis training
Copyright © by the contributing authors. All material on this collaboration platform is the property of the contributing authors. Ideas, requests, problems regarding Foswiki? Send feedback