Docstoc

FINAL Requirements

Document Sample
FINAL Requirements Powered By Docstoc
					                                                                                                                         PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category              Requirement Title        Mandatory                                      Description
  ID
          Government      Administrative filtering                   The solution must provide a capability to Government Administrators to define and
            System                                                   implement filtering, in order to strip unwanted/prohibited types of attachments, types
   1     Administration                                             of email, or embedded code. This functionality may be available to FAA
            Rights                                                   administrative personnel and may be in addition to that normally administered by the
                                                                     service provider (such as spam filtering).
          Government      Administrator broadcast                    The solution must provide Government Administrators with the ability to send
            System        notifications                              outbound emails to all email accounts for emergency notifications.
   2
         Administration
                                                            
            Rights
          Government      Bandwidth regulation                       The solution must provide the ability for Government Administrators to control
            System                                                   bandwidth intensive activity.
   3
         Administration
                                                            
            Rights
          Government      Blocking IP addresses                      The solution must provide Government Administrators with the ability to block IP
            System                                                   addresses as directed or required by agency policy via self-service administration or
   4
         Administration
                                                                    submission of support ticket to the service provider.
            Rights
          Government      Distribution list management               The solution must allow Government Administrators to create distribution lists and
            System                                                   designate an end-user(s) as a distribution list owner.
   5
         Administration
                                                            
            Rights
          Government      Dormant account access                     The solution must provide Government Administrators with the ability to provide
            System                                                   access to a dormant user account to another active user account.
   6
         Administration
                                                            
            Rights
          Government      Group mailbox administration               The solution must allow Government Administrators to create group mailboxes and
            System                                                   designate an end-user(s) as the group mailbox owner.
   7
         Administration
                                                            
            Rights
          Government      IM enable/disable                          The solution must allow Government Administrators the ability to enable or disable a
            System                                                   user’s instant messaging service.
   8
         Administration
                                                            
            Rights




                                                                Page 1 of 12
                                                                                                                               PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category             Requirement Title               Mandatory                                       Description
  ID
          Government      Optional password access                         The solution must allow Government Administrators to permit end-user access
            System                                                         through the use of username and password, if an administrator determines that the
   9
         Administration
                                                                          end-user cannot utilize the agency’s multi-factor identification.
            Rights
          Government      Remote administration                            The solution must allow Government Administrators to perform selected
            System        capabilities                                     administrative functions (e.g., provisioning/deprovisioning of users, account creation,
  10     Administration                                                   alias and mailing list creation/management, mailbox and email size constraints, end-
            Rights                                                         user featurem anagement, etc.) through a web browser interface.

          Government      Remote authentication                            The solution must support a secure, dual factor method of remote authentication and
            System                                                         authorization to identified Government Administrators that will allow Government
  11
         Administration
                                                                          designated personnel the ability to perform management duties on the system.
            Rights
  12     Mobile Access    BlackBerry account expansion                    The solution must be capable of expanding to additional BlackBerry accounts.
         Mobile Access    BlackBerry interface                             The solution must have a FIPS 140-2 compliant synchronization interface to the FAA
                                                                           BlackBerry Enterprise Server (BES) and other smartphone devices to support the
                                                                           synchronization of emails, calendars, contacts, journals, folders, memos, etc.
  13                                                              


         Mobile Access    Device compatibility - Active-Sync               The solution must support email, Instant Messaging, Contact Sync, and Calendar
  14                                                                      Sync with Active-Sync devices (i.e. Android powered devices, iPhone, Microsoft's
                                                                           Windows Mobile).
         Mobile Access    Device compatibility - BlackBerry                The solution must support email, Instant Messaging, Contact Sync, and Calendar
  15                                                                      Sync with BlackBerry devices using a solution-provided implementation of BES
                                                                           Services.
        System Feature Access delegation                                   The solution must provide individuals with a capability to delegate the access and/or
                                                                           control of objects (such as mailboxes, calendars, schedules, contacts, tasks, etc.) to
  16                                                                      other users (i.e. office administrators). The solution may allow users designated as
                                                                           group mailbox owners the ability to control who has access to the group mailbox
                                                                           (i.e., ACL control).
        System Feature API archive access                                  The solution must provide API access to content allowing integration with third party
  17                                                                      tools such as email archiving, e-discovery, and electronic records management.
                                                                           APIs must conform with voluntary consensus standards.




                                                                      Page 2 of 12
                                                                                                                       PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category           Requirement Title        Mandatory                                       Description
  ID
        System Feature API integration                             The solution must support Application Program Interface (API) integration for email,
  18                                                              calendars, and contact management.
        System Feature Assured deletion                            The solution must permanently remove all copies of messaging content (e.g. an
                                                                   email, its metadata and its attachments) from all internal accounts and from the
  19                                                              service provider's systems when its retention period expires, or when the litigation
                                                                   hold is released; whichever is later; or as requested by authorized Government staff.

  20    System Feature Attachment size                            The solution must be able to regulate the attachment size.
        System Feature Authentication                              The solution must support dual factor authentication including support for PKI
  21                                                              certificates from FAA's Personal Identity Verification (PIV) access card.
        System Feature Browser compatibility                       The solution must be accessible via web browsers on both PCs and mobile devices.
                                                                   Supported browsers must include the following:
                                                                   - Internet Explorer 7+
                                                                   - Mozilla Firefox 3+
  22                                                              - Apple Safari 3++
                                                                   - BlackBerry Browser
                                                                   - Google Chrome

        System Feature Calendar                                    The solution must provide integrated calendar functionality. This capability must
                                                                   synchronize with mobile accounts.
                                                                   - Create, edit, and delete personal appointments and meeting requests.
  23                                                              - Send calendar requests to other end-users.
                                                                   - Create and edit shared calendars for use in resource schedule (i.e. conference
                                                                   rooms).
                                                                   - Designate owners and schedulers of shared calendars.
        System Feature Calendar user delegations                   The solution may support time constrained calendar delegation capabilities. For
  24                                                               instance, an end-user could appoint a personal assistant delegation privileges for a
                                                                   specific period of time.
        System Feature Calendar applications                       The solution must support the calendaring function and must support full bidirectional
  25                                                              synchronization with external calendaring applications, including the ability to view
                                                                   resource availability from the external calendar.
        System Feature Calendar collaboration                      The solution must provide calendaring collaboration features. Describe any calendar
  26                                                              features that your solution offers in the collaborative offering (such as viewing or
                                                                   sharing calendars with internal and external users).




                                                                Page 3 of 12
                                                                                                                              PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category            Requirement Title              Mandatory                                       Description
  ID
        System Feature Calendar events migration                         All existing calendar events must be migrated to new solution, including future
  27                                                                    scheduled events.
        System Feature Calendar sharing and access                       The solution must support calendaring which allows for sharing and blocking access
  28                                                                    to calendar entries by users - different from delegation of calendar.
        System Feature Capacity and scalability                          The solution must be able to support 60,000 or more user accounts and provide
                                                                         improvements to current system performance levels (approximately 1,000,000
  29                                                                    emails and 22,000 instant messages daily (with over 7,500 concurrent instant
                                                                         messages).
        System Feature Characters & language support                     The solution must support UNICODE characters as well as additional languages.
  30                                                            
        System Feature Collaboration                                     The solution may provide the capability for users to share and collaborate on
  31
                                                                         documents with internal users and authenticated external customers.
        System Feature Collaboration activity monitoring                 The solution may provide an ability to monitor collaboration activity. Describe any
                                                                         monitoring capability (such as RDF, RSS, ATOM, email, trackback, commenting)
  32
                                                                         that your solution offers in the collaborative applications (such as blog, wiki, or data
                                                                         collaboration).
        System Feature Collaboration files version control               The solution may provide features for version control of collaboration files. Describe
  33                                                                     the solution’s ability to maintain version control (what has changed, who has
                                                                         changed it, and when it was changed.)
        System Feature Collaboration tools                               The solution may provide interfaces to collaboration tools and unified messaging.
                                                                         Describe any capability the solution provides for a single interface to all the
  34
                                                                         collaboration tools such as email, SMS [Short Message Service], facsimiles, instant
                                                                         messaging, etc.
        System Feature Contact management                                The solution may provide the ability for users to add/delete/update Contact records
                                                                         and Contact information contained within those records. This capability must
  35                                                                     synchronize with mobile accounts.
                                                                         - Group or tag a collection of contacts
                                                                         - Send emails to a collection of contacts
        System Feature Contact sharing                                   The solution may allow the end-user to designate Contacts as shared with other end-
  36
                                                                         users.
        System Feature Contingency planning                              The solution must provide for backup, recovery, and refresh operations on a periodic
                                                                         basis, supporting FAA Disaster Recovery (DR) and Continuity of Operations (COOP)
  37                                                                    requirements. The solution must meet the Recovery Point Objective (RPO) and their
                                                                         Recovery Time Objective (RTO).




                                                                    Page 4 of 12
                                                                                                                            PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category            Requirement Title            Mandatory                                       Description
  ID
        System Feature Data at rest locations                          The solution must ensure that all data at rest is in location(s) subject to U.S.
  38                                                                  jurisdiction.
        System Feature Data protection / separation                    The solution must separate FAA data from other customers’ data and prevent
  39                                                                  access to FAA data.
        System Feature eDiscovery - API integration of                 The solution must support an open Application Program Interface (API) that
                       third party tools                               conforms to voluntary consensus standards allowing interoperability with third party
  40                                                                  such as email archiving solutions, e-discovery solutions, and electronic records
                                                                       management software applications.
        System Feature eDiscovery - Archive querying                   The solution must enable end-users to search and view via their mailbox, via a
                       capability                                      browser-based interface or by mobile device, email messages and attachments
                                                                       placed under archive control. End-users must at a minimum have the following query
                                                                       capabilities:
  41                                                                    - Keyword search across all content fields
                                                                         - Date/Time search
                                                                         - Sender, Recipient by email address
                                                                         - Boolean
        System Feature eDiscovery - Archiving capability               The solution must allow designated agents to have access to e-discovery message
                                                                       archive functionalities used for retention; suspending and resuming disposition;
  42                                                                  manual classification, categorization, and/or tagging; rendering and viewing; legal
                                                                       hold and FOIA collection, management, and exporting; and reports and metrics.

        System Feature eDiscovery - audit and                          The proposed solution must include an e-discovery service inclusive of audit
  43
                       governance capability
                                                                      transparency and other similar governance requirements.
        System Feature eDiscovery - Exporting formats                  The solution must include an e-discovery service that will allow for the export of an
                                                                       agent-defined set of messaging content (e.g. an email, its metadata and its
                                                                       attachments), on demand and in native file format. The e-discovery service must
  44                                                                  include the following standard formats: Bates Stamped PDF, mbox and PST/NSF.
                                                                       Other formats may include Concordance load file with accompanying native files,
                                                                       EDRM-XML.
        System Feature eDiscovery - Flagging capability                The solution must support the flagging by an agent of content for the following
  45                                                                  purposes: assigning retention policies and identifying email messages and
                                                                       attachments for legal hold matters.




                                                                  Page 5 of 12
                                                                                                                             PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category            Requirement Title            Mandatory                                       Description
  ID
        System Feature eDiscovery - Litigation hold                    The solution must include the ability to apply a litigation hold or other similar hold
                       capability                                      capability for all message content and attachments without affecting the ability of the
                                                                       individual user to manage their email. The litigation hold effectively creates an
                                                                       immutable copy, retaining records in their authentic state regardless of disposition
  46                                                                  state, for the purposes of legal proceedings, FOIA, and other compliance matters.
                                                                       The solution must allow for multiple litigation holds to be applied to messaging
                                                                       content, and be able to remove a litigation hold without affecting other litigation holds
                                                                       or the underlying retention period of the messaging content.

        System Feature eDiscovery - Mailbox attributes                 The solution must capture the following mailbox attributes and place them under
  47                                                                  archive control: foldering, email categorization/classification, and calendaring.

        System Feature eDiscovery - Metadata                           All metadata and foldering information associated with messaging content including
  48                   preservation                                   messages, attachments, and calendar entries must be preserved in accordance with
                                                                       Department of Justice guidelines.
        System Feature eDiscovery - Records retention                  The solution must support the assignment of a content or role-based retention policy
                       capability                                      at ingestion of email messages and attachments or retroactively, according to FAA's
                                                                       retention policy. Support for assignment or modification of retention policy may be
  49                                                                  from an external application. All content may be preserved in immutable storage in a
                                                                       non-proprietary format for the designated retention period.

        System Feature eDiscovery - Searching capability               The solution must include an e-discovery service that will allow authorized agents to
                                                                       query on demand the entire message repository for messaging content (e.g. an e-
                                                                       mail, its metadata and its attachments), and provide audit logs of end-user query and
                                                                       access. At a minimum, the following search methods must be supported: Full text,
  50                                                                  keyword, parametric, Boolean, proximity, content based, and context based search.
                                                                       The solution must allow agent searches to be saved for reuse and for search results
                                                                       to be organized and filtered.

        System Feature Email additional integrated                     Describe any additional integrated services provided by the solution.
  51
                       services
        System Feature Email attachments                               The solution must support opening of attachments from within email using the
  52                                                                  appropriate application for the document type.




                                                                  Page 6 of 12
                                                                                                                            PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category             Requirement Title           Mandatory                                       Description
  ID
        System Feature Email creation and sending                      The solution must be capable of creating, saving as draft, and sending messages
  53                                                                  including multiple attachments to recipients designated as “TO”, “CC”, and “BCC”.

        System Feature Email distribution list                         The solution must allow the end-user(s) designated as the distribution list owner to
  54
                       administration
                                                                      manage the email addresses in the distribution list.
        System Feature Email forwarding                                The solution must provide end-users with the ability to specify an email address to
  55                                                                  forward all incoming mail.
        System Feature Email importance level for                      The solution must provide an indication to the recipient as to the sender's transmitted
  56
                       recipient
                                                                      importance level (high, normal, low) of a message.
        System Feature Email importance level for sender               The solution must allow sender to indicate the importance level (high, normal or low)
  57                                                                  of a message before sending the email.
        System Feature Email mailbox full notifications                The solution may have the capability to notify users when their mailbox has
  58
                                                                       exceeded the storage limit and provide instructions for resolution.
        System Feature Email mailbox getting full                      The solution must notify end-users when mailbox reaches 90% of storage quota.
  59
                       notifications
                                                              
        System Feature Email mailing lists                             The solution must provide the ability to establish and maintain mailing lists of internal
  60                                                                  and external email addresses.
        System Feature Email message security                          The email solution must provide best-practice features for message security, such as
  61                                                                  spam filtering, anti-virus/anti-malware protection, Anti-phishing, screening outbound
                                                                       messages, etc.)
        System Feature Email Out of office                             The solution must allow users to create Out of Office notifications/replies. The
                                                                       solution must allow the end-user to enable the system to automatically respond to
  62                                                                  email senders with an “out of office message” both for indefinite periods and for time-
                                                                       boxed designations.
        System Feature Email pop-up editing capability                 The solution may provide the end-user with the option to create and edit email in a
  63
                                                                       pop-up window.
        System Feature Email receiving / read and unread               The solution must be capable of receiving messages and delineating between read
  64                                                                  and unread messages in an inbox.
        System Feature Email requesting read receipt                   The solution may support an end-user’s ability to request a read receipt upon
  65
                                                                       sending an email message.




                                                                  Page 7 of 12
                                                                                                                               PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category             Requirement Title              Mandatory                                       Description
  ID
        System Feature Email security classification                      The solution must support the end-user's ability to indicate email classification
                       markings capability                                markings in accordance with all applicable federal regulations and with FAA Order
                                                                          1600.75, Protecting Sensitive Unclassified Information, including Controlled
                                                                          Unclassified Information (CUI) as identified by NARA CUI office and Sensitive
  66                                                                     Unclassified Information (SUI), including Sensitive Security Information (SSI) and For
                                                                          Official Use Only (FOUO) as identified in FAA Order 1600.75, and classified email
                                                                          messages as legally privileged as identified by the Federal Rules of Evidence (FRE).

        System Feature Email sending read receipt                         The solution may support the transmitting of a read receipt to the sender upon an
  67
                                                                          end-user’s reading of an email message.
        System Feature Email sending to one or more                       The solution must be capable of replying to a sender, replying to all recipients and
  68
                       recipients
                                                                         forwarding messages to new recipients with and without attachments.
        System Feature Email shared mailboxes                             The solution must provide shared /group mailboxes.
  69                                                             

        System Feature Email spam/junk retention                          The solution must retain messages identified as “SPAM” or “Junk Mail” for a period
                                                                          of at least 14 days, for an end-user to review, and optionally identify as not junk mail
  70                                                                     to affect filters for future transmission by at least sender email address, and sender
                                                                          domain name.
        System Feature Email spell check                                  The solution must allow end-users to perform a spell check before sending the email.
  71                                                             
        System Feature Email system scalability                           The solution must be scalable to allow for the creation of additional, new user
  72                                                                     accounts and the removal of unused user accounts.
        System Feature Email threat filtering for spam                    The solution must support third party message threat filtering which includes but is
  73                                                                     not limited to inbound and outbound Spam, Anti-phishing, and Virus.
        System Feature Email threat filtering for stripping               The solution must define to Government Administrators and implement filtering, in
  74                                                                     order to strip unwanted/prohibited types of attachments, types of email, or embedded
                                                                          code in addition to that normally administered by the solution.
        System Feature Email user delegations                             The solution must support end-user controlled email delegation capabilities
  75                                                                     (supervisor/personal assistant).
        System Feature Email user delegations, time                       The solution may support time constrained email delegation capabilities. For
  76                   constrained                                        instance, an end-user could appoint a personal assistant delegation privileges for a
                                                                          specific period of time.




                                                                     Page 8 of 12
                                                                                                                       PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category           Requirement Title         Mandatory                                      Description
  ID
        System Feature Encryption - FIPS 140                       The solution must provide the capability for all traffic, including web access, to be
                                                                   over a Secure Sockets Layer (SSL)/Transport Layer Security (TLS) session in
  77                                                              compliance with FIPS 140 (current version), as amended, encryption. The solution
                                                                   must upgrade to any new Federal data encryption standard that replaces FIPS 140-2
                                                                   within six months of final version.
        System Feature Encryption - FIPS 197                       Data at rest must be encrypted using an appropriate algorithm in accordance with
  78                                                              FIPS 197.
        System Feature Extended UC offerings                       The solution may include extended offerings related to unified communications (If
                                                                   so, describe what capabilities are offered that might work in conjunction with or
  79                                                               replace services such as Cisco MeetingPlace 7.0, Cisco Unified Presence Server
                                                                   7.0.6, Cisco IP Communicator 7.0.3, Cisco Unified Personal Communicator 7.0.2,
                                                                   and Cisco Unified Communications Manager 7.1.3).
        System Feature Federal electronic records                  The solution must support an immutable email management solution integrated with
                       management compliance                       the messaging system in accordance with the requirement for Federal agencies to
                                                                   manage their email messages and attachments as electronic records in accordance
                                                                   with 36 CFR § 1236.22 (ref. a), including capabilities such as those identified in: DoD
  80                                                              STD-5015.2 V3 (ref. b), Electronic Records Management Software Applications
                                                                   Design Criteria Standard, NARA Bulletin 2008-05, July 31, 2008, Guidance
                                                                   concerning the use of email archiving applications to store email (ref. c), and NARA
                                                                   Bulletin 2010-05 September 08, 2010, Guidance on Managing Records in Cloud
                                                                   Computing Environments.
        System Feature Global address list searching               The solution must allow users to find other FAA accounts, contact information, and
  81                                                              shared mailing lists within the enterprise.
        System Feature IETF 4510 / 5321 / 5322                     The solution must be compatible with IETF 4510, 5321, and 5322.
                       compliance
  82                                                       

        System Feature Instant messaging                           The solution must provide:
                                                                   - secure instant messaging communications
                                                                   - an online-presence indicator, and/or status message capability
  83                                                              - the ability to send, accept, and reject file attachments

                                                                   These capabilities may be available from PCs, BlackBerrys, and other mobile
                                                                   devices.




                                                                Page 9 of 12
                                                                                                                        PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category            Requirement Title       Mandatory                                        Description
  ID
        System Feature Keyword search and                          The solution must support the automated discovery of keywords or phrases and the
  84
                       confidentiality rules
                                                                  flagging of content for protection of its confidentiality and integrity.
        System Feature LDAP integration                            The solution must be compliant with the FAA's TRM. The solution must integrate
                                                                   with FAA’s multiple LDAP-based directory services to securely authenticate and
  85                                                              authorize users. The solution must be compliant with IETF 4510 (LDAP). Future
                                                                   features will need to be compliant with the FAA's TRM.
        System Feature Management of accounts                      The solution must provide the capability to integrate with multiple Active Directories
  86                                                              and LDAP servers.
        System Feature Migration at termination                    The solution must be capable of exporting data (current, archive, and litigation hold)
                                                                   into a recognized open data format upon termination of service. The solution must
  87                                                              allow for the testing of this feature for a limited percentage of accounts on a periodic
                                                                   basis.
        System Feature Migration of archived data                  The solution must support the ingestion of messaging content including email
                                                                   messages, attachments, calendar entries and address books from both backup
  88                                                              tapes and from personal archive files (Lotus Notes .nsf) from existing systems.

        System Feature Migration of existing data                  The solution must provide for the importing of existing email accounts from the
                                                                   existing system (user id creation and transfer of calendar and contact information).
  89                                                              The solution must also include the transfer of current litigation hold archives (now in
                                                                   CommonStore) and be capable of transferring current and other archived email data
                                                                   to the target system.
        System Feature Multiple domain addresses                   The solution must provide for management of multiple email domains (i.e.
  90                                                              abc.dept.gov, xyz.dept.gov, 123.gov, abc.us, 123.mil, xyz.org, etc…) from a single
                                                                   administration and global directory perspective.
        System Feature Network access                              The solution must be accessible via multiple ISPs to prevent performance
  91                                                              degradation or outage if one or more ISPs’ service is unavailable.
        System Feature Offline access                              The solution may provide end-users with a local client application allowing offline
                                                                   access to cached email. If a separate local client application is provided by the
                                                                   solution, the local client must only perform all or a subset of all of the solution’s
  92
                                                                   functionality available through the web interface. The local client application will not
                                                                   be necessary to perform any function offered by the solution.

        System Feature Offline capability                          The solution must support offline capabilities through connection aware web
  93                                                              interfaces and/or non-web based clients.




                                                               Page 10 of 12
                                                                                                                       PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category            Requirement Title         Mandatory                                      Description
  ID
        System Feature Recovery Point Objective                     The solution must provide for a Recovery Point Objective (RPO) of < 15 minutes per
  94                                                               event.
        System Feature Recovery Time Objective                      The solution must provide for a Recovery Time Objective (RTO) of < one (1) hour
  95                                                               per event.
        System Feature Resource scheduling                          The solution must provide the capability for users to schedule resources (such as
  96                                                               conference rooms, phone and web conference slots, communications equipment,
                                                                    etc.)
        System Feature Resource utilization reporting               The solution must provide automatic monitoring of resource utilization and other
  97                                                               events such as failure of service, degraded service, etc. and report via service
                                                                    dashboard or other electronic means.
        System Feature S/MIME v3                                    The solution must support S/MIME v3 and later functions (encryption and digital
  98                                                               signature) for both messages and calendar invites/replies.
  99    System Feature Sender Policy Framework                     The solution must support Sender Policy Framework (SPF).
        System Feature Service failure / degradataion               The solution must provide automatic alerting to pre-determined Government staff in
  100
                       automated alerts
                                                                   the event of service failure or degraded service.
        System Feature Service provisioning times                   The solution must provide for service provisioning and de-provisioning times (scale
  101                                                              up and down) in near real-time.
        System Feature Shared document repositories                 If document collaboration capability is provided, the solution must show awareness
  102
                                                                    of the presence of other users.
        System Feature Synchronization tools                        The solution must provide configurable synchronization tools for integration with a
                                                                    Government LDAP source (IETF RFC 4510 compatible) for provisioning (including
                                                                    user account provisioning), de-provisioning (including de-provisioning of user
  103                                                              accounts), account disablement and enablement. Synchronization communication
                                                                    must be conducted over Secure Sockets Layer (SSL)/Transport Layer Security (TLS)
                                                                    session supporting FIPS 140-2 encryption.

        System Feature System availability                          The solution must provide a high availability of 99.9% of the time, excluding pre-
                                                                    scheduled maintenance. The solution must document and provide their pre-
  104                                                              scheduled maintenance policies and windows of operation as part of this solicitation.

        System Feature User locations                               The solution must support users from various geographic locations both nationally
  105                                                              and internationally.
        System Feature User password resets                         The solution must provide end-users with the ability to reset their own passwords.
  106                                                      



                                                               Page 11 of 12
                                                                                                                    PRESOLICITATION FINAL


             FAA Enterprise Messaging System (EMS) Requirements, Features, and Functions Matrix
This matrix describes the requirements, features, and functions of the modernized FAA's Enterprise Messaging System (EMS). The intent
is to identify for prospective Offerors, the EMS requirements, features, and functions that serve as solution constraints and to allow the
submission of a detailed Performance Work Statement (PWS).
 Req      Category            Requirement Title       Mandatory                                      Description
  ID
        System Feature VoIP                                        The solution must interoperate with FAA’s existing Voice over Internet Protocol
  107                                                             (VoIP) service (FAVES and AVAYA) and provide fully unified messaging of voice
                                                                   and email messages within the email environment.




                                                               Page 12 of 12

				
DOCUMENT INFO
Shared By:
Categories:
Tags:
Stats:
views:15
posted:8/4/2011
language:English
pages:12