EMPIREPWS2-11-08-5yr.doc

UNCLASSIFIED // FOR OFFICIAL USE ONLY

EMPIRE Sustainment and Enhancements Performance Work Statement

Prepared by

Electronic Warfare Analysis Flight (EWA)

453d Electronic Warfare Squadron (453 EWS)

318th Information Operations Group (318 IOG)

Air Force Information Operations Center (AFIOC)

8th Air Force (8 AF) Air Combat Command (ACC)

Dated: 2/11/2008 EMPIRE Sustainment & Enhancement Performance Work Statement

1. BACKGROUND: The Electromagnetic Propagation Integrated Resource Environment (EMPIRE) is an outgrowth of efforts begun in 1997 by the Naval Information Operations Command (NIOC) & the University of Texas; Applied Research Laboratory (UT-ARL) to provide a consistent, single application programming interface (API) between a number of electromagnetic propagation models, algorithms, & data sources & the Naval Information Operations Center’s (NIOC) “Radio Frequency Mission Planner” (RFMP), a Tactical Decision Aid (TDA), also known as a model, or analytical tool. RFMP is used to study & evaluate the performance of Command, Control Communications Intelligence, Surveillance & Reconnaissance (C3ISR) & Electronic Warfare (EW) systems in real world operational environments. The EMPIRE approach has become so successful that TDAs from the Navy (NRL’s “Interactive Scenario Builder), Air Force (453 EWS’ “Improved Many-on-Many” (IMOM)) & Army, as well as DoD contractors now make use of the software, & there are efforts underway to develop a similar capability for surface acoustic (sound) propagation modeling. After studying the methods, implementations and interfaces of as many as 80 propagation models, it became clear that the expertise required to use them correctly and efficiently should be encapsulated within one software module, with which any portion of RFMP requiring RF propagation information should communicate instead of using the RF models directly. Upon initation of the EMPIRE development effort, NIOC Suitland negotiated with the various “owners” of the original propagation models to gain non-transferable access to their source code. Today, EMPIRE wraps the following EM propagation models:

· The Advanced Propagation Model (APM), the HF Field Strength Model (Damboldt-Lucas), the Standard Propagation Model (also referred to as FFACTR), the Radio Physical Optics (RPO) model, and the Variable Terrain Radio Parabolic Equation (VTRPE) model, from US Navy’s Standard Systems Center (SSC), San Diego.

· The Millimeter Wave Propagation model (MMWPROP), and the Terrain Integrated Rough Earth Model (TIREM, and its hybrids) from the Joint Spectrum Center.

· The Low Frequency/Medium Frequency (LFMF, and its hybrids) model and the Irregular Terrain Model (ITM, aka Longley Rice) from US Department of Commerce’s National Telecommunications Institute/Institute for Telecommunications Sciences (NTIA/ITS).

2. SCOPE/PURPOSE: This work statement describes a multi-year task order-based effort to provide the Department of Defense’s (DOD) EMPIRE user community with services in the areas of basic phenomenology research; hardware & software development; and analysis, modeling & simulation support in the inter-related areas of electromagnetic (EM) propagation, antennas, meteorology & oceanography (MetOc), & geo-environmental sciences.

3. REQUIRMENTS: This section loosely defines the broad categories of support to be provided by the contractor in support of the ongoing efforts of the government to enhance EMPIRE’s capabilities. In all task categories below, exact details of each requirement, to include task specifications, identification of deliverables, CDRLS, performance standards, goals & metrics will be included in each separate task order. The enhancement & sustainment of EMPIRE has generally followed a 2 phase (aka “cycle”) per fiscal year cycle. The first phase normally consists of requirement refinement, basic phenomenology research, initial design & risk reduction activities. In general, this phase usually results in deliverables that are programmatically oriented, allowing the sponsors’ managerial & technical staffs to understand & properly plan for the follow-on development phase. Deliverables generated during the first phase generally include technical reports, software design plans, & software requirements documents, as well as the monthly project progress & financial status reports. The second phase generally consists of continued programmatic support, detailed software development, capability documentation, & release testing & delivery.

a. EMPIRE SUSTAINMENT SUPPORT: Tasks in this category specifically consist of those efforts needed to maintain, sustain and enhance existing capabilities in the EMPIRE software suite. The following list, while not exhaustive, is meant to illustrate categories of individual tasks that could fit task category:

i. TDA Runtime Performance & Interfacing Enhancements: Tasks in this category generally will include, but not be limited to, efforts needed to assist TDA developers with enhancing the execution runtime of their particular TDAs when using the EMPIRE software suite. Typically this class of support might include, but not be limited to, API enhancements/adaptations; modifications to EMPIRE's internal structures and self contained interfaces; and advice on improved means of interfacing the subject TDA with EMPIRE.

ii. TDA Verification & Validation Support: Tasks in this category generally will include, but not be limited to, efforts needed to verify and validate the performance of the task sponsor identified TDA to ensure the accuracy of the TDA's analytical results. Typical tasks may include participation in field measurement campaigns, to include test planning, range scheduling, test execution, etc., statistical data analysis & reduction of field measurements, comparison of field measurements to TDA generated analysis results, comparisons of TDA-generated results to those produced by standalone EMPIRE or standalone propagation models, TDA software design reviews as described in the Joint Accreditation Support Activity’s (JASA) Accreditation Support Plans (ASP). For more information on DoD’s modeling & simulation verification, validation and accreditation processes, see https://www.dmso.mil/public/transition/vva/. For more information on JASA, see http://www.nawcwpns.navy.mil/~jasa/. Support tasks in this category may also include developing and presenting technical papers at professional conferences (IEEE, AOC, etc.).

iii. Propagation Model Updates: Tasks in this category generally will include, but not be limited to efforts needed to update the existing component propagation models contained in EMPIRE. The contractor shall:

a. Integrate & test new versions of EMPIRE’s component propagation models.

b. Work with the component model developers to resolve any errors discovered during unit, integration, regression or functional testing, & ensure critical corrections to the models are implemented in EMPIRE.

c. Revise &/or update EMPIRE’s model recommendation rule set to reflect any changes brought about by the propagation model updates.

d. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand how to properly utilize the updated propagation model. Descriptions of model updates, enhancements, results of unit, integration, regression & functional testing as well as changes to the component model’s documentation suite shall be incorporated into the EMPIRE documentation suite.

e. Demonstrate successful implementation of the updated propagation models for no more than two (2) contractor-selected / government approved test scenarios.

iv. Propagation Model Integration: Tasks in this category generally will include, but not be limited to efforts needed to add existing propagation models, algorithms & supporting data sources to the EMPIRE suite as identified by the task sponsor. Algorithms, models & data sources may come from the following or similar categories of EM phenomenology:

a.

Ionospheric propagation models, algorithms, models & data sources b.

Ground wave & sky wave propagation algorithms, models, & data sources c.

Multipath algorithms, models, & data sources d.

Parabolic Equation algorithms, models, & data sources e.

Diffraction algorithms, & models, data sources f.

“Point-to-Point”, “Area Coverage” & “Volumetric” algorithms, models, & data sources g.

Trans-Horizon transmission algorithms, models, & data sources h.

Urban Propagation algorithms, models, & data sources i.

Empirically based algorithms, models & data sources j.

Space, Exo-atmospheric & trans-atmospheric algorithms, models, & data sources k.

Fading channel, scintillation, & multi-path algorithms, models, & data sources l.

Ducting algorithms, models, & data sources m.

Ray tracing algorithms, models, & supporting data n.

Finite Difference Time Domain (FDTD) algorithms, models, & supporting data o.

Uniform Theory of Diffraction (UTD) algorithms, models, & supporting data p.

Geometric Theory of Diffraction (GTD) algorithms, models, & supporting data q.

Time Domain & Wideband algorithms, techniques, model & supporting data.

r.

Algorithms for uniform handling/manipulation/caching of MetOc, Ionospheric, terrain, foliage, dielectric, and noise data.

The contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the newly added propagation models & add them to the EMPIRE test case suite.

b. Execute these test cases, and report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand how to properly utilize the newly added propagation model.

d. Demonstrate successful implementation of the newly integrated propagation model for no more than two (2) contractor-selected / government approved test scenarios.

v. EMPIRE Defect Repairs: Tasks in this category generally will include, but not be limited to efforts needed to correct defects in the EMPIRE software as identified by the task sponsor. The contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the identified defects & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand the implications of the defect & to properly utilize the repaired capability.

