Pagpapanatili at Suporta sa IT
Hosting, Pagpapanatili, at Teknikal na Suporta
Suriin muna ang mga responsibilidad na kasama sa unang taon. Pagkatapos, pumili ng hiwalay na quote para sa taunang hosting at basic maintenance o opsiyonal na buwanang technical support.
Halimbawang saklaw sa Ingles
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.Ihambing ang mga opsyon
Ano ang matatanggap mo
- 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.
Ano ang ihahanda
- Application/version, repository rights, host owner and dependency inventory.
- Backup/recovery evidence, known incidents and critical operating hours.
- Authorized requesters, approver and update recipient.
Hiwalay na pagkakasunduan
- 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.
Tingnan ang halimbawa
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.
Aming Mga Serbisyo ng Suporta
Panatilihin ang mga sistema at gawaing nakasaad sa kasunduan.
Nakakatulong ang mga awtomatikong pagsusuri na matukoy ang mga isyu sa availability. Ang pagsubaybay ay hindi nagpapahiwatig ng 24/7 na pagtugon sa insidente ng tao.
Ilapat ang security maintenance na napagkasunduan para sa application at hosting plan. Itinatakda ng kasunduan ang mga responsibilidad, exclusions, at update scope.
Kailangan ng napagkasunduang saklaw at available engineering hours para sa performance diagnosis at tuning. Hindi awtomatikong kasama sa basic maintenance ang patuloy na optimization.
Proseso ng Onboarding
Paano namin kinukuha at pinapatatag ang iyong mga system
Pagsusuri ng Sistema
Kumpirmahin ang source at data access, dependencies, operating responsibilities, at hiwalay na assessment scope bago ang takeover.
- Ulat ng Pagsusuri
Pagpapatatag ng Sistema
I-estimate at aprubahan ang stabilization work bago implementation. Hindi ito awtomatikong kasama sa hosting o ongoing support.
- Batayan ng Katatagan
Patuloy na Pamamahala
Isagawa ang monitoring, scheduled maintenance, at reporting na tahasang kasama sa kasunduan.
- Napagkasunduang maintenance records at ulat
Mga Plano ng Suporta
Malinaw na tinukoy ng mga opsyonal na plano ang saklaw ng serbisyo, kasama ang mga oras ng engineering at mga gastos ng third-party.
Taunang Hosting at Basic Maintenance
Pinakamahusay para sa: Taunang hosting at basic maintenance
Maaaring bilhin nang hiwalay ang napagkasunduang server, backup, monitoring, at security maintenance. Nakabatay ang presyo sa aktuwal na saklaw.
Ang Kalamangan
Malinaw na responsibilidad, exclusions, at dagdag na gastos
- Napagkasunduang backup frequency, retention, lokasyon, at recovery checks
- Nakatala ang hosting at maintenance responsibilities
- Hindi subscription para sa engineering hours
Buwanang Teknikal na Suporta
Pinakamahusay para sa: Buwanang technical support
Hanggang 4 oras/buwan, hindi kasama ang server fees. Binibilang ang aktuwal na komunikasyon, konsultasyon, diagnosis, implementation, checks, at deployment. Hindi naiipon ang hindi nagamit na buwanang oras.
Ang Kalamangan
Malinaw na responsibilidad, exclusions, at dagdag na gastos
- Nakasulat na estimate at pag-apruba ng pagbabago
- Napagkasunduang coverage at escalation
- Hindi ibinabawas sa paid hours ang warranty defects na responsibilidad namin
Dagdag na Teknikal na Trabaho
Pinakamahusay para sa: Dagdag na technical work
Fixed quote ang malinaw na saklaw. Ginagamit ang hourly rate sa maliliit na gawaing hindi pa tiyak matapos ang estimate at nakasulat na pag-apruba. Walang prepaid 10-hour package para sa bagong quotes.
Ang Kalamangan
Malinaw na responsibilidad, exclusions, at dagdag na gastos
- Napagkasunduang estimate at iskedyul
- Walang dagdag na trabahong hindi inaprubahan
- Ipinapahayag ang third-party costs
Espesyal na Coverage
Pinakamahusay para sa: Espesyal na coverage
Kailangan ng hiwalay na saklaw at kumpirmadong kapasidad para sa out-of-hours coverage o espesyal na operating responsibilities. Hindi ipinapangako ang agarang staffing.
Ang Kalamangan
Malinaw na responsibilidad, exclusions, at dagdag na gastos
- Itinalagang coverage at escalation responsibilities
- Ebidensiya para sa recovery targets
- Walang default na 24/7 o uptime commitment
Higit pa sa Basic na Suporta
Kailangan ng napagkasunduang saklaw at kapasidad para sa dagdag na payo at engineering.
Patuloy na Pagpapabuti
Regular na mga rekomendasyon para sa mga pagpapabuti ng system.
Pagpaplano ng Paglaki
Paghahanda ng inyong infrastructure para sa susunod na paglaki.