Cloud Solutions Quick Guide - draft v8 SBB 071625.docx

DOCX document 334 KB Posted

Attached to
IT - NASPO Cloud Solutions Contract (All XaaS) | Wisconsin Participating Addendums
Contract number
505ENT-O18-NASPOCLOUD-00
Issued by
Wisconsin

About this file

This is a user guide for the NASPO Cloud Solutions contract, a cooperative purchasing agreement led by Utah with participation from the State of Wisconsin. The contract involves three primary vendors: Unisys (505ENT-O18-NASPOCLOUD-01), VMware (505ENT-O18-NASPOCLOUD-02), and Carahsoft (505ENT-O18-NASPOCLOUD-03). Wisconsin state agencies, University of Wisconsin campuses, and Wisconsin municipalities are authorized to use this optional cooperative contract through Wisconsin's Participating Addendums, which remain in effect until 2026 or until terminated by either party.

The contract covers cloud services and related products and services, excluding hardware or peripheral devices and equipment related to software functionality. Each purchase requires individual Engagement Addendums and Statements of Work with separate annual terms. For Software as a Service purchases, users must first request a business case exception from the mandatory NASPO SVAR contract. Pricing is established by the NASPO Master Agreement as maximum rates that can be negotiated lower but not exceeded, with firm pricing during contract terms. Carahsoft operates through authorized resellers listed in their price documentation. Prior to utilizing the contract, agencies must obtain approval from both the SBOP Contract Manager and DET, with additional requirements for high-risk IT processes over $1,000,000 including completion of DOA-3730 forms and various assessments.

View the file

Other files

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

User Guide NASPO Cloud Solutions (link) State Contract#: 505ENT-O18-NASPOCLOUD-00

Unisys: 505ENT-O18-NASPOCLOUD-01 VMware: 505ENT-O18-NASPOCLOUD-02 Carahsoft: 505ENT-O18-NASPOCLOUD-03

Mandatory:No
Cooperative:Yes (WI municipalities may use this contract)
P-Card:Yes

Master Contract by Lead State Utah: Term 2016 - 2026

· The State of Wisconsin Participating Addendums (PA) will continue in effect until 2026 or until terminated by either party.

· Each Engagement Addendum/ SOW (purchase) shall have its own annual term dictated by the time and terms of purchase.

Scope The State of Wisconsin has executed a PA with Carahsoft, Unisys and VMware for the purchase of Cloud Services and related products and services. The PA’s are available for optional use by Wisconsin state agencies, UW campuses, and Wisconsin municipalities as cited in Wisconsin statutes s. 16.73.

Excluded from the Scope The scope does not include the following:

· Purchase of hardware or peripheral devices required to meet the functional or technical requirements; and

· Purchase of any equipment related to software functionality.

SaaS – Business Case Exception from SVAR - Required

For Software as a Service only, a business case exception shall be requested from the mandatory NASPO SVAR contract prior to using this contract. This request should be via email to the contract manager of the NASPO SVAR contract. You can find that contact information on the NASPOSVAR VendorNet page.

Participating Addendums, Engagement Addendums The (PAs were negotiated and include the standard terms and conditions for the State. The PAs provide procurement authority for State use.

Each Authorized User will need to enter into an Engagement Addendum and Statement of Work (SOW) for each purchase made with the exception of additional purchases for the same scope as the Engagement Addendum where additional SOW’s or amendments can be executed.

All purchases will accompany terms and conditions for licensing and services as applicable which must be reviewed and negotiated by the agency with the vendor.

Each PA contains an “Order of Precedence” section designed to capture any specific requirements or terms and conditions as governing in the event of conflict with the other contractual documents respectively.

Requesting Quotes

Quotes shall contain the NASPO CLOUD contract # on them. If the contract number is missing, end users need to reach out to the vendor and ensure that the cloud solution is being quoted on the NASPO CLOUD contract.

Pricing Unisys Price List (link) VMware Price List (link) Carahsoft Price List (link)

All pricing is established by the NASPO Master Agreement which should be considered the maximum price and may be negotiated further. Pricing cannot exceed the rate card, but can be lower.

All prices are firm during a contract term. Pricing can be lowered (or a higher discount) at any time during the contract without requiring an amendment of the published rates.

Purchase Order (PO) and Invoicing The PO and invoices shall be itemized.

Authorized Resellers – Carahsoft

The Carahsoft Master Agreement allow certain vendors to resell products on Carahsoft’s behest. You can find the list of approved Carahsoft resellers on the their NASPO CLOUD page. From there, click pricing documents und Documents/Details, click the Carahsoft Price File. From there select the Carahsoft – Fulfillment Partner Listing. Vendors listed on the left, are authorized to sell on behalf of Carahsoft and purchase orders can be issued directly to the Reseller. When doing this, be sure to put the contract # in the reseller ID in STAR. See attachment to the contract page for instructions.

Permission needed to use State Contract Prior to utilizing the cloud contract, please reach out to the SBOP Contract manager (Sandra Barg) via email Sandra.Barg1@wisconsin.gov. The email correspondence should include the agency’s IT director as a CC. Please also indicate in your email where you are at in the process. The preference is that this email takes place during the exploration stage and prior to the solution being identified, if possible. The SBOP contract manager will review the email to ensure that it falls under the scope of the cloud contract and will then forward the email on to DET for their input. Agencies shall wait until approval is provided by both the SBOP contract manager and DET before pursuing a purchase.

Vendor Contacts Unisys: Rob Silverberg Email: Rob.Silverberg@unisys.com

925-639-8082

VMware: Karin Whitwood Email: NASPO-VP@vmware.com 571-375-3481

Carahsoft: Mariah Edwards Email: Mariah.Edwards@carahsoft.com 703-889-9734

Additional Considerations prior to making a purchase

In addition to adhering to applicable policies and/or procedures, contract users must ensure to consult with the appropriate IT representative or stakeholder within their individual organization to understand what IT specific pre-screening, assessments, or approvals may need to occur before a transaction can be completed.

Such pre-screening, assessments, or approvals may include but are not limited to the following:

· High Risk IT Process -PIM 22-001

· If the goods or services purchased through this contract are intended to support a High-Risk Project (this includes a PO being issued for over $1,000,000), state agencies shall ensure that the High-Risk approval process is initiated and completed prior to the PO being issued or the contract signed. More about this process can be found in the PIM 22-001 (linked above). State agencies need to complete the DOA–3730 and submit it through the RPA portal https://rpa.wi.gov/#/Home selecting the High-Risk tile from the main page.

· Cloud Brokerage Review

· DET Architecture Assessment

· Telecommunications System Study Report (TSSR)

Additional Resources:

· State Procurement Manual (PRO-508)

· High-Risk IT Plan

Contract Use Questions and Feedback Direct any questions, comments, complaints, or feedback to the Contract Manager (below). User feedback will help to address and correct contractual issues and to prepare for future solicitations.

Contract Manager Sandra Barg DOA – State Bureau of Procurement 101 E. Wilson Street, 6th Floor Madison, WI 53703 608-266-1558 sandra.barg1@wisconsin.gov image1.jpeg image2.png image3.png image4.png image5.png image6.png

File details come from the government source that posted it. Updated .