![BATTLEGROUND-LOGO-WITH-TAG415x100px.png]](https://pages.battleground.com.au/hs-fs/hubfs/BATTLEGROUND-LOGO-WITH-TAG415x100px.png?width=332&height=80&name=BATTLEGROUND-LOGO-WITH-TAG415x100px.png){kind=logo}
Understanding Configuration in Battleground Live
1.1 Business Units
Description: Top‑level organizational grouping (e.g., Operations, Technology, Retail).
Where used:
- BIAs (ownership and filtering)
- Plans
- Incidents
- User assignment
What to enter:
- Clear, business‑recognized unit names
- Avoid over‑granularity; departments sit underneath
Import notes:
- Bulk import supported via Import → Content Type: Business Units
- CSV should contain a single column with business‑unit names
1.2 Departments
Description: Functional sub‑groups within a Business Unit.
Where used:
- BIAs
- Plans
- User assignment
- Incident scoping
What to enter:
- Departments that actually own processes
- Do not mirror HR cost centers unless they align to operations
Import notes:
- Bulk import supported
- CSV must include Business Unit + Department mapping
1.3 Locations
Description: Physical or logical locations where work is performed.
Where used:
- BIAs (primary and alternate locations)
- Workplace section
- Plans and relocation tasks
What to enter:
- Offices, warehouses, plants, data centers
- Use consistent naming (e.g., “London – Head Office”)
Import notes:
- Strongly recommended to bulk import
- CSV first row must be location
- Address fields optional but recommended
1.4 Geographies & Countries
Description:
- Country: Nation‑state (U.S., UK, Australia)
- Geography: Regional grouping (EMEA, APAC)
Where used:
- User profiles
- BIAs
- Reporting filters
What to enter:
- Use business‑standard regional groupings
Notes: Countries and geographies are explicitly listed as Company configuration items in onboarding material.
1.5 Organizational Teams
Description: Logical groups/teams used for assignment, filtering, and reporting.
Where used: Company‑wide and in BIA/Plan assignment contexts.
Notes: Organizational teams are explicitly called out in Company configuration lists.
1.6 Hyperlinks
Description: Centralized links referenced across modules (e.g., SharePoint locations, policies, external references).
Where used: Embedded links in objects and templates (client usage varies).
What to enter: Only stable, evergreen URLs; avoid personal links that may break.
Notes: Hyperlinks are listed as part of Company configuration in onboarding collateral.
1.7 Assets & Asset Types
Description:
- Asset Types: Categories of assets (e.g., Facility, Application, Vendor Contract, Data Center).
- Assets: Individual assets used for mapping and linking.
Where used: Plans and resilience mapping; may also link into BIAs depending on modules used.
What to enter:
- Define Asset Types first, then populate Assets
- Align names with existing client registers to avoid duplication
Notes: Assets and Asset Types are explicitly included in the Company configuration checklist.
1.9 Job Titles
Description: Controlled list of job titles (or a mapping layer) used in user profiles and reporting.
Where used: User profiles and reporting.
Required: ❌ Optional (often supplied via directory integration instead).
1.10 Roles (organizational roles, not access roles)
Description: Organizational/functional roles (distinct from platform access roles) used for assignment and response structures.
Where used: Response planning and operational assignment patterns.
Required: ⚠️ Conditionally required (required where tasks are assigned by role rather than named individuals).
2. People & access
2.1 Users
Description: Individuals with platform access.
Roles (access‑control roles):
- User – standard access
- Manager – admin‑level configuration access
- Escalated User – elevated editing capability without full deletion rights (where enabled)
- Read‑Only roles – view‑only access (user or manager)
Import notes:
- Bulk import supported where data is clean
- Standard CSV header example:
email,first_name,last_name,mobile,company,occupation,orgbusiness_unit,orgdepartment,org__location,roles
2.2 External Contacts
Description: Third parties involved in response (vendors, emergency services, landlords).
Where used:
- Plans
- Incidents
Required: ❌ Optional
What to enter:
- Company
- Contact name
- Role in response
Import notes:
- CSV import supported
3. Organization attributes (field visibility and tolerance frameworks)
3.1 Field Visibility (BIA Field Visibility)
Description: Controls which fields are shown/hidden in BIAs to reduce complexity during rollout.
Where used: BIA user experience, data quality, training, and adoption.
Required: ⚠️ Conditionally required (recommended for all implementations).
3.2 Consequence Table
Description: Client impact‑consequence model used for criticality and tolerance decisions.
Where used: Risk‑governance alignment and BIA/BCP tolerance framing.
Required: ⚠️ Conditionally required where a formal consequence model exists.
3.3 Criticality Description
Description: Narrative definitions explaining criticality tiers.
Where used: BIA interpretation, reporting, and training.
Required: ⚠️ Conditionally required.
3.4 Target MTPD / Target RTO‑RPO Key
Description: Tolerance‑definition layer standardizing interpretation of recovery targets.
Where used: BIA tolerance reporting.
Required: ⚠️ Conditionally required for regulated or tolerance‑driven programs.
4. Configuration dictionaries (controlled values)
4.1 Process Criticality Tier
Description: High‑level tier derived from time and impact.
Where used:
- BIAs
- Reporting
4.2 Process Time Criticality
Description: Time to restore a process to BAU.
Where used: BIAs
4.3 Process Impact Category
Description: Impact type if a process fails (financial, regulatory, safety, reputational).
Where used: BIAs and reporting
4.4 Dependency Reliance Level
Description: Degree of reliance on a dependency.
Where used: BIAs
5. Dependencies & IT applications
5.1 IT Applications
Description: Applications supporting key processes, controls etc.
Import notes: CSV import strongly recommended
6. Plans
6.1 Plan Types
Description: Classification of plans (BCP, Crisis, ITDR).
6.2 Plan Checklists
Description: Action lists executed during incidents.
7. Incidents
7.1 Incident Assessment Questions
Description: Structured questions used when logging an incident.
8. Simulations
8.1 Inject Types & Styles
Description: Defines how injects behave and appear.
9. Third Parties / Service Providers
9.1 Service Providers
Description: Third‑party organizations supporting business processes.
10. Global system configuration
Description: Platform‑wide settings not tied to client content.
Required: ❌ Optional
12. Import specification (authoritative)
All CSV imports must follow the filename and header rules defined
13. BIAs – Additional Configuration Items (Detailed)
The following BIA‑related configuration items exist in the platform and must be understood and configured where BIAs are in scope. These sections add to (and do not replace) the earlier BIA coverage.
13.1 BCP Report Templates
Screen / Menu: Configuration → BIAs → BCP Report Templates
Description: Defines the Word templates used to generate BCP outputs once BIAs are complete.
Fields (UI):
- Title (required)
- Description (optional)
- Report Template File (required – Word document)
Actions:
- Add BCP Report Template – client‑specific template
- Add Global BCP Report Template – reusable across BIAs
Guidance:
- Templates should align to the client’s governance and branding.
- Do not finalize templates until BIA structure and terminology are locked.
Downstream impact:
- Controls BCP export structure and language.
13.2 BIA Expiry Settings
Screen / Menu: Configuration → BIAs → BIA Expiry Settings
Description: Defines when BIAs automatically expire and require review and when you get notified.
Fields (UI):
- Title
- Expiry Period (minutes / hours / days / weeks / months)
- Receive Email Notification (checkbox)
Downstream impact:
- Drives governance reminders and reporting.
13.3 Critical Operation Categories
Screen / Menu: Configuration → BIAs → Critical Operation Category
Description: Groups critical operations and links them to time and impact categories.
Fields (UI):
- Title
- Description
- Owner
- Time Criticality
- Impact Category
Guidance:
- Keep categories limited and meaningful.
- Align categories with operational reality, not theoretical models.
13.4 Dependency Internal Types
Screen / Menu: Configuration → BIAs → Dependency Internal Types
Description: Defines internal dependency types used when assessing key processes.
Fields (UI):
- Title
Downstream impact:
- Appears when adding internal dependencies to key processes.
13.5 Dependency Reliance Level
Screen / Menu: Configuration → BIAs → Dependency Reliance Level
Description: Defines the degree of reliance a process has on a dependency.
Fields (UI):
- Title
Guidance:
- Use business‑understandable language (e.g., Total, Partial, Minimal reliance).
13.6 IT Application Business RTO & RPO
Screen / Menu:
- Configuration → BIAs → IT Application Business RTO
- Configuration → BIAs → IT Application Business RPO
Description: Defines business‑side recovery objectives for applications.
Fields (UI):
- Title
- Status
Guidance:
- These are business expectations, not technical guarantees.
13.7 IT Application Hosting Location
Screen / Menu: Configuration → BIAs → IT Application Hosting Location
Description: Defines hosting location options for IT Applications.
Fields (UI):
- Title
14. Company – Additional Configuration Items
14.1 Countries
Screen / Menu: Configuration → Company → Countries
Description: Defines countries in which the organization operates.
Fields (UI):
- Title
14.2 Industries
Screen / Menu: Configuration → Company → Industries
Description: Defines industry classifications for reporting and filtering.
Fields (UI):
- Title
14.3 External Companies & Internal Dependencies
Screen / Menu: Configuration → Company → External Companies and Internal Dependencies
Description: Master list of dependencies used across BIAs.
Fields (UI):
- Title
- Type (External / Internal)
15. Plans – Additional Configuration Items
15.1 Plan Expiry Settings
Screen / Menu: Configuration → Plans → Plan Expiry Settings
Description: Defines when Plans automatically expire.
Fields (UI):
- Title
- Expiry Period
- Receive Email Notification
15.2 Plan Types
Screen / Menu: Configuration → Plans → Plan Types
Description: Defines available plan classifications.
Fields (UI):
- Title
- Description
16. Simulations – Additional Configuration Items
16.1 Inject Styles
Screen / Menu: Configuration → Simulations → Inject Styles
Description: Defines how injects are presented.
Fields (UI):
- Title
- Inject Type
- Feature Image
- Main Body
16.2 Inject Types
Screen / Menu: Configuration → Simulations → Inject Types
Description: Defines inject structure and form behavior.
Fields (UI):
- Title
- Description
- Name / Label
- Form Modifiers (Visible / Unwidgetized / Required)
- Preview Template
16.3 Scenarios
Screen / Menu: Configuration → Simulations → Scenarios
Description: Defines scenario groupings for simulations.
Fields (UI):
- Title
16.4 Workshop Participant Roles
Screen / Menu: Configuration → Simulations → Workshop Participant Roles
Description: Defines participant roles used in simulation workshops.
Fields (UI):
- Title
16.5 Workshop Types
Screen / Menu: Configuration → Simulations → Workshop Types
Description: Defines workshop classifications.
Fields (UI):
- Title
17. Legal & Usage Notes (Client‑Facing Documents Only)
The following statements typically appear in client‑facing configuration or advisory documents, not internal SOPs:
- Inherent limitations of advisory services
- Limitation of use
- Confidentiality statements
Guidance:
- These sections should be excluded from internal SOPs.
- Include them only in client‑issued reports aligned to the Statement of Work.
Completeness Check
With the additions above, this SOP now covers all configuration items visible in the Battleground Live Configuration menu, aligned to current UI labels and behavior, without removing or altering previously approved content.
Appendix A – Common “How do I…?” Configuration Tasks
This appendix provides step‑by‑step, screen‑accurate micro‑procedures for the most common configuration and setup questions. It is designed to support consultants, client admins, and Copilot/GPT‑based assistance.
These procedures do not replace the configuration guidance above; they operationalize it.
A1. How do I add a new Business Unit?
Menu path: Configuration → Company → Business Units
1) Click Add Business Unit (top right). 2) Enter the Business Unit name. 3) (Optional) Enter a description. 4) Click Save and Close.
Notes:
- Business Units should represent ownership, not reporting lines.
- Departments cannot be created until a Business Unit exists.
A2. How do I add a Department and link it to a Business Unit?
Menu path: Configuration → Company → Departments
1) Click Add Department. 2) Select the Business Unit from the dropdown.
- If it does not exist, click + to create it first.3) Enter the Department 4) (Optional) Enter a description. 5) Click Save and Close.
A3. How do I add a Location (manually)?
Menu path: Configuration → Company → Locations
1) Click Add Location. 2) Enter the Location name. 3) Enter the Address. 4) Click Save and Close.
A4. How do I bulk import Locations?
Menu path: Import → Import Content
1) Prepare a CSV file named location.csv. 2) First row (header) must be: import_key, title, address, status 3) Populate one row per location. 4) In Battleground Live, select Content Type: Locations. 5) Upload the CSV and run the import.
Common errors:
- Filename does not match content type.
- Header row does not match exactly.
A5. How do I assign a Process Owner to a Key Process?
Menu path: BIAs → Open BIA → Key Processes
1) Open the relevant Key Process. 2) In Process Owner, select an existing user from the dropdown. 3) If the user does not exist, click + and create the user. 4) Save the Key Process.
Dependency:
- Users must exist before they can be assigned as owners.
A6. How do I change Process Time Criticality labels (e.g., Today, Tomorrow)?
Menu path: Configuration → BIAs → Process Time Criticality
1) Click an existing Process Time Criticality to edit, or 2) Click Add Process Time Criticality to create a new one. 3) Enter the Title (e.g., Immediate (0–4 hours)). 4) Assign it to a Process Criticality Tier. 5) Click Save and Close.
Impact:
- Changes apply across all BIAs using that time criticality.
A7. How do I add an Internal Dependency type?
Menu path: Configuration → BIAs → Dependency Internal Types
1) Click Add Dependency Internal Type. 2) Enter the Title. 3) Click Save and Close.
A8. How do I add a new IT Application?
Menu path: Configuration → BIAs → IT Applications Setup
1) Click Add IT Application. 2) Enter the Title and Description. 3) (Optional) Set:
- Business Owner
- Technology Owner
- Hosting Location
- Vendor
- RTO / RPO (Target and Actual)4) Click Save and Close.
Best practice:
- Standardize application names before importing or creating manually.
A9. How do I control which BIA fields users see?
Menu path: Configuration → Organization → BIA Field Visibility
1) Review the list of available BIA fields. 2) Toggle fields On or Off as required. 3) Changes apply immediately to all BIA users.
Recommended approach:
- Start with minimal fields visible during rollout.
- Enable advanced fields as user maturity increases.
A10. How do I add an Incident Assessment Question?
Menu path: Configuration → Incidents → Incident Assessment Questions
1) Click Add Incident Assessment Question. 2) Enter the Question text. 3) Set Status to Active. 4) Save and reorder questions as required.
Impact:
- Questions appear when incidents are initiated.
A11. How do I add a new Inject Type?
Menu path: Configuration → Simulations → Inject Types
1) Click Add Inject Type. 2) Enter Title and Description. 3) Define form modifiers:
- Visible (Y/N)
- Unwidgetized (Y/N)
- Required (Y/N)4) Add additional rows if required. 5) Select a Preview Template. 6) Click Save and Close.
A12. How do I add a new Service Provider?
Menu path: Service Providers
1) Click New Service Provider. 2) Enter Service Provider name and Legal Name. 3) Set Service Provider Type, Priority, and Status. 4) Assign a Relationship Owner. 5) Click Save and Close.
A13. How do I know if something should be imported or created manually?
General rule:
- Import: Large, stable datasets (Locations, Applications, Users).
- Manual: Governance‑driven or frequently adjusted values (Field Visibility, Criticality narratives).