HC1028-16-T-0183.docx

HC1028-16-T-0183

Section SF 1449 - CONTINUATION SHEET

Software

FFP

Cairs Fault and Performance Enterprise Server License

Part #: CNET-RS FOB: Destination

PURCHASE REQUEST NUMBER: DEEMZ60043

NET AMT

Software

Cairs Fault and Performance Entity License (1-1,000 Ports)

Part #: CNET-TS-1

NET AMT

Software

Cairs Fault and Performance Entity License (3,001-4,000 Ports)

Part#: CNET-TS-6

NET AMT

Software

Cairs Fault and Performance Entity License (4,001-6,000 Ports)

Part #: CNET-TS-7

NET AMT

Software

Cairs Fault and Performance Entity License (8,001-10,000 Ports)

Part #: CNET-TS-9

NET AMT

Software

Cairs Fault and Performance Entity License (10,001-15,000 Ports)

Part #: CNET-TS-10

NET AMT

Software

Microsoft Windows 2012 (Lab Server)

Part #: WIN2012

NET AMT

Profesional Services

Labor, Training, Post Cust Support, Lab Installation and Support

NET AMT

Travel

Travel to support the Performance Work Statement (PWS). The contractor is authorized to invoice in accordance with the Federal Travel Regulations FAR 31.205-46.

NET AMT

PWS

PEO C4I PMW 790 Shore Telephony Regional Telephony Management System (RTMS) NSA Norfolk, Norfolk VA Performance Work Statement (PWS) As of 16 Jun 2016

Contract Number:

1. Technical Representative: Jon.kershaw@navy.mil

1. Primary Technical Representative: LaManual.mckinney@navy.mil

Department of Defense Activity Address Code (DODAAC):

N00039

San Diego, CA 92110

Fax Number:

1. Alternate Technical Representative.

San Diego, CA 92110

1. Contract Title: Program Management Warfare (PMW) 790 Shore Telephony; Implementation of a Configuration Accounting Information Retrieval System (CAIRS.NET) Regional Telephony Management System (RTMS) at NSA Norfolk, Building M51.

1. Background: The PMW 790 Shore Telephony project has a requirement to remotely manage Private Branch Exchange (PBX) site data to include Call Detail Records (CDR), alarms, inventory, master 411 directories, 911/E911 interface, web based work order control, and technical assistance. An initial RTMS solution was deployed in the Norfolk and San Diego region to perform these functions. Shore Telephony is seeking award of this contract action to procure the software, installation, and training services required to upgrade the existing Norfolk RTMS configuration to perform Fault, Configuration, Accounting, Performance and Security (FCAPS) management as defined in the ISO-TMN specification for telecommunications systems management.

In addition, Shore Telephony is seeking a Sole Source Award of this contract to procure the software, installation, and training services required for the Shore Telephony In-Service Engineering Activity Lab to support this request.

Rationale;

1. Unique Communications is the Sole Source software developer and provider for CAIRS.NET.

1. There are no other companies that provide the CAIRS system. It is only available through Unique Communications, and is trademarked by Unique Communications. The Software Upgrade Kits are specific to the Software Unique supports.

Department of Defense (DoD) Unified Capabilities Requirements (UCR2013, Errata 1) requires that all systems connecting to a DoD network shall be on the current Unified Capabilities Certification Office (UCCO) Approved Products List (APL).

Department of Defense Instruction Information Assurance Accreditation requires that modernized switch, software, and ancillary equipment shall have received Information Assurance (IA) accreditation in accordance with DODI 8100.4, DOD Unified Capabilities and UCR 2013, Errata 1. The Contractor shall provide the appropriate IA APL documentation as a part of the proposal. In addition, the Contractor shall ensure that the system meets the criteria for DoD Information Assurance Certification and Accreditation Process (DIACAP).

