MAS - Advantaged Solutions, LLC - 47QTCA22D004D

1 | P a g e

AUTHORIZED

SPECIAL ITEM NUMBERS OFFERED:

Special Item No. 511210, 54151, 518210C, 54151S

Note: All non-professional labor categories must be incidental to and used solely to support hardware, software and/or professional services, and cannot be purchased separately.

ADVANTAGED SOLUTIONS, INC.

POC: ERIC FERNANDEZ

1300 PENNSYLVANIA AVE NW

SUITE 700

WASHINGTON, DC 20004-3024

PHONE: 202-204-3083

Pricelist current through Modification # PS-0021, dated 02/14/25.

Other than Small Business

On-line access to contract ordering information, terms and conditions, up-to-date pricing, and the option to create an electronic delivery order are available through GSA Advantage!, a menu-driven database system. The Internet address GSA Advantage! Is: GSAAdvantage.gov.

For more information on ordering from Federal Supply Schedules click on the FSS Schedules button at fss.gsa.gov.

2 | P a g e

SPECIAL ITEM NUMBER 511210- Software License

SubSIN Categorie(s):

FSC/PSC Class 7030 ADP SOFTWARE

• Ancillary Financial Systems Software

• Application Software • Communications Software

• Core Financial Mangement Software

• Electronic Commerce (EC) Software

• Large Scale Computers

• Microcomputers

• Operating System Software

• Special Physical, Visual, Speech, and Hearing Aid Software. Provide specific information.

• Utility Software

SPECIAL ITEM NUMBER 54151 Software Maintenance Services

FSC/PSC Class J070 MAINT/REPAIR/REBUILD OF EQUIPMENT- ADP EQUIPMENT/SOFTWARE/SUPPLIES/SUPPORT EQUIPMENT • Maintenance of Software

SPECIAL ITEM NUMBER 518210C Cloud and Cloud-Related IT Professional Services

FSC/PSC Class D305 IT AND TELECOM- TELEPROCESSING, TIMESHARE, AND CLOUD COMPUTING • Cloud Computing Services

SPECIAL ITEM NUMBER 54151S- INFORMATION TECHNOLOGY PROFESSIONAL SERVICES

FSC/PSC Class D399 IT AND TELECOM- OTHER IT AND TELECOMMUNICATIONS • Other Information Technology Services, Not Elsewhere Classified

SPECIAL ITEM NUMBER - OLM

Order-Level Materials (OLM) OLMs are supplies and/or services acquired in direct support of an individual task or delivery order placed against a Federal Supply Schedule (FSS) program contract or BPA. OLM pricing is not established at the FSS contract, but at the order level. Since OLMs are identified and acquired at the order or BPA level, the ordering contracting officer (OCO) is responsible for making a fair and reasonable price determination for all OLMs using FAR 15.404 techniques for commercial price determinations. Using this procedure, ancillary supplies and services that are unknown at the time of the Schedule contract award may be included and priced at the order level or BPA level.

3 | P a g e

Contract Number:

Period Covered by Contract:

ADVANTAGED SOLUTIONS, INC.

1300 PENNSYLVANIA AVE NW

SUITE 700

WASHINGTON, DC 20004-3024

PHONE: 202-204-3083

47QTCA-22-D-0004

8 February 2022 – 7 February 2027

4 | P a g e

TABLE OF CONTENTS

BLANKET PURCHASE AGREEMENTS……………………………………………8

CONTRACTOR TEAM ARRANGEMENTS………………………………………11

TERMS and CONDITIONS…………………………………………………………12

PRODUCT PRICING….……………………………………………………………P 1

SERVICES PRICING….……………………………………………………………S 1

5 | P a g e

CUSTOMER INFORMATION:

1. Awarded Special Item Number(s):

SIN Description

511210 Software License

54151 Software Maintenance Services

518210C Cloud and Cloud-Related IT Professional Services

54151S IT Professional Services

1b. Identification of the lowest priced labor category description, job title # and hourly rate awarded under the contract is: See Price list

2. Maximum Order: $500,000 per SIN – For SINs 511210,54151,518210C, 54151S

3. Minimum Order: $100

4. Geographic Scope of Coverage: The Geographic Scope of Coverage is Domestic Delivery. This is delivery within the 48 contiguous states, Alaska, Hawaii, Puerto Rico, Washington, DC, and U.S.

Territories. Domestic delivery also includes a port or consolidation point, within the aforementioned areas, for orders received from overseas activities.

5. Points of Production: USA

6. Discount from list prices or statement of net price: See Price list

