Timeline for your own instance

While creating an instance of Flying Fleet for you takes only a couple of hours, the process till your members and visitors can use it require a bit of planning. The timeline presented here as example is for a medium size airport. If your instance is just for your own aircraft, all will go much quickly.

1) Initial setup

In this phase Redcrest Solutions GmbH will setup a private virtual machine, setting up test domains and more.

Time required: a couple of hours

2) Setting up the instance for your requirements

Based on the documentation / requirements provided by the customer, Redcrest set the articles, the price, and the base workflows. Some technical setup may require additional knowledge from the customer, like setting up the URL for the instance, or the email settings.

Time required: depends on the requirements, from a couple of hours to a couple of days

3) Import members, movements and more

While this step is optional, it's also a very important step if the customer has existing data to be able to keep as must as possible in the new system.

Time required: depends on the availability of the data, but can be done till the system goes in production.

4) Super admin schooling

Included in the setup package the customer has a given number of work hours, being for the setup and/or the training of the super admins. Ideally the customer super admins shall have the availability to follow the setup, and have access to the required information. The super admins are the only one by default to be trained by Redcrest. This can be discussed and changed in the contract.

Time required: training itself is between 1-4 hours initially, however the super admins must most likely invest about 10-40h before having a big picture of the system.

5) Admin / staff testing

Once the super admins know how to handle the wished workflows, super admins shall train the other admins / staff members. Due to the fact the training is done internally, super admins increase their expertise and know better the required workflows as external people. This is also important in order to reduce the setup costs. After the internal training, an internal testing shall be conducted, to ensure the setup of the initial data is correctly done, and this will also increase the staff knowledge.

Time required: depends of the staff availability, ideally a couple of days or weeks.

6) Member / visitors information

Before the deployment, information about the new software shall be conducted. In the communication the access to the software must be explained. Multiple options are available at this point:

1. Members must register themselves and staffs members will then accept them and give the appropriate roles / memberships.
2. Imported members must recover their password via the password reset link.
3. Imported members get a private email containing their initial password.
4. Imported members all get the same password and they shall change it as soon as possible.

In the communication email / newsletter shall also contain when the new system will be production, but ideally offer at least a couple of weeks of testing, acclimatization to the members. Ideally on the airport infrastructures like hangars doors, C office, or briefing rooms, a poster informing the change shall be placed. Contact Redcrest for an example of such poster.

Time required: ideally should be 1-2 months before, and repeat the communication 1 week before the change.

7) Release to production

Depending on the airport, and the time of year, the first few days before and after the deployment can be more stressing / intensive for all. Redcrest will of course be available by phone to help as quickly as possible, however it is good practice to have skilled (super admins) available on site during the first days.

Time required: most likely a couple of days before, and up to 1 week after the release.