alt

차터 3일차 오전

Shared on October 26, 2026

Board Meeting: Cloud Organization, Communications, Website, and SARI Exercise

Overview

The board reviewed the updated cloud document structure, communication and outreach plans, public website performance, and findings from the SARI-32 exercise. Discussion focused on improving visibility, participant engagement, exercise procedures, and follow-up on recommendations.

Participants & Roles

  • Board meeting chair: Led the agenda and discussion.
  • Mark: Reported on the cloud reorganization.
  • Communication group representatives: Presented communications priorities and website updates.
  • Chris: Presented website and social media statistics.
  • SARI-32 training team: Reported on the exercise and its outcomes.
  • Agency representatives and ECOs: Provided feedback and recommendations.

Decisions Made

  • The communication group will continue work on a public satellite information page, which is scheduled to go live the following week. Agencies can review it after publication and report errors.
  • The new LinkedIn channel will be prepared for use; other social media platforms will be considered by the communication group.
  • The SARI-32 exercise highlighted the need to improve procedures, participation, and consistency. Recommendations will be tracked and addressed through relevant ES actions and system development.
  • Future SARI exercises should consider using relative timelines such as Day 0 and T+1, rather than calendar dates, to reduce confusion. The proposal remains subject to further planning.

Action Items

  • All member agencies: Nominate at least one communication representative.
  • Communication group and webmaster: Add communication-group actions to the shared action-tracking spreadsheet and consider distributing newsletters to ES and board members.
  • Member agencies: Review the satellite page after publication and provide satellite illustrations and sample data imagery.
  • Communication group: Explore outreach cooperation with UN-SPIDER and other organizations.
  • Agencies providing services: Encourage ECOs to complete all exercise workflows and contact the AU during exercises. Provide regular internal refresher training.
  • ES and training teams: Update SARI procedures and guidelines, follow up with participants who did not complete the exercise, and address identified contact, workflow, and scenario-consistency issues.
  • POST-Tune team: Review reported bugs and proposed interface and workflow improvements.
  • Future training teams: Use consistent simulated-AU responses and suitable email addresses; avoid shared group inboxes for AU contact where possible.
  • Exercise organizers: Consider a follow-up tracker showing how SARI recommendations are handled, and clarify exercise timing in future scenarios.

Discussion Points

Cloud document structure

  • The ownCloud README, files, and protocol documents were updated to reflect the revised structure.
  • The official-letters folder is being checked for completeness and currency.
  • The charter documents overview will guide users through the new structure. A fuller report will be shared once the review is complete.
  • The implementation plan is being updated to include additional sites, data, or server information.

Communications and outreach

  • Member agencies are expected to nominate communication representatives. The group meets monthly and discusses outreach and promotional work.
  • Topics included maintaining the public website, reviewing the newsletter’s audience and content, and refining web stories.
  • The group requested a shared action spreadsheet, broader newsletter distribution, and collaboration with external organizations to increase the charter’s visibility.
  • The satellite page will replace the less flexible PDF poster. Agencies were asked to provide satellite illustrations; sample satellite data may also be added.

Website and social media

  • Website traffic rose around major activations, particularly the Venezuela earthquake and Nepal floods. Activation listings, the charter overview, and resources were among the most visited pages.
  • News receives comparatively limited traffic. News visibility is expected to improve through homepage updates and a planned website release.
  • Most recorded news traffic was internal or direct. Social-media referrals may be undercounted because analytics track only users who accept cookies.
  • The X account had 7,582 followers at the end of September, up 40 in six months and 97 over the year. A LinkedIn channel has been created and is being prepared for launch.
  • Activation-related posts were among the most reposted content.

SARI-32 exercise

  • The exercise ran from 15 June to early August, with a forum held on 18 August. Its scenario involved floods, landslides, and storms in Russia’s Far East.
  • 41 ECOs participated; 32 completed the exercise. Nine did not complete it, including four who did not start. Only slightly more than half contacted the simulated AU.
  • An intentional priority inconsistency was included to test attentiveness. Most participants noticed it, but not all. The exercise also exposed gaps in checking disaster information, weather conditions, priorities, and scenario details.
  • Participants reported technical issues, outdated contact information, interface and workflow concerns, and confusion caused by different start dates.
  • The exercise tested a newly revised interface. Training and an updated manual were provided, though not all ECOs could attend preparatory training. Many participant suggestions were already implemented or planned for a forthcoming release.
  • Participants recommended more frequent practical training, clearer naming conventions, consistent scenario handling, and follow-up with ECOs who did not complete the exercise.
  • Feedback on non-contact with the AU suggested that shared inboxes can cause technical and attribution problems. Individual emails and clearer contact instructions were recommended.
Browse all public notes