EIS_RFP_Section_B_Amendment_02.docx

Enterprise Infrastructure Solutions (EIS) Request for Proposals

Section B Supplies or Services and Prices/Costs

Issued by:

General Services Administration Office of Integrated Technology Services 1800 F St NW Washington, DC 20405

October 2015

Table of Contents

General Services Administration Network Services 2020 Enterprise Infrastructure Solutions

EIS RFP #QTA0015THA3003 Enterprise Infrastructure Solutions EIS RFP #QTA0015THA3003 190 Enterprise Infrastructure Solutions Appendix A

Appendix B Pricing Overview Overview This section defines price tables and other pricing mechanisms for the services and features described in Section C. All prices shall conform to the format and structure defined herein. Additional price elements not included in the defined format and structure are not permitted, except as defined in separate TOs awarded under this contract. All prices and price elements defined under this contract or defined under TOs shall conform to the pricing requirements, specifications, element definitions, and numbering schemes defined in this contract.

Contract prices and price tables define the permitted charges and charging schemes. Pricing mechanisms defined for TOs must be derived from (i.e., logically flow from) contract price tables. Examples of such price mechanisms and elements associated with TO pricing may include, but are not limited to, the following:

Pricing mechanisms identical to those in the contract, except for additional pricing discounts or reductions negotiated under the TO competition.

Prices for multiple contract elements or TO elements combined under a single price element (e.g., single price for service plus Service Related Equipment (SRE), so-called “solutions,” or a special labor skill need).

Pricing for services, SRE, or labor, that vary from the contract in some significant aspect, such as higher performance levels, additional features, or a special security service labor requirement.

Individual Case Basis (ICB) pricing.

Task Order Unique CLINs (TUCs).

All prices agreed to at the contract award are established for all contract users (e.g., agencies/customers). Agencies and/or customers are expected to conduct one or more fair opportunity actions that will result in the award of TOs under this contract.

Where price elements awarded under a TO differ from contract pricing, the contractor shall associate the TO number with each CLIN and price element awarded that differs from contract pricing. For more information, see Section B.1.2.16.

The contractor shall not process orders nor will the government pay invoices until the contractor has submitted these prices into GSA Systems (see Section J.2.9.5). The contractor shall submit to GSA a copy of the resulting TO for purposes of validating the orders, bills and invoices as defined in Section J.2.10.3.3. For a complete description of the ordering requirements, refer to Section G.3.

General Pricing Principles Pricing for telecommunications and networking services historically has been complex, due in large part to regulatory requirements. Simpler pricing approaches are expected for the future. Such pricing simplification is already being seen in residential and commercial pricing trends for combined services such as voice and data. Services based on legacy copper wire and circuit switching will be retired in the next few years. Accordingly, price tables and elements defined in this section reflect a hybrid of complex legacy and simpler modern pricing mechanisms. As providers retire legacy infrastructure, agencies will modernize their networks and applications, reducing pricing, ordering, and billing complexities. EIS seeks to provide an orderly path to future pricing by accommodating current legacy services pricing while allowing for the evolution of future services pricing toward greater flexibility and simplicity. This approach is expected to result in fewer pricing elements and greater pricing transparency.

Critical to the EIS approach is allowing (but not requiring) the network engineered access topography to be decoupled from pricing. This is accomplished by allowing common access prices to be defined for services and service groupings regardless of location or access engineering, which allows for fewer pricing points and simpler price structures. Legacy services may continue to be priced as in the past. Access pricing is described in Section B.2.9.

Service Areas, Services and References Service areas refer to collections of related telecommunications services, plus discrete areas to be priced such as labor and equipment. Services refer to the components of the service areas.

The following service areas are defined in Section C.2:

1. Data Service

1. Voice Service

1. Contact Center Service

1. Colocated Hosting Service

1. Cloud Service

1. Wireless Service

1. Commercial Satellite Communications Service

1. Managed Services

1. Access Arrangements

1. Service Related Equipment

