WESTERN CAROLINA UNIVERSITY REQUEST FOR PROPOSALS by alicejenny

VIEWS: 43 PAGES: 30

									           WESTERN CAROLINA UNIVERSITY

    REQUEST FOR PROPOSALS NO. 73-RFP20583

 Bid will be publicly opened: 10-15-2012 @ 3:00pm ET




OFFEROR:

FEDERAL ID OR SOCIAL SECURITY NO.:




    THIS COVER PAGE IS FOR OFFICE USE ONLY AND
    WILL BE REMOVED AND DESTROYED AT AWARD
                      OF BID.
                                                                                       1


                           STATE OF NORTH CAROLINA
                            REQUEST FOR PROPOSALS
                                  73-RFP20583

TITLE:                    Web Content Management System Replacement

USING AGENCY:             Western Carolina University (WCU)

ISSUE DATE:               September 28, 2012

ISSUING AGENCY:           Western Carolina University (WCU)
                          Purchasing Department
                          340 H. F. Robinson Administration Bldg.
                          65 West University Way
                          Cullowhee, NC 28723
                          Attn: Arthur Stephens
                          Director of Procurement & AP Services
                          (828) 227-7203

Sealed Proposals subject to the conditions made a part hereof will be received until
October 15, 2012, 3:00 p.m. ET, for furnishing services described herein.

SEND ALL PROPOSALS DIRECTLY TO THE ISSUING AGENCY ADDRESS
SHOWN ABOVE.

IMPORTANT NOTE: Indicate firm name and RFP number on the front of each sealed
proposal envelope or package, along with the date for receipt of proposals specified
above.

Direct all inquiries concerning this RFP to: Arthur Stephens
                                             Western Carolina University
                                             Cullowhee, NC 28723
                                             (828) 227-7203
                                             stephensa@email.wcu.edu


NOTE: Questions concerning the specifications in this Request for Proposals will be
received until October 8, 2012, 2:00 p.m. ET. All questions must be submitted in
writing to the individual indicated above. A summary of all questions and answers
will be posted on the Internet at www.doa.state.nc.us/pandc/ as an addendum,
located under the RFP # being modified. It is the offeror's responsibility to assure
that all addenda have been reviewed and, if needed, signed and returned.




                                      73-RFP20583
                                                                                             2

IMPORTANT NOTE: NON-MANDATORY CALLIN PRE-BID CONFERENCE
Participation in the pre-bid conference call is optional. However, if you wish to ask
informal questions or solicit informal clarification, please feel free to participate using the
following dial-in information. Anything verbally discussed on this call will have no
official standing and is nonbinding on the University as all questions must be officially
submitted and answered in writing as described elsewhere in this document.

1. Date and Time: Friday, October 05, 2012 at 10:00 AM Eastern Daylight Time.
2. Join the conference call:

Dial +1 (267) 507-0009
Access Code: 910-329-271
Audio PIN: Shown after joining the meeting

Meeting ID: 910-329-271

STATE OF NORTH CAROLINA/UNIVERSITY RELATIONSHIPS:
1. Are you or any officer of your company or any member of your immediate family employed
by the State of North Carolina? Yes___ No___
If yes, list name, relationship, and agency where employed: ___________________________
__________________________________________________________________________

2. Are you or any officer of your company or any member of your immediate family a member
of the UNC Board of Governors, WCU Board of Trustees, any WCU foundation board, or any
WCU related corporations, joint ventures, or associations? Yes___ No___
If yes, list name, relationship, and which board:_____________________________________
__________________________________________________________________________


HUB VENDOR PARTICIPATION:
WCU is committed to increase HUB (Historically Underutilized Businesses)
vendor participation. In order to be considered as a HUB vendor, the following
information must be completed (51% owned and controlled by the following):
___African American
___Asian American
___Hispanic
___American Indian
___Female Owned (non-minority)
___Disabled Owned
___Disabled-Owned Business Enterprise
___Non-Profit Work Center for Blind and Severely Disabled
___Socially and Economically Disadvantaged as defined in 15 U.S.C. 637
      (www4.law.cornell.edu/uscode/)
___None of the above




                                        73-RFP20583
                                                                                                            3

                                   EXECUTION OF PROPOSAL

By submitting this proposal, the potential contractor certifies the following:
   1. This proposal is signed by an authorized representative of the firm.
   2. The cost and availability of all equipment, materials, and supplies associated with
      performing the services described herein have been determined and included in
      the proposed cost.
   3. All labor costs, direct and indirect, have been determined and included in the
      proposed cost.
   4. The potential contractor has read and understands the conditions set forth in this
      RFP, and agrees to them with no exceptions.

Therefore, in compliance with this Request for Proposals, and subject to all conditions
herein, the undersigned offers and agrees, if this proposal is accepted within 30 days
from the date of the opening, to furnish the subject services.

OFFEROR:

ADDRESS:

CITY, STATE, ZIP:

TELEPHONE NUMBER: _____________ FAX NUMBER: ____________

E-MAIL:
Principal Place of Business if different from above (See General Information on
Submitting Proposals, Item 18.):

Will any of the work under this contract be performed outside the United States?
   Yes      No (If yes, describe in technical proposal.)
N.C.G.S. § 133-32 and Executive Order 24 prohibit the offer to, or acceptance by, any State Employee of
any gift from anyone with a contract with the State, or from any person seeking to do business with the
State. By execution of any response in this procurement, you attest, for your entire organization and its
employees or agents, that you are not aware that any such gift has been offered, accepted, or promised by
any employees of your organization.

BY: _______________________________ TITLE:________________________
                 (Signature)
 _________________________________ DATE: _______________________
         (Typed or printed name)
             *************************************************************
ACCEPTANCE OF PROPOSAL
This proposal was accepted by Western Carolina University.

BY: ___________________________ TITLE: ________________________
              (Signature)
DATE: _________________________

    THIS PAGE MUST BE SIGNED AND INCLUDED IN YOUR PROPOSAL.
                Unsigned proposals will not be considered.

                                             73-RFP20583
                                                                                                4

                           Where Service Contracts Will Be Performed
            In accordance with NC General Statute 143-59.4 (Session Law 2005-169),
      this form is to be completed and submitted with the offeror’s (technical) proposal/bid.

        Issuing Agency: Western Carolina University           Solicitation # 73-RFP20583

               Agency Contact Person & phone #: Arthur Stephens 828-227-7203

Solicitation Title / Type of Services: Web Content Management System Replacement
______________________________________________________________________________

OFFEROR: ___________________________________________
City & State: __________________________________________

Location(s) from which services will be performed by the contractor:

         Service                                    City/Province/State         Country

        _____________________________             _________________              _______

        _____________________________             _________________              _______

        _____________________________             _________________              _______

Location(s) from which services are anticipated to be performed outside the U.S. by the
contractor:

        _____________________________            _________________              ________

        _____________________________            _________________              ________

