• No results found

Contract Type: Open Market

N/A
N/A
Protected

Academic year: 2021

Share "Contract Type: Open Market"

Copied!
57
0
0

Loading.... (view fulltext now)

Full text

(1)

Rev. 1/07/2014 Page 1 of 57 Department of Transportation Bids will be publicly opened: December 30, 2015

Purchasing Contract Type: Open Market

Refer ALL Inquiries to: Sharon Smith Telephone No. (919) 707-2622

Date Issued: November 20, 2015 Commodity Number: 920

Commodity: Information Technology Service Management Tool (ITSM)

E-Mail: [email protected] Using Agency Name: Department of Transportation (See page 2 for delivery instructions) Agency Requisition No. 11422631

OFFER AND ACCEPTANCE: The State seeks offers for the Services and/or goods described in this solicitation. All offers and responses received shall be treated as offers to contract. The State’s acceptance of any offer must be demonstrated by execution of the acceptance found below, and any subsequent Request for Best and Final Offer, if issued. Acceptance shall create a contract having an order of precedence as follows: Best and Final Offers, if any, Special terms and conditions specific to this RFP, Specifications of the RFP, except as amended, the North Carolina Department of Information Technology General Terms and Conditions for Goods and Related Services, the North Carolina Department of Information Technology Supplemental Terms and Conditions for Software and Services, and the awarded Vendor’s offer.

EXECUTION: In compliance with this Request for Proposal, and subject to all the conditions herein, the undersigned offers and agrees to furnish any or all Services or goods upon which prices are offered, at the price(s) offered herein, within the time specified herein. By executing this offer, I certify that this offer is submitted competitively and without collusion. Failure to execute/sign bid prior to submittal shall render bid invalid. Late bids are not acceptable.

BIDDER:

STREET ADDRESS: P.O. BOX: ZIP:

CITY & STATE & ZIP: TELEPHONE NUMBER: TOLL FREE TEL. NO

PRINT NAME & TITLE OF PERSON SIGNING: FAX NUMBER:

AUTHORIZED SIGNATURE: DATE: E-MAIL:

Offer valid for one hundred eighty (180) days from date of bid opening unless otherwise stated here: ______ days

ACCEPTANCE OF OFFER: If any or all parts of this offer are accepted, an authorized representative of NCDOT shall affix their signature hereto and this document and the documents identified above shall then constitute the written agreement between the parties. A copy of this acceptance will be forwarded to the successful Vendor(s).

FOR NCDOT USE ONLY

Offer accepted and contract awarded this ___ day of _____________________, 20__, as indicated on attached certification, by _____________________________________________ (Authorized representative of NCDOT).

(2)

Rev. 1/07/2014 Page 2 of 57 DELIVERY INSTRUCTIONS: Vendor must deliver one (1) signed original and four (4) copies of the Offer to Issuing Agency in a sealed package with Company Name and RFP Number clearly marked on the front. Vendor must return all the pages of this solicitation in their response.

Vendor must also submit two (2) signed, executed electronic copies of this offer on USB Flash Drive or read-only CD/DVD(s). The files should not be password-protected and should be capable of being copied to other media. Additionally, Vendor must submit two (2) discs containing the offer excluding the proprietary information reported as confidential and proprietary in accordance with “17) Confidentiality” in Section VII: Department of Information Technology Procurement Office General Terms and Conditions for Goods and Related Services, NC DOT, in responding to open records requests, will release the information on these discs. It is the sole responsibility of the Vendor to ensure that these discs comply with the requirements of “17) Confidentiality” in Section VII: Department of Information Technology Procurement Office General Terms and Conditions for Goods and Related Services. A label must be affixed to the discs that includes: (1) Vendor name: (2) the RFP number and title; (3) the due date; and (4) the words “Offer-Redacted Copy”.

Address envelope and insert bid number as shown below. Please note that the US Postal Service does not deliver any mail (US Postal Express, Certified, Priority, Overnight, etc.) on a set delivery schedule to this Office. It is the responsibility of the Vendor to have the bid in this Office by the specified time and date of opening.

DELIVERY BY US POSTAL SERVICE:

DELIVERY BY OTHER MEANS:

OFFER NUMBER: 54-JC-11422631R

Department of Transportation

Attn: Sharon L. Smith

1510 Mail Service Center

Raleigh, NC 27699-1510

OFFER NUMBER: 54-JC-11422631R

Department of Transportation

Attn: Sharon L. Smith

1 S. Wilmington Street, Room 412

Raleigh, NC 27601

Sealed offers, subject to the conditions made a part hereof, will be received at 1 S. Wilmington Street until 2:00 pm Eastern Standard Time on the day of opening and then opened, for furnishing and delivering the commodity as described herein. Offers must be submitted in a sealed package with the Execution of Proposal signed and dated by an official authorized to bind the Vendor’s firm. Failure to return a signed offer shall result in disqualification. All offers must comply with Section VI, Proposal Content and Organization.

Offers will not be accepted by electronic means. This RFP is available electronically at https://www.ips.state.nc.us/ips/. All inquiries regarding the RFP requirements are to be addressed to the contact person listed on Page One.

VENDOR STANDARD AGREEMENT(S): The terms and conditions of Vendor’s standard license, maintenance or other agreement(s) applicable to Software and other Products acquired under this Agreement may apply to the extent such terms and conditions do not materially change the terms and conditions of this Agreement. In the event of any conflict between the terms and conditions of this Agreement and the Vendor’s standard agreement(s), the terms and conditions of this Agreement relating to audit and records, jurisdiction, choice of law, the State’s electronic procurement application of law or administrative rules, the remedy for intellectual property infringement and the exclusive remedies and limitation of liability in the Terms and Conditions Section herein shall apply in all cases and supersede any provisions contained in Vendor’s relevant standard agreement or any other agreement. The State shall not be obligated under any standard license and/or maintenance or other Vendor agreement(s) to indemnify or hold harmless the Vendor, its licensors, successors or assigns; nor arbitrate any dispute, nor pay late fees, legal fees or other similar costs.

DIGITAL IMAGING: The State will digitize the Vendor’s response if not received electronically, and any awarded contract together with associated contract documents. This electronic copy shall be a preservation record, and serve as the official record of this solicitation with the same force and effect as the original written documents comprising such record. Any printout or other output readable by sight shown to reflect such record accurately is an "original."

(3)

Rev. 1/07/2014 Page 3 of 57 email. The questions are to be submitted in the following format:

Citation Vendor Question The State’s Response

Bid Section, Page Number

The State will prepare responses to all written questions submitted, and post an addendum to the Interactive Purchasing System (IPS) https://www.ips.state.nc.us/ips/. Oral answers are not binding on the State.

Vendor contact regarding this RFP with anyone other than Sharon L. Smith may be grounds for rejection of said Vendor’s offer.

This is a repost of RFP #54-JC-11422631.

Addendum to RFP: If a pre-offer conference is held or written questions are received prior to the submission date, an addendum comprising questions submitted and responses to such questions, or any additional terms deemed necessary by the State will be posted to the Interactive Purchasing System (IPS), https://www.ips.state.nc.us/ips/, and shall become an Addendum to this RFP. Vendors’ questions posed orally at any pre-offer conference must be reduced to writing by the Vendor and provided to the Purchasing Officer as directed by said Officer.

