Digitizing the Dirt

©1997 Marcus H. Sachs

Task Force XXI Advanced Warfighting Experiment

National Training Center Rotation 97-3

(These notes were submitted by MAJ Marcus H. Sachs, 4th Infantry Division Automation Officer, to the Functional Area 53 Listserver during the Task Force XXI Advanced Warfighting Experiment conducted at the National Training Center in Spring, 1997.)

TFXXI Day 0 (Wednesday), 19 Feb 1997

Tomorrow's the big day. I depart for a wonderful six plus weeks at the NTC. We've been pushing out soldiers for about two weeks now, and will continue through the end of the month. The first two trains (over 650 rail cars!!) have departed, with many more to follow. I'm going to try to post daily to the list as time permits, with a running play-by-play of what we're up to. I'll have to stay within limits of OPSEC, of course, but I'm sure there is plenty that I can discuss.

Today our CG gave the leaders our sendoff. His controlling idea: Kill the OPFOR! I reckon they are just a bit intimidated and somewhat nervous about what we might do to them. If there are any Krasnovians on this list, please jump right in! I'd love to hear your side of the story!

And now.... off to Digitize the Desert.

TFXXI Day 1 (Thursday), 20 Feb 1997

You get these funny looks from the OPFOR when you walk around here with a 4ID patch on. I think that the psychological attack has begun!

We got in last night and began the process. We'll be setting up TOCs and establishing ourselves for several days. Most of the rail cars come in next week. Within the next 10 days we will be in control of the NTC. Until then, it's unpacking, wiring, coordinating, fighting for real estate, normal stuff.

By the way, if you ever get to fly on a KC-10 refueler (our bird yesterday), ask to go see the boom room in the back. What an extraordinary view!! New Mexico and Arizona from 40,000 feet (looking straight down between your legs) is absolutely awesome. I guess that's one of the little things that makes being an Army Automator different from a Civilian Automator.

TFXXI Day 2 (Friday), 21 Feb 1997

First full day in the Desert is done. Trucks and equipment start arriving tomorrow. Today was filled with coordinating, scrounging, wheeling and dealing. We are setting up unclass reachback from Irwin to Hood for all of our installation LAN users. Seems as though it will work.

For those of you that have been here before, we are connecting the Rotational Headquarters to the installation backbone fiber via a line I'm going to run over 3rd street. Also, our Division TAC will be behind the Starwars building and will get its unclass LAN from the DOIM building. Other users on post will dial the local TSACS server for access back to Hood. A similar arrangement is being made for the TRADOC and FORSCOM personnel here. Interesting how this part of TFXXI will probably never make the history books, but it just as important in providing timely information to the senior decision makers.

TFXXI Day 3 (Saturday), 22 Feb 1997

The first two trainloads of equipment arrived today. We've got a total of 650 rail cars that will eventually arrive at Yermo. We hoped to get the Division TAC CP established before sundown, but there was some confusion in finding the floorboards and tents.

The 1st Infantry Division's Ft. Riley Brigade came out of the box on Saturday, very happy to be done with their rotation. Their soldiers and ours seem to be everywhere. Once they clear later this coming week, our troops will begin occupying the dust bowl. Until then, we are sandwiched into temporary holding areas.

Contractors are also starting to arrive. For those who have never experienced the NTC, it is a shock. Many are going to be living with the BCT in the box, and I'm willing to bet they are going through the same gut-wrenching thoughts as the soldiers are.

TFXXI Days 4 and 5 (Sunday/Monday), 23 & 24 Feb 1997

It got a bit busy this morning to sum up yesterday's events, so I'll cover both days in one note.

The highlight of Sunday's activities for me was getting the Division TAC CP set up. We started at sunup, and by the end of the day had most of the parts in place. We are still looking for some trailers and a conex. Can't put up the camo nets until we locate them. Oh, darn! :) The hunt will continue tomorrow (it's got to be somewhere here in all of this dust!)

Last night we established a VTC link between the TAC and the division conference room at Hood. This is via GTE's new highspeed MUX cards in the SENs. At the TAC there is a SEN with the HSMUX card installed. The SEN has an LOS shot to the NC sitting on Beacon Hill. The NC is connected to a SEN at Hood via a TACSAT shot. In the SEN at Hood is another HSMUX card, plus the RS449 cable from the SEN to the VTC system in the division HQ building. The circuit runs at 256kbs, and is in continuous operation. The link between the SENs and the NC is 512kbs (normal 256kbs DTG plus the 256kbs VTC circuit). The 256kbs VTC circuit is channel reassigned in the NC to connect the two SENs. Pretty cool stuff.

The 1BCT has been testing their vehicles as they arrive from the Yermo rail yards. So far all but a few of the Appliqué and other systems are coming up and working on the first try. We'll have the EPLRS nets up shortly, and by the end of the week will have the nucleus of the tactical internet well established.

Control of the rotation will be via the normal 52d Mech headquarters in the Starwars building. The 4ID TAC will track the battle, but will not direct it. The ATCCS LAN for the 52d Mech should be up by the end of the week. We started installing parts of it today, ditto for the ATCCS LAN in the TAC. Both will be joined together via CISCO routers and TPAs to the MSE TPN backbone.

As for my unclass LANs that will connect back to Hood, we got some of the fiber installed today and I hope to finish it tomorrow. The DOIM has been very cooperative (as has everybody here) in getting us what we need when we need it. I've also been tasked to install a (yet another) VTC system for our CG to use at his desk in the rotational HQ. This system will ride the TRADOC circuit that they are so graciously sharing with us. It's wonderful when the techno-bureaucrats all work together to solve these problems. I must say that I've never been in a situation where everybody is bending over backwards to help everybody else. It's almost too perfect.

So, off to my bunk in the circus tent. At least we got carpets today, so no more dirt floors. Moving up in the world.

TFXXI Day 6 (Tuesday), 25 Feb 1997

We got the NIPRNET connection working into the TAC today. It's a fiber link between a hub in the G6 area and a hub inside the DOIM building. Total fiber length is about 500 feet. We ran out the TAC, over a pair of towers to avoid a road, and into the DOIM building. At each end of the fiber is a media converter that allows us to bridge between the two 10bT hubs. Tomorrow we will extend this network, again via fiber, from the TAC to the rotational headquarters building area (about a quarter mile). We'll make use of a fiber segment put in by the ops group to support the TPN that we will not need for this rotation. If you've been a SIGO here recently, you know which cable I'm talking about. This NIPRNET connection allows me to put all of my division staff onto an unclass network that is linked to Ft. Hood so that they can do their email, reach our file servers, etc. We DHCP an IP address, but we use our WINS servers at Hood to validate us as Hood NT domain members. TRADOC has a similar arrangement set up for their people.

The 1BCT continues to receive vehicles and test their Appliqué equipment. They will move out into the box next week, where they will stay until the end of the month. The number of soldiers here from 4ID grows by several hundred each day.

Tomorrow we plan to finish installing the ATCCS LAN in the TAC, and to get the ATCCS LAN in the Starwars building up. The expected endstate is both LANs up and running by the end of the day so that we can begin training the ops group members on ATCCS.

TFXXI Day 7 (Wednesday), 26 Feb 1997

One thing that went great today was the weather! Mid 70s, slight breeze, lots of sunshine. Good view of the mountains and the beautiful NTC. Gotta love it.

Today's focus was trying to figure out who expected cables to be run from the Starwars building to the TAC area. There are six 20' towers in place between the building and the TAC so that we don't have to dig trenches. We've got well over a dozen different cables strung, and I'm sure there are plenty more to go. I got stuck with honchoing the TAC end, a Signal Corps CPT in the ops group got the Starwars end.

Towards the end of the day we fired up the ATCCS LAN in the TAC. All but a couple of machines came up on the first try. Looks like we have a couple of crusty connections to fix. We also figured out today that we need to connect the ATCCS LAN in the Starwars building with the ATCCS LAN in the TAC via 10Mb ethernet. The designed connectivity was via the TPN (16kbs) but that's too slow for the amount of data we will run. Since we have BGP-4 available to us, we can "short-circuit" the path between the two TOCs with ethernet and provide a faster path. Keep in mind that all of our TOCs are router based, with the packet switched TPN providing the WAN connectivity between the TOCs.

Enough for now.

TFXXI Day 8 (Thursday), 27 Feb 1997

It's interesting to note the unintended effect these daily summaries have had. My intention was to keep my fellow automators informed on what is going on here. Many of you have chosen to hit the forward button and send these notes off to places where they are causing some consternation. So be it. It's an "unofficial list", right?

For those of you who are worried about me connecting the NIPRNET to the Tactical Internet, please don't. There's a big physical separation between my NIPRNET hub and my TI hub. And all of the computers on the NIPRNET here in the TAC are under my careful watch.

This day's activities centered on getting the STAMIS connectivity up for the DISCOM. They have a NES/CAISI system that normally has a SEN to support it. This time they don't, so we came up with a way to use a CISCO router and a TPA to bridge the 1000ft gap between their site and the nearest SEN. Most of what I'm involved in is situations like this. Plans change from the way it was designed at Hood, and we have to adjust to fit.

One thing to keep in mind as you read these notes. I'm only one of several thousand people here. I can only report on things that I see or hear about. There are lots of things going on that I am unaware of, and I would ask that any folks here at the NTC on this list also start posting some observations.

So much for yesterday's great weather. The wind was howling today! Lot's of grit and dust in your teeth and down your shirt (and in the computers!)

TFXXI Day 9 (Friday), 28 Feb 1997

The 1BCT moved over to the dust bowl yesterday from a temporary holding area. Today they built their TOC, and began standing up their ATCCS LAN. Ours in the TAC is up, as is the one in the 52nd Mech TOC in the Starwars building. Tomorrow we will start doing connectivity testing between the three TOCs, as well as the support facility and help desk.

I overheard an interesting story this morning while standing in the chow line. Yesterday was quite windy, and there were the normal dust storms that kick up in the box on such days. A couple of soldiers were caught in one near a geographic feature known as The Whale. Fortunately, their Appliqué was on, and they had no trouble navigating through the blinding dust. I guess that's the Army's new version of IFR (Instrument Fighting Rules)! ;)

