TITUS SOFTWARE

Trade Agreement: NAFTA/AIT/Canada-Peru FTA/Canada-Colombia FTA
Tendering Procedures: Generally only one firm has been invited
to bid
Attachment: None
Non-Competitive Procurement Strategy: Exclusive Rights
Comprehensive Land Claim Agreement: No
Vendor Name and Address:
TITUS INTERNATIONAL INC
343 Preston Street
Suite 800
Ottawa Ontario
Canada
K1S1N4
Nature of Requirements:
Advanced Contract Award Notice (ACAN)

FILE NUMBER: 24062-120380
CONTRACTING OFFICER: Christopher Farinaccio
TELEPHONE NUMBER: 819-956-2954
DESCRIPTIVE TITLE: Network System Classification

REQUIREMENT: Message Classification and Document Classification
Standard Suite, including one year of Maintenance and Support
Services with the Option to extend the contract for four (4)
periods of one (1) year each on behalf of the Treasury Board of
Canada Secretariat (TBS). The Department of Public Works and
Government Services Canada (PWSGC) intends to enter into a
sole-source contract with TITUS Inc., 343 Preston Street,
Ottawa, Ontario, Canada. The estimated value of the contract is
$135,000.

The software product listed above is the only one that meets all
of the mandatory requirements listed in ANNEX A. TITUS Inc. is
the author of the software in question, and the only company
that can deliver on the contract due to exclusive proprietary
rights.

Section 6.(d) of the Government Contract Regulations is being
invoked in this procurement as only one firm is capable of
performing the contract. Articles 506.12(a) of AIT is
applicable on the basis of limited tendering due to
compatibility with existing products, to recognize exclusive
rights, such as exclusive licenses, copyright and patent rights,
or to maintain specialized products that must be maintained by
the manufacturer or its representative.

Articles 1016.2(d) of NAFTA are applicable on the basis of
limited tendering due to reasons where, for additional
deliveries by the original supplier that are intended either as
replacement parts or continuing services for existing supplies,
services or installations, or as the extension of existing
supplies, services or installations, where a change of supplier
would compel the entity to procure equipment or services not
meeting requirements of interchangeability with already existing
equipment or services, including software to the extent that the
initial procurement of the software was covered by this Chapter.

PERIOD OF CONTRACT: The contractor shall deliver the licensed
software and documentation no later than March 31st, 2012. The
Contract will be for a period of one (1) year. Canada retains
the right to extend the period of the Contract for up to four
(4) additional one-year periods.

CLOSING DATE AND TIME FOR WRITTEN SUPPLIER RESPONSES CHALLENGING
THIS REQUIREMENT IS 2:00 p.m. EST, March 9th, 2012.

Refer to the attached ANNEX A for details concerning this
requirement. You are hereby notified that the Government
intends to solicit a bid and negotiate with one firm only as
identified above.

If you wish to submit a written response showing that you are
capable of meeting this requirement, it must be done no later
than the specified closing date and time. Responses must be
submitted to Christopher Farinaccio, by email only, to
C••••••••@••••••••.••.ca. Responses transmitted
by facsimile or mail courier will not be accepted. The file
number, contracting officer's name, and the closing date of the
ACAN must appear in the email. As it is intended to proceed in
a timely manner, responses received after the closing date will
not be considered.

Responses received on or before the closing date will be
considered solely for the purpose of deciding whether or not to
conduct a competitive procurement. Information provided will be
used by the Crown for technical evaluation purposes only and is
not to be construed as a competitive solicitation. Your written
response must provide sufficient evidence (e.g. specifications,
technical data, drawings, or any other proof) that clearly
demonstrates that your product or service is capable of
fulfilling this requirement.

Suppliers that have submitted a response will be notified in
writing of PWGSC's decision to continue with the non-competitive
procurement or to compete the requirement.

ANNEX A
DATED February 21, 2012

STATEMENT OF WORK
FOR
TBS NETWORK SYSTEM CLASSIFICATION

TABLE OF CONTENTS

1. PLATFORM REQUIREMENTS

2. USER INTERFACE REQUIREMENTS

3. VISUAL INDICATORS

4. SECURITY

5. MAINTENANCE REQUIREMENTS

6. PROFESSIONAL SERVICES REQUIREMENTS
1. Platform Requirements:
1.1. The products shall work on Microsoft Office and Microsoft
Outlook 2003, 2007 and 2010, Outlook Web Access 2007 and 2010.

