Attachment_J.1-Support_Contract_SOW_01172017_(003).docx

FMSG TECHNICAL SUPPORT CONTRACT

STATEMENT OF WORK

VERSION 31; 01-17-2017

Table of Contents

INTRODUCTION

The Office of Financial Management (OFM) has overall responsibility for the fiscal integrity of CMS’s programs. As a group within OFM, the FMSG mission is to provide a first class suite of information technology systems that serve CMS financial management purposes.

FMSG faces challenges to design, develop, implement and operate various financial and accounting systems, including, but not limited to, the Healthcare Integrated General Ledger Accounting System (HIGLAS), Electronic Submission of Medical Documentation system (esMD), Security Management, and other new (and as yet unknown) FMSG initiatives.

BACKGROUND

HIGLAS is an integrated, dual-entry accounting system that replaced the Medicare Contractor’s accounting systems with a single standardized system. All Medicare Contractors use the same system, i.e. there is no customization of HIGLAS that makes it different from one Medicare Contractor to the next.

HIGLAS communicates with the Medicare Contractor’s shared systems to process claim billing information, provider profile information, beneficiary profile information, check reconciliation information, payment information, and other claim-related information. These Medicare Contractor shared systems interfacing with HIGLAS are the Federal Intermediary Shared System (FISS) and the Multi-Carrier System (MCS). HIGLAS calculates payments, produces numerous reports and generates demand letters for the use of CMS and the Medicare Contractors.

Currently, the FISS and MCS shared systems process claims and interact with HIGLAS for financial processing. The FISS and MCS shared systems continue to issue checks and Electronic Funds Transfers (EFTs) based on the payment information returned from HIGLAS. In the future it is anticipated that a third shared system, ViPS Maintenance System (VMS), will interface with the HIGLAS. A technical support contractor (TSC) for that system will be needed at that time.

Electronic Submission of Medical Documentation (esMD) enables providers to submit electronically the medical documentation records indicated in the Medicare Review Contractors request. The esMD system was moved from the CMS Baltimore Data Center (BDC) to the Hewlett Packard Enterprise Service (HPES) VDC as of March 2016. Standards, enhancements, and change requests are being designed and developed to enhance existing functionality.

PURPOSE

The purpose of this FMSG Support Contractor (SC) Statement of Work (SOW) is to obtain assistance in administration and management of functions encompassing: business process reengineering, requirements formulation, software development, implementation, testing, research, analysis, and post-implementation support, to achieve accounting functionality and general project management activities. The administrative and management tasks will follow system support activities to ensure compliance with the various stages of the system life cycle.

The TSC will provide Security Management support to ensure that OFM systems are in accordance with applicable industry best practices and comply with Federal regulations and CMS policies.

FMSG also requires contractor support to assist with program management and technical activities for the esMD system. This effort requires disciplined project management support to coordinate tasks across multiple components and vendors.

Each of these tasks, HIGLAS, esMD, Security Management and other FMSG systems support will have unique requirements and schedules as needs develop under the terms of the contract. This SOW describes work CMS requires to support the activities, processes, and tools used for these operations.

PERIOD OF PERFORMANCE

The contract shall have a base ordering period which will be effective from the date of issuance and through a twelve month base period thereafter. There shall also be four (4) twelve month option periods, which shall be individually exercised at the discretion of the Government. The total contract ordering period will be effective from date of issuance and will be no longer than a total of five (5) years (60 months) thereafter.

GENERAL REQUIREMENTS

The TSC will work closely with the OFM and CMS FMSG Staff including but not limited to the subordinate organizational divisions of FMSG: the Division of Financial Application Systems (DFAS), Division of Technical Operations (DTO), Division of Program and Data Management (DPDM), and Division of Program and Support Systems (DPSS).

Independently and not as an agent of the Government (except where noted herein), the TSC shall furnish all the necessary services, qualified personnel, material, equipment, and workspace facilities, not otherwise provided by the Government, as needed to perform the Scope of Work.

Unless otherwise specified, the TSC shall deliver to CMS all written documents for this contract in electronic form, using the CMS enterprise office suite software format appropriate to the document (MS Word, PowerPoint, Excel, email attachments as appropriate). The TSC shall also provide a hard copy of each deliverable as specified in the deliverables section. The TSC shall be compliant to all Section 508 requirements. The TSC shall complete all its own individual Line Item support work plans, as well as any Medicare project planning documentation work products under this Agreement using Microsoft Project software. The TSC shall maintain a history of authorized support work for each individual Line of Business LoB. Comment by Author: What is LOB?