1. Objectives: Implement a CAIRS.Net RTMS at NSA Norfolk, Norfolk VA and St. Julien’s Creek Annex, Portsmouth, VA.

1. Scope: RTMS Norfolk Region and Shore Telephony Lab – CAIRS.NET System

Current Telephony Management System (TMS) capabilities are comprised of individual Unique Communications CAIRS software modules, running on Windows 2008 server platforms. Currently supported telephony systems are a combination of Nortel Meridians and Avaya Definity & Communication Manager configuration.

Location and Space: The RTMS central site hosting all system servers is currently located at NSA Norfolk, Building M-51, Norfolk, VA. Central site servers provide TMS services to 7 remote sites where the supported telephony systems reside. Space at the facility will be provided by the government. The site list is provided in paragraph 9 of this document.

Additionally, the Shore Telephony ISEA Lab will be a replica RTMS central site hosting all system servers located at St. Julien’s Creek Annex, Portsmouth, VA in Building 12. Central site servers provide TMS services to remote sites where the supported telephony systems reside. Space at the facility will be provided by the Government. The site list is provided in paragraph 9 of this document.

1. REQUIREMENTS

5. NSA Norfolk, Norfolk VA - Building M-51

0. PMW 790 has a requirement to remotely manage the PBX site data through the usage of the CAIRS.NET Automatic Switch Interface (ASI) and Fault/Performance modules. By adding these modules to the current RTMS, the government will have a complete FCAPS management system as defined in the International Organization for Standardization Telecommunications Management Network (ISO-TMN) specification for telecommunications systems management. The Contractor will provide a turnkey solution to install/upgrade/replace the existing CAIRS suite at NSA Norfolk. The Contractor will utilize the existing Government owned equipment to complete this task. The Contractor shall provide training support to Government Base Communication Office (BCO) employees and local TMS operators.

5. St. Julien’s Creek Annex, Portsmouth, VA - Building 12

1. PMW 790 has a requirement to provide Shore Telephony ISEA support to the deployed RTMS suites throughout the Navy, which entails providing routine Engineering Technical Assistance (ETAS) to include fleet engineering support and maintenance support, and configuration management. The ISEA Lab will utilize RTMS to provide periodic support for Naval Voice shore telephony sites to include Information Assurance Vulnerability (IAV) assistance, management and administration for multiple systems, apply information assurance configurations (i.e. security upgrades and patches), diagnostic, maintenance, and minor programming changes on current software applications. The Contractor will provide a turnkey solution to install a replica RTMS Central and Remote site system. The Contractor will utilize the existing Government owned equipment removed from the Norfolk region central site (Building M-51) to complete this task. The Contractor shall provide training to the Shore Telephony ISEA staff.

5. At a minimum, the RTMS solution must provide the following functionality:

· CAIRS Client: The CAIRS client is the primary interface for CAIRS.NET users and administrators. All visual forms are in this smart client. This smart client is downloaded to authorized workstations and can be setup to automatically update. All users must have user accounts in both CAIRS.NET and Active Directory in order to run the CAIRS client. The CAIRS client also requires Microsoft .NET framework 2.0 & 4.0 to be installed on each client workstation.

· Subscriber Portal: The Subscriber Portal empowers Government subscribers with the ability to manage set features and view or search calls made to and from their telephone set. Through a standard web browser, users can also place work orders and trouble tickets and browse corporate directory information.

· CAIRS Enterprise Data Center (CEDC): CEDC is the heart of the CAIRS.NET system. CEDC is the primary processing system of the application server that uses ASP.NET web services to connect and support all CAIRS clients. CEDC works closely with SMA to provide switch interface communication, works with UCE to process and report call record data, and works with WOPR to generate MAC work orders. CEDC is built on the Microsoft .NET framework 2.0 & 4.0 and runs on an IIS 6.0 web server.