d. Demonstrate successful implementation of the “repairs” for no more than two (2) contractor-selected / government approved test scenarios.

vi. Antenna Modeling Support: Tasks in this category generally will include, but not be limited to, modeling assorted antennas & related components for use in EMPIRE; the generation of antenna pattern data delivered in a task sponsor defined format; the documentation of the processes used to generate antenna pattern data; the interfacing/integration of antenna modeling libraries & data generation tools such as the Antenna Integrated Resource Environment (AIRE) with EMPIRE; the enhancement of AIRE to include new antenna classes (types), or other efforts that affect how EMPIRE handles antennas. Where appropriate to the individual task order, the contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the tasked antenna modeling capability & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the antenna modeling capability capability.

d. Demonstrate successful implementation of the antenna modeling capabilities for no more than two (2) contractor-selected / government approved test scenarios.

vii. Development of Specially Structured EMPIRE Versions: Tasks in this category generally will include, but not be limited to efforts needed to produce specially formatted & structured version of EMPIRE to meet task sponsor needs. For example, this might be the development of a version of EMPIRE that might be releasable to foreign nations, or to the commercial market, or the development of a services oriented architecture (SOA) version of EMPIRE.

viii. Commercial Capabilities Integration: Tasks in this category generally will include, but not be limited to, efforts needed to integrate selected commercially available EM propagation & related products that have an existing API. Such products may include “Wireless InSite”, “XFDTD”, & “XGTD” amongst others. The contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the integrated commercial capability & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the integrated commercial capability.

d. Demonstrate successful integration of the commercial capabilities for no more than two (2) contractor-selected / government approved test scenarios.

ix. Meteorological & Oceanographic (MetOc) Modeling: Tasks in this category generally will include, but not be limited to, phenomenology investigation, software development, & testing, integration of existing capabilities to use meteorological & oceanographic models, algorithms, & data in the computation of electromagnetic propagation effects. These efforts might include enhancement of the capability in EMPIRE to directly read data from DoD MetOc data sources using the Joint MetOc broker language (JMBL), or modifying the climatological capabilities in EMPIRE to recover ducting condition information, or implementing the capability to read data directly from MetOc soundings or the IBS-N real-time intelligence broadcast system. Other tasks may include implementing the ability to handle large MetOc datasets or allow for various interpolations between data points. Where appropriate to the individual task order, the contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the MetOc capabilities & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the MetOc capability.

d. Demonstrate successful implementation of the MetOc modeling capabilities for no more than two (2) contractor-selected / government approved test scenarios.

x. Geo-Environmental Modeling: Tasks in this category generally will include, but not be limited to, phenomenology investigation, software development, & testing, integration of existing capabilities to use geo-environmental models, algorithms, & data sources within EMPIRE. Such tasks may involve, but not be limited to enhancement & updating dielectric constant databases & modeling capabilities, studying the effects of mixed resolution digital terrain data on EM propagation modeling results, studying & modeling the effects of natural & man-made obscurants / aerosols, (i.e. snow, sleet, rain, smoke, fog, foliage, etc.) on RF signal propagation, development of the capability to model natural & man-made radio frequency noise, in a variety of operationally relevant setting from rural to urban environments, and studying & implementing the capabilities to model the effects of the Earth’s magnetic fields on Electromagnetic propagation. Where appropriate to the individual task order, the contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the geo-environmental capabilities & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the geo-environmental capabilities.

d. Demonstrate successful implementation of the geo-environmental modeling capabilities for no more than two (2) contractor-selected / government approved test scenarios.

b. ELECTROMAGNETIC PROPAGATION MODELING RESEARCH AND DEVELOPMENT SUPPORT: Tasks in this category specifically consist of those efforts that focus on basic scientific research and development & those efforts needed to develop and implement new capabilities in the EMPIRE software. In all cases, each new capability will need to be vetted using an appropriate combination of peer review or and/or presentations at recognized technical symposia and conferences. The vetting process may also include the use of traditional verification & validation processes to include field measurement campaigns as described in 3. b. vii. below. Potential topic areas in this category could consist of understanding & documenting the physical phenomenology in the interrelated areas of Electromagnetic (EM) Propagation, Meteorology & Oceanography (MetOC), and geo-environmental sciences, designing new modeling capabilities of those phenomenologies, and implementing these new capabilities into the EMPIRE software suite. The following list, while not exhaustive, is meant to illustrate types of individual tasks that could fit task category:

i. Antenna Modeling Capability Development: Tasks in this category generally will include, but not be limited to development of new antenna modeling tools and analytical algorithms, as well as developing & documenting new procedures (using new and/or existing antenna modeling tools like EIGER, NEC-4, Feko, etc) to generate antenna patterns for specific type of antennas. Where appropriate to the individual task order, the contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the tasked antenna modeling capability & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the antenna modeling capability capability.

d. Demonstrate successful implementation of the antenna modeling capabilities for no more than two (2) contractor-selected / government approved test scenarios.

ii. Electromagnetic Propagation Algorithms, Models & Data Sources Development: Tasks in this category generally will include, but not be limited to, electromagnetic propagation phenomenology investigation, the implementation of new electromagnetic propagation models, algorithms, & data sources covering the extremely low to extremely high frequency range (3 Hz to 300 GHz). Phenomenology, algorithms, models & data sources of interest will include but not be limited to:

a.

Ionospheric propagation models, algorithms, models & data sources b.

Ground wave & sky wave propagation algorithms, models, & data sources c.

Multipath algorithms, models, & data sources d.

Parabolic Equation algorithms, models, & data sources e.

Diffraction algorithms, & models, data sources f.

“Point-to-Point” & “Area Coverage” algorithms, models, & data sources g.

Trans-Horizon transmission algorithms, models, & data sources h.

Urban Propagation algorithms, models, & data sources i.

Empirically based algorithms, models & data sources j.

Space, Exo-atmospheric & trans-atmospheric algorithms, models, & data sources k.

Fading channel, scintillation, & multi-path algorithms, models, & data sources l.

Ducting algorithms, models, & data sources m.

Ray tracing algorithms, models, & supporting data n.

Finite Difference Time Domain (FDTD) algorithms, models, & supporting data o.

Uniform Theory of Diffraction (UTD) algorithms, models, & supporting data p.

Geometric Theory of Diffraction (GTD) algorithms, models, & supporting data q.

Time Domain & Wideband algorithms, techniques, model & supporting data.

r.

Development of algorithms for uniform handling/manipulation/caching of MetOc, terrain, foliage, dielectric, and noise data.

The contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the newly added propagation models & add them to the EMPIRE test case suite. The contractor shall

b. Execute these test cases, and report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand how to properly utilize the newly added propagation model.

d. Demonstrate successful implementation of the newly integrated propagation model for no more than two (2) contractor-selected / government approved test scenarios.

iii. Analysis Algorithms & Performance Metrics Development: Tasks in this category will generally consist of the research, development, design & implementation of new analysis algorithms & performance metrics for the analytical tool(s) identified by the task sponsor. Example of tasks might include, but not be limited to the development of algorithms to perform mixed Time Difference of Arrival (TDOA) & Frequency Difference of Arrival (FDOA) for fixed, ground mobile, Ship borne & Airborne signals intelligence (SIGINT) collection systems, or the development of EM propagation measures of merit (MOM), measures of performance (MOP), & measures of effectiveness (MOE), (eg, Lott Plots, Probability of Signal Acquisition, etc.) The contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the newly developed analysis algorithm or performance metric capability & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the newly developed analysis algorithm or performance metric capability.

d. Demonstrate successful implementation of the newly developed analysis algorithm or performance metric capability for no more than two (2) contractor-selected / government approved test scenarios.

iv. Specialized Hardware & Software Development: Development of hardware & software-based processing acceleration techniques to include the use of commercial video graphics cards, graphics processing units (GPUs) such as the NVIDIA TESLA™ family, specialized digital signal processing chips & circuit cards, field programmable gate arrays, array processors, & computer clusters built using commercial gaming engines such as the SONY PS-2/PS-3™ family, coprocessor card’s such as Aegia’s “PhysX”™, ClearSpeed’s “Advance”™ series or other related combinations of hardware & software.

