英語のスコープ例
Agree who responds, approves and operates the system
You need bounded help with an application that has a named owner, known access and a clear support scope.
Use a modernization project for a significant replacement or migration. A support allowance is not an unlimited feature-development subscription.選択肢を比較する
受け取る成果物
- Application/access inventory and a responsibility record.
- Request classification, diagnosis and approval before chargeable changes.
- Agreed work/time record, checked release outcome and remaining risks.
準備するもの
- Application/version, repository rights, host owner and dependency inventory.
- Backup/recovery evidence, known incidents and critical operating hours.
- Authorized requesters, approver and update recipient.
別途合意する事項
- An initial response acknowledges or starts diagnosis. It is not a guaranteed resolution time.
- Out-of-hours coverage and severity commitments require explicit agreement.
- New features, vendor outages and work beyond the approved allowance follow their own approval decision.
サンプルを見る
Illustrative request record: reported issue → priority and coverage check → diagnosis → estimate/approval → implement/check/deploy → time used and outcome. Classify a warranty defect, a maintenance task, a new feature and a vendor incident separately.
Acceptance example. The approver sees the scope and any charge before extra work. The final record states what changed, what was checked, approved time used and unresolved risks. The operating owner retains responsibility for vendor accounts and bills unless agreed otherwise.
Read the sample scope, acceptance and handover recordsAre backups and hosting included?
Only the accepted plan defines hosting, backup frequency, recovery checks and ownership. A technical allowance does not imply universal operating coverage.
What if the allowance is exhausted?
Agree the next priority and approve additional work before it starts. Response, diagnosis, implementation and vendor recovery are different steps.
Four different kinds of post-launch help
| Concept | Purpose | Example and boundary |
|---|---|---|
| First-year basic maintenance | The basic-care tasks and term listed in the accepted project scope. | An agreed maintenance task is different from adding another approval screen. Hosting, backups and renewals need named owners. |
| Annual consultation allowance | 4 hours of first-year consultation where those project terms apply. | Discussing a workflow change does not include implementing it. Confirm the term, availability and work classification. |
| Scoped defect warranty | 90-day warranty under the applicable accepted project terms. | A failure against an agreed acceptance rule differs from a new requirement or vendor outage. Coverage depends on the warranty terms. |
| Optional monthly technical allowance | 4 approved technical hours per month under that plan. | Agreed fixes or changes consume recorded time. Extra work needs approval. Unused hours do not imply unlimited work or rollover. |
These project-care concepts do not replace the separate product rules for Luma or ResumeForU. Confirm plan applicability, initial response coverage, renewal, exclusions and request authorization in writing. A response begins communication or diagnosis, not a promise of immediate resolution.
Care, editing and operating responsibilities
| Task | Buyer responsibility | Scope to confirm |
|---|---|---|
| Hosting and vendor bills | Name the account and payment owner. | First-year term, renewal owner and any annual hosting/basic-maintenance coverage. |
| Backups and recovery | Approve recovery needs and access. | Backup owner, retention, restore checks and recovery work explicitly covered. |
| Patches and monitoring | Identify critical operating constraints. | Systems covered, update approval and monitoring/incident contact. |
| Content edits | Supply approved copy/images and nominate an editor. | Staff editing versus agreed care tasks or separately approved work. |
| Defects and new features | Describe expected behavior and approve changes. | Warranty classification versus technical allowance or an additional quote. |
| Reporting and exit | Keep authorized contacts and account ownership current. | Work/time record, remaining risks, access, exports, licences and cancellation/renewal terms. |
First-year care, annual basic maintenance and a monthly technical allowance are different scopes. This checklist does not add coverage to a plan. Record included work and extra-work approval in writing.
保守で対応する作業
契約に記載したシステムと作業を対象にします。
自動確認で稼働状況の問題を検知します。自動監視は24時間の有人障害対応を意味しません。
アプリケーションとホスティングに対して合意した保守を行います。責任、対象外、更新範囲を契約に明記します。
性能調査と調整は範囲と作業時間を合意して進めます。継続的な最適化がすべての基本保守に含まれるわけではありません。
保守の開始手順
引き継ぎと安定化の内容を順に確認します。
システムの確認
ソースとデータへのアクセス、依存関係、運用責任、別途範囲を定めた調査を確認してから引き継ぎます。
- 調査報告書
安定化作業
必要な安定化を見積もり、承認後に実施します。ホスティングや継続支援に自動的に含まれる作業ではありません。
- 安定性を確認する基準
継続管理
契約に含む監視、予定した保守、報告を行います。
- 合意した保守記録と報告
保守と技術支援のプラン
含まれる作業、時間枠、外部費用を確認します。
年間ホスティングと基本保守
対象: 年間のホスティングと基本保守が必要な企業
サーバー、バックアップ、監視、セキュリティ保守を合意して単独契約できます。料金は実際の範囲で確定し、一律の料金表ではありません。
主な特徴
責任、対象外、追加費用を明確に
- バックアップの頻度、保存期間、場所、復旧確認を合意
- ホスティングと保守の責任を記録
- 開発時間の定額契約ではありません
月額技術支援
対象: 月単位の技術作業が必要な企業
月最大4時間で、サーバー費用は別途です。連絡、相談、調査、実装、確認、公開の実時間を計上します。未使用時間は繰り越せません。
主な特徴
責任、対象外、追加費用を明確に
- 書面での見積もりと変更承認
- 対応範囲と上位担当への連絡を合意
- Nodesifyの責任となる保証対象修正は有料時間を使用しません
追加の技術作業
対象: 契約外の追加作業
明確な範囲は固定見積もりです。小規模で不確定な作業は見積もりと書面承認後に時間単価を適用します。新規見積もりでは10時間の前払いパックは提供しません。
主な特徴
責任、対象外、追加費用を明確に
- 見積もりと日程を合意
- 未承認の追加作業は行いません
- 外部費用を明記
個別の対応体制
対象: 特別な運用責任や時間帯が必要な企業
時間外対応や特別な運用責任は別の範囲と実際の担当体制を確認します。即時に人員を確保できるとは約束しません。
主な特徴
責任、対象外、追加費用を明確に
- 対応担当者と連絡責任を指定
- 復旧目標には根拠が必要
- 標準の24時間対応や稼働率の約束はありません
必要に応じた追加の改善
追加の助言と開発は範囲と担当体制を合意します。
継続的な改善
調査結果に基づく改善の提案と実装を個別に合意します。
利用拡大への計画
想定業務量に応じてインフラの変更と費用を検討します。