Orbit Logic's Collection Feasibility Tool provides scalable web-based single or multi-satellite feasibility determination with an integrated Google Map and configurable feasibility formula and configurable spacecraft parameters. This tool can be used for analysis, collection planning, disaster management feasibility, constellation planning and more. Feasibility is determined based on a defined AOI and associated collection parameters and constraints defined by the user. The function computes the number of required strips and total scan time based on required imaging mode. Constrained collection opportunities are computed based on order geographic location and the orbital model for the duration of the ephemeris to determine revisit frequency and average access duration. Order priority, statistical cloud cover and competition from other orders in the area of the AOI are taken into account to determine both minimum and maximum expected time to collect.
The function also allows for "tuning" by configurable weightings for each competition factor as well as a general "operational" factor, and allows an authorized user to adjust the aggressiveness of the reported collection time by a configurable "slider" between minimum and maximum computed times.
Please feel free to try our Collection Feasibility Tool yourself: CFT Demo Server ». Login is: public. Password is: orbitlogic. CFT is currently available for Internet Explorer 7+, Safari, Opera, Firefox browsers - and can now also be accessed on an iPad/iPhone. On Internet Explorer when the screen comes up asking about displaying nonsecure items, you will need to click "no". There are no security issues, but it is a required step. Please read the help file for best performance tuning.
A sample snapshot of a sample the Collection Feasibility Tool main screen:
A snapshot of a sample test in Florida with the Collection Feasibility Tool:
Multisource
Orbit Logic has previously implemented multi-satellite feasibility computations for other customers. We have applied this previous experience and implemented single and multi-satellite feasibility into the online tool available today. Multi-satellite feasibility assumes that collaborative collection of the AOI by all selected satellites is acceptable (i.e. that portions of the AOI may be collected by different satellites to complete the collection).
Order Information
Orbit Logic's feasibility function incorporates competition from nearby orders (distance from AOI is configurable) that exist in the Feasibility tool database. The Feasibility Tool database is updated "live" through a web services interface to listen for and ingest new and modified orders. Orbit Logic's existing feasibility function already accounts for priority when determining feasibility. The basic approach is to only consider orders of equal or higher priority as competition in the area of the AOI. The supported priority range is 1-100 (with 100 considered the most important).
Input Data
For each feasibility request the user specifies the AOI (by clicking on the map) and standard collection constraints including view angles, GSD, collection window, etc. The user may also apply external kml , shapefiles and stk area target files to assist in defining the AOI.
Reporting Functions
Feasibility reports may displayed on web page, printed, or saved as text files. Reports are requested by the user through a Report menu interface on the web page. Orbit Logic's solution also provides a feasibility summary report overlaid on the Map window for any feasibility request. This will allow the operator to quickly see basic feasibility information and make proposed order adjustments as required to bring in the feasibility. Our internal testing has proved this to be a very popular and useful feature. In addition to report generation, the user may generate a New Order XML file for import into Orbit Logic's CPM/CPAW systems . . . so getting the feasibility order tasked is a quick and easy process.
Architecture
The Enterprise Collection Feasibility Tool is implemented as a web application with client/server architecture to support many simultaneous clients. Google Maps is integrated into the Feasibility Tool web page to provide a comprehensive set of map tools to assist the operator with defining AOIs. The Collection Feasibility Tool is hosted on a single multi-processor server hardware platform that supports both the web server and related application server.
Performance
The architecture supports multiple simultaneous clients and feasibility requests. Current feasibility function response with the Collection Feasibility Tool runs about 5 seconds per request.
Visualization
The Collection Feasibility Tool utilizes Google Maps Professional. The pricing depends on the operational needs, and number of users taking the site. More detail can be provided by Orbit Logic.
Click on the GSA Advantage logo below to purchase a license of this software through your GSA account, or contact Orbit Logic directly for non-GSA purchases at sales@orbitlogic.com
