SOW_-_Attachment_C_-_Data_Elements.pdf

ATTACHMENT C– DATA ELEMENTS

This attachment describes the key data elements for export and import. See the Software Requirements, Auction Setup and Reporting sections in the SOW. This information is subject to change depending on the capabilities and requirements of the new bidding system.

1 Export Data Elements

This information may be made available via an API or web service call. The final process and approval of that process will be defined as part of the implementation and integration services.This information is subject to change depending on the capabilities and requirements of the new bidding system.

1.1 Applicant Data

Applicant data includes applicant FRN (FCC Registration Number), name and address,initial eligibility, and other information that may be needed by the bidding system. The table below contains the recommended format.

Attribute Name Data Type Description application_id numeric(9,0) The unique application ID auction_id smallint The auction ID frn varchar(10) The applicant FRN applicant_company varchar(50) The applicant name applicant_address1 varchar(60) Applicant address line 1 applicant_address2 varchar(60) Applicant address line 2 applicant_city varchar(20) Applicant city applicant_state char(2) Applicant state applicant_zip_code char(9) Applicant zip code applicant_email varchar(50) Applicant email address initial_eligibility numeric(13,0) The applicant’s initial eligibility (in bidding units)

1.2 Applicant Contact Data

Applicant contact data includes information about the applicant contact, such as name and address. The table below contains the recommended format.

Attribute Name Data Type Description contact_id numeric(9,0) The unique contact ID application_id numeric(9,0) The unique application ID auction_id smallint The auction ID contact_title varchar(30) The contact title contact_fname varchar(20) The contact first name contact_mi char(1) The contact middle initial

Attribute Name Data Type Description contact_lname varchar(20) The contact last name contact_suffix char(3) The contact suffix applicant_address1 varchar(60) Applicant address line 1 applicant_address2 varchar(60) Applicant address line 2 applicant_city varchar(20) Applicant city applicant_state char(2) Applicant state applicant_zip_code char(9) Applicant zip code applicant_email varchar(50) Applicant email address contact_phone varchar(10) The contact phone number contact_ext char(7) The contact extension contact_fax varchar(10) The contact fax number contact_email varchar(50) The contact email address contact_country char(2) The contact country (address)

1.3 Authorized Bidder Data

Authorized bidder data includes the names of individuals authorized to place bids on behalf of the applicant/bidder. The table below contains the recommended format.

Attribute Name Data Type Description auth_bidder_id numeric(9,0) The unique authorized bidder ID application_id numeric(9,0) The unique application ID auction_id smallint The auction ID auth_bidder_fname varchar(20) The authorized bidder first name auth_bidder_contact_mi char(1) The authorized bidder middle initial auth_bidder_lname varchar(20) The authorized bidder last name auth_bidder_suffix char(3) The authorized bidder suffix

1.4 Item Data

Item data includes the auction inventory – the license, permits, or other items being auctioned.

NOTE: The current auction bidding system allows for several user-defined data elements which can be used to further define or classify an item. The current auction bidding system can be configured to allow bidders to filter items based on the user-defined data elements.

Attribute Name Data Type Description

Item_id numeric(9,0) The unique item ID auction_id smallint The auction ID item_desc varchar(40) The item description item_name varchar(20) The unique item name (unique within an auction) bid_units numeric(13,0) The number of bidding units associated with the item mob money The minimum opening bid amount (in dollars) package_ind char(1) The package bidding indicator (‘Y’ = can be packaged;

‘N’= cannot be packaged) reserved_ind char(1) The entrepreneur/closed bidding indicator (‘Y’ = can available to applicants with entrepreneur eligibility) bc_group_id tinyint An ID representing the bidding credit group uda_1 varchar(30) User‐defined attribute 1 uda_2 varchar(30) User‐defined attribute 2 uda_3 varchar(30) User‐defined attribute 3 uda_4 varchar(30) User‐defined attribute 4 uda_5 varchar(30) User‐defined attribute 5 uda_6 varchar(30) User‐defined attribute 6 uda_7 varchar(30) User‐defined attribute 7 uda_8 varchar(30) User‐defined attribute 8 uda_9 varchar(30) User‐defined attribute 9 uda_10 varchar(30) User‐defined attribute 10 allow_withdraw_ind char(1) Indicates whether or not the item can be withdrawn (‘Y’ = item can be withdrawn) allow_drop_ind char(1) Indicates whether or not the item can be dropped (‘Y’ = item can be dropped) tier_level tinyint The item tier‐level, used for certain package bidding auctions