7. Quantity Discount: SAP only SIN 511210, 54151 (30.25%>/equal to $650,000 to $1,000,000 orders

8. Prompt Payment Terms: Net 30 Days

9. A. Notification that Government purchase cards are accepted at or below the micro-purchase threshold: Government Purchase Cards will be accepted however no additional discounts will apply under the contract.

B. Notification whether Government purchase cards are accepted or not accepted above the micro-purchase threshold: Government Purchase Cards will be accepted however no additional discounts will apply under the contract.

10. Foreign Items: No foreign items are awarded under this contract.

11. Normal Delivery Terms – 30 DARO

6 | P a g e

11b. Expedited Delivery Terms: Contact Contractor

11c. Overnight/2-Day Delivery Terms: Contact Contractor

11d. Urgent Requirements: When the Federal Supply Schedule contract delivery period does not meet the bona fide urgent delivery requirements of an ordering activity, ordering activities are encouraged, if time permits, to contact the Contractor for the purpose of obtaining accelerated delivery. The Contractor shall reply to the inquiry within 3 workdays after receipt. (Telephonic replies shall be confirmed by the Contractor in writing.) If the Contractor offers an accelerated delivery time acceptable to the ordering activity, any order(s) placed pursuant to the agreed upon accelerated delivery time frame shall be delivered within this shorter delivery time and in accordance with all other terms and conditions of the contract.

12. FOB Point: Destination

13. Ordering Address:

14. Payment Address:

Advantaged Solutions, Inc 1300 Pennsylvania Ave NW Ste 700 Washington, DC 20004

Advantaged Solutions, Inc 1300 Pennsylvania Ave NW Ste 700 Washington, DC 20004

7 | P a g e

15. Warranty/Guarantee Provisions: All services performed under this contract will be guaranteed to completed in a satisfactory workmanlike manner as delineated with this Authorized FSS IT Schedule Pricelist.

16. Export Packing Charges: Export Packing is not offered under this contract.

17. Terms and conditions of Government purchase card acceptance (any thresholds above the micro-purchase level): Accepted

18. Terms and conditions of rental, maintenance, and repair (if applicable): Not applicable

19. Terms and conditions of installation (if applicable): Not Applicable

20. Terms and conditions of repair parts indicating date of parts price lists and any discounts from list prices (if applicable). Not applicable a)Terms and conditions for any other services (if applicable): Not applicable

21. List of service and distribution points (if applicable): Not applicable

22. List of Participating dealers (if applicable): Not applicable

23. Preventive maintenance (if applicable): Not applicable

24. Special attributes such as environmental attributes (e.g. recycled content, energy efficiency, and/or reduced pollutants): Not applicable

b. If applicable, indicate that Section 508 compliance information is available on Electronic and information Technology (EIT) supplies and services and show where full details can be found(e.g.

contractor’s website or other location) The EIT standards can be found at www.Section508.gov/. :

Not applicable

25. Data Universal Numbering System (DUNS) Number: 190169610

26. Advantaged Solutions, Inc is currently registered within the System for Award Management (SAM) database.

8 | P a g e

BEST VALUE

BLANKET PURCHASE AGREEMENT

FEDERAL SUPPLY SCHEDULE

(Insert Customer Name)

In the spirit of the Federal Acquisition Streamlining Act (ordering activity) and (Contractor) enter into a cooperative agreement to further reduce the administrative costs of acquiring commercial items from the General Services Administration (GSA) Federal Supply Schedule Contract(s) ____________________.

Federal Supply Schedule contract BPAs eliminate contracting and open market costs such as: search for sources; the development of technical documents, solicitations and the evaluation of offers. Teaming Arrangements are permitted with Federal Supply Schedule Contractors in accordance with Federal Acquisition Regulation (FAR) 9.6.

This BPA will further decrease costs, reduce paperwork, and save time by eliminating the need for repetitive, individual purchases from the schedule contract. The end result is to create a purchasing mechanism for the ordering activity that works better and costs less.

Signatures

Ordering Activity Date Contractor Date

9 | P a g e

BPA NUMBER_____________

(CUSTOMER NAME)

BLANKET PURCHASE AGREEMENT

Pursuant to GSA Federal Supply Schedule Contract Number(s)____________, Blanket Purchase Agreements, the Contractor agrees to the following terms of a Blanket Purchase Agreement (BPA) EXCLUSIVELY WITH (ordering activity):

(1) The following contract items can be ordered under this BPA. All orders placed against this BPA are subject to the terms and conditions of the contract, except as noted below:

MODEL NUMBER/PART NUMBER *SPECIAL BPA DISCOUNT/PRICE

(2) Delivery:

DESTINATION DELIVERY SCHEDULES / DATES

(3) The ordering activity estimates, but does not guarantee, that the volume of purchases through this agreement will be

(4) This BPA does not obligate any funds.

(5) This BPA expires on _________________ or at the end of the contract period, whichever is earlier.

(6) The following office(s) is hereby authorized to place orders under this BPA:

OFFICE POINT OF CONTACT

(7) Orders will be placed against this BPA via Electronic Data Interchange (EDI), FAX, or paper.

(8) Unless otherwise agreed to, all deliveries under this BPA must be accompanied by delivery tickets or sales slips that must contain the following information as a minimum:

(a) Name of Contractor;

(b) Contract Number;

(c) BPA Number;

(d) Model Number or National Stock Number (NSN);

(e) Purchase Order Number;

(f) Date of Purchase;

10 | P a g e

(g) Quantity, Unit Price, and Extension of Each Item (unit prices and extensions need not be shown when incompatible with the use of automated systems; provided, that the invoice is itemized to show the information); and

(h) Date of Shipment.

(9) The requirements of a proper invoice are specified in the Federal Supply Schedule contract. Invoices will be submitted to the address specified within the purchase order transmission issued against this BPA.

(10) The terms and conditions included in this BPA apply to all purchases made pursuant to it. In the event of an inconsistency between the provisions of this BPA and the Contractor’s invoice, the provisions of this BPA will take precedence.

