To insert data from your BIA into a Microsoft Word document, you need to use the following codes. Instructions on how to use each code is included below, with an example available to download in the link in Step 1 above.
|
How to insert a structured table of data, with multiple columns and rows ${chunk-processes-sequence}
${chunk-workplaces-sequence}
${chunk-dependencies-sequence}
${chunk-applications-sequence}
${chunk-people-sequence}
|
In your word document, create and format a table that has at least one row and one column. Before the table, enter the appropriate code that relates to the data you would like to insert into the table: ${chunk-processes-sequence}
Inside the first column of the table, insert the following code ( ${iterable-row} ) followed by the first data variable you would like to insert into the first column. For example:${iterable-row}${title}
Insert as many variables you would like in other columns of the same row.
After the end of the table, insert the following closing statement (note: it is the exact same code to start, but with a “/” at the beginning of the code).${/chunk-processes-sequence}
Refer to the downloadable template as an example.
|
|---|---|
|
How to insert unstructured, repeatable blocks data ${chunk-processes-loop}
${chunk-workplaces-loop}
${chunk-dependencies-loop}
${chunk-applications-loop}
${chunk-people-loop}
|
The follow codes allow you to enter a set of data into a word document without using a table. To start the area where you would like to insert data, use the opening code relating to the set of data you would like to insert. ${chunk-processes-loop}
Format and insert variables into the word document in any way you see fit.Refer to the variables available below. Mark the end of the block of data, insert the following closing statement (note: it is the exact same code to start, but with a “/” at the beginning of the code). ${/chunk-processes-loop}
Refer to the downloadable template as an example.
|
These variables can be inserted anywhere within the Microsoft Word document template without needing to use the Merge Fields above. They do not repeat or iterate.
These variables must be used inside the Merge Fields, as instructed above.
New fields or changes are highlighted in yellow
BIA |
|
|---|---|
| ${name} | BIA Name |
| ${bia_owner} | BIA owner |
| ${business_unit} | The name of the business unit |
| ${departments} | The name of the department(s) |
| ${teams} | The name of the organisational team(s) |
| ${geographies} | The name of the geography(ies) |
| ${meetup_location} | Meetup location details |
| ${teleconf_details} | Teleconference Details |
Processes |
|
| ${title} | The title of the key process |
| ${description} | The process summary / Strategy |
| ${owner} | The process owner |
| ${bau_criticality} | The business as usual level of criticality |
| ${bau_time_criticality} | The business as usual level of time criticality |
| ${bau_impact_category} | The business as usual impact category |
| ${is_peak} | Have different criticality during peak seasons? (yes/no) |
| ${peak_season} | Peak seasons (months) |
| ${peak_details} | Detail on peak seasons |
| ${peak_criticality} | The peak season level of criticality |
| ${peak_time_criticality} | The peak season level of time criticality |
| ${peak_impact_category} | The peak impact category |
| ${max_criticality} | The max level of criticality across BAU/peak |
| ${max_time_criticality} | The max level of time criticality across BAU/peak |
| ${bia} | The name of the BIA |
| ${business_unit} | The name of the business unit |
| ${department} | The name of the department(s) |
| ${org_team} | The name of the organisational team(s) |
| ${geography} | The name of the geography(ies) |
People |
|
| ${role} | Role |
| ${primary_alternate} | Primary or Alternate |
| ${name} | Name |
| ${mobile} | Mobile Number |
| ${landline} | Landline Number |
| ${email} | |
| ${occupation} | Occupation |
| ${bia} | The name of the BIA |
| ${business_unit} | The name of the business unit |
| ${department} | The name of the department(s) |
| ${org_team} | The name of the organisational team(s) |
| ${geography} | The name of the geography(ies) |
Internal and External Third Parties / Vendors |
|
| ${process} | Process name |
| ${internal_external} | Internal or External |
| ${title} | Dependency name (title) |
| ${reliance} | Reliance Level |
| ${description} | Description of service provided |
| ${contact_name} | Contact Name |
| ${contact_first_name} | Contact First Name |
| ${contact_last_name} | Contact Last Name |
| ${contact_number} | Contact Number - Number chosen by the first number available in this order: mobile->work->home |
| ${contact_mobile} | Contact Mobile Number |
| ${contact_phone_home} | Contact Home Number |
| ${contact_phone_work} | Contact Work Number |
| ${contact_email} | Contact Email |
| ${contact_name_number} | Contact Name and Number |
| ${contact_name_email} | Contact Name and Email |
| ${contact_name_number_email} | Contact Name, Number and Email |
| ${internal_dependency_type} | The Internal Dependency Type |
| ${bia} | The name of the BIA |
| ${business_unit} | The name of the business unit |
| ${department} | The name of the department(s) |
| ${org_team} | The name of the organisational team(s) |
| ${geography} | The name of the geography(ies) |
IT Applications |
|
| ${process} | Process Name |
| ${title} | IT Application Name |
| ${max_criticality} | The max level of criticality of associated key process |
| ${max_time_criticality} | The max level of time criticality of associated key process |
| ${rto} | Recovery Time Objective |
| ${rpo} | Recovery Point Objective |
| ${manual_workaround} | Manual Workaround |
| ${bia} | The name of the BIA |
| ${business_unit} | The name of the business unit |
| ${department} | The name of the department(s) |
| ${org_team} | The name of the organisational team(s) |
| ${geography} | The name of the geography(ies) |
Workplaces |
|
| ${title} | The title of the BAU workplace |
| ${processes} | The processes performed at the workplace |
| ${bau_staff} | Number of staff for normal operation |
| ${bau_additional_comments} | BAU additional comments |
| ${remote} | Can staff work from home? |
| ${remote_table} | Number of people working from home over time (table) |
| ${remote_staff} | Number of staff working from home |
| ${remote_staff_percentage} | % these staff with remote access capability |
| ${remote_additional_requirements} | Additional requirements for work from home |
| ${remote_max_operation} | Max time operable working from home |
| ${transfer_process} | Can the processes be transferred to another team? |
| ${transfer_who} | The person/team/department who will take over the process |
| ${transfer_location} | Person/team/department transferred to |
| ${transfer_max_operation} | Max time operable on transferred person/team/department |
| ${transfer_additional_site_info} | Additional information for alternate team |
| ${workplace_alternate} | Can staff be relocated? |
| ${workplace_table} | Decommissioned - Please use ${alternative_workplaces} or ${alternative_workplaces_table} |
| ${workplace_preferred} | Decommissioned - Please use ${alternative_workplaces_comments} or ${alternative_workplaces_comments_table} |
| ${alternative_workplaces} | Alternative Workplaces with staff distribution |
| ${alternative_workplaces_table:<font size>} | Alternative Workplaces with staff distribution in Word table format :<font size> is optional. Example usage: ${alternative_workplaces_table:9} for a 9 pt font size |
| ${alternative_workplaces_comments} | The comments to each alternative workplace location |
| ${alternative_workplaces_comments_table} | The comments to each alternative workplace location in Word table format |
| ${workplace_additional_comments} | Additional comment on alternate workplace |
| ${bia} | The name of the BIA |
| ${business_unit} | The name of the business unit |
| ${department} | The name of the department(s) |
| ${org_team} | The name of the organisational team(s) |
| ${geography} | The name of the geography(ies) |