Location(s) from which services will be performed by subcontractor(s):

          Service                        Subcontractor    City/Province/State Country

         ______________________         ___________      _________________       ______

         ______________________         ___________      _________________       ______

         ______________________         ___________      _________________       ______

Location(s) from which services are anticipated to be performed outside the U.S. by the
subcontractor(s):

         ______________________         ___________      _________________       ______

         ______________________          ___________     _________________       ______

                              (Attach additional pages if necessary.)



                                         73-RFP20583
                                                                                                                                5

Administration Information                                                                                               Page
......................................................................................................................
Pre-bid Conference                                                                                                        2
Execution of Proposal                                                                                                     3
Due Date                                                                                                                  6
Project Overview                                                                                                          6
Project Deliverables                                                                                                      7
System Requirements                                                                                                       7
Submission Requirements                                                                                                   19
Evaluation Criteria                                                                                                       19
Proposal Requirements                                                                                                     20
The Procurement Process                                                                                                   21
General Information on Submitting Proposals                                                                               22
North Carolina General Contract Terms and Conditions                                                                      25
Attachment A: Reference Information                                                                                       29




                                                                  73-RFP20583
                                                                                         6

DUE DATE

Proposals must be submitted by October 15, 2012, 3:00 p.m. ET. See “Instructions” in
the Submission Requirements section of this document for details.

Schedule of Events  
    Request for proposals issued                           September 28, 2012 
    Pre‐bid conference                                     October 5 
    Written questions due                                  October 8      
    Summary of questions and responses posted              October 10 
    Proposal deadline to WCU                               October 15 
    Proposal evaluation                                    Oct. 15‐31 
    Notification to short‐listed firms                     October 31   
    Product presentations and test drives                  Nov. 1‐9       
    Proposal evaluation                                    Nov. 12‐30                        
    Selection of finalist                                  December 1                        
    Schedule discussions                                   Dec. 1‐7                          
    Award of contract                                      December 7 (approximate)          
    Migration of web sites                                 Jan. 7 – March 29, 2013 
    Training of users                                      Spring 2013 

PROJECT OVERVIEW 
 
Background and Purpose 
Western Carolina University currently uses Open Text (formerly Red Dot) as its primary 
web content management system (CMS). WCU seeks a new CMS to support the 
management of approximately 11,000 pages, which are distributed across four web 
sites, and edited by more than 200 web editors.  Those sites include: 
 
    1. WCU (administration, admissions, academics and library, student life, and giving)  
    2. Ramsey Center 
    3. Bardo Arts Center (BAC) 
    4. Fine Art Museum (FAM) 

WCU seeks implementation services for the new CMS, managed hosting of the system, 
training and support in its use, and the associated documentation and manuals. This 
implementation will not include a redesign of the University’s web site or its navigation 
architecture/site structure. The implementation services must include the migration of 
the four websites listed above with no changes to design or structure, and no 
interruption to the end‐user experience.  
 
Note:  WCU maintains some sites and assets outside of the CMS including the university 
news, alumni and athletics websites as well as a number of other sub‐sites, forms, and 
digital media elements.  Those sites and assets are not within the scope of this project. 
 
                                      73-RFP20583
                                                                                      7

PROJECT DELIVERABLES  
 
   1. New Content Management System 
   2. Managed hosting of CMS or CMS delivered as Software as a Service 
   3. All web content currently managed by WCU’s implementation of Open Text to 
      be migrated into new CMS in a way that does not change the published version 
      of the website (web pages must publish in the same architecture, design, and 
      URL structure) 
   4. Training for Web Services team in use of CMS 
   5. Documentation 
 
 
SYSTEM REQUIREMENTS 

   1. Capable of automated migration of Red Dot web pages 
      CRITICAL 
         a. Software is able to map /automatically migrate all web content currently 
             existing in WCU’s CMS, Red Dot, including all pages, assets, and 
             templates, from RedDot to the new software.   
         b. Migrated content publishes from the new CMS to the web with the same 
             page structure and URL form. 
         c. The software supports a business model with centralized application 
             support/administration but distributed site management and 
             administration. 

       IMPORTANT 
          d. Preference is given to automated migration, rather than migrating pages 
             one by one by hand/ manually. 

   2. Vendor  
      CRITICAL 
         a. The vendor can begin work no later than January 7, 2013 and complete 
             implementation by March 30, 2013. 
         b. Will the next release of the software require any data to be converted to 
             a format different than the format required by the current version of the 
             software?  

       IMPORTANT 
              
          c. List all colleges and universities using this software.  
          d. Has the vendor shown good performance and financial stability in its last 
             two fiscal years?  


                                    73-RFP20583
                                                                                  8

       e. Has the vendor has been in business at least 3 years under the same 
          ownership? 
       f. What percent of the vendor’s resources (people and money) is dedicated 
          to new product development?  
       g. What percent of vendor’s resources (people and money) is dedicated to 
          product support? 
       h. Describe the history of the software.  
       i. When was the software FIRST released to the general market?  
       j. What is the product’s maturity; what was the release date of the 
          CURRENT release of the software?  
       k. Will the next release of the software require significant changes to 
          existing data or sites upon upgrade?  
       l. When is the next release of the software planned?  
       m. Describe key upcoming features in the next release of the software.  
       n. Describe the vendor’s 3‐5 year roadmap.  

   NICE TO HAVE 
      o. Under what circumstances would the software cease to be supported? 

3. Hosting and Support 
   CRITICAL 
      a. Describe the following: 
               i. How clients request support, M‐F, 8‐5 EST and outside that 
                  timeframe 
              ii. The available hours of support 
             iii. Support limitations  
             iv. Service desk availability  
              v. Response times 
             vi. Evaluation/priority criteria for support    
      b. The university website has very strict up‐time requirements. Content 
          management functions have less strict up‐time requirements.  
               i. Describe service levels offered, including maintenance windows 
                  and how major version upgrades and incremental releases are 
                  communicated to clients. 
      c. Describe services provided for business continuity and disaster recovery.  
      d. Describe any training services for the web team (system administrators, 
          not end users). 
      e. Describe and/or provide documentation to be used by the web team 
          (system administrators) for technical/ functional support. 
           
                                 73-RFP20583
                                                                                    9

    
   IMPORTANT 
      f. Describe any optional on‐going training services that may be available 
          above and beyond the standard service.  
      g. Do you have a user community and/or knowledge base? Describe how 
          you interact and support this.  
           
   NICE TO HAVE 
      h. Attach your privacy policy for user data. 
      i. Describe how clients submit feature requests.  
      j. Is there a dedicated site where outstanding bugs and feature requests 
          are documented with resolutions and responses schedule and do clients 
          have access?   
      k. Do you provide documentation for end users? Describe or provide 
          samples. 