11 | P a g e

BASIC GUIDELINES FOR USING

“CONTRACTOR TEAM ARRANGEMENTS”

Federal Supply Schedule Contractors may use “Contractor Team Arrangements” (see FAR 9.6) to provide solutions when responding to a ordering activity requirements.

These Team Arrangements can be included under a Blanket Purchase Agreement (BPA). BPAs are permitted under all Federal Supply Schedule contracts.

Orders under a Team Arrangement are subject to terms and conditions or the Federal Supply Schedule Contract.

Participation in a Team Arrangement is limited to Federal Supply Schedule Contractors.

Customers should refer to FAR 9.6 for specific details on Team Arrangements.

Here is a general outline on how it works:

The customer identifies their requirements.

Federal Supply Schedule Contractors may individually meet the customers needs, or -

Federal Supply Schedule Contractors may individually submit a Schedules “Team Solution” to meet the customer’s requirement.

Customers make a best value selection.

12 | P a g e

TERMS AND CONDITIONS APPLICABLE TO SOFTWARE LICENSES (SPECIAL ITEM NUMBER 511210) AND MAINTENANCE AS A SERVICE (SPECIAL ITEM NUMBER 54151) OF GENERAL PURPOSE COMMERCIAL INFORMATION TECHNOLOGY

SOFTWARE

1. INSPECTION/ACCEPTANCE

The Contractor shall only tender for acceptance those items that conform to the requirements of this contract. The ordering activity reserves the right to inspect or test any software that has been tendered for acceptance. The ordering activity may require repair or replacement of nonconforming software at no increase in contract price. The ordering activity must exercise its post acceptance rights (1) within a reasonable time after the defect was discovered or should have been discovered; and (2) before any substantial change occurs in the condition of the software, unless the change is due to the defect in the software.

2. ENTERPRISE USER LICENSE AGREEMENTS REQUIREMENTS (EULA)

The Contractor shall provide all Enterprise User License Agreements in an editable Microsoft Office (Word) format.

3. GUARANTEE/WARRANTY

a. Unless specified otherwise in this contract, the Contractor’s standard commercial guarantee/warranty as stated in the contract’s commercial pricelist will apply to this contract. See SCW.

b. The Contractor warrants and implies that the items delivered hereunder are merchantable and fit for use for the particular purpose described in this contract. If no implied warranties are given, an express warranty of at least 60 days must be given in accordance with FAR 12.404(b)(2)

c. Limitation of Liability. Except as otherwise provided by an express or implied warranty, the Contractor will not be liable to the ordering activity for consequential damages resulting from any defect or deficiencies in accepted items.

4. TECHNICAL SERVICES

The Contractor, without additional charge to the ordering activity, shall provide a hot line technical support number____for the purpose of providing user assistance and guidance in the implementation of the software. The technical support number is available from______to ___________________.

5. SOFTWARE MAINTENANCE

a. Software maintenance as it is defined: (select software maintenance type) :

(1) _____ Software Maintenance as a Product (SIN 511210)

Software maintenance as a product includes the publishing of bug/defect fixes via patches and updates/upgrades in function and technology to maintain the operability and usability of the software product. It may also include other no charge support that is included in the purchase price of the product in the commercial marketplace. No charge support includes items such as user blogs, discussion forums, on-line help libraries and FAQs (Frequently Asked Questions), hosted chat rooms, and limited telephone, email and/or web-based general technical support for user’s self-diagnostics.

Software maintenance as a product does NOT include the creation, design, implementation, integration, etc. of a software package.

These examples are considered software maintenance as a service.

Software Maintenance as a product is billed at the time of purchase.

(2) _____ Software Maintenance as a Service (SIN 54151)

13 | P a g e

Software maintenance as a service creates, designs, implements, and/or integrates customized changes to software that solve one or more problems and is not included with the price of the software. Software maintenance as a service includes person-to-person communications regardless of the medium used to communicate: telephone support, on- line technical support, customized support, and/or technical expertise which are charged commercially. Software maintenance as a service is billed arrears in accordance with 31U.S.C. 3324.

Software maintenance as a service is billed in arrears in accordance with 31 U.S.C. 3324.

b. Invoices for maintenance service shall be submitted by the Contractor on a quarterly or monthly basis, after the completion of such period. Maintenance charges must be paid in arrears (31 U.S.C. 3324). PROMPT PAYMENT DISCOUNT, IF APPLICABLE, SHALL

BE SHOWN ON THE INVOICE.

6. PERIODS OF MAINTENANCE (SIN 54151)

a. The Contractor shall honor orders for periods for the duration of the contract period or a lessor period of time.

b. Term licenses and/or maintenance may be discontinued by the ordering activity on thirty (30) calendar days written notice to the Contractor.

c. Annual Funding. When annually appropriated funds are cited on an order for term licenses and/or maintenance, the period of the term licenses and/or maintenance shall automatically expire on September 30 of the contract period, or at the end of the contract period, whichever occurs first. Renewal of the term licenses and/or maintenance orders citing the new appropriation shall be required, if the term licenses and/or maintenance is to be continued during any remainder of the contract period.

d. Cross-Year Funding Within Contract Period. Where an ordering activity’s specific appropriation authority provides for funds in excess of a 12 month (fiscal year) period, the ordering activity may place an order under this schedule contract for a period up to the expiration of the contract period, notwithstanding the intervening fiscal years.