· CAIRS SQL Database: The CAIRS.NET system uses the Microsoft SQL Server 2008 R2 database platform. All data, including activity/security logs, call data, and WOPR scripts, is stored here. Note: user passwords are not stored here; passwords are managed by the network MS Active Directory.

· Universal Collection Engine (UCE): Universal Collection Engine (UCE) is a service that collects call records and traffic and alarm data from your PBX/switch. Call data can be collected in real-time via IP or Serial, or can be processed through a flat file generated by a 3rd party application. UCE formats the call data and adds it to the CAIRS SQL Database. Call record reporting is available in the CAIRS client and Subscriber Portal. Traffic and alarm reporting is available through a web browser powered by the CAIRS Fault & Performance Server.

· CAIRS Enterprise Services (CES): The Enterprise Services (CES) component is a windows service that does background processing for CAIRS.NET activities such as scheduling and summarizing report data for UCE and WOPR data collection and maintenance.

· Configuration Management: Automatic Switch Interface (ASI):

· Ability to perform Adds, Moves, Changes, and Deletes through Cairs.net graphical user interface

· Ability to Generate telephone set templates

· Ability to schedule and perform switch sync to keep the PBX database and Cairs.net database in sync

· Fault Management: The solution must provide a means of securely connecting to remotely located telephone systems within the Navy inventory and collecting fault information published by the telephone systems. Using the network standard Simple Network Management Protocol (SNMP3) protocol the traffic system is constantly listening on the network to pre-configured network elements. When these elements send a trap or notify message that alarm system listens for these specific messages and notifies technicians and others about the element status through a notification and on the dashboard. The RTMS user console should provide an intuitive dashboard that displays the operational state of all telephone systems being managed, as well as generating notifications to the technician based on the types of alarm.

· Ability to categorize the PBX alarms: Minor, Major, Critical

· Ability to notify via SMS, Phone Call, and Email

· Ability to escalate the notification

· Ability to clear the alarm

· Performance Management: The solution must be capable of collecting and reporting on a variety of performance criteria published by the telephone switch. Examples are Trunk Group Summary, Percent out Block, Total Seize, Trunk ATB and Call Summary. Reports should be able to be published in table and graph formats and exportable via PDF.

5. The Contractor shall deliver to the government a list of all Government Furnished Equipment (GFE) software and hardware that can be reused in the Contractor’s proposed solution and pricing of the proposed solution shall be adjusted according to upgrade the Norfolk region RTMS and replicate an RTMS Central Site at the Telephony ISEA Lab.

5. The Contractor shall provide all materials, hardware, and software necessary for the Government’s successful completion of the RTMS installation and integration.

5. Deliverables. The Contractor shall provide commercial operation and maintenance documentation for the new RTMS. All deliverables shall be provided in Microsoft Office and/or editable format where possible.

5. Warranty. At a minimum, the Contractor shall provide a minimum full/unlimited one-year warranty for all Contractor provided hardware/software, and materials. Warranty will not begin until final Government acceptance. The warranty shall include emergency off-site technical assistance as required via a modem connection from the Contractor’s/manufacturer’s facility. The Contractor shall track and resolve the problem(s) in accordance with standard commercial practices.

5. Training Support. The Contractor shall develop training support, provide training materials, and conduct training courses at each site. The Contractor shall provide the instructors, training support materials, and administrative support necessary to accomplish the training. Training support shall not interfere with system operation. The Contractor shall use COTS terminals and owner manuals to the maximum extent possible to accomplish training objectives. Individual training stations shall be provided if needed.

Training shall be conducted at each site listed in paragraph 9. The Contractor-led training support shall detail administration and operation of all TMS modules. Training support shall be provided for those personnel assigned to the administration, management and maintenance of roles being performed at the BCO. This instruction shall include but is not limited to the following subject matter:

· System Familiarization

· Database Administration and Management

· Performance Monitoring

· Reporting Options

· Station Moves, Adds, and Changes

· System Maintenance Procedure Overview

1. Performance Standards.

