(U) NGA_CTDR_Template_05122025.xlsx

1 Introduction

CLASSIFICATION: UNCLASSIFIED

Trung C. Trieu-DNI-Y-: Please classify each tab appropriately, if populated.

&"Courier"&12UNCLASSIFIED

&"Courier"&12UNCLASSIFIED

GENERAL INSTRUCTIONS:

1. The following workbook should be filled out annually, as well as at FOC and in support of contract close-out. If the data provided is for a follow-on contract, please ensure that the first submittal of data captures only the existing baseline prior to any modifications.

2. Please provide as much detail as possible for each included development effort.

3. Orange cells contain drop-down menus. Peach cells are conditional cells that are automatically populated from other sources.

4. Comments in each header row cell provide definitions/clarification on what data should be captured in each field.

5. Please use the text box below to provide a description of any changes that have occurred since the last submission of this datasheets. This should include any contract, schedule, scope, planning, development, or other changes to the system.

6. Please classify on each tab accordingly.

Description of Changes from Previous Submission:

In addition to filling out these spreadsheets, please provide the following in separate documentation:

- Cost Reporting information (specific format to be determined in coordination with agency cost groups)

- Detailed descriptions of implemented agile development methods and processes (if agile development is performed)

2 Program Info

CLASSIFICATION: UNCLASSIFIED

Trung C. Trieu-DNI-Y-: Please classify each tab appropriately, if populated.

Saumil S. Shah-DNI-Y-: Description of primary program capabilities to support the MSA/PSI/SIA being reported. This field only needs to be filled out if the MSA/PSI/SIA is supporting multiple functions.

Data Analysis and Exploitation The Analysis and Exploitation function is responsible for examination of mission data (dissection, investigation, cross-referencing, etc.) and conversion of this data into finished intelligence. This includes manual and automated integration, evaluation and analysis of all available data. The process is completed with the preparation of intelligence products that include assessments of events and judgments about the implications of the information.

The Analysis and Exploitation function would include:

• Manage Need

• Manage Analytic Mission

• Perform Analysis

• Detection

• Change Detection

• Multi-INT Data Integration & Fusion

• Classification

• Identification

• Association

• Tracking

• Forecasting

• Tipping

• Exploit Data Sets

Command and Control (CC) The Command and Control (CC) function provides CC for the vehicle and payloads. This function decodes, demultiplexes, and decrypts telemetry, generates and encrypts commands for transmission and processes tracking data to generate ephemeris. This function provides the capability to prepare and output commands to receive and process telemetry, tracking, and other non-mission data from the vehicle.

The Command and Control function would include:

• Schedule Execution

• Command Generation

• Uplink Data Generation

• Telemetry Processing

• State Management

• Vehicle Maintenance

• Space Vehicle Simulation

Mission Management (MM) The Mission (Payload Data) Management function receives tasking, generates and provides the system and mission plans, schedules, and timelines for the vehicle and Ground Segment(s).

The Mission Management function would include:

• Task Management

• Mission Analysis

• Mission Plan Generation

• Collection Schedule Generation

• Real Time Schedule Management

• Orchestration

• Mission Execution

Dissemination The Dissemination Function includes the timely distribution of intelligence products to departmental and agency intelligence consumers in a suitable form.

The Dissemination function would include:

• Manage Enterprise Services

• Measure Content access

• Visualize GEOINT

• Organize Content

Ground Terminal The Ground Terminal (GT) function receives, demodulates and conditions telemetry, tracking, command and mission (payload) data. In addition this system generates the radio frequency (RF) uplink, accepts tracking and command signals, and modulates them onto the RF uplink.

The Ground Terminal function would include:

• GT Foundation / Field

• GT Antenna (a...n)

• GT Optical Communication Assembly (OCA)

• GT RF and Digital Electronics (GTEL) (Band a...n)

• GT Baseband Network and Data Handling Equipment (GTNW)

• GT Monitor and Control (GTMC)

Infrastructure & Framework (I&F) The Infrastructure & Framework (I&F) function includes hardware and/or software that supports multiple functions, supports engineering development of administrative networks, and/or supports development of systems required to interface to other ground segments (other programs) at the same Ground Site.

