Getting started

This document should walk you through what you would expect when you begin engaging with Leidos for connecting to our Web Services.

Due to program requirements, it is necessary to restrict access to our web services to organizations with a completed product that can be vetted and reviewed prior to granting lab access. If you are a student or hobbyist developer, your request will be rejected.

To request further information, send an email to our Vendor Support Team.
Include in the email:

• Company name
• Contact information for individuals who will attend the initial meeting
• Type of application that will be using the web services
• Approximate implementation date

Once we have had a meeting to discuss our services and whether both parties are a good fit to work together, we will provide access to our development environment.

While waiting for these activities to be completed, you can get started looking at the Web Services documentation here:

• Easy-to-read documentation: https://www.1800wxbrief.com/Website/resources/doc/WebService.xml

Once we have verified with you that your account is set up, you are free to test whatever you want in our testing environment. We will be available to answer questions and troubleshoot any problems that you experience using the web services.

For an application that performs flight plan filing, the following minimum capabilities must be implemented before the application will be authorized by Leidos for deployment in operations:

• Filing VFR flight plans - file, amend, activate, cancel, and close
• Filing IFR flight plans - file, amend, and cancel

Once you are finished with your testing and the system is the way you want, please contact our Vendor Support Team. When we are in this phase, we will require a beta version of your software to test with a large test set to make sure that your user will be getting the expected behavior out of the tool when they make a specific request. (A VFR flight plan is filed as a VFR flight plan on our system, for example) Assuming that this testing is successful, we will schedule the activation of your account in operations and any other configuration changes that are necessary.

If you make subsequent upgrades to your application, we request that we are notified so that we can re-run the testing above. You can do this with a subsequent Request Access to Operations request. If the changes require a change on the operational side on our end we will schedule it. Otherwise we will let you know of any issues we run across.