v. Meteorological & Oceanographic Modeling: Tasks in this category generally will include, but not be limited to, phenomenology investigation, software development, & testing, integration of new capabilities to use meteorological & oceanographic data in the computation of electromagnetic propagation effects. These efforts might include developing new models, algorithms or data set to recover information on elevated ducts from existing metoc data sources, or implementing a new capability to read data directly from MetOc soundings or the IBS-N real-time intelligence broadcast system. Other tasks may include implementing a new capability to handle large MetOc datasets or allow for various interpolations between data points. Where appropriate to the individual task order, the contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the MetOc capabilities & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the MetOc capability.

d. Demonstrate successful implementation of the MetOc modeling capabilities for no more than two (2) contractor-selected / government approved test scenarios.

vi. Geo-Environmental Modeling: Tasks in this category generally will include, but not be limited to, phenomenology investigation, software development, implementation, testing & integration support leading to the fielding of new or improved capabilities in EMPIRE. Such tasks may involve, but not be limited to development of dielectric constant databases & modeling capabilities, studying the effects of mixed resolution digital terrain data on EM propagation modeling results, studying & modeling the effects of natural & man-made obscurants / aerosols, (i.e. snow, sleet, rain, smoke, fog, foliage, etc.) on RF signal propagation, development of the capability to model natural & man-made radio frequency noise, in a variety of operationally relevant setting from rural to urban environments, and studying & implementing the capabilities to model the effects of the Earth’s magnetic fields on Electromagnetic propagation. Where appropriate to the individual task order, the contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the geo-environmental capabilities & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the geo-environmental capabilities.

d. Demonstrate successful implementation of the geo-envornmental modeling capabilities for no more than two (2) contractor-selected / government approved test scenarios.

vii. TDA Verification & Validation Support: Tasks in this category generally will include, but not be limited to, efforts needed to verify and validate the performance of the task sponsor identified TDA to ensure the accuracy of the TDA's analytical results. Typical tasks may include participation in field measurement campaigns, to include test planning, range scheduling, test execution, etc., statistical data analysis & reduction of field measurements, comparison of field measurements to TDA generated analysis results, comparisons of TDA-generated results to those produced by standalone EMPIRE or standalone propagation models, TDA software design reviews as described in the Joint Accreditation Support Activity’s (JASA) Accreditation Support Plans (ASP). For more information on DoD’s modeling & simulation verification, validation and accreditation processes, see https://www.dmso.mil/public/transition/vva/. For more information on JASA, see http://www.nawcwpns.navy.mil/~jasa/. Support tasks in this category may also include developing and presenting technical papers at professional conferences (IEEE, AOC, etc.).

viii. Commercial Capabilities Integration: Tasks in this category generally will include, but not be limited to, efforts needed to integrate selected commercially available EM propagation & related products that have an existing API. Such products may include “Wireless InSite”, “XFDTD”, & “XGTD” amongst others. The contractor shall:

a. Produce unit, integration, regression and / or functional test cases for the integrated commercial capability & add them to the EMPIRE test case suite.

b. Execute these test cases, & report findings in a technical memorandum to be added to the EMPIRE software test report (STR).

c. Update the EMPIRE software user’s manual (SUM) with information needed by TDA developers & users to understand & properly utilize the integrated commercial capability.

d. Demonstrate successful integration of the commercial capabilities for no more than two (2) contractor-selected / government approved test scenarios.

c. PROGRAM MANAGEMENT: Overall program management requirements for the base contract and all task orders will be specified in a “program management” task. Task specific requirements will be identified in the individual task orders. In all cases monthly status reporting for the basic contract and all task orders will be consolidated in to a single monthly status report.

4. SERVICE DELIVERY SUMMARY: The following performance objectives and thresholds will be used by 453 EWS quality assurance personnel to assess successful accomplishment and progress on the basic contract. Task order specific performance objectives and thresholds will be included with each individual task order.

Objective: Ensure software usability by EMPIRE Users (aka TDA developers) Deliverable: Support to TDA developers & EMPIRE users

Objective: Produce EMPIRE software releases Deliverable: EMPIRE software releases containing EMPIRE software and documentation

Documentation will not require more than 2 significant corrections/edits per release cycle.