The Infrastructure & Framework function would include:

• Compute

• Record

• Store

• Routing

• Distribution

• Service Broker

• Sharing

• Fusion

• Tools

Mission Data Processing (MP) The Mission Data Processing function decodes, demultiplexes, decrypts and processes Mission data from the Payload(s) and provides usable data for analysis and exploitation.

The Mission Data Processing function would include:

• Data Conditioning

• Mission Data Processing

• Processing Workflow Management

• Mission Data Management

• Quality Assurance

Tasking and Management The Tasking and Management function includes generating requests for data, delivering instructions to a collection element, and subsequently tracking the fulfillment of each request.

The Tasking and Management function would include:

• Manage Source Strategies

• Monitor Strategy Execution

• Determine Value

• Manage Supplier Needs

• Manage Source Models

c. Secondary Program Function Saumil S. Shah-DNI-Y-: Description of secondary program capabilities to support the MSA/PSI/SIA being reported. This field only needs to be filled out if the MSA/PSI/SIA is supporting multiple functions.

Data Analysis and Exploitation The Analysis and Exploitation function is responsible for examination of mission data (dissection, investigation, cross-referencing, etc.) and conversion of this data into finished intelligence. This includes manual and automated integration, evaluation and analysis of all available data. The process is completed with the preparation of intelligence products that include assessments of events and judgments about the implications of the information.

The Analysis and Exploitation function would include:

• Manage Need

• Manage Analytic Mission

• Perform Analysis

• Detection

• Change Detection

• Multi-INT Data Integration & Fusion

• Classification

• Identification

• Association

• Tracking

• Forecasting

• Tipping

• Exploit Data Sets

Command and Control (CC) The Command and Control (CC) function provides CC for the vehicle and payloads. This function decodes, demultiplexes, and decrypts telemetry, generates and encrypts commands for transmission and processes tracking data to generate ephemeris. This function provides the capability to prepare and output commands to receive and process telemetry, tracking, and other non-mission data from the vehicle.

The Command and Control function would include:

• Schedule Execution

• Command Generation

• Uplink Data Generation

• Telemetry Processing

• State Management

• Vehicle Maintenance

• Space Vehicle Simulation

Mission Management (MM) The Mission (Payload Data) Management function receives tasking, generates and provides the system and mission plans, schedules, and timelines for the vehicle and Ground Segment(s).

The Mission Management function would include:

• Task Management

• Mission Analysis

• Mission Plan Generation

• Collection Schedule Generation

• Real Time Schedule Management

• Orchestration

• Mission Execution

Dissemination The Dissemination Function includes the timely distribution of intelligence products to departmental and agency intelligence consumers in a suitable form.

The Dissemination function would include:

• Manage Enterprise Services

• Measure Content access

• Visualize GEOINT

• Organize Content

Ground Terminal The Ground Terminal (GT) function receives, demodulates and conditions telemetry, tracking, command and mission (payload) data. In addition this system generates the radio frequency (RF) uplink, accepts tracking and command signals, and modulates them onto the RF uplink.

The Ground Terminal function would include:

• GT Foundation / Field

• GT Antenna (a...n)

• GT Optical Communication Assembly (OCA)

• GT RF and Digital Electronics (GTEL) (Band a...n)

• GT Baseband Network and Data Handling Equipment (GTNW)

• GT Monitor and Control (GTMC)

Infrastructure & Framework (I&F) The Infrastructure & Framework (I&F) function includes hardware and/or software that supports multiple functions, supports engineering development of administrative networks, and/or supports development of systems required to interface to other ground segments (other programs) at the same Ground Site.

The Infrastructure & Framework function would include:

• Compute

• Record

• Store

• Routing

• Distribution

• Service Broker

• Sharing

• Fusion

• Tools

Mission Data Processing (MP) The Mission Data Processing function decodes, demultiplexes, decrypts and processes Mission data from the Payload(s) and provides usable data for analysis and exploitation.

The Mission Data Processing function would include:

• Data Conditioning