Before work begins on any large-volume effort involving significant documentation, the TSC shall submit an outline showing the content of the documentation and receive concurrence from the Contracting Officer Representative (COR). Once work begins on any documentation, the TSC shall submit working copies of the document at regular intervals for review. The Contractor and COR will set the interval for each document review in the individual line item.

MONTHLY STATUS REPORT AND MEETING

The TSC shall submit to the FMSG COR and the CMS Contracting Officer a Monthly Status Report per task order that includes the following:

A) Activities completed B) Activities in process C) Activities planned for the next period D) Status report of all reviewed deliverables E) Issues and concerns Generally, these reports will consist of charts, a brief written document plus discussions for elaboration, explanations, and to insure a common understanding of efforts. All activities, as identified within the SOW, shall be reported by hours, and show start and stop dates. At the activity level, the TSC shall provide both current reporting period, and cumulative figures for the hours worked by labor category and individuals within that category. Monthly status meetings shall be held between (but not be limited to) the TSC, the COR, and other CMS staff. The dates and times of the status meetings shall be established mutually between all parties. These meetings will be used to review the status of the support Work Plan, upcoming events, outstanding issues, and budget/money expenditures. In addition, the TSC must be available for ad hoc meetings and teleconferences as requested by CMS.

The TSC shall submit a weekly status report with activities performed as requested by, and at the discretion of, the CMS COR.

MEETING AGENDA AND MINUTES

The TSC shall prepare agendas for all meetings concerning the project unless otherwise stated by the individual support task order COR/business owner. Agendas shall be submitted to the CMS COR/business owner (unless otherwise directed) at least one business day prior to the meeting. When meeting with CMS, the TSC is responsible for recording meeting minutes and submitting those minutes to the CMS COR within two (2) business days after the meeting.

KEY PERSONNEL REQUIREMENTS

Certain positions may be designated as “Key Personnel”, within the meaning of Health and Human Services Acquisition Regulation 352.270-5. In addition, CMS reserves the right to have the TSC remove incompatible supporting labor resources without cause and require their immediate removal from CMS facilities. In addition, it is CMS Agency policy that all badges, passes, access and government property shall be surrendered to the CMS COR within 24 hours of determination that need no longer exists. The following are considered "Key Personnel": Comment by Author: Need to list the key personnel Project Manager OBIEE Developer Security Lead Information Security Officer

SCHEDULING/FACILITIES

CMS has a policy that encourages employees to work remotely or to work flexible schedules. As such, the TSC is advised to work with the COR to understand and work within schedule requirements. The nature of the work required at FMSG requires regular face-to-face communication between CMS and the TSC.

FMSG has a limited number of workstations available for contractor staff to use on an itinerant basis. These spaces can be shared among resources should they choose to work remotely intermittently.

As a result of the fluid nature of activities and schedules, the TSC is encouraged to coordinate work schedules with their CMS business owner to accommodate support requirements, other personnel availability, meeting schedules, vacation schedules and leave schedules.

TECHNICAL REQUIREMENTS

Due to the nature of the work under this contract, all of the TSC work papers, interim products, drafts, and deliverables shall be the property of the Government, and may be released only with consent of the COR and the CMS Contracting Officer (CO). All information provided by the TSC to CMS will be considered “procurement sensitive” and shall be treated accordingly. All TSC personnel shall be required to sign a statement of non-disclosure in regard to all information and materials received and viewed under this contract, prior to commencing work. All documentation provided by the Government to the TSC, to support the performance of this Agreement, shall be returned to CMS, when requested by the COR.

QUALITY ASSURANCE

Quality Assurance verification may include, but is not limited to:

· Validation that the established processes and procedures are being followed and required documentation and objective proof of performed activities is produced;

· Validation of daily HIGLAS production reconciliation reports such as system, application, and financial integrity

· Contract deliverables

· Work products

· Other outputs

· Key milestones, as identified, are tracked and status review to verify schedule(s) are met.

CMS will submit an annual evaluation of the TSC’s performance to the TSC and it will become part of the permanent record in the Government’s Contractor Performance Assessment Reporting System (CPARS).

TRAVEL

Contractor may be required to travel. Incurred costs shall be considered to be reasonable and allowable only to the extent that the Contractor does not exceed, on a daily basis, the maximum per diem rates in effect at the time of travel as set forth in the Federal Travel Regulations (FTR). Comment by Author: Do we have an estimated amount of travel. If so please add to this section.

ORGANIZATIONAL CONFLICT OF INTEREST

Due to the nature of the work inherent in this contract, the TSC:

1. Shall not be currently acting, and will not while acting as the FMSG TSC, be acting, as a Medicare Administrative Contractor (MAC), fiscal intermediary, carrier, Medicare Part C or D payment processor, MSPRC, or any other FMSG systems as listed in Appendix A; either as a prime or as a subcontractor.