Critical updated information may be included in these Addenda. It is important that all Vendors bidding on this proposal periodically check the State website for any and all Addenda that may be issued prior to the offer opening date.

Basis for Rejection. Pursuant to 9 NCAC 06B.0401, the State reserves the right to reject any and all offers, in whole or in part; by deeming the offer unsatisfactory as to quality or quantity, delivery, price or service offered; non-compliance with the requirements or intent of this solicitation; lack of competitiveness; error(s) in specifications or indications that revision would be advantageous to the State; cancellation or other changes in the intended project, or other determination that the proposed requirement is no longer needed; limitation or lack of available funds; circumstances that prevent determination of the best offer; or any other determination that rejection would be in the best interest of the State.

NOTICE TO VENDORS: The State objects to and will not be required to evaluate or consider any additional terms and conditions submitted with a Offer’s response. This applies to any language appearing in or attached to the document as part of the Offer’s response. By execution and delivery of this Invitation for Offer and response(s), the Offer agrees that any additional terms and conditions, whether submitted purposely or inadvertently, shall have no force or effect unless such are specifically accepted by the State.

LATE OFFERS: Regardless of cause, late offers will not be accepted and will automatically be disqualified from further consideration. It shall be the Vendor’s sole risk to ensure delivery at the designated office by the designated time. Late offers will not be opened and may be returned to the Vendor at the expense of the Vendor or destroyed if requested. VENDOR REGISTRATION AND SOLICITATION NOTIFICATION SYSTEM: Vendor Link NC allows Vendors to electronically register with the State to receive electronic notification of current procurement opportunities for goods and services available on the Interactive Purchasing System at the following web site: https://www.ips.state.nc.us/ips

(4)

Rev. 1/07/2014 Page 4 of 57

North Carolina Department of Transportation

Information Technology Service Management Tool

Implementation – ITP.00248

(5)

Rev. 1/07/2014 Page 5 of 57

Bidding Information ... 7

A. Instructions to Vendors ... 7

B. General Conditions for Proposals ... 7

C. Evaluation Process ... 10

Technical Specifications ... 13

Cost Proposal ... 35

Other Requirements and Special Terms ... 36

Proposal Content and Organization ... 39

North Carolina Information Technology Procurement Office General Terms and Conditions for Goods and Related Services ... 41

North Carolina Office of Information Technology Supplemental Terms and Conditions for Software and Services ... 51

Appendix A: Cost Form ... 56

(6)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 6 of 57

Introduction

The purpose of this Request for Proposal (RFP) is to solicit responses for a vendor to provide and implement an Information Technical Service Management (ITSM) Tool Implementation solution (hereinafter referred to as “ITSM solution”) for the North Carolina Department of Transportation (NCDOT) that meets the requirements of the ITSM Tool Implementation project specified in this RFP. This ITSM solution will be used by the NCDOT Office of Information Technology (IT) as an agency-wide standard to bring uniformity to NCDOT’s IT service delivery and operations in five NCDOT help desks. The ITSM solution shall be configured for use by NCDOT IT, agency-wide. The objective is to standardize the service delivery process within NCDOT. The standardized processes are identified in the phased implementation outlined in this RFP. This is a repost of RFP #54-JC-11422631. Vendors must return a new proposal in order to be considered for award. Approximately 350 NCDOT IT professionals are responsible for the support of over 9,500 NCDOT knowledge workers. The key business objectives for the project are to procure and implement an ITSM Solution that:

 replaces the currently used tools:

o FrontRange HEAT Version 8.6 for the IT Help Desk Ticketing system and

o Open Technology Real Service (OTRS) ITSM Cloud Edition to manage the NCDOT-IT change management process, and

 consolidates efforts onto a single common platform for NCDOT ITSM.

This RFP includes the following which are needed to implement the specific Information Technology Infrastructure Library (ITIL) processes:

 technical specifications for the acquisition and configuration of the ITSM solution  implementation of the ITSM solution

 ITSM solution and process training, and  professional services

Only Vendors with documented and demonstrable experience in providing ITSM solutions are encouraged to respond. In addition, the State reserves the right to make partial, progressive or multiple awards: where it is advantageous to award separately by items; or where more than one supplier is needed to provide the contemplated requirements as to quantity, quality, delivery, service, geographical areas; and where other factors are deemed to be necessary or proper to the purchase in question.

(7)

Rev. 1/07/2014 Page 7 of 57

Bidding Information

A. Instructions to Vendors

Additional acronyms, definitions and abbreviations may be included in the text of the RFP. 1) Offers submitted electronically, or via facsimile (FAX) machine will not be accepted. 2) EXECUTION: Failure to sign under EXECUTION section will render proposal invalid.

3) TIME FOR CONSIDERATION: Unless otherwise indicated on the first page of this document, Vendor’s offer must be valid for one hundred and eighty (180) days from the date of proposal opening

4) FAILURE TO MEET PROPOSAL REQUIREMENTS: While it is not anticipated that the awarded Vendor will fail to meet the proposal requirements, if such should occur, the right is reserved to further evaluate the responses to this RFP and then to recommend an award to the next Vendor response that represents the best interest of the State. 5) PROMPT PAYMENT DISCOUNTS: Vendors are urged to compute all discounts into the price offered. If a prompt

payment discount is offered, it will not be considered in the award of the contract except as a factor to aid in resolving cases of identical prices.

6) MISCELLANEOUS: Masculine pronouns shall be read to include feminine pronouns and the singular of any word or phrase shall be read to include the plural and vice versa.

7) VENDOR REGISTRATION AND SOLICITATION NOTIFICATION SYSTEM: Vendor Link NC allows Vendors to electronically register with the State to receive electronic notification of current procurement opportunities for goods and services available on the Interactive Purchasing System at the following web site:

https://www.ips.state.nc.us/IPS/Vendor/Vndrmess.asp

8) ORGANIZATION: Vendors are directed to carefully review Section VI herein and fully comply with the content and organizational requirements therein.

9) E-PROCUREMENT: This is NOT an e-procurement solicitation. Paragraphs 48) a) and 48) b) of the attached Department of Information Technology Procurement Office General Terms and Conditions for Goods and Related Services do not apply to this solicitation. The Terms and Conditions made part of this solicitation contain language necessary for the implementation of North Carolina’s statewide e-procurement initiative. It is the Vendor’s responsibility to read these terms and conditions carefully and to consider them in preparing the offer. By signature, the Vendor acknowledges acceptance of all terms and conditions including those related to e-procurement.

a. General information on the e-procurement service can be found at http://eprocurement.nc.gov/.

b. Within two days after notification of award of a contract, Vendor must register in NC E-Procurement @ Your Service at the following web site: http://eprocurement.nc.gov/Vendor.html.

