|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Our customers can freely switch between the delivery models when and if their
business conditions change. Earned credits can be applied to offset the costs.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
QuestaWeb offers all three models for delivery of TradeMasterQW solutions.
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
Global trade applications that
automate import and export processes and require collaboration of multiple supply
chain partners located anywhere in the world naturally benefit from Internet-based
systems.
All Web-native systems are hosted. The hosting is defined as an ability of
the user to access software over the Internet using only an
Internet Browser. There are three ways to host an application:
|
|
|
|
|
|
|
|
|
|
|
|
|
In-House Hosting
|
|
|
|
A licensed model. A customer buys software licenses and maintenance from the
application vendor and deploys it on its own premises. In this arrangement,
the customer owns the system and all supporting hardware, software and databases.
|
|
|
|
Vendor Hosting
|
|
|
|
Sometimes called a SaaS (Software as a Service) or an ASP (Application Service Provider) model. In this arrangement,
the vendor is responsible for the maintenance of the application and any supporting
hardware and software. Customers are responsible for the installation and maintenance
of communication access (personal computers, routers, high speed Internet lines, etc.)
and application services, typically per transaction. The real shortcoming of this
model lays in the promotion and adoption of counter-productive business practices
to avoid transaction fees (accumulate paperwork to avoid corrections, limit EDI
messages, use of a single invoice that cover multiple entities, manual consolidation
of information to reduce data entry, etc.).
|
|
|
|
Hybrid Hosting
|
|
|
|
This model combines a vendor hosting with a licensed model. A customer hosts the
most sensitive parts of an application that require access to complex transactions
and private data (such as commercial invoices, purchase orders, customs entries,
manifests, etc.) and allows the vendor to host those parts of an application that
need a minimum of integration efforts, fill in smaller gaps in in-house legacy
applications, or access only public information such as HTS Classifier, Denied
Party Screening, Export Licensing, etc.
|
|
|
|
|
|
|
|
Pros and Cons (next page)...
|
|
|
|
|
|
|
|
|
|
|
|
|
