英文範圍示例
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.
我們的支援服務
選擇系統所需的監控、維護和技術協助。
自動檢查有助於發現服務可用性問題。監控不代表提供全天候人工事件回應。
更新服務範圍內的應用程式和託管組件。計劃會列明包含的安全維護、負責處理的系統及排除項目。
我們事先約定效能診斷和調校的範圍及工程工時。基礎維護不自動包含持續優化。
服務接管流程
我們評估系統，約定所需的穩定性改善工作，並明確持續服務責任。
系統審計
評估原始碼和數據存取權限、系統依賴及營運責任。接管支援前，我們另行約定評估範圍。
- 審計報告
改善系統穩定性
實施前，我們估算穩定性改善工作並取得您的批准。這類工作不自動包含在託管或持續支援服務中。
- 穩定性基準
持續管理
我們執行支援計劃內的監控、定期維護和報告工作。
- 約定的維護記錄與報告
支援計劃
選擇託管維護、每月技術工時或另行報價的工作。每項計劃均明確服務範圍和第三方費用。
年度託管與基礎維護
適合對象: 需要託管與基礎維護的企業
託管與基礎維護可以單獨購買。我們根據系統所需的伺服器、備份、監控和安全維護報價。
Nodesify 服務特點
清楚列明責任、排除項目和額外費用
- 約定備份頻率、保留期限、位置及復原檢查
- 記錄託管與維護責任
- 不屬於工程工時訂閱
每月技術支援
適合對象: 需要每月技術工時的企業
每月包含最多 4 小時。伺服器費用另計。溝通、諮詢、診斷、實施、檢查和部署均計入工時。未使用的工時每月到期，不累積。
Nodesify 服務特點
清楚列明責任、排除項目和額外費用
- 書面估價與變更批准
- 約定支援範圍和升級處理流程
- 保養範圍內的缺陷修復不佔付費支援工時
額外技術工作
適合對象: 範圍明確的項目或範圍尚不確定的小型任務
範圍明確的工作採用固定報價。範圍尚不確定的小型任務，我們先提供估價並取得書面批准，再按公布的時薪計費。此服務按獲批工作收費，不提供預付工時套餐。
Nodesify 服務特點
清楚列明責任、排除項目和額外費用
- 約定估價和時間安排
- 未經批准不增加工作
- 披露第三方費用
特別服務安排
適合對象: 非工作時間或特殊營運需求
非工作時間服務及特殊營運責任需另行約定。服務開始前，必須確認人員安排和可用時間。
Nodesify 服務特點
清楚列明責任、排除項目和額外費用
- 指定服務範圍與升級處理責任
- 依據驗證結果確認復原目標
- 不提供統一的全天候回應或可用率承諾
基礎支援以外的服務
透過另行約定範圍的諮詢和工程服務，規劃系統改善及未來容量。
持續改善
定期提供系統改善建議。
擴展能力規劃
為未來業務增長規劃基礎設施。