AFSCI21-101 — Test Program Set

AFSCI21-101 governs the management, funding, execution, and reporting of Test Program Software maintenance engineering projects.

Search AFSCI21-101

  • Publication number: AFSCI21-101
  • Title: TEST PROGRAM SET
  • Date: 2025-04-03

View AFSCI21-101 on armypubs.army.mil

AFSCI21-101 covers TPS requirements, software deficiencies, project submissions, execution-year activities, budgeting, funding allocation, closeout, and support systems. It requires project development, review, approval, documentation, tracking, status reporting, and closeout actions.

Topics covered

  • Test Program Software requirements
  • Software deficiencies
  • Project submission requirements
  • Execution-year workload
  • Budgeting information
  • Funding allocation
  • Project closeout
  • Support systems

Questions and answers

When must TPS software maintenance projects be submitted?

Projects shall be developed, input, reviewed, signed and submitted to Strategic Sourcing Program before EOM February for organic and by 15 March for contract TPS. (paragraph 5)

What happens if project requirements are not entered or documented properly?

Project requirements not entered in their entirety or documented properly within MP&E, MPST, and/or any other applicable system database; will result in project disapproval. (paragraph 5)

How quickly is an out-of-cycle project’s validation status determined?

Validation status of OoC shall be determined by Strategic Sourcing Program within 15 working days of project submission. (paragraph 5)

When must CSAG-S funds for TPS be obligated?

All CSAG-S funds for TPS must be obligated within the year of execution. (paragraph 8)

What is required to realign funding between validated projects?

Sites must request authorization from Strategic Sourcing Program to realign funding between validated projects during the year of execution to meet mission requirements and schedules as they are identified. (paragraph 8)

Ask Reggie.Bot a question about AFSCI21-101