Уляна

Уляна Чемеринська
Графічний дизайнер

[open contact info](look above in the "contact info" section)

[open contact info](look above in the "contact info" section)

@uliana3224

Я Уляна графічна дизайнерка, досвід роботи в дизайні SKILLS
та поліграфії 4 роки. Працює з візуальними
концепціями, брендингом та digital-дизайном. Вмію Graphic Design
перетворювати ідеї та задачі бізнесу на цілісні, сучасні Branding & Visual Identity
й функціональні візуальні рішення. Social Media Design
Працюю з композицією, типографікою, кольором, рекламні креативи
візуальною ієрархією та створенням рекламних банери та digital-реклама
матеріалів. Постійно розвиваю професійні навички та презентації
стежу за сучасними тенденціями у дизайні. типографіка
композиція та візуальна ієрархія
робота з фотографією
Graphic Designer створення візуальних концепцій
створення рекламних та digital-матеріалів; підготовка макетів до публікації та друку
розробка візуалів для соціальних мереж;
створення банерів, креативів та презентацій;
робота з типографікою, кольором і композицією;
адаптація дизайну під різні формати;
підготовка матеріалів до публікації;
взаємодія з командою та врахування задач бренду.

This Business Continuity Plan outlines procedures in place to ensure that critial Cloudlet Systems
business functions continue during and after a disruption. It provides guidance for minimizing
downtime and protecting vital company assets

Business name: Cloudlet Systems Inc.

Industry: Information Tchnology

Primary products/services: Software Development and IT Support

Locations: Cloudlet Systems Central Harbor
123 Anywhere St., Any City, ST 12345

Summary Description:

Cloudlet Systems is a small IT firm that provides software development, cloud solutions, and technical
support services to local businesses. It focuses on delivering reliable and scalable technology systems
using modern cloud platforms.

Risk Assessment
A. Identified Risks

Risk Type Description Likelihood Impact Notes

Natural disaster Flooding 🟡 Medium 🟢 High Remote work
affecting the reduces impact
office

Power outage System 🟡 Medium 🟢 High Backup systems
downtime maintain
affecting cloud operations
access and client
support

B. Risk Summary
A flood can damage vital office infrastructure, hardware, and network equipment. It may cause
extended downtime, limit employee access to systems, and delay client service delivery. Without proper
safeguards, critical data and systems could be at risk, impacting business continuity and client trust.

Business Impact Analysis
A. Critical Functions

Function Description Owner Recovery Time Recovery Point
Objective (RTO) Objective (RPO)

Customer User issue Support 4 hours 1 hour
Support resolution Manager

System Cloud system IT Manager 2 hours 30 minutes
Monitoring management

B. Impact of Disruption
A disruption in customer support operations can limit access to systems, tools, and communication
channels. This may lead to delayed responses, unresolved tickets, and reduced service quality.
Prolonged interruptions can impact client satisfaction and damage the company’s reputation.

Continuity Strategies
A. Operational Continuity
Enable remote work for staff who rely on cloud-based tools.
Prioritize critical services such as customer support and system monitoring.
Ensure consistent communication and coordination.

B. Facilities and Structure
Use cloud infrastructure to host all critical systems and applications.
Maintain regular automated backups in secure off-site locations.
Implement system redundancy to reduce single points of failure.

C. Data Protection and Recovery
Perform regular backups of critical files and client data.
Store backup copies in secure cloud-based locations.
Test recovery procedures regularly to ensure system reliability.

Emergency Response Plan

A. Immediate Actions
1. Assess the situation and determine the scope of the disruption.
2. Ensure the safety of all personnel.
3. Notify key staff and activate the response team.
4. Secure critical systems and data from further risk.
5. Switch to backup systems or remote operations if required.
6. Communicate status updates to employees and clients.
7. Document actions taken and monitor ongoing recovery efforts.

B. Incident Response Team

Role Name Contact Responsibility

Incident Lead Zola Bekker 123-456-7890 Overall coordination

IT Manager Riela Agustin 123-456-7890 System recovery

C. Recovery Priorities
Restore cloud systems and client access services.
Recover critical business data from secure backups.
Resume customer support and technical operations.

Recovery Plan
A. Recovery Procedures
1. Assess damage to systems, infrastructure, and data.
2. Restore critical systems from backups in priority order.
3. Verify data integrity and system functionality.
4. Reconnect networks and test user access.
5. Resume core business operations and services.
6. Monitor systems closely for issues or instability.
7. Document actions taken and identify improvements.

B. Timeline for Recovery

Timeframe Actions

0–4 hours Assess impact, secure systems, initiate recovery actions

4–24 hours Restore critical systems and enable basic operations

1–3 days Resume full service delivery and stabilize systems

3–7 days Complete full recovery, testing, and performance checks

Post-recovery Conduct review and update continuity plans

C. Post-Recovery Actions
Evaluate the effectiveness of recovery procedures.
Document lessons learned and gaps identified.
Update continuity and emergency response plans as needed.

Appendices

File Name Description

Emergency Contact List Contains the names and contact details of key personnel and external parties
needed during a disruption

System Backup Procedures Outlines backup, recovery, and data restoration processes for critical systems