• Mission Data Processing

• Processing Workflow Management

• Mission Data Management

• Quality Assurance

The Tasking and Management function includes generating requests for data, delivering instructions to a collection element, and subsequently tracking the fulfillment of each request.

The Tasking and Management function would include:

• Manage Source Strategies

• Monitor Strategy Execution

• Determine Value

• Manage Supplier Needs

• Manage Source Models

d. Protection Level woollej: Description of the appropriate Protection Level (PL) for information systems (IS) based on the required clearance(s), formal access approval(s), and need-to-know of all direct and indirect users who receive information from the IS without manual intervention and reliable human review. It indicates an implicit level of trust that is placed in the system’s technical capabilities.

PL1: An IS operates at Protection Level 1 when all users have all required approvals for access to all information on the IS. This means that all users have all required clearances, formal access approvals, and the need to know for all information on the IS.

PL2: An IS operates at Protection Level 2 when all users have all required formal approvals for access to all information on the IS, but at least one user lacks administrative approval for some of the information on the IS. This means that all users have all required clearances and all required formal access approvals, but at least one user lacks the need to know for some of the information on the IS.

PL3: An IS operates at Protection Level 3 when at least one user lacks at least one required formal approval for access to all information on the IS. This means that all users have all required clearances, but at least one user lacks formal access approval for some of the information on the IS.

PL4: An IS operates at Protection Level 4 when at least one user lacks sufficient clearance for access to some of the information on the IS, but all users have at least a Secret clearance.

PL5: An IS operates at Protection Level 5 when at least one user lacks any clearance for access to some of the information on the IS.

e. Domain Level Saumil S. Shah-DNI-Y-: Clearance Level for Domain (i.e.: Top Secret)

Saumil S. Shah-DNI-Y-: The requirement for retention of data for the program (Years)

Jennifer G. Woolley-DNI-Y-: Provide the current dates (actual or anticipated) for the provided milestones (MM/DD/YYYY) k. Comments/Notes Jennifer G. Woolley-DNI-Y-: Provide any comments/notes necessary to provide clarification, additional detail, or context

Davis Aubrey M NGA-DXAC USA CTR: Regarding the subsystem, the date that the product was released or delivered: MM/DD/YYYY

o. Subsystem Davis Aubrey M NGA-DXAC USA CTR: Identify the top-level CSCI or components of the computer application

Davis Aubrey M NGA-DXAC USA CTR: The number of interfaces of the subsystem on the Domain

Rhodes Kenneth S NGA DXAC USA CTR: Periodicity, Timeliness, Throughput, Size t2. Performance Attributes (L2) u1. Security (L1) Rhodes Kenneth S NGA DXAC USA CTR: Protection, Classification, Caveat, Releasability, Security Standard

Davis Aubrey M NGA-DXAC USA CTR: Regarding each subsystem, any comments/notes necessary to provide clarification, additional detail, or context. Describe any contractual situations that should be taken into account when evaluating the total cost of the program.

&"Courier"&12UNCLASSIFIED

&"Courier"&12UNCLASSIFIED

INSTRUCTIONS:

Please add rows to the tables below as necessary

The data provided in this section should be based on data collected as part of the data migration and data conditioning process. Database development relevant data should be excluded from this datasheet.

3 Contract Info

CLASSIFICATION: UNCLASSIFIED

Trung C. Trieu-DNI-Y-: Please classify each tab appropriately, if populated.

Saumil S. Shah-DNI-Y-: Location of the prime contactor (City, State)

Saumil S. Shah-DNI-Y-: % of contract that is subcontracted out to other parties

h. Comments/Notes Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-Y-: Please provide the contract number

The 1st row should contain base contract data

woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY

Found in Block 5.j of IPMR m. Option Executed Saumil S. Shah-DNI-Y-: Has the option of the contact been executed (Yes/No)

n. Hours/FTE Saumil S. Shah-DNI-Y-: Provide the number of hours per FTE used on the contract

For example:

- 1860 hrs

- 1920 hrs

- etc.

o. Comments/Notes Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Saumil S. Shah-DNI-Y-: Location of the sub-contactor (City, State)

woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY

Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY

Found in Block 5.j of IPMR bb. Option Executed Saumil S. Shah-DNI-Y-: Has the option of the contact been executed (Yes/No)

cc. Hours/FTE Saumil S. Shah-DNI-Y-: Provide the number of hours per FTE used on the contract

For example:

- 1860 hrs

- 1920 hrs

- etc.

dd. Comments/Notes Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-: Provide a description of the activities performed as part of the Engineering Change Proposal (ECP)

Note: In addition to the ECP title, please provide contextual information regarding the ECP scope and effort nn. ECP Type Saumil S. Shah-DNI-Y-: Type of ECP associated with changes to the contract baseline

Special Study:

- Special studies and all related items

Engineering Change Order (Technical Requirements):

- Changes via Engineering Change Order (ECO), Engineering Change Proposal (ECP), Contract Change Proposal (CCP), or Special Contract Requirement (SCR)

Schedule Impacts:

- Government-directed schedule slips and/or negotiated schedule extensions indirectly related to requirement and/or technical changes

Estimation Revision:

- Estimating revision and proposal pricing errors

Other:

- Including, but not limited to, requests for equitable adjustments, economic price adjustments, GFE/GFP to CFE/CFP cost, overhead rate adjustment, inflation

Trung C. Trieu-DNI-Y-: Provide the negotiated duration (in months) of the ECP.

qq. Negotiated ECP Value Saumil S. Shah-DNI-Y-: Provide the value of the ECP negotiated between the Program Office and Contractor

Trung C. Trieu-DNI-Y-: Please classify each tab appropriately, if populated.

Jennifer G. Woolley-DNI-Y-: Please provide the name of the prime contractor company Saumil S. Shah-DNI-Y-: Location of the prime contactor (City, State) woollej: Indicate type of contract (list includes those described in the FAR) woollej: Please provide the date that the contract started (whether it is anticipated or has already occurred): MM/DD/YYYY woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY Jennifer G. Woolley-DNI-Y-: Please provide the contract number

The 1st row should contain base contract data The additional rows should contain Option year data Saumil S. Shah-DNI-Y-: Total contract value ($) Jennifer G. Woolley-DNI-Y-: Provide the base and option years of the contract Saumil S. Shah-DNI-Y-: % of contract that is subcontracted out to other parties woollej: Please provide the date that the contract started (whether it is anticipated or has already occurred): MM/DD/YYYY Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY

Found in Block 5.j of IPMR Saumil S. Shah-DNI-Y-: Has the option of the contact been executed (Yes/No)

Saumil S. Shah-DNI-Y-: Provide the number of hours per FTE used on the contract

For example:

- 1860 hrs

- 1920 hrs

- etc.

Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-Y-: Please provide the names of all sub-contractors supporting the given contract number Saumil S. Shah-DNI-Y-: Location of the sub-contactor (City, State) woollej: Indicate type of contract (list includes those described in the FAR) Jennifer G. Woolley-DNI-Y-: Please provide the contract number woollej: Please provide the date that the contract started (whether it is anticipated or has already occurred): MM/DD/YYYY woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY

Saumil S. Shah-DNI-Y-: Total contract value ($) Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-Y-: Please provide the contract number Jennifer G. Woolley-DNI-Y-: Provide the base and option years of the contract woollej: Please provide the date that the contract started (whether it is anticipated or has already occurred): MM/DD/YYYY woollej: Please provide the date that the contract ended (whether it is anticipated or has already occurred): MM/DD/YYYY

Found in Block 5.j of IPMR Saumil S. Shah-DNI-Y-: Has the option of the contact been executed (Yes/No)

Saumil S. Shah-DNI-Y-: Provide the number of hours per FTE used on the contract

For example:

- 1860 hrs

- 1920 hrs

- etc.

Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-Y-: Please provide the contract number Jennifer G. Woolley-DNI-Y-: Please provide all of CLINs related to the contract being reported Saumil S. Shah-DNI-Y-: The value of the CLIN ($) (with Fee) Saumil S. Shah-DNI-Y-: Details of the scope of the associated CLIN Jennifer G. Woolley-DNI-Y-: Please provide any comments/notes necessary to provide clarification, additional detail, or context

