Closing the demo technically
First close the demo on the system side. Stop it with the stop command and confirm the status. The demo deletes only the markers of its own demo accounts. For a demo longer than two hours, when the cache tunnel has expired, the markers must be deleted by hand, so check the map before leaving the room.
Then make a note of the state of the demo instance, because the next demo may start from it. The demo data is kept for the next scenario, and the database backup from the start remains as the reference state.
- stop the demo with the stop command and confirm the status
- check the map and confirm that no test markers remain
- delete markers by hand if the demo ran longer than two hours and the cache has expired
- note the state of the demo instance and the date of the last backup
Writing down the conclusions
Write down the questions the board asked, the functions it wants to test and the functions it did not need. Note the day, the participants and their roles. These notes are the basis of the pilot decision, so they should be written before the people leave the room, not from memory a week later.
Record the answers that were not given during the meeting. Each open question gets an owner and a date for the answer, so the decision does not wait for an informal reply.
- list the functions the board wants to test in the pilot
- list the functions that did not match the plant procedures
- record the questions without answers, with an owner and a date
- record the participants and their roles
Items after the demo by stage
Preparing the pilot decision
Propose the pilot scope on the basis of the conclusions: one hall or zone, a defined group of users, success indicators set before the start and a decision date. A narrower scope shortens the pilot, which is the saving the demo makes possible.
The pilot decision belongs to the client. The demo shows how the system works on plant data, but the pilot checks it in a real hall, including transmitter placement and watch operation. Present both sides in the decision document, so the board knows what the demo proved and what it did not.
- propose the pilot scope: hall or zone, user group, indicators, decision date
- mark the functions the demo did not cover, for the pilot
- prepare the decision document with what the demo proved and what it did not
Follow-up after the meeting
Send the decision document to the participants within a few working days, while the conversation is still fresh. Attach the list of open questions with owners and dates, so each person knows what they must answer.
Set a date for the next step. A pilot decision without a date tends to stall, and a short follow-up call keeps the scope from growing back after the demo.
- send the decision document to the participants
- attach the open questions with owners and dates
- set the date of the next step
Checklist
Video
Frequently asked questions
Why write down the conclusions on the same day?
Without a written record the board drifts back to a broad pilot scope, and the time saved by the demo is lost.
What if the board does not decide at the demo?
The decision document with the scope and the open questions lets the board decide later on the same basis.
Does the demo instance need to be cleaned up after the meeting?
Stop the demo and clear the markers of the demo accounts. The demo instance itself is kept for the next scenario.
Can the pilot start without a decision document?
We do not recommend it. The decision document records what the demo proved and what the pilot must check.
Agree the pilot scope with us
Send us the conclusions from the demo and we will propose the pilot scope and date. Individual pricing.
Let's talk