2. User Interface Requirements:
2.1. The products shall enable the selection of a classification
label via a toolbar (for Office 2003, OWA) or ribbon and task
pane (for Office 2007, 2010)
2.2. The products must display classification of received email
or document in the toolbar (Office 2003, OWA) or ribbon and
task pane (Office 2007, 2010).
2.3. The products must provide a method of context-sensitive
guided classification in Office 2003, 2007 and 2010.
2.4. The products must provide context-sensitive labeling using
hierarchical menus in Office 2003, 2007 and 2010
2.5. The products must provide an option to enable users to
classify, mark, and protect their email with only one mouse
click in Office or Outlook 2003, 2007 and 2010.
2.6. The products must provide classification labels that are
customizable in Office 2003, 2007 and 2010
2.7. The products must provide an ability to establish a default
selection for any classification in Office 2003, 2007 and 2010.
2.8. The products must provide an ability to prompt users to
change defaults if sensitive content is found through built in
email scanning engines in Outlook 2003, 2007 and 2010.
2.9. The products must provide an ability to force selection at
any classification level in Office 2003, 2007 and 2010.
2.10. The products must provide the ability to support an
unlimited number of levels of classification data (e.g.
Classification, Project, Retention etc.) in Outlook 2003, 2007
and 2010 and up to 7 levels in OWA, Word, Excel and PowerPoint.
2.11. The products must provide multiple classification types
(e.g. dropdowns, multi-selects, calendar, and user type-in) in
Office 2003, 2007 and 2010.
2.12. The products must provide customizable HTML Help to
provide application specific help to users in Office 2003, 2007
and 2010.
2.13. The products must provide customizable Help Tooltips to
provide context sensitive help to users in Outlook 2003, 2007
and 2010.
2.14. The products must provide customizable warnings and error
messages in Office 2003, 2007 and 2010.
2.15. The products must provide support for the classification
of calendar appointments and tasks in Outlook 2003, 2007 and
2010.
2.16. The products must support Sorting, Filtering and searching
capability of Outlook Inbox by leveraging classifications in
Outlook 2003, 2007 and 2010.
2.17. The products must provide the ability for classifications
to be presented to various users based on their role in the
organization in Office 2003, 2007 and 2010.
2.18. The products must provide classification selections that
can be controlled by the user's Active Directory properties in
Outlook 2003, 2007, and 2010.
2.19. The products must provide support for retention periods or
declassification dates using a date field in Office 2003,
2007, and 2010.
2.20. The products must provide support for the auto-population
of Microsoft Outlook categories to provide visual cues and
enhanced searching in the user's inbox in Outlook 2003, 2007
and 2010.
2.21. The products must provide support for portion marking of
message body and paragraphs in Office 2003, 2007, and 2010.