2. The TSC will not be able to bid on any CMS future work for which they contributed, developed, wrote requirements and/or contributed to SOW development due to impaired objectivity, and unfair advantage.

3. The TSC principals, management, and support personnel shall not have any financial interest in any contractor performing work for FMSG as either a prime or first-level subcontractor. This prohibition shall also apply to nuclear family members. This is to avoid questions of impaired objectivity.

Initial and Annual-renewal Organizational Conflict of Interest disclosure and financial certifications will be required.

TRANSITION PLAN

Incoming Transition Plan

The incoming TSC contractor shall meet with CMS representatives and the Outgoing contractor (Tantus) within three (3) business days of contract award to establish appropriate liaison activities and priorities, and discuss the Transition Plan. Not later than one (1) week after notification by CMS that the transition to a new TSC contractor will take place, the incoming TSC contractor shall submit to the COR an Incoming Transition Plan. The Plan shall include but not be limited to the following categories of activities, which shall be performed during the transition:

Management:

1. The incoming TSC contractor shall establish internal liaison and administrative procedures for ensuring a smooth transition of maintenance activities from the incumbent TSC contractor (Tantus).

1. The incoming TSC contractor shall establish internal procedures for liaison and working relationships with the FSMG Divisions as specified by CMS (e.g., DFAS, DTO, DPDM and DPSS) who are involved with FMSG technical support activities.

1. The incoming TSC contractor shall establish and initiate control procedures needed for site and preparation and institute appropriate site security.

1. The incoming TSC contractor shall provide weekly progress status reports on achievement of transition milestones, deliverables, problems encountered, corrective action initiated and costs incurred versus costs projected.

Risk Management:

The incoming TSC contractor shall provide a list of, the priority of, and probability of, the potential risks during the transition period and the plan to mitigate each to the DPDM PM team.

System Security:

The incoming TSC contractor shall implement appropriate system security measures to assure the confidentiality of transactions.

Staffing:

The incoming TSC contractor shall address acquiring sufficient, qualified staff to support the FMSG systems.

Training:

1. The incoming TSC contractor shall establish a training schedule with the incumbent TSC contractor (Tantus) to address the technical aspects of the FMSG systems such as hardware and software configuration, overall structure of programs, formats, documentation, data dictionary layouts, reports, etc.

1. The incoming TSC contractor shall establish a training plan to address the program aspects of the FMSG systems, such as, CMS initiatives, etc... that will orient the new staff to the FMSG systems.

Hardware, peripheral and other FMSG resources:

1. The incoming TSC contractor shall ensure full access of system documentation.

1. The incoming TSC contractor shall install, test and ensure full operability of change control system (Integrity) for CMS CRs.

1. The incoming TSC contractor shall implement controls for detecting and averting problems in processing.

Knowledge Transfer:

For this transition, knowledge transfer will occur over the entirety of the 1 Month transition period. The knowledge transfer will take place via various methods. The incumbent Project Manager (PM) will coordinate formal classroom training sessions to be conducted by the incumbent IT Transition Lead. These sessions will focus on the specific IT concerns related to the database tasks and activities. The incumbent PM will also coordinate formal classroom sessions to be conducted by the incumbent Program Manager. These sessions will cover documentation requirements and organizational processes and assets. These sessions will be completed no later than 15 business days prior to the end of the 30 day transition period. Additionally, all successor contractor’s staff will work alongside their contractor counterparts throughout the 1 month period in order to gain familiarity with the database, tools, processes, and organizational assets. The PMs from incumbent TSC contractor (Tantus), successor contractor, and the CMS will meet no later than 10 business days prior to transition completion in order to determine if any further training or knowledge transfer is required.

The contractor shall identify how they shall coordinate with the incoming contractor and/or Government personnel to transfer knowledge regarding the following:

· Project management processes

· Points of contact

· Location of technical and project management documentation

· Status of ongoing technical initiatives

· Appropriate contractor to contractor coordination to ensure a seamless transition

· Transition of key personnel

· Identification of schedules and milestones

· Identification of actions required of the Government

· Establishment and maintenance of effective communication with the incoming contractor/ Government

· Personnel for the period of the transition via weekly status meetings

Knowledge Transfer shall also include, but is not limited to:

• Delivery of copies of existing policies and procedures, and delivery of required metrics and sstatistics.

• Timelines/Milestones

• Review, evaluation and transition of current support services

• Review of current system processes

• Transfer of historic data to new contractor

• All elements of the then-current database architecture to be transferred to the Government, or its designee, at the time of transition, along with any newly developed programs, source codes, system documentation, working papers, and all related information gathered or developed during the contract period of performance