c. As of the RFP submittal date, the Vendor must be current on all e-Procurement fees. If the Vendor is not current on all e-Procurement fees, the State may disqualify the Vendor from participation in this RFP. 10) E-VERIFY: Pursuant to N.C.G.S. § 143B-1323(k), the State shall not enter into a contract unless the awarded

Vendor and each of its subcontractors comply with the E-Verify requirements of N.C.G.S. Chapter 64, Article 2. Vendors are directed to review the foregoing laws. Any awarded Vendor must submit a certification of

compliance with E-Verify to the awarding agency, and on a periodic basis thereafter as may be required by the State.

B. General Conditions for Proposals

1) Definitions, Acronyms and Abbreviations. Generally, see 9 NCAC 06A.0102 for definitions. The following are additional defined terms:

a) The State: Is the State of North Carolina, and its Agencies.

b) NCDIT or DIT: The NC Department of Information Technology, formerly Office of Information Technology Services.

c) Goods: Includes intangibles such as computer software; provided, however that this definition does not modify the definition of “goods” in the context of N.C.G.S. §25-2-105 (UCC definition of goods). b) Vendor: Company, firm, corporation, partnership, individual, etc., submitting a response to a solicitation. c) Open Market Contract: A contract for the purchase of goods or services not covered by a term, technical,

(8)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 8 of 57

d) 24x7: A statement of availability of systems, communications, and/or supporting resources every hour (24) of each day (7 days weekly) throughout every year for periods specified herein. Where reasonable downtime is accepted, it will be stated herein. Otherwise, 24x7 implies NO loss of availability of systems, communications, and/or supporting resources.

e) Reasonable, Necessary or Proper: as used herein shall be interpreted solely by the State of North Carolina.

f) RFP: Request for Proposal

g) ITSM: Information Technology Service Management h) ITIL: Information Technology Infrastructure Library i) NCDOT: North Carolina Department of Transportation j) IT: Information Technology

k) PMO: Project Management Office l) SAP: Systems Application Products m) CI: Contract Initiation

n) CMDB: Content Management Data Base o) SCCM: System Center Configuration Manager

p) MS SCOM: Microsoft System Center Operations Manager

2) Read and Review. It shall be the Vendor’s responsibility to read this entire document, review all enclosures and attachments, and comply with all requirements and the State’s intent as specified herein. If a Vendor discovers an inconsistency, error or omission in this solicitation, the Vendor should request a clarification from the State’s contact person listed on the front page of the solicitation. Questions and clarifications must be submitted in writing and may be submitted by personal delivery, letter, fax or e-mail within the time period identified hereinabove.

3) Vendor Responsibility. The Vendor(s) will be responsible for investigating and recommending the most effective and efficient technical configuration. Consideration shall be given to the stability of the proposed configuration and the future direction of technology, confirming to the best of their ability that the recommended approach is not short lived. Several approaches may exist for hardware configurations, other products and any software. The Vendor(s) must provide a justification for their proposed hardware, product and software solution(s) along with costs thereof. Vendors are encouraged to present explanations of benefits and merits of their proposed solutions together with any accompanying Services, maintenance, warranties, value added Services or other criteria identified herein. 4) Vendor certifies that in accordance with N.C.G.S. § 143-59.1(b), Vendor is not an ineligible vendor as set forth in

N.C.G.S. § 143-59.1 (a).

5) Oral Explanations. The State will not be bound by oral explanations or instructions given at any time during the bidding process or after award. Vendor contact regarding this RFP with anyone other than the Agency contact or procurement officer named on Page 2 above may be grounds for rejection of said Vendor’s offer. Agency contact regarding this RFP with any Vendor may be grounds for cancellation of this RFP.

6) Insufficiency of References to Other Data. Only information that is received in response to this RFP will be evaluated. Reference to information previously submitted or Internet Website Addresses (URLs) will not suffice as a response to this solicitation.

7) Conflict of Interest. Applicable standards may include: N.C.G.S. §§ 147-33.100, 14-234, 133-32. The Vendor shall not knowingly employ, during the period of this contract, nor in the preparation of any response to this solicitation, any personnel who are, or have been, employed by a Vendor also in the employ of the State and who are providing services involving, or similar to, the scope and nature of this solicitation or the resulting contract.

8) Contract Term. A contract awarded pursuant to this RFP shall have an effective date as provided in the Notice of Award. The term shall be one (1) year, and will expire upon the anniversary date of the effective date unless otherwise stated in the Notice of Award, or unless terminated earlier. The State retains the option to extend this contract for two (2) additional one (1) year periods at its sole discretion.

9) Effective Date. This solicitation, including any Exhibits, or any resulting contract or amendment shall not become effective nor bind the State until the appropriate State purchasing authority/official or Agency official has signed the document(s), contract or amendment; the effective award date has been completed on the document(s), by the State purchasing official, and that date has arrived or passed. The State shall not be responsible for reimbursing Vendor for goods provided nor Services rendered prior to the appropriate signatures and the arrival of the effective

(9)

Rev. 1/07/2014 Page 9 of 57 payment of the sums due under the contract.

10) Recycling and Source Reduction. It is the policy of this State to encourage and promote the purchase of products with recycled content to the extent economically practicable, and to purchase items which are reusable, refillable, repairable, more durable, and less toxic to the extent that the purchase or use is practicable and cost-effective. We also encourage and promote using minimal packaging and the use of recycled/recyclable products in the packaging of goods purchased. However, no sacrifice in quality of packaging will be acceptable. The Vendor remains responsible for providing packaging that will protect the commodity and contain it for its intended use. Vendors are strongly urged to bring to the attention of the purchasers at the Statewide IT Procurement Office those products or packaging they offer which have recycled content and that are recyclable.

11) Historically Underutilized Businesses. Pursuant to General Statute 143-48, 143-128.4 and Executive Order #13, the State invites and encourages participation in this procurement process by businesses owned by minorities, women, disabled, disabled business enterprises and non-profit work centers for the blind and severely disabled. Additional information may be found at: http://www.doa.nc.gov/hub/.

12) Clarifications/Interpretations. Any and all amendments or revisions to this document shall be made by written addendum from the NCDOT Procurement Office. Vendors may call the purchasing agent listed on the first page of this document to obtain a verbal status of contract award. If either a unit price or extended price is obviously in error and the other is obviously correct, the incorrect price will be disregarded.

13) Rights Reserved. While the State has every intention to award a contract as a result of this RFP, issuance of the RFP in no way constitutes a commitment by the State of North Carolina, or the procuring Agency, to award a contract. Upon determining that any of the following would be in its best interests, the State may:

a) waive any formality; b) amend the solicitation; c) cancel or terminate this RFP;

d) reject any or all proposals received in response to this document;

e) waive any undesirable, inconsequential, or inconsistent provisions of this document, which would not have significant impact on any proposal;

f) if the response to this solicitation demonstrate a lack of competition, negotiate directly with one or more Vendors;

g) not award, or if awarded, terminate any contract if the State determines adequate State funds are not available; or

h) if all responses are deficient, determine whether Wavier of Competition criteria may be satisfied, and if so, negotiate with one or more Vendors.

14)