3. Visual Indicators:
3.1. The products must support the ability to insert visual
labels in the first line of a message in Outlook and OWA 2003,
2007 and 2010.
3.2. The products must support the ability to insert visual
labels in last line of a message in Outlook and OWA 2003, 2007
and 2010.
3.3. The products must support the ability to ensure that Visual
labels in first and last line of message can be different in
Outlook and OWA 2003, 2007 and 2010.
3.4. The products must support the capability to add Visual
markers based on specific classifications selected. (e.g.
Secret and Finance Department Only means that a body tags
should be formatted in a particular way) in Outlook and OWA
2003, 2007 and 2010.
3.5. The products must support the insertion of classification
labels in the subject line (preceding or trailing) in Outlook
and OWA 2003, 2007 and 2010.
3.6. The products must support the ability to Label in subject
lines by abbreviation in Outlook and OWA 2003, 2007 and 2010.
3.7. The products must support a Signature or disclaimer
automatically added to message based on the classification in
Outlook and OWA 2003, 2007 and 2010.
3.8. The products must support visual labels that can include
static and dynamic values (e.g. "Classification:
Confidential", where "Confidential" is dynamically generated) in
Outlook and OWA 2003, 2007 and 2010.
3.9. The products must support labels that can be formatted with
colors when using HTML or RTF message format in Outlook and
OWA 2003, 2007 and 2010.
3.10. The products must support labels that can be formatted
using any font or size when using HTML or RTF message format in
Outlook and OWA 2003, 2007 and 2010.
3.11. The products must support the Insertion of labels in
header and/or footer of document, along with any disclaimers
or additional text as required in Word, Excel and PowerPoint
2003, 2007 and 2010.
3.12. The products must support the ability to customize the
font, size, color and location of headers and footers in Word,
Excel and PowerPoint 2003, 2007 and 2010.
3.13. The products must support the addition of specific visual
markers that can be determined based on classifications
selected in Word, Excel and PowerPoint 2003, 2007 and 2010.
3.14. The products must support the Insertion of a
classification watermark in a document in Microsoft Word 2003,
2007 and 2010.
3.15. The product must support the ability to ensure that the
current user's name can be placed as watermark in a document
in Microsoft Word 2003, 2007 and 2010.

4. Security:
4.1. The products must support a flexible policy architecture
that allows policies to be associated with any classification
selection in Office 2003, 2007 and 2010.
4.2. The products must support the ability to restrict the
recipients of an e-mail based on classification (i.e. Safe
lists based on Active Directory) in Outlook 2003, 2007 and 2010.
4.3. The products must support the ability to warn users based
on classification of message in Outlook and OWA 2003, 2007 and
2010.
4.4. The products must support the ability to force document
classification before Save or Print in Word, Excel and
PowerPoint 2003, 2007 and 2010.
4.5. The products must support the ability to warn users based
on classification and size of recipient list in Outlook and
OWA 2003, 2007 and 2010.
4.6. The products must support the ability to restrict sending
emails based on domains of recipients, (supporting both
Trusted Domains and Restricted Domains) in Outlook and OWA
2003, 2007 and 2010.
4.7. The products must support the insertion of classification
properties in MAPI so that e-mail can be acted on in exchange
data stores or archival systems in Outlook and OWA 2003, 2007
and 2010.
4.8. The products must support the insertion of metadata in
messages and documents that can be leveraged by DLP,
e-discovery or archival systems in Office 2003, 2007 and 2010.
4.9. The products must support the creation of custom X-headers
for interoperability in Outlook 2003, 2007 and 2010.
4.10. The products must support the ability to force selection
of classifications at all levels independent of each other
before a message is sent or saved (e.g. first and second level
may be mandatory but third is optional) in Outlook and OWA
2003, 2007 and 2010.
4.11. The products must support the ability to automatically
force application of Microsoft Rights Management Services
(RMS) templates (eg. Which can apply rights like "Do Not
Forward") on specific classifications in Outlook 2003, 2007
and 2010.
4.12. The products must support the ability to apply S/MIME
encryption and/or digital signatures based on classification
in Outlook 2003, 2007 and 2010.
4.13. The products must support the ability to warn or prevent
sending if classification is downgraded on Reply/Forward in
Outlook and OWA 2003, 2007 and 2010.
4.14. The products must support the ability to warn or prevent
sending if classification is changed on Reply/Forward in
Outlook 2003, 2007 and 2010.
4.15. The products must support non-repudiated label authoring
to ensure that the labels have not been modified during
transmission in Outlook 2003, 2007 and 2010 and Word, Excel
and PowerPoint 2003, 2007 and 2010.
4.16. The products must support the ability to BCC a specific
mailbox based on classification (e.g. an archiving address) in
Outlook 2003, 2007 and 2010.
4.17. The products must support the ability to provide Event
Logging of classification actions that can be amalgamated in a
centralized place for statistical analysis, auditing of user
actions and forensic evidence in Outlook 2003, 2007 and 2010.
4.18. The products must support attachment checking using
classification metadata in documents and embedded email. E.g.
If a document is classified as Secret and is attached to an
email, the software can ensure that the email is classified at
least Secret in Outlook 2003, 2007 and 2010.
4.19. The products must support attachment checking by filename.
E.g. If a document has the word "Secret" in its filename, the
software can ensure that the email is classified at least
Secret in Outlook 2003, 2007 and 2010.
4.20. The products must support the ability to let users
acknowledge that they've understood the contents of an email in
Outlook 2003, 2007 and 2010.
4.21. The products must support role-based messaging so that
messages can be sent and received via roles (e.g. Land forces
Commander) rather than from the person in Outlook 2003, 2007
and 2010.
4.22. The products must support the ability to prevent users
from sending emails with a blank subject line in Outlook 2003,
2007 and 2010.
4.23. The products must support the ability to read
classifications of some third party classification systems
including BlackBerry classification in Outlook 2003, 2007 and
2010.
4.24. The products must include a content scanning feature that
scans emails and attached Office documents before sending and
warns users if they are about to send sensitive content in
Outlook 2003, 2007 and 2010
4.25. The products must include a Content Review feature that
visually highlights sensitive terms within an email so that
users can remediate any policy violations before the email
leaves the desktop in Outlook 2003, 2007 and 2010
4.26. The products must include a Redaction feature which
enables users to automatically redact (i.e. black out)
sensitive content in an email in Outlook 2003, 2007 and 2010
4.27. The products must include the ability for classifications
to automatically trigger application of Microsoft Rights
Management Services (RMS) templates in Office 2003, 2007 and
2010.
4.28. The products must include the ability to warn or prevent
saving/printing if any classification is downgraded in Word,
Excel and PowerPoint 2003, 2007 and 2010.
4.29. The products must include Signed Trusted Labels that use
digital signatures to ensure that labels have not been modified
during transmission in Word, Excel and PowerPoint 2003, 2007
and 2010.
4.30. The products must support Event Logging of classification
actions that can be amalgamated in a centralized place for
statistical analysis, auditing of user actions and forensic
evidence in Word, Excel and PowerPoint 2003, 2007 and 2010.
4.31. The products must interoperate with PDF conversion tools
by saving classification properties to Keyword property in
Word, Excel and PowerPoint 2003, 2007 and 2010.
4.32. The products must support the ability to scan the document
and advice when a word or phrase may be inappropriate for the
current classification in Word, Excel and PowerPoint 2003,
2007 and 2010.
4.33. The products must support the ability to remove hidden and
sensitive document content using Document Inspector in Word
2007 and 2010 based on a classification label like "FINAL".
4.34. The products must automatically upgrade the overall
document classification to the highest classification denoted
by portion markings in Word, Excel and PowerPoint 2003, 2007
and 2010.
4.35. The products must be able to prevent the viewing of
sensitive material in Outlook Web Access 2007 and 2010.
4.36. The product must support the ability to enforce the
labeling of documents and messages.
4.37. The product must be able to be deployed in a transparent
mode where users will not be forced to label anything and have
a default classification of "Unmarked"
4.38. The product must identify who applied the classification
label on each document and message.
4.39. The product must identify who applied the classification
label on the documents and messages when printed
4.40. The product must support multiple message disclaimers
based on different classification labels.
4.41. The product must have the ability to conduct content
verification by cross referencing a list of key words against
the classification label applied.
4.42. The product must have the ability to support seven (7)
sub-levels of classification.
4.43. The product must support a method for batch marking of
documents.

5. Maintenance Requirements:
5.1. The product must provide the ability to add or change email
labels or information protection policies from a central
location without requiring changes on each individual
workstation.

6. Professional Service Requirements:
6.1. Provide Installation and Configuration Professional
Services to plan, configure and deploy product onsite and
transfer knowledge to TBS personnel in order to ensure
continuous operation at: Treasury Board Secretariat Ottawa,
Ontario.
Delivery Date: Above-mentioned

You are hereby notified that the government intends to negotiate
with one firm only as identified above. Should you have any
questions concerning this requirement, contact the contracting
officer identified above.

An Advance Contract Award Notice (ACAN) allows departments and
agencies to post a notice, for no less than fifteen (15)
calendar days, indicating to the supplier community that it
intends to award a good, service or construction contract to a
pre-identified contractor. If no other supplier submits, on or
before the closing date, a Statement of Capabilities that meets
the requirements set out in the ACAN, the contracting authority
may then proceed with the award. However, should a Statement of
Capabilities be found to meet the requirements set out in the
ACAN, then the contracting authority will proceed to a full
tendering process.

Suppliers who consider themselves fully qualified and available
to provide the services/goods described herein, may submit a
statement of capabilities in writing to the contact person
identified in this Notice on or before the closing date of this
Notice. The statement of capabilities must clearly demonstrate
how the supplier meets the advertised requirements.

The PWGSC file number, the contracting officer's name and the
closing date of the ACAN must appear on the outside of the
envelope in block letters or, in the case of a facsimile
transmission, on the covering page.

The Crown retains the right to negotiate with suppliers on any
procurement.

Documents may be submitted in either official language of Canada.