• Government approved training and certification process

• Transfer of hardware warranties and software licenses (if applicable)

• Transfer of all necessary business and/or technical documentation

• Orientation phase and program to introduce Government personal, programs, and users to the contractor’s team, tools, methodologies, and business processes

• Lessons learned in the development of the system and during its operation and maintenance

• Turn-in of any government keys, ID/access cards, and security codes (as applicable)

Outgoing Transition Plan In the event that the incumbent contractor is not awarded the new contract for FMSG Technical Support, CMS will require the incumbent to provide transition services prior to the conclusion of their period of performance. The incumbent shall work with the new TSC contractor, CMS staff, as well as other identified CMS contractors to ensure continued operation of the FMSG System Support.

Prior to commencement of transition, CMS will request a transition plan from the incumbent. The incumbent contractor (Tantus) shall work with the incoming contractor to establish a joint transition management team capable of providing overall management and logistical support of all transition activities as well as provide adequate coverage to ensure uninterrupted service to the FMSG systems, be effectively and efficiently administered, and be completed within a one (1) month timeframe.

At a minimum, the Transition Plan shall provide for the following:

1. A resource-loaded project management schedule compatible with predecessor contractor software (if different).

0. Milestones and measurable commitments will be included in the schedule that will be used to ensure a smooth transition from the incumbent (Tantus) operation to sole operation by the successor.

1. A milestone chart detailing the time lines and stages of transition from the effective date of contract performance until the new TSC contractor assumes sole responsibility for the FMSG System Support work;

1. An organizational chart that displays internal and external organizational relationships. The organizational chart shall identify the individuals (at all levels) who will be responsible for the transition and their respective roles; detail the lines of communication and how the incumbent will interface with CMS during this phase of contract performance;

1. The Contractor will regularly report status to CMS in periodic meetings and regular written reports;

1. A plan to transfer Government-Furnished Property (GFP) (e.g., hardware, software, and records/data) from the incumbent to the successor, or to CMS or another CMS Contractor(s). CMS may elect to require the transition of contract-acquired property as follows:

4. Prior to procurement of an asset, that the incumbent shall propose a transition charge to be evaluated and negotiated by the CMS.

4. A successor to this contract, or CMS, will be afforded the opportunity to acquire assets at a reasonable transition charge. All existing assets shall remain installed and usable by CMS through the transition of assets for their replacement by the successor. In the event a decision is made not to procure the assets, then the incumbent has the responsibility to dispose of the assets as instructed by CMS.

1. As part of the transition plan the Contractor shall develop a support plan which includes the incoming Contractor for any operational/production issues or deployment fixes related to FMSG systems during the one (1) month transition.

The Contractor shall ensure transfer of knowledge and coordination regarding communication and transition support.

SCOPE OF WORK

The TSC will work closely with the components in FMSG to support their individual business functions and IT Systems. These functions include Project Management, Business Processes, Technical Operations, Applications Systems, Quality Assurance and Strategic Planning, esMD Program & Financial Systems, Governance, and Data Warehouse Management and Security Management. In addition to HIGLAS and esMD, FMSG also supports several legacy systems and other e-Health initiatives. These systems are listed in the Appendix to this document. Additionally, as new systems are brought under FMSG’s purview, the TSC shall provide support for the transition, start-up, and operation of such systems. The TSC will provide assistance in several areas of the HIGLAS implementation, operations, maintenance, strategic planning, analytic capabilities, reporting, transparency and general project management activities. The TSC will also provide assistance to other FMSG components as required and will support FMSG to ensure compliance with Federal and CMS IT guidance, The TSC shall be knowledgeable of and compliant with CMS IT Security Policies and Procedures. In order for FMSG to keep up with the growing number of new technologies, the TSC shall assist FMSG by providing technical advising services. These services may include business and technical analytics in the assessment and implementation of new technologies such as storage virtualization, cloud computing, identity management and credentialing services. In support of transparency the TSC shall assist FMSG with publishing data to strengthen its accountability to the public and to better use data and information in decision-support activities. The TSC shall assist FMSG with data sharing as it applies to sensitive information shared amongst multiple partners, using a wide variety of system platforms, applications and data format, and effective use of technology. The TSC shall assist FMSG with assessing current processes and developing new standardized processes as needed.

The TSC must possess knowledge and expertise in quality management. The TSC should include in their proposal a description of such expertise and should document results attained such as improved customer satisfaction, requirements determination, and testing success, etc.

The Government, through the CMS COR shall review and approve all work products, deliverables, and invoices submitted by the TSC.

The TSC will support FMSG in ensuring the quality of technical deliverables, work products, documentation, software releases, and operational services.