Alternate Offers. Vendor may submit alternate offers for various levels of service(s) or products meeting specifications. Alternate offers must specifically identify the RFP requirements and advantage(s) addressed by the alternate offer. Any alternate offers must be clearly marked with the legend as shown herein. Each offer must be for a specific set of Services or products and offer at specific pricing. If a Vendor chooses to respond with various service or product offerings, each must be an offer with a different price and a separate RFP offer. Vendors may also provide multiple offers for software or systems coupled with support and maintenance options, provided, however, all offers must satisfy the specifications

.

Alternate offers must be clearly marked

“Alternate Offer for ‘name of Vendor’”

and numbered sequentially with the first offer if separate offers are submitted.

This legend must be in bold type of not less than 14-point type on the face of the offer, and on the text of

the alternative offer.

15) Co-Vendors. Vendors may submit offers as partnerships or other business entities. Such partners or other “co-Vendors”, if any, shall disclose their relationship fully to the State. The State shall not be obligated to contract with more than one Vendor. Any requirements for references, financial statements or similar reference materials shall mean all such partners or co-Vendors.

(10)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 10 of 57

16) Submitting an Offer. Each Vendor submitting an offer warrants and represents that:

a) The offer is based upon an understanding of the specifications and requirements described in this RFP. b) Costs for developing and delivering responses to this RFP and any subsequent presentations of the offer

as requested by the State are entirely the responsibility of the Vendor. The State is not liable for any expense incurred by the Vendors in the preparation and presentation of their offers.

17) All materials submitted in response to this RFP become the property of the State and are to be appended to any formal documentation, which would further define or expand any contractual relationship between the State and Vendor resulting from this RFP process.

18) An offer may not be unilaterally modified by the Vendor for a one hundred and eighty (180) day period following the delivery of the offer, or of any best and final offer.

19) Non-Responsive Offers: Vendor offers will be deemed non-responsive by the State and will be rejected without further consideration or evaluation if statements such as the following are included:

 “This offer does not constitute a binding offer”,

 “This offer will be valid only if this offer is selected as a finalist or in the competitive range”,  “The vendor does not commit or bind itself to any terms and conditions by this submission”,

 “This document and all associated documents are non-binding and shall be used for discussion purposes only”,

 “This offer will not be binding on either party until incorporated in a definitive agreement signed by authorized representatives of both parties”, or

 A statement of similar intent.

20) North Carolina Secretary of State Registration: Vendors must be registered with the North Carolina Secretary of State to do business in North Carolina, or be willing to complete the registration process in conjunction with the execution of the contract documents (see www.secretary.state.nc.us/corporations).

C.

Evaluation Process

1) "Best Value" procurement methods are authorized by N.C.G.S. §143-135.9. The award decision is made based on multiple factors, including: total cost of ownership, meaning the cost of acquiring, operating, maintaining, and supporting a product or service over its projected lifetime; the evaluated technical merit of the Vendor's offer; the Vendor's past performance; and the evaluated probability of performing the requirements stated in the solicitation on time, with high quality, and in a manner that accomplishes the stated business objectives and maintains industry standards compliance. The intent of "Best Value" Information Technology procurement is to enable Vendors to offer and the Agency to select the most appropriate solution to meet the business objectives defined in the solicitation and to keep all parties focused on the desired outcome of a procurement. Evaluation shall also include compliance with information technology project management policies, compliance with information technology security standards and policies, substantial conformity with the specifications, and other conditions set forth in the solicitation.

2) Source selection. A one-step procurement process shall be used. Vendors shall submit offers combining technical and price information together. A trade-off/ranking method of source selection will be utilized in this procurement to allow the State to award the contract to the Vendor providing the Best Value, and recognizing that Best Value may result in award other than the lowest price or highest technically qualified offer. By using this method, the overall ranking may be adjusted up or down when considered with, or traded-off against other non-price factors.

a) The evaluation committee may request clarifications, an interview with or presentation from any or all Vendors as allowed by 9 NCAC 06B.0307. However, the State may refuse to accept, in full or partially, the response to a clarification request given by any Vendor. Vendors are cautioned that the evaluators are not required to request clarifications; therefore, all offers should be complete and reflect the most favorable terms. Vendors should be prepared to send qualified personnel to Raleigh, North Carolina, to discuss technical and contractual aspects of the proposal.

b) Evaluation Process Explanation. State Agency employees will review all offers. All offers will be initially classified as being responsive or non-responsive. If an offer is found non-responsive, it will not be considered further. All responsive offers will be evaluated based on stated evaluation criteria. Any references in an answer

(11)

Rev. 1/07/2014 Page 11 of 57 reference.

c) To be eligible for consideration, a Vendor must meet the intent of all requirements. Compliance with the intent of all requirements will be determined by the State. Responses that do not meet the full intent of all requirements listed in this RFP may be deemed deficient. Further, a serious deficiency in the response to any one factor may be grounds for rejection regardless of overall score.

d) Vendors are advised that the State is not obligated to ask for, or accept after the closing date for receipt of proposal, data that is essential for a complete and thorough evaluation of the proposal.

3) Best and Final Offers (BAFO). If negotiations or subsequent offers are solicited, the Vendors shall provide BAFOs in response. Failure to deliver a BAFO when requested shall disqualify the non-responsive Vendor from further consideration. The State may establish a competitive range based upon evaluations of proposals, and request BAFOs from the Vendors within this range; e.g. “Finalist Vendors”. The State will evaluate BAFOs and and scores may be adjusted up or down. If the State requests selected Vendor Finalists to provide on-site oral presentations and product demonstrations during negotiations, scores may be adjusted up or down to reflect information from presentations and demonstrations.

4) Vendor may be disqualified from any evaluation or award if Vendor or any key personnel proposed, has previously failed to perform satisfactorily during the performance of any contract with the State, or violated rules or statutes applicable to public bidding in the State.

5) Evaluation Method. The weighted factors below will be used in the evaluation of the Vendor proposals.

Evaluation Criteria Weight

Completeness of Offer: Effectiveness of proposed recommendations, approaches, designs, products, services; deliverables, and management methodologies, processes, and practices (including Vendor/State relations and Vendor service delivery and management) that respond to the business objectives, specifications/requirements, needs, challenges, and opportunities presented in this RFP.

50%

Project plan, including the proposed approach and schedule of work to be performed for implementing the ITSM solution. This encompasses the areas of producing acceptable deliverables; organization, timing, and structure of work activities; system/application

development processes; resource application and representation; key personnel; and project management organization, approach, and oversight.

20%

Cost Effectiveness and Value: Cost proposals will be evaluated from a total cost of ownership (TCO) perspective. The State anticipates examining cost proposals for evaluation criteria that may include, but are not limited to, the following:

i. Project costs and operational/maintenance costs for each of years one through the term of the the contract, 3 years (one year contract with 2 renewal years). For services performed pursuant to a Statement of Work and charged on an hourly rate basis, one fully loaded hourly rate that is applicable to all work and all levels and types of

personnel, assuming the work is in the Raleigh/Wake County area. The proposed rate should be fully loaded for travel and per diem in accordance with N.C.G.S. §138-6, with the vast majority of the work will be conducted in the Raleigh/Wake County area.

