P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
3.3
CRITERIA
3.3.1
SECTION I. CAPACITY, CAPABILITY, KNOWLEDGE, BACKGROUND
AND EXPERIENCE – 20 Points Possible
3.3.1.1
Provide a brief narrative describing the history of your firm. Identify the number of employees in
your firm, the ownership and if the company has ever filed bankruptcy, been in loan default, or if
there are any pending liens, claims or lawsuits against the firm.
3.3.1.2
Provide demonstrated experience that supports your firm’s ability to perform the services
identified in the goals and intent of this RFP.
3.3.1.6
SUPPORT AND MAINTENANCE
Confirm your firm’s ability to enter a multiple year Maintenance and Support Agreement with
renewals.
Describe whether Maintenance and Support Agreement includes unlimited user support via tollfree phone support on a 7x24x365 basis including holidays.
Describe whether Maintenance and Support Agreement includes unlimited user support via email
and internet on a 7x24x365 basis including holidays.
Describe process for contacting Vendor in case of an outage or other emergency.
3.3.1.7
Identify all services your firm can supply to fulfill the Services.
3.3.1.8
State the name, title or position, telephone number and e-mail address of the individual who
would have primary responsibility for the potential project services resulting from this RFP.
3.3.1.9
Identify names, responsibilities, qualifications and location(s) of staff who will be assigned to the
projects. CNM may at CNM’s sole discretion request removal and replacement of any of the
Contractor’s staff not meeting performance requirements. Changes to staff assigned to projects
made by the Contractor must be mutually agreed to by the Parties.
3.3.1.10
Identify names, responsibilities, qualifications and location(s) of subcontractors and/or consultants
who will be assigned to the projects. All changes to personnel assigned to projects must be
mutually agreed to by the parties.
3.3.1.11
Provide an organizational chart of your firm indicating lines of authority for personnel involved in
performance of this potential contract and relationships of this staff to other programs or functions
of the firm. This chart must also show lines of authority to the next senior level management.
3.3.1.12
Describe if your firm has had a contract terminated for default in the last five (5) years.
Termination for default is defined as notice to stop performance due to the Offeror's non-
3.3.1.3
3.3.1.4
3.3.1.5
Page 1 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
performance or poor performance or if the issue of performance was either (a) not litigated due to
inaction on the part of the Proposer, or (b) litigated and such litigation determined that the
proposer was in default. Submit full details of their terms for default including the other parties’
name, address, and telephone number. Present the Offeror’s position on the matter. CNM will
evaluate the facts and may, at its sole discretion, reject the proposal on the grounds of the past
experience. Indicate if no such termination for default has been experienced by the Offeror in the
past five (5) years.
3.3.2
SECTION II. PROPOSED IMPLEMENTATION PLAN – 40 POINTS
POSSIBLE
3.3.2.1
Submit a detailed proposal identifying your approach for developing an implementation plan that
will allow CNM to deploy an Emergency Notification System meeting the requirements stated in
paragraphs 2. through 2.1.54. The information provided must be in sufficient detail to convey to
the evaluation committee the Offeror’s knowledge of the subjects and skills necessary to perform
the services as described in the RFP.
SYSTEM
3.3.2.2
MANDATORY - Confirm that System is offered as Software as a Service (SaaS), hosted off-site.
3.3.2.2.1
MANDATORY - Describe the Redundancy provided for continued service hosting in the event of
outages or natural disasters such as power, communications or datacenter outages. Please
describe business continuity plan and methods used to ensure redundancy in the event of a power
outage. Specifically describe the hosting infrastructure and methods used to ensure redundancy.
3.3.2.3
MANDATORY - Describe how the System provides security for individual user’s data.
3.3.2.4
MANDATORY - Describe the System’s data back-up and recovery policies and capabilities.
3.3.2.5
MANDATORY - Confirm that the System works across all major wireless carriers and wireless
phone models. Identify any limitations to this and how the system addresses delivery to smaller
carriers.
3.3.2.6
MANDATORY - Confirm that the System is able to detect and re-call busy, no-answer, and
operator intercept telephone numbers upon request.
3.3.2.7
DESIRED - Describe whether System allows for customization of “retry” duration/behavior when
subscriber contacts are not successfully messaged, and if so, how this is handled.
3.3.2.8
DESIRED – Describe whether the System provides carrier grade voice message delivery.
Describe how this is achieved including delivery architecture. Does the system rely on VOIP or
Page 2 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
SS7? If VOIP, please describe any additional features to prevent quality degradation under high
volume or denial of service attacks
3.3.2.9
MANDATORY - Confirm that Notifications are provided in SMS text messages and other
formats as may be required by CNM. Describe your SMS delivery architecture. Do you deliver
messages via SMTP or SMPP? If delivery is via SMTP only, please detail carrier whitelisting
relationships. If SMPP, does your system utilized direct binds or aggregators? What safeguards
are in place to ensure message delivery. Identify all other formats currently available from the
system for delivering Notifications.
3.3.2.10
DESIRED - Describe how the System measures and adjusts for network congestion or oversubscription during emergency conditions.
3.3.2.11
MANDATORY - Describe the System’s ability to use and rebroadcast Common Alerting
Protocol (CAP) v1.2 (or greater).
3.3.2.12
MANDATORY - Describe the System’s phone validation processes to validate the user who
registers owns the phone registered and is able to receive messages.
3.3.2.13
DESIRED - Describe capabilities enabled through APIs or remote applications.
MESSAGING:
3.3.2.14
MANDATORY - Confirm that the System is capable of messaging the entire target CNM student
and staff population (35,000 people) within 10 minutes via text and describe any limitations.
3.3.2.15
MANDATORY - Confirm the System’s ability to broadcast in multiple formats to all registered
users on a 24/7 basis.
3.3.2.16
MANDATORY- Describe the System’s capability of providing unlimited Emergency Notification
text and email messages.
3.3.2.17
MANDATORY - Describe the System’s monitoring utility for an Administrator to confirm
message delivery.
3.3.2.18
MANDATORY - Confirm that the System supports rapid delivery of voice messages. Describe
how this is achieved and any limitations.
3.3.2.19
DESIRED - Describe whether the System supports bridging of voice message recipients into
instant conference calls.
3.3.2.20
MANDATORY - Confirm that the System supports rapid delivery of email messages and identify
any limitations.
Page 3 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
3.3.2.21
MANDATORY - Describe the System’s method for publishing alerts via RSS.
3.3.2.22
DESIRED - Describe whether the System is capable of publishing alerts to social networking sites
such as Facebook, Twitter, etc. and if so, list supported networks and describe how.
3.3.2.23
MANDATORY- Describe how the System is capable of using alternate means to send messages
in the event of a network outage at the college.
3.3.2.24
DESIRED - Describe whether the System allows a broader range of messaging capabilities
beyond the scope of emergency notifications. If so, how are these capabilities handled differently
than Emergency Notifications?
3.3.2.25
DESIRED - Describe how the System supports multi-lingual messaging. What language(s) are
supported? How are translated messages managed in the system? Describe how translation works
and how subscribers signify their preference for a specific language and how messaging works if
a translated message is NOT provided.
SYSTEM ADMINISTRATION
3.3.2.26
MANDATORY - List and describe the System tools provided for administrators to manage user
information within the system.
3.3.2.27
MANDATORY - Describe how System Administrators are able to define target audiences based
on parameters within the system.
3.3.2.28
DESIRED - Describe whether the System allows for user types that are only allowed permission
to message defined groups that are a subset of the larger user population.
3.3.2.29
MANDATORY - Confirm that Administrators are able to create groups and identify any
limitations to this.
3.3.2.30
DESIRED - Describe whether the System allows for opt-in groups, and if so, how this is
achieved.
3.3.2.31
MANDATORY - Confirm that the System allows for various user types. For example, users that
are only allowed to send broadcast alert messages, not edit or access user data.
3.3.2.32
MANDATORY - Describe how the System allows for regular bulk upload of users captured
outside the System.
3.3.2.33
MANDATORY - Confirm that the System allows uploading the recipient list in common formats
and identify all supported formats (e.g., docx, xlsx, .csv, etc.).
Page 4 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
3.3.2.34
MANDATORY - Describe how the System allows the creation, saving and editing of “preprogrammed” alerts and allow for scheduling of alert notifications at future dates and times.
3.3.2.35
MANDATORY - Describe the System’s comprehensive alert reporting capability down to the
individual level.
3.3.2.36
MANDATORY - Describe how the System allows for the cancellation of in-process messages.
3.3.2.37
MANDATORY - Describe all System reports that are available that that detail the integrity of the
contact information in the system. Examples include but are not limited to reports of
undeliverable text messages, emails or phone numbers.
3.3.2.38
MANDATORY – Describe how the System provides a means for administrators to send messages
in the event that an integrated directory service or remote login on campus is unavailable.
USER MANAGEMENT
3.3.2.39
MANDATORY - Confirm that the System allows users to self-register through the college
website.
3.3.2.40
DESIRED - Describe whether the System’s web-based interface allows registered users to modify
their contact information and preferences, and if so, to what degree.
3.3.2.41
DESIRED - Describe whether the System allows user registration via text. If so, the System must
have a mechanism for authenticating those users. Please describe authentication mechanism.
3.3.2.42
MANDATORY - Confirm that the System provides registration authentication to ensure users are
affiliated with the institution.
3.3.2.43
MANDATORY - Confirm that the System performs phone validation processes to validate that
the user who registers owns the phone registered and is able to receive messages.
3.3.2.44
DESIRED - Describe whether the System provides users the ability to set their own
communication preferences (e.g. email and text, no email, etc.).
3.3.2.45
DESIRED - Describe whether the System provides users the ability to opt-out of all text
messaging services except for emergency alerts.
3.3.2.46
DESIRED - Describe whether the System allows users the ability to opt-in or opt-out of text
messages from their phone.
Page 5 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
3.3.2.47
DESIRED - Describe whether the System allows 2-way texting enabling individual users to
interact with college officials, and if so, how this is achieved.
3.3.2.48
DESIRED - Describe whether the System is capable of using Smart-Phone capabilities in the
form of downloadable Apps to provide greater control of messaging to the recipient, and if so,
how this is achieved.
INTEGRATION
3.3.2.49
MANDATORY - Confirm that the proposed System will interface with CNM’s existing network
and infrastructure. Identify whether any changes to CNM’s network or infrastructure are required
for System implementation.
3.3.2.50
DESIRED - Describe all published APIs which will facilitate automated messaging through the
system’s message delivery architecture from an external system.
3.3.2.51
DESIRED - Describe all published APIs which will facilitate automated management of
subscriber information.
MANDATORY - Describe how the System allows subscribers to authenticate via a common
university directory services username/password available via LDAP/Active Directory.
3.3.2.52
3.3.2.53
DESIRED - Describe how the System supports the provisioning of a user session based on a
remote single sign-on (SSO) integration.
3.3.2.54
DESIRED - Describe how the System supports integration with siren systems, bluelight systems,
campus displays and other safety hardware systems used on campus.
3.3.2.55
DESIRED - Describe whether the System is capable of delivering messaging to other media via
CAP, RSS feed or other methods to the following:
Access Control System
On-Campus Computers
Campus Office Phones
Campus outdoor sirens or speakers
Non-campus cell or home phones
Digital signage.
Social media including Facebook and Twitter
Code Blue emergency phones
CNM’s website, www.cnm.edu
3.3.2.55.1
3.3.2.55.2
3.3.2.55.3
3.3.2.55.4
3.3.2.55.5
3.3.2.55.6
3.3.2.55.7
3.3.2.55.8
3.3.2.55.9
IMPLEMENTATION, TRAINING AND SUPPORT
Page 6 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
3.3.2.56
MANDATORY - Confirm that if awarded, your firm shall provide all necessary tools and
services to provide a seamless, uninterrupted implementation, in addition to training and
supporting the System.
3.3.2.57
MANDATORY - Describe the training included in your offer provided for system administrators
and operators.
3.3.2.58
MANDATORY - Confirm 24/7/365 phone and email support is provided with your offered
solution.
OTHER
3.3.2.59
DESIRED - Describe any other related services offered by your firm that CNM may wish to
consider.
3.3.2.60
DESIRED - Provide a brief overview of the general direction of your product’s development
focus over the next three (3) years and how you feel that will impact capabilities to provide the
Services
3.3.2.61
Describe the types of services that would be provided during the project. Explain how your
services will enhance the service of performing projects.
3.3.2.62
Discuss the information and support that would be required from CNM.
3.3.2.63
Identify any subcontractors which would be used during this project and describe their role(s).
3.3.2.64
Provide a time frame, breaking the project into tasks, milestones, and deliverables
3.3.3
SECTION III. REFERENCES - 10 POINTS POSSIBLE
List up to five (5) contracts the Offeror may have had with institutes of higher education or
businesses of similar size and complexity during the last five (5) years that relate to the Offeror’s
ability to perform the service(s) as requested in this RFP. List by company contract reference
numbers, project name/title, contract amount, contract period of performance, date of completion,
contact person’s name, title, address, E-mail address and web address. By responding to this
RFP, the Offeror grants permission to CNM to contact the references. NOTE: ALL
REFERENCES WILL BE CONTACTED BY EMAIL, SO PLEASE BE SURE TO
INCLUDE THE CONTACT’S EMAIL ADDRESS. Do not include CNM as a reference
3.3.4
SECTION IV. ECONOMY & PRICE – 30 POINTS POSSIBLE
Page 7 of 8
P-353 EVALUATION CRITERIA
ANY MODIFICATIONS TO SECTION E SIGNATURE OF FIRM’S AUTHORIZED REPRESENTATIVE RESPONSE FORM OTHER
THAN FILLING IN THE FORM FIELDS IS NOT ACCEPTABLE AND WILL RESULT IN DISQUALIFICATION OF THE
OFFEROR’S RESPONSE. THE GENERAL TERMS AND CONDITIONS ON THE REVERSE SIDE OF CNM’S PURCHASE
ORDER ARE AN EQUAL AND INTEGRAL PART OF THIS REQUEST FOR PROPOSALS (RFP) AND ARE NOTED IN SECTION
C. THE TERMS, CONDITIONS AND SPECIFICATIONS CONTAINED IN THIS RFP ALONG WITH ANY ATTACHMENTS AND
THE OFFEROR’S RESPONSE ARE HEREBY INCORPORATED INTO ALL PURCHASE ORDERS ISSUED AS A RESULT OF
THIS RFP, INCLUDING ANY ADDENDA. CNM RESERVES THE RIGHT TO NEGOTIATE WITH A SUCCESSFUL OFFEROR
(CONTRACTOR) PROVISIONS IN ADDITION TO THOSE STIPULATED IN THIS RFP. THE CONTENTS OF THIS RFP, AS
REVISED AND/OR SUPPLEMENTED, AND THE SUCCESSFUL OFFEROR’S PROPOSAL WILL BE INCORPORATED INTO
THE CONTRACT. SHOULD AN OFFEROR OBJECT TO ANY OF THE CNM STANDARD TERMS AND CONDITIONS THAT
OFFEROR MUST PROPOSE SPECIFIC ALTERNATIVE LANGUAGE THAT WOULD BE ACCEPTABLE TO CNM. GENERAL
REFERENCES TO THE OFFEROR’S TERMS AND CONDITIONS OR ATTEMPTS AT COMPLETE SUBSTITUTIONS ARE NOT
ACCEPTABLE TO CNM AND WILL RESULT IN DISQUALIFICATION OF THE OFFEROR’S PROPOSAL. OFFERORS MUST
PROVIDE A BRIEF STATEMENT OF THE PURPOSE AND IMPACT, IF ANY, OF EACH PROPOSED CHANGE FOLLOWED BY
THE SPECIFIC PROPOSED ALTERNATE WORDING.
3.3.4.1
Proposals should include all charges associated for services requested. Provide rates of all
individuals who may work on the services identified in this proposal. Additional charges, if
required, for various types of help (telephone support, on-site-support). Please provide pricing on
all other services not requested by CNM that may be of interest to CNM that are related to the
Services requested in this RFP.
3.3.4.1.1
Yearly License and/or Service fee
3.3.4.1.2
Yearly Hosting fee (if not included above).
3.3.4.2
If the price or hourly rates are to change in subsequent yearly contract renewals, indicate the
maximum annual increase per year, expressed as a percentage. Cost increase/adjustments will
only be reviewed once a year at time of renewal.
If contractor requests a price
adjustment/increase supporting documentation must accompany the request.
The quoted hourly rates offered in response to this RFP may be decreased for future projects on a
project-by-project basis upon written mutual agreement between the awarded Price Agreement
holder and CNM.
Costs for Services required for which the successful Offeror does not identify shall be borne by
the Offeror and will shall not be charged to CNM. Indicate for what period of time these costs
will be effective.
Page 8 of 8