Answer: The exact times saving will vary from job to job but most jobs should experience at least a 75% reduction in times to build the completed OpenTrack infrastructure model. For example a model that might take 4 days to build in OpenTrack using IVT format file loading combined with manual working can potentially be built in one day using CLIP.
There are things which CLIP can't do such as contact clients and get them to send you all the correct source files or read signal graphical diagrams to determine signal position. Compiling a list of signal names, description and locations from a drawing will still take time for example.
If you start a project with your data already in an easily readable electronic format such as Microsoft Excel then your modelling task with CLIP will be quicker than if you have to manually convert drawings and diagrams into electronic format. However once you've got all your data in electronic format CLIP enables you to quickly turn it into an OpenTrack infrastructure model.
2. CLIP requires at least 11 separate input files. Doesn't it take a lot of time to build so many files? How can a requirement to load so many files result in quick model building?
Answer: Whatever method you use to build an OpenTrack document you will usually start with your data in several separate files anyway. For example your track curvature, gradient, track speed limits and signal description and location as well as station location information will usually start life each in their own separate file or table.
So CLIPs multiple input files actually saves time because you leave the data in its original separate tables (with minor modification to CLIP's simple format). Using CLIP means you don't have to do any further processing to combine the data into one file as you would for example in IVT format loading into OpenTrack. CLIP takes care of the data combining for you.
3. How much does CLIP cost?
Answer: CLIP costs can be found by contacting Plateway on Phone number: +61 (0)2 9637 5830 or Email: firstname.lastname@example.org
4. How much training does it take to learn how to use CLIP>
Answer: CLIPs input file format is pretty simple and can be learned quickly without official training. In our experience a customer who is already familiar with OpenTrack model building can simply take the CLIP manual and CLIP example data files and be building large infrastructure models within a day, typically with just a couple hours of Skype or Link discussion over the internet to answer questions.
Plateway are based in Sydney Australia and are happy to provide face to face CLIP instruction to anyone willing to pay the costs of getting a trainer into face to face contact with them. While face to face meeting is the best and quickest way to learn CLIP it really is so simple that one should be able to learn it with just some example CLIP files to work from and a manual and maybe a few emails/phone conversations to answer questions.
Ongoing CLIP support is free to users who already have an up to date OpenTrack support agreement with Plateway. For new users who didn't purchase their OpenTrack through Plateway and so don't have a Plateway OpenTrack support agreement we are happy to provide initial training as necessary over the internet to learn how to build a CLIP model as part of the purchase price of the CLIP license.
5. Can I take an existing OpenTrack model that wasn't built with CLIP and convert it into CLIP format?
Answer: At present the answer to this is no but it is a possibility for future CLIP development.
6. Who can I contact at Plateway to find out more about CLIP?
Answer: To find out more about CLIP contact Plateway on Phone: +61 (0)2 9637 5830 or Email: email@example.com
7. Can I be sent an example of CLIP input files?
Answer: Yes Plateway is happy to send you an example of CLIP input files. To do this contact Plateway on Phone: +61 (0)2 9637 5830 or Email: firstname.lastname@example.org
8. Are CLIP built infrastructure models compatible with OpenPowerNet?
Answer: Yes CLIP built OpenTrack infrastructure models are specifically designed to be compatible with OpenPowerNet and have been used by clients in conjunction with OpenPowerNet.