20%

Corporate Background and Experience: Vendor’s background and experience: including references; strength of financial information; and experience specifically relevant to responding to the State’s business and technical situations, requirements, needs, challenges, and

opportunities presented in this RFP. The State may deduct points for poor references. The State may elect to seek references other than the ones provided.

(12)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 12 of 57

Evaluation Criteria Weight

TOTAL 100%

6) The Procurement Manager will make every effort to adhere to the following schedule:

Action Responsibility Date

Issue of RFP NCDOT November 20, 2015

Deadline To Submit Questions Vendors December 4, 2015

Response to Written Questions/RFP Amendments

NCDOT December 11, 2015

Submission of Offer Vendors December 30, 2015

Proposal Evaluation Evaluation Committee January 22, 2016

Selection of Finalists Evaluation Committee January 29, 2016

Oral Presentation and/or Product

Demonstrations by Finalists (if requested by DOT)

Vendors February 5, 2016

Best and Final Offers from Finalists Vendors March 11, 2016

Submission of Evaluation Team Recommendation

Evaluation Committee March 18, 2016

Contract Award Statewide IT Procurement Office April 15, 2016

Protest Deadline Vendors 15 days after award

7) Award Of Contract. Qualified proposals will be evaluated and acceptance may be made in accordance with Best Value procurement practices as defined by GS §143-135.9 and applicable administrative rules. The responsible Vendor whose proposal is most advantageous to the State, taking into consideration the evaluation factors herein, will be recommended for contract award. Unless otherwise specified by the State or the Vendor, the State reserves the right to accept any item or group of items on a multi-item proposal.

8) The State has implemented links to the Interactive Purchasing System (IPS) that allow the public to retrieve proposal award information electronically from our Internet web site: https://www.ips.state.nc.us/ips/. Click on the IPS BIDS icon, click on Search for BID, enter the Agency prefix-offer number (54-JC-11422631), and then search. This information may not be available for several weeks dependent upon the complexity of the acquisition and the length of time to complete the evaluation process.

9) Protest Procedures: Protests of awards exceeding $25,000 in value must be submitted to the issuing Agency at the address given on the first page of this document. Protests must be received in this office within fifteen (15) calendar days from the date of the contract award and provide specific reasons and any supporting documentation for the protest. All protests will be governed by Title 9, Office of Information Technology Services, Subchapter 06B Sections .1101 - .1121.

(13)

Rev. 1/07/2014 Page 13 of 57

Technical Specifications

1) Enterprise Architecture Standards:

The North Carolina Statewide Technical Architecture (NCSTA) is located at the following website:

(https://it.nc.gov/services/it-architecture/statewide-architecture-framework ). This provides a series of domain documents describing objectives, principles and best practices for the development, implementation, and integration of business systems. Agencies and Vendors should refer to these Architecture documents when implementing enterprise applications and/or infrastructure.

2) Enterprise Licensing:

In offering the best value to the State, Vendors are encouraged to leverage the State’s existing resources and license agreements. The agreements may be viewed at: https://it.nc.gov/services/license-and-agreements.

a. Identify components or products that are needed for your solution that may not be available with the State’s existing license agreement.

b. Identify and explain any components that are missing from the State’s existing license agreement. c. If the Vendor can provide a more cost effective licensing agreement, please explain in detail the

agreement and how it would benefit the State.

d. Explain the transportability and transferability of the proposed license agreements. Any licenses or warranties purchased on behalf of the State for this project must be transferable at the time the Vendor is paid under contract for said component.

3) Virtualization:

For on premise hosted solutions, the State desires the flexibility to host Vendor’s proposed solution in a virtualized environment, should it determine in the future that virtualized hosting for such solution would be more economical or efficient. The State currently utilizes server virtualization technologies including VMware, Solaris and zLinux. Vendor should state whether its solution operates in a virtualized environment. Vendor also should identify and describe all differences, restrictions or limitations of its proposed solution with respect to operation, licensing, support, certification, warranties, and any other details that may impact its proposed solution, when hosted in a virtualized environment.

4) NCID: The proposed solution must externalize identity management and may be required to utilize the North Carolina Identity Service (NCID) for the identity management and authentication related functions performed by this application. NCID is the State's enterprise identity management (IDM) service. It is operated by the North Carolina Department of Information Technology. Additional information regarding this service can be found in the ITS Service Catalog at: http://www.its.state.nc.us/ServiceCatalog/Index.asp (see Identity Management - NC Identity Management under the main menu item Application Services) and the NCID Web site at:

https://www.ncid.its.state.nc.us/. 5) Equivalent Items:

Whenever a material, article or piece of equipment is identified in the specification(s) by reference to a

manufacturer’s or Vendor’s name, trade name, catalog number or similar identifier, it is intended to establish a standard, unless otherwise specifically stated as a brand specific requirement (no substitute items will be allowed). Any material, article or piece of equipment of other manufacturers or Vendors shall perform to the standard of the item named. Equivalent bids must be accompanied by sufficient descriptive literature and/or specifications to provide for detailed comparison. Samples of items, if required, shall be furnished at no expense to the State and if not destroyed in the evaluation process, may be returned to the Vendor at the Vendor’s expense.

6) All offers shall include specifications and technical literature sufficient to allow the State to determine that the equipment meets all requirements. This technical literature will be the primary source for evaluation. If a requirement is not addressed in the technical literature it must be supported by additional documentation and included with the offer. Offer responses without sufficient technical documentation may be rejected.

7) The State may, in its sole discretion, investigate any substitute or equivalent goods irrespective of any representation made by a Vendor or manufacturer.

(14)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 14 of 57

8) Specifications: Any deviation from specifications indicated herein must be clearly identified as an exception and listed on a separate page labeled “Exceptions to Specification”; otherwise, it will be considered that items offered are in strict compliance with these specifications, and Vendor will be held responsible. Any deviations shall be explained in detail. The Vendor shall not construe this paragraph as inviting deviation or implying that any deviation will be acceptable. Offers of alternative or equivalent goods may be rejected; and if offered, must be supported by independent documentary verification of equivalence to the specified goods.

9) Technical Specifications:

The Vendor’s response must specifically describe in detail and provide examples, when applicable, as to how the Vendor will comply with each specification specified in each sub-section below. Suitable alternative solutions may be considered, if the solution is deemed “equal to or greater than” the specification. When applicable, the

Vendor’s response must address pertinent details to be used in the evaluation, such as methodologies, hardware and software utilization, technical specifications, response times, downtimes, timeframes, deadlines, volume restraints/limits, staffing resources, size capacities, service-level expectations, etc. Acknowledgement that a specification can be met is not sufficient; “read and understood” and similar responses are not

sufficient. A description of the service or adherence to the specification must be provided.

Means, as used herein, is a specification that documents the requirements of a system or system component. It typically includes functional requirements, performance requirements, interface requirements, design

requirements, development standards, maintenance standards, or similar terms. Compliance with technical specifications is mandatory.

a) General

ID

Description

