Case 2:17-cv-00513-JRG Document 233-5 Filed 12/14/18 Page 1 of 3 PageID #: 14011
`Case 2:17-cv-00513-JRG Document 233-5 Filed 12/14/18 Page 1 of 3 PageID #: 14011
`
`(cid:0) (cid:0) (cid:0)
`
`EXHIBIT D
`  (cid:0)(cid:0)
`
`(cid:0)
`
`(cid:0)
`
`

`

`Case 2:17-cv-00513-JRG Document 233-5 Filed 12/14/18 Page 2 of 3 PageID #: 14012
`Case 2:17-cv-00513-JRG Document 233-5 Filed 12/14/18 Page 2 of 3 PagelD #: 14012
`
`D245 l8—003A
`
`13 May 1997
`
`b)
`
`Prepared original draft of the FBCBZ 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.
`
`Prepared and internally coordinated an updated outline for the FBCBZ Interface
`Control Document (CDRL B005).
`
`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, Scaleability, Reliable Delivery of C2
`messages and server implementation and distribution schemes and security.
`
`Initiated decomposition of Technical Performance Measures to support subsystem
`performance requirement definition.
`
`Coordinated Operational Architecture activities with Ed McCarthy (Mitre) to
`ensure the products of the our analyses can be fed into the Operational
`Architecture database.
`
`Coordinated Plans with the Signal Center to visit the to visit Army Schools in
`support of the Operational Architecture analyses (F10). 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
`
`E. Modeling and Simulation
`
`1. Verifying DBCM enhancements to include Situational Awareness and
`Communications trade studies. Enhancements include support for dynamic server
`registration and C2 broadcast using EPLRS CSMA.
`
`Developing plan to evaluated Mil—3 (OPNET) OS PF module. Plans are to
`determine feasibility of using this module to support dynamic routing in the
`DBCM.
`
`Documented and distributed for review the SE review, the results of analyses used
`to determine performance requirements in support of ADOC and S/SDD. These
`results were incorporated into the FPDD which is scheduled to be delivered to the
`Government in Early May.
`
`SIEGEL000794
`
`

`

`Case 2:17-cv-00513-JRG Document 233-5 Filed 12/14/18 Page 3 of 3 PageID #: 14013
`Case 2:17-cv-00513-JRG Document 233-5 Filed 12/14/18 Page 3 of 3 PageID #: 14013
`
`D245 18-003A
`
`13 May 1997
`
`4.
`
`Started M&S coordination activities with Sal Barone (CECOM RDEC) to ensure
`SPM modeling activities are in sync with FBCBZ. Plans are being developed to
`conduct a Technical Interchange Meeting (TIM) during the week of 12 May to
`discuss details of algorithm changes needed to support dynamic SA client
`registration and C2 broadcast over CS MA.
`
`F.
`
`Interfaces/Interoperability
`
`l. BCIS European demonstration (T&M). Installed Applique Version 1.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). Successfully completed field integration of Applique software
`Version 1.0.2b with CBDCOM 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 I/F 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 funds were received to
`support this integration effort which is schedule for July/August 1997. This effort
`will produce a new software Version 1.0.2c 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. Successfully 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, MODSAF, 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 (from 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
`
`