1. Service Related Labor

1. Cable and Wiring The National Security and Emergency Preparedness service area is defined in Sections C.1.8.8 and G.11.

Table B.1.2.1.1 defines the structure for service areas and services. The table also defines which services are mandatory (to be included in the contractor’s proposal), and which services are optional. Refer also to Section C.2.1 for a discussion of mandatory and optional services.

Pricing Identification Structure

B.4.1.13, B.4.1.14

* Services identified with a Yes (One-sided) may only be provisioned in awarded CBSAs; services identified with “Yes” (Two-sided) may only be provisioned between two awarded CBSAs. Services identified with “No” may be provisioned where priced (e.g., CONUS, OCONUS, non-domestic).

** The contractor shall propose prices for at least one of the two Voice services. If prices for both are provided, the contractor shall indicate by CBSA which one the government is to regard as the mandatory service.

*** Access arrangements are required where the contractor proposes service. Section J.1.3 provides the geographic requirements for access.

B.1.1.1.1.1 CLINs and Features Each permissible individual pricing element is identified by a Contract Line Item Number (CLIN)[footnoteRef:2]. Each CLIN is a seven-character identifier, the first two characters of which identify the service, as shown in the Service CLIN Prefix column in Table B.1.2.1.1. The referenced subsections for each service contain further CLIN discussion and definitions. [2: Additional information may be required to determine a price; for example, location information is required to determine access prices (see Section B.2.9).]

Services, as defined in this contract for pricing purposes, may include “standard features” that do not have separate CLINs. Additional features may be separately identified, ordered, and priced. Such features are identified by a separate CLIN. Their prices may be zero (i.e., not separately priced (NSP)) or non-zero.

Features are addressed in the sections identified for each service in Table B.1.2.1.1.

Service Pricing Elements and Conditions All services will have either defined fixed prices or ICB price elements, except where previously unanticipated pricing types are needed, such as the following:

· A bandwidth that is not listed on the contract, but logically should be added and defined on the contract as a fixed price item. For example, if CLINs for 10 Mbps, 20 Mbps, and 40 Mbps are defined, but the agency requires a 30 Mbps CLIN, then this 30 Mbps CLIN shall be added to the contract with a fixed price prior to the TO.

· A bandwidth that is not listed on the contract, but logically should be added and defined on the contract with an ICB CLIN. For example, if CLINs for OC12 and OC192 access are defined, but the agency requires an OC48 access CLIN, then it shall be added to the contract prior to the TO.

· A new item that does not fall into any of the fixed or ICB CLINs for that service. In this instance, the agency and the contractor shall use the TUCs defined for the specific service. A new CLIN is not required for the contract. See Sections B.1.2.12 and B.1.2.15 for further information.

Any equipment, material, facility, labor, site preparation, training, or other service required in the performance of this contract for which a price is not specifically identified in the contract will be considered to be included in the price of another item or provided at no cost to the government, except as otherwise provided for in this contract or the applicable TO. The contractor may waive any charge at any time. No charges are permitted for interconnection with a government provided circuit at a contractor’s POP. Prices for any associated SRE shall be provided in accordance with Section B.2.10.

The following conditions also apply to prices and price structures:

· Prices shall be specified and billed in United States (U.S.) currency.

· Prices populated in Section B price tables shall have a maximum of two (2) decimal places, except for prices associated with CLINs that are priced using charging units of a particularly small measure (e.g., per minute, per six-second or per second), which shall have a maximum of six (6) decimal places. The maximum number of decimal places for each charging unit is defined in the price precision column of the “unit” reference table. In addition, at least six (6) decimal places shall be carried in all calculations up to final rounding. See Section J.2.5.1.6 for a discussion of rounding.

