Skip to main content
Rules for when BFMCs change

Rules for managing data in the RMP when a BFMC changes.

Updated over 2 months ago

General rules

  • You must have the highest admin permissions to make any changes to a BFMC in the RMP.

  • You cannot reuse a BFMC code; they must always be unique. The RMP will not let a user create a code that a BFMC has previously used.

When a BFMC boundary changes

If a BFMC boundary changes, an RMP admin user will archive the original BFMC and add a new BFMC. The new BFMC can have the same name as the original BFMC (edge case), but it will need a new, unique two-letter code to distinguish it from the old BFMC easily.

When a BFMC name changes

If a BFMC name changes, an RMP admin user must archive the original BFMC and add a new BFMC.

When a BFMC ceases to exist

If a BFMC ceases to exist, an RMP admin user must archive the BFMC—but only when that same area has a new BFRMP with its new BFMC.

Did this answer your question?