The TSC shall support FMSG in stakeholder management, including, but not limited to, CMS, the Department of Health and Human Services (DHHS), and other interested parties. The TSC shall assist FMSG with the development of communication materials. This may include, but is not limited to, briefing materials for presentations to stakeholders both within and external to CMS, meeting agendas, and meeting minutes. The TSC shall support FMSG in coordinating and consolidating comments on deliverables and other products. The TSC may need to create and maintain issue logs, spreadsheets, databases and perform data analysis.

The TSC in coordination with FMSG, and their CMS contractors shall assist in the overview and continual support including, but not limited to, quality services including procedures, checklists, quality criteria, and formats, to ensure efficient and effective reviews of deliverables and services. The TSC shall review deliverables, change requests, and/or software releases for acceptance and shall support FMSG in coordinating and consolidating comments on the deliverables and other products submitted by FMSG prime contractors.

The TSC shall support CMS FMSG staff with reviewing and verifying completeness, consistency and correctness of deliverables, work products, and other operational or technical documentation to ensure optimum quality of operations. The TSC may be required to coordinate a deliverable review process, track and compile deliverable status items and statistics reports that would include timeliness and quality indicators.

SUPPORT FOR CMS INTEGRATED IT INVESTMENT AND SYSTEM LIFE CYCLE FRAMEWORK

The TSC shall support FMSG with activities associated with the CMS Integrated IT Investment and System Life Cycle Framework. This includes, but is not limited to, support for: project management, change management, risk management, requirements development, interface coordination, business process reengineering, testing, reporting, development of project material in support of gate reviews and other project-related documentation as needed.

Competency 1 – Project Management Support Comment by Author: I do not see anything noted for transition in/out. Are there specific action items the KTR must do for transition in/out. The IGCE has it broken out-shouldn’t the SOW note what is expected of the Contractor during these times.

A Program Manager is needed and will be accounted for in Competency 1. Typical activities include oversight of the activities of this SOW, staff recruitment and retention, monthly status reports and financials submission, invoice reconciliation efforts as needed, etc.

A typical staff person performing assorted Project Management (PM) tasks should have project management experience, with proven expertise in earned value management, risk management, and cost and scheduling control. A BA or BS degree is highly desirable. The person should be adept at using Microsoft applications, have the ability to communicate verbally and in writing, and be able to analyze data, put it in a usable format, and maintain updates for CMS management.

Support to FMSG Management

The TSC will provide support and assistance to CMS in carrying out their duties related to:

Communications

The TSC shall support FMSG in developing and implementing HIGLAS communications for all HIGLAS stakeholders including, but not limited to, CMS, DHHS, the Office of Management and Budget (OMB), and Medicare Administrative Contractors (MACs). The TSC shall assist FMSG with the development of communication materials. This may include briefing materials for presentations to stakeholders both within and external to CMS.

Program and Cost Management The TSC shall assist FMSG in the support and analysis of the Project Master Plan, support review and analysis of contractor integrated baseline review materials, PM support for FMSG, earned value reporting/analyses, risk management and other related PM FMSG support.

The government anticipates this will require approximately 1.15 FTEs.

Competency 2 – Testing

The TSC shall provide support in managing the various types of application testing based on guidelines set by the HIGLAS Test Center of Excellence (HTCoE).

The TSC shall provide functional and technical support to FMSG in carrying out a variety of duties including but not limited to:

1. The TSC shall assist CMS with managing testing efforts throughout various stages related to HIGLAS Quarterly Release and Special Project testing. This will entail the review and validation of pre executed test scripts and post executed test scripts and results by providing comments as to completeness of documentation and adherence to procedures. This will be on an as needed basis and not applicable to all HIGLAS Change Request (HCRs) in a given Quarterly Release (QR). Comment by Author: Need to spell out HCRs and QR

2. The TSC shall assist CMS with managing the testing efforts related to special releases (non-standard quarterly releases) as needed in the same fashion as noted in item 1. This will be on an as needed basis and not applicable to all HCRs in a given special release.

3. The TSC shall assist CMS with providing support in managing the testing efforts related to Break Fix activity by validating test results. Break fix activity normally occurs during normal business hours except in cases where a Severity 1 or Business Severity 2 has been identified. The TSC will be responsible for addressing Severity 1 or business Severity 2 issues as directed by CMS. This work may occur outside typical business hours and may extend staff’s work hours on a particular day. Should that occur, staff will be required to adjust their weekly schedule accordingly so that they still work a 40-hour work week, (i.e. another day’s hours must be shortened so that the week’s hours are limited to 40.)

