英文范围示例
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 服务特点
清楚列明责任、排除项和额外费用
- 指定服务范围与升级处理责任
- 依据验证结果确认恢复目标
- 不提供统一的全天候响应或可用率承诺
基础支持以外的服务
通过另行约定范围的咨询和工程服务，规划系统改进及未来容量。
持续改进
定期提供系统改进建议。
扩展能力规划
为未来业务增长规划基础设施。