1 The ITSM solution shall support approximately 350 named ITSM users or 120 concurrent ITSM users and 9,500 end users with a potential growth in internal and external users of 30% over five years. The DOT IT help desk currently generates over 80,000 help desk tickest per year. The breakdown of the help desk tickets is as follows:

 Password Reset 43%  Incident 26%  Service Request 16%  Move, Add, Chg 7%  Question 5%  Tech/User Assist 2%  Other 1%

2 Vendor shall provide on-going remote administrator support for up to ten (10) hours per month for the term of the contract. The scope of administrative support includes the following:

 Guidance and advice on technical questions

 Support enhancements or technical configuration services for release upgrades  Maintenance assistance on customer configurations

 Perform day-to-day administration work

 Observations regarding current configurations against best practices  A single point of contact to the vendor.

3 Vendor shall indicate whether the ITSM solution is: 1) an on premise NCDOT solution or

2) a hosted Software-as-a-Service (SaaS) solution, or

3) a solution that has the option of both on premise and SaaS.

4 Vendor shall describe the solution’s implementation of best practices out-of-box. 5 Vendor shall describe the solution’s use of modern technologies.

(15)

Rev. 1/07/2014 Page 15 of 57

ID

Description

6 Vendor shall provide examples of the Vendor’s market leadership, and describe the Vendor’s focus, history and financial stability.

b) General Usability

ID

Description

7 The ITSM solution shall integrate with Microsoft Active Directory for user authentication and support SAML, WS Federation and support for claims.

8 The ITSM solution shall integrate with North Carolina’s Identify Service (NCID)

https://www.ncid.its.state.nc.us/TrainingAndDocumentation.asp to support a single sign-on implementation.

c) Service Desk & Incident Management

ID

Description

9 The ITSM solution shall support ITIL v3 best practices for Service Desk and Incident Management processes.

10 The ITSM solution shall address multiple separate and unique customer help desks or call centers e.g., NCDOT IT Help Desk, DMV IT Help Desk, and the DMV Business Help Desk. 11 The Vendor shall provide a detailed description of how the ITSM solution addresses multiple

customer help desks or call centers including what capabilities, constraints and restrictions are involved.

12 The Vendor shall provide ITSM solution details regarding the functional design of the solution e.g., multiple virtual instances running concurrently for each help desk or partitions or one solution.

13 The Vendor shall describe how confidentially is maintained for the ITSM solution’s network traffic, (i.e. customer meta data, system logging, CMDBs, etc.). For example: through segmentation, encryption, etc.

14 The ITSM solution shall integrate with the Bomgar Remote Customer Support Tool. 15 The Vendor shall provide documentation demonstrating the Vendor’s previous experiences

with the Bomgar Integration.

16 The ITSM solution shall easily initiate or transition into a major incident process from the incident process, including changing the categorization, escalations, emergency notifications and a critical incident management process.

d) Problem Management

ID

Description

17 The Vendor shall provide a detailed description of the ITSM solution’s key features that support ITIL v3 for the Problem Management process.

e) Change Management

ID

Description

(16)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 16 of 57

ID

Description

19 The ITSM solution shall link incidents to completed changes with a completed change request.

20 The ITSM solution shall have the capability to identify or flag a failed change, using manual or automated methods and calculate a warranty period (SLA) for failed and successful change requests.

21 The Vendor shall provide description of how work flow would be used to handle a Standard pre-approved Change and a low risk change that do not have to be approved by the Change Approval Board but has to be approved by a local change manager.

22 The Vendor shall provide a detailed description of how a Change Analyst will update the Configuration Item(s) in the Change Management Data Base (CMDB) when executing a change.

23 The Vendor shall provide details as to how the CMDB will be kept current in a rapidly changing production environment which includes web services, business applications, software platforms and servers, databases, and network infrastructure.

f) Release & Deployment Management

ID

Description

24 The Vendor shall provide a description of how the ITSM solution will comply with ITIL v3 best practices for Release and Deployment Management.

25 The Vendor shall provide a description of how the ITSM solution supports multiple teams executing the Software Development Life Cycle (SDLC) Waterfall methodology (ie. ITIL Release and Deployment process).

26 The Vendor shall provide a description of how the ITSM solution supports multiple teams executing Agile development methodologies for software development.

g) Request Fulfillment

ID

Description

27 The Vendor shall provide details of how the ITSM solution will comply with ITIL v3best practices for Request Fulfillment.

h) Knowledge Management

ID

Description

28 The Vendor shall provide a description of how the ITSM solution will comply with ITIL v3 best practices for Knowledge Management.

29 The Vendor shall provide details of how the ITSM solution will support the initial population of the knowledge database from existing knowledge databases and information.

i) Configuration Management Database

ID

Description

30 The Vendor shall describe the key features of the ITSM solution’s industry standard CMDB/CMS solution and how the ITSM solution is differentiated from other products with these features.

(17)

Rev. 1/07/2014 Page 17 of 57

ID

Description

31 The Vendor shall describe how the ITSM solution supports the initial population of CMDB from existing databases and systems, including desktop PCs, mobile devices, datacenter servers and network devices.

32 The Vendor shall provide details as to how to maintain and keep the CMDB current and up-to-date. For example, the Vendor will differentiate automated and manual procedures for servers, network devices, PCs and related information from Microsoft SCCM data.

33 The Vendor shall provide details as to how applications and individual web services level data associated with a server Configuration Item will be maintained when making changes and upgrades to applications running on servers in the datacenter. Identify the automated and manual procedures.

j) Supplier, Contract & Software Asset Management

ID

Description

34 The Vendor shall provide details of how the ITSM solution will comply with ITIL v3best practices for Supplier and Contract Management.

35 The Vendor shall provide details of how the ITSM solution will comply with ITIL v3best practices for Software Asset Management. The Vendor shall describe the Best Practices implemented out-of-the-box and typical integrations with third party systems and tools in support of the software asset management process.

k) Integrations

ID

Description

36 The Vendor shall provide a list of supported integrations they have successfully integrated with its ITSM solution. Integrations include systems such as: Systems, Applications & Products in Data Processing (SAP) Solution Manager, Microsoft System Center Configuration Manager (SCCM)/System Center Operations Manager (SCOM), Microsoft Active Directory, e-mail, Bomgar, Pingdom, What’s-Up-Gold, etc.

37 The Vendor shall describe the capabilities of the ITSM solution to integrate with Microsoft Outlook Enterprise e-mail.

38 The Vendor shall describe the ITSM solution’s integration with mobile support e.g., iPhone, iPad and Android devices. The description shall include a description of the Short Message Service (SMS) texting capabilities.

39 The Vendor shall describe the ITSM solution’s integration with inventory/discovery technologies, including Microsoft SCCM and BMCAtrium Discovery and Dependency Mapping (BMC/ADDM). The Vendor shall demonstrate specific experiences where they have integrated the ITSM solution with Microsoft SCCM and BMC/ADDM.

40 The Vendor shall describe the solution’s integration with Microsoft System Center Operations Manager (MS SCOM). The Vendor shall demonstrate specific experiences where they have integrated the solution with MS SCOM.