4. The TSC shall assist CMS with support in assessing and validating the existing software and hardware testing plans, procedures, tools, test cases, and test scripts providing feedback as to the validity and accuracy of information provided. The TSC will not be responsible for running software/testing offline.

5. The TSC shall assist CMS FMSG DFAS staff in updating Standard Operation Procedures (SOPs) documentation needed for testing activities, tracking logs for open and closed testing defects, reports, and other test related functions.

6. As needed, the TSC shall review and provide comments to FMSG with recommended updates to the HIGLAS Release Management Process Framework and the HIGLAS Application Maintenance Support Process Framework and Procedures documents that are typically sent out for review by the HIGLAS Contractor on a semi-annual basis.

The government anticipates this will require approximately 2. FTEs.

Competency 3 - FMSG System Solution Support

The TSC shall support FMSG with tracking and assessing system changes that are governed by the CMS Change Management Process. The CMS Change Management includes the CMS Change Requests, the HIGLAS Quarterly Releases, and the HIGLAS break-fix. The HIGLAS business processes refer to all HIGLAS Lines of Business. The TSC should have experience with reviewing regulations or policy changes that require a revision to existing instructions or the development of new instructions. The TSC should have experience with developing, tracking, and communicating system changes. The TSC should have knowledge of Government Accounting Regulations and Procedures. The TSC should have experience with collaboratively working with other teams to communicate system changes that are governed by the CMS Change Management Process. The FTEs shall work within the same core hours (6:30am-6:30pm) as CMS staff unless otherwise authorized by CMS Management.

The TSC shall assist FMSG staff with overseeing the activities that enable and enhance the functionality of FMSG System Solutions.

Stakeholders Communication and Support

The TSC shall assist FMSG with supporting communications and coordination between all levels of CMS, MACs, Shared System Maintainers, HIGLAS contractors, Data Center, and other Government Agencies. The TSC will assist with communicating system changes to the applicable stakeholders. The communication of system changes should be accomplished either face to face or via electronic media. The TSC should also have experience with Microsoft Office applications to include PowerPoint, Word, Excel, Visio, and Access Databases. The TSC should have a good working knowledge of the Oracle Federal Financials. The communications are managed through a variety of channels such as User Group meetings, online web meetings, regular meetings, electronic notifications, ad-hoc meetings, and written documentation.

1. The TSC shall support CMS Staff as needed/requested with the coordination activities related to the HIGLAS Quarterly Release Process. CMS will be providing direction to all stakeholders.

2. The TSC shall support the coordination activities related to the HIGLAS DFAS Break-Fix support. The HIGLAS DFAS Break-Fix support encompasses all lines of business (e.g., Benefits, APA, CCIIO, etc.). The TSC personnel do not provide direction; CMS will be providing direction to all stakeholders and the TSC will ensure that all stakeholders adhere to established schedules.

3. While the TSC will continue to provide Break-Fix support, they shall also assist with provisioning knowledge transfer and SOP documentation to DFAS on this activity to enable the transition of a majority of the work efforts that occurs during normal business hours to DFAS federal staff.

4. The TSC shall prepare weekly and monthly status reports.

5. As needed, the TSC shall provide support and advise FMSG of possible solutions to HIGLAS software and control problems. TSC personnel do not provide direction; CMS will be providing direction to all stakeholders and the TSC may be available to support CMS and provide any additional recommendations.

Change Management Support

The activities within the Change Management Support Task include but are not limited to:

1. The TSC shall assist FMSG in the review of draft versions of CMS Change Requests (CRs) that are in POC Review status in eCHIMP and Technical Direction Letters (TDLs) for HIGLAS impacts. The TSC shall assist FMSG with the review of the business requirements designated in the draft CRs and TDLs to determine impacts to existing HIGLAS business processes and functionality and solicit comments from the appropriate HIGLAS Subject Matter Expertise (SME) within FMSG in addition to the HIGLAS contractor. The TSC as requested shall consolidate and post the FMSG comments for draft CRs in eCHIMP. After CMS CRs with HIGLAS impacts have been finalized and approved for clearance in eCHIMP, the TSC as requested shall assist FMSG with the logging of a HIGLAS Enhancement Request (ER) and request the HIGLAS contractor to provide an LOE for CMS review to implement the mandated changes to the existing HIGLAS business processes and functionality to conform with the approved legislative, regulatory or policy changes stipulated in the CMS CRs and/or related TDLs. Additionally, the TSC shall review examine those same eCHIMP changes for potential impact to esMD and alert the DPSS Business Functional team when appropriate.

2. As requested, the TSC shall assist FMSG by participating in the HIGLAS Quarterly Release review of Enhancement Requests (ERs) prioritized by CMS to include the associated Level of Effort (LOE) estimates provided by the HIGLAS contractor.