This afternoon we planned to use our cool VTC system to let our soldiers in the TAC talk to their spouses and kids back at Hood. As luck would have it, it was working great until about a half hour before showtime. Then a radio in the SEN here at the TAC died, and with it died the video link. Oh, well. We the automators and signaleers have our tails between our legs for a while and are the brunt of some interesting jokes this evening.

Off to do my laundry. That's low tech. It should work.

TFXXI Day 10 (Saturday), 1 Mar 1997

I've been here just a bit over a week, and in that time we've established the Division TAC CP, the Division Main (ala the 52nd Mech in the Starwars Bldg), the TAFs (also in the SW Bldg), the CTSF (tech support), the 124th Sig Bn SYSCON, and part of the 1BCT TOC. The Div TAC is adjacent to the SW Bldg, the CTSF is in the southeast corner of main post in the IMMC area, and 1BCT is in the dust bowl. SYSCON in on top of Beacon Hill. By this time next week we should have all of the TF TOCs up, with full ATCCS and Appliqué connectivity. Lot's of work to do, eh? We also have the challenge of training the ops group personnel next week on running ATCCS software.

The TOC LANs are connected via X.25 connections into the local SEN, then over the TPN as a wide area network. We use BGP4 as our WAN routing protocol and OSPF within the TOCs. Today I was trying to figure out why my Div TAC LAN (that's TAC LAN, not TACLAN; big difference) would not talk to the LAN in the SW building. Turns out that both LANs were connected to the TPN but we were pointing at different neighbors for BGP routing (actually, the problem was a bit more involved than that, but I don't want to air any dirty laundry). Well, we worked that out late this afternoon and it looks like we are doing better now.

Irwin continues to expand and wheeze as more soldiers and equipment pour into it. We are putting a big strain on the facilities here but so far nothing has busted. As the last soldiers of 1ID disappear out the main gate, we are backfilling their buildings and areas in the dust bowl. Even AAFES has gotten into the spirit here, offering quite an assortment of Force XXI items such as T-shirts, coffee mugs, backpacks, Zippo lighters, and hats. We couldn't get that stuff at Hood, so I guess the saying "been there, done that, got the T-shirt" will really apply to this rotation!

TFXXI day 11 (Sunday), 2 Mar 1997

Another pretty day in the desert today. Lots of sunshine, and the dust is still a bit damp from the rain we had two days ago. I'm sure that by tomorrow it will be kicking up again.

The 1BCT and the TF TOCs were set up today in the dust bowl. They have connectivity with each other via the SINCGARS/EPLRS/SDR nets. We are still working to get the brigade TOC up on the TPN. There are problems with BGP routing that we are hammering through. It should be worked out by tomorrow.

The Appliqué nets are working well. From here at the Div TAC we can see three big blobs of blue icons, one at the dust bowl, one at the motor pool on Langford Lake Road, and one near the TAC/Starwars. You can watch the Appliqué equipped vehicles as they drive around main post. In the TAC we have three 37" monitors connected to a video switch. We can view the outputs of each of the ATCCS systems in the TAC, plus UAV video, CNN/Weather Channel, VTCs (ATM and HSMUX), etc. Right now we have CNN on the left, a view of the Division Conference Room at Hood in the middle (via the MSE mux cards), and Appliqué on the right. Not bad. Good situational awareness.

We extended the garrison LAN from the TAC to the rotational headquarters (bldg 480) late today. That gives our command group the same reachback to Ft. Hood via the NIPRNET as we have in the TAC. The connection is via fiber and RG-58, and works quite well. Tomorrow we build yet another VTC system, but this one will run via a commercial ISDN circuit, not over MSE.

As for the conveniences of life, we moved out of the circus tent into buildings last night. It was nice to sleep under a roof again.

TFXXI Day 12 (Monday), 3 Mar 1997

We now have LAN connectivity between all of the operational TOCs. 1BCT popped in today when we got their BGP neighbors updated. In the original design, we were using T20s in the Node Centers to receive BGP neighbor updates from all of the routers connected to the TPN. Unfortunately there is a bug in the T20 software that was causing routes to be dropped from the TOC CISCOs, and hence, lost connectivity to the TOCs. A workaround was developed to use two CISCOs as "surrogate T20's", one in the CTSF (tech support) and one at the SYSCON. We will add one more tomorrow at the 1BCT TOC.

The CTSF is operating a prototype Network Operations Center (NOC) that is experimenting with various ways to monitor the TOC LANs and the Tactical Internet in general. The SYSCON still controls the network, the NOC provides an additional set of eyes to locate and solve network problems. Hopefully the systems and tools that we learn and develop from the NOC will become part of ISYSCON. We also will document the role of the NOC and will propose some new doctrine for its use. We can no longer treat TOC LANs as "user owned and operated". The health of these networks are too important to the success of the battlefield commander. This implies a new level of training and manning, and we plan to pass along the lessons learned out here on what this level will be.

TFXXI Day 13 (Tuesday), 4 Mar 1997

More parts continue to come together. The TOC LANs are talking fairly well now. We began the process of training the ops group personnel in the Div Main (52nd Mech) on ATCCS today. Also built part of the LAN for the Division Plans cell that will join us next week.

The special ops folks got their TOC established yesterday, and came to us today for connectivity. They have their ATCCS boxes, but were lacking a router. We'll get that squared away tomorrow. Details, details.

I can't go far into the next comment, but suffice to say that we are still working issues with some organizations that want to tie their TFXXI LANs to other sites off Ft. Irwin. The network here is closed, for many reasons including security of what we are doing. It is interesting to watch these organizations' reactions when they are told that what they concocted in a lab may not be able to be done here because they did not do their homework.

I received several emails and phone calls today on the NOC that I mentioned yesterday. Just for the sake of completeness, the NOC is being operated by a team from Mitre Corp., the organization that designed the router-based backbone that makes the ATCCS LANs and the Tactical Internet come together. They are using three main software tools, TKINED (from the Technical University of Braunschweig, Germany), What's Up (Ipswitch, Inc.), and SNMPc (Castle Rock Computing) to measure the health of the network. They also got some SNMP code from Carnegie Mellon University that they modified to allow them to sample and compare routing tables in the CISCOs. Eventually, a summary of this information will be available on a web server they have established on the tactical internet. Using Netscape 2.01 or higher, we will get real-time updates of the network health down to the TOC LAN Managers (74Bs that operate the TOC LANs) and to the SYSCON. Since there is so much interest in this, I'll keep the list updated on what comes of it. We have also discussed using the PointCast and/or Microsoft Information Server software as an enhancement to the web site for pushing network status. If this method works, I'm going to experiment (at Hood after the AWE) with doing the same for sitreps, intsums, fragos, etc. (BTW, if you haven't seen PointCast, you should. Look at http://www.pointcast.com).

TFXXI Day 14 (Wednesday), 5 Mar 1997

