Purpose Statement
The secondary address management feature within the Pre-Plans module allows users to organize related occupancies by establishing parent-child relationships between addresses. This functionality helps streamline pre-plan organization by grouping secondary or auxiliary addresses under a main parent address, creating a hierarchical structure that improves navigation and reduces duplicate entries for related properties.
Background Information
Secondary address management is essential for fire departments and EMS agencies that need to organize complex properties with multiple buildings, entrances, or related structures. Common use cases include hospital campuses with multiple buildings, industrial complexes, shopping centers, apartment complexes, and educational facilities. This feature requires existing occupancies to be entered in the system and appropriate permissions to modify pre-plan data.
Required Permissions
These permissions are located in the General Section of Pre-Planning Permissions:
- Pre-Plan Organizer--Provides Read Only access to the Organizer
- Pre-Pans Read--Allows User to access Pre-Plan Maps and Pre-Plan list as well as view Pre-Plans in a read only state.
- Pre-Plans Edit--Allows User to edit Pre-plans within the First Due System.
- Edit Pre-Plan Organizer--Allows for edit on Pre-Plan Assignments, Due Dates Cycles and offers the ability to print Occupancy Records.
- Change Primary Address-- Allows User to alter the status of an address as a Primary or a Secondary & allows Users to associate Secondary Addresses to Primary Addresses.
Video
Step-by-Step Guide
5. Select Change to confirm the change.
6. The address is now assigned to the Parent Address.
Removing a Secondary Address
Best Practices
Do's
- Establish clear naming conventions for parent addresses to maintain consistency
- Use the most recognizable or primary entrance/building as the parent address
- Group related structures logically (e.g., all buildings within a campus under the main facility)
- Document the reasoning behind parent-child assignments for future reference
- Train all relevant personnel on the organizational structure before implementation
- Regularly review parent-child relationships to ensure they remain accurate
Don'ts
- Don't create overly complex hierarchies that may confuse field personnel
- Don't assign parent relationships without considering operational impact
- Don't forget to verify changes after making parent-child assignments
- Don't make bulk changes without proper planning and documentation
Tips
- Start with the most obvious parent-child relationships first
- Consider how field personnel will search for and access these addresses during emergencies
- Use consistent terminology across all related addresses within a property group
- Test the organizational structure with field personnel before full implementation
Troubleshooting & FAQs
Q: What happens if I accidentally assign the wrong parent address?
A: Simply follow the assignment process again and select the correct parent address, or remove the parent relationship entirely and reassign.
Q: Can a child address have its own child addresses?
A: The system supports parent-child relationships, but check your specific system configuration for multi-level hierarchy capabilities.
Q: Why can't I find the address I'm looking for when searching for a parent?
A: Ensure the parent address exists as an occupancy in the system and that you have proper permissions to view it.
Q: What happens to existing pre-plan data when I change parent-child relationships?
A: Pre-plan data typically remains intact, but verify that all relevant information is still accessible after making changes.