3. As requested, the TSC shall review new instructions to determine the impact of the instructions as it relates to HIGLAS and current business processes. The TSC shall assess the impact of new instructions on system requirements and the need to develop new requirements.

4. The TSC shall support the implementation of system changes for all HIGLAS lines of business through the break fix and Quarterly Release Processes. Only as requested, the TSC shall attend meetings, review functional/technical documentation, review test scripts, and provide comments related to the new or revised system changes related to a specific HCR. There are typically four Quarterly Releases per year.

5. The TSC, with FMSG, shall identify and coordinate business process changes and improvements based on requirements for all HIGLAS lines of business related to financial management and reporting while determining potential procedural risk for any HCR they are requested to review. This shall happen quarterly.

6. The TSC shall provide the knowledge and understanding of the Oracle Federal Financials products used in HIGLAS in order to provide the expertise needed to support system changes. The TSC should provide support by reviewing change request documents, attending meetings, communicating system changes, and reviewing changes to determine impacts to HIGLAS for specific HCRs where input is requested.

7. The TSC shall provide analysis of current procedures and make recommendations for process improvements based on industry best practices, as tasked -at least annually, in order to support the FMSG system changes.

8. The TSC shall provide recommendations on industry standards for automating configuration setups or system changes, as requested, or approximately every six months.

9. The TSC shall provide oversight, maintenance, testing, and support of the FMSG Tools (e.g. Analytics, Formatting, Exceptions) addressing new requirements and issues to ensure continuity of operations. The TSC shall support CMS and End Users by the provisioning of User Training and Documentation for these tools.

10. The TSC shall provide minimal technical support for the Budget Formulation Tool. This includes system maintenance, code and report fixes, testing, and implementation of fixes as required.

The government anticipates this will require approximately 2.25 FTEs.

Competency 4 – Functional Support

The TSC will provide functional support and assistance to FMSG in carrying out their duties related to the task noted below. The TSC shall have experience with business process reengineering, Oracle Federal Financials, and Financial Integrity functionality, and should possess analytical skills, and knowledge of basic accounting concepts. The FTEs shall work within the same core hours (6:30am-6:30pm) as CMS staff unless otherwise authorized by CMS Management.

Business Process Reengineering Efforts (BPR)

1. As requested, the TSC shall provide functional support to CMS to identify business processes to be reengineered for FMSG system operations in support of all established Lines of Business (LOB) and any future LoB.

2. The TSC shall assist with the functional requirements definition and functional testing for the Oracle Business Intelligence Enterprise Edition (OBIEE).

3. As requested, the TSC shall recommend solutions, risk, and mitigation plans to support the ongoing operation of the HIGLAS System.

4. As requested, the TSC shall assist FMSG with improving the overall HIGLAS integrity reconciliations to include the financial, system, and application integrity reconciliations.

5. As requested, the TSC shall assist FMSG with efforts pertaining to month end close, financial reconciliation, and financial reporting.

6. As requested, the TSC shall assist FMSG with improving HIGLAS Audit Support processes and providing recommendations on Corrective Action plans resulting from CMS A-123 Internal Controls and CFO audits.

7. The TSC shall assist with provisioning knowledge transfer and SOP documentation on topics where the TSC has SME knowledge.

Supporting and Deploying Set Ups

The TSC shall support the deployment of various set ups in different environments including Production as requested by CMS. These include setups across all system modules. Examples include items such as CANs, AR Transaction Types and Receivable Activities, Year-End setups, GL setups, etc. The TSC shall assist CMS in providing Knowledge Transfer and SOP documentation of this activity. This work effort shall be shared across the TSC and DFAS staff.

Maintenance of the Commercial-off-the Shelf (COTS) Accounting System

The TSC shall assist FMSG in developing and reviewing detailed queries and reports designed to address the HIGLAS user community’s data request requirements. The number of queries and reports will depend on the type of data that is requested. The TSC should document each recurring query/report maintained by the TSC as part of a SOP.

Medicare and APA Reporting Requirements

1. The TSC shall assist FMSG in gathering and documenting Medicare reporting requirements including, but not limited to, those based on claim data. The claim data is interfaced to HIGLAS from the Shared Systems to include FISS and MCS.

2. The TSC shall assist FMSG in reviewing program and compliance reports based on claims and accounts receivable data and will provide technical comments. This activity will occur weekly and will amount to no more than eight hours per week.

BPR and Maintenance of HIGLAS Flat File Rendering

