Atch_02_-_Database_Design_Requirements.pdf

PDF 40 KB Posted

Attached to
KDAM ATARS Federal contract opportunity
Solicitation number
FA8621-15-R-6328
Issued by
Department of the Air Force Materiel Command Lifecycle Management Center Wright Patterson Air Force Base

About this file

DRAFT RFP DATABASE DESIGN REQUIREMENTS

View the file

Other files for this federal contract opportunity

Other files attached to KDAM ATARS, newest first.
File Type Posted
Atch_03_-_KDAM_ATARS_Section_L.pdf PDF
RFP_FA8621-15-R-6328_Amendment_0002.pdf PDF
Notice_to_Industry_-_RFP_Clarification_11_Aug_15.pdf PDF
RFP_FA8621-15-R-6328_Amendment_0003.pdf PDF
Notice_to_Industry_-_RFP_Clarification_28_Jul_15.pdf PDF
Atch_12_-_Collective_Bargaining_Agreements_and_Wage_Determinations_23_Jul_15.pdf PDF
RFP_FA8621-15-R-6328_20_Jul_15.pdf PDF
Atch_04_-_KDAM_ATARS_Section_M_20_Jul_15.pdf PDF
FA8621-15-R-6328_-_Request_for_Clarification_1.pdf PDF
Atch_05_-_Instructions_to_Offerors_-_Pricing_Matrix.pdf PDF
Atch_04_-_KDAM_ATARS_Section_M.pdf PDF
Atch_21_-_Kirtland_AFB_Opposing_Forces_Operations.pdf PDF
Atch_06_-UH-1N_WST_OFT_HTAWS_TCAD_Concurrency_Modificiation_Statement_of_Objectives.pdf PDF
Request_for_Proposal_FA8621-15-R-6328_14_Jul_15.pdf PDF
Notice_to_Industry_-_Request_for_Clarification_30-jun-15.pdf PDF
KDAM_ATARS_PPI_Tool.pdf PDF
ppi_tool.accdb —
Atch_05_-_Instructions_to_Offerors_-_Pricing_Matrix_v3.pdf PDF
Atch_14_-_ESM_Form.pdf PDF
Atch_01_-_KDAM_ATARS_PWS.pdf PDF
Atch_05_-_KDAM_ATARS_Pricing_Matrix_v3.xlsx XLSX spreadsheet
Atch_16_-_KDAM_ATARS_Cross_Reference_Matrix_v11.xlsx XLSX spreadsheet
Atch_17_-_DD254.pdf PDF
Atch_24_-_CBA_WD_Labor_Hour.pdf PDF
RFP_FA8621-15-R-6328_25_Jun_15.pdf PDF
Atch_15_-_Incentive_Option.pdf PDF
Atch_04_-_Section_M.pdf PDF
Atch_08_-__Syllabus-MESL_List.pdf PDF
Atch_06_-_KDAM_SOO_and_Exhibit_Info.pdf PDF
Atch_02_-_Database_Design_Requirements.pdf PDF
Atch_11_-_Subcontractor-Teaming_Partner_Consent_Letter.pdf PDF
Atch_08_-__Syllabus-MESL_List_v7.pdf PDF
Atch_04_-_Draft_Section_M.pdf PDF
Atch_03_-_Draft_Section_L.pdf PDF
KDAM_ATARS_Follow-Up_QA_12_Jun_15.pdf PDF
KDAM_Updated_DRAFT_L M_Docs_8_May_15.pdf PDF
Atch_03_-_Section_L_DRAFT.pdf PDF
KDAM_ATARS_Industry_Day_v3_FINAL_Shown.pdf PDF
Industry_Day_Notice_-_UPDATE.pdf PDF
Atch_17_-_DD254.pdf PDF
Atch_08_-__Syllabus_List.pdf PDF
Atch_15_-_Incentive_Option.pdf PDF
Atch_06_-_Draft_KDAM_UH-1N_HTAWS-TCAD_SOO_v11_DRAFT_RFP.pdf PDF
Atch_01_-_KDAM_ATARS_PWS_.pdf PDF
Model_Contract_Draft_RFP_6-_Apr-15.pdf PDF
Atch_14_-_KDAM_ATARS_Engineering_Service_Memorandum.pdf PDF
Atch_10_-_Client_Authorization_letter.pdf PDF
PWS_Questions_to_Government.pdf PDF
KDAM_ATARS_SectionM_DRAFT_rev11.pdf PDF
KDAM_ATARS_section_L_DRAFT_rev15.pdf PDF
Show all 50

KDAM ATARS has more files on GovTribe.

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

