v_personnel

v_personnel

Purpose

  1. Personnel information and assignments.


Relationships

  • v_fire_dept_user: One-to-One (1:1)

    • One personnel links to one user account

    • Referenced through id/personnel_id

  • f_all_schedule: One-to-Many (1:N)

    • One personnel can have many schedules

    • Referenced through personnel_id

  • v_personnel_pay_rate: One-to-Many (1:N)

    • One personnel can have many pay rates

    • Referenced through personnel_id




Table

Column Name

Data Type

Nullable

Default

id

integer

Yes

-

personnel_id

integer

Yes

-

batt_dept_id

integer

Yes

-

client_code

character

Yes

-

batt_dept_name

character

Yes

-

personnel_created_at

timestamp

Yes

-

personnel_birth_date

date

Yes

-

personnel_start_date

date

Yes

-

personnel_status_code

character

Yes

-

personnel_gender_code

character

Yes

-

personnel_iaff_local_number

character

Yes

-

personnel_ems_provider_level

integer

Yes

-

personnel_career_volunteer

character

Yes

-

pesonnel_crew_service_provider

boolean

Yes

-

personnel_agency_id

character

Yes

-

personnel_cad_id

character

Yes

-

personnel_payroll_id

character

Yes

-

personnel_fema_id

character

Yes

-

personnel_firefighter_id

character

Yes

-

personnel_address

character

Yes

-

personnel_unit

character

Yes

-

personnel_city

character

Yes

-

personnel_district

character

Yes

-

personnel_district_id

integer

Yes

-

personnel_zip

character

Yes

-

personnel_is_active

boolean

Yes

-

personnel_secondary_start_date

date

Yes

-

personnel_start_date_ranking

integer

Yes

-

personnel_badge_number

character

Yes

-

personnel_marital_status

character

Yes

-

personnel_end_of_service_date

date

Yes

-

personnel_driver_license_expiration_date

date

Yes

-

personnel_lunch_period_code

character

Yes

-

personnel_days_scheduled_code

character

Yes

-

personnel_hours_scheduled_code

character

Yes

-

personnel_rank_id

integer

Yes

-

personnel_division_id

integer

Yes

-

personnel_shift_id

integer

Yes

-

personnel_driver_license

character

Yes

-

personnel_drivers_license_class

character

Yes

-

personnel_drivers_license_status

character

Yes

-

personnel_driver_license_state

character

Yes

-

personnel_dod_id

character

Yes

-

personnel_race

character

Yes

-

personnel_inspector_number

character

Yes

-

personnel_inspector_designator

character

Yes

-

personnel_investigator_number

character

Yes

-

personnel_station_num

character

Yes

-

personnel_division

character

Yes

-

personnel_position

character

Yes

-

personnel_shift

character

Yes

-

personnel_rank

character

Yes

-

personnel_apparatus_id

integer

Yes

-

personnel_apparatus

character

Yes

-

admin_account_public_name

character

Yes

-

admin_account_first_name

character

Yes

-

admin_account_middle_name

character

Yes

-

admin_account_last_name

character

Yes

-

admin_account_name_suffix

character

Yes

-

personnel_last_first_name

text

Yes

-

personnel_full_name

text

Yes

-

admin_account_ff_title

character

Yes

-

admin_account_phone

character

Yes

-

user_type_code

character

Yes

-

admin_account_email

character

Yes

-

email_is_approved

boolean

Yes

-

personnel_state_code

character

Yes

-

personnel_qualifier_ids

integer[]

Yes

-

personnel_group_ids

integer[]

Yes

-

personnel_qualifiers

text

Yes

-

personnel_groups

text

Yes

-

personnel_home_address

text

Yes

-

personnel_mailing_address

text

Yes

-

personnel_home_phone

character

Yes

-

 personnel_accrual_start_date                                                date            Yes            - 

    • Related Articles

    • v_incident_report_personnel

      Purpose Personnel response records for incidents. Relationships v_incident_report_apparatus: Many-to-One (N:1) Many personnel link to one apparatus response Referenced through incident_report_apparatus_id v_personnel: Many-to-One (N:1) Many responses ...
    • v_personnel_pay_rate

      Purpose Personnel pay rate history. Relationships v_personnel: Many-to-One (N:1) Many pay rates link to one personnel Referenced through personnel_id v_fire_dept_user: Many-to-One (N:1) Many pay rates link to one user Referenced through user_id Table ...
    • v_personnel_nemsis_licensure

      Purpose Personnel NEMSIS licensure records. Relationships v_personnel_nemsis: Many-to-One (N:1) Many licenses link to one NEMSIS record Referenced through personnel_nemsis_id v_personnel: Many-to-One (N:1) Many licenses link to one personnel ...
    • v_personnel_nemsis

      Purpose Personnel NEMSIS certification details. Relationships v_personnel: Many-to-One (N:1) Many NEMSIS records link to one personnel Referenced through personnel_id v_personnel_nemsis_licensure: One-to-Many (1:N) One NEMSIS record can have many ...
    • v_personnel_employment_history

      Purpose Personnel employment history records. Relationships v_personnel: Many-to-One (N:1) Many history records link to one personnel Referenced through user_id v_fire_dept_user: Many-to-One (N:1) Many history records created by one user Referenced ...