1. The TSC shall assist FMSG in maintaining HIGLAS Interface documentation including Design Specifications for interfaces and flat file renderings (FFRs) by maintaining the official configuration record, reviewing changes and incorporating approved changes. The TSC shall assist FMSG with reviewing the HIGLAS Interface documentation, providing recommendations for process improvements, and ensuring that the updated documentation is maintained in the data repositories. The TSC shall have extensive knowledge of the X12 and Health Insurance Portability and Accountability Act (HIPAA) standards, archival and retrieval processes, and data retention requirements. The TSC shall provide support within the same core hours (6:30am-6:30pm) as CMS staff unless otherwise authorized by CMS Management.

2. The TSC shall provide surveillance and reporting of changes or additions that are needed for HIGLAS interface documentation or FFRs.

HIGLAS Deliverables

As requested, the TSC will assist FMSG in reviewing the HIGLAS deliverables that require functional review or are associated with the tasks listed above and will provide technical comments.

The government anticipates this will require approximately 1.5 FTEs.

Competency 5 – Technical Support

The TSC will provide two experienced and knowledgeable SMEs to support development, implementation and problem resolution for HIGLAS OBIEE dashboards, including upgrades to the product.

The government anticipates this will require approximately 2 FTEs.

Security Management

The TSC shall provide technical expertise and analysis to assist FMSG in the oversight, validation, and verification of HIGLAS and other FMSG systems security operations. The TSC shall conduct access control management, processing and monitoring support for CMS on FMSG systems.

The specific activities required of the SC include:

1. FMSG Systems Security Management: The TSC shall assist CMS staff with the technical review of material provided by other contractors to document the activities related to the HIGLAS. These documents include a System Security Plan (SSP), the Information Systems Risk Assessment (ISRA), and other types of plans or assessments for the HIGLAS. The TSC shall assist FMSG to ensure that these documents are complete and in accordance with applicable industry best practices, and comply with Federal regulations and CMS policies.

The TSC shall provide the following support to FMSG as specifically tasked:

a. Assist in the analysis of security events or incidents that may arise

b. Assess firewall changes and make recommendations

c. Analyze job roles and responsibilities and provide recommendations on various role based access initiatives

d. Review change requests submitted by the HIGLAS contractor for implementation to Oracle Financial Systems for security compliance and impacts

e. Assist in researching and providing recommendations for the use of additional tools and software patches that FMSG could utilize to further improve its security posture

2. Disaster Recovery Planning: The TSC shall assist CMS with the assessment of risks to its facilities and business processes, and shall assist in describing the physical security and contingency measures it will undertake to preclude, minimize or counter these risks in the Disaster Recovery (DR) Plan, including contingency planning. This assessment should include all risks including personnel control, fire protection and prevention, electrical outages and natural disasters. The TSC shall assist FMSG with planning of the DR test and analysis of results.

3. Vulnerability Assessments: The TSC shall assess CMS vulnerability scans or in some cases conduct scans, and will assist CMS in developing the recommended solutions to resolve the vulnerability. This activity includes review of reports and data provided from device profiler scans, as well as tools such as AppScan, QRadar, Tenable, and nCircle. The TSC shall also assist FMSG in tracking findings to closure. Additionally, the TSC shall assist FMSG with the development and maintenance of processes and procedures for the device profiler scanning.

4. Annual Assessments: The TSC shall provide support to FMSG for conducting annual self-assessments and evaluation of Federal Information Security Management Act (FISMA) controls. This activity shall include developing and executing plan of action incorporating milestones and providing assistance to FMSG for reporting and tracking.

5. Audit and Review Support: The TSC shall provide support to FMSG for all internal and external audits and reviews, such as the OMB A-123 review, CFO audit, Security Controls Assessments (SCAs), and self-assessments. The support shall include assisting in the review of findings, in the development and closure of corrective action plans, and to ensure that all compliance descriptions, which may result from audits or assessments, remain current in the security documentation (i.e., SSP, ISRA). The TSC shall assist FMSG in tracking and providing management reports on all findings and progress on audits and reviews.

6. User and Account Management: The TSC shall establish, with the concurrence of CMS, a User Management Program, in which access to the HIGLAS environment (Production, Testing, and Development) is automated and controlled using procedural means combined with technical products. The current primary method for implementing User Management for the HIGLAS Oracle databases and Oracle applications is via the CMS Enterprise User Administration (EUA) system. The primary method for implementing User Management for other HIGLAS related applications (such as ClearCase, ClearQuest, ReqPro, VDI, HTCOE, GRC Tools, CMOD, Tenable, Remedy, ServiceNow, WebCenter, AIX servers, Window servers, and Linux servers) would consist of utilization of email notifications via the CMS EUA system or directly from CMS FMSG Division of Technical Operation’s (DTO’s) Security Team along with coordination between the DTO Security Team and the system administrators at the…