PWS_Attachment_13_-_EFDS_Project_Summary_26Aug2013.pdf
PDF 20 KB Posted
- Attached to
- GEOSPATIAL SERVICES Federal contract opportunity
- Solicitation number
- FA2517-17-Q-5051
About this file
PWS Attachment 13
View the file
Other files for this federal contract opportunity
Show all 16
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Summary of Deliverables Developed for GSA Contract FA8903-12-F-0126 Subtask:
“Environmental Functional Data Set (EFDS) Support”
26 August 2013
The following deliverables were developed to document Booz Allen Hamilton’s EFDS data review, applicability analysis, searches for available data, summaries of data gaps, and actions completed in updating and/or completing map layers for Cape Cod Air Force Station (AFS), Cavalier AFS, Clear AFS, and Thule Air Base (AB) GeoBase EFDS. The folder for each installation contains two sub-folders and one EFDS spreadsheet. The first sub-folder is labeled with the site name and documents (e.g.
CapeCod_AFS_Documents). The second sub-folder is labeled with the site name and GIS (e.g.
CapeCod_GIS_Data). The corresponding EFDS spreadsheet is named [Installation Name]_ EFDS_ Status_ Spreadsheet_08082013.xlsx. This folder layout is the same for Cavalier AFS, Clear AFS, and Thule AB.
The “Documents” folder contains all the documents provided by the Site to research usable data to create a layer contained in the EFDS spreadsheet. The “GIS Data” folder contains all the GIS references and data utilized to populate layers; as well as the Microsoft Access file recording that data. The EFDS spreadsheets each contain three worksheets. The first worksheet is the legend. The legend worksheet provides the color codes used to differentiate between layers that are not applicable (= not highlighted or ”white” cells); layers that need more information to complete (= yellow highlighted cells); and layers that were able to be completed with data provided from the installation (= green highlighted cells). The “Checklist” worksheet lists all the layers for the EFDS with the corresponding applicable and/or completeness color coding highlights for each layer. The EFDS spreadsheet is also organized by the columns displayed in Figure 1.
Figure 1-Column Headers in EFDS Spreadsheet
The “Entity Type” column is the SDSFIE 2.6 layer name. The “Definition (SDSFIE 2.600)” is the standard definition for that Entity Type. The “Applicable to Installation (Y/N)” column was derived from the gap analysis conducted via site visits and communications with Site Subject Matter Experts (SMEs) to determine if the Entity Type was applicable to the Site. The “Data Acquired & Populated (Y/N)” column denoted if data was obtained from the Site to complete or partially complete the layer. The “Current Status” column displays if the layer is Completed, Incomplete, or N/A (this column also refers to the highlight color legend previously stated). The “Notes” column states how a layer was completed, why it is incomplete, or why it is not applicable to the Site. The “Questions to Be Answered to Help Close Data Gaps” column contains follow-up questions asked by Booz Allen Hamilton to further understand what data or documents exist to complete that layer. The “Response/Direction from Site Manager” column states the response provided to those questions. The “3.0 SDSFIE Crosswalk Feature” column links the SDSFIE 2.6 layer to the new SDSFIE 3.0 standard.
The “Completion Summary” worksheet provides a quick overview of the 72 layers. This worksheet lists the layers completed, layers incomplete, layers that are applicable but data to populate was unavailable or did not exist, and layers that are not applicable. (Note: The stand-alone attributes [“not a feature class”] are not included. When this support effort began standalone tables in SDSFIE 2.6 were relevant.
The new SDSFIE 3.0 standard eliminated all stand-alone tables. However, some information does exist in the checklist worksheet for informational purposes).
For additional information please contact Anthony Brigantic brigantic_anthony@bah.com or Laurie Baker baker_laurie@bah.com
ENTITY TYPE DEFINITION (SDSFIE 2.600)
APPLICABLE TO
INSTALLATION?
(Y/N)
DATA ACQUIRED &
POPULATED? (Y/N)
CURRENT
STATUS NOTES QUESTIONS TO BE ANSWERED TO HELP CLOSE
DATA GAPS RESPONSE/DIRECTION FROM SITE MANAGER 3.0 SD SFIE CROSSWALK FEATURE
mailto:brigantic_anthony@bah.com mailto:baker_laurie@bah.com
File details come from the government source that posted it. Updated .