4. User Experience 
   CRITICAL 
      a. The software provides full content management functionality and 
          consistent user interface via all major web browsers (current versions of 
          Internet Explorer, Firefox, Safari, and Chrome) on both Mac and PC.  
      b. The software provides full content management functionality accessible 
          from off‐campus locations. 
      c. The software content author, approver, and publisher interfaces are 
          intuitive and easy to use, without being overly restrictive. Attach screen 
          shots that adequately represent the interfaces.  

   IMPORTANT 
        d. Is an online help menu an index of topics, searchable by keyword, 
           similar to that found in Windows, available in the software? 

   NICE TO HAVE 
      e. Is there a mobile app for editing content?  
      f. Does the software provide context‐sensitive help, i.e., help specific to 
          individual data entry fields or related collections of fields?  
      g. Can the online help be modified by a user with proper clearance?  
      h. If the software provides for user‐defined fields, can online help related to 
          each individual field be created?  




                                  73-RFP20583
                                                                                   10

 

Features and Functions 
 
5. Asset/media management 
   CRITICAL 
       a. The software allows document (i.e. pdf, MS Word) uploads as part of 
          content authoring interface.  
       b. The software allows image uploads as part of content authoring 
          interface.  
       c. The software allows embedding and display of video (streaming and 
          stored) on web pages. (ex., embedding YouTube videos, not necessarily 
          storing video files)  
       d. List file (document, image, etc.) types that can be uploaded as part of the 
          content author interface. (pdf, Word, Excel, jpg, gif, etc.) . 

    IMPORTANT 
       e. The software should have a central repository of files/assets and some 
          mechanism for content authors to view and select them.  
       f. The software should have a local repository of files/assets (ex. 
          Department).  
       g. The software should have role or group‐based access to files/assets.  
       h. The software should allow content items like images, documents, 
          multimedia etc. to have expiration date options that remove content 
          from public view.  
       i. The software should allow content items like images, documents, 
          multimedia etc. have a go‐live/publish date option that delays live 
          publication.  
       j. The software should allow documents and video to be tagged with 
          metadata.  
       k. The software should allow file size limits to be set to prevent upload of 
          massive, uncompressed image or video files. 
       l. The software should have an image management solution that 
          automatically compresses/resizes images (i.e. Tim Thumb in Wordpress) . 

    NICE TO HAVE 
       m. The software should allow versioning of images, documents, multimedia 
           files.  
     
     
     
                                  73-RFP20583
                                                                                    11

6. Email Forms 
   IMPORTANT 
      a. The software supports the creation of custom forms that send an email 
          to an individual or group. Example might be a feedback form.  
      b. The software custom form creator can  to set the following optional 
          validation criteria: required fields, date format, email format, URL format  
      c. The software allows the creation of simple forms without coding or 
          technical skills.  
      d. Form creator allows standard form field types like text, long text, check 
          box, drop down, date field/calendar, email. 
      e. Form creator offers protection from cross‐site scripting and other hacks. 
      f. If forms save to a database, the software allows this to be enabled/ 
          disabled.   

   NICE TO HAVE 
      g. The software should provide or be compatible with added captcha‐like 
          technology on public forms. 
      h. The software should provide a local site (department, unit) role that can 
          create custom public site forms for submission of data (ex. Feedback 
          form, simple data collection form). 