More of the "same" today. Continuing to tweak the networks in the TOCs and the systems in the vehicles. The Brigade's recon troop, a tank company, and a mech company took off today to establish a forward presence in the box. One of the TFs will move their TOC out tomorrow, and the remainder follow on Friday. The wheels are in motion....

The NOC has their web server working. We can now see the health of the entire TFXXI network on one screen in Netscape. It's a green/red indication of the status of the routers and is automatically updated.

We got the SOCCE TOC integrated into the DivTAC. They were missing some parts that we had to scrounge up. They are happy now.

I'm going to get another device tomorrow. It's a tool that allows me to monitor our networks for intrusions. I'm not sure exactly how it works, but rest assured I let you know what I can (within security limits of course) in the days to come.

There were good comments on the list today about PointCast. Like one individual pointed out, my intent was not to have TI users receiving Internet traffic. I do think that this may be a technology that can be exploited for the next generation of ATCCS. I'd like to see some sort of information server tied into database warehouses making vast amounts of knowledge available to users anywhere on the battlefield. Whether PointCast or IIS is the specific software doesn't matter.

TF XXI Days 15 and 16 (Thursday/Friday), 6/7 Mar 1997

Rather busy last night, and did not get to send off a daily summary. So here's the update for two days.

The pace is picking up, and the soldiers are quite excited about the next few weeks. The first TF TOC went out yesterday, followed by the other TFs and the Bde TOC today. Tonight, they all sit out in the box, ready to conduct further training on their systems. Over the next several days, we will stress the networks and comms systems to make sure that we are razor sharp to defeat and kill the OPFOR during the last two weeks of this month. You can feel the electricity in the air around here. The troops are chomping at the bit to be the first unit to ever whip the OPFOR. And many of us believe that they will do it.

I was talking to some of our intel folks today. There is a concurrent exercise going on over at Edwards AFB during the AWE. They are going to provide quite a bit of aerial imagery in real time to the BCT as they fight the OPFOR. This will truly be a different rotation. For the past several days we've been watching UAV feeds in the Div TAC. Unbelievable what you can see from those platforms. There is literally no way for the enemy to hide!

I got the network intrusion detector today. It's a UNIX box that listens to my network, and alerts on events that are suspicious (like repeated logins on a particular box as ROOT). It tells me if an event occurs and allows me to trap the datagrams for analysis. We ran SATAN against a machine and watched the NID trap the probes. It was very effective. There is a NID on the TF network and one on the SIPRNET-connected LAN in the ACE.

We actually have four independent networks up, the TF XXI (TPN and below) network that is running unclass and is not connected to the outside world; the NIPRNET network I built in the TAC and at the rotational HQ for email reachback to Hood; and the SIPRNET and JWICS networks in the ACE. It's a bit of a challenge to keep all four electrically separated from each other, but doable.

The web page at the NOC is working out quite well. They are only monitoring the routing status of one top-level router, and we will add in at least one and possibly two more. Right now, there is only a green/red status based on if the router in question is listed in the NOC's router tables. When we add the other two top-level routers, we can show a green/amber/red status. Once we get back from the NTC I'll put together some briefings explaining how all of this works.

TFXXI Day 17 (Saturday), 8 Mar 1997

The Appliqué picture in the Div TAC now shows two digitized task forces (1-22 Inf and 3-66 Armor) arrayed on either side of East Range Road in the central corridor, facing east, waiting to launch out to find and destroy the OPFOR. TF 1-5 Inf (light fighters) as well as the remainder of the BCT are also visible as blue icons on the map background. There are also Appliqué equipped vehicles on main post, and those that stop by the PX are just as visible to us in the TAC as those deep in the box. The UAV was up again today, providing an incredible live view of the desert below and the hundreds of tanks and vehicles.

The BCT is ready to go. We are in the shake out phase, the final week before we go forth and make NTC history by locating and killing the OPFOR before they can get out of their assembly areas. It promises to be a good fight. Tomorrow we do a commex, and by the end of the week we will be locked and cocked.

Generals Reimer and Hartzog came aboard this morning. If either of you gentlemen receive these notes, welcome to the NTC! Thanks for all that you have done to get us to where we are today! They spent the day out with the BCT. We expect over 1300 visitors in the next three weeks, and something like 200 various media organizations. A German and Danish TV film crew came through yesterday. Watch for my mug on European TV in the near future, talking on a DNVT while a contractor to my left is operating the network intrusion detector. ;)

For me the bulk of the day was spent working more NOC issues, trying to figure out if one of our subnets had outside connectivity (it did not), helping the G2 find a repeater for his SIPRNET LAN, troubleshooting the CG's VTC computer, and hooking up an Appliqué display for the CG in his mess tent, along with all of the normal nit-noid questions and little problems that crop up.

TFXXI Day 18 (Sunday), 9 Mar 1997

Good day of training today. We did a commex this morning with all of the information systems. Overall it was quite successful.

The BCT continued the company team lane training today. We are into the last few days before the force-on-force (the actual "experiment") begins. As I've said in the last few notes, the soldiers are really pumped up about this. They are ready to move on from this phase into the kill the OPFOR phase.

I was fortunate to be able to get out from the Div TAC and journey into the box to the BCT TOC. Quite an impressive setup. It was always good to see the folks at the Brigade doing their thing at Hood. Here as well they are really into this stuff. I had a friend of mine who works in the Pentagon (and will remain totally anonymous except to say that he is a 53 and a member of this list) along for the ride. This was his first time in the field since the very early 80's. His eyes were as round as a little kid's at Christmas. All he could do was grin and ask lots of questions. I told him that he needs to carefully put his boots into a bag in order to preserve the coating of NTC dust, then place those boots in his office in the Pentagon with a "been there, done that" sign to impress his friends. He said that he would consider it. I had to keep from giggling when he asked me what type of helicopter passed close overhead (it was a Blackhawk). I told him that he really needed to get out beyond the beltway more often! ;)

One good lesson that my soldiers learned today that needs to be passed on. When you are using WF-16 to connect TPAs to X.25 J-boxes, you need to restrip the wires every few days. It has been over two weeks since we set up the TAC, and this morning we were starting to show serious deterioration of the signal between our TPAs and the packet switches in the SENs. I forgot about learning that lesson at Bragg a few years ago when we were connecting the SIPRNET to the TPN. There we also had a WF-16 connection that was exposed to the elements and needed to be restripped every week or so. For the other TOCs, this is not an issue since they will jump frequently. Only at those TOCs that will sit still for nearly six weeks will we have this problem.

TFXXI Day 19 (Monday), 10 Mar 1997

This evening the brigade's scouts launched out to begin a movement to contact operation involving the entire BCT. This is the last of the shakeout exercises. After this current operation is over, the BCT will regroup, conduct final checks, reset databases, catch up on much-needed rest, and get prepared for this weekend's opening round. The next step is for the digital division operations order to be transmitted to the BCT staff, who will then create a digital brigade order. A digital order is transmitted via ATCCS systems, and includes text paragraphs supported by overlays and supporting graphics. Nice to be able to do away with paper.

Day 0 is on Saturday. The BCT will LD early Sunday morning. I don't know how well I will be able to keep up these daily updates once the fighting starts, but I will try.

We had some NTC-specific problems to work through today. As those of you know who have come through here, the ops group has organizations (TAFs) that monitor the activities of various elements of the rotational units, and collect massive amounts of data for use in AARs. Because of the unique way that our ATCCS boxes are connected with DCE cells, we had to engineer some changes to how the fire support computers (AFATDS) in the fire support TAF are connected to the Division TOC LAN in the Starwars building. I won't go into the gory details, but suffice to say it takes quite a bit of negotiations and patience on the parts of us (the 4ID), the network engineers that put all of this stuff together, and the NTC staff, to make even minor adjustments to the LAN architectures. It was a delicate dance of egotistical elephants, and it did work out in the end.

We experienced one additional physical problem with the X.25 ports into the SENs. After cleaning all of the wires and their binding posts in the J-boxes, we still had a rough connection into the TPN. As it turns out, the cable connection into the side of the SEN wasn't seated properly. Once we cleaned it up and got it inserted well, the data throughput went way up. A little housekeeping goes a long way.