Section J, Attachment 02 –Draft Database Design Requirements

FA8621-15-R-6328

6-Apr-15, Page 1 of 2

ATTACHMENT 02

DATABASE DESIGN REQUIREMENTS

All work shall include database documentation

1. Geocells

The geocell areas shall be designed to meet the following requirements:

1 geocell =~ 60nm x 60nm area

a. 1.0m textel/pixel resolution imagery or high quality generic imagery where the eye can detect mountains, valleys, ridgelines, and slopes

b. Level I DTED (approx. 90m post)

c. Feature data equal to Joint Operation Graphic (JOG) 1:250k detail

d. Feature data matched only to geocell boundaries

e. Microtexture on all non-high resolution textures

f. Natural vegetation scatter

g. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights.

2. Targets

The target areas shall be designed to meet the following requirements:

1 target = 30nm x 30 nm area around target + 6nm x 6nm area around target

a. 30nm x 30nm square around target

i. .625 textel/pixel resolution imagery or best available within 30nm x 30nm area*

ii. Level II DTED (approx. 30m post) or best available within 30nm x 30nm area*

iii. Feature data equal to Topographic Line Map (TLM) 1:50k detail or best available within 30nm x 30nm area*

b. 6nm x 6nm square around target

i. .3125m textel/pixel resolution imagery or best available within 6nm x 6nm area*

ii. Level III DTED (approx. 10m post) or best available within 6nm x 6nm area*

iii. Feature data equal to TLM 1:24k detail or best available within 6nm x 6nm area*

c. Microtexture on all non-high resolution textures

d. Natural vegetation scatter

e. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights

3. Objectives

The objective areas shall be designed to meet the following requirements:

1 Objective = 6nm x 6nm square around area of interest

a. .3125m textel/pixel resolution imagery or best available within 6nm x 6nm area*

b. Level III DTED (approx. 10m post) or best available within 6nm x 6nm area*

c. Feature data equal to TLM 1:24k detail or best available within 6nm x 6nm area*

d. Microtexture on all non-high resolution textures

e. Natural vegetation scatter

f. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights.

4. Airfields

The airfields shall be designed to meet the following requirements:

Section J, Attachment 02 –Draft Database Design Requirements

FA8621-15-R-6328

6-Apr-15, Page 2 of 2

1 airfield = 30nm x 30nm area + 6nm x 6nm area + actual airfield

a. 30nm x 30nm square around airfield

i. .625 textel/pixel resolution imagery or best available within 30nm x 30nm area*

ii. Level II DTED (approx. 30m post) or best available within 30nm x 30nm area*

iii. Feature data equal to TLM 1:50k detail or best available within 30nm x 30nm area*

b. 6nm x 6nm square around airfield

i. .3125m textel/pixel resolution imagery or best available within 6nm x 6nm area*

ii. Level III DTED (approx. 10m post) or best available within 6nm x 6nm area*

iii. Feature data equal to TLM 1:24k detail or best available within 6nm x 6nm area*

c. Microtexture on all non-high resolution textures

d. Natural vegetation scatter

e. Include lights/illumination glow in built-up areas (i.e. - cities). Must have ability to control multiple levels of lights

f. Include all taxiways, runways, parking ramps, etc. accurate to real-world locations, widths and lengths

g. Include all taxiway and runway markings

h. Include all airfield detail included in real-world approach plates and FLIP data

i. Include geotypical models of the same size and shape appropriate for the airfield buildings. Models must be placed in real-world positions

j. Control tower must be placed in real-world location

k. Include accurate airfield lighting

i. All airfield lighting shall have multiple levels of control and appropriate directionality.

Individual runway lighting shall have separate controls (i.e. approach lights, VASI, PAPI, runway lights, end lights).

l. Beacons and navaids must be placed in real-world positions.

5. Routes

The routes shall be designed to meet the following requirements:

a. Route based on Black Diamond - Kirtland AFB to Pueblo

b. Feature data equal to Joint Operation Graphic (JOG) 1:250k detail

c. Match feature data 5 miles on either side of route

d. Assumes no geospecific imagery

6. Models

a. Low Fidelity Models - 1 to 500 polygons

b. Medium Fidelity Models - 501 to 1300 polygons

c. High Fidelity Models - 1301 to 3000 polygons

7. Radar/CTDB

a. Any change made to the visual database will require an update to both the radar and CTDB databases unless otherwise specified.

*Or best available - sometimes in areas there is not high resolution imagery or map data because it doesn't exist or there is an additional charge to acquire it or create it from a third party vendor.

File details come from the government source that posted it. Updated .