J.6 Contractor Furnished Property.docx

DOCX document 39 KB Posted

Attached to
Durable Medical Equipment (DME) Medicare Administrative Contractor (MAC) Jurisdiction C
Solicitation number
75FCMC19R0041
Issued by

About this file

This document outlines contractor furnished property requirements for a Durable Medical Equipment Medicare Administrative Contractor solicitation issued by the Centers for Medicare and Medicaid Services. The contractor must provide infrastructure including telephone systems, EDI translation software, personal computers meeting specified requirements to operate the Next Generation Desktop, facsimile capability, web hardware and software, and IVR hardware and software to support claims processing, beneficiary inquiries, and provider customer service for Jurisdiction C which includes Alabama, Arkansas, Colorado, Florida, Georgia, Louisiana, Mississippi, New Mexico, North Carolina, Oklahoma, South Carolina, Tennessee, Texas, Virginia, West Virginia, Puerto Rico, and the U.S. Virgin Islands. The contractor must also provide financial management systems to support trust fund operations. Computer security requirements include using a separate operating system, adhering to federal desktop standards, encrypting hard drives and removable media, locking unattended systems, and following CMS password and remote access policies.

View the file

Other files

File Type Posted
Q&A Solicitation 75FCMC19R0041 Amend 2.xlsx XLSX spreadsheet
Amendment #0002.pdf PDF
JC_Solicitation_75FCMC19R0041 CLEAN amend 2.docx DOCX document
JC_Solicitation_75FCMC19R0041 redline amend 2.docx DOCX document
JC_Solicitation_75FCMC19R0041 redline Amend 1.docx DOCX document
J.23 Government Provided Proposal Assumptions (GPPA)-clean.docx DOCX document
75FCMC19R0041.pdf PDF
J.22 Basis of Estimate-redline.xlsx XLSX spreadsheet
J.23 Government Provided Proposal Assumptions (GPPA)-redline.docx DOCX document
J.22 Basis of Estimate-clean.xlsx XLSX spreadsheet
Q&A Solicitation 75FCMC19R0041.xlsx XLSX spreadsheet
JC_Solicitation_75FCMC19R0041 CLEAN Amend 1.docx DOCX document
J.45 CLIN 0012 Cost Proposal Template - Option Year 2 (MPIP).xlsx XLSX spreadsheet
J.1.B List of Key Acronyms.docx DOCX document
J.37 CLIN 0004 Cost Proposal Template - Option Year 2 (PM, MIP, RAC).xlsx XLSX spreadsheet
J.47 CLIN 0014 Cost Proposal Template - Option Year 4 (MPIP).xlsx XLSX spreadsheet
J.36 CLIN 0003 Cost Proposal Template - Option Year 1 (PM, MIP, RAC).xlsx XLSX spreadsheet
J.1.C Fee-For-Service Shared System Base Functions.docx DOCX document
J.40 CLIN 0007 Cost Proposal Template - Option Year 5 (PM, MIP, RAC).xlsx XLSX spreadsheet
J.4 HHS Contracting Guide for Contract of Government Property.docx DOCX document
J.24 Attestations.docx DOCX document
J.41 CLIN 0008 Cost Proposal Template - Option Year 6 (PM, MIP, RAC).xlsx XLSX spreadsheet
J.2 Deliverable Schedule.docx DOCX document
J.7 DME MAC Award Fee Plan and Self Assessment Template.docx DOCX document
J.35 CLIN 0002 Cost Proposal Template - Base Year (PM, MIP, RAC).xlsx XLSX spreadsheet
J.5 Government Systems Provided For Use.docx DOCX document
Solicitation 75FCMC19R0041.pdf PDF
J.22 Basis of Estimate.xlsx XLSX spreadsheet
J.33 Cost Template Summary Sheet.xlsx XLSX spreadsheet
J.25 Past Performance Questionnaire.docx DOCX document
J.9 Non-Disclosure Statement.docx DOCX document
J.49 CLIN 0016 Cost Proposal Template - Option Year 6 (MPIP).xlsx XLSX spreadsheet
J.28 Voluntary Product Accessibility Template.docx DOCX document
J.23.B Government Provided Proposal Assumptions CSR-Handled Telephone Inquiries Tables.docx DOCX document
J.39 CLIN 0006 Cost Proposal Template - Option Year 4 (PM, MIP, RAC).xlsx XLSX spreadsheet
J.1.D Cash Collections Worksheet For HIGLAS Users.xlsx XLSX spreadsheet
J.34 CLIN 0001 Cost Proposal Template - Implementation.xlsx XLSX spreadsheet
J.3 Small Business Subcontracting Plan Template.docx DOCX document
J.1 Statement of Work (SOW)_Jurisdiction C sent12-4.docx DOCX document
J.11 Personal Conflicts of Interest Financial Disclosure.docx DOCX document
J.10 Contractor-Business-Ethics-COI-and-Compliance-Program-Requirements.docx DOCX document
J.1.A List of Key Definitions.docx DOCX document
J.42 CLIN 0009 Cost Proposal Template - Outgoing Contractor Workload Transition Activities.xlsx XLSX spreadsheet
J.48 CLIN 0015 Cost Proposal Template - Option Year 5 (MPIP).xlsx XLSX spreadsheet
J.43 CLIN 0010 Cost Proposal Template - Base Year (MPIP).xlsx XLSX spreadsheet
J.32 Systems of Records.docx DOCX document
J.8 MAC Security Incident and Reportable Event Reporting and Response.docx DOCX document
J.23 Government Provided Proposal Assumptions (GPPA).docx DOCX document
J.44 CLIN 0011 Cost Proposal Template - Base Year (MPIP).xlsx XLSX spreadsheet
J.38 CLIN 0005 Cost Proposal Template - Option Year 3 (PM, MIP, RAC).xlsx XLSX spreadsheet
Show 40 more