1. Incentives. In this fixed price contract, the incentives have been embodied in the pricing and the Contractor can either maximize profit through effective performance or have payments reduced because of failure to meet the performance standard.

1. Place of Performance.

NSA Norfolk, VA (Bldg. M51) SPAWAR Atlantic, VA (Bldg. 12)

1. Period of Performance: All work shall be completed within one year from date of award.

1. Delivery Schedule.

6.1 6.2

Final – 30 days after contract award

(allowable if desired)

Jon.kershaw@navy.mil paula.dacus@navy.mil

One Time

*Standard Distribution: 1 copy of the transmittal letter without the deliverable to the Contracting Officer; 1 copy of the transmittal letter with the deliverable to the Primary COR.

1. Government-Furnished Equipment (GFE)/Government-Furnished Information (GFI). The Telephony ISEA shall furnish adequate workspace, tools, equipment, computer network and telephone services.

1. Other Pertinent Information or Special Considerations. Deliverables. The Contractor shall provide commercial operation and maintenance documentation for the new RTMS. All deliverables shall be provided in Microsoft Office and/or editable format where possible.

1. Section 508 Accessibility Standards. The following Section 508 Accessibility Standard(s) (Technical Standards and Functional Performance Criteria) are applicable (if box is checked) to this acquisition.

Technical Standards

|X| 1194.21 - Software Applications and Operating Systems |X| 1194.22 - Web Based Intranet and Internet Information and Applications |X| 1194.23 - Telecommunications Products |X| 1194.24 - Video and Multimedia Products |X| 1194.25 - Self-Contained, Closed Products |X| 1194.26 - Desktop and Portable Computers |X| 1194.41 - Information, Documentation and Support

The Technical Standards above facilitate the assurance that the maximum technical standards are provided to the Offerors. Functional Performance Criteria is the minimally acceptable standards to ensure Section 508 compliance. This block is checked to ensure that the minimally acceptable electronic and information technology (E&IT) products are proposed.

Functional Performance Criteria

|_| 1194.31 - Functional Performance Criteria

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

DELIVERY INFORMATION

14-AUG-2017

4301 PACIFIC HIGHWAY, OT-1

SAN DIEGO CA 92110

JON KERSHAW

858-537-8510

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

14-AUG-2017

N00039

CLAUSES INCORPORATED BY REFERENCE

CLAUSES INCORPORATED BY FULL TEXT

52.204-9000 POINTS OF CONTACT (AUG 2005)

Contracting Officer Name: Tricia L. Singler Organization/Office Symbol: DITCO/PL8321 Phone No.: 618-229-9378 E-Mail Address: tricia.l.singler.civ@mail.mil

Contract Specialist Name: Tricia L. Singler Organization/Office Symbol: DITCO/PL8321 Phone No.: 618-229-9378 E-Mail Address: tricia.l.singler.civ@mail.mil

COR/Mission Partner Point of Contact (Note: To be filled in upon contract award) Name:

Organization/Office Symbol:

Phone No.:

E-Mail Address:

Contractor Point of Contact Contractor Legal Business Name:

DUNS:

CAGE CODE:

Contractor POC:

E-Mail Address:

Phone Number:

Fax Number:

(End of clause)

52.204-9001 CONTRACT/ORDER CLOSEOUT—FIXED-PRICE, TIME-AND-MATERIALS, OR LABOR-HOURS (JAN 2007)

Timely contract closeout is a priority under this contract/order. The Contractor shall submit a final invoice within ninety (90) calendar days after the expiration of this contract/order, unless the Contractor requests and is granted an extension by the Contracting Officer, in writing. In addition, and concurrent with the submission of the final invoice, the Contractor shall notify the Contracting Officer of the amount of excess funds that can be deobligated from this contract/order so the closeout process can begin as soon as possible upon expiration of this contract/order. A bilateral contract/order closeout modification will be forwarded to the Contractor by the Contracting Officer and must be signed by the Contractor and returned to the Contracting Officer within thirty (30) calendar days of issuance of the modification. A Contractor’s failure to respond and/or sign the bilateral closeout modification within thirty (30) calendar days of receipt will constitute approval of the terms of the modification and the modification will subsequently be processed unilaterally by the Contracting Officer to deobligate excess funds and close this contract/order.

