Project, contract and cost

No term matches your search.

Project, contract and costCloud (SaaS) deployment

Running the software on the vendor's infrastructure under a subscription. Updates sit with the vendor; data location and outage plans must be agreed with the customer.

See also: On-premise deployment, Data residency

Detailed guide →

Project, contract and costConfiguration

Adapting the product to processes through settings, without code changes. Preferred over customisation because it survives upgrades.

See also: Customisation

Project, contract and costCustomisation

Changing the standard product at code level. It fits the process exactly but raises upgrade cost and lock-in.

See also: Configuration, Scope creep

Project, contract and costDemo script

A demonstration where the vendor runs your process step by step with your data. Asking for a script instead of a canned demo exposes real capability gaps.

See also: RFP (request for proposal), UAT (user acceptance testing)

Detailed guide →

Project, contract and costGo-live

Starting to use the system in real operations. Stock cutover, parallel running and a rollback plan must be written beforehand.

See also: UAT (user acceptance testing), Stock cutover

Detailed guide →

Project, contract and costLicence model

What the fee is based on: user, concurrent user, device, site, order volume or transaction. The model decides how cost grows as you grow.

See also: TCO (total cost of ownership)

Detailed guide →

Project, contract and costOn-premise deployment

Running the software on the organisation's own servers. Control increases, and so does responsibility for updates, backup and continuity.

See also: Cloud (SaaS) deployment

Detailed guide →

Project, contract and costReference call

A call with the vendor's existing customer, ideally on a deployment similar to yours. Without written questions it turns into a sales pitch.

See also: RFP (request for proposal)

Detailed guide →

Project, contract and costRFP (request for proposal)

A document stating requirements and evaluation criteria, asking vendors for structured proposals. A precondition for comparable quotes.

See also: Demo script, Reference call

Detailed guide →

Project, contract and costROI and payback period

How long the savings take to cover the investment. Inputs must be measurable; a savings claim based on assumption cannot be verified.

See also: TCO (total cost of ownership), Warehouse KPIs

Detailed guide →

Project, contract and costScope creep

Requirements expanding beyond the written scope during a project. The most frequent cause of schedule and cost overrun.

See also: RFP (request for proposal), UAT (user acceptance testing)

Detailed guide →

Project, contract and costSLA (service level agreement)

Committed support response, resolution time and availability. Without a stated measurement method and exceptions it cannot be enforced.

See also: Source code escrow, Support and maintenance

Project, contract and costSource code escrow

An agreement that releases source code to the customer through a third party if the vendor ceases operations. Raised in critical on-premise deployments.

See also: SLA (service level agreement), On-premise deployment

Project, contract and costStock cutover

Counting stock in the old system and loading it into the new one by location. In most projects it is the riskiest weekend.

See also: Go-live, Full (physical) count

Project, contract and costSupport and maintenance

Defining bug fixing, version upgrades and consulting scope in the contract. Annual maintenance is a permanent line in TCO.

See also: SLA (service level agreement), TCO (total cost of ownership)

Project, contract and costTCO (total cost of ownership)

The sum of licence or subscription, implementation, integration, hardware, training, support and internal effort over a period. Comparing quotes on licence price alone is misleading.

See also: Licence model, ROI and payback period

Detailed guide →

Project, contract and costUAT (user acceptance testing)

Testing processes with real users and real data before go-live. Without written acceptance criteria, testing never ends.

See also: Demo script, Go-live