Describe any contractual situations that should be taken into account when evaluating the total cost of the program (Examples: Another contract paid for a piece of development, Award of an option early in development changed development schedule/scope).

Jennifer G. Woolley-DNI-Y-: Provide the name of the program for which the ECPs are being reported Jennifer G. Woolley-DNI-Y-: Provide the contract number or "gov" if a government team is performing the work Jennifer G. Woolley-DNI-Y-: The number assigned to the ECP based on program naming conventions Jennifer G. Woolley-DNI-: Provide a description of the activities performed as part of the Engineering Change Proposal (ECP)

Note: In addition to the ECP title, please provide contextual information regarding the ECP scope and effort Saumil S. Shah-DNI-Y-: Type of ECP associated with changes to the contract baseline

Special Study:

- Special studies and all related items

Engineering Change Order (Technical Requirements):

- Changes via Engineering Change Order (ECO), Engineering Change Proposal (ECP), Contract Change Proposal (CCP), or Special Contract Requirement (SCR)

Schedule Impacts:

- Government-directed schedule slips and/or negotiated schedule extensions indirectly related to requirement and/or technical changes

Estimation Revision:

- Estimating revision and proposal pricing errors

Other:

- Including, but not limited to, requests for equitable adjustments, economic price adjustments, GFE/GFP to CFE/CFP cost, overhead rate adjustment, inflation

- Costs due to natural disasters, unforeseen events not listed above Jennifer G. Woolley-DNI-Y-: Provide the date upon which the ECP received authority to proceed (ATP) (MM/DD/YYYY) Trung C. Trieu-DNI-Y-: Provide the negotiated duration (in months) of the ECP.

&"Courier"&12UNCLASSIFIED

&"Courier"&12UNCLASSIFIED

INSTRUCTIONS:

Please add rows to the tables below as necessary

NGA requests data for all Contracts, Subcontracts, and ECPs. It is assumed that the data collection provider will provide data via one of the following methods:

Data Collection Datasheet Earned Value Management Budget Logs Pre-determined ECP Database download

4 WBS

CLASSIFICATION: UNCLASSIFIED

Includes, for example:

a. Program Office SEITPM & Risk Management

b. Integration and coordination with other programs

c. Planning and implementation of technical integration efforts, as well as the testing and evaluation of required software and hardware

1.1.1 Program Management

Management of day-to-day activities, through all phases of the program (Development, Production, O&M, etc.…).

Includes, for example:

a. Management direction (planning and direction of contract activities)

b. Planning, schedule management, and control (preparing and maintaining integrated contract master schedule)

c. Cost and performance management (analysis and control for cost expenditures, cost performance, cost estimation, budget planning, budget execution, report generation, EVM performance, etc.)

d. Contract, subcontract, and procurement administration (subcontract management and tracking)

e. Configuration management (efforts and procedures for control of program baseline to include proper tracking of GFE/GFI items)

f. Quality assurance (provide adequate confidence that a product or service will satisfy given requirements for quality)

g. Business process engineering program management (review, analyze, and develop business management processes)

h. Security management (security management efforts consistent with approved policies, procedures, and facilities)

i. Data management (control, tracking, documentation, distribution [as in the form of an integrated development environment or IDE], and disposition)

j. ROM/ECP management and preparation

k. Source selection support

l. Development, implementation, and operation of a proactive risk management program to include risk identification, quantification, and management

Excluded costs include:

a. Actual mitigation or risk avoidance costs

b. Costs tied to specific risks

c. Travel costs

d. Training costs

Includes, for example:

System engineering activities performed to evaluate and or investigate options and alternative system designs.

1.1.2.1 System Design and Architecture Technical effort required to transform user requirements into a system solution.

Includes, for example:

a. Systems engineering management (manage engineering design and development)

b. Systems requirements analysis and allocation

c. Systems architecture analysis and design (design and evaluate architecture alternatives)

d. Systems analysis and control (systems verification and validation, document requirements verification traceability matrix)

e. Data architecture and engineering (develop overall data architecture, data migration planning, data synchronization)

f. Systems migration and transition planning (develop transition and migration plan)

g. Systems security engineering (design systems security consistent with approved policies, procedures, and facilities)

h. Technology insertion and pre-production environment (engineer inclusion of advanced technologies)

i. Facility planning and engineering (design and develop all facilities)

j. Integrated logistics support (design and develop logistics support)

1.1.2.2 Special Studies System engineering activities performed to evaluate or investigate alternative options for future execution.

Includes, for example:

a. Assessment of advanced technologies for future incorporation into the system

b. Evaluation of alternatives to solve a capability shortfall or system deficiency

Excludes, for example:

a. Development and incorporation of advanced technologies into the system

Includes, for example:

a. Developmental Test and Evaluation associated with the system

b. Operational Test and Evaluation associated with the system

c. System Wide Testing performed with all relevant program and system components.

c. If IV&V cannot be captured separately, please capture it here

1.1.3.2 Independent Verification and Validation (IV&V) Independent planning, support, and testing of a system to ensure that it meets all stated performance requirements, processes and procedures. This work is performed by an independent team not involved in the development effort.

Includes, for example:

a. Program level support and personnel doing the IV&V work

Includes, for example:

Travel associated with the following activities:

a. Program Management

b. Deployment

c. Engineering

d. Operations and Maintenance

e. Training travel for trainees (applicable to program)

Excludes, for example:

a. Trainer travel (captured in section related to Training)

Includes, for example:

a. The cost of developing and/or procuring the appropriate tutorial programs, training tapes, aids, services, and equipment that trainers use to facilitate instruction to program personnel

b. The resources and services expended to structure and develop the training class

Excludes, for example:

a. Any effort associated with actually executing training

1.2.2 Training Execution Training for managers, operators, maintainers, and support personnel.

Includes, for example:

a. Student materials (binders, handouts, etc.…)

b. Training equipment and devices

c. Instructors

d. Instructor travel

e. Training time f: Train the Trainer g: Training site fees

Includes, for example:

a. The integration of multiple custom software configuration items

1.3.2 Custom SW Development Source Code Development of source code for a specific block/spiral/release.

Includes, for example:

a. Writing the actual source code and conducting unit level testing of that code as part of the programming process

b. Software components, consisting of the source code/applications that satisfy an end use function

1.3.2.1 Custom SW Source Code SEIT Analysis of preliminary software requirements for source code.

Derive and map out software design specifications for source code.

Analysis of preliminary interface design specifications for source code.

Integration and test verification and validation of the source code.

Includes for example:

a. generating input to software test plans, descriptions, and procedures

b. defining software test cases

c. performing software build and test

Excludes, for example:

a. System level IV&V

1.3.2.2 Custom SW Source Code Development (CSCI 1...n; Specify) and Unit Test Development through unit testing of source code by CSCI 1…n.

Note: A Computer Software Configuration Item (CSCI) is an aggregation of software that satisfies a function and is designated for separate configuration management by the acquirer.

1.3.3 Custom SW Development Glue/Wrapper Code Development of glue/wrapper code for a specific block/spiral/release.

Glue/wrapper code is defined as any code that ensures proper interface and operation of COTS, GOTS and Custom SW applications.

Includes, for example:

a. Writing the actual glue/wrapper code and conducting unit testing of that glue/wrapper code

1.3.3.1 Custom SW Glue/Wrapper Code SEIT Analysis of preliminary software requirements for glue/wrapper code.

Derive and map out software/database design specifications for glue/wrapper code.

Analysis of preliminary interface design specifications for glue/wrapper code.

Integration and test verification and validation of the glue/wrapper code.

Includes for example:

a. generating input to software test plans, descriptions, and procedures

b. defining software test cases

c. performing software build and test

Excludes, for example:

a. System level IV&V

Includes, for example:

a. Creation and modification of database tables and queries

1.3.4.1 Custom SW Database Development Code SEIT Analysis of preliminary software/database requirements for Database Development code.

Derive and map out software/database design specifications for Database Development code.

Analysis of preliminary interface design specifications for Database Development code.

Integration and test verification and validation of the Database Development code.

Includes for example:

a. generating input to software test plans, descriptions, and procedures

b. defining software test cases

c. performing software build and test

Excludes, for example:

a. System level IV&V

Includes for example:

a. Software and Database code maintenance activities

b. Database administrative activities

c. DR work off post deployment to Ops

1.3.5.1 Custom Software Maintenance Maintenance of existing software code. Effort shall include support of custom and glue/wrapper code.

Includes for example:

a. DR work off post deployment to Ops

1.3.5.2 Custom Database Maintenance and Administration Maintenance of existing database manipulation and administrative activities.

Includes, for example:

a. Maintenance of software code specifically for querying records from a database

b. Maintenance of software code specifically for putting records into a database

c. Database administrative activities

d. DR work off post deployment to Ops

Excludes, for example:

a. Maintenance of existing software code that does not involve database manipulation

Includes, for example:

a. The integration of multiple custom hardware configuration items

Includes, for example:

a. Maintenance of FPGAs and ASICs

b. Residing FPGA and ASICs firmware

1.4.4 Custom HW Recapitalization Sites 1…n (Specify) The periodic replacement of equipment to ensure continued reliability of equipment and/or improved speed and capacity by site.

Includes, for example:

a. Procuring hardware to replace equipment that has experienced normal wear and tear or become technologically obsolete

Excludes, for example:

a. Procurement for new capability

Describes the purchase of SW and HW products that are standard manufactured products rather than customized products. Furthermore, COTS can be defined as commercial items, including services, available in the commercial marketplace.

GOTS (Government Off the Shelf):

SW and HW government products that are ready to use and which were created and are owned by the government. Typically GOTS are developed by the technical staff of the government agency for which it is created, or readily available.

FOSS (Free and Open Source Software):

Open-source software is computer software whose source code is available under a copyright license that permits users to study, change, and improve the software, and to redistribute it in modified or unmodified form.

Includes, for example:

a. Subsystem SW/IT IandT management

b. Requirements definition, planning and scheduling (i.e.: Engineering Bill Of Materials)

c. Development of test plans and procedures

d. Test preparations, conduct and teardown

e. Review, analysis and documentation of test results

f. Support for the integration and testing provided by the producer/integrator of the SW/HW

g. IandT resources specifically related to and limited to COTS/GOTS SW/HW

h. Resources necessary to integrate and test the Subsystem SW/HW components

1.5.2 COTS/GOTS SW COTS/GOTS SW purchases related to initial procurement, maintenance, and managed services. These should be separable from the COTS/GOTS/Custom HW and the Custom SW.

Includes, for example:

a. Licenses and administrative COTS/GOTS packages, etc.

Excludes, for example:

a. Interface code used to integrate COTS SW into the existing software baseline (captured under glue code CES item)

1.5.2.1 COTS SW COTS SW purchases related to initial procurement, maintenance, and managed services.

Includes, for example:

a. Licenses and administrative COTS packages, etc.

Excludes, for example:

a. Interface code used to integrate COTS SW into the existing software baseline (captured under glue code WBS item)

Includes the following:

a. Installation of recurring patches (Preventative Maintenance)

b. Purchase of new software as needed to perform these maintenance activities

c. Corrective maintenance actions beyond the capabilities of the maintainer which will restore systems to operations

Includes, for example:

a. Licenses and administrative GOTS packages, etc.

Excludes, for example:

a. Interface code used to integrate GOTS SW into the existing software baseline (captured under glue code WBS item)

Includes the following:

a. Installation of recurring patches (Preventative Maintenance)

b. Purchase of new software as needed to perform these maintenance activities

c. Corrective maintenance actions beyond the capabilities of the maintainer which will restore systems to operations

Includes the following:

a. Purchase of parts and spares as needed to perform these maintenance activities

b. Efforts that detect and troubleshoot anomalies through coordinated operations and maintenance efforts

c. Preventative/Corrective maintenance actions