Notes Skype meeting (Steve Ives, Mark Leusink) 29 October 2012

General

The list of BCM Roles should be extended to:
Global BCM Coordinator
Global BCM Coordinator (alternate)
Local BCM Coordinator
Local BCM Coordinator (alternate)
BCM Team Member
Rename “Event” to “Incident”
To be able to show 6 icons for the BCM application in Unplugged, we’re going to use 6 databases (ML: not anymore: use 1 application in Unplugged combined with Unplugged's AutoLaunch option).
Those database are just used as entry points into the application, all data is stored in a single database.
The default Unplugged functionality to define what users have access to what application can be used to offer a subset of the BCM functionality.
Confirm that Microsoft’s AD is able to export data into a format that can be read by the BCM application.
Create a specifications document in Basecamp to list any requirements or describe the mapping.
Next steps:
Install the PoC application on a server that’s accessible from the internet so it can be reviewed by others.
Create a Gantt-chart-like Excel sheet listing the milestones for the remainder of the project (including a description). The applications’ requirements are defined in the following documents/ items:
high level specifications
data model
prototype application
BCM Rules
this document

Add a ‘matrix’ with all OrgUnits on the X-axis and all BCM roles on the Y-axis. In the matrix the administrator can select what contact/ user is assigned. This way the application administrator can make sure that all positions are filled.

Change “responsibilities” option to “my role”.
The mobile interface defaults to the information relevant to the current user’s OrgUnit. A global BCM coordinator should be able to switch to another OrgUnit.
A new user role (“contact”) should be defined in the system. These users only need a subset of the functions:
Contacts (co-workers within the current OrgUnit)
Plans
The main screen should show the current OrgUnit’s alert level (colored: green=normal, amber=elevated, red=high).
From the main screen the user should be able to view the current incident’s description. This can be a link from the OrgUnit alert level status indicator.
If no plan has been linked: show the current incident’s description.

A plan (for a scenario) has a category. When showing a list of plans (for your OrgUnit), we should also those categories.
The categories need also to be shown in the “activate team” screen (when selecting the plan to link the incident too)

The “Contacts” option should only show the contacts for the current OrgUnit only plus the Global BCM Coordinator (and alternate)
The Global BCM Coordinator should be able to see all contacts.
A contact should be able to edit his own details in the mobile interface
Including uploading a picture (also should be offered in the browser interface).
Contact’s pictures should be shown in the contacts list and details

Show a default explanation on top of the screen.
“Linking this incident to an existing plan is optional.”
“Enter a description of the current incident”
Show the current OrgUnits alert level next to the OrgUnit name (‘traffic light’)
Add a ‘change alert level’ button
The ‘notify team’ option should link to a screen in which a user can enter a text and select what team members to contact (show a list of contacts with – default checked – checkboxes).
The “Activate team” menu option is only available to user with a coordinator role. The local coordinator can change the alert level for his OrgUnit, the global coordinator (or his alternate) can change the alert level for all OrgUnits.

Should show either the ‘global’ communication guidelines or the guidelines of the current scenario.
The admin interface should offer a way to link in a scenario to the global guidelines or use these as a starting point/ template for the scenario’s guidelines.