Application Date
value: date
2023 Annual Commitment
values: check, blank
Experience
Deployed 2022
values: check, blank
Ops
values:Data Field from Original Excel | Field Value | Comments | |
---|---|---|---|
1 | Name | LAST, First | Resource’s name |
2 | Region | CTL, HQ, NEA, NWE, SEA, SWE, VIC | Region which corresponds to the resource’s work location. |
3 | Work Location - total 61 values for all 7 regions |
| Contact information section includes: Work Location, Ministry, Primary Phone #, Secondary Phone #, Other Phone #, Email : In the future, it would be ideal if most of this information could be pulled directly from PeopleSoft/CHIPS (HR system used by the public service). This would help prevent errors and would allow for employee changes to occur automatically. This is a feature that already exists with WildfireOne. Specific fields would be:
|
4 | Ministry |
| Ministry - It is valuable to know which ministry a member is from, but ministries sometimes go through name changes. Some of these acronyms are out of date or not in the correct format. |
5 | Primary Phone # | Format 123-456-7890 | |
6 | Secondary Phone # | Format 123-456-7890 | |
7 | Valid government email address | Email - The only email address that should be on here is the member's government email. | |
8 | Application Date | YYYY-MM-DD | |
9 | YYYY Annual Commitment | check, blank | YYYY represents the current year |
10 | Deployed YYYY | check, blank | YYYY represents previous year |
11 | Operations | N, X, C, O, I |
ESS
values:N = Do not deploy to this position | ||
12 | Emergency Support Services (ESS) | N, X, C, O, I |
---|
FN
values:13 | First Nations | N, X, C, O, I | |
---|---|---|---|
14 |
Finance |
---|
N, X, C, O, I | |
15 |
Liaison |
---|
N, X, C, O, I | |
16 |
Logistics |
---|
N, X, C, O, I |
17 | Plans |
---|
N, X, C, O, I |
APU
values:18 | Advanced Planning Unit | N, X, C, O, I | |
---|---|---|---|
19 |
Recovery |
---|
N, X, C, O, I |
DDir
20 | Deputy Director | N, X, C, O, I | |
---|---|---|---|
21 |
BCWS |
---|
TEAMS |
---|
check, |
GIS
values:blank | ||
22 | GIS | check, |
---|
X X - Experience
C C - Chief Experience
O O - Experience outside PECC/PREOC
I I - Interested
Not Applicable Training Information
blank | |
23 | ICS Manual Sent |
---|
check, |
blank, red |
fill | check = training completed |
24 | ICS 100 |
---|
check, |
blank, red fill | |
25 |
EOC Essentials |
---|
/Intro to EOC |
---|
check, |
blank, red fill | |
26 |
The CORE |
---|
check, |
blank, red fill |
27 | Intro to EM |
---|
check, |
blank, red fill | |
28 |
WebEOC |
---|
check, |
blank, red fill |
29 | Self Discovery & Awareness Workshop |
---|
check, |
blank, red fill | |
30 |
UN Declaration/TRC Group Discussion (Part 1 &2) |
---|
check, |
blank, red fill | |
31 |
Kairos Blanket |
---|
Exercise |
---|
check, |
blank, red fill |
32 | Skills and Abilities of Note |
---|
values: text field
Additional Information
Supervisor's Name
Notes Availability
Date:
values: Avail, Unavail, LV, RO P
A A - Available
U U - Unavailable
H H - Home Region Only
LV LV - On Leave
P P - Possibly
D D - Deployed
RO R-Remote Onl
Data Field | Field Value | Comments | 1 | TEAMS resource name | LAST, First | 2 | Region | HQ, CTL, NEA, NEW, SEA, SWE, VIC | 3 | Resource’s contact information |
| text field | ||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
33 | Supervisor’s Name | First Last | ||||||||||||
34 | Notes | text field | Currently, on the Excel sheet this field value includes the resource’s job title and classification. It would be better if these were two separate fields:
How much a person earns should not be a contributing factor to deployment opportunities, but knowing if they are part of the union or excluded will help us take into consideration that they may not qualify to receive overtime compensation. | |||||||||||
35 | Availability Date | A, U, H, LC, P, D, R | A: Available I would love to see this look a lot different. For instance, it would be nice to see: or Caitlyn Loveday - Unavailable until XXX If someone is deployed, a field to enter a resource request number would be nice. It wouldn't have to be a mandatory field (at this time): Request #: XX-XXXX | |||||||||||
36 |