41 The Vendor shall describe the ITSM solution’s integration with SAP (e-Procurement) for the CMDB and the Software Asset Management process.

42 The Vendor shall describe the ITSM solution’s integration with “What’s Up Gold” discovery, monitoring, reporting and alert capability. The Vendor shall provide specific experiences where they have integrated the ITSM solution with “What’s Up Gold”.

(18)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 18 of 57

ID

Description

43 The Vendor shall describe the ITSM solution’s integration with the SolarWinds Pingdom web site monitoring tool. The Vendor shall provide specific experiences where they have

integrated the ITSM solution with SolarWinds Pingdom.

44 The Vendor shall describe the ITSM olution’s integration real time with SAP Solution Manger for incident, problem and change management. The Vendor shall provide specific

experiences where they have integrated the ITSM solution with SAP Solution Manager. 45 The Vendor shall describe the ITSM solution’s integration with the Bomgar Remote Support

Tool. The Vendor shall demonstrate specific experiences where they have integrated the ITSM solution with the Bomgar Tool.

46 The Vendor shall describe the ITSM solution’s integratration with current mobile devices. The Vendor shall provide a list of mobile devices supported e.g., smart phone, tablets, Android, etc.

47 The Vendor shall describe the ITSM solution’s migration of historical data from existing tools such as Serena Team Track, Front Range Solutions/HEAT, IBM Clear Quest (all SQL databases), local Microsoft Access data bases and Microsoft Excel spreadsheets to the new solution. (assume 5,000 records in each database to be migrated) Note: No current help desk tickets are to be migrated.

48 The Vendor shall describe the ITSM solution’s integration with NCDOT’s Avaya 9608 telephone used by the NCDOT IT Service Desk.

49 The Vendor shall provide the ITSM solution’s interface specifications and descriptions including Application Programming Interfaces (APIs) and Software Developer’s Kits (SDKs). l) Employee Self-service

ID

Description

50 The Vendor shall describe in detail the ITSM solution’s Employee Self-service portal. 51 The Vendor shall describe in detail the ITSM solution’s Employee Self-service for password

resets. m) Reporting

ID

Description

52 The Vendor shall describe in detail how the ITSM solution’s management dashboard is made available and viewed by Business Executives, IT Senior Management, IT Managers, Process Owners, and IT Technician.

53 The Vendor shall provide a list of reports that will be available in Phase I – Out-of-box Implementation and Phase II – Configured Implementation.

54 The Vendor shall describe a recommended approach to implement architecture compliance reporting. (i.e. comparing devices to a list of authorized devices and authorized release and version levels)

55 The Vendor shall describe the ITSM solution’s capability for Service Desk surveys of end users.

n) Upgrades

ID

Description

56 The Vendor shall describe the ITSM solution upgrade process and how configuration of changes will be maintained.

(19)

Rev. 1/07/2014 Page 19 of 57

ID

Description

57 The Vendor shall describe in detail the testing requirements that NCDOT must perform prior to “going live” with a new release or version of the ITSM solution.

o) Development & Production Operating Environment

ID

Description

58 The Vendor shall describe, in detail, the number of environments available for

pre-development (sandbox), pre-development, and test and production environments. The Vendor shall describe how these environments are used.

p) Architecture

ID

Description

59 The Vendor shall provide documentation and diagrams describing the logical architecture of the ITSM solution. The documentation shall provide names for all components such as workflow, transaction, reporting and interfaces between components.

60 The Vendor shall provide a description for each of the logical components that contain the following information: name, purpose, technology, and any additional and relevant characteristics.

q) Physical Architecture

ID

Description

61 The Vendor shall describe in detail how the ITSM solution will be installed in a phased approach. If the product is sold by modules, will the modules be installed to a limited number of users or globally, by function within module, etc. If the solution is not available by discreet module, describe how the ITSM solution will be deployed by phases.

r) Technology Strategy

ID

Description

62 The Vendor shall describe the future technology initiatives that may impact the application of the product e.g., rebuilds, sun setting or end-of-life technology.

63 The Vendor shall provide details as to how the ITSM solution technology will be improved in the next 2-3 years.

s) Security

ID

Description

64 The Vendor shall describe how the ITSM solution meets NCDOT’s Information Security requirements located at this address: https://www.scio.nc.gov/Mission/Information SecurityManual.aspx

65 The Vendor shall describe how the ITSM solution classifys, restricts and protects data accessible or entered into the system e.g., HIPPA, PCI, PII, addresses, Driver’s License numbers, birth dates, etc.

66 The Vendor shall describe how the ITSM solution manages the encryption of system data in transit and at rest including details e.g., encryption algorithms used, key strengths, etc. 67 The Vendor shall describe how the ITSM solution manages encryption keys for data in the

solution and provides certificates that are required and maintained for the transport encryption.

(20)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 20 of 57

ID

Description

68 The Vendor shall describe how the ITSM solution to utilize Microsoft Active Directory (AD) or NCID for managing and storing authentication for users. NCID implementation information is located at this address: https://www.ncid.its.state.nc.us/TrainingAndDocumentation.asp

u) Implementation

ID

Description

69 The Vendor shall install and implement the ITSM solution in Raleigh, NC, in two Phases: Phase I (Out-of-box) and Phase II (Configured Services). The Vendor shall work with the NCDOT Project Manager to finalize all implementation plans.

70 Phase I – Out-of-the-box

The NCDOT IT Help Desks shall be deployed in Phase I. The following functions, in addition to out-of-box ITIL v3 processes, shall be provided out-of-box for Phase I:

 IT Service Desk  Incident Management  Problem Management  Change Management

 Configuration Management Database (CMDB)  Service Catalog (basic)

 Request Fulfillment & Management

 Integration with NCDOT’s Avaya 9608 telephone system  Microsoft Outlook enterprise e-mail integration

 Microsoft Active Directory Integration for secure, single sign-on  Microsoft SCCM (System Center Configuration. Manager) Integration  Administrator Training

 Integrations training/transition for MS Active Directory or NCID, MS SCCM and email  Process Owner Training

(21)

Rev. 1/07/2014 Page 21 of 57

ID

Description

71 Phase II – Configured Services The Vendor shall:

 Implement the DMV Business help desk: The DMV help desk takes calls from DMV offices across the state and may engage IT to resolve a ticket. The DMV help desk handles primarily non-IT calls and requests, but needs to be able to easily transfer IT related tickets to the IT help desk.

 Implement the DMV IT Help Desk and DMV application release and deployment process (a mini-SDLC process).

 Implement Employee Self-service (Incident Management, Service Request and Password Reset).

 Implement Service Desk Chat.

 Integrate with Bomgar Remote Support.

 Implement Contract Management including Contract Tracking, linking to appropriate Contract Interfaces (CIs) and alerts.

 Implement Software License Management.

 Integrate with SAP Solution Manager for Incident, Problem, Change and Configuration Management Database (CMDB) processes.

 Implement Knowledge management processes.

 Migrate historical data from Serena, IBM Clear Case (SQL database) and local access databases to the solution.

 Integrate with mobile support e.g., smart phones, tablets, android devices with the solution.

 Integrate with “What’s Up Gold” discovery, monitor, event and alert.  Integrate with SolarWinds Pingdom.

 Integrate with BMC/ADDM.

 Integrate with CMDB and CI Asset Discovery (exclude MS SCCM data from Phase I).  Implement Service Desk surveys.

 Implement Process Owner and ITSM Solution Training for Phase II processes and any updates to the Phase I processes.

 Integrate training and transition for Bomgar, SAP, Mobile device support, “What’s Up Gold”, Solar Winds Pingdom, BMC/ADDM and Microsoft SCOM.