If this contract/order contains option periods, the Contractor is required to submit an invoice within ninety (90) calendar days after expiration of the base period of performance and the expiration of each exercised option period of performance to allow for deobligation of excess funds that were obligated in those respective periods of performance.

52.209-9000 ORGANIZATIONAL AND CONSULTANT CONFLICTS OF INTEREST (OCCI) (DEC 2005)

(a) An offeror shall identify in its proposal, quote, bid or any resulting contract, any potential or actual Organizational and Consultant Conflicts of Interest (OCCI) as described in FAR Subpart 9.5. This includes actual or potential conflicts of interests of proposed subcontractors. If an offeror identifies in its proposal, quote, bid or any resulting contract, a potential or actual conflict of interests the offeror shall submit an Organizational and Consultant Conflicts of Interest Mitigation Plan to the contracting officer. The Organizational and Consultant Conflicts of Interest Mitigation Plan shall describe how the offeror addresses potential or actual conflicts of interest and identify how they will avoid, neutralize, or mitigate present or future conflicts of interest.

(b) Offerors must consider whether their involvement and participation raises any OCCI issues, especially in the following areas when:

(1) Providing systems engineering and technical direction.

(2) Preparing specifications or work statements and/or objectives.

(3) Providing evaluation services.

(4) Obtaining access to proprietary information.

(c) If a prime contractor or subcontractor breaches any of the OCCI restrictions, or does not disclose or misrepresents any relevant facts concerning its conflict of interest, the government may take appropriate action, including terminating the contract, in additional to any remedies that may be otherwise permitted by the contract or operation of law.

52.211-9000 REQUIREMENT TO SUBMIT AN ELECTRONIC PRODUCT LIST (OCT 2015)

The contractor shall submit the following in addition to complying with all requirements of DFARS 252.211-7003, Item Identification and Valuation:

(a) Complete the Electronic Product List (EPL) attached to this contract for all products delivered under this contract. If a copy of the EPL has not been provide with the contract document, the EPL should be obtained from the Contracting Officer. A separate EPL shall be submitted each time products are delivered under this contract, including when products are replaced through a warranty or service support agreement.

(b) The EPL shall be delivered electronically for review and approval to the Acceptor identified as the Customer/COR/TM Point of Contact in the clause at 52.204-9000, Points of Contact if method of payment is via the government purchase card, or the WAWF point of contact identified in the clause at DFARS 252.232-7006, Wide Area WorkFlow Payment Instructions for contracts process through WAWF. A copy of the EPL shall also be submitted to the Manpower, Personnel and Security (MPS) Directorate at the following email address: disa.meade.mps.list.mps31-warehouse-branch-cam-l@mail.mil.

(c) The contractor shall submit the EPL to the Acceptor and MPS in advance of or concurrently with delivery of products. The Acceptor will not accept products delivered under this contract until the EPL is approved.

(d) If the EPL is delivered in advance of the products, the Acceptor will notify the contractor via email if the list is approved or disapproved. If the EPL is delivered concurrently with the products, acceptance of the products delivered via WAWF will also serve as approval of the EPL.

52.237-9001 ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (eCMRA) REPORTING (JAN 2015)

The contractor shall ensure ALL contractor labor hours including subcontractor, at all levels/tiers, labor hours required for the performance of services provided under this contract are reported via a secure data collection site.