Objective: Ensure sponsored research & software designs are technically sound and scientifically accurate Deliverable: Research / Technical Reports & Presentations 3.a.ii, 3.a.ix, 3.a.x, 3.b.ii, 3.b.iii, 3.b.iv, 3.b.v, 3.b.vi.

3.b.vii.

All research & technical reports are reviewed & approved by QA personnel prior to starting software development efforts. No more than 2 Task Order QAP directed rework” per release cycle.

5. DELIVERABLES

a. Deliverable Format: All deliverables will be provided on a Microsoft Windows “readable” DVD or CD disk containing the EMPIRE software archive in both ".zip" and ".tgz" compressed formats. At conclusion of the contract, the contractor shall deliver a consolidated digital archive containing all documentation (monthly status reports, technical reports, data accession list, EMPIRE software documentation, etc) generated under all task orders to the 453 EWS QAP. All documentation deliverables prepared during the contract and its individual task orders will be created using Microsoft Office product suite, version 2000 or later, to include “Visio”, and “Project”, and Adobe Acrobat (PDF-format), or in HTML/XML format, & delivered to the QAP & the task sponsor. Unless otherwise specified, contractor format for all documentation is acceptable.

a.

b. Standard EMPIRE Deliverable Contents: A normal EMPIRE delivery “package” will consist of the following items:

i. Executable code (object libraries, etc.; those files an external TDA needs to interface with EMPIRE.)

ii. Supporting documentation which will include all of the following:

· API documentation

· Propagation Primer

· EMPIRE Software User’s Guide

· EMPIRE Software Design Description

· EMPIRE Software Requirements Specification

· EMPIRE Software Test Report

· Any specific system configuration & installation instructions such as Platform notes, Change logs, etc.

c. Incorporation of Software Modifications into EMPIRE: The NIOC-Suitland EMPIRE Program Manager has furnished written authorization for the modifications developed under this contract to be incorporated into the EMPIRE baseline software upon completion of each task order. Orders placed against this contract will be construed as authorization from the task sponsor to incorporate task sponsored modifications into the EMPIRE baseline software upon completion of each contracted task. This shall include all source code, header files, object code, documentation, test cases, etc. Additionally, orders placed against this contract shall also be construed to mean the task sponsor implicitly grants NIOC approval to release the software & documentation developed during this effort to any future approved EMPIRE requestors or using organizations.

d. Contract Data Requirements List (CDRL): The following list of Data Item Descriptions (DIDs) is available for use by task orders issued under this contract:

6. PERFORMANCE PERIOD: The period of performance for the base contract is one (1) year with four (4) option years

7. PERFORMANCE LOCATION: All work shall be performed at the contractor’s facilities, and at locations specified in individual task orders.

8. TRAVEL REQUIRMENTS: All contractor travel will be specified in the individual task orders, and will be in compliance with the provisions of the Joint Travel regulations (JTR). When government & contractor personnel travel is coincident (same dates, same destination, same travel objective), government personnel will obtain rental car & miscellaneous supplies (fuel, oil, tools, parking) and contractor personnel shall attempt to have identical travel & lodging arrangements as government travelers.

9. GOVERNMENT FURNISHED PROPERTY, EQUIPMENT & SERVICES: Specific requirements for Government furnished property, equipment, information or support services will be identified in the individual task orders issued under this basic contract. In general, should the contractor require other items not specifically identified in the individual task orders, the contractor shall request the items, in writing, to the quality assurance personnel (QAP). They will work with the task sponsor & the servicing contracting office to fulfill these requests within established security procedures, guidelines & availability of funding.

10. SECURITY REQUIREMENTS:

All security requirements for this contract and its subsequently issued task orders will be detailed in the DD 254 and its supplements and attachments.

a.

b.

11. RELEASE OF SCIENTIFIC & TECHNICAL INFORMATION: Foreign hostile intelligence organizations continue increasing the scope of their collection efforts against all aspects of DoD activities & operations. When developing advanced modeling, simulation or analytical tools for the defense & intelligence communities, inadvertent or overt disclosure of programs currently being pursued or employed must be avoided in order to maintain the technological advantage these capabilities provide. Yet, as stewards of the taxpayers’ resources we must ensure maximum reusability of the capabilities developed within appropriate communities. Therefore, in accordance with the requirements, processes and procedures contained in Air Force Instruction (AFI) 61-202 “United States Air Force Technical Publications Program”, dated 25 July 1994 and AFI 61-204 “Disseminating Scientific and Technical Information”, dated 30 August 2002, all materials developed during this effort shall be clearly marked with a unique identifying serial number, the appropriate “distribution statement” based on their classification level, a warning notice for those materials that are “export controlled”, and a “destruction notice”. For classified documents, these marking are in addition to the security classification markings required by US defense and intelligence communities detailed in their respective security classification guidance.