Latest 50 of 51 listed here. See the rest on GovTribe.

On GovTribe

Work with this file

  • Download the original file
  • Contacts named in this file
  • Similar government files
  • Ask GovTribe AI about this file

Text version

Attachment J.6 Contractor Furnished Property

RFP # 75FCMC19R0041

Requirement SOW Number and Name
Contractor Furnished Property
C.2 Infrastructure Requirements
Telephone systems
D.1.2.2 Electronic Data Interchange (EDI) Support Related to General Claims Processing
Commercial Off The Shelf (COTS) Translation software package for Electronic Data Interchange (EDI) transactions
D.6.3 Responses to Complex Beneficiary Inquiries
Personal computers (hardware/software) to operate Next Generation Desktop (NGD):

Disk space: 100 MB available Memory: 1 GBrowser: Internet Explorer 10 (or higher version) NOTE: More than one instance of NGD open at a time is not supported.

Monitor: 21”

1. Pointing device: mouse with scroll

2. Network interface: network interface card compatible with the call center Local Area Networks (LAN), which will ultimately allow workstation access to CMSNET

3. Word processor: Microsoft Word 2010 (or higher version) — required only for generation of correspondence.

4. Viewers: Microsoft Word Viewer and Adobe Acrobat Reader are required

D.5 Provider Customer Service Program
Facsimile capability
D.5 Provider Customer Service Program
Web hardware and software
D.5 Provider Customer Service Program
Interactive voice response (IVR) hardware and software
C.5 Financial Management of Trust Fund Dollars
1.1 Installation Support

Non-CMS-issued computers are not supported by the Centers for Medicare & Medicaid Services (CMS) Information Technology (IT) Service Desk. If your organization’s IT service professional has determined that a particular problem is not related to your hardware or software, and is directly related to CMS application access or functionality, your organization’s IT service professional should contact the CMS IT Service Desk for assistance.

1.2 Additional Hardware Requirements

The CMS Virtual Private Network (VPN) client requires a token to be registered and activated by Leidos, or a CMS Personal Identity Verification (PIV) Card to be issued by the Badging Office, for each contractor to access the VPN. The token authorized for use on the CMS VPN is the Rivest, Shamir, & Adleman (RSA) Model SID800.

1.3 Additional Software Requirements

The CMS AnyConnect VPN client installation attempts to install the various components on the C:\ drive of the target machine.

Any other VPN client software (i.e., SafeNet, Nortel, etc.) must be removed from the target machine before installation of the Cisco VPN client. If a different version of Cisco AnyConnect is installed, it may still be used, but the Contractor assumes responsibility for any conflicts related to the non-CMS version being used.

The following software is required:

It is assumed that the Program Files/Program Files (x86) folder is located on the C: drive.

Microsoft Windows 7 (32-bit or 64-bit), Windows 8/8.1, or Windows 10 must be used.

Microsoft Transmission Control Protocol (TCPP)/ Internet Protocol (IP) must be installed (normally this is installed by default).

Anti-virus software must be present, running, and current. Although Cisco advertises support for a wide array of A/V products, the following five enterprise anti-virus products have been tested and are known to work with the CMS VPN: McAfee, Norton, Trend Micro, CA, and Panda. The most current version should be used, unless otherwise advised to be incompatible with the current CMS National Advocacy Center (NAC) environment.

All current Microsoft service packs, hotfixes, and patches must be installed.

All installed software must be current with security patches.

If the VPN gateway detects that anti-virus software or security patches are either missing or outdated, access to the CMS network will be denied. The user is responsible for obtaining updated software. See Section 2.5 for additional detail.

1.4 Computer Security Requirements

The following security requirements must be met:

A separate operating system partition (dual boot) or a dedicated computer must be used for CMS VPN access. Virtual machines may be used, but are not supported by CMS.

Federally-mandated Federal Desktop Core Configuration (FDCC) settings must be adhered to as specified in CMS’s Minimum Security Configuration Standards for Operating Systems document.

The CMS Wireless Client Access Policy must be adhered to.