e. Ordering activities should notify the Contractor in writing thirty (30) calendar days prior to the expiration of an order, if the term licenses and/or maintenance is to be terminated at that time. Orders for the continuation of term licenses and/or maintenance will be required if the term licenses and/or maintenance is to be continued during the subsequent period. **The phrase, “Term Licenses and/or Maintenance” in the preceding paragraphs may need to be revised in order to be consistent with the Offeror’s proposal; e.g., if only software maintenance is offered, all references to “term licenses” should be deleted from the preceding paragraphs.**

7. CONVERSION FROM TERM LICENSE TO PERPETUAL LICENSE

a. The ordering activity may convert term licenses to perpetual licenses for any or all software at any time following acceptance of software. At the request of the ordering activity the Contractor shall furnish, within ten (l0) calendar days, for each software product that is contemplated for conversion, the total amount of conversion credits which have accrued while the software was on a term license and the date of the last update or enhancement.

b. Conversion credits which are provided shall, within the limits specified, continue to accrue from one contract period to the next, provided the software remains on a term license within the ordering activity.

c. The term license for each software product shall be discontinued on the day immediately preceding the effective date of conversion from a term license to a perpetual license.

d. The price the ordering activity shall pay will be the perpetual license price that prevailed at the time such software was initially ordered under a term license, or the perpetual license price prevailing at the time of conversion from a term license to a perpetual license, whichever is the less, minus an amount equal to % of all term license payments during the period that the software was under a term license within the ordering activity.

8. TERM LICENSE CESSATION

a. After a software product has been on a continuous term license for a period of * months, a fully paid-up, non-exclusive, perpetual license for the software product shall automatically accrue to the ordering activity. The period of continuous term license for automatic accrual of a fully paid-up perpetual license does not have to be achieved during a particular fiscal year; it is a written Contractor commitment which continues to be available for software that is initially ordered under this contract, until a fully paid-up perpetual license accrues to the ordering activity. However, should the term license of the software be discontinued before the specified period of

14 | P a g e the continuous term license has been satisfied, the perpetual license accrual shall be forfeited. **Each separately priced software product shall be individually enumerated, if different accrual periods apply for the purpose of perpetual license attainment.**

b. The Contractor agrees to provide updates and maintenance service for the software after a perpetual license has accrued, at the prices and terms of Special Item Number l32-34, if the licensee elects to order such services. Title to the software shall remain with the Contractor.

9. UTILIZATION LIMITATIONS - (SIN 511210, AND SIN 54151)

a. Software acquisition is limited to commercial computer software defined in FAR Part 2.101.

b. When acquired by the ordering activity, commercial computer software and related documentation so legend shall be subject to the following:

(1) Title to and ownership of the software and documentation shall remain with the Contractor, unless otherwise specified.

(2) Software licenses are by site and by ordering activity. An ordering activity is defined as a cabinet level or independent ordering activity. The software may be used by any subdivision of the ordering activity (service, bureau, division, command, etc.) that has access to the site the software is placed at, even if the subdivision did not participate in the acquisition of the software. Further, the software may be used on a sharing basis where multiple agencies have joint projects that can be satisfied by the use of the software placed at one ordering activity's site. This would allow other agencies access to one ordering activity's database. For ordering activity public domain databases, user agencies and third parties may use the computer program to enter, retrieve, analyze and present data. The user ordering activity will take appropriate action by instruction, agreement, or otherwise, to protect the Contractor's proprietary property with any third parties that are permitted access to the computer programs and documentation in connection with the user ordering activity's permitted use of the computer programs and documentation. For purposes of this section, all such permitted third parties shall be deemed agents of the user ordering activity.

(3) Except as is provided in paragraph 8.b(2) above, the ordering activity shall not provide or otherwise make available the software or documentation, or any portion thereof, in any form, to any third party without the prior written approval of the Contractor.

Third parties do not include prime Contractors, subcontractors and agents of the ordering activity who have the ordering activity's permission to use the licensed software and documentation at the facility, and who have agreed to use the licensed software and documentation only in accordance with these restrictions. This provision does not limit the right of the ordering activity to use software, documentation, or information therein, which the ordering activity may already have or obtains without restrictions.

(4) The ordering activity shall have the right to use the computer software and documentation with the computer for which it is acquired at any other facility to which that computer may be transferred, or in cases of Disaster Recovery, the ordering activity has the right to transfer the software to another site if the ordering activity site for which it is acquired is deemed to be unsafe for ordering activity personnel; to use the computer software and documentation with a backup computer when the primary computer is inoperative;

to copy computer programs for safekeeping (archives) or backup purposes; to transfer a copy of the software to another site for purposes of benchmarking new hardware and/or software; and to modify the software and documentation or combine it with other software, provided that the unmodified portions shall remain subject to these restrictions.

(5) "Commercial Computer Software" may be marked with the Contractor's standard commercial restricted rights legend, but the schedule contract and schedule pricelist, including this clause, "Utilization Limitations" are the only governing terms and conditions, and shall take precedence and supersede any different or additional terms and conditions included in the standard commercial legend.

10. SOFTWARE CONVERSIONS - (SIN 511210)

