bcgov / bcgov/wps

FireBAT: Confirm requirements for RWCO approval / Generated by fields

Open
#1,907 0 comments 0 reactions 0 assignees View on GitHub
Decision Task
Dominant language
Python
Stars
65
Forks
11
Avg merge
21h 25m
Merged PRs (30d)
70

Description

**Describe the task**
Each FBA template is slightly different across the 6 fire centres. More UXR would be needed to understand exact requirements / negotiables. Light change management / process standardization opportunity. [Samples here](https://miro.com/app/board/o9J_lWy3dqw=/?moveToWidget=3074457361445375863&cot=14)

**Additional context**
- Prepared by: First Name / Last Name, Title (FBAN, Fire Weather Forecaster), sometimes a phone number is included
- Approved by: First Name / Last Name, Title (RWCO), sometimes a phone number is included
- KFC have a line for Plans below RWCO
- PG has a 'received by / employee number / zone' below the FBAN/RWCO
- Some capture a date/time printed
- Some have distribution instructions or notes, e.g. please fax signed copy to [number] to confirm all crews notified, or a list of groups it was distributed to are captured or instructions to zones and dispatchers
- FCs do not have standardized distribution flows (e.g. not all FBAs are read out by dispatchers to crews). All use cases for PDF output are unclear

**Acceptance Criteria**
Confirm:
- [ ] "Generated by" field requirements. I believe this needs to be a clear name for folks to contact, not an IDIR
- [ ] "Approved by" field requirements. Same as above - full name, not IDIR?
- [ ] Any other signature requirements for Plans / Zones
- [ ] Timestamp requirement is assumed critical
- [ ] Distribution instructions / notes - will we include and try to standardize these, or exclude? FCs diverge here
- [ ] Use cases for PDF: read by dispatch, emailed to stakeholders/crew, printed or merged into digital IAPs, printed and displayed in Zone/FC offices... this will inform formatting

Contributor guide

Open the contributing guide

Research direction

Start with the linked Miro samples and compare the six fire-centre FBA templates, focusing on the Generated by, Approved by, Plans, Zones, timestamp, and distribution details listed in the issue. Done means the requirements and PDF use cases are confirmed, including which fields and distribution instructions should be standardized or excluded.

Written by the indexing model from the issue text.

Assessment

Domain
design
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Needs clarification
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.