@litfamily/lithermes 1.0.16 → 1.0.18
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +11 -11
- package/README_Ko-KR.md +11 -11
- package/assets/lithermes-plugin/core_contexts.py +2 -2
- package/assets/lithermes-plugin/payload-version.json +305 -53
- package/assets/lithermes-plugin/plugin.yaml +1 -1
- package/assets/lithermes-plugin/skills/frontend-ui-ux/references/complete-contract.md +2 -2
- package/assets/lithermes-plugin/skills/frontend-ui-ux/references/slop-register.md +3 -3
- package/assets/lithermes-plugin/skills/frontend-ui-ux/resources/THIRD-PARTY-NOTICE.txt +0 -5
- package/assets/lithermes-plugin/skills/lit-docx/SKILL.md +40 -7
- package/assets/lithermes-plugin/skills/lit-docx/references/components.md +150 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/direction-step.md +140 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/01-report-ko.md +115 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/02-brief-ko.md +79 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/03-manual-ko.md +93 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/04-proposal-ko.md +79 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/05-memo-en.md +45 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/06-journal-en.md +100 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/07-report-en.md +102 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/08-proposal-en.md +82 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/examples/09-memo-ko.md +37 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/page-composition.md +150 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/tonalities/brief.md +73 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/tonalities/journal.md +81 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/tonalities/manual.md +77 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/tonalities/memo.md +75 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/tonalities/proposal.md +83 -0
- package/assets/lithermes-plugin/skills/lit-docx/references/tonalities/report.md +83 -0
- package/assets/lithermes-plugin/skills/lit-docx/scripts/convert_md_to_docx.py +429 -93
- package/assets/lithermes-plugin/skills/lit-docx/scripts/docx_design.py +2429 -0
- package/assets/lithermes-plugin/skills/lit-docx/scripts/docx_gate.py +207 -0
- package/assets/lithermes-plugin/skills/lit-docx/scripts/docx_layout.py +945 -0
- package/assets/lithermes-plugin/skills/lit-docx/scripts/slop_lint.py +23 -6
- package/assets/lithermes-plugin/skills/lit-docx/templates/tonalities/brief.yaml +28 -0
- package/assets/lithermes-plugin/skills/lit-docx/templates/tonalities/journal.yaml +25 -0
- package/assets/lithermes-plugin/skills/lit-docx/templates/tonalities/manual.yaml +26 -0
- package/assets/lithermes-plugin/skills/lit-docx/templates/tonalities/memo.yaml +26 -0
- package/assets/lithermes-plugin/skills/lit-docx/templates/tonalities/proposal.yaml +26 -0
- package/assets/lithermes-plugin/skills/lit-docx/templates/tonalities/report.yaml +26 -0
- package/assets/lithermes-plugin/skills/lit-pptx/FORBIDDEN_TERMS.json +55 -0
- package/assets/lithermes-plugin/skills/lit-pptx/SKILL.md +39 -6
- package/assets/lithermes-plugin/skills/lit-pptx/agents/analyst.md +2 -2
- package/assets/lithermes-plugin/skills/lit-pptx/agents/antithesis.md +4 -3
- package/assets/lithermes-plugin/skills/lit-pptx/agents/architect.md +1 -1
- package/assets/lithermes-plugin/skills/lit-pptx/agents/critic.md +2 -1
- package/assets/lithermes-plugin/skills/lit-pptx/agents/synthesizer.md +1 -2
- package/assets/lithermes-plugin/skills/lit-pptx/agents/thesis.md +4 -4
- package/assets/lithermes-plugin/skills/lit-pptx/bin/office.mjs +2 -1
- package/assets/lithermes-plugin/skills/lit-pptx/pretendard-font/public/static/Pretendard-Bold.otf +0 -0
- package/assets/lithermes-plugin/skills/lit-pptx/pretendard-font/public/static/Pretendard-Regular.otf +0 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/anti-slop-checklist.md +9 -5
- package/assets/lithermes-plugin/skills/lit-pptx/references/authoring-guide.md +27 -12
- package/assets/lithermes-plugin/skills/lit-pptx/references/consensus-protocol.md +7 -3
- package/assets/lithermes-plugin/skills/lit-pptx/references/data-display-cookbook.md +3 -3
- package/assets/lithermes-plugin/skills/lit-pptx/references/density-and-fill.md +105 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/design-system-azure.md +3 -4
- package/assets/lithermes-plugin/skills/lit-pptx/references/direction-step.md +119 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/01-pitch-signal-ko.md +140 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/02-business-review-ledger-ko.md +138 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/03-research-talk-paper-en.md +133 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/04-lecture-chalk-ko.md +150 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/05-data-review-night-en.md +152 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/06-image-led-atlas-ko.md +137 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/07-briefing-gazette-ko.md +139 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/08-status-update-ledger-en.md +146 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/09-image-led-studio-en.md +145 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/10-research-talk-night-ko.md +140 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/11-lecture-studio-en.md +146 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/examples/12-status-update-gazette-ko.md +157 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/layout-families.md +132 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/title-treatments.md +110 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/atlas.md +92 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/chalk.md +97 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/gazette.md +103 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/ledger.md +97 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/night.md +107 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/paper.md +95 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/signal.md +97 -0
- package/assets/lithermes-plugin/skills/lit-pptx/references/tonalities/studio.md +95 -0
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/compile-deck.js +89 -64
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/craft_extras.py +28 -7
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/deck_output.py +635 -0
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/embed_fonts.py +1 -1
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/directive-parser.js +3 -8
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/gen-bg.js +2 -4
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/grid-resolver.js +503 -0
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/layout-resolver.js +410 -63
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/markdown-loader.js +6 -7
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/render-adapter-html.js +2 -2
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/render-adapter-pptx.js +487 -118
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/render-pack.js +3275 -0
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/slide-ast.js +81 -36
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/spec-validator.js +3 -9
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/lib/template-registry.js +331 -11
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/qa_deck.py +70 -34
- package/assets/lithermes-plugin/skills/lit-pptx/scripts/validate_pptx.py +24 -7
- package/assets/lithermes-plugin/skills/lit-pptx/templates/enrolled/AZURE-A2Z/layout-mapping.yaml +1 -1
- package/assets/lithermes-plugin/skills/lit-pptx/templates/enrolled/AZURE-A2Z/template.yaml +4 -1
- package/assets/lithermes-plugin/skills/lit-pptx/templates/enrolled/AZURE-PRO/layout-mapping.yaml +1 -1
- package/assets/lithermes-plugin/skills/lit-pptx/templates/enrolled/AZURE-PRO/template.yaml +4 -1
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/atlas/pack.yaml +92 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/chalk/pack.yaml +97 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/gazette/pack.yaml +93 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/ledger/pack.yaml +94 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/night/pack.yaml +93 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/paper/pack.yaml +98 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/signal/pack.yaml +94 -0
- package/assets/lithermes-plugin/skills/lit-pptx/templates/tonalities/studio/pack.yaml +92 -0
- package/assets/lithermes-plugin/skills/lit-typographic-motion/bin/runtime.mjs +2 -2
- package/assets/lithermes-plugin/skills/lit-typographic-motion/engine/THIRD_PARTY_NOTICES +2 -2
- package/assets/lithermes-plugin/skills/lit-typographic-motion/engine/frame.mjs +3 -3
- package/assets/lithermes-plugin/skills/lit-typographic-motion/engine/gate.mjs +1 -1
- package/assets/lithermes-plugin/skills/lit-typographic-motion/references/runtime.md +1 -1
- package/assets/lithermes-plugin/skills/lit-typographic-motion/references/style-bibles.md +2 -2
- package/assets/lithermes-plugin/skills/lit-typographic-motion/references/type-craft.md +4 -4
- package/assets/lithermes-plugin/skills/visual-qa/references/complete-contract.md +2 -2
- package/package.json +1 -1
- package/readme-assets/badge-version.svg +1 -1
- package/assets/lithermes-plugin/skills/lit-pptx/pretendard-font/public/static/PretendardGOV-Bold.otf +0 -0
- package/assets/lithermes-plugin/skills/lit-pptx/pretendard-font/public/static/PretendardGOV-Regular.otf +0 -0
|
@@ -0,0 +1,93 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 연구동 실험 폐액 수거·보관 절차서
|
|
3
|
+
subtitle: 예시 연구원 제1연구동 폐액 분류, 용기 관리, 수거, 누출 대응
|
|
4
|
+
author: 예시 연구원 연구안전팀
|
|
5
|
+
organization: 예시 연구원
|
|
6
|
+
date: 2026-10-19
|
|
7
|
+
short_title: 실험 폐액 수거·보관 절차서
|
|
8
|
+
notice: "예시 데이터: 기관·물질 구분·수치는 모두 가정입니다"
|
|
9
|
+
tonality: Manual
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=typographic kicker="안전 절차서"
|
|
13
|
+
제1연구동 실험실에서 폐액을 모으고, 수거 날에 넘기고, 보관실에서 위탁 처리 전까지 보관하는 사람을 위한 절차서다.
|
|
14
|
+
:::
|
|
15
|
+
|
|
16
|
+
# 적용 범위와 책임
|
|
17
|
+
|
|
18
|
+
## 폐액 구분
|
|
19
|
+
|
|
20
|
+
이 절차서는 제1연구동 실험실 28곳과 지하 1층 폐액 보관실에 적용한다. 폐액은 섞으면 반응할 수 있는 성질에 따라 다섯 가지로 나누어 모은다.
|
|
21
|
+
|
|
22
|
+
표 1. 폐액 구분과 용기 (예시)
|
|
23
|
+
|
|
24
|
+
| 구분 | 대표 물질 | 용기 | 라벨 색 |
|
|
25
|
+
| --- | --- | --- | --- |
|
|
26
|
+
| 할로겐 유기 | 클로로포름 | 20 L 고밀도 폴리에틸렌 | 주황 |
|
|
27
|
+
| 비할로겐 유기 | 아세톤, 에탄올 | 20 L 고밀도 폴리에틸렌 | 노랑 |
|
|
28
|
+
| 산성 수용액 | 묽은 염산 | 10 L 내산성 용기 | 빨강 |
|
|
29
|
+
| 염기성 수용액 | 묽은 수산화나트륨 | 10 L 내염기성 용기 | 파랑 |
|
|
30
|
+
| 중금속 함유 | 크로뮴 함유 용액 | 5 L 밀폐 용기 | 회색 |
|
|
31
|
+
|
|
32
|
+
자료: 예시 연구원 화학물질 관리 기준(2026년 6월 개정)
|
|
33
|
+
|
|
34
|
+
## 역할과 책임
|
|
35
|
+
|
|
36
|
+
::: sidebar title="연락처" width=third
|
|
37
|
+
- **연구안전팀 당직**: 내선 5520
|
|
38
|
+
- **보관실 관리자**: 내선 5524
|
|
39
|
+
- **시설 당직실**: 내선 5000
|
|
40
|
+
:::
|
|
41
|
+
|
|
42
|
+
실험실 책임자는 용기와 라벨을 관리하고 수거 신청을 넣는다. 실험 수행자는 폐액을 맞는 용기에 붓고 투입 기록을 남긴다. 연구안전팀은 수거, 보관실 운영, 위탁 처리를 맡는다.
|
|
43
|
+
|
|
44
|
+
구분을 알 수 없는 폐액은 붓지 않는다. 원래 용기째 밀봉하고 물질 이름을 적어 당직에게 연락한다.
|
|
45
|
+
|
|
46
|
+
# 실험실 안 폐액 모으기
|
|
47
|
+
|
|
48
|
+
## 투입 순서
|
|
49
|
+
|
|
50
|
+
1. 흄 후드 안에서 보안경과 내화학 장갑을 착용하고 작업한다.
|
|
51
|
+
2. 용기 라벨의 구분이 버리려는 폐액과 같은지 확인한다.
|
|
52
|
+
3. 투입 기록지에 날짜, 물질 이름, 양, 이름을 적는다.
|
|
53
|
+
4. 깔때기로 천천히 붓고, 용기의 80% 위로는 채우지 않는다.
|
|
54
|
+
5. 뚜껑을 바로 닫고 용기를 2차 용기 안에 다시 놓는다.
|
|
55
|
+
|
|
56
|
+
::: callout kind=warning title="서로 다른 구분 섞지 않기"
|
|
57
|
+
산성과 염기성 수용액, 산화성 물질과 유기 용매를 한 용기에 섞으면 열과 기체가 나며 용기가 터질 수 있다. 헷갈리면 붓지 말고 당직에게 먼저 묻는다.
|
|
58
|
+
:::
|
|
59
|
+
|
|
60
|
+
## 용기 관리 기준
|
|
61
|
+
|
|
62
|
+
표 2. 실험실 용기 관리 기준 (예시)
|
|
63
|
+
|
|
64
|
+
| 항목 | 기준 | 벗어나면 |
|
|
65
|
+
| --- | --- | --- |
|
|
66
|
+
| 채움 높이 | 용기 용량의 80% 이하 | 새 용기로 바꾸고 수거 신청 |
|
|
67
|
+
| 보관 기간 | 처음 투입한 날부터 90일 이내 | 양과 관계없이 수거 신청 |
|
|
68
|
+
| 보관량 | 실험실당 합계 60 L 이하 | 추가 투입 중단, 수거 신청 |
|
|
69
|
+
|
|
70
|
+
주: 기준은 이 연구원 내부 기준의 예시이며, 실제 기준은 해당 법령과 기관 규정을 따른다.
|
|
71
|
+
|
|
72
|
+
# 층별 수거
|
|
73
|
+
|
|
74
|
+
수거는 매주 화요일 오전, 층별로 한다. 실험실 책임자는 전주 금요일 17시까지 연구안전 시스템에 용기 수와 구분을 등록하고, 등록하지 않은 용기는 그 주에 수거하지 않으므로 다음 주까지 실험실에 둔다.
|
|
75
|
+
|
|
76
|
+
1. 용기를 실험실 문 안쪽의 정해진 자리로 옮긴다.
|
|
77
|
+
2. 수거자와 함께 라벨, 기록지, 무게를 확인하고 서명한다.
|
|
78
|
+
3. 빈 용기를 같은 구분으로 받아 새 라벨을 붙인다.
|
|
79
|
+
|
|
80
|
+
# 누출 대응
|
|
81
|
+
|
|
82
|
+
1 L 이하의 누출은 실험실에서 처리한다. 먼저 주변 사람에게 알리고 가열판과 버너 같은 점화원을 모두 끈 뒤, 흡착 패드를 누출 범위의 바깥에서 안쪽으로 옮겨 가며 닦아 낸다. 피부에 묻으면 15분 이상 흐르는 물로 씻는다.
|
|
83
|
+
|
|
84
|
+
양이 많으면 다르다. 실험실을 비우고 문을 닫은 뒤 당직에게 연락한다. 보관실 누출이면 들어가지 않는다. 출입문의 비상 배기 버튼을 누르고, 당직이 올 때까지 복도 출입을 막으며, 누출된 물질과 양을 아는 사람이 현장에 남아 상황을 설명한다.
|
|
85
|
+
|
|
86
|
+
# 개정 이력
|
|
87
|
+
|
|
88
|
+
표 3. 개정 이력 (예시)
|
|
89
|
+
|
|
90
|
+
| 판 | 시행일 | 주요 내용 | 작성 |
|
|
91
|
+
| --- | --- | --- | --- |
|
|
92
|
+
| 1.0 | 2025. 2. 3. | 최초 제정 | 연구안전팀 |
|
|
93
|
+
| 1.1 | 2026. 10. 19. | 보관 기간 90일 기준 추가 | 연구안전팀 |
|
|
@@ -0,0 +1,79 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 산업단지 공동 통근버스 시범 운행 제안서
|
|
3
|
+
subtitle: 예시 산업단지 입주기업 공동 6개월 시범 운행 계획과 예산
|
|
4
|
+
author: 예시 산업단지 입주기업협의회 사무국
|
|
5
|
+
organization: 예시 산업단지 입주기업협의회
|
|
6
|
+
date: 2026-10-21
|
|
7
|
+
short_title: 공동 통근버스 시범 운행 제안
|
|
8
|
+
notice: "예시 데이터: 단체·노선·금액은 모두 가정입니다"
|
|
9
|
+
tonality: Proposal
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=typographic kicker="사업 제안서"
|
|
13
|
+
지하철역 두 곳과 산업단지를 잇는 공동 통근버스 4개 노선을 2027년 3월부터 6개월 동안 시범 운행하자는 제안이다.
|
|
14
|
+
:::
|
|
15
|
+
|
|
16
|
+
# 제안 개요
|
|
17
|
+
|
|
18
|
+
예시 산업단지에는 42개 기업, 직원 약 6,800명이 일한다. 가장 가까운 지하철역까지 3km가 넘어, 2026년 9월 설문에서 직원의 71%가 자가용으로 출근한다고 답했다. 출근 시간대 진입로 정체는 평균 25분이다.
|
|
19
|
+
|
|
20
|
+
::: keyfigures
|
|
21
|
+
- **하루 1,200명** 통근버스 이용 목표 (예시)
|
|
22
|
+
- 2026년 9월 설문의 이용 의향 비율을 전체 직원 수에 적용
|
|
23
|
+
- **8%p** 자가용 출근 비율 감소 목표 (예시)
|
|
24
|
+
- 71%에서 63%로, 시범 마지막 달 설문 기준
|
|
25
|
+
- **약 3.8만 원** 이용자 1인당 월 기업 부담 (예시)
|
|
26
|
+
- 기업 분담금 2.73억 원을 6개월과 하루 이용 목표로 나눈 값
|
|
27
|
+
:::
|
|
28
|
+
|
|
29
|
+
공동 노선이면 자체 버스가 없는 작은 기업 직원도 탈 수 있다.
|
|
30
|
+
|
|
31
|
+
::: callout kind=key title="결정 요청"
|
|
32
|
+
2026년 12월 총회에서 시범 사업비 3.9억 원(예시) 가운데 기업 분담분 2.73억 원의 분담 기준과 2027년 3월 운행 시작을 승인해 주기를 요청한다.
|
|
33
|
+
:::
|
|
34
|
+
|
|
35
|
+
# 현황
|
|
36
|
+
|
|
37
|
+
표 1. 출근 수단별 비중 (2026년 9월 설문, 예시)
|
|
38
|
+
|
|
39
|
+
| 출근 수단 | 응답자 (명) | 비중 (%) |
|
|
40
|
+
| --- | ---: | ---: |
|
|
41
|
+
| 자가용 | 1,669 | 71.0 |
|
|
42
|
+
| 기업 자체 통근버스 | 270 | 11.5 |
|
|
43
|
+
| 시내버스 | 230 | 9.8 |
|
|
44
|
+
| 기타 | 181 | 7.7 |
|
|
45
|
+
| 합계 | 2,350 | 100.0 |
|
|
46
|
+
|
|
47
|
+
자료: 입주기업협의회 출퇴근 실태 설문
|
|
48
|
+
|
|
49
|
+
주차면은 약 3,600면인데 평일 오전 주차 차량은 4,100대 안팎이다. 남는 차량은 진입로와 이면 도로에 서서 화물차 진입을 늦춘다.
|
|
50
|
+
|
|
51
|
+
# 운행 계획
|
|
52
|
+
|
|
53
|
+
45인승 버스 8대가 출퇴근 시간에 4개 노선을 노선마다 하루 16회씩 다닌다. 하루 2,880석으로, 이용 목표 1,200명의 왕복 승차 2,400회를 받을 수 있다.
|
|
54
|
+
|
|
55
|
+
# 예산과 일정
|
|
56
|
+
|
|
57
|
+
표 2. 시범 사업비 내역 (6개월, 예시)
|
|
58
|
+
|
|
59
|
+
| 항목 | 내용 | 금액 (만 원) |
|
|
60
|
+
| --- | --- | ---: |
|
|
61
|
+
| 버스 임차 | 45인승 8대, 대당 월 650만 원 | 31,200 |
|
|
62
|
+
| 정류장 시설 | 표지판, 대기 쉼터 4곳 | 2,400 |
|
|
63
|
+
| 승차 확인 | 단말기 8대, 앱 기능 | 1,800 |
|
|
64
|
+
| 운영 관리 | 전담 인력 1명 | 2,100 |
|
|
65
|
+
| 홍보와 예비비 | 설명회, 노선 조정 대비 | 1,500 |
|
|
66
|
+
| 합계 | | 39,000 |
|
|
67
|
+
|
|
68
|
+
주: 기업 분담 70%(2.73억 원), 시 지원금 30%(1.17억 원)로 가정한 예시이며, 부가가치세를 포함한다.
|
|
69
|
+
|
|
70
|
+
표 3. 추진 일정 (예시)
|
|
71
|
+
|
|
72
|
+
| 시기 | 할 일 | 담당 |
|
|
73
|
+
| --- | --- | --- |
|
|
74
|
+
| 2026년 12월 | 협의회 총회 승인, 시 지원금 신청 | 사무국 |
|
|
75
|
+
| 2027년 2월 | 정류장 설치, 승차 앱 배포 | 사무국, 운수 업체 |
|
|
76
|
+
| 2027년 3월 | 시범 운행 시작 | 운수 업체 |
|
|
77
|
+
| 2027년 8월 | 결과 보고, 정식 운행 여부 결정 | 사무국 |
|
|
78
|
+
|
|
79
|
+
가장 큰 위험은 시 지원금이 늦게 확정되는 경우다. 결정이 2월을 넘기면 첫 달은 4대로 두 노선만 운행한다.
|
|
@@ -0,0 +1,45 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Expense claims in the new finance system from 1 December
|
|
3
|
+
subtitle: Cut-off dates, receipts and approval routes for all staff
|
|
4
|
+
author: Finance Operations
|
|
5
|
+
organization: Example Org
|
|
6
|
+
date: 2026-10-26
|
|
7
|
+
short_title: Expense claims from 1 December
|
|
8
|
+
notice: "Sample memo: names, dates and amounts are examples"
|
|
9
|
+
tonality: Memo
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=masthead kicker="Notice"
|
|
13
|
+
To: All staff and budget holders · From: Finance Operations · Subject: Moving expense claims to the new finance system
|
|
14
|
+
:::
|
|
15
|
+
|
|
16
|
+
# Summary of the change
|
|
17
|
+
|
|
18
|
+
From Monday 1 December, expense claims are made in the new finance system instead of the spreadsheet form and email approval. The old form closes on Friday 21 November. Reimbursement moves from a monthly run to a weekly one, so most claims will be paid within eight working days of approval.
|
|
19
|
+
|
|
20
|
+
# Changes by group
|
|
21
|
+
|
|
22
|
+
## Claimants
|
|
23
|
+
|
|
24
|
+
Attach a photo or scan of each receipt to its claim line, and keep the paper receipt for three months. Mileage takes two postcodes.
|
|
25
|
+
|
|
26
|
+
## Budget holders
|
|
27
|
+
|
|
28
|
+
Claims arrive in your approval list instead of your inbox. Approve or return each one within five working days; after that it moves to your own manager. Set a delegate before any absence longer than a week.
|
|
29
|
+
|
|
30
|
+
## Corporate card holders
|
|
31
|
+
|
|
32
|
+
Card transactions appear each night. Add the receipt and a cost code. You no longer send a separate monthly statement, and transactions left without a receipt for more than thirty days are listed to your budget holder.
|
|
33
|
+
|
|
34
|
+
# Key dates
|
|
35
|
+
|
|
36
|
+
| Date | Step | Who |
|
|
37
|
+
| --- | --- | --- |
|
|
38
|
+
| 3-14 November | Thirty-minute online briefings | All staff |
|
|
39
|
+
| 21 November | Last day for the old spreadsheet form | Claimants |
|
|
40
|
+
| 1 December | New system opens | Everyone |
|
|
41
|
+
| 5 December | First weekly reimbursement run | Finance Operations |
|
|
42
|
+
|
|
43
|
+
Source: Finance Operations project plan, October 2026 (sample)
|
|
44
|
+
|
|
45
|
+
Questions go to extension 4170 or the finance request form.
|
|
@@ -0,0 +1,100 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Surface heat in primary school playgrounds
|
|
3
|
+
subtitle: Two summers of field measurements across fourteen schools
|
|
4
|
+
author: Example Urban Climate Group
|
|
5
|
+
organization: Example Org
|
|
6
|
+
date: 2026-10-28
|
|
7
|
+
short_title: Playground surface heat
|
|
8
|
+
notice: "Sample white paper: schools, figures and findings are examples"
|
|
9
|
+
tonality: Journal
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=masthead kicker="White paper"
|
|
13
|
+
:::
|
|
14
|
+
|
|
15
|
+
# Background
|
|
16
|
+
|
|
17
|
+
Most primary school playgrounds in the study city are open asphalt laid decades ago. On a clear summer afternoon that surface absorbs sunlight for hours, and by the lunch break it can be far hotter than the air above it.
|
|
18
|
+
|
|
19
|
+
The study covered fourteen primary schools in 2025 and 2026. Every school had open asphalt, and most also had at least one other surface. Each surface was treated as a separate measured patch, so that surfaces could be compared within the same school on the same afternoon.
|
|
20
|
+
|
|
21
|
+
Table 1. Measured surface patches by type (sample data)
|
|
22
|
+
|
|
23
|
+
| Surface and cover | Schools with this patch | Typical patch area (m²) |
|
|
24
|
+
| --- | ---: | ---: |
|
|
25
|
+
| Asphalt, unshaded | 14 | 600-1,800 |
|
|
26
|
+
| Asphalt under tree canopy | 9 | 150-400 |
|
|
27
|
+
| Asphalt under shade sail | 5 | 80-200 |
|
|
28
|
+
| Rubber safety surface, unshaded | 8 | 60-250 |
|
|
29
|
+
| Grass, unshaded | 11 | 300-1,200 |
|
|
30
|
+
|
|
31
|
+
Source: school site surveys, spring 2025 (sample)
|
|
32
|
+
|
|
33
|
+
## Measurement approach
|
|
34
|
+
|
|
35
|
+
A hot day was a school day on which the air temperature at the nearest weather station reached 30 °C; there were 23 in 2025 and 31 in 2026. A fixed infrared sensor above each patch logged surface temperature every ten minutes, and the 14:00 value was used for comparison. Active play is time a child spends running, climbing or in a ball game, recorded by observers who scanned set zones every five minutes during the lunch break.
|
|
36
|
+
|
|
37
|
+
# Surface temperatures
|
|
38
|
+
|
|
39
|
+
Surface type and shade made a large difference, and the ranking was the same in both summers. Unshaded rubber was hottest, which matters because it lies under climbing frames where children sit and put their hands. Shaded asphalt was coolest, about 20 °C below the same material in the sun.
|
|
40
|
+
|
|
41
|
+
Table 2. Median surface temperature at 14:00 on hot days (sample data)
|
|
42
|
+
|
|
43
|
+
| Surface and cover | 2025 (°C) | 2026 (°C) | Difference from unshaded asphalt, 2026 (°C) |
|
|
44
|
+
| --- | ---: | ---: | ---: |
|
|
45
|
+
| Rubber safety surface, unshaded | 58 | 60 | +6 |
|
|
46
|
+
| Asphalt, unshaded | 52 | 54 | 0 |
|
|
47
|
+
| Grass, unshaded | 36 | 39 | -15 |
|
|
48
|
+
| Asphalt under shade sail | 38 | 39 | -15 |
|
|
49
|
+
| Asphalt under tree canopy | 33 | 34 | -20 |
|
|
50
|
+
|
|
51
|
+
Source: patch infrared sensors, summer terms 2025 and 2026 (sample)
|
|
52
|
+
|
|
53
|
+
Grass rose the most in the dry second summer. Sails and trees cooled the surface by similar amounts at midday, but a sail's shade moves off its patch as the sun moves west. By 15:30 the surface under sails had risen by a median of 6 °C, while under canopy it stayed within 2 °C of the 14:00 value.
|
|
54
|
+
|
|
55
|
+
# Use of the playground
|
|
56
|
+
|
|
57
|
+
Shade changed how children used the playground. Six schools had at least 30 % shade over their main play area, and eight had less than 10 %. On mild days active play was almost the same in both groups. On hot days it fell by nearly half in the low-shade schools.
|
|
58
|
+
|
|
59
|
+
Table 3. Active play per child during the lunch break (sample data)
|
|
60
|
+
|
|
61
|
+
| School group | Schools | Mild days (minutes) | Hot days (minutes) | Change on hot days (%) |
|
|
62
|
+
| --- | ---: | ---: | ---: | ---: |
|
|
63
|
+
| Shade cover of 30 % or more | 6 | 24 | 21 | -13 |
|
|
64
|
+
| Shade cover below 10 % | 8 | 23 | 13 | -43 |
|
|
65
|
+
|
|
66
|
+
Note: mild days are school days with a maximum air temperature between 20 and 25 °C. Source: observer scans, summer terms 2025 and 2026 (sample)
|
|
67
|
+
|
|
68
|
+
In the low-shade schools, children crowded into narrow strips of shade along building walls, and play there was mostly sitting and talking. Five of those eight schools kept younger pupils indoors at lunch when the forecast passed 30 °C; none of the high-shade schools had such a rule.
|
|
69
|
+
|
|
70
|
+
# Cost and maintenance
|
|
71
|
+
|
|
72
|
+
The three measures a school could add within one summer holiday differ in cost, in how soon they work and in upkeep.
|
|
73
|
+
|
|
74
|
+
Table 4. Cost of cooling measures per 100 m² of playground (sample data)
|
|
75
|
+
|
|
76
|
+
| Measure | Installed cost (thousand) | Full effect | Annual upkeep (thousand) |
|
|
77
|
+
| --- | ---: | --- | ---: |
|
|
78
|
+
| Shade sail with posts | 9.0 | At once | 0.6 |
|
|
79
|
+
| Three large-stock trees with tree pits | 6.0 | After 8-12 years | 0.3 |
|
|
80
|
+
| Grass in place of asphalt | 4.0 | After one season | 0.5 |
|
|
81
|
+
|
|
82
|
+
Source: city grounds contractors' price list, 2026 (sample)
|
|
83
|
+
|
|
84
|
+
Sails come down each autumn and last eight to ten years. Trees are cheapest and grow more effective each year, but shade little in their first summers. Grass needs watering in dry spells to keep its cooling effect.
|
|
85
|
+
|
|
86
|
+
::: callout kind=note title="Scope of the measurements"
|
|
87
|
+
The sensors measured surface temperature only. Air temperature at child height, radiant heat and ultraviolet exposure were not recorded.
|
|
88
|
+
:::
|
|
89
|
+
|
|
90
|
+
# Discussion
|
|
91
|
+
|
|
92
|
+
Shade over the surfaces children use is the measure that changed both temperature and behaviour, and mature trees did best across the whole afternoon. Two limits apply. The schools were not chosen at random, and those with mature trees tended to have larger grounds. And two summers is a short record.
|
|
93
|
+
|
|
94
|
+
# Recommendations
|
|
95
|
+
|
|
96
|
+
Order matters. The findings suggest a sequence for a school planning changes to its playground. First, shade the rubber surfaces under play equipment, with a sail if no tree can reach them, since these are the hottest patches and the ones children touch. Second, plant trees along the south and west edges of the main asphalt area now, accepting that their shade will come in later years. Third, replace little-used asphalt with grass only where it can be watered.
|
|
97
|
+
|
|
98
|
+
# Further work
|
|
99
|
+
|
|
100
|
+
The sensors stay for a third summer. A follow-up study will add air temperature at one metre and radiant heat measured with globe thermometers.
|
|
@@ -0,0 +1,102 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: Smart water meter programme, first-year results
|
|
3
|
+
subtitle: Installation, reading reliability and leak response, October 2025 to September 2026
|
|
4
|
+
author: Metering Programme Office
|
|
5
|
+
organization: Example Water Utility
|
|
6
|
+
date: 2026-10-29
|
|
7
|
+
short_title: Smart meter programme, year one
|
|
8
|
+
notice: "Sample report: volumes, rates and costs are examples"
|
|
9
|
+
tonality: Report
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=typographic kicker="Annual programme report"
|
|
13
|
+
The programme replaced 17,600 household water meters in its first year, 10 % ahead of plan, and the new meters now send a reading every day.
|
|
14
|
+
:::
|
|
15
|
+
|
|
16
|
+
# Summary
|
|
17
|
+
|
|
18
|
+
The first year met all three of its targets. Installations ran ahead of plan from January, daily readings arrived from more than 98 % of the new meters, and estimated bills fell from 11 % to 1.2 % in the converted areas. The weak point is meters in basements, where the radio signal is poor.
|
|
19
|
+
|
|
20
|
+
::: keyfigures
|
|
21
|
+
- **17,600** meters installed (sample)
|
|
22
|
+
- October 2025 to September 2026, work order system; plan 16,000
|
|
23
|
+
- **98.4%** daily read success (sample)
|
|
24
|
+
- Share of expected daily readings received, all installed meters
|
|
25
|
+
- **9 days** median customer leak duration after alert (sample)
|
|
26
|
+
- Confirmed leaks only; previously about 41 days
|
|
27
|
+
:::
|
|
28
|
+
|
|
29
|
+
::: callout kind=key title="Request to the programme board"
|
|
30
|
+
Approve €180,000 (sample) for 400 signal repeaters and the change to the installer contract that adds Saturday appointments from January 2027.
|
|
31
|
+
:::
|
|
32
|
+
|
|
33
|
+
# Programme scope
|
|
34
|
+
|
|
35
|
+
The programme replaces all 48,000 household meters in the northern supply zone over three years. The old meters were read by hand once a quarter, and about one read in nine was an estimate. The new meters send a daily reading over a low-power radio network. Year one started where estimates were worst.
|
|
36
|
+
|
|
37
|
+
Read success is the number of daily readings received divided by the number expected. A leak alert is raised when a meter records continuous flow for 48 hours, which in a household almost always means a leak or a running toilet.
|
|
38
|
+
|
|
39
|
+
# Installation progress
|
|
40
|
+
|
|
41
|
+
The first quarter fell short because the installer contract started late. From January the crews worked at full strength, and every later quarter exceeded its plan.
|
|
42
|
+
|
|
43
|
+
Table 1. Meters installed by quarter (sample data)
|
|
44
|
+
|
|
45
|
+
| Quarter | Plan | Installed | Share of plan (%) |
|
|
46
|
+
| --- | ---: | ---: | ---: |
|
|
47
|
+
| October-December 2025 | 3,000 | 2,650 | 88 |
|
|
48
|
+
| January-March 2026 | 4,000 | 4,300 | 108 |
|
|
49
|
+
| April-June 2026 | 4,500 | 5,150 | 114 |
|
|
50
|
+
| July-September 2026 | 4,500 | 5,500 | 122 |
|
|
51
|
+
| Year | 16,000 | 17,600 | 110 |
|
|
52
|
+
|
|
53
|
+
Source: installer work order system (sample)
|
|
54
|
+
|
|
55
|
+
One booked visit in seven ended without an installation, mostly because nobody was home. Most of those households asked for a Saturday slot when called back.
|
|
56
|
+
|
|
57
|
+
# Reading reliability
|
|
58
|
+
|
|
59
|
+
Read success depends on where the meter sits. Basement meters lose readings when the signal cannot reach a collector through walls and floors.
|
|
60
|
+
|
|
61
|
+
Table 2. Daily read success by meter location (sample data)
|
|
62
|
+
|
|
63
|
+
| Meter location | Meters installed | Read success (%) |
|
|
64
|
+
| --- | ---: | ---: |
|
|
65
|
+
| Kerbside chamber | 11,900 | 99.3 |
|
|
66
|
+
| Front garden box | 3,700 | 98.6 |
|
|
67
|
+
| Inside property | 1,000 | 96.0 |
|
|
68
|
+
| Basement | 1,000 | 89.5 |
|
|
69
|
+
| All locations | 17,600 | 98.4 |
|
|
70
|
+
|
|
71
|
+
Source: meter data platform, September 2026 (sample)
|
|
72
|
+
|
|
73
|
+
A field test fitted a signal repeater outside twelve buildings with basement meters, and their read success rose from 88 % to 99 %. A repeater costs about €450 installed.
|
|
74
|
+
|
|
75
|
+
# Leak detection
|
|
76
|
+
|
|
77
|
+
The daily data revealed many more customer-side leaks than quarterly reads did.
|
|
78
|
+
|
|
79
|
+
Table 3. Leak alerts and outcomes (sample data)
|
|
80
|
+
|
|
81
|
+
| Outcome | Alerts |
|
|
82
|
+
| --- | ---: |
|
|
83
|
+
| Confirmed leak, fixed within 14 days | 1,450 |
|
|
84
|
+
| Confirmed leak, fixed after 14 days | 380 |
|
|
85
|
+
| Confirmed leak, not yet fixed | 130 |
|
|
86
|
+
| No leak found | 350 |
|
|
87
|
+
| Total alerts | 2,310 |
|
|
88
|
+
|
|
89
|
+
Source: customer service case records (sample)
|
|
90
|
+
|
|
91
|
+
# Second-year plan
|
|
92
|
+
|
|
93
|
+
The second year raises the target to 18,000 meters in four districts with older housing, where repeaters will be fitted at installation.
|
|
94
|
+
|
|
95
|
+
Table 4. Second-year plan (sample data)
|
|
96
|
+
|
|
97
|
+
| Period | Step | Owner |
|
|
98
|
+
| --- | --- | --- |
|
|
99
|
+
| November 2026 | Board decision on repeaters and Saturday appointments | Programme office |
|
|
100
|
+
| January 2027 | Saturday appointments start | Installer |
|
|
101
|
+
| April 2027 | Work starts in the four older districts | Installer |
|
|
102
|
+
| September 2027 | Year-two report to the board | Programme office |
|
|
@@ -0,0 +1,82 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: On-demand minibus service for outlying villages
|
|
3
|
+
subtitle: Funding proposal for a twenty-four-month pilot in eleven villages
|
|
4
|
+
author: Example District Transport Partnership
|
|
5
|
+
organization: Example Org
|
|
6
|
+
date: 2026-10-30
|
|
7
|
+
short_title: Village minibus proposal
|
|
8
|
+
notice: "Sample proposal: organisations, budget and figures are examples"
|
|
9
|
+
tonality: Proposal
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=typographic kicker="Funding proposal"
|
|
13
|
+
Two accessible minibuses, booked by phone or app, linking eleven villages that lost their bus route in 2019 with the market town, its health centre and the railway station.
|
|
14
|
+
:::
|
|
15
|
+
|
|
16
|
+
# Proposal in brief
|
|
17
|
+
|
|
18
|
+
Eleven villages have had no scheduled bus since 2019. Residents without a car, about one in five households, depend on lifts or a taxi fare of €25 to €40 each way. This proposal funds two eight-seat minibuses with wheelchair access that collect passengers on request, Monday to Saturday from 07:00 to 19:00.
|
|
19
|
+
|
|
20
|
+
::: keyfigures
|
|
21
|
+
- **11** villages served (sample)
|
|
22
|
+
- 4,300 residents, district population register 2026
|
|
23
|
+
- **About 1,500** passenger trips a month by month 12 (sample)
|
|
24
|
+
- Based on take-up in two comparable rural schemes
|
|
25
|
+
- **About €13** public funding per trip (sample)
|
|
26
|
+
- Pilot cost less expected fares, over 28,000 expected trips
|
|
27
|
+
:::
|
|
28
|
+
|
|
29
|
+
::: callout kind=key title="Decision requested"
|
|
30
|
+
Approval of €410,000 (sample) from the 2027 rural mobility fund round, with the service starting on 1 April 2027.
|
|
31
|
+
:::
|
|
32
|
+
|
|
33
|
+
# Need and evidence
|
|
34
|
+
|
|
35
|
+
The villages form three clusters, each five to twelve kilometres from the nearest hourly bus. Almost a quarter of residents are over seventy.
|
|
36
|
+
|
|
37
|
+
Table 1. Village clusters in the pilot area (sample data)
|
|
38
|
+
|
|
39
|
+
| Cluster | Villages | Residents | Residents over 70 |
|
|
40
|
+
| --- | ---: | ---: | ---: |
|
|
41
|
+
| North | 4 | 1,500 | 360 |
|
|
42
|
+
| East | 3 | 1,200 | 290 |
|
|
43
|
+
| South | 4 | 1,600 | 340 |
|
|
44
|
+
| Total | 11 | 4,300 | 990 |
|
|
45
|
+
|
|
46
|
+
Source: district population register, 2026 (sample)
|
|
47
|
+
|
|
48
|
+
The health centre recorded 1,140 missed appointments from these villages in 2025, a rate per resident almost twice that of the town, and its patient survey named transport as the most common reason.
|
|
49
|
+
|
|
50
|
+
# Service design
|
|
51
|
+
|
|
52
|
+
Passengers book up to a week ahead or until 17:00 the day before. The booking system groups requests into shared runs to four fixed destinations: the health centre, the station, the market square and the supermarket. The fare is €2 a single trip; for holders of the national concessionary pass the fare is paid by the national scheme.
|
|
53
|
+
|
|
54
|
+
Table 2. Pilot budget over twenty-four months (sample data)
|
|
55
|
+
|
|
56
|
+
| Item | Detail | Amount (€) |
|
|
57
|
+
| --- | --- | ---: |
|
|
58
|
+
| Vehicle leases | Two accessible minibuses, €1,250 a month each | 60,000 |
|
|
59
|
+
| Drivers | 2.5 full-time posts, two years | 240,000 |
|
|
60
|
+
| Fuel and insurance | Both vehicles, two years | 52,000 |
|
|
61
|
+
| Booking system | Software licence, phone line, setup | 38,000 |
|
|
62
|
+
| Evaluation | Independent evaluation, final report | 12,000 |
|
|
63
|
+
| Publicity and travel training | Leaflets, village sessions | 8,000 |
|
|
64
|
+
| Total | | 410,000 |
|
|
65
|
+
|
|
66
|
+
Note: expected fare income of about €56,000 is not deducted from the request and will be reported quarterly to the fund.
|
|
67
|
+
|
|
68
|
+
# Outcomes and evaluation
|
|
69
|
+
|
|
70
|
+
The evaluation compares the cost per trip with the taxi journeys and volunteer lifts the service replaces.
|
|
71
|
+
|
|
72
|
+
Table 3. Pilot measures and how they are counted (sample data)
|
|
73
|
+
|
|
74
|
+
| Measure | Expected over the pilot | Counted by |
|
|
75
|
+
| --- | ---: | --- |
|
|
76
|
+
| Passenger trips | 28,000 | Booking system records |
|
|
77
|
+
| Trips by wheelchair users | 1,200 | Driver trip sheets |
|
|
78
|
+
| Missed health appointments | 25 % fewer | Health centre records |
|
|
79
|
+
|
|
80
|
+
Source: Example District Transport Partnership pilot plan (sample)
|
|
81
|
+
|
|
82
|
+
The main risk is slow take-up, which village hall sessions on booking are meant to reduce.
|
|
@@ -0,0 +1,37 @@
|
|
|
1
|
+
---
|
|
2
|
+
title: 본관 지하 주차장 바닥 보수 공사 안내
|
|
3
|
+
subtitle: 2026년 11월 공사 기간의 구역별 통제와 대체 주차
|
|
4
|
+
author: 예시 공사 시설관리팀
|
|
5
|
+
organization: 예시 공사
|
|
6
|
+
date: 2026-10-27
|
|
7
|
+
short_title: 지하 주차장 보수 공사 안내
|
|
8
|
+
notice: "예시 안내문: 일정과 구역 이름은 모두 가정입니다"
|
|
9
|
+
tonality: Memo
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
::: cover variant=masthead kicker="안내"
|
|
13
|
+
받는 사람: 본관 근무 전 직원 · 보내는 사람: 시설관리팀 · 제목: 11월 지하 주차장 바닥 보수와 구역별 주차 통제
|
|
14
|
+
:::
|
|
15
|
+
|
|
16
|
+
# 공사 개요
|
|
17
|
+
|
|
18
|
+
시설관리팀은 11월 3일부터 28일까지 본관 지하 주차장의 바닥 방수층과 도장을 새로 한다. 공사는 네 구역으로 나누어 진행한다. 한 번에 한 구역만 막지만, 많게는 주차면 420면 가운데 140면을 쓸 수 없어 출근 차량이 몰리는 오전 9시 전후에는 빈자리를 찾기 어려울 수 있다(예시). 공사 기간에는 별관 지상 주차장 90면을 열어 둔다.
|
|
19
|
+
|
|
20
|
+
# 구역별 통제 일정
|
|
21
|
+
|
|
22
|
+
표 1. 구역별 통제 기간과 주차면 (2026년 11월, 예시)
|
|
23
|
+
|
|
24
|
+
| 구역 | 통제 기간 | 통제 주차면 (면) | 대체 이용 |
|
|
25
|
+
| --- | --- | ---: | --- |
|
|
26
|
+
| 지하 2층 동측 | 11월 3일-9일 | 140 | 별관 지상 주차장 |
|
|
27
|
+
| 지하 2층 서측 | 11월 10일-16일 | 120 | 별관 지상 주차장 |
|
|
28
|
+
| 지하 1층 동측 | 11월 17일-23일 | 90 | 지하 2층 전 구역 |
|
|
29
|
+
| 지하 1층 서측 | 11월 24일-28일 | 70 | 지하 2층 전 구역 |
|
|
30
|
+
|
|
31
|
+
자료: 시설관리팀 공사 계획서(2026년 10월 확정)
|
|
32
|
+
|
|
33
|
+
# 직원 협조 사항
|
|
34
|
+
|
|
35
|
+
통제 구역의 차량은 전날 22시까지 옮긴다. 남은 차량은 별관 주차장으로 견인되며 비용이 청구될 수 있다. 장기 출장이나 휴가로 차를 세워 둔 채 자리를 비우는 사람은 출발 전에 시설관리팀에 차량 번호와 돌아오는 날짜를 알려 주면, 팀이 통제 일정에 맞추어 차를 옮길 자리를 미리 마련해 준다.
|
|
36
|
+
|
|
37
|
+
문의는 시설관리팀 내선 2240으로 한다.
|