A humorous story for the geeks out there: I was asked by an un-named organization to find a repeater for them a few days ago. Seems that the ethernet cable they laid was a bit longer than the IEEE thinks it should be. So I scared up one of those big old mongo 802.3 repeaters that have two AUI ports on the back. One of the ports had a cable connected to a very large transceiver containing two 10b2 connectors. The other port still required a transceiver, and I told them they needed to find one. I was poking around today in the area where they said that the repeater was needed, and found it sitting there with the single AUI cable and transceiver connected and running outside of the TAC. Nothing connected to the other AUI port. I went outside and found both ends of the RG-58 connected to either side of the transceiver. The lights on the transceiver were blinking away. I found the fellow that wanted the repeater and asked him if it was working OK. "Yes," he said, "thanks! Works much better now!" I didn't have the heart to tell him that all he had effectively done was installed a $500 barrel connector between his two coax segments.

Such is life in TFXXI.

TFXXI Day 20 (Tuesday), 11 Mar 1997

The movement to contact was an eye-opener for the Brigade today. It was the first time they were able to exercise full-up, in the manner that they will use to kill the OPFOR beginning on Sunday. There were MANY lessons learned, far too numerous to post here. Tonight they rest, for tomorrow morning they receive their NTC OPORD. It will be delivered to them digitally (via ATCCS), by FTP, by disk, and on paper. We want to make dang sure that they get it! A formal mission briefing is scheduled right after lunch. Briefbacks and WARNORDs will follow throughout the day.

Thursday and Friday are maintenance days for the equipment, and planning/rehearsal days for the BCT and TF staffs. On Saturday they move into position, and LD early Sunday. The contractors and support staffs must have all systems go by Saturday. We are tracking specific changes to any and all systems, real tight configuration control. Our CG told us earlier today that if the system, initiative, or change won't make it easier for the BCT to kill OPFOR, then don't mess with it. Focus on KILLING OPFOR.

As yesterday, we had quite a few visitors. More expected tomorrow and each day through the end of the rotation. It's hard to remember what you've briefed previous groups. Glossy eyes from the visitors are a clear sign that you have to back up and explain something in greater detail.

The NOC continues to improve itself. Today they started posting notes (on their web server) to the 74B's on lessons learned. This is a great tool for getting general information out to where many can retrieve it. I've challenged one of my own 74Bs to write some perl or java scripts to create fill-in-the-blank web forms in the TAC. These would be used by the staff sections for the afternoon staff update to the CG. If it works, the input from the web site will be used to automatically create a PowerPoint briefing (yes, even Force XXI units use PowerPoint to brief their leaders. It's for internal updates that have nothing to do with the battle. We do those updates using ATCCS screens on our integrated video monitors in the TAC.)

Training for the NTC personnel in the Starwars DivTOC and the TAFs is going well. They should be ready by the weekend to conduct battle. We continue to have minor disputes over who will control the brigade in the box (us, the 4th ID, or them, the 52nd Mech). According to the rules of the NTC, it will be the 52nd Mech. But since we have most of the division staff here, it's hard for us to back out of the picture. By Saturday I'm sure we'll have that technicality worked out.

TFXXI Day 21 (Wednesday), 12 Mar 1997

If you can barely hear me, it's because I lost my voice today. Either too much fun or too much yelling, or both. But it's gone. The support staff is getting a kick out of it, as are my buds in the TAC. I'll get it back in a few days. Good thing I can touch-type, eh?

The BCT got their operations order this morning. It was sent by ATCCS, by FTP, by tape, and on paper. The electronic process took several hours to get it out due to the large amount of data and the slow wide area network. In case I haven't explained the basic architecture, the order was written on ATCCS computers in the Starwars building (the 52nd Mech Division TOC). From there to the DivTAC is quick due to our ethernet connection between the LAN hubs in the DivTOC and the DivTAC. But the path to the BCT requires use of the 16kbs TPN backbone. And from the BCT to the Task Forces and slice elements the path is via SDR, EPLRS, and SINCGARS (data radios) networks. So it takes a while. I think that a better approach would be to distribute the base order on a CD along with the necessary maps and graphics. This would be like issuing a basic load of ammunition, food, and fuel. When you LD, you have 72 hours of basic load; this basic load should also include information. The relatively slow send time frustrated the brigade and TF staffs. This will be one of many areas that will need to be fixed when we field the first digital division in the next century.

Even though day 1 is not until Sunday, the rotation has effectively started. There is a massive intelligence gathering effort underway. For OPSEC reasons I will stop at that and explain later, after the rotation is over.

For those keeping score on your old dusty maps of the NTC, place the bulk of the brigade clustered on Four Corners, with the Brigade HQ about five miles east on East Range Road. The aviators are at Bike Lake. They will stay in these TAAs until this weekend when they move to their start positions. The "JTF HQ" is in the dustbowl. DivTOC is in the Starwars Building, DivTAC is just southwest of it in the open field. The DISCOM is located off Langford Lake Road in the industrial area. SYSCON is on top of Beacon Hill. The PX is next to the Commissary. Burger King is near Clothing Sales.... Oooops, got carried away. :)