Full monetary credit will be allowed to the ordering activity when conversion from one version of the software to another is made as the result of a change in operating system , or from one computer system to another. Under a perpetual license (132-33), the purchase price of the new software shall be reduced by the amount that was paid to purchase the earlier version. Under a term license (132-32), conversion credits which accrued while the earlier version was under a term license shall carry forward and remain available as conversion credits which may be applied towards the perpetual license price of the new version.

11. DESCRIPTIONS AND EQUIPMENT COMPATIBILITY

The Contractor shall include, in the schedule pricelist, a complete description of each software product and a list of equipment on which the software can be used. Also, included shall be a brief, introductory explanation of the modules and documentation which are offered.

12. RIGHT-TO-COPY PRICING

The Contractor shall insert the discounted pricing for right-to-copy licenses.

15 | P a g e

TERMS AND CONDITIONS APPLICABLE TO PURCHASE OF CLOUD COMPUTING PRODUCTS AND CLOUD

RELATED IT PROFESSIONAL SERVICES (SPECIAL ITEM NUMBER 518210C)

****NOTE: This SIN presents a solution for Contractors to provide cloud computing services and cloud-related IT professional services that comply with NIST definitions and principles within the scope of today’s technology and standards with a secondary goal of accommodating ongoing technical advances in cloud computing. SIN 518210C Cloud Computing Services and Cloud- Related IT Professional Services is designed to cover core Cloud Services including Infrastructure as a Service, Platform as a Service, and Software as a Service, as well as the Cloud-related IT Professional Services required to assess, prepare, refactor, migrate, DevOps, integrate or govern a Cloud implementation. In accordance with section 889 of the National Defense Authorization Act for Fiscal Year 2019 (Pub. L. 115-232, August 13, 2018), an executive agency will be prohibited one year after enactment of the

TERMS AND CONDITIONS APPLICABLE TO PURCHASE OF CLOUD COMPUTING PRODUCTS AND CLOUD

RELATED IT PROFESSIONAL SERVICES (SPECIAL ITEM NUMBER 518210C)

Act from procuring, obtaining, extending or renewing a contract to procure or obtain any equipment, system or service that uses covered telecommunications equipment or services as a substantial or essential component of any system, or as critical technology as part of any system; and two years after enactment of the Act from entering into, renewing or extending a contract with an entity that uses covered telecommunications equipment or service in that entity’s equipment, system or service, as a substantial or essential component of any system, or as critical technology as part of any system. Section 889 defines “covered telecommunications equipment or services” as any of the following:

(A) Telecommunications equipment produced by Huawei Technologies Company or ZTE Corporation (or any subsidiary or affiliate of such entities).

(B) For the purpose of public safety, security of government facilities, physical security surveillance of critical infrastructure, and other national security purposes, video surveillance and telecommunications equipment produced by Hytera Communications Corporation, Hangzhou Hikvision Digital Technology Company, or Dahua Technology Company (or any subsidiary or affiliate of such entities).

(C) Telecommunications or video surveillance services provided by such entities or using such equipment.

(D) Telecommunications or video surveillance equipment or services produced or provided by an entity that the Secretary of Defense, in consultation with the Director of the National Intelligence or the Director of the Federal Bureau of Investigation, reasonably believes to be an entity owned or controlled by, or otherwise connected to, the government of a covered foreign country (i.e. the People’s Republic of China). (Pub. L. 115-232, section 889(f)(3), italicized parenthetical added).

1. SCOPE The prices, terms and conditions stated under Special Item Number (SIN) 518210C Cloud Computing Services (i.e.

IaaS, etc.) and Cloud-Related Professional Services apply exclusively to Cloud Computing Services (i.e. IaaS, etc.) and Cloud- Related Professional Services within the scope of this Information Technology Schedule.

This SIN provides ordering activities with access to Cloud (i.e. SaaS, etc.) technical services that run in cloud environments and meet the NIST Definition of Cloud Computing Essential Characteristics. Cloud Services [(i.e. SaaS, etc.)] relating to or impinging on cloud that do not meet all NIST essential characteristics should be listed in other SINs. (For example: Software subscription services or Software as a Service offerings that do not meet the essential “measured service” requirement may meet the definition of “Term Licenses” under SIN 132-32. See the Measured Service requirement in Table 2, below.)

The scope of this SIN is limited to cloud capabilities provided entirely as a “pay as you go” service and cloud-related IT professional services. Hardware, software and other artifacts acquired to supporting the physical construction of a private or other cloud are out of scope for this SIN. Currently, an Ordering Activity can procure the hardware and software needed to build private on premise cloud functionality, through combining different services on other IT

Schedule FSS SINs (e.g., 54151S).

16 | P a g e

Sub-categories in scope for this SIN are the three NIST Service Models: Software as a Service (SaaS), Platform as a Service (PaaS), and Infrastructure as a Service (IaaS). Offerors may optionally select a single sub-category that best fits a proposed cloud service offering. Only one sub-category may be selected per each proposed cloud service offering. Offerors may elect to submit multiple cloud service offerings, each with its own single sub-category. The selection of one of three sub-categories does not prevent Offerors from competing for orders under the other two sub-categories. See service model guidance for advice on sub-category selection. Sub-category selection within this SIN is optional for any individual cloud service offering, and new cloud computing service (i.e. IaaS, etc.) technologies that do not align with the aforementioned three sub-categories may be included without a sub-category selection so long as they comply with the essential characteristics of cloud computing as outlined by NIST. See Table 1 for a representation of the scope and sub-categories.