Unclassified materials shall be marked with distribution statement C as shown here:

DISTRIBUTION C - Distribution authorized to U.S. Government agencies and their contractors (CRITICAL Technology) 19 November 2003. Refer other requests for this document to 453 EWS/EWA, 102 Hall St, Ste 333, San Antonio, TX 78243-7020. (210) 977-2427; DSN 969-2427

Classified materials shall be marked with distribution statement F as shown here:

DISTRIBUTION F - Further dissemination only as directed by 453 EWS/EWA or DoD higher authority (per DoD 5200.1-R para 5.208). Refer other requests for this document to 453 EWS/EWA, 102 Hall St, Ste 333, San Antonio, TX 78243-7020. (210) 977-2427; DSN 969-2427.

Export controlled materials shall contain the following notice in addition to the distribution statement:

WARNING -- This document contains technical data whose export is restricted by the Arms Export Control Act (Title 22, U.S.C. 2751 et seq.) or the Export Administration Act of 1979, as amended, Title 50, U.S.C., App. 2401, et seq. Violation of these export-control laws is subject to severe criminal penalties. Dissemination of this document is controlled under DoD Directive 5230.25.

All materials shall be marked with the following destruction notices:

DESTRUCTION NOTICE: For SCI classified materials - follow the requirements in DoD 5105.21-M-1, Sensitive Compartmented Information Administrative Security Manual. For Non-SCI classified materials, follow the procedures in DoD 5220.22-M, National Industrial Security Program Operating Manual (NISPOM), section 5-705, or DoD 5200.1-R, Information Security Program Regulation, Chapter VI. For unclassified, limited distribution materials, destroy by any method that will prevent disclosure of contents or reconstruction of the material.

All materials shall be marked with the appropriate government rights as described in the federal acquisition regulations (FAR) Part 27, Sub Part 27.4, and Defense Federal Acquisition Regulations (DFARS), Part 227, Sub Part 227.71, and implementing terms and clauses. The contractor shall be responsible for completing the Standard Form 298 “Report Documentation” for scientific and technical reports generated during this effort.

12. MISSION ESSENTIAL PERSONNEL STATEMENT: The contractor’s personnel are NOT considered to be essential personnel during national emergencies and/or wartime.

� EMBED MSPhotoEd.3 ���

�Mary/Donna: We really don’t want this to be 2 minor corrections like a typographical error, but rather 2 major , significant content revision per release cycle. Does this newly revised statement work that way?

�After more complete review, I would drop All report DIDs except DI-MISC-80652. It will need to be tailored to eliminate the formatting requirements

�I forgot to add the following

DI-IPSC-81438A “SOFTWARE TEST PLAN” (STP);

DI-IPSC-81439A “SOFTWARE TEST DESCRIPTION” (STD),

DI-IPSC-81488 “COMPUTER SOFTWARE PRODUCT” (where the code is actually delivered), I would use the new one & drop DI-MCCR-80700 as it more clearly defines what the deliverable contains.

- DI-IPSC-81633 “SOFTWARE PROGRAMMER”S GUIDE” (which needs tailoring in the DD-1423 CDRL to remove the formatting requirements

�I forgot to add the following

DI-IPSC-81438A “SOFTWARE TEST PLAN” (STP);

DI-IPSC-81439A “SOFTWARE TEST DESCRIPTION” (STD),

DI-IPSC-81488 “COMPUTER SOFTWARE PRODUCT” (where the code is actually delivered), I would use the new one & drop DI-MCCR-80700 as it more clearly defines what the deliverable contains.

- DI-IPSC-81633 “SOFTWARE PROGRAMMER”S GUIDE” (which needs tailoring in the DD-1423 CDRL to remove the formatting requirements

UNCLASSIFIED // FOR OFFICIAL USE ONLY

_1178569930.bin