(By the way, the locations of these units is public knowledge here, by both sides. Once the killing of the OPFOR starts I won't reveal friendly positions.)

TFXXI Day 22 (Thursday), 13 Mar 1997

The BCT briefed their order this afternoon, and the TFs had their orders ready tonight. Tomorrow the company teams and platoons begin rehearsals. The BCT also jumped their TOCs today. We were able to "watch" the jump by monitoring the network status (the routers went red when they unplugged and started moving, back to green as they started setting back up) and of course, by watching the Appliqué screen.

The first operation will be a movement to contact on Sunday morning. Between now and then, the elements of the BCT will finish the orders process, conduct rehearsals, and move to the final assembly areas. The soldiers are still very motivated and spirits remain high.

The division's planning team arrived from Hood today. They will occupy a building adjacent to the Starwars building. Over the next few days they will write the order for the second phase of the rotation. This part will focus on the new tactics of Information Operations, ala FM 100-6 and TP 525-5. The first phase (LD is on Sunday) has a "traditional" order published by the 52d ID.

A great story was told to me today by an individual here. He said that several days ago he was talking to a soldier about the Appliqué and the new digital tools at his disposal. The soldier stated that he feels much more comfortable now, especially at night, driving alone in the desert. With his Appliqué on and operational, he is no longer "alone". "I can see all of my other soldiers there on the screen and know that I'm not really all by myself in the middle of nowhere." What a moving story. If nothing else, we are creating a much higher level of confidence in our soldiers. There's nothing as scary as the feeling of being alone on a battlefield.

TFXXI Day 23 (Friday), 14 Mar 1997

There's quite a lot going on here now as we get into the last hours before the operation starts. The BCT conducted company team rehearsals today. Tomorrow are TF rehearsals followed by a BCT rehearsal. The soldiers are psyched, on both sides. We saw a sticker today, one of those circles with a diagonal bar in it, that had the TFXXI symbol behind it. Apparently it was issued by the OPFOR, who are rumored to be mumbling something about "kill TFXXI" much in the same light as we say "kill the OPFOR!" Just imagine, within the next 48 hours, there will be dead OPFOR littering the battlefield and the BCT will be victorious!

Up in the TAC today we worked through some problems with our DCE cell server. It had been the ASAS machine, but it appeared that being the cell server was slowing it down. So we tried using the AFATDS machine and the FAAD box. Neither worked. Eventually we settled on a CSSCS computer. Still had problems getting some of the MCS client computers to come up. After checking the cabling and tightening up the connections a bit, it started working. The end result was that most of the original problems stemmed from operator error, not equipment or software failure. I suppose that with more training we will get better at this. Our DCE cell is by far the largest out here, but at least we don't have to move it (as in jumping the TOC, which the TF and BCT TOCs will do).

Our LAN management tools were a great help in working through the DCE mess. Just a glance at the screen and I knew who was up or down. The web page that the NOC is using is absolutely invaluable for the afternoon briefings to the CG. He wants timely information, and he gets it. I've also gotten pretty good at getting the briefing sent back to Hood electronically so that we can conduct our VTC between the CG and Chief of Staff. The GTE HSMUX cards are working great, too. We route UAV video to the Aviation Task Force when we aren't in a VTC to Hood. When we are connected to Hood, we can either be in a single point mode to the Division Conference room, or we can add in the Corps Assault CP for a multipoint conference. Good job, GTE!

I'm proud to announce that my TOC LAN manager's wife delivered a son this evening. We were able to get him back to Hood to be with his wife and newborn. Unfortunately for me, that leaves yours truly as the TLM for the DivTAC. I suppose that I wasn't busy enough. At least most of the hard work is done, and he was very instrumental in making it come together (he's a 74B SGT that is way beyond his peers in maturity and technical expertise; the type of soldier we want to retain but probably won't).

One short editorial comment for those of you who have not been getting these notes from the start. I'm but one of over 10,000 people that came to Irwin as part of TFXXI. My notes are intended to keep my fellow automators on the 53List informed and updated on the most exciting thing to happen to the Army in several generations. I realize that these notes are forwarded to hundreds of people off the list. Please remember that what I write is from my perspective and in no way tells the entire story of what is going on here. If I get a technicality wrong, I'm sorry. Do me a favor, though and drop me a note if you disagree with something that I said. We'll work through it and make sure that everybody understands what's going on.

And to my wife (who gets blind copies of these notes on our ISP account), HAPPY BIRTHDAY! Sorry that I missed it! I'll make it up to you after we get done killing OPFOR!

TFXXI Day 24 (Saturday), 15 Mar 1997

Let the games begin!

The screens are full of red icons on the left (west) and blue icons on the right (east). We are now watching (it's 2100 local) the recon elements of both the OPFOR and 1BCT move into position. The brigade will LD at 0630 in the morning. Overnight, we will conduct a deep attack with the aviation assets into the China Lake area, as well as the recon battle. The plan is for 1-22 Infantry to lead the BCT in the main attack down East Range Road towards a projected encounter near Four Corners. 3-66 Armor will sweep south then west to engage the second echelon. As I type this, we have UAV coverage deep into enemy territory, allowing us to see just about every vehicle out there. There are also lots of eyes deep, and plenty of live intel coming back from several sources. By this time tomorrow the first battle will be in the history books. (I am not concerned revealing anything sensitive with the above information since I will wait to transmit this file until after the battle.)

We continued solving technical problems right up to the end of the day today. I must say that we have a terrific support staff here from the many PMs, contractors, agencies, schools, and other interested organizations. There has been and still is a lot of frustration in making these systems come together. But working as a team, we all have done remarkable things. Thanks, everybody!

Now, off to get a bit of sleep before coming back to the TAC to witness history. I hope to have pleasant dreams about killing OPFOR....

TFXXI Day 25 (Sunday), 16 Mar 1997

(I realize the sensitivity of discussing what happened here on such an "open" list. Please pardon me if I stay in general terms and don't go into much detail.)

So, the results of the first battle: I'd say it was a draw. The tactical internet and information systems worked great. Probably worked too good. I think that the BCT had the normal jitters and while they did not get squashed, they did not wipe out the OPFOR either. Many of the soldiers used their Appliqué and ATCCS systems to their advantage, and many opted to go with the more familiar approach of voice and visual communications. Some used a combination of both. I think that in the next battle (probably Tuesday morning) there will be a more extensive use of the electronics.

The OPFOR was observed crossing the "international border" in the wee hours of the morning, and the BCT LD'd almost immediately after the incursion. We were able to observe the OPFOR's movements but the ROE would not let us kill him deep. The BCT was able to force the OPFOR against the northern edge of the central corridor, as the OPFOR moved from west to east. But, after they appeared to pin them down, the BCT failed to swing north and kill them. I'm not sure why, and I'll leave that up to the OCs to figure out. Around 11am we got a change of mission. At that time, there were about as many red icons on the left as there were blue on the right. They were straddling roughly the Barstow Road, with some of each force on either side of the road.

Outside of the first battle of TFXXI, I fought my own battles along with many of the network architects trying to figure out what is wrong with our DCE cell in the TAC. It hasn't really worked well since we got here. We know that a big part of it is training, but there still seems to be other instabilities. We spent a lot of time verifying grounds, ethernet cables, connections, etc. The last thing we did was establish a separate computer as a DCE cell server, one that has no ATCCS software running on it. When I left the TAC an hour or so ago it was still working. I'm keeping my fingers crossed...

The VTC systems are making big money. We were able to push UAV video to the aviation task force over night to support their deep attack. This afternoon we did a three-way VTC with our conference room at Hood, the Corps ACP at Hood, and the TAC at Irwin. All over MSE using the HSMUX cards. It went very well and is rapidly becoming a normal part of our CP operations. The ATM VTC is also working well. I'm going to use the ATM circuit on Wednesday to move the next division OPORD. It's a much bigger pipe than the TPN and will cut the total transmission time from several hours to several minutes.

TFXXI Day 26 (Monday), 17 Mar 1997

The BCT spent the day today getting ready for round two - a deliberate attack. They conducted rehearsals and finished AARs from yesterday's battle. The excitement level remains high both in the BCT and here in the TAC. LD is again early tomorrow morning. Tonight the intel folks are working at full speed to provide products to the BCT.

Getting those products to the brigade has been a challenge. I worked out a way yesterday where we can use the ATM circuit as a highspeed data path between the Division and the Brigade, Aviation Task Force and Forward Support Battalion. When we are not using it for VTC, I can push large amounts of data down a pipe that can run as fast as 768kbs when conditions are perfect. The ATM system is being used several times a day to conduct synchronization drills, to pass immediate information, and for conferencing between multiple locations. In addition, we use the GTE HSMUX cards to pump live UAV video from the division to the Aviation Task Force, as well as conducting our daily updates to Ft. Hood (this link has grown to a three-way VTC with us, the division conference room, and the corps ACP, all on MSE equipment.)

In the TAC today the subject of biggest concern was our ATCCS DCE cell server. It hasn't been well for several days now. The first couple of weeks it worked fine. The cell server was hosted on an ASAS machine in the G2. This was OK until the intel load picked up to a point where the ASAS box could not keep the DCE cell healthy. So we moved the server process to a FAAD box, then to a AFATDS box, then to a CSSCS box. None would work as well as the original ASAS before it got overloaded. We did not attempt to use MCS as a server since it has known problems in that role. Our next idea was to use a standalone cell server. It was set up yesterday, but failed after a short time. Today we loaded that same computer with an ASAS harddrive, but only activated the cell server process. It's been working great now for almost 12 hours. We will feel better after 48 hours of no failure. (The cell server is the box that controls or mediates the DCE cell in a TOC. Without it, the ATCCS boxes would be unable to run client/server services with each other. They would appear as standalone machines.)

I had the great pleasure of meeting the Honorable Togo West today as he visited the TAC. My CG introduced me as "the Engineer who likes to break things but always manages to put them back together working better." Probably a pretty good assessment. Mr. West seemed to understand.

TFXXI Day 27 (Tuesday), 18 Mar 1997

Today was a dark day for the BCT. It did not go as well as it should have. The OPFOR were up to their usual tactics and methods, and ate up the blue forces. It was very much like a "normal rotation". So what went wrong? They used their Appliqué, and had full situational awareness. ATCCS connectivity was the best it had been yet. Good intel and full UAV coverage. I think that what we saw was what we were predicting last year. The electronics will get you to the fight, but they won't kill the enemy for you. It still boils down to good crew training and cool execution of the plan. So tonight they prepare a defense and get ready for the next fight, probably tomorrow night or on Thursday. There should be a good recon battle this evening into tomorrow morning.

We are seeing other things as well. Reporting up the chain (TF to BCT to Div) is still a semi-manual process. The Appliqué updates the MCS at some points automatically. But a soldier must still manually send an update to higher via a message. In the TAC, our battle captain (actually a Major) was using our Appliqué to locate units, then calling their locations via Meshnet to his MCS operator in the HMMWV, who poked the info into the computer. Not a good way of doing business. He was forced to since the BCT was too busy fighting a battle to keep him electronically updated. Now I know that this boils down to unit training and discipline, but how many of you current and former division staffers out there remember how hard it is to get current info from the brigades during a fight? It's the same in a digital staff. I've challenged our contractors to come up with a way to make this fully automated, and not dependent on a soldier sending updates manually.

The UAV coverage has been spectacular. We are able to pump it from the TAC to the aviation task force via the VTC system running on the HSMUX cards in the MSE switches. The aviators were getting fancy today and continuing the feed on to the 1BCT TOC via the VTC system that rides on ATM. Good thinking, ATF!

Tomorrow we will publish the next division order. We rehearsed sending files using FTP on the ATM system today. I'll be able to report tomorrow if we were successful. I suspect we will be, since I can move a 1Mb file in under half a minute on ATM vs almost an hour on the busy TPN.

Last item. The Honorable William Cohen visited the TAC along with GENs Reimer and Harzog. There was an army of cameras and security personnel as well. One of my buddies asked a security guy what new Force XXI gadget he had to play with. He grinned just a bit, then turned and talked into his wrist. Ooops.

I've got two great 74Bs that are working for me. One is a young specialist who has now briefed almost every high ranking official that has come through the TAC. Today he was invited to lunch with the Sec Def. On his return he was clutching a coin. From the Sec Def. It is his first one. Nothing like starting at the top and working your way down!

TFXXI Day 28 (Wednesday), 19 Mar 1997

The BCT was ordered to defend in sector last night against the evil OPFOR. If you recall, the OPFOR came across the international border early Sunday morning and was stopped by the blue forces. A counterattack by blue was unsuccessful yesterday. Since then, the digitized blue forces have been preparing defenses for an expected continuation of the OPFOR attack, possibly as early as Thursday morning. This evening a reconnaissance and aerial battle ensues. The UAV is observing enemy activity and the TAC is forwarding that video feed directly to the Aviation Task Force for servicing. The ADA folks are tracking and killing all objects in the air that don't belong to us. Tomorrow the Valley of Death will be a killing field full of dead OPFOR once we get done with them.

The digital OPORD for phase two has not gone out as of this writing (2200 hrs). It should be finished sometime this evening or early tomorrow morning. We are ready to send it to the BCT, the ATF, and the FSB by ATM (768kbs). All other TOCs will receive it over the tactical internet (16kbs or less).

Today our CG obtained a pair of virtual reality glasses. These are COTS equipment costing a couple of hundred bucks. We are going to give them to some of our scouts to use with their Appliqué in their vehicle. The idea is to give them a way to view a computer screen without having a blue glow coming from the inside of the vehicle. A blue hue is a quick giveaway for a scout or recon team that is trying to be stealthy in the dark. Too bad we don't have infrared LCD screens for our computers that can be viewed using night vision goggles. That would be too cool.

The training level of the TAC staff is getting better. They are starting to figure out how to use the electronics to their advantage. Nothing has changed in the amount of information flow, just their ability to interpret what they see. From this standpoint, we are getting lots of great feedback on improvements to these systems. This is precisely why we do AWEs, to let the warfighter provide meaningful feedback to the material developer so that the fielded system is what the soldier wants and needs.

The NOC continues to come up with good ideas. They've developed a status chart available on their home page that shows the past 24 hour status of all of the routers in the network. It's just a simple text chart with router names down the left side and time across the top, but full of useful information for network managers in the TOCs. I brief the division CG each afternoon on the overall health of our ATCCS systems and networks, and the info that the NOC puts out is invaluable. And, during the day if we feel that we are losing connectivity with a particular unit, the NOC can give us an immediate status of connectivity. Some day, I think that we will get our own automation BFA that will give me a full view of the Information Operations battlespace. Such a BFA will not only provide a connectivity check, but would also show me if particular pieces of information (a frago, for example) has been delivered to a specific location.

TFXXI Day 29 (Thursday), 20 Mar 1997

That was a nice summary that some anonymous observer posted to the C4I list, and was subsequently cross-posted by CW3 Miletich to this list. Thanks, Chief. I don't want to provide the level of detail that was in that report, and from the comments I've received it looks like most of you are satisfied with my brief updates. If you find any other similar updates, throw them on the list for the rest of us to read.

The score, if we are keeping score, is 0-1-2 for the BCT (win-lose-tie). Today they defended against a deliberate attack from the OPFOR. The defense belts stretched north-south, east of the Barstow road. The main belts were in the central corridor. Last night, the friendly aviation systems were very successful, and were clear winners. Good recon effort, and it appears that the intel feeds are getting better. The OPFOR was able to breach a tank ditch in the valley of death (southern corridor), and pushed quite a few vehicles through there, killing four company teams of blue. They did make it into the BCT's rear, but with severe attrition. The central and northern corridor defenses were successful. So, since the OPFOR did make it to the uranium mines (their objective), but the blue forces were not destroyed and held the central and northern areas, we have agreed to call it a draw.

The 124th Signal Battalion SYSCON is located on Beacon Hill, just south of the pass where the OPFOR came roaring through. A spot report was sent in to the BCT, "30 vehicles are blazing through...". Roger, said the BCT. A few minutes later, another spot report goes to the BCT, "30 vehicles passing through...". Already got that report, says the BCT. Negative, says the SYSCON. That's ANOTHER 30 vehicles!

Tomorrow is a pausex, allowing the BCT time to repair equipment and get some rest. The tech support people will be with them tomorrow adjusting and tweaking. The next phase of the AWE begins Saturday night, and is what we call the "525-5" phase. It will be conducted as an Information Operations exercise. The past week was a baseline exercise conducted according to the usual NTC rules. My understanding is that the next phase will have more free play and more freedom for the BCT. I'm sure that there will be a much larger intel feed into the S2 from the division G2.

The Marines and the Special Ops folks departed today. They have been supporting the DivTAC staff with their perspective of this stuff. The SF'ers had live teams in the box that were doing great things. The Marines were tied to their home unit at Twenty-nine Palms, and were providing a simulated feed of an adjacent Marine unit. It's good to have interoperability this early in the experimentation process. We will have both organizations back in June to participate in the first of three DivXXI exercises.

The digital order for the next phase went out last night. Unfortunately it was sent by FTP on the TI before we knew it at the TAC. Once we found out that it had been published, we got a copy of it from the DivTOC and pushed the 100k file in about two seconds via the ATM circuits to the BCT, the Aviation Task Force, and the Forward Support Battalion. I thought that it would be bigger (the original order was over 2Meg total). Regardless, we have documented the procedures for moving large amounts of data without clogging up the narrow TI pipes.

Our G3 is getting pretty good at figuring out what he wants the ATCCS systems to do. Now that he and his staff are getting some good stick time, they are coming up with better ways to organize and move information. Their comments and feedback are being recorded and will be considered in the next versions of the software. One thing that is not working well yet is automatic reporting. I think that I mentioned that in an earlier note. The support staff tells me that it was supposed to be a part of our system, but was not ready for the AWE at the time we locked down the software. So part of the updating is manual, part is automatic. This frustrates the G3, but I think he will be satisfied if it is working by the time we do the DivXXI AWE.

TFXXI Day 30 (Friday), 21 Mar 1997

Today was a day of rest for the BCT, and an opportunity to repair and fine tune the TI systems. The BCT received an order to defend NLT xxxx hrs tomorrow for a possible resumption of hostilities. We expect that the OPFOR will violate the international border again, and we have gone into a mobile defense in preparation for it. This is the beginning of phase II, something that does not happen during a "normal" rotation. The BCT is tired, but highly motivated and ready to kick some butt. (I'm sure the OPFOR feels the same way.) What will follow over the next week will be free-play, with little control from the Starwars building. It will be an interesting fight. Info ops at its best.

A correction to my scorecard from yesterday. The following comments concerning my posting were forwarded to me via a secret back channel (ain't information operations great!):

====

Date: Friday, March 21, 1997 12:17PM

FYI. Note the score (0-1-2). I agree, if one counts surviving combat power. However, if one examines both Blue and OPFOR mission statements (they're briefed during the VTCs), then the score is 2-1 Blue. OPFOR, despite what the source below states, did not achieve their terrain objectives during either the MTC or DIS missions. Since Blue only had to deny OPFOR achievement, Blue wins.

====

This came from an individual that will go unnamed, but is quite connected to the battles here. Nice to hear that he thinks the EXFOR is winning.

We again had several visitors through today, including my former Commanding General and the Corps G3 from the XVIII Airborne Corps. We were also visited by the president of a major defense contractor. I noticed an interesting phenomena. When a senior military official (SecDef, SecArmy, CSA, etc.) come in, the uniformed members of the TAC make an effort to get introduced and get at least a handshake out of it. Except for the likes of the SecDef and SecArmy, the soldiers don't pay much attention to the civilians, including company presidents. But, when the president of one of the companies that supports us comes in, the employees of that company come out of the woodwork to try to at least shake his hand. I guess that everybody knows who's their own boss!

I found out today that I've been walking in the footsteps of an actual author of an Internet RFC. And I believe that there is a second one here as well. I've never met an RFC author before. This particular person and I have spent many hours in jestful geek-speak. Then today I find out that he's an RFC god. I am indeed humbled.

TFXXI Day 31 (Saturday), 22 Mar 1997

The BCT has occupied defensive positions roughly east of the Barstow road, back to the east gate. The nasty OPFOR crossed the international border earlier today (west side of post) and appear to be probing to find friendly weaknesses in order to strike east again. We suspect that they are after those uranium mines east of here, like last week. Early reports are painting a picture of a two regiment force, much larger than before, and well equipped. Our UAV coverage continues to be spectacular, and tonight we will benefit from a live JSTARS feed (a couple of days ago we heard the double sonic boom of an SR71 coming back into Edwards AFB. I don't know if it is up tonight or not.)

My understanding is that the OPFOR has about two days to figure out how to fight through the BCT to reach the uranium mines. In a normal rotation, they are given certain formations, tactics, avenues of approach, and other controls. In this phase of our rotation, these controls are drastically reduced or eliminated. Likewise for the blue side. It should be an interesting fight. We have a clear intel and situational awareness superiority, but the OPFOR is well trained and knows the terrain far better than us.

On the technical side, there is nothing new to report today. Several visitors to the TAC, as usual. The daily VTC session via MSE to Ft. Hood went flawlessly. All comms are green. ATCCS boxes are up. Life is good.

All we have to do is sustain our successes for seven more days and we're outta here.

TFXXI Day 32 (Sunday), 23 Mar 1997

It's a sign from the gods. A brilliant comet in the western sky, the Moon passing through the Earth's shadow as it rises above Tiefort Mountain, Mars, God of War, in spectacular beauty just above the Moon..... Last week we had a minor earthquake; and the weather has been better the past four weeks then has been seen in the month of March in the Mojave Desert in many years. It is a sign that the gods are smiling. Smiling on the mighty EXFOR. For tonight they stand victorious over the smoldering remains of the OPFOR.

Need I say more? Victory was sweet. And tonight brings the possibility of further destruction. Ahhhh, to have the new capabilities of Force XXI. The intel folks are producing like never before. Even Task Force commanders have a live feed from JSTARS to see exactly where the enemy is moving. Comms are green. Computers are processing thousands of messages and millions of bits of data. Unbelievable how all of this has come together. It appears as though the soldiers of the EXFOR have gotten over their early jitters and are now becoming more confident in their systems. This morning the OPFOR attempted to breach our forward defenses with no success. The central and northern corridors held exceptionally well. Enemy penetrations into the southern sectors (after the OPFOR violated the UN Safe Zone [an area west of main post occupied by a NASA deep space facility], a clear sign of their malicious intent) were halted by the quick reactions of the digitized forces. We fully expect a regimental attack tonight, and lie prepared to defeat it. Hostilities will most likely continue through Tuesday before an anticipated break in the action. The EXFOR is tired, but spirits remain high after today's victories.

Life is good. The gods are pleased.

TFXXI Day 33 (Monday), 24 Mar 1997

Things are really looking great here. The EXFOR got a change of mission this morning at 0900 after it appeared that the OPFOR could not break through the defensive belts. The expected regimental attack came overnight, and was successfully repelled by a combination of aviation, artillery, and direct fires. It was a very good job of synchronization and integration of the systems. The JSTARS and UAV systems have really earned their pay in providing timely intel to the maneuver commanders. And the Appliqué/ATCCS network is performing in a spectacular manner.

Tonight, the EXFOR will advance west, conducting reconnaissance in advance of a hasty attack against the OPFOR. The fighting is anticipated to continue at least 24 more hours (an admin pausex is scheduled for Wednesday). The TFXXI AWE is still on track for ENDEX on the 29th. Then comes the long process of analyzing what we've learned.

For those of us in 4ID and many of our supporting organizations and agencies, we return to home station next week and immediately transition into the DivXXI AWE mode. We have a very full schedule between now and November. But, it will be nice to focus on only one event (DivXXI) for the next several months and put TFXXI behind us. I could sure use some help if any of you could figure out a way to get here (I'm dreaming, sorry).

Today's visitors to the TAC included quite a large group of foreign officers from Germany, France, Spain, and Israel. Our Corps Commander and his Chief of Staff also came by. In the G6 we got interviewed by two German papers, the Wall Street Journal, and FOX News. Tomorrow all of the branch school commandants in TRADOC plus several 3- and 4-stars will be visiting. The visibility of what we are doing is beyond what I could have imagined. I hope that our PAO will be able to capture all of the printed articles and stories so that we can see what has been written about this.

In the past several days, I've been briefing "green" status for comms and automation. It sure is a pleasure to do that. A great reflection on the systems (legacy and experimental) that are out here, and the people that have put all of this together. I couldn't ask for a more professional team. Thanks, again, ladies and gentlemen!

TFXXI Day 34 (Tuesday), 25 Mar 1997

Another fine day in sunny southern California has come to a close. The EXFOR conducted a hasty attack against the OPFOR to push them back towards the international border. The EXFOR did well, but was unable to gain as much ground as they wanted to. We still have a bit of a problem with soldiers not believing what the situational awareness systems are telling them. The locations of the OPFOR were pin-pointed by the UAV and sent to the ground commanders, but they let their intuition get the best of them. It appeared as though the EXFOR was concerned about a possible counterattack from an area where our intel sources said that there was no OPFOR. At 0900, a change of mission was called, bringing a 72-hour continuous operation to a temporary halt. We are now in a pausex, giving both the OPFOR and the EXFOR an opportunity to receive AARs and resupplies. So tonight they rest, and plan for the final event. The battle will continue Wednesday night with a likely deliberate attack to push the OPFOR back across the international border once and for all.

Yesterday I asked for some help in executing the DivXXI AWE. I got a very unique reply from a list member. He suggested that we get RC officers and NCOs to participate in the exercises, and get AT credit for it. What a great idea! If there are any readers out there that are network engineers or a similar profession in civilian life that can swing something like that, please let me know. I'm not sure if we can pull it off, but it sure is worth a try.

We got our CG's virtual reality glasses to work with the Appliqué in his HMMWV today. So tonight if you see a general with plastic glasses on, consumed by the image on his miniature screen, you'll know what's really happening. (If you recall from a previous note, this was to experiment with eliminating the blue glow coming from the LCD screens of the Appliqué computers in scout and recon HMMWVs.)

It was a pleasure today to show off our shop to the Chief of Signal, MG Ackerman. He spent over an hour viewing our TAC, and was also able to see the SYSCON and the Network Operations Center. We are getting a unique view of the future of the Signal Corps here. It looks like the next century will continue to provide a challenging environment for the Signal soldier, and will involve not only the traditional voice circuits and RF side, but also data network engineering and management challenges, as well as this new thing called information operations. Maybe we will some day get our own BFA that allows us to view and interpret our battlespace in the same manner that the other BOSs can see theirs. Thanks for the visit, sir! PPV!

This evening during the pausex our contractors will be tinkering with the DCE cell in the TAC. We have had it running for over a week without failure on a dedicated cell server. Tonight they will bring it down and reestablish it with the system that was causing problems last week. The idea is to attempt to trap the exact cause of the crashes and slowdowns that we were experiencing two weeks ago. This part of the experiment is important for the TOC LANs. We will continue to use DCE for the foreseeable future as a means of interfacing the ATCCS systems, and need to know specifically why it does not work as it was designed. Eventually we hope that ATCCS will collapse into one larger integrated system that will not require the environment we are using today.

Earlier today, as the UAV was returning to the airfield, the operator circled several times, making sure that the camera was well aimed and focused on etchings in the desert floor. I'm sure these markings were left by some mysterious extraterrestrials many centuries ago. Looking closely, we could clearly make out in large, 10-foot high letters, the words:

UAV - 2

OPFOR - 0

What would Erik von Daniken say?

TFXXI Day 35 (Wednesday), 26 Mar 1997

Today's activities for the BCT centered on AARs, orders writing, resupply, and rehearsals for the last battles of TFXXI. Tomorrow we embark on the final chapter of a long story of success that started many years ago with a vision of C4I For The Warrior. From this document came The Vision, the Army Enterprise Strategy, and ultimately, Force XXI. I am deeply honored to have been a part of this modernization effort, and owe much to the original author, COL(P) David Bryan. Thanks, sir! I only wish that you could have come to the NTC to see the fruits of your efforts as these soldiers live and fight the future battlefields that you proposed several years ago.

Tomorrow evening the EXFOR will send forth reconnaissance elements searching for weaknesses in the OPFOR's defense belts. A deliberate attack will follow, and after the dust settles we will be standing in line at the OPFOR's MKT waiting for a plate full of their food. It should be a good final fight. Here at the TAC we will have the usual ringside seats, and I'll do my best to give you a summary of our successes.

We lost a UAV today, not to good OPFOR aim, but to a mechanical or electrical problem in the aircraft itself. It did just what it is supposed to when in trouble, it cut power, deployed a parachute, and executed a perfect PLF onto the desert floor. Not much sustained damage, and good to see that the safety systems worked as designed. The UAV has had an interesting effect on the OPFOR. They spend lots of time looking for it, and tend to talk about it on FM as well. This gives the intel boys a chance to intercept the conversations, and provides us with a remarkable amount of visual as well as audible info on the OPFOR.

The AARs on yesterday's battle confirmed what we suspected. The Appliqué screens were very close to ground truth as shown on the Starwars systems. The BCT's mistake was in not translating the known enemy positions into a modified enemy template. They wanted to stay with what they thought was right, rather than what the machine was telling them. I suspect that it has a lot to do with confidence in the heat of battle; you fall back on those skills that are burned into your brain when the situation gets hot.

The DCE cell server test was inconclusive last night. The contractors brought up the other system, it functioned fine, and they could not find anything wrong that was causing it to crash last week. We have two different versions of the DCE cell servers, and are trying to determine if one is more stable than the other. At the end of the test we restored the server back to the configuration that has been running uninterrupted for over a week.

I had a chance to learn more about network intrusion today. A gentleman from LIWA came down and showed me more tricks of the trade. I think that we are getting better at the C2 protect side of this. It's not easy, but it looks like we can train our 74Bs to operate the automated detection systems, as well as teaching them how to look for and find evidence of possible C2 attack. This is one area that needs more instruction and practice for both the 74Bs and the system operators in the BFA's.

TFXXI Day 36 (Thursday), 27 Mar 1997

Well, gang, we are down to our last 36 hours or so of TFXXI. There will be a fight tonight, and probably a final hooah on Saturday morning. The EXFOR is going to conduct a deliberate attack against a defending OPFOR overnight, then if all goes well, will conduct a pursuit to push them back beyond the international border. The bulk of the EXFOR is situated in the eastern portion of the central corridor, oriented south. They will attack south and west towards the Langford Lake area. The OPFOR is tucked into waddies and ravines west of the Whale and back towards Langford Lake.

The original attack plan was changed this evening by the EXFOR commander. He did something that we have been wanting to see from the beginning. As I've pointed out in previous notes, we have an ATM circuit connecting the DivTAC, 1BCT, Avn TF, and 4FSB TOCs. This evening there was a VTC session between the 1BCT and ATF commanders to discuss an immediate change in the plan. The EXFOR commander used the whiteboard to draw a sketch of his new concept of maneuver, and the ATF commander added his comments. The Division Engineer along with members of the Div staff were watching our computer as well, monitoring this impromptu session, and are fully briefed on his new plan. It looks like this is taking the O/C's completely by surprise. Not to mention the OPFOR, who may have had access to the original plan. Talk about information operations at its best! The fact that two Brigade O6's can negotiate then execute a complete plan change, and keep the Div staff informed in real time is quite remarkable.

As before, the UAV and other intel systems have the OPFOR's defenses pinpointed down to the last hole, and last strand of barbed wire. That may be why the EXFOR commander changed his plan tonight. Once you know where the enemy's obstacles and battle positions are, you should make corrections to your plan as needed. Earlier today we heard a loud sonic boom. I went outside, and overhead was the very obvious contrail of an aircraft that had made a huge arc, passing directly over the suspected OPFOR positions. You could just make out the aircraft at the nose of the contrail, and it was hauling ass. I went to the G2 staff to see if they knew what it was. All I got was some nods and grunts, but nobody would acknowledge what had just passed over. hmmmmm.....

We got just a bit out of control in the TAC today. We maintain an open video connection between us and the Aviation TF TOC so that we can pass them live UAV video. They send us a view of the inside of their TOC in return. We keep this circuit monitored at all times in the G6 to ensure success. Well, just after lunch, when the temperature outside (and inside the TAC as well) was getting into the uncomfortable zone, we noticed a flurry of activity on the screen. Watching the movement, it became very clear that they were under an NBC attack and had gone to MOPP4. Everybody was donning masks and suits, getting hot, and hating life. We immediately switched the video feed to one of the large monitors in the middle of the TAC for all of the Div staff to observe. We switched off the UAV feed and sent them a view of us, sitting there without our MOPP gear. Naturally, we got some rather suggestive "digital" signs of friendship from the ATF staff. Not to be outdone, we placed an ice-cold 24-pack of Pepsi on the table and zoomed the VTC camera onto it, so that it filled the screen at their end. Bevis and Butthead would have been proud of our juvenile approach to a high level of motivation and esprit de corps in the new world of Army Digitization! (no worries.... we returned to UAV coverage after about two minutes of misbehavior)

TFXXI Day 37 (Friday), 28 Mar 1997

It's like a boxing match that has gone to the last round. Both fighters are in their respective corners, bloody and exhausted. Teeth are missing, eyes swollen, sweat glistens on their heads. The noise from the crowd is deafening. Their coaches are giving them the last pep talks, and they each are focusing on one thing: survive until the bell rings.

Tonight the EXFOR and the OPFOR are the respective gladiators. Today's fight was bloody, but inconclusive. The EXFOR had about 95% knowledge of all enemy locations prior to LD, but were unable to maneuver to a position where they could punch through the defensive belts. Each side is worn down and is badly wounded (for real, not notionally). Following this morning's fight, the OPFOR was repositioned to the west, and the EXFOR was given the mission to defend along the Barstow Road and to the east. The final bout will begin around 0500 tomorrow morning. The soldiers are mentally and physically tired. Their equipment has been through hell. The crowd (us in the TAC) expect that both fighters will come out of their corners, advance towards each other taking jabs and pokes, circle a bit, curse each other, then stop short of total destruction someplace near the Four Corners. To our amazement, they will dismount and greet each other with an understanding that only two superb and well matched units can appreciate. If they could, I suppose that they would roast a pig and have a barbecue. The crowd would cheer for both fighters, for they deserve plenty of praise and recognition.

If nothing else, these past two weeks have proven that the Army is ready to advance into the next century with capabilities unthought of just a few years ago. A few of us were discussing earlier today that if you could take the digital capabilities of the EXFOR and put it into the hands of the OPFOR (who possibly train on their combat skills more than any other unit in the Army) you would have an unstoppable team. I wish that there were a way for the 1BCT to spend the next 12 months training like the OPFOR does, then come back and do this rotation again. (I'm sure the soldiers in 1BCT would lynch me if they could for suggesting such an idea!)

We had several visitors today, including the Honorable William Perry. What a fantastic moment when he told me that geeks like us hold the keys to the future of the Army!

So tomorrow it all comes to a close. We should ENDEX around noon. The TAC will be disassembled and prepared for the return to Hood. The EXFOR will come back into the dustbowl after three weeks of the best training available to any military unit. By the end of next week, most of the equipment will be on rail cars, and most soldiers back at Hood. Division XXI is next, and we start getting ready for round one as soon as we get back.

As for the OPFOR, well they have another rotation coming in a few weeks. I bet they will be glad to have a "conventional" opponent to train. Fort Irwin will back to normal.

TFXXI Day 38 (Saturday) THE LAST NOTE!, 29 Mar 1997

Whew! It's done. The last battle was a success for the EXFOR, and was terminated once it was determined that they had defeated the OPFOR's last push. Good fighting on both sides, and this time the friendly intel read of OPFOR movements was interpreted correctly by the EXFOR, who bobbed and swayed in sync with each swing and punch. The battle ended with both forces in the general vicinity of Four Corners (as predicted) around 0900 this morning.

It's always amazing to watch a group of soldiers that have been told to tear down a TOC. It took us over five weeks to "build" the TAC, and about five hours to completely tear it apart. That's called Moving with a Purpose. The same story was repeated across the box as the EXFOR also prepared to wrap this event up and go home.

This will be my last note from the NTC. I will now focus my attention to writing several AARs and information papers on what I saw here. I'll try to make as much of it public as possible. Please, no requests for personal copies of briefings, notes, and papers until after I get a chance to put my thoughts and ideas together. This may take a while. I've got lots of ideas to put on paper.

In closing out this journal, I'd like to say that it has been an absolute dream come true to be here and participate in what will go down in the history books as the most significant military experiment since the Louisiana Maneuvers in the 1930's. I realize that some of my notes have upset some people while at the same time making others proud. I have tried to be as accurate as possible in "reporting" what I observed here, and I hope that you have not minded the tone of language that I wrote in.

The future is now. C4I For The Warrior is a reality. From the sands of the National Training Center, see you in the 21st Century!

ms

Marcus H. Sachs

MAJ, Army Automator

4th Infantry Division

Chief, Division Automation Management Office

Digitizing the Dirt at the NTC

DSN 259-7696

sachsm@hood-emh3.army.mil