· All mandatory CLINs for mandatory services shall be offered by the contractor, including Individual Case Basis (ICB) items that will be instantiated as CLINs when priced. These mandatory ICB CLINs are not part of the contract as orderable CLINs until priced and added to the TO. Until then, these ICB CLINs represent place-holders for specific priced CLINs so that the service being proposed may be defined and associated with a unique identifier. ICB elements require additional information to fully specify the prices involved. This information shall be provided by the contractor in the format provided in GSA Systems. In this system, the contractor shall provide the anticipated CLIN, ICB Case Number, Case Description, Charging Unit, and, where applicable, the Network Site Code and Country Jurisdiction ID, in Table B.1.2.14.1. The Case Description shall contain sufficient information to distinguish one case from another of the same CLIN. Customers will use this description to assist in their evaluations.

· The ICB CLIN, Case Number, Description, Charging Unit, and Price are instantiated in the TO. The Case Number shall be unique for each CLIN and Case.

· Where service is distinguished between routine and critical, it is assumed that the fixed prices proposed are for routine service. Pricing for critical service levels will be obtained as specified in the TO. The critical service obtained in the TO will include one or more of the following:

· Existing diversity CLINs

· ICB CLINs

· TUCs

· If a contractor proposes optional services, it shall offer the mandatory CLINs associated with those services.

· Prices shall be fixed for all services, features, and labor for each applicable fiscal year within the contract period.

· All prices proposed shall exclude the Associated Government Fee (AGF).

Effective Pricing Dates The contractor shall maintain all price tables for the full contract period. All prices shall be binding at the time of the effective date of the contract. For prices that are effective later than contract award, the contractor shall define the day, month, and year in which the prices are to become effective. The contract shall be for a base period of 60 months, with two (2) option periods of 60 months each. Prices shall be specified for the base period. Pricing shall change only on the first day of the U.S. Government fiscal year, except as provided below.

All prices on a row of a price table shall carry a start date, which is when the prices on that row become effective and the service becomes available. These prices shall remain in effect through their listed price stop date or until the prices are changed by modification[footnoteRef:3]. When prices are revised by modification, the newly inserted rows shall include the start date(s) when the prices become effective. If a service is ordered for delivery on or after the price start date (but before the stop date) shown on the price table row, the contractor shall provide the service at the accepted price, subject to the conditions identified in Section J.1. [3: Modifications can take the form of contract modifications, TO-specific submissions, or catalog submissions.]

Thereafter, the billed price shall be obtained from the price table row within which the billing date is contained. The only exception to this rule is the SRE MRC, for which the billed price for the duration of the SRE MRC payment term is fixed at the time of the order. The same rules regarding price table row start dates and stop dates shall apply to the start dates and stop dates for all price tables (e.g., cross-reference tables, Point of Presence (POP) identification tables, and POP relationship tables). See Section B.4 for additional information. See Section J.4 for information on the modification process.

Price Banding Structures Some tables permit prices to be defined by bands (e.g., by distance or bandwidth). Each band is defined by a “Band Low” and a “Band High”. Where the contractor is permitted to define bands, the bands shall be contiguous with no overlapping bands or gaps between bands.

To ensure that bands are contiguous, each “Band High” shall be identical to the “Band Low” of the subsequent band. Using this convention, each band shall include the entire interval from “Band Low” up to, but not including, “Band High” except for the last band in a given table, where the “Band High” shall be included.

Price banding can be used for fixed price and variable price components applied separately or in combination in a given price table:

· With fixed price banding, the banded value serves as an index into the price table to select the correct row, and then the value in the fixed price column of that row is used as the CLIN price.

· With variable price banding, the banded value serves as an index into the price table to select the correct row, and then the value in the variable price column of that row is multiplied by the banded value to arrive at the CLIN price.

XX00001

XX00001

XX00001

In the example above, the fixed and variable price components are used in combination to calculate the MRC.

Assuming the quantity of CLIN XX00001 for the month is 10, then the price calculation for that CLIN is the fixed component for that band – $300 in this case, plus the variable component – in this case $80 per unit of the CLIN, or $800 for the month. The total price is $300 + $800 = $1,100.