Table 1: Cloud Computing Services (i.e. IaaS, etc.)

SIN Description Sub-Categories1 ● Commercially available cloud computing services ● Meets the National Institute for Standards and Technology (NIST) definition of Cloud Computing essential characteristics ● Open to all deployment models (private, public, community or hybrid), vendors specify deployment models 1. Software as a Service (SaaS): Consumer uses provider’s applications on cloud infrastructure. Does not manage/control platform or infrastructure. Limited application level configuration may be available. 2. Platform as a Service (PaaS): Consumer deploys applications onto cloud platform service using provider-supplied tools. Has control over deployed applications and some limited platform configuration but does not manage the platform or infrastructure. 3. Infrastructure as a Service (IaaS): Consumer provisions computing resources. Has control over OS, storage, platform, deployed applications and some limited infrastructure configuration, but does not manage the infrastructure.

1 Offerors may optionally select the single sub-category that best fits each cloud service offering, per Service Model Guidance, or select no sub-category if the offering does not fit an existing NIST service model.

2. DESCRIPTION OF CLOUD COMPUTING SERVICES (i.e. IaaS, etc.) AND PRICING **NOTE TO CONTRACTORS: The information provided below is designed to assist Contractors in qualifying cloud computing services for this SIN and providing complete descriptions and pricing information. This language should NOT be printed as part of the Information Technology Schedule Pricelist; instead, Contractors should respond to each service requirement as it relates to each cloud computing service offered under the contract. There is guidance provided in subsequent sections of the Terms and Conditions to assist in determining how to meet these requirements. This section delineates requirements for submitting a proposal for the Cloud Services (i.e. IaaS, etc.) SIN, as well as requirements that apply to Task Orders** a. Service Description Requirements for Listing Contractors The description requirements below are in addition to the overall Schedule 70 evaluation criteria described in SCP-FSS-001-N Instructions Applicable to New Offerors (Alternate I – MAR 2016) or SCP-FSS-001-S Instructions Applicable to Successful FSS Program Contractors, as applicable, SCP-FSS-004 and other relevant publications. Refer to overall Schedule 70 requirements for timelines related to description and other schedule updates, including but not limited to clauses 552.238-81 – section E and clause I-FSS-600. Table 2 summarizes the additional Contractor-provided description requirements for services proposed under the Cloud Computing Services (i.e IaaS, etc.). All mandatory description requirements must be complete, and adequate according to evaluation criteria. In addition there is one “Optional” reporting descriptions which exists to provide convenient service selection by relevant criteria. Where provided, optional description requirements must be complete and adequate according to evaluation criteria:

(1) The NIST Service Model provides sub-categories for the Cloud SIN and is strongly encouraged, but not required. The Service Model based sub-categories provide this SIN with a structure to assist ordering activities in locating and comparing services of interest. Contractors may optionally select the single service model most closely corresponding to the specific service offering. (2) If a sub-category is selected it will be evaluated with respect to the NIST Service Model definitions and guidelines in “Guidance for Contractors".

Table 2: Cloud Service Description Requirements

# Description Requirement Reporting Type Instructions 1 Provide a brief written description of how the proposed cloud computing services Mandatory The cloud service must be capable of satisfying each of the five NIST essential Characteristics as outlined in NIST Special Publication 800-145. See ‘GUIDANCE FOR CONTRACTORS: NIST

17 | P a g e

(i.e. IaaS, etc.) satisfies each individual essential NIST Characteristic

Essential Characteristics’ below in this document for detailed overall direction, as well as guidance on inheriting essential characteristics. The NIST “Measured Service” characteristic requires a minimal “pay as you go” unit of measurement appropriate for the service. In the case of SaaS, the appropriate maximum measured increment of service shall be no more than 30 days per user, or some other equivalent discrete measurement that provides the government with the advantage of frequent (approximately every 30 days) “pay as you go” metering cycles. SaaS products, where consumption is only measured on an annual basis, may better fit under “Term Software License” SIN 132-32. Likewise, offers of any combinations of IaaS, PaaS or any other cloud product services in a bundle or other fashion that do not meet the frequency requirements of approximately 30-day measurement and billing cycles, will not be accepted as complying with the NIST Measured Service characteristic.

2 Select NIST deployment models for the cloud computing service proposed.

Mandatory Contractors must select at least one NIST deployment model as outlined in NIST Special Publication 800- 145 describing how the proposed cloud computing service is deployed. Select multiple deployment models if the service is offered in more than one deployment model. See ‘GUIDANCE FOR CONTRACTORS: NIST Deployment Model’ below in this document for detailed direction on how to best categorize a service for the NIST deployment models.

3 Optionally select the most appropriate NIST service model that will be the designated sub- category, or may select no sub-category.

Optional Contractor may select a single NIST Service model to subcategorize the service as outlined in NIST Special Publication 800-145. Sub-category selection is optional but recommended. See ‘GUIDANCE FOR CONTRACTORS: NIST Service Model’ below in this document for detailed direction on how to best categorize a service for the NIST IaaS, PaaS, and SaaS service models.

