Common use of Build-Out Clause in Contracts

Build-Out. Sprint built a cell site near La Porte, Indiana that is in the Service Area. Manager built a cell site in Bryan, Ohio that is outside the Service Area. The Service Area will no longer include coverage in the (a) Battle Creek BTA that is a result of bordering cell sites in the Fort ▇▇▇▇▇ BTA and (b) Kalamazoo BTA that is a result of bordering cell sites in the Elkhart BTA. The parties have agreed to amend Exhibit 2.1 to delete from the Service Area the area where Sprint has a cell site near La Porte, Indiana and the areas in the Battle Creek and Kalamazoo BTAs and to add to the Service Area the area where the cell site in Bryan, Ohio is located. The narrative description and the coverage maps attached to this Addendum as Exhibit 2.1 supersede the narrative description and coverage maps of Exhibit 2.1 attached to Addendum IV of the Management Agreement. The table portion of Exhibit 2.1 is not being updated. The Parties agree that the 2.1 build-out language and the corresponding maps were created in Mapinfo and the geographic details of the boundaries for the Manager's Service Area were agreed upon by referencing a specific Mapinfo table encompassing Manager's entire Service Area. This Mapinfo table is dependent on other related files in order to fully represent the geographic boundary. All of these related files can be compressed into a MapInfo Interchange Format (MIF), which is an ASCII file format that can fully describe a MapInfo database/table. Both graphic and tabular data are exported into MIF files. The graphic data is in a file with a ".mif "extension, and the tabular data is in a file with an ".mid" extension. MapInfo Interchange Format (MIF) files can be translated into other formats with other standard mapping programs. The MIF and MID files are attached hereto and are the files which were used to create the attached reference map images for the Manager's Service Area and were agreed upon by the Parties. Any future disputes with regard to Manager's Service Area will be referenced to and resolved by the use of these files.

Build-Out. Sprint built wants to build a cell site near La Porte, Indiana that is in the Service AreaArea near Fort ▇▇▇▇▇▇▇, Nebraska and a cell site in the Service Area in Madison County, Iowa where Manager previously decommissioned a cell site. Manager has built a cell site in BryanValley, Ohio that is Nebraska outside the Service Area. The Service Area will no longer include coverage in the (a) Battle Creek BTA that is a result of bordering cell sites in the Fort ▇▇▇▇▇ BTA and (b) Kalamazoo BTA that is a result of bordering cell sites in the Elkhart BTA. The parties have agreed to amend Exhibit 2.1 to delete from the Service Area the area those areas where Sprint has a would like to build the two cell site near La Porte, Indiana and the areas in the Battle Creek and Kalamazoo BTAs sites and to add to the Service Area the location in Valley, Nebraska where Manager built a cell site and an area where the adjacent to an existing iPCS cell site in BryanAmes, Ohio is locatedIowa. The narrative description and the coverage maps attached to this Addendum as Exhibit 2.1 supersede the narrative description and coverage maps of Exhibit 2.1 attached to Addendum IV IX of the Management Agreement. The table portion of Exhibit 2.1 attached to Addendum IX of the Management Agreement is not being updated. The Parties agree that the 2.1 build-out language and the corresponding maps were created in Mapinfo and the geographic details of the boundaries for the Manager's Service Area were agreed upon by referencing a specific Mapinfo table encompassing Manager's entire Service Area. This Mapinfo table is dependent on other related files in order to fully represent the geographic boundary. All of these related files can be compressed into a MapInfo Interchange Format (MIF), which is an ASCII file format that can fully describe a MapInfo database/table. Both graphic and tabular data are exported into MIF files. The graphic data is in a file with a ".mif "extension, and the tabular data is in a file with an ".mid" extension. MapInfo Interchange Format (MIF) files can be translated into other formats with other standard mapping programs. The MIF and MID files are attached hereto and are the files which were used to create the attached reference map images for the Manager's Service Area and were agreed upon by the Parties. Any future disputes with regard to Manager's Service Area will be referenced to and resolved by the use of these files.