v) Project Management

ID

Description

72 The Vendor shall provide an on-site, full-time Project Manager to work closely with the NCDOT Project Manager to ensure successful implementation of the ITSM olution.

73 The Vendor shall provide an initial Project Management Plan in its proposal. At a minimum, the plan must include a description of the project management approach, assumptions, constraints, and key risks. The Project Plan must be updated when significant changes occur and are approved by the Agency Project Manager.

(22)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 22 of 57

ID

Description

74 The Vendor shall provide a Final Project Report of the project for closeout purposes to satisfy NCDOT requirements. The Final Project Report will include details showing how all

requirements have been met and implemented, as appropriate.

75 The Vendor shall submit with its response to the RFP a detailed Work Plan that illustrates how the Vendor will meet all the requirements of this RFP.

76 The Vendor’s Project Manager shall be the single point of contact between the Vendor and the NCDOT Project Manager for management and coordination of the Vendor's work (installation, configuration, testing, data migration, deployment). All work performed shall be coordinated with the NCDOT Project Manager.

77 Within fifteen (15) business days after contract award, the Vendor shall provide a Project Communication Plan to NCDOT detailing how communication will be handled on the project and shall include, but not be limited to, roles and responsibilities, project status, and

meetings (i.e. weekly and monthly).

78 The NCDOT Project Manager shall review and approve all project deliverables before any deliverable can be considered finalized and completed by the Vendor.

w) Support

ID

Description

79 The Vendor shall provide detailed ITSM solution release documentation, including all new capabilities being delivered, with new solution releases and updates. The Vendor shall provide detailed updates and documentation for all documented known issues with new ITSM solution releases and updates.

80 The Vendor shall provide an Escalation Plan for issues identified with the ITSM solution during production; this includes escalation for issues that are unresolved in the agreed upon timeframe.

81 The Vendor shall provide a draft Service Level Agreement (SLA) for their support of the ITSM solution as outlined in Appendix B for NCDOT Management review and approval. The SLA shall not be considered finalized until the NCDOT Management has approved the SLA. x) Training

ID

Description

82 The Vendor shall provide a detailed Training Plan encompassing all training to ten NCDOT Administrators, five T3 Trainers and five NCDOT Process Owners.

83 The Vendor shall provide on-site Administrator training, in Raleigh, NC, to ten Administrators. Administrator Training will include all necessary documentation and training materials to be provided to and owned by the NCDOT.

84 The Vendor shall provide on-site training for five T3 Trainers and five NCDOT Process Owners in Raleigh, NC, for the Phase I and Phase II implementations.

85 The Process Owner training shall include the following processes: Incident Management, Problem Management, Change Management, Configuration Management (CMDB), Service Level Management (SLM), Service Catalog Management, Access Management, Service Request Management, Service Desk, and Business Help Desk.

86 The Process Owner Training shall address the following for each process: Process design, Process operation/execution, Process tool integrations, Related process interfaces, and technical considerations and procedures to modify the process.

87 All training materials used by the Vendor for training all NCDOT trainees shall be owned by the NCDOT.

(23)

Rev. 1/07/2014 Page 23 of 57

ID

Description

88 The Vendor shall provide all training resources available to the NCDOT such as but not limited to training documentation, Computer Based Training (CBT) resources, online ITSM knowledge bases, or support contacts.

89 All training materials and system documentation shall be freely reproducible by NCDOT, for internal use only, with no infringement on copyright or use.

y) Test

ID

Description

90 The Vendor shall provide an initial Test Plan in its proposal. The Vendor shall deliver revised draft and final Test Plans after Contract Award, as specified in the approved Project

Schedule. At a minimum, the Test Plan shall clearly describe the Vendor’s strategy for performing Configuration Testing, Unit Testing, System/Integration Testing, Stress/Load Testing, and User Acceptance Testing.

91 The Test Plan shall describe the manner in which system interfaces and security requirements will be tested. The Test Plan shall identify all automated testing tools the Vendor plans to employ, including the specific release/version number of the projects. 92 If the Vendor plans to employ automated test tools, then all test data files shall be in

electronic format suitable for input into other testing tools. The Vendor shall deliver revised and final Test Plans at the appropriate and approved times as specified in the approved Project Schedule.

10)

NCDOT Technical Architecture Specifications

The following section delineates the Technical Architecture Specifications for this RFP; the Vendor shall explain how the ITSM solution will comply with Technical Architecture Specifications and how the proposed ITSM solution meets the project’s objectives.

A. Logical Application Environment

As detailed in the NCSTA, there must be clear separation between the presentation, business logic, and data components of the application, deployed on different physical/virtual machines.

(24)

NCDOT Information Technology Service Management (ITSM) Tool Implementation Project

Rev. 1/07/2014 Page 24 of 57

B. Logical Network Environment

All on premise environments of the ITSM solution shall be hosted in State data centers and shall function within the network topology described below. For off premise or Cloud solutions, the solution shall meet the NC Statewide Security requirements as well as all other applicable requirements outlined in this RFP.

Client Interface

Data Tier Data Access Tier

Business Tier Presentation Logic Tier

Presentation GUI

Storage

Query and Storage Optimization Performance, Indexing, etc.

Database Interface Data I/O Scalable, Stateless Business Objects and Rules Data Manipulation and Transformation

End User

Web Server-side IIS ASP.NET, Jscript, Web Forms, C#, etc. Producing HTML, XML,

DHTML, WML, etc. Proxy Tier SOAP, RPC, DCOM, etc.

Distributed Logic and Connections to Proxy

Devices

Client and Server separation

References

Related documents

These have also been briefly discussed in AHWAC (2006). a) The AIHW allied health data collection is comprehensive in the data that is collected but is limited in

Either party to this Agreement shall have the right to terminate this Agreement upon thirty (30) days written notice to the other party for convenience, with or without cause,

In addition to any other rights under the Agreement, either Party may terminate the Agreement on any anniversary of the Commencement Date by giving the other thirty days’

Either party may terminate this Agreement for any reason at any time upon thirty (30) days prior written notice provided that no such termination shall affect or modify any rights

any procedure agreed upon by the parties or under the procedure of paragraph (2) of this article is not successful, the challenging party may request, within thirty days after having

a) By the Second Party in giving 60 days notice in writing to the First Party if the First Party will fail to pay any sum due under the terms of this contract within 30 working

If either party to the Government’s public works contract does not wish the dispute to be referred to mediation or if the dispute cannot be resolved through mediation,

Either party may terminate this Agreement without cause upon thirty (30) days written notice to the other party. Any notice given or requested to be given pursuant to this