b. Pricing of Cloud Computing Services All current pricing requirements for Schedule 70, including provision SCP-FSS-001-N (Section III Price Proposal), SCP-FSS-001-S, SCP-FSS-004 (Section III Price Proposal), and clause I-FSS-600 Contract Price Lists, apply. At the current time there is no provision for reducing or eliminating standard price list posting requirements to accommodate rapid cloud price fluctuations. In addition to standard pricing requirements, all pricing models must have the core capability to meet the NIST Essential Cloud Characteristics, particularly with respect to on-demand self-service, while allowing alternate variations at the task order level at agency discretion, pursuant to the guidance on NIST Essential Characteristics. 3. RESPONSIBILITIES OF THE CONTRACTOR The Contractor shall comply with all laws, ordinances, and regulations (Federal, State, City, or otherwise) covering work of this character. a. Acceptance Testing Any required Acceptance Test Plans and Procedures shall be negotiated by the Ordering Activity at task order level. The Contractor shall perform acceptance testing of the systems for Ordering Activity approval in accordance with the approved test procedures. b. Training If training is provided commercially the Contractor shall provide normal commercial installation, operation, maintenance, and engineering interface training on the system. Contractor is responsible for indicating if there are separate training charges.

c. Information Assurance/Security Requirements The contractor shall meet information assurance/security requirements in accordance with the Ordering Activity requirements at the Task Order level. d. Related Professional Services The Contractor is responsible for working with the Ordering Activity to identify related professional services and any other services available on other SINs that may be associated with deploying a complete cloud service (i.e. IaaS, etc.) solution. Any additional substantial and ongoing IT professional services related to the offering such as assessing, preparing, refactoring, migrating, DevOps, developing new cloud based applications and managing/governing a cloud implementation may be offered per the guidelines below. e. Performance of Cloud Computing Services (i.e. IaaS, etc.) The Contractor shall respond to Ordering Activity requirements at the Task Order level with proposed capabilities to Ordering Activity performance specifications or indicate that only standard specifications are offered. In all cases the Contractor shall clearly indicate standard service levels, performance and scale capabilities. The Contractor shall provide appropriate cloud computing services (i.e. IaaS, etc.) on the date and to the extent and scope agreed to by the Contractor and the Ordering Activity. f. Reporting

The Contractor shall respond to Ordering Activity requirements and specify general reporting capabilities available for the Ordering Activity to verify performance, cost and availability. In accordance with commercial practices, the Contractor may

18 | P a g e furnish the Ordering Activity/user with a monthly summary Ordering Activity report. 4. RESPONSIBILITIES OF THE ORDERING ACTIVITY The Ordering Activity is responsible for indicating the cloud computing services requirements unique to the Ordering Activity. Additional requirements should not contradict existing SIN or IT Schedule 70 Terms and Conditions.

Ordering Activities should include (as applicable) Terms & Conditions to address Pricing, Security, Data Ownership, Geographic Restrictions, Privacy, SLAs, etc. Cloud services typically operate under a shared responsibility model, with some responsibilities assigned to the Cloud Service Provider (CSP), some assigned to the Ordering Activity, and others shared between the two. The distribution of responsibilities will vary between providers and across service models. Ordering activities should engage with CSPs to fully understand and evaluate the shared responsibility model proposed. Federal Risk and Authorization Management Program (FedRAMP) documentation will be helpful regarding the security aspects of shared responsibilities, but operational aspects may require additional discussion with the provider. a. Ordering Activity Information Assurance/Security Requirements Guidance (1) The Ordering Activity is responsible for ensuring to the maximum extent practicable that each requirement issued is in compliance with the Federal Information Security Management Act (FISMA) as applicable. (2) The Ordering Activity shall assign a required impact level for confidentiality, integrity and availability (CIA) prior to issuing the initial statement of work.2 The Contractor must be capable of meeting at least the minimum security requirements assigned against a low-impact information system in each CIA assessment area (per FIPS 200) and must detail the FISMA capabilities of the system in each of CIA assessment area. (3) Agency level FISMA certification, accreditation, and evaluation activities are the responsibility of the Ordering Activity. The Ordering Activity reserves the right to independently evaluate, audit, and verify the FISMA compliance for any proposed or awarded Cloud Computing Services. (4) The Ordering Activity has final responsibility for assessing the FedRAMP status of the service, complying with and making a risk-based decision to grant an Authorization to Operate (ATO) for the cloud computing service, and continuous monitoring. A memorandum issued by the Office of Management and Budget (OMB) on Dec 8, 2011 outlines the responsibilities of Executive departments and agencies in the context of FedRAMP compliance. 3

2. Per Federal Information Processing Standards Publication 199 & 200 (FIPS 199, “Standards for Security Categorization of Federal Information and Information Systems”) (FIPS 200, “Minimum Security Requirements for Federal Information and Information Systems”) 3. MEMORANDUM FOR CHIEF INFORMATION OFFICERS: Security Authorization of Information Systems in Cloud Computing Environments. December 8, 2011.

(5) Ordering activities are responsible for determining any additional information assurance and security related requirements based on the nature of the application and relevant mandates. b. Deployment Model If a particular deployment model (Private, Public, Community, or Hybrid) is desired, Ordering Activities are responsible for identifying the desired model(s). Alternately, Ordering Activities could identify requirements and assess Contractor responses to determine the most appropriate deployment model(s). c. Delivery Schedule The Ordering Activity shall specify the delivery schedule as part of the initial requirement. The Delivery Schedule options are found in Information for Ordering Activities Applicable to All Special Item Numbers. d.