7. Accessibility/Validation 
   CRITICAL 
      a. The software meets HTML validation/standards compliance, and WCU 
          usability standards (University Policy 86: 
          http://www.wcu.edu/25360.asp) 
      b. The software allows users to add “alt” tags for images.  
      c. The WYSIWYG editor supports 508 compliance. 
      d. Web content created by the software is WC3 compliant.  
      e. The software generates valid html.  

   IMPORTANT 
      f. The software should allow for summaries to be associated with tables to 
         accommodate people using assistive technologies, however, tables are 
         used for formatting should not have summaries.  
      g. The software should provide some sort of accessibility compliance 
         content review.  

8. Public Website Search (box on the site) 
   CRITICAL 



                                  73-RFP20583
                                                                                    12

       a. Software either provides robust public search capability or integrates 
          easily with third party products that provide robust search (Google 
          Search Appliance or other).  

9. Search Engine Optimization (Google) 
   CRITICAL 
      a. The software employs techniques for search engine optimization.  
      b. The software can automatically generate a site map.  
      c. The software has the ability to control the discoverability of content 
          items by external search engines.  

10. Internal Search (for users in the CMS) 
    CRITICAL 
        a. The software incorporates an intuitive search mechanism for authors to 
           locate content. Describe how content authors/editors locate content to 
           edit.  

11. Workflow 
    CRITICAL 
       a. The software has tiered work flow for approval of web content and 
           structure, with notifications (task‐based workflow i.e. creation, editing, 
           approval).  
       b. Workflow creation and interface are intuitive and easy to use. Attach 
           screen shots that adequately represent the interface.  
       c. Content authors/editors/approvers are able to preview content updates 
           as they will appear in context prior to publishing live. 
       d. The software supports at least the following roles relevant to workflow: 
           content author, content reviewer/approver, content publisher.  
       e. It is possible to alter or override workflow dependencies to meet real‐
           time needs (e.g. re‐route workflow tasks). 
       f. Workflow is configurable for different content areas or items. For 
           example, a department may require that one set of pages has a rigorous 
           workflow while another set does not need review prior to publishing. 
       g. The software has a user interface for authors and reviewers that shows 
           the status of items in workflow. 

   IMPORTANT 
      h. The software should send email notifications of workflow tasks, including 
         task that have not been completed in a timely manner.   
      i. Notifications should be manageable, based on role or permission group 
         or content type.  

                                  73-RFP20583
                                                                                    13

       j. The software should provide audit trails of content editing activity and 
          they should be easily accessible by site managers/administrators. 
          Pertinent information would be date of change, user, changes made, 
          comments, etc.  
       k. The software should provide local sites (department, unit) with the ability 
          to view content inventory reports or summaries and review status of 
          content in workflow.  

   NICE TO HAVE 
      l. The software should allow comments to be associated with content 
          changes.  
      m. Each workflow action should have the option to add a comment.  

12. Accounts 
    CRITICAL 
       a. The software limits user access to specific areas (possibly sites, pages, 
           directories, repositories). For example, different divisions, departments, 
           and units and sub units should have editorial access only to their own 
           content.  
       b. The software allows for hierarchical access rights to content. For 
           example, an academic division web master may have access to all sites 
           within that division whereas a department web master may have access 
           to a subset of the same content.  
       c. The software supports multiple concurrent users.  List number of 
           concurrent users supported. 
       d. The software has been tested and approved or certified for deployment 
           to no fewer than 100 users.  
       e. The software allows custom roles.   
       f. The software allows a global administrator to limit local administrator 
           functionality.  
       g. The software allows for the same user to have different privileges based 
           on the site. For example, someone is an author for one site and a 
           reviewer for another site.  
       h. The software allows access rights to be relatively granular to site, 
           subdirectory, page, and other content items.  
       i. If an account is terminated, ownership of their content defaults to 
           administrator – or be able to be reassigned. 
            

13. Templates 
    CRITICAL 
                                  73-RFP20583
                                                                                  14

       a. The software provides for custom templates.  
       b. The software provides for the creation and use of multiple templates.   
       c. The software provides global/master templates to be supported centrally 
          that lock down certain areas or design elements to maintain a consistent 
          campus look and feel.  
       d. The software provides for some mechanism for end‐users to select 
          among template options when creating a new page. 
       e. Templates do not require complex coding and must allow a designer to 
          quickly edit and view changes in a staging environment.  
       f. Changes to global or master templates are propagated to child pages 
          throughout the site.  
       g. Style sheets are available and enforced to maintain consistency of 
          content appearance via the editor. 

   IMPORTANT 
      h. Administrators should be able to design and manage templates without a 
         proprietary language. 
      i. In addition to centrally‐supported, global style sheets, the software 
         should support the ability to add a style sheet to individual pages or a 
         sub‐site, given appropriate permissions/workflow. 

14. Metadata 
    IMPORTANT 
       a. The software should allow metadata tags to be added content items like 
          text, structured content, and images.  

   NICE TO HAVE 
      b. The software should provide a mechanism for storing both university‐
          wide and local (ex. Department) taxonomies or vocabularies.  
      c. Global administrators should be able to pre‐define list options for 
          commonly encountered metadata needs, for example a list of standard 
          department names.  
      d. Local site administrators should be able to pre‐define list options for 
          common local metadata needs.  

15. Content  
    CRITICAL 
       a. The software allows “check in/check out” to lock content to the current 
           user only. 
       b. The software “check in/check out” can be overridden. 
       c. Each content object is associated with an owner(s) and it is possible to 
           reassign ownership.  
                                 73-RFP20583
                                                                                   15

       d. Content items have a review date option that triggers notification to the 
          author to review and update the content.  
       e. The software provides versioning and roll‐back to a previous features. 
       f. The software allows the ability to compare and easily view changes 
          between versions. Refers to changes to text mostly. 
       g. The software supports the embedding of external content.  
       h. The software allows for content from third‐party systems to be 
          incorporated into published content – i.e. R25 or RSS feeds. 

   IMPORTANT 
      i. The software should allow for the syndication of content.  
      j. The software should allow for content items like news stories or event 
         descriptions to have an expiration date option upon which the content 
         should be removed from public view.   
              i. Content should only be expirable if it has no other content 
                 dependencies. 
             ii. Upon expiration of a content item, links to that content object in 
                 other areas of the system be updated automatically. 
            iii. The software should maintain link integrity by tracking the 
                 relationships (or links) that exist between content items in the 
                 system such that if an item is moved or expired from the site, all 
                 related items are automatically updated by the system without 
                 end‐user intervention. 
            iv. Describe what types of content relationships are managed 
                 (images, documents, pages) and what occurs when a content item 
                 is changed or deleted. 
             v. Expiration dates should be configurable to trigger automatic 
                 removal without requiring further manual intervention. 
      k. The software should allow content items like news stories or event 
         descriptions to have a go‐live/publish date option that delays live 
         publication. 

    NICE TO HAVE 
       l. The software should have some mechanism for reusing authoritative 
           content which is stored/updated in a single location for display on other 
           pages in the system. Information on other pages should be updated 
           automatically.  
            
16. Reports 
    CRITICAL 


                                  73-RFP20583
                                                                                    16

       a. The software integrates easily with third party analytics tools like Google 
          Analytics. 

   IMPORTANT 
      b. The software should include a link checker that detects broken links 
         during editing/publishing. 
      c. The software should provide a site report that identifies orphaned pages.  
      d. The software should provide a site report that identifies potentially stale 
         pages. For example, a report that identifies content items with a review 
         date in the past.  
      e. The software should provide site reports that identify: 
              i. Content items with owner, date of last update, review date, etc. 
             ii.  User reports – last logged in, pages currently being edited  
            iii. Status of items in some stage of a workflow and might include 
                 duration in current status, review date, task assignee, etc.  

   NICE TO HAVE 
      f. The software should provide some custom reporting functionality. 

17. Editor 
    CRITICAL 
        a. WYSIWYG editor allows editing of HTML directly. 
        b. WYSIWYG editor includes a spell checker with customizable dictionary. 
        c. Content authors can navigate to a page and edit content in context. 
        d. WYSIWYG editor can create tables for display of tabular data. 
        e. WYSIWYG editor works in any current browser/OS. 
        f. Preview works for different browsers and devices. 
        g. The software supports basic non‐English character sets, for example, 
            letters with diacritic marks. 
        h. The software allows administrators to control which WYSIWG functions 
            are available for authors so that greater compliance with standards is 
            enforced.  
        i. The software allows users to paste content from a MS Word document 
            into the WYSIWYG editor without having to clean up extraneous data.  

    
   NICE TO HAVE 
      j. The software should provide both simple and more complex user 
          interfaces to accommodate different skill levels of content managers.  

18. Publishing 
    CRITICAL 
                                  73-RFP20583
                                                                                       17

           a. The software can generate friendly URLs.  
           b. The software has the ability for single‐page publishing.  
           c. The software has the ability for scheduled publishing ‐ pages auto publish 
              and expire.  
           d. The software has the ability to publish mobile‐friendly options. 

       NICE TO HAVE 
              e. The software should provide web site visitors with an option to 
                 view/print a print‐friendly version of the page.  
 
    19. Other Features 
        CRITICAL 
           a. Integration of Web 2.0 features – Facebook, Twitter, RSS (push and pull), 
               polls, surveys, etc.  
           b. The software is compatible with secure socket layers for encryption of 
               information transmitted to and from a web site. 
           c. The software supports random/alternating images on web pages.  
           d. The software is able to automatically generate breadcrumbs. 
           e. The software is able to automatically generate an A‐Z index.  

       NICE TO HAVE 
          f. The software should have the ability to auto‐paginate  
          g. If simple widgets are available to plug into the application, they should be 
              pluggable without coding.  
          h. Email addresses on websites should be protected from automated 
              scanners that collect email addresses for sending spam.  

    20. Administration 
        CRITICAL 
           a. Template creation process and/or interface is acceptable to campus 
               designers. Attach screen shots that adequately represent the interface. 
           b. Administrative interface is usable and straightforward. Attach screen 
               shots that adequately represent the interface. 
           c. The software allows at least 4 administrative accounts. 
           d. The software allows new file types to be added. 

    21. Technology 
        CRITICAL 
           a. The software is hosted or delivered as Software as a Service, and all 
               updates, upgrades and patches are managed by vendor. 
           b. The software has the ability to enable SSL page‐by‐page. 
           c. The software is capable of secure FTP. 
                                    73-RFP20583
                                                                               18

   d. The software is compatible with setting up individual development, test, 
      and production environments. 
   e. The software complies with industry security best practices. 
   f. The vendor provides security breach response practices consistent with 
      industry standards. Ideally, the vendor utilizes robust intrusion detection 
      systems. 
   g. The software is secured behind a firewall. 
   h. Passwords are transmitted in encrypted format. 
   i. The software supports publishing pages in the .asp file format, as well as 
      .htm and .html. 
   j. The software supports javascript, jquery, iframes within content pages. 
   k. Data, including content, configurations, and logs are backed up and 
      retained such that the system and all information can be recovered 
      quickly. Describe service levels offered. 
   l. The software provides some mechanism for import of structured content 
      especially during migration. 
   m. The software provides controls that prevent dev and test environments 
      from performing production specific functions like sending email to end 
      users. 
   n. The software allows programming with asp and asp.net. 
   o. For any authentication managed by the software, authentication 
      attempts are logged. 
   p. For any passwords managed by the software, the application enforces 
      good password strength with length and character type controls, with 
      preference give to lockout from CMS after unsuccessful attempts. 

IMPORTANT 
   q. The software should allow for integration with MS Active Directory for 
      authentication. 
   r. The software bug list should be available. 
   s. Web content should be easily exportable. 
   t. The software should have mechanisms for deployment of code from dev, 
      to test, to production. 

NICE TO HAVE 
   u. The software should have well documented, open, standards based APIs. 
   v. The software should allow for session time‐outs for both application 
       content managers and administrators. 
   w. The software should provide activity audits for content and key 
       configuration changes, including changes to user rights and privileges. 

                             73-RFP20583
                                                                                      19

           x. The software should allow for the code base to be exposed so that 
              developers can understand system function. 
           y. The software should provide some measure of antivirus capability for 
              content uploaded via the application interface. 

 
SUBMISSION REQUIREMENTS 
 
Please submit a proposal that includes the following: 
 
     Detailed responses to all individual RFP requirements numbered and ordered 
        according to the line item numbers indicated in the RFP. 
     A project plan with task level detail. 
     Evidence of sustained financial stability such as certified Statement of Financial 
        Position or prospectus including this information. Status of any active or 
        anticipated law suits should be identified along with the expected impact to 
        finances if lost. 
     A minimum of three client references, preferably academic, for which your firm 
        has done similar projects (complete Attachment A).  
     A timetable for completing this project that fits within the overall timeframe 
        required by WCU. 
     The cost, broken down by project deliverables. Additional optional cost items 
        must be clearly identified. 
     Detailed listing and description of ongoing costs. 
     Any other information you consider to be helpful, especially that which helps us 
        understand what sets your company apart from your competition. 
         
Finalists will be required to conduct a system presentation November 1‐9, and provide a 
system test drive.  Vendors should be able to demonstrate an automated migration of at 
least 25 www.wcu.edu web pages, and allow hands‐on testing of key features by 10‐15 
members of the project task force. 
 
EVALUATION CRITERIA 
 
Western Carolina University will use the following criteria in evaluating proposals 
received in response to this RFP. The successful proposal will be the proposal submitted 
in response to this RFP by the submittal deadline, and is the most advantageous to 
Western Carolina University. Western Carolina University personnel will evaluate 
proposals. The evaluation of proposals and the selection of the successful proposal will 
be based on the information provided by the vendor in its proposal (80%), overall price 
(15%), and information provided by references (5%). 
 
Consideration may also be given to any additional information helpful to the University. 
Western Carolina University is not bound to accept the lowest priced proposal if that 

                                     73-RFP20583
                                                                                     20

proposal is not the most advantageous to the university as determined by Western 
Carolina University. 
 
Completeness of Proposal 
 
Any proposal that does not contain each element described in this RFP, fully completed, 
initialed or executed, as appropriate, may be judged to be nonresponsive and may not 
be considered further. 
 
Scoring Method 
 
A combined weighting/scoring method will be used to evaluate to what degree each 
requirement is met, allowing for careful consideration of different criteria.   
 
Weighting/Scoring Methodology:  A point range of 0‐9 is applied to each of the 
weighted categories.   
 
Critical: 0, 7‐9 
         0, not met 
         7, partially met 
         8, fully met 
         9, exceeded 
 
Important: 0, 4‐6 
         0, not met 
         4, partially met 
         5, fully met 
         6, exceeded 
 
Nice to Have: 0, 1‐3 
         0, not met 
         1, partially met 
         2, fully met 
         3, exceeded 
 
Proposals ordered by total weighted scores. The results provide a short list of the top 
vendors who will be included in the final selection process. 
 
 
PROPOSAL REQUIREMENTS 
 
The response to this RFP shall consist of the following sections: 
 
     1. Corporate Background and Experience 
         This section shall include background information on the vendor and should give 
                                     73-RFP20583
                                                                                        21

      details of experience with similar projects. A list of a minimum of three 
      references (including contact persons and telephone numbers) for whom similar 
      work has been performed shall be included. This section must include the 
      proposed staffing, deployment and organization of personnel to be assigned to 
      this project. The vendor shall provide information as to the qualifications and 
      experience of all executive, managerial, legal and professional personnel to be 
      assigned to this project, including resumes citing experience with similar projects 
      and the responsibilities to be assigned to each person. 
       
   2. Technical Approach  
      This section shall include in narrative, outline, and/or graph form the vendor’s 
      approach to accomplishing the tasks outlined in this RFP. A broad brush plan 
      with a description of each task and deliverable and the schedule for 
      accomplishing each shall be included. Also indicate the commitments of 
      University staff required under the proposal (for example, 10 hours of interviews 
      with faculty or staff). Please list any other local resources the University will be 
      expected to provide. 
       
   3. Cost Proposal  
      Itemized project costs must be provided. In addition, the vendor is encouraged 
      to provide a daily rate for extending services in the event that additional services 
      are identified in the process of completing the project deliverables. 
 
 
THE PROCUREMENT PROCESS 
 
1. Request for Proposals (RFP) is issued. 
2. Pre‐bid conference to be held via Go To Meeting or conference call to allow vendors 
   to seek clarity on any part of the RFP. Questions must be submitted in writing, 
   following the conference, and responses will be shared with all potential vendors. 
3. Proposals in one original and four copies will be received from each vendor in a 
   sealed envelope or package. Each original shall be signed and dated by an official 
   authorized to bind the firm. Unsigned proposals will not be considered. 
4. All proposals must be received by the issuing agency not later than the date and 
   time specified on the cover sheet of this RFP. 
5. At that date and time, the package containing the proposals from each responding 
   firm will be opened publicly and the name of the vendor and cost(s) offered will be 
   announced. Interested parties are cautioned that these costs and their components 
   are subject to further evaluation for completeness and correctness, and therefore 
   may not be an exact indicator of a vendor's pricing position. At their option, the 
   evaluators may request oral presentations or discussion with any or all vendors for 
   the purpose of clarification or to amplify the materials presented in any part of the 
   proposal. However, vendors are cautioned that the evaluators are not required to 
   request clarification; therefore, all proposals should be complete and reflect the 
   most favorable terms available from the vendor.  
                                     73-RFP20583
                                                                                           22

6. Proposals will be evaluated according to a scoring/weighted criterion.   
 
    
   Award of a contract to one vendor does not mean that the other proposals lacked 
   merit, but that all factors considered, the selected proposal was deemed to provide 
   the best value to the State. 



           GENERAL INFORMATION ON SUBMITTING PROPOSALS

1. EXCEPTIONS: All proposals are subject to the terms and conditions outlined
   herein. All responses shall be controlled by such terms and conditions and the
   submission of other terms and conditions, price lists, catalogs, and/or other
   documents as part of an offeror's response will be waived and have no effect
   either on this Request for Proposals or on any contract that may be awarded
   resulting from this solicitation. Offeror specifically agrees to the conditions set
   forth in the above paragraph by signature to the proposal.

2. CERTIFICATION: By executing the proposal, the signer certifies that this proposal
   is submitted competitively and without collusion (G.S. 143-54), that none of our
   officers, directors, or owners of an unincorporated business entity has been convicted
   of any violations of Chapter 78A of the General Statutes, the Securities Act of 1933,
   or the Securities Exchange Act of 1934 (G.S. 143-59.2), and that we are not an
   ineligible vendor as set forth in G.S. 143-59.1. False certification is a Class I felony.

3. DEBARMENT CERTIFICATION: By signing the execution page, bidder certifies
   to the best of its knowledge and belief, that it and its principals are not presently
   debarred, suspended, proposed for debarment, declined ineligible or voluntary
   excluded from covered transactions by any Federal or State agency.

4. ORAL EXPLANATIONS: Western Carolina University (WCU) shall not be bound
   by oral explanations or instructions given at any time during the competitive process
   or after award.

5. REFERENCE TO OTHER DATA: Only information that is received in response to
   this RFP will be evaluated; reference to information previously submitted shall not be
   evaluated.

6. ELABORATE PROPOSALS: Elaborate proposals in the form of brochures or other
   presentations beyond that necessary to present a complete and effective proposal are
   not desired.

   In an effort to support the sustainability efforts of the State of North Carolina, we
   solicit your cooperation in this effort.



                                       73-RFP20583
                                                                                         23

   It is desirable that all responses meet the following requirements:

   1. All copies are printed double sided.
   2. All submittals and copies are printed on recycled paper with a minimum post-
      consumer content of 30% and indicate this information accordingly on the
      response.
   3. Unless absolutely necessary, all proposals and copies should minimize or
      eliminate use of nonrecyclable or non re-usable materials such as plastic
      report covers, plastic dividers, vinyl sleeves, and GBC binding. Three-ringed
      binders, glued materials, paper clips, and staples are acceptable.
   4. Materials should be submitted in a format that allows for easy removal and
      recycling of paper materials.

7. COST FOR PROPOSAL PREPARATION: Any costs incurred by offeror’s in
   preparing or submitting offers are the offeror’s' sole responsibility; WCU will not
   reimburse any offeror for any costs incurred prior to award.

8. TIME FOR ACCEPTANCE: Each proposal shall state that it is a firm offer that
   may be accepted within a period of 30 days. Although the contract is expected to be
   awarded prior to that time, the 30-day period is requested to allow for unforeseen
   delays.

9. TITLES: Titles and headings in this RFP and any subsequent contract are for
   convenience only and shall have no binding force or effect.

10. CONFIDENTIALITY OF PROPOSALS: In submitting its proposal, the offeror
    agrees not to discuss or otherwise reveal the contents of the proposal to any source
    outside of WCU, government or private, until after the award of the contract. Offeror
    not in compliance with this provision may be disqualified, at the option of WCU,
    from contract award. Only discussions authorized by WCU are exempt from this
    provision.

11. RIGHT TO SUBMITTED MATERIAL: All responses, inquiries, or
    correspondence relating to or in reference to the RFP, and all other reports, charts,
    displays, schedules, exhibits, and other documentation submitted by the offeror shall
    become the property of WCU when received.

12. OFFEROR’S REPRESENTATIVE: Each offeror shall submit with its proposal the
    name, address, and telephone number of the person(s) with authority to bind the firm
    and answer questions or provide clarification concerning the firm's proposal.

13. SUBCONTRACTING: Offeror may propose to subcontract portions of the work
    provided that their proposals clearly indicate what work they plan to subcontract and
    to whom and that all information required about the prime contractor is also included
    for each proposed subcontractor.

14. PROPRIETARY INFORMATION: Trade secrets or similar proprietary data which
    the offeror does not wish disclosed to other than personnel involved in the evaluation
                                      73-RFP20583
                                                                                         24

   or contract administration will be kept confidential to the extent permitted by NCAC
   T01:05B.1501 and G.S. 132-1.3 if identified as follows: Each page shall be identified
   in boldface at the top and bottom as "CONFIDENTIAL." Any section of the proposal
   which is to remain confidential shall also be so marked in boldface on the title page of
   that section. Cost information may not be deemed confidential. In spite of what is
   labeled as confidential, the determination as to whether or not it is shall be
   determined by North Carolina law.

15. HISTORICALLY UNDERUTILIZED BUSINESSES: Pursuant to General Statute
    143-48 and Executive Order #77, WCU 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.

16. DECLINE TO OFFER: Any firm which receives a copy of the RFP but which
    declines to make an offer is requested to send a written “Decline to Offer" to WCU.
    Failure to respond as requested may subject the firm to removal from consideration
    on future requirements.

17. PROTEST PROCEDURES: When a bidder wants to protest any contract awarded
    by a university, they must submit a written request to the procurement officer at the
    address of the issuing agency. This request must be received in that office within
    thirty (30) consecutive calendar days from the date of the contract award. Protest
    letters must contain specific reasons and any supporting documentation for the
    protest. Note: Contract award notices are sent only to those actually awarded
    contracts, and not to every person or firm responding to this solicitation. Bid status
    and Award notices are posted on the Internet at http://www.state.nc.us/pandc/ for bids
    exceeding $10,000. All protests will be handled pursuant to the North Carolina
    Administrative Code, Title 1, Department of Administration, Chapter 5, Purchase and
    Contract, Section 5B.1519. (See Protest Information at
    http://www.doa.state.nc.us/PandC/protests.pdf for more information.)


18. VENDOR REGISTRATION AND SOLICITATION NOTIFICATION
    SYSTEM: Vendor Link NC allows vendors to electronically register free with the
    State to receive electronic notification of current procurement opportunities for goods
    and services available on the Interactive Purchasing System. Online registration and
    other purchasing information are available on our Internet web site:
    http://www.doa.state.nc.us/PandC/.

19. RECIPROCAL PREFERENCE: G.S. 143-59 establishes a reciprocal preference
    law to discourage other states from applying in-state preferences against North
    Carolina’s resident offeror. The “Principal Place of Business” is defined as the
    principal place from which the trade or business of the offeror is directed or managed.




                                      73-RFP20583
                                                                                                                25

     NORTH CAROLINA GENERAL CONTRACT TERMS AND CONDITIONS
                (Contractual and Consultant Services)

                     FOR WESTERN CAROLINA UNIVERSITY (WCU)

1.   GOVERNING LAW: This contract is made under and shall be governed and construed in accordance
     with the laws of the State of North Carolina.

2.   SITUS: The place of this contract, its situs and forum, shall be North Carolina , where all matters,
     whether sounding in contract or tort, relating to is validity, construction, interpretation and enforcement
     shall be determined

3.   INDEPENDENT CONTRACTOR: The Contractor shall be considered to be an independent contractor
     and as such shall be wholly responsible for the work to be performed and for the supervision of its
     employees. The Contractor represents that it has, or will secure at its own expense, all personnel
     required in performing the services under this agreement. Such employees shall not be employees of,
     or have any individual contractual relationship with WCU.

4.   KEY PERSONNEL: The Contractor shall not substitute key personnel assigned to the performance of
     this contract without prior written approval by WCU’s Contract Administrator. The individuals
     designated as key personnel for purposes of this contract are those specified in the Contractor’s
     proposal.

5.   SUBCONTRACTING: Work proposed to be performed under this contract by the Contractor or its
     employees shall not be subcontracted without prior written approval of WCU’s Contract Administrator.
     Acceptance of an offeror’s proposal shall include any subcontractor(s) specified therein.

6.   PERFORMANCE AND DEFAULT: If, through any cause, the Contractor shall fail to fulfill in timely and
     proper manner the obligations under this agreement, WCU shall thereupon have the right to terminate
     this contract by giving written notice to the Contractor and specifying the effective date thereof. In that
     event, all finished or unfinished deliverable items under this contract prepared by the Contractor shall, at
     the option of WCU, become its property, and the Contractor shall be entitled to receive just and
     equitable compensation for any satisfactory work completed on such materials. Notwithstanding, the
     Contractor shall not be relieved of liability to WCU for damages sustained by WCU by virtue of any
     breach of this agreement, and WCU may withhold any payment due the Contractor for the purpose of
     setoff until such time as the exact amount of damages due WCU from such breach can be determined.

     In case of default by the Contractor, WCU may procure the services from other sources and hold the
     Contractor responsible for any excess cost occasioned thereby. WCU reserves the right to require
     performance bond or other acceptable alternative guarantees from successful offeror without expense
     to WCU.

     In addition, in the event of default by the Contractor under this contract, the State may immediately
     cease doing business with the Contractor, immediately terminate for cause all existing contracts the
     State has with the Contractor, and de-bar the Contractor from doing future business with the State.

     Upon the Contractor filing a petition for bankruptcy or the entering of a judgment of bankruptcy by or
     against the Contractor, the State may immediately terminate, for cause, this contract and all other
     existing contracts the Contractor has with the State, and de-bar the Contractor from doing future
     business with the State.

     Neither party shall be deemed to be in default of its obligations hereunder if and so long as it is
     prevented from performing such obligations by any act of war, hostile foreign action, nuclear explosion,
     riot, strikes, civil insurrection, earthquake, hurricane, tornado, or other catastrophic natural event or act
     of God.

7.   TERMINATION: WCU may terminate this agreement at any time by 30 days notice in writing from the
     WCU to the Contractor. In that event, all finished or unfinished deliverable items prepared by the
     Contractor under this contract shall, at the option of WCU, become its property. If the contract is
     terminated by WCU as provided herein, the Contractor shall be paid for services satisfactorily
     completed, less payment or compensation previously made.

                                                73-RFP20583
                                                                                                            26

8.   PAYMENT TERMS: Payment terms are Net not later than 30 days after receipt of correct invoice(s) or
     acceptance of services, whichever is later, or in accordance with any special payment schedule
     identified in this RFP. The using agency is responsible for all payments to the contractor under the
     contract. Payment by some agencies may be made by procurement card and it shall be accepted by the
     contractor for payment if the contractor accepts that card (Visa, Mastercard, etc.) from other customers.
     If payment is made by procurement card, then payment may be processed immediately by the
     contractor.

9.   AVAILABILITY OF FUNDS: Any and all payments to the Contractor are dependent upon and subject
     to the availability of funds to WCU for the purpose set forth in this agreement.

10. CONFIDENTIALITY: Any information, data, instruments, documents, studies or reports given to or
    prepared or assembled by the Contractor under this agreement shall be kept as confidential and not
    divulged or made available to any individual or organization without the prior written approval of WCU.

11. CARE OF PROPERTY: The Contractor agrees that it shall be responsible for the proper custody and
    care of any property furnished it for use in connection with the performance of this contract or
    purchased by it for this contract and will reimburse WCU for loss of damage of such property.

12. COPYRIGHT: No deliverable items produced in whole or in part under this agreement shall be the
    subject of an application for copyright by or on behalf of the Contractor.


13. ACCESS TO PERSONS AND RECORDS: The State Auditor and the using agency’s internal auditors
    shall have access to persons and records as a result of all contracts or grants entered into by State
    agencies or political subdivisions in accordance with General Statute 147-64.7 and Session Law 2010-
    194, Section 21 (i.e., the State Auditors and internal auditors may audit the records of the contractor
    during the term of the contract to verify accounts and data affecting fees or performance).

14. ASSIGNMENT: No assignment of the Contractor’s obligations nor the Contractor’s right to receive
    payment hereunder shall be permitted. However, upon written request approved by the issuing
    purchasing authority, WCU may:
         a. Forward the contractor’s payment check(s) directly to any person or entity designated by the
    Contractor, or
         b. Include any person or entity designated by Contractor as a joint payee on the Contractor’s
    payment check(s).
    In no event shall such approval and action obligate WCU to anyone other than the Contractor and the
    Contractor shall remain responsible for fulfillment of all contract obligations.

15. COMPLIANCE WITH LAWS: The Contractor shall comply with all laws, ordinances, codes, rules,
    regulations, and licensing requirements that are applicable to the conduct of its business, including
    those of federal, state, and local agencies having jurisdiction and/or authority.

16. AFFIRMATIVE ACTION: The Contractor shall take affirmative action in complying with all Federal and
    State requirements concerning fair employment and employment of people with disabilities, and
    concerning the treatment of all employees without regard to discrimination by reason of race, color,
    religion, sex, national origin, or disability.

17. INSURANCE: During the term of the contract, the contractor at its sole cost and expense shall provide
    commercial insurance of such type and with such terms and limits as may be reasonably associated
    with the contract. As a minimum, the contractor shall provide and maintain the following coverage and
    limits:

         a.   Worker’s Compensation - The contractor shall provide and maintain Worker’s
              Compensation Insurance, as required by the laws of North Carolina, as well as employer’s
              liability coverage with minimum limits of $150,000.00, covering all of Contractor’s employees
              who are engaged in any work under the contract. If any work is subcontracted, the contractor
              shall require the subcontractor to provide the same coverage for any of its employees engaged
                    in any work under the contract.

         b.   Commercial General Liability - General Liability Coverage on a Comprehensive Broad Form on
              an occurrence basis in the minimum amount of $500,000.00 Combined Single Limit. (Defense
                  cost shall be in excess of the limit of liability.)
                                              73-RFP20583
                                                                                                                    27

         c.   Automobile - Automobile Liability Insurance, to include liability coverage, covering all owned,
              hired and non-owned vehicles, used in connection with the contract. The minimum combined
              single limit shall be $150,000.00 bodily injury and property damage; $150,000.00
              uninsured/under insured motorist; and $1,000.00 medical payment.

    Providing and maintaining adequate insurance coverage is a material obligation of the contractor and is
    of the essence of this contract. All such insurance shall meet all laws of the State of North Carolina.
    Such insurance coverage shall be obtained from companies that are authorized to provide such
    coverage and that are authorized by the Commissioner of Insurance to do business in North Carolina.
    The contractor shall at all times comply with the terms of such insurance policies, and all requirements
    of the insurer under any such insurance policies, except as they may conflict with existing North
    Carolina laws or this contract. The limits of coverage under each insurance policy maintained by the
    contractor shall not be interpreted as limiting the contractor’s liability and obligations under the contract.

18. ADVERTISING: Contractor agrees not to use the existence of this contract, the name Western
    Carolina University (WCU), or the name of the State of North Carolina as part of any commercial
    advertising.

19. ENTIRE AGREEMENT: This contract and any documents incorporated specifically by reference
    represent the entire agreement between the parties and supersede all prior oral or written statements or
    agreements. This Request for Proposals (if one has been used), any addenda thereto, and the offeror’s
    proposal are incorporated herein by reference as though set forth verbatim.

    All promises, requirements, terms, conditions, provisions, representations, guarantees, and warranties
    contained herein shall survive the contract expiration or termination date unless specifically provided
    otherwise herein, or unless superseded by applicable Federal or State statutes of limitation.

20. AMENDMENTS: This contract may be amended only by written amendments duly executed by WCU
    and the Contractor. The NC Division of Purchase and Contract shall give prior approval to any
    amendment to a contract awarded through that office.

21. TAXES: G.S. 143-59.1 bars the Secretary of Administration from entering into contracts with vendors if
    the vendor or its affiliates meet one of the conditions of G. S. 105-164.8(b) and refuse to collect use tax
    on sales of tangible personal property to purchasers in North Carolina. Conditions under G. S. 105-
    164.8(b) include: (1) Maintenance of a retail establishment or office, (2) Presence of representatives in
    the State that solicit sales or transact business on behalf of the vendor and (3) Systematic exploitation
    of the market by media-assisted, media-facilitated, or media-solicited means. By execution of the bid
    document the vendor certifies that it and all of its affiliates, (if it has affiliates), collect(s) the appropriate
    taxes.

22. YEAR 2000 COMPLIANCE/WARRANTY: Vendor shall ensure the product(s) and service(s) furnished
    pursuant to this agreement (“product” shall include, without limitation, any piece of equipment,
    hardware, firmware, middleware, custom or commercial software, or internal components, subroutines,
    and interfaces therein) which perform any date and/or time data recognition function, calculation, or
    sequencing, will support a four digit year format, and will provide accurate date/time data and leap year
    calculations on and after December 31, 1999, at the same level of functionality for which originally
    acquired without additional cost to the user. This warranty shall survive termination or expiration of the
    agreement.

23. GENERAL INDEMNITY: The contractor shall hold and save the State, its officers, agents, and
    employees, harmless from liability of any kind, including all claims and losses accruing or resulting to
    any other person, firm, or corporation furnishing or supplying work, services, materials, or supplies in
    connection with the performance of this contract, and from any and all claims and losses accruing or
    resulting to any person, firm, or corporation that may be injured or damaged by the contractor in the
    performance of this contract and that are attributable to the negligence or intentionally tortious acts of
    the contractor provided that the contractor is notified in writing within 30 days that the State has
    knowledge of such claims. The contractor represents and warrants that it shall make no claim of any
    kind or nature against the State’s agents who are involved in the delivery or processing of contractor
    goods to the State. The representation and warranty in the preceding sentence shall survive the
    termination or expiration of this contract.




                                                  73-RFP20583
                                                                                                              28

24. OUTSOURCING: Any vendor or subcontractor providing call or contact center services to the State of
    North Carolina shall disclose to inbound callers the location from which the call or contact center
    services are being provided.

    If, after award of a contract, the contractor wishes to outsource any portion of the work to a location
    outside the United States, prior written approval must be obtained from the State agency responsible for
    the contract.

    Vendor must give notice to the using agency of any relocation of the vendor, employees of the vendor,
    subcontractors of the vendor, or other persons performing services under a state contract outside of the
    United States.

25. By EXECUTIVE ORDER 24, issued by Governor Perdue, and N.C. G.S.§ 133-32, it is unlawful for any
    vendor or contractor ( i.e. architect, bidder, contractor, construction manager, design professional,
    engineer, landlord, offeror, seller, subcontractor, supplier, or vendor), to make gifts or to give favors to
    any State employee of the Governor’s Cabinet Agencies (i.e., Administration, Commerce, Correction,
    Crime Control and Public Safety, Cultural Resources, Environment and Natural Resources, Health and
    Human Services, Juvenile Justice and Delinquency Prevention, Revenue, Transportation, and the
    Office of the Governor). This prohibition covers those vendors and contractors who:
         (1) have a contract with a governmental agency; or
         (2) have performed under such a contract within the past year; or
         (3) anticipate bidding on such a contract in the future.

         For additional information regarding the specific requirements and exemptions, vendors and
         contractors are encouraged to review Executive Order 24 and G.S. Sec. 133-32.

         Executive Order 24 also encouraged and invited other State Agencies to implement the
         requirements and prohibitions of the Executive Order to their agencies. Vendors and contractors
         should contact other State Agencies to determine if those agencies have adopted Executive Order
         24.”

By execution of this document or any response in this procurement, you attest, for your entire organization
and its employees or agents, that you are not aware that any such gift has been offered, accepted, or
promised by any employees of your organization.


                                                                                                       9/14/2011




                                               73-RFP20583
                                                                                           29


     Attachment A: Reference Information
     The Vendor shall provide the following reference information for which the proposed
     system has been installed and operating.

                                          References
1.   Name of Client Agency
     Address

     City                                        State          ZIP Code
     Contact                                                    Title
     Contact Telephone                           Contact Fax
     Contact E-Mail
     Description of the project
     and/or services provided to
     the client.


2.   Name of Client Agency
     Address

     City                                        State          ZIP Code
     Contact                                                    Title
     Contact Telephone                           Contact Fax
     Contact E-Mail
     Description of the project
     and/or services provided to
     the client.


3.   Name of Client Agency
     Address

     City                                        State          ZIP Code
     Contact                                                    Title
     Contact Telephone                           Contact Fax
     Contact E-Mail
     Description of the project
     and/or services provided to
     the client.




                                         73-RFP20583

								
To top