Welcome Login

For current information from GSA about COVID19 please click HERE

You are here

New Draft Section C

Hello ASTRO Community!

As we go through questions, recommendations, and document submissions, we begin to realize where further clarifications are necessary and where it makes sense to make edits to the draft solicitation documents. 

One such area is the requirement for any project submitted in any Pool of ASTRO to be platform related.  We are seeing many examples of keyword searches that forego being within the context of a Pool or Domain definition.  The following questions and answers elaborate more on this:

Q:  We believe that the example we submitted meets some of the functional factors across some of the Pools but fear that it does not meet the first gate of being “platform” related, so therefore it is not a compliant Relevant Experience Project.  In other words, must a project pass the first gate of being platform related before any functional factors or other scoring elements are considered?

 

Response:  That is correct.  EVERYTHING on ASTRO is platform related.  This is written into every Pool definition and scope domain.  We see a lot of submission examples of companies performing keyword searches that match an example in Section C or Functional Factors without any context of the associated definitions.  We will be providing definitions for Functional Factors as well in a coming update.

 

Q:  What is the definition of a platform?

 

Response:  Platform:  a vehicle (such as a satellite, tank, ship, or aircraft) used for a particular purpose or to carry equipment or personnel.  

 

In order to clarify this, we have removed the word “system” from the Domain/Sub-Domain definitions as well as the Functional definitions of the Pools as it seemed to be confusing people.  The following is an example of the new language (located in many places) in the draft solicitation (all changes to Section C done thus far are included in the attachment to this blog):

FROM: 

2.2.1.1.            OPERATIONS DOMAIN

2.2.1.1.1         SUB DOMAIN:  DATA OPERATIONS

Definition: Data Operations includes all data collection, processing, exploitation, and dissemination activities associated with manned, unmanned, and optionally manned systems, robotics, and platforms supporting mission performance.

TO:

2.2.1.1.            OPERATIONS DOMAIN

2.2.1.1.1         SUB DOMAIN:  DATA OPERATIONS

Definition: Data Operations includes the performance of data collection, processing, exploitation, and dissemination activities associated with manned, unmanned, and optionally manned platforms and robotics supporting mission performance.

C.2.2.1.1.1. Definition: Data Operations includes the performance of data collection, processing, exploitation, and dissemination activities associated with manned, unmanned, and optionally manned platforms and robotics supporting mission performance.

***Speaking of OPERATIONS!  Please understand that to qualify for the Data Operations or Mission Operations Pools, your Relevant Experience Project documentation needs to demonstrate that your company is performing the operational activity… not supporting the Government in performing the activity; not supporting the system the Government uses to perform the activity; but that your company is actually performing the activity.  Support activities belong in the Support Pool.  Development or Integration of the platform systems being used for Operations belongs in the Development/Systems Integration Pool.  The Data Operations or Mission Operations Pools are for projects where the contractor is performing operational activities on behalf of the Government.

Good Examples of Data Operations Projects:

1.   Contractor is to provide a turn-key Contractor Owned Contractor Operated (COCO) aerial intelligence system, including commercial airplanes, commercial cameras and software, datalink connectivity, pilots, and operators of the aircraft and Processing Exploitation and Dissemination (PED) processing for DoD missions.

2.   Contractor shall perform data analytics in real time on video information coming from an unmanned platform.

3.     Contractor shall perform data dissemination to and from all platforms as necessary to conduct anti-narcotic trafficking.

4.  Contractor pilots unmanned aerial vehicles to provide 3D rendering and forensics of a crime scene investigation.

Non-Qualifying Examples of Data Operations Projects:

1.     Contractor will provide test and evaluation of ISR sensors and platforms.

2.     Contractor is to provide aircraft that the Government will use for ISR operations.

3.     Contractor will provide ISR software updates.

4.  Contractor provides support for but does not actually perform data collection, processing, exploitation, and dissemination activities associated with manned, unmanned, and optionally manned platforms and robotics supporting mission performance.

That’s it for this blog.  Stay tuned for a series of blogs here on Interact providing updates to the draft solicitation; scoring; questions and answers; and a host of other things!

Please have a great ASTRO Day!!!

Todd and Team

941
Upload
Files: 
Attachment TitleSizeType
File ASTRO Draft Section C May 15.docx31.41 KBDOCX
Share

Views: 122

Comments

liz.tribelli
Thank you for distributing the updated draft Section C. On a related front, with respect to teaming, if a contractor decides to submit a bid to Prime a Pool, can you please confirm that it is acceptable to also sub to other companies that may be bidding in the same Pool?
Will Fortier
We are starting to encourage companies with questions regarding ASTRO to ask them via astro@gsa.gov.
Welcome to the ASTRO/ATLAS Program's Outreach Community; a forum to connect industry partners and the federal acquisition community to discuss an... More
  • edward.hughes's picture
    edward.hughes
  • kharford@potomacwave.com's picture
    kharford@potoma...
  • Jdcash01's picture
    Jdcash01