Interoperability Ordering Activities are responsible for identifying interoperability requirements. Ordering Activities should clearly delineate requirements for API implementation and standards conformance. e. Performance of Cloud Computing Services The Ordering Activity should clearly indicate any custom minimum service levels, performance and scale requirements as part of the initial requirement. f. Reporting The Ordering Activity should clearly indicate any cost, performance or availability reporting as part of the initial requirement. g. Privacy The Ordering Activity should specify the privacy characteristics of their service and engage with the Contractor to determine if the cloud service is capable of meeting Ordering Activity requirements. For example, a requirement could be requiring assurance that the service is capable of safeguarding Personally Identifiable Information (PII), in accordance with NIST SP 800-1224 and OMB memos M-06-165 and M-07-166. An Ordering Activity will determine what data elements constitute PII according to OMB Policy, NIST Guidance and Ordering Activity policy. 4. NIST SP 800-122, “Guide to Protecting the Confidentiality of Personally Identifiable Information (PII)” 5.

OMB memo M-06-16: Protection of Sensitive Agency Information http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2006/m0616.pdf 6. OMB Memo M-07-16: Safeguarding Against and Responding to the Breach of Personally Identifiable Information http://www.whitehouse.gov/sites/default/files/omb/memoranda/fy2007/m07-16.pdf

19 | P a g e

h. Accessibility The Ordering Activity should specify the accessibility characteristics of their service and engage with the Contractor to determine the cloud service is capable of meeting Ordering Activity requirements. For example, a requirement could require assurance that the service is capable of providing accessibility based on Section 508 of the Rehabilitation Act of 1973 (29 U.S.C. 794d). i. Geographic Requirements Ordering activities are responsible for specifying any geographic requirements and engaging with the Contractor to determine that the cloud services offered have the capabilities to meet geographic requirements for all anticipated task orders. Common geographic concerns could include whether service data, processes and related artifacts can be confined on request to the United States and its territories, or the continental United States (CONUS). j. Data Ownership and Retrieval and Intellectual Property Intellectual property rights are not typically transferred in a cloud model. In general, CSPs retain ownership of the Intellectual Property (IP) underlying their services and the customer retains ownership of its intellectual property. The CSP gives the customer a license to use the cloud services (i.e. IaaS, etc.) for the duration of the contract without transferring rights. The government retains ownership of the IP and data they bring to the customized use of the service as spelled out in the FAR and related materials. General considerations of data ownership and retrieval are covered under the terms of Schedule 70 and the FAR and other laws, ordinances, and regulations (Federal, State, City, or otherwise). Because of considerations arising from cloud shared responsibility models, ordering activities should engage with the Contractor to develop more cloudspecific understandings of the boundaries between data owned by the government and that owned by the cloud service provider, and the specific terms of data retrieval. In all cases, the Ordering Activity should enter into an agreement with a clear and enforceable understanding of the boundaries between government and cloud service provider data, and the form, format and mode of delivery for each kind of data belonging to the government. The Ordering Activity should expect that the Contractor shall transfer data to the government at the government's request at any time, and in all cases when the service or order is terminated for any reason, by means, in formats and within a scope clearly understood at the initiation of the service. Example cases that might require clarification include status and mode of delivery for: � Configuration information created by the government and affecting the government’s use of the cloud provider’s service. � Virtual machine configurations created by the government but operating on the cloud provider’s service.

� Profile, configuration and other metadata used to configure SaaS application services or PaaS platform services.

The key is to determine in advance the ownership of classes of data and the means by which Government owned data can be returned to the Government. k. Service Location Distribution The Ordering Activity should determine requirements for continuity of operations and performance and engage with the Contractor to ensure that cloud services have adequate service location distribution to meet anticipated requirements. Typical concerns include ensuring that: (1) Physical locations underlying the cloud are numerous enough to provide continuity of operations and geographically separate enough to avoid an anticipated single point of failure within the scope of anticipated emergency events. (2) Service endpoints for the cloud are able to meet anticipated performance requirements in terms of geographic proximity to service requestors. Note that cloud providers may address concerns in the form of minimum distance between service locations, general regions where service locations are available, etc.

5. GUIDANCE FOR CONTRACTORS This section offers guidance for interpreting the Contractor Description Requirements in Table 2, including the NIST essential cloud characteristics, service models and deployment models. This section is not a list of requirements. Contractor-specific definitions of cloud computing characteristics and models or significant variances from the NIST essential characteristics or models are discouraged and will not be considered in the scope of this SIN or accepted in response to Factors for Evaluation. The only applicable cloud characteristics, service model/subcategories and deployment models for this SIN will be drawn from the NIST 800-145 special publication. Services qualifying for listing as cloud computing services (i.e. IaaS, etc.) under this SIN must substantially satisfy the essential characteristics of cloud computing as documented in the NIST Definition of Cloud Computing SP 800-1457. Contractors must select deployment models corresponding to each way the service can be deployed. Multiple deployment model designations for a single cloud service are permitted but at least one deployment model must be selected.