The contractor and all subcontractors, at all levels/tiers, providing direct labor under this contract shall report complete and accurate data for the labor executed during the period of performance during each Government fiscal year (FY), which runs from October 1 to September 30. The Contractor shall input the data into the appropriate eCMRA reporting tool, which can be accessed via a secure web site at http://www.ecmra.mil/. There are four separate eCMRA tools: Army, Air Force, Navy and All Other Defense Components. The appropriate eCMRA reporting tool to use is determined by the requiring activity being supported (e.g., if DISA awards a contract for an Air Force requiring activity, the contractor shall load the required reporting data in the “Department of Air Force CMRA” tool). While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year. The contractor shall completely fill in all required data fields. The contractor shall enter initial data into the appropriate eCMRA tool to establish the basic contract record no later than 15 working days after receipt of contract award or contract modification incorporating this clause. The contractor shall notify the COR when the basic contract record has been established in the appropriate eCMRA tool.

eCMRA User Manuals and Frequently Asked Questions (FAQs) are available at http://www.ecmra.mil/

Contractors may direct technical questions to the eCMRA help desk at usaf.pentagon.saf-aq.mbx.cmra-help-desk-dod@mail.mil

252.232-7006 WIDE AREA WORKFLOW PAYMENT INSTRUCTIONS (MAY 2013)

(a) Definitions. As used in this clause--

Department of Defense Activity Address Code (DoDAAC) is a six position code that uniquely identifies a unit, activity, or organization.

Document type means the type of payment request or receiving report available for creation in Wide Area WorkFlow (WAWF).

Local processing office (LPO) is the office responsible for payment certification when payment certification is done external to the entitlement system.

(b) Electronic invoicing. The WAWF system is the method to electronically process vendor payment requests and receiving reports, as authorized by DFARS 252.232-7003, Electronic Submission of Payment Requests and Receiving Reports.

(c) WAWF access. To access WAWF, the Contractor shall--

(1) Have a designated electronic business point of contact in the System for Award Management at https://www.acquisition.gov; and

(2) Be registered to use WAWF at https://wawf.eb.mil/ following the step-by-step procedures for self-registration available at this Web site.

(d) WAWF training. The Contractor should follow the training instructions of the WAWF Web-Based Training Course and use the Practice Training Site before submitting payment requests through WAWF. Both can be accessed by selecting the “Web Based Training” link on the WAWF home page at https://wawf.eb.mil/.

(e) WAWF methods of document submission. Document submissions may be via Web entry, Electronic Data Interchange, or File Transfer Protocol.

(f) WAWF payment instructions. The Contractor must use the following information when submitting payment requests and receiving reports in WAWF for this contract/order:

(1) Document type. The Contractor shall use the following document type(s).

Invoice and Receiving Report (Combo)

(2) Inspection/acceptance location. The Contractor shall select the following inspection/acceptance location(s) in WAWF, as specified by the contracting officer.

Destination

(3) Document routing. The Contractor shall use the information in the Routing Data Table below only to fill in applicable fields in WAWF when creating payment requests and receiving reports in the system.

Routing Data Table* Field Name in WAWF Data to be entered in WAWF

(4) Payment request and supporting documentation. The Contractor shall ensure a payment request includes appropriate contract line item and subline item descriptions of the work performed or supplies delivered, unit price/cost per unit, fee (if applicable), and all relevant back-up documentation, as defined in DFARS Appendix F, (e.g. timesheets) in support of each payment request.

(5) WAWF email notifications. The Contractor shall enter the email address identified below in the “Send Additional Email Notifications” field of WAWF once a document is submitted in the system.

Primary Acceptor Name: Jesus Roman Office Code: SSC LANT Email: Jesus.Roman @navyl.mil Phone Number: 757-541-6559

(g) WAWF point of contact. (1) The Contractor may obtain clarification regarding invoicing in WAWF from the following contracting activity's WAWF point of contact.

N/A

(2) For technical WAWF help, contact the WAWF helpdesk at 866-618-5988.

image1.wmf image2.wmf