Meridian Disaster Recovery Policy

Meridian Disaster Recovery Policy

AUTOMATED MONITORING TOOLS USE FOR PRODUCTION

Meridian software utilizes Google Cloud Engine. We use their Dev Ops tools to monitor the health of the service in production.

ISSUE PRIORITY LEVELS

Priority Level	Description	Examples	Acknowledge Time	Status Update Time
Level 1	Any critical service outage that causes significant loss of critical functionality to a significant number of customers. (See definition below)	App crashes on nearly all devices on initial load or Editor doesn’t load for all customers.	1 hour	4 hours
Level 2	Any intermittent or partial service outage that effects some functionality for most customers.	App crashes when searching for a placemark on iOS devices, Editor fails to save a map, etc.	8 hours	2 days
Level 3	Any irregularity in service that affects some functionality for a small number of customers.	Untranslated word on certain Android devices, slower than normal response time in Editor, etc.	2 days	1 week
Level 4	Minor inconvenience or variance in service affecting a very small number of customers.	Obscure Android device crashes when running obscure Android version, cosmetic bugs, etc.	2 days	2 weeks

* Acknowledge & Status Update Times are limited to USA Business Hours. Emergencies during off-hours, contact TAC at networkingsupport.hpe.com

SLA FOR RESPONSE

Meridian software utilizes Google Cloud Engine, and accordingly our response time depends on Google’s. Google notes a monthly uptime of 99.95%: https://cloud.google.com/compute/sla.

MAINTENANCE SCHEDULE

Google has emergency power capabilities as described here: https://cloud.google.com/security/whitepaper#state-of-the-art_data_centers

Google's servers are fault tolerant and redundant. Redundancy is an automatic process as described here: https://cloud.google.com/security/whitepaper#low_latency_and_highly_available_solution

DISASTER RECOVERY

We backup Meridian data daily. We test our disaster recovery plan every two months. Data can be recovered by processes described here: https://cloud.google.com/solutions/disaster-recovery-cookbook

P1 – DEFINITION OF CRITICAL WORKFLOW

Critical workflows are defined as functionality that is core to the Meridian platform. Core functionalities are defined as Maps, Beacons, Tags, Placemarks, Routes, Blue Dot, and Asset Tracking.

A break in a critical workflow means all hands-on deck to fix the problem.

SDKs

• View maps with placemarks
• Get Directions
• View Blue-Dot
• View Asset Tracking tags

MERIDIAN MANAGER APP

• Authentication
• Show configured and non-configured tags/beacons
• Add beacon/tag to map
• View Blue Dot
• View and Verify tag position is updating
• SSO if enabled

EDITOR

• Authentication
• Add/Edit Organizations and locations, buildings and floors
• Add/Edit users with permissions
• Upload maps
• Set Anchor points
• Add/Edit/Remove placemarks
• Add/Edit/Remove routes
• Parent- child locations and inheritance rules
• Publish/Hide maps
• Set up Beacon management
• SSO if enabled