Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 1 of 4 PageID #: 16238
`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 1 of 4 PageID #: 16238
`
`
`
`
`
`EXHIBIT 4
`
`
`
`
`
`EXHIBIT 4
`
`
`
`
`
`
`

`

`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 2 of 4 PageID #: 16239
`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 2 of 4 PageID #: 16239
`
`1.1.
`
`KEY ACCOMPLISHMENTS
`
`A. Task Force XXI AWE. Completed all activities at NTC, including the de-install of the
`Applique equipment from the 1-5 Btn.
`
`B. Program Planning. Provided technical, cost, and schedule estimates for various
`alternatives and excursions (for example, adding a late 1998 or early 1999 NTC
`rotation to the program plan, adding a Limited User Test [LUT] to the program plan,
`moving the FDT&E fi'om 1998 2’ system Version 2 to 1999 2’ system Version 3, etc.)
`to PM Applique upon request, for their use in refining the program plan for the next
`several years in light of the results of the TF XX] AWE, and emerging Army decisions
`regarding the future of the FBCBZ program.
`
`C. Lessons-Learned. Completed initial Cut at developing “lessons-learned” fi'om system
`version 1 and the TF XXI AWE. Eighty-five (85) specific technical improvements to
`the system were identified, and tentatively scheduled into future releases of the FBCB2
`system (although these have not yet been finalized with PM Applique, and some
`adjustments and additions may still be made to this list). More than fifty (50) of these
`are now scheduled to be incorporated into the Version 2 system to be brought to the
`FBC B2 test milestone (FDT&E or LUT) in 1998; these are over-and-above
`previously-planned capabilities for FBCB2 Version 2.
`
`D. Tactical Interth. Made substantial progress on the design of the “next-generation”
`Tactical lnterNet, including coordination with other “stake-holders” in the Tactical
`lnterNet process. Specific activities include:
`
`1. Continued video teleconferences on Tactical lntemet (T1) implementation topics
`with participation from PM Applique, PM TRCS, PM JTACS, CECOM, ITT,
`
`HAC, TRW, and others. These meetings, which are held approximately every two
`weeks, provide a forum for discussionfiresolution of technical issues related to the
`TI. Examples of topics discussed to date include mini-router concept, approach to
`network lnonjtoringhnanagement, and emerging results from data analysis.
`
`2. Reached agreement among the TI “stake-holder” group (PM Applique, PM TRCS,
`CECOM RDEC, PEO C3s, ITT, HAC, TRW, and others) on key elements of the
`design and functionality of the T1 for the 1998 FBC B2 LUT (FBCBZ system
`Version 2). Functionality and top-level design for the key Tl threads (unicast,
`broadcast, and multicast) have been agreed to, with a small number of topics for
`further discussion identified, and a process and time-frame for reaching closure
`agreed to. A concept for the schedule to reach the 1998 test milestone (a LUT in
`August 1998 at Ft. Hood) has also been agreed to, with topics requiring further
`coordination identified and a process and time-frame for reaching closure agreed
`
`SIEGEL000789
`
`

`

`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 3 of 4 PageID #: 16240
`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 3 of 4 PageID #: 16240
`
`D24518-003A
`
`13 May 1997
`
`3. Prepared original draft of the FBCB2 Performance Description Document
`(FPDD). This document will be used in place of the Applique Performance
`
`Description Document for documenting the analysis and results of performance
`related issues. This document will be released to the government in early May.
`
`4. Prepared and internally coordinated an updated outline for the FBCB2 Interface
`Control Document (C DRL BOOS).
`
`D. Communications Studies and Analyses
`
`1. Continued planning process to identify, establish, prioritize and schedule critical
`systems engineering studies needed to support hardware and software design
`activities. Studies include expanded Situational Awareness (Friendly, Enemy and
`Sensor data) dissemination and correlation, Sealeability, Reliable Delivery of C2
`
`messages and server implementation and distribution schemes and security.
`
`2.
`
`Initiated decomposition of Technical Performance Measures to support subsystem
`performance requirement definition.
`
`3. Coordinated Operational Architecture activities with Ed McCarthy (Mitre) to
`ensure the products of the our analyses can be fed into the Operational
`Architecture database.
`
`4. Coordinated Plans with the Signal Center to visit the to visit Army Schools in
`support of the Operational Architecture analyses (FIO). A project coordination
`meeting will be held in early May to make sure project (software, hardware, ILS,
`communications) information requirements are identified.
`
`Presented the evolving FBCBZ Security concepts and requirements to the project
`staff
`
`U1
`
`1.
`
`2. Developing plan to evaluated Mil—3 (OPNET) OSPF module. Plans are to
`determine feasibility of using this module to suppon dynamic routing in the
`DBCM.
`
`3. Documented and distributed for review the SE review, the results of analyses used
`to determine performance requirements in support of ADOC and SESDD. These
`
`results were incorporated into the F PDD which is scheduled to be delivered to the
`Government in Early May.
`
`SIEGEL000794
`
`

`

`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 4 of 4 PageID #: 16241
`Case 2:17-cv-00513-JRG Document 257-4 Filed 01/04/19 Page 4 of 4 PageID #: 16241
`
`D24518-003A
`
`13 May 199?
`
`F.
`
`Interfacesllntcroperability
`
`1. BCIS European demonstration (T&M). Installed Applique Version [.02 software
`and map data onto the PND computers. Collected and shipped equipment to
`Germany in preparation for end of May activity.
`
`CBDCOM (T&M). Successfiilly completed field integration of Applique software
`Version l.0.2b with C BDCOM patch with the CP LR-BSDS during the week of 7
`
`April. Prior exchange of VMF message bit streams greatly reduced the integration
`time. A minor problem was discovered and fixed where the serial HF baud rate
`was set for 9600 bps instead of 4800 bps specified in the ICD. All 5 DSSU
`computers were configured with the final release of 1.0.2b with CBDCOM patch
`and shipped to three different locations (2 to Aberdeen, MA 2 to Orlando, FL and
`l to MICAD contractor in Glendale, CA). MICAD integration was proposed as a
`separate task option due to its schedule. Additional fiJnds were received to
`support this integration effort which is schedule for JulyfAugust [997. This effort
`will produce a new software Version 1.0.20 that incorporate fixes discovered
`during the integration process with MICAD.
`
`G. RFPI. Submitted an early (rough) release of RFPI address book assignments to
`
`Applique URNs. Supported numerous questions following release of this data.
`
`1. Completed update to Applique database to include 70 new Tactical Unit Names
`mapped against existing URNs used during TF XXI. Suecessfitlly integrated patch
`floppies with Applique software Version 1.0.2a including all patches up to patch
`#13. Modified SA server assignments to ensure proper SA dissemination.
`
`Began on—site support at Ft. Benning, GA and Huntsville, AL starting 21 April to
`begin integration of RFPI patch with LDTOC, MODS AF, and DCZ equipment.
`Patch was fully installed and tested in 2 days. Subsequent efforts focused on inter-
`site communication using DIS network, the injection of MODSAF VMF position
`reports for virtual units, and DC2 interface with ABCS. Discovered that
`MODSAF was changing the source URN of each position report to match the
`
`URN of the unit that was being reported. Previous discussions assumed that
`MODSAF would be injected the same as JANUS data (fi'om a single URN with a
`role code of 480). MODSAF was changed to act the same as JANUS.
`
`2.1.2. Major difficulties encountered, and plans to overcome those difficulties
`
`None
`
`SIEGEL000795
`
`