The hard drive(s) of the machine used for VPN connection must be encrypted using software that is compliant with Federal Information Processing Standard (FIPS) 140-2 requirements. In addition, the system must encrypt any data transferred to removable media (also via FIPS 140-2 compliant encryption software).

After 30 minutes of inactivity, the VPN connection must be terminated. If the computer is left unattended, the screen must be locked.

CMS retains the right to request that a contractor computer pass verification testing. As part of the verification, CMS will verify that all of the hardware, software, and security requirements have been met.

Prior to logging into the CMS network via the VPN, contractors shall submit a signed copy of the CMS Rules of Behavior document titled “Centers for Medicare and Medicaid Services (CMS) Rules of Behavior (ROB) Security Agreement for Interconnection to CMS Networks.”

The VPN machine cannot be connected to a corporate domain when connected to the CMS VPN.

Laptops must be physically secured (i.e. locked to a desk with a cable lock) at all times unless being transported by the user, in which case it must remain in the user’s possession.

The CMS password policy must be adhered to for all accounts used to access the CMS VPN. Federal Information Security Management Act of 2002 (FISMA)/ United States Government Configuration Baseline (USGCB)/ Defense Information Systems Agency (DISA) Security Technical Implementation Guide (STIG) requirements must be met for the local administrator account.

Two-factor token-based user authentication plus Active Directory authentication must be used.

A Secure Sockets Layer (SSL) tunnel will be used for data confidentiality.

Split tunneling will be disabled when connected to the CMS VPN if connecting from any network other than the CMS Central Office network.

All non-VPN traffic will be blocked by the VPN client when connected. This may cause some processes to run slowly or not at all.

The contractor shall monitor and adhere to all Information Technology (IT) policies, standards, procedures, directives, templates, and guidelines that govern the CMS Information Security Program. CMS IT Security Policy documents (such as the Acceptable Risk Safeguards (ARS), Policy for the Information Security Program (PISP), and Minimum Security Configurations, Wireless Access Policy) can be accessed at Information Security (http://www.cms.gov/informationsecurity).

1.5 Validation of Secure Computer

The Cisco Identity Service Engine (ISE) provides the ability to check security requirements on client computers and laptops. The AnyConnect ISE Posture Module will be installed on the computer during the client installation to facilitate communication with the ISE on the CMS VPN network. The ISE automatically updates itself daily to ensure client machines are checked against the most recent hot fixes and virus signature files. The ISE evaluates all requirements to determine whether access should be granted.

1.6 Pre-installation Requirements

Prior to installing this product and attempting to use it, please ensure that the following conditions are met:

Your machine is running the Microsoft Windows 7, Windows 8/8.1, or Windows 10 operating systems.

A separate operating system partition (dual boot) or a dedicated computer is being used for VPN access. Note: Machines imaged with a corporate image have proven problematic in the past, especially if a security suite (Trend Micro, Symantec, etc.) has been installed. If you are having trouble installing the Cisco AnyConnect VPN client on a corporate-imaged machine, please revert to a machine or boot partition running a “vanilla” copy of the OS.

All firewalls, including the Microsoft firewall, have been disabled. You can and should re-enable them after the installation is complete.

The VPN machine is not connected to a corporate network/domain.

No other VPN clients are installed on your computer.

You have verified that your Internet connection is functioning properly, and that Transmission Control Protocol (TCP) and User Datagram Protocol (UDP) port 443 is permitted.

You have successfully completed the CMS VPN request process and you are approved to use CMS VPN services. See Section 1.1 of this document for full details regarding obtaining access to the CMS VPN.

You have an authorized RSA Token activated by Leidos, or a CMS-issued PIV Card.

You have administrator access to your local machine’s operating system (i.e. Windows 7, Windows 8/8.1, or Windows 10).

You have the latest Operating System (Windows 7, Windows 8/8.1, or Windows 10) security updates/patches.

Your anti-virus software and signature files are up to date (within 3 days of connection time).

Note:

Currently, the Cisco AnyConnect VPN Client for Windows 7 and Windows 8/8.1 have been fully tested for use on the CMS VPN. The Cisco AnyConnect VPN Client for Windows 10 OS is known to also function on the CMS VPN, but has not been fully vetted.

Certain security requirements will be validated and enforced by Cisco’s AnyConnect Identity Service Engine (ISE) Posture module (System Scan). If the machine does not meet the security requirements, it will be denied access until all requirements are met.

1.7 Computer System Requirements

The CMS AnyConnect VPN Client minimum system hardware requirements are as follows:

Intel Pentium-class processor or greater (or Advanced Micro Devices' (AMD) equivalent)

512 MB RAM

100 MB of available hard disk space Ethernet card and/or high speed connection (i.e., T1, Digital Subscriber Line (DSL), Cable Modem) to the Internet Microsoft Internet Explorer 7.x or later Super Video Graphics Array (VGA) (800 × 600) or higher-resolution video adapter CD-ROM or DVD drive RSA SID800 Token OR CMS-issued PIV Card

January 10, 2019 Page 5 of 5

File details come from the government source that posted it. Updated .