STEP 1: Solution specifications
Initial specifications for WebProof Platinum
- These specifications can also be adjusted continuously, but it is important to clarify what needs to be ready at startup.
- Number of extra (named) users (100 included)
- Number of extra Sharing users (Express users) (10 included)
- Extra storage (20GB included)
- Extra page-flips (1,000,000 included)
- WebFlow Modules
- WebFlow system required specifications:
- Evaluate the customer production volume/type to specify what hardware/software is the best match.
See info about pricing and modules
See info about system requirements
- Quote is created and sent to customer.
STEP 2: Confirmation
- Quote is confirmed, and initial payment is transferred according to the quote.
STEP 3: Preparation
- Setup hardware,install Windows Server, and grant remote access to WebProof (by customer).
- Setup file shares. If InDesign Server is installed, WebFlow needs access to the linked files (by customer).
- Specification of workflows (WebProof statusflows). It is important to have a clear agreement regarding WebProof statusflow and the integration of statuscode triggers to WebFlow (by customer with online meeting assistance from WebProof).
Read more about workflow description and download template here.
- Specificationsfor integration to other systems,e.g., ERP systems, Media Portals, FTP systems (by customer with online meeting assistance from WebProof).
- Specifications for current file structure and for job file and folder naming. To ensure a smooth production workflow, some features require a structured file and folder naming policy (by customer with online meeting assistance from WebProof).
- Fonts: If InDesign Server is installed, the WebFlow Server requires all relevant fonts to be installed. The customer will prepare all fonts in a ZIP file for the first installation and place the file on the server. The customer will be trained on how to upload fonts to server (by customer).
- PDF presets and ICC profiles: If InDesign Server is installed, the relevant presets/profiles need to be installed (customer sends these to WebProof).
- Pitstop preflight: If Pitstop Server is installed, specifications or relevant settings must be installed before it can conduct a preflight or actions (customer sendswith online meeting assistance from WebProof).
STEP 4: Installation
- WebProof installs WebFlow and other specified applications, such as InDesign Server, Pitstop Server, and FTP (remote by WebProof).
- WebProof sets up the WebFlow workflows (remote by WebProof).
- WebProof sets up WebProof according to specified statusflows, statuscodes, roles, notification flows, system settings, and test users (remote by WebProof).
STEP 5: Test
- WebProof tests the setup completely before handing it over to customer (remote by WebProof).
- Customer test: A few users are picked to conduct the test. Their user roles are used for the test in addition to other test users, e.g., clients. The customer tests all the scenarios specified in the workflow, includingall the roles, status codes, and notifications. If included, WebFlow drop folders are checked and the designer checks upload via a plug-in (customer tests on-site andremotely communicates with WebProof).
- Make adjustments until the test is successful.
STEP 6: Training workshop (on-site with customer and WebProof)
- Train relevant users,especially the administrator, project manager, and designer.
- Walkthrough the setup, workflow, administrator support options, WebProof support responsibilities, and online support guides/video guides.
- Make adjustments until the customer is satisfied.