1.5 Item Selection Data

Item selection data contains a list of items on which each bidder is allowed to place bids. The table below contains the proposed format.

Attribute Name Data Type Description application_id numeric(9,0) The applicant (or bidder) ID item_id numeric(9,0) The unique item ID bc_pct numeric(5,4) The bidding credit associated with the particular item (e.g., 0.35) item_desc varchar(40) The bidder‐specific item description, used for Media non‐ table service auctions item_name varchar(20) The item name

2 Import Data Elements

This section describes data that the Commission will need to have available at the close of an auction. As stated in the previous section, this information will likely be made available via an API or web service call. This information is the minimum required.

2.1 Round Data

Round data includes information about the rounds conducted during an auction, such as the date and time a round opened, and the date and time a round closed. The table below contains the recommended format.

Attribute Name Data Type Description auction_id smallint The auction ID round_num smallint The round number round_open smallint The date/time on which the round opened round_close smallint The date/time on which the round closed round_completed_ind char(1) Indicates whether or not round results completed for a given round

2.2 Bid Data

Bid data includes all bids placed during an auction. The table below contains the data elements required;

however, these specifications could change depending on the bidding system’s ability to provide this information.

Attribute Name Data Type Description auction_id smallint The auction ID bidder_id numeric(9,0) The unique bidder ID bip_id numeric(9,0) The unique BIP id

For package bidding auctions, the BIP could relate to a single item, or a collection of items (“package”).

round_num smallint The round number bid_amt money The bid amount (in dollars) net_bid_amt money The net bid amount (in dollars) bid_amt_num tinyint The bid increment number bid_date datetime The bid date/time last_action_date datetime The date on which the bid was last updated bid_status char(1) The bid status (Submitted, Removed, Withdrawn) withdrawal_round_num smallint The round number in which a bid was withdrawn drop_round_num smallint The round number in which a bid was dropped unit_bid_amt money The unit bid amount; used for Mobility Fund auctions net_unit_bid_amt money The net unit bid amount; used for Mobility Fund auctions

2.3 Winning Bid Data

Winning bid data, also known in the Commission’s current auction bidding system as “provisionally winning bids”, will need to be available for import at the close of an auction. The table below contains the data elements required.

auction_id smallint The auction ID bidder_id numeric(9,0) The unique bidder ID bip_id numeric(9,0) The unique BIP ID bid_id numeric(9,0) The unique bid ID round_num smallint The provisionally winning bid round number

2.4 BIP, Bidder BIP Data

BIP (biddable item or package) data will need to be provided from the new bidding system. Detailed specificationswill be provided once the new bidding system’s capabilities are made available.

2.5 Bidder Eligibility, by Round

Bidder eligibility data is tracked by round, and should be provided at the close of an auction. The table below contains the proposed data elements, subject to change as more information is obtained about the new bidding system.

Attribute Name Data Type Description auction_id smallint The auction ID bidder_id numeric(9,0) The unique bidder ID round_num smallint The round number open_activity numeric(13) The bidder’s activity when the round opened open_elig numeric(13) The bidder’s eligibility when the round opened required_activity numeric(13) The bidder’s required activity current_activity numeric(13) The bidder’s activity when the round closed current_elig numeric(13) The bidder’s eligibility when the round closed bid_cnt int The number of bids placed consdrd_cnt int The number of considered bids max_dollar_exp money The bidder’s maximum dollar exposure rmng_withdrawals tinyint The number of withdrawal rounds remaining rmng_waivers tinyint The number of waivers remaining withdrawn_ind char(1) Indicates whether or not a bidder placed a withdrawal in the round rmng_drop_rounds tinyint The number of drop bids remaining

2.6 Bid Control, Round Control, Post Round Control Data

The current auction bidding system stores parameters that control the behavior of the bidding system in a various database tables. For example, the BID_CONTROL table stores the number of packages allowed in an auction; the maximum number of watchlists allowed by a bidder; and the maximum number of withdrawal rounds. The ROUND_CONTROL table stores parameters that can change from round to round, such as the minimum acceptable bid floor, or the percentage used to calculate bidder activity. The

POST_ROUND_CONTROL table stores additional parameters needed by IRP (Inter-Round Processing) and the solver.

Detailed specifications will be provided once the new bidding system’s capabilities are made available.