Alternatively, if the quantity of CLIN XX00001 for the month is 250, then the price for that CLIN is $200 fixed, plus $50 per unit of the CLIN, or $12,500. The total price for this item is $200 + $12,500 = $12,700 for the month.

If the Variable Price column had not been included in the table above, then the MRCs would be $300 and $200, respectively. If the Fixed Price column had not been included in the table above, the MRCs would be $800 and $12,500, respectively.

Pricing Domestic and Non-Domestic Locations Prices for telecommunications services as defined in Table B.1.2.1.1 shall provide geographic coverage for domestic and non-domestic locations, as specified in Section J.1. Domestic wireline locations are further divided into CONUS and OCONUS as defined in Section J.12. Prices for wireline access for service at non-domestic locations, except as otherwise included in transport pricing, shall be provided in fixed price tables. Domestic wireless locations are defined in Section B.2.6.

No pass-through pricing shall be allowed for any service.

Non-domestic calls are classified as:

· Outbound – calls made from a domestic service delivery point (SDP) to a non-domestic location

· Inbound – calls made from a non-domestic location to a domestic location

· Non-domestic-to-non-domestic – calls made from one non-domestic location to another non-domestic location All non-ICB CLINs listed in price tables that do not have Country/Jurisdiction ID or Pricing Hub (PHub) ID columns shall apply to all locations, and shall be offered at the stated fixed price where offered commercially by the contractor. See Section J.1 for non-domestic coverage requirements.

Price Factors and CLINs The fixed prices for services may depend on a number of factors, including but not limited to:

1. Geographic location

1. Access type

1. Types of data service port requirements as defined in the individual service sections in Section C

1. Types of services and features provided

1. Distance[footnoteRef:4] [4: Where distance-sensitive pricing is provided in the form of distance bands, these distance bands shall be contiguous.]

The total basic service price for a connection will consist of various CLINs, with the number and types of CLINs being dependent on the mix of conditions associated with the service. Basic service prices will vary by service type and are described in more detail in the individual service pricing sections. Prices for services may include, but are not necessarily limited to, the following components:

1. Non-Recurring Charges (NRC) for access and priced features (see B.2.9 for access pricing)

1. Monthly Recurring Charges (MRC) for flat rate charges, cloud services, access, transport, and priced features

1. SRE charges

1. Service Related Labor charges

1. Usage-based charges for access, transport, cloud services, and priced features

1. ICB charges for customized or unique requirements. ICB prices are determined as needed and specified in TOs (see Section B.1.2.14).

Domestic access prices and domestic transport prices shall be unbundled except as otherwise provided (e.g., VPNS CLINs that bundle access with the transport, or CLIN bundling per Section B.1.2.12).

Use of Geographic Coordinates and POPs For domestic locations, all distance[footnoteRef:5] measurements shall be calculated using Vertical and Horizontal (V&H) coordinates. The V&H coordinates of a Physical Concentration Location (PCL), such as a serving wire center, fiber hotel or cable head, shall be provided by the contractor. The V&H coordinates of POPs shall be provided and maintained by the contractor. In tables and other documents prepared for the government, distances shall be reported in miles. [5: The distance between two locations shall be calculated in miles as:

Distance (miles) = ROUNDUP(SQRT(((V1-V2)^2+(H1-H2)^2)/10),0) Where (V1, H1) and (V2, H2) are the V and H coordinates of the locations, respectively.]

Price tables for transport (i.e., POP-to-POP transmission) for services are defined in the individual service subsections in Section B.2. Transport prices are for the transmission of information, including voice, data, video, and/or multimedia, across the network.

Domestic transport distance is measured between the POPs that are designated for the on-net or off-net locations. The price for transport between a domestic location and a non-domestic location or between a non-domestic location and another non-domestic location is computed on a country/jurisdiction-to-country/jurisdiction basis (except as otherwise provided for), with the locations in the domestic definition divided into separately identified regional groupings (each with its own Country/Jurisdiction ID for transport pricing purposes). See Table B.4.2.1.

The formats for domestic POPs and non-domestic POP locations are listed in Section B.4.1. Table B.4.1.5 identifies bandwidth groups available at each PCL and maps PCLs to POPs. No PCL shall map to more than one POP for any assigned bandwidth group. For each service provided at a POP in Table B.4.1.1, all bandwidth groups identified for that service shall be available at any PCL mapped to that POP for those bandwidth groups. Each POP shall provide all bandwidth groups from all PCLs mapped to that POP. POPs may be added or deleted at any time during the term of the contract; however, no increase in access arrangement pricing shall be permitted. The contractor shall give a minimum of six months’ notice of such a change, except in the case of emergency conditions.

Waiver of Charges The contractor may waive the application of any charges at any time during the contract period, including during transition to EIS.

Pricing Volume The contractor’s Pricing Volume shall be incorporated at award. The contractor shall provide updates throughout the life of the contract as needed to assure a clear, unambiguous understanding of pricing methods. Any significant change to the pricing methodology should be reflected. Examples include, but are not limited to:

· The introduction of new services

· Allowable changes to pricing methodologies

· End of Life services If the contractor fails to clearly define a pricing method for any service, then the government’s interpretation shall apply. Refer to Section F for other deliverable requirements.

Usage Based Charges The contractor shall round up usage based charges if the billable measurement exceeds the unit. For example, for usage billing in six-second increments, a seven-second call will round up usage to 12 seconds. For usage billing in one-minute increments, a 61 second call will be rounded up to two minutes for billing purposes.

Auto-Sold CLINs Some services include other CLINs that the contractor automatically includes with those services. For example, conferencing customers may request any of the features associated with a contractor’s specific conferencing services.

A comprehensive list of auto-sold CLINs (which may include catalog items) shall be incorporated into Table B.1.2.11.1. As new capabilities and features are added to the contract for the services that have auto-sold CLINs (such as Audio, Web and Video Conferencing), contractors shall update Table B.1.2.11.1.

Auto-Sold CLINs Table

* All CLINs within Section B that have auto-sold CLINs ** CLINs which are auto-sold with the base CLIN *** A row where the Task Order Number = -1 shall apply to all task orders. A row where the Task Order Number column is populated with a specific agency task order shall, for that task order only, disable the auto-sold relationship defined by that row.

CLIN Bundling Agencies may desire to combine multiple contract CLINs and/or TUCs into a single TUC. For example, an agency may wish to bundle a VPNS Port CLIN, MNS CLIN, and SRE into one combined CLIN. In these instances, the contractor shall provide items that have been combined for a specific TO in Table B.1.2.12.1, to facilitate the collection of the components necessary for an accurate inventory. A combined TUC shall not contain multiple component CLINs for transport (e.g., combining 50 Mbps VPNS with 100 Mbps VPNS), or multiple component CLINs for Access Arrangements. All component CLINs bundled into a single TUC must use the same billing frequency.

TUC Combined CLIN Component Table

* From the appropriate TUCs of the basic transport service for the combined CLIN set (e.g., VPNS) ** Component CLINs associated with the combined TUC. A separate row shall be used for each component CLIN *** Where applicable, otherwise “-1” **** Where applicable, otherwise null Adding CLINs Post-Award Contractors may submit proposals for contract modifications post-award (see Section J.4) and define new CLINs using Table B.1.2.13.1, which includes:

· Name – the description of the specific service provided under the CLIN

· Frequency – the billing frequency – “NRC”, “MRC” or “Usage”

· ICB – “T” if the CLIN is priced on an individual case basis, “F” otherwise

· NSP – “T” if the CLIN is not separately priced, “F” otherwise

· Unit ID – the charging unit ID from the “unit” reference table

· Notes – contains any additional information that might be useful to understand the service defined by the CLIN CLIN Table

Defining New ICB Cases Contractors shall define new ICB cases for which they submit pricing (see Section J.4). Contractors shall use Table B.1.2.14.1 to define ICB cases for TOs that use an ICB CLIN. Contractors shall ensure that NSCs and Country/Jurisdiction IDs in Table B.1.2.14.1 are the same as the values in the corresponding columns of the price table(s) used to price the CLIN and case number. Contractors shall populate the NSC and Country/Jurisdiction ID columns of Table B.1.2.14.1 with null values for cases where those location elements are not relevant.

General ICB Information Table

Jurisdiction ID Terminating Country/ Jurisdiction ID***

* For catalogs, this column is not used and shall be populated with “N/A” – the catalog description column takes precedence ** Used only when the price table specifically identifies the NSC as a Terminating NSC *** Used only when the price table specifically identifies the Country/Jurisdiction ID as a Terminating Country/Jurisdiction ID In CLIN Table B.1.2.13.1, the Unit ID for an ICB CLIN shall function as a placeholder or recommended charging unit until a specific ICB case is defined using General ICB Information Table B.1.2.14.1. If no recommended charging unit is readily apparent for the ICB CLIN, the contractor shall populate the Unit ID column of CLIN Table B.1.2.13.1 with “73” to designate the charging unit as ICB. When a specific case is defined using General ICB Information Table B.1.2.14.1, the Unit ID in Table B.1.2.14.1 shall determine the charging unit used to calculate the price for that case.

Task Order Unique CLINs As stated in Section B.1.2.2, TUCs are to be used for custom solutions not otherwise defined and priced on the contract. They allow services to be added for such solutions without requiring a contract modification. Only the TUCs that are predefined for each service shall be used by agencies for ordering. Three types of TUCs are typically defined per service: MRC, NRC, and usage-based. All TUCs are priced as ICB CLINs.

When agencies and contractors define the technical and performance requirements for a custom solution, they shall include ICB descriptions for any associated TUCs. Multiple TUCs may be specified on a TO.

TUCs are also used for CLIN bundling as described in Section B.1.2.12.

Task Order Number Columns Contractors shall populate the Task Order Number column of price tables with one of the following options:

· The value “-1” for contract pricing

· The specific agency TO number for TO-specific pricing Table Types Section B uses four types of tables to support service pricing. Two of the table types are maintained by the contractor and the other two are maintained by the government.

Contractor-Maintained Tables Price Tables contain prices by CLIN, TO number, date, and, where applicable, other pricing elements such as case number, location and price bands. Each price table specifies the pricing elements required for the particular service.

Supporting Tables do not contain prices but they contain other information that is required to price services. Examples include General ICB Information Table B.1.2.14.1, TUC Combined CLIN Component Table B.1.2.12.1, Auto-Sold CLINs Table B.1.2.11.1, and Services Offered by Point of Presence Table B.4.1.4.

Government-Maintained Tables Instruction Tables accompany the price tables throughout Section B and define the CLIN structures and charging mechanisms for the CLINs. In these tables, each CLIN is given a description of the service it provides and is assigned a billing frequency and a charging unit. The Notes column indicates if the CLIN is ICB, NSP or optional. CLINs are mandatory unless identified as optional in the Notes column. When multiple CLINs occupy the same row of an instruction table (e.g., NRC and MRC CLINs, or NRC, MRC and Usage CLINs):

· If a single charging unit is listed, it applies to all CLINs in that row.

· If the CLINs in that row do not share a common charging unit, the charging units will be listed separately and separated by semicolons.

· The information in the Notes column applies to all CLINs in that row unless stated otherwise.

Reference Tables contain information that is the same for all contractors. The government will maintain each reference table for contractors to access via GSA Systems. Examples include Country/Jurisdiction Identifications Table B.4.2.1 and Network Site Codes Table B.4.1.8.

Catalog Pricing Requirements - General For certain EIS services, contractors must develop and maintain catalog-style offerings as part of the pricing requirements. Following are the services for which catalog requirements exist, along with the section references where they are found:

· Cloud Service – Section B.2.5

· Wireless Service – Section B.2.6

· Commercial Mobile Satellite Service – Section B.2.7.1

· Managed Security Service – Section B.2.8.5

· Service Related Equipment – Section B.2.10 For each service that requires a catalog pricing approach as part of the overall service pricing, the contractor shall develop and maintain an online catalog that meets the general requirements specified in this section, and also the service-specific requirements found in the section associated with the service.

Requirements for Catalog Pricing Information Prices for catalog items shall be based on a discount from the Official List Price (OLP). OLP is a common term defined under EIS to include a variety of possible list price types or trade names. For example, if the catalog item is equipment not manufactured by the contractor, the OLP could be called, “Original Equipment Manufacturer’s Published List Price.” When the catalog item is a service provided by the contractor, the OLP could be called the contractor’s “Published List Price” for the service. Many other trade names may exist to identify the price to be associated with the OLP for a particular catalog item. The contractor shall provide the OLP trade name(s) that are associated with its catalog item OLPs for each catalog offering. Other specific pricing requirements, discount strategies and catalog elements unique to the catalog items are further defined in the service sections.

All pricing catalogs provided by the contractor shall contain, at a minimum, the data elements defined in the appropriate catalog pricing section and in Section B.1.2.14.

The contractor may organize its catalogs as it sees fit, subject to the following requirements:

· Catalog content and pricing shall be accessible by authorized users at any time (i.e., 24x7x365).

· Catalog content shall be organized logically, with features that enable common online browsing functions such as search and comparison.

· The online catalog shall meet the Section 508 requirements in Section C.4.

· The appropriate item identification shall be provided in the catalog to identify the catalog items being ordered (see individual sections for specific requirements).

· Contract prices and price-related information shall be provided to users who access the catalog (TO-specific prices need not be included).

· The contractor shall supply sufficient information to allow the government to verify the OLP and the accuracy of the item description in terms of capabilities and limitations, or other distinguishing characteristics, such as color, or other cosmetic features that could affect the price.

· All prices in catalogs shall be provided in U.S. dollars.

· Contract discounts offered shall not vary by geographic location. Additional discounts may be offered on TOs.

· Each Ccatalog items shall belong only to only a single discount class.

· Percentage discounts in class discount tables shall be specified as decimal values between 0 and 1, inclusive.

· The contractor shall keep catalog information up to date including, but not limited to, the OLP.

· If the OLP for a particular catalog item is not available, the price charged shall be agreed upon between the government and the ordering agency at the time of TO award. The contractor shall populate the OLP column with the agreed-upon price, populate the No List Price column with “T”, and specify a discount class that has a discount of zero.

· Price elements other than OLP shall be provided as appropriate and available.

· Additional information may be provided by the contractor in its catalog at its option.

Catalog Operational Rules The following operational conditions, or rules, shall apply to the contractor’s catalog for the term of the contract:

· The contractor shall be solely responsible for developing and maintaining its online catalog in accordance with the provisions of this contract.

· The catalog shall be accessible via the Internet under the access controls provided by the contractor.

· Authorized personnel shall be allowed access to the catalog at the direction of either the government or the contractor.

· For catalog-based services and equipment, only items listed in the contractor’s current catalog may be ordered.

· The catalog as provided at any given point in time during the term of the contract shall constitute the contractor’s official source of contract prices for items in the catalog.

· The contractor may change its catalog at any time at its option as follows:

An item shall be added by providing at least the minimum data elements required for that item as defined in each service section.

Discount classes for items shall only be added, removed, or changed via contract modification, except that TO-specific discount increases are permitted for any discount class at any time using the TO submission process (see Section J.4.1 for details).

Items and their associated data elements may be changed at any time, except for end-of-life items. Catalog item prices shall not be increased unless the increased price results from an increase in the OLP. Discounts shall not be decreased for items with a discount structure.

The contractor shall ensure that the OLP is current and shall only change the value in the OLP column for that purpose.

Where appropriate, items may be removed by being designated as end-of-life; users shall have the option of masking or viewing end-of-life items when viewing the catalog.

End-of-life items shall not be changed once designated as end-of-life.

All changes to the catalog shall be conveyed to the government as defined in Section J.4.2.

Termination of Support If the contractor desires to discontinue support for an item (for example, an item that will no longer be supported by the manufacturer), the contractor shall notify the GSA CO and any affected agencies at least 18 months before support is stopped (see Section B.2.10.7 for an exception for mobile devices). As appropriate, at time of notification, the contractor shall also recommend a solution acceptable to the government that ensures service continuity. The contractor shall continue to provide support for the existing item at the established price until a solution acceptable to the government is implemented by the contractor. Following notification of the GSA CO and affected agencies, the contractor shall no longer accept orders for the item.

Pricing Tables Data Service Virtual Private Network Service The technical requirements for Virtual Private Network Service (VPNS) are defined in Section C.2.1.1.

VPNS Price Structure The price structure for VPNS includes the following elements:

1. Transport Charges

2. (Optional) Transport with Embedded Access Charges

3. Feature Charges The pricing associated with a VPNS is dependent upon a number of factors, including the number of sites, bandwidth requirements, additional security services, and the type of access. Network design and engineering services can be provided using Service Related Labor CLINs as provided in Section B.2.11. SRE pricing for the user-to-network interfaces shall be provided in accordance with Section B.2.10.

VPNS Access Pricing for access arrangements is described in Section B.2.9. Access includes wireline, Ethernet, wireless, and satellite. Remote VPNS access (e.g., DSL, Cable) shall be ordered via a TUC.

As an option, specific shared Ethernet and Satellite access speeds may be acquired as embedded with the port for a combined price.

For embedded access, the speed of the access component shall equal or exceed the speed of the port with which it is embedded.

Table B.2.1.1.3.3 provides the pricing instructions for embedded access.

VPNS Transport All configurations of Quality of Service (QoS) are defined in Section C.2.1.1.1.4. Capabilities #7, #8, and #9 shall be included in the port price (i.e., NSP). Since QoS is also ICB, a case number shall be assigned for each port purchase and a description shall be provided of how the port will be configured.

All network security services are defined in Section C.2.1.1.1.4. Capabilities #2, #3, and #4 shall be included in the port price (i.e., NSP).

Table B.2.1.1.3.1 provides the format for pricing VPNS ports, ports with embedded access, and QoS. Tables B.2.1.1.3.2, B.2.1.1.3.3 and B.2.1.1.3.4 provide the pricing instructions.

VPNS Port Prices Table

Jurisdiction ID**

Start Date Price Stop Date

* Case Number applies to ICB CLINs only ** Country/Jurisdiction IDs are provided in Table B.4.2.1 VPNS Port Pricing Instructions Table

Non-domestic only

Non-domestic only

1 Mbps ≤ committed bandwidth < 10 Mbps

10 Mbps ≤ committed bandwidth < 100 Mbps

100 Mbps ≤ committed bandwidth < 1 Gbps

1 Gbps ≤ committed bandwidth < 10 Gbps

Because agencies have differing interests for balancing budgetary control against ordering complexity, Table B.2.1.1.3.2 includes two mandatory pricing mechanisms for achieving dynamic bandwidth: scalable bandwidth and burstable bandwidth.

Scalable bandwidth is ordered in anticipation of a future, temporary need for increased capacity. A scalable Ethernet transport MRC CLIN shall guarantee a committed bandwidth while ensuring the availability of the increased capacity. An Ethernet Bandwidth-on-Demand usage CLIN shall provide the increased capacity and must be ordered for the period of time during which the increased capacity will be required. An example of a valid CLIN pairing is Ethernet Bandwidth-on-Demand CLIN VN21002 used with scalable Ethernet transport CLIN VN20004.

Burstable bandwidth allows an agency to subscribe to a bandwidth commitment that is less…