FY98 Army Military Space RDDS
0208010A Joint Tactical Communications Program (TRI-TAC)
A. Mission Description and Budget Item Justification: A requirement exists to automate Signal Corps unit's capability to manage multiple tactical communications
systems in support of battlefield operations. The Integrated System Control (ISYSCON) facility will provide automated, integrated management of the tactical
communications network, establish an interface with each technical control facility in the Army Tactical Command and Control System (ATCCS) architecture, and enable
automation assisted configuration and management of a dynamic battlefield. ISYSCON is being developed in an evolutionary manner with incremental software releases.
A change to the requirements document has added planning and management of satellite resources as a requirement. The ISYSCON has been selected as the baseline for
network management system for joint task force use. The Battlefield Spectrum Management (BSM) software has been designated as part of the migration system for DOD
use. The work efforts in FY 1996 - FY 1999 support the development of the first three software releases (P0, IOT&E & P2, P3), the fabrication of Low Rate Initial
Production (LRIP) prototype, support for an IOT&E, and initiation of Nodal Management, Automatic Network Management and work efforts for follow-on software
releases. This program element also supports any development required for PM, Joint Tactical Area Communications System ( JTACS) Area Common User Systems
(ACUS). This program is assigned to Budget Activity 7 since it includes those development projects, in support of a development acquisition program or upgrades, still in
engineering and manufacturing development but which have received approval for production through DAB or other action, or production funds have been included in the
DOD budget submission for the budget or subsequent fiscal year. The ISYSCON Program serves as a baseline foundation to support future network management initiatives
tied to and part of the evolution to the Digitized Division and the WIN Architecture.
Acquisition Strategy: The acquisition strategy for the development phase was to competitively award an Engineering Manufacturing Development phase contract (awarded
Sep 92). A Milestone III Decision for the Full Production Phase is scheduled for FY 98 following a successful IOT&E in 4QFY97.
FY 1996 Accomplishments:
| |
1046 |
Initiated systems design for IOT&E software baseline |
| |
523 |
System integration test (P0) |
| |
2616 |
Completed detail design and conducted Developmental Progress Review (DPR) |
| |
3100 |
Task Force XXI |
| |
600 |
Completed BSM Version 4.0 |
| |
3178 |
Began code, unit test, and system test of the IOT&E software baseline |
| |
584 |
Delivered draft training materiel |
| |
500 |
CDR for hardware prototypes |
| |
500 |
Developed and deliver draft tech pubs |
| Total |
12647 |
|
FY 1997 Planned Program:
| |
5200 |
Participation in the Army Warfighter Experiment (AWE) Exercise |
| |
1543 |
Conduct DPR for IOT&E baseline |
| |
2489 |
Complete systems design for IOT&E software baseline |
| |
1869 |
IOT&E training/testing support |
| |
2043 |
Initiate systems design for Phase 2 (P2) baseline |
| |
3368 |
Code, unit test, system test for P2 baseline |
| |
1272 |
Continue systems design for P2 baseline |
| |
445 |
Small Business Innovative Research/Small Business Technology Transfer (SBIR/STTR) |
| Total |
18229 |
|
FY 1998 Planned Program:
| |
506 |
Conduct DPR for P2 baseline |
| |
2160 |
Conduct code, unit test, system test for P2 baseline |
| |
3173 |
Complete systems design for P2 baseline |
| |
1155 |
P2 software release |
|
1989 |
Conduct Follow-On Test & Evaluation (FOT&E) for P2 |
| Total |
8983 |
|
FY 1999 Planned Program:
| |
2462 |
Continue systems design for P3 baseline |
| |
3187 |
Code, unit test, system test for P3 baseline |
| |
996 |
Conduct DPR for P3 baseline |
| |
1171 |
Complete systems design for P3 |
| |
1000 |
P3 software release |
| |
1125 |
Support Limited User Test (LUT) |
| Total |
9941 |
|
B. Project Change Summary |
FY 1996 |
FY 1997 |
FY 1998 |
FY 1999 |
| FY 1997 President's Budget |
12972 |
18693 |
9409 |
10420 |
| Appropriated Value |
13368 |
18229 |
|
|
| Adjustments to Appropriated Value |
-721 |
|
|
|
| FY 1998 Pres Bud Request |
12647 |
18229 |
8983 |
9941 |
| C. Other Program Funding Summary |
FY 1996 |
FY 1997 |
FY 1998 |
FY 1999 |
FY 2000 |
FY 2001 |
FY 2002 |
FY 2003 |
To Comp |
Total Cost |
| Other Procurement, Army-2, BX0007 |
12766 |
9821 |
10645 |
10539 |
4174 |
0 |
0 |
0 |
|
47945 |
| D. Schedule Profile |
FY 1996 |
FY 1997 |
FY 1998 |
FY 1999 |
|
1 |
2 |
3 |
4 |
1 |
2 |
3 |
4 |
1 |
2 |
3 |
4 |
1 |
2 |
3 |
4 |
| P0 Software |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| PDR |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| CDR |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| IOT&E Software |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DPR |
*X |
|
|
*X |
|
|
|
|
|
|
|
|
|
|
|
|
| IOT&E |
|
|
|
|
|
|
|
X |
|
|
|
|
|
|
|
|
| P2 Software |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DPR |
|
|
|
|
|
X |
|
X |
|
|
|
|
|
|
|
|
| FOT&E |
|
|
|
|
|
|
|
|
|
|
|
X |
|
|
|
|
| P3 Software |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DPR |
|
|
|
|
|
|
|
|
|
X |
|
X |
|
|
|
|
| LUT |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
X |
|
| P4 Software |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| DPR |
|
|
|
|
|
|
|
|
|
|
|
|
|
X |
|
X |
*Milestone Completed
| A. Project Cost Breakdown |
FY 1996 |
FY 1997 |
FY 1998 |
FY 1999 |
| Software Development (Contractor) |
10784 |
16221 |
7251 |
8124 |
| Contractor Engineering Support |
567 |
439 |
571 |
584 |
| Government Engineering Support |
1000 |
923 |
876 |
955 |
| Program Management Support |
296 |
201 |
285 |
278 |
| SBIR/STTR |
|
445 |
|
|
| Total |
12647 |
18229 |
8983 |
9941 |
B. Budget Acquisition History and Planning Information: Not applicable.