How to use the list
The list consists of points that have a yes or no answer and a piece of proof: a screenshot, the result of a command or a note in the protocol. A point without proof is not accepted. The IT manager may add their own items that follow from the plant's policy.
We split the acceptance into four areas: the split of work and documentation, the instances, the network and the handover point, and the data and backups. Each area has a responsible person on the client's side and on the vendor's side.
Area 1: split of work and documentation
First we confirm that everyone understands the split. The infrastructure, meaning the machines, the network and the disks, was provided by the client. The vendor deployed the software in Docker containers in two instances.
InnerWeb is a software vendor, not a device manufacturer. The installation does not require our own access control readers or replacing the client's existing system, so we do not look for such elements during the acceptance.
Number of checkpoints in the acceptance areas
Area 2: production and pre-production instances
The acceptance covers both instances. Pre-production is meant to be a twin: the same image versions and the same structural configuration, but different data and address. The IT manager checks the versions and the status of the containers in both places.
It is good practice to run a trial login on pre-production and on production and to record the result. The protocol then contains proof that both paths work.
Area 3: network and the handover point
The network zones should match the pattern: the plant area with BLE transmitters, the users in the plant, the plant LAN and the client's private cloud. Traffic from outside must arrive only through the handover point: the WAF, one published address, the outbound firewall and the end of the IPsec tunnel on the client's side.
The IT manager checks that no other path from outside leads to the server, and records who may switch off the service tunnel.
Area 4: data and backups
Data and backups must be on the client's disks. The protocol records the backup location, the frequency and the date of the trial restore on pre-production. A restore that has not been tried remains an assumption.
It is also worth describing the behaviour after a loss of connectivity: the mobile app queues data offline, and the server accepts the backlogged batches once the app is back online. Monitoring should distinguish such a break from a server failure.
Checklist
Video
Frequently asked questions
Who signs the acceptance protocol?
The person responsible on the client's side, usually the IT manager, and a representative of the software vendor.
Does the acceptance cover pre-production?
Yes. Pre-production is part of the installation and should be accepted in the same way as production.
What if the backup has not been restored yet?
The point stays unaccepted until a trial restore on pre-production has been done.
Do the access control readers have to be accepted?
No. InnerWeb does not supply or replace them, it integrates with the client's existing system.
Let's talk about the installation in your server room
We will present the requirements and the split of responsibilities for your plant based on the installation documentation. Book a conversation with the InnerWeb team.
Let's talk