DIAGNOSE_SOW_12-18-2025_RFI.docx

CMS Data-Informed IT Alignment, Governance, Navigation, Oversight, Strategy, and Execution (DIAGNOSE) Statement of Work (SOW) Updated: 01/05/2026

Table of Contents

CMS Data-Informed, IT Alignment, Governance, Navigation, Oversight, Strategy, and Execution (DIAGNOSE) Statement of Work (SOW)

I. Purpose The Centers for Medicare & Medicaid Services (CMS) seeks to acquire experienced/expert support that enhances CMS’s capacity to plan, oversee and deliver mission-critical Information Technology (IT) and business initiatives while strengthening strategic IT capacities/initiatives, organizational communications, change management, and operational effectiveness.

The objective of this effort is to develop and coordinate comprehensive plans and technical approaches for solving IT problems throughout CMS while facilitating/coordinating the developed solutions with CMS and external partners. The objective includes developing plans that supporting CMS in IT Strategy, Program/Project Management support for Medicare Payment System Modernization (MPSM), Shared Services support and other initiatives , CIO Objectives and Key Results (OKR) Performance Meetings Support, Communications Strategy, Organizational Change Management, IT Governance and IT Investments.

Achieving this objective may be complicated by several factors, including conflicting program goals and initiatives, as well as evolving legislative, regulatory, and policy requirements. Decision-making is further complicated by unique technical requirements, variable operational conditions, inconclusive or incomplete data, and emerging technologies not yet adopted by CMS. Additional challenges include the need to integrate solutions with existing systems and processes and managing dependencies with external partners. The Centers for Medicare & Medicaid Services (CMS) seeks expert support to facilitate planning, oversight, and delivery of mission-critical IT and business initiatives.

· Provide a critical infusion of project management expertise and solutions engineering.

· Help plan, control, and monitor projects as an integral part of the project management team.

· Function as an agent in the management of assigned projects and as an integrated team member.

· Provide rapid responsiveness to changing requirements.

· Recognize Government objectives as its own objectives.

· Institute and practice the same services being requested by CMS.

· Be responsible for the correctness of methods and techniques used.

II. Background CMS provides health care services to over 130 million beneficiaries. The agency faces increasing complexity and resource constraints as it implements new legislative mandates and modernizes business processes and IT to support the business. With the increase in the number of Americans receiving healthcare through these programs, CMS is responsible for leading transformational change in the health care delivery system. At the same time, resource constraints and increasing program complexity pose significant challenges to CMS as it seeks to expand its capacity for supporting and effectively executing its mission.

Additionally, CMS has the responsibility of implementing many provisions under enacted laws, such as the Affordable Care Act (ACA) of 2010, the American Recovery and Reinvestment Act (ARRA) of 2009, and Medicare Modernization Act (MMA) of 2003, as well as enforcing and 47881) and Protecting and Improving Medicare for Our Nation's Seniors (84 FR 53573). In the administration of these programs and provisions, CMS makes continuous changes to existing programs, systems, and management processes as well as developing new ones, both in response to new legislation, and through our constant efforts to improve our management of these programs.

Since 2021, the Program/Project Management Support (PPMS) (prior contract name) contract has supported the Agency in modernizing business processes and supporting systems and operations in a collaborative and efficient manner. Due to legislative drivers and CMS high impact initiatives the number of priority operational initiatives and projects continues to grow, and CMS is challenged with completing more projects with less time and limited resources. In addition, there is increasing administrative demand in tracking and reporting for different audiences on the various projects, especially the high priority projects and initiatives, as they support CMS and Department of Health and Human Services (HHS) priorities. Further, the current communication infrastructure encompasses a broad spectrum of platforms, services, and communication artifacts that are essential to the organization's internal operations and external engagement. These artifacts vary in scope from enterprise-wide messages and executive-level briefings to operational alerts and technical guidance and require careful coordination to ensure consistency, clarity, and compliance with federal communication standards. Consequently, the volume of communication data flows varies.

III. Objectives Task 1: IT Strategy The Contractor shall support, participate in, and collaborate with CMS staff in support of the endeavors deemed mission focused by the CIO initiatives and OIT Leadership.

The Contractor shall support organizational and process improvements as well as other transformational initiatives. The contractor shall support the CIO and OIT Groups in the development, finalization, and execution of the CMS IT Strategy. This includes stakeholder engagement, information gathering, drafting and refining long-term plan objectives, aligning initiatives with CMS mission and federal mandates, and supporting implementation through performance measurement, reporting, and communications to ensure the strategy is adopted and sustained across CMS.

Task 1.1: IT Strategy Implementation (Program Management Support) IT Strategy is the comprehensive roadmap that aligns CMS's technology initiatives with the agency's mission, priorities, and federal mandates. IT Strategy under this contract should reflect helping the CIO and OIT develop, refine, and execute Enterprise technology planning to include but not limited to:

· Strategic Planning Excellence – Enable successful development, refinement, and execution of the CMS IT Enterprise Plan

· Enterprise Alignment – Achieve effective stakeholder engagement and alignment of technology initiatives with CMS mission and federal mandates

· Execution Effectiveness – Deliver measurable progress through robust project management, change management, and performance tracking capabilities

· Innovation Readiness – Provide actionable insights on emerging technologies and industry best practices that inform strategic decisions

· Secure Access Enablement – Support achievement of AccessCMS program objectives for secure, seamless user access across the enterprise Task 1.2 MPSM Program and Project Management Support The contractor shall provide program/project management support to the Division of Medicare System Modernization (DMSM) in support of the Medicare Payment Systems Modernization (MPSM) effort.

· Risk Management- The contractor shall provide support to identify and consider impact of potential risks related to scope, resources, schedule, cost (annual and total life cycle), technology, security, partnership/stakeholder involvement, organizational culture, and sponsorship, to help ensure that CMS considers risks appropriately in the planning process and manages risks efficiently and effectively throughout the program/project life cycle.

· Budget Support: The contractor shall provide support to in relation to the MPSM budget and investment reporting. The contractor shall provide ongoing support and expertise with investment related deliverables and artifacts, as requested by CMS.

· SharePoint and Confluence Support: The contractor shall provide SharePoint and Confluence related support to CMS and authorized Contractors including managing access and providing technical support for the DMSM and MPSM SharePoint and Confluence sites.

· Meeting Support & Facilitation: The contractor shall attend DMSM and MPSM related meetings to provide support, take meeting minutes, and action items. The contractor shall be responsible for ensuring meeting minutes are distributed and stored/organized for future access. Additionally, the contractor shall capture relevant action items and follow up if/when needed. The contractor shall also prepare meeting materials, presentations, or other artifacts, as requested by CMS.

Task 1.3: Project Management Office (PMO) for Shared Services Support The contractor shall provide the following supports services:

· Agile Support: The contractor shall provide support with an Agile approach, including, but not limited to: development of sprints and related analytical products for the selection, implementation, agile support and training and governance of new projects. The contractor shall use Agile methodologies and collaboration tools such as JIRA, Confluence and M365 Collaboration tools to develop a program management framework for Shared Services efforts.

· Shared Services Program Management Office (PMO) Support: The contractor shall facilitate enterprise solutions that realize cost avoidance and enhance functionality beyond what a component would be able to do independently. In addition, the contractor will provide project management support via development of agendas, participation in governance board meetings and documenting minutes and action items. The vendor shall integrate all aspects of the Shared Services program into this existing PMO structure. In addition, the contractor shall provide strategic planning advice and guidance on how to best identify and support new shared services candidates, including but not limited to resource needs, implementation support, meeting facilitation, preparation of analytical papers, and serving as a liaison with Shared Services team members and component business owner.

· Shared Services Governance Support: The contractor shall deliver and enable comprehensive governance of CMS Shared Services operations in alignment with OIT Front Office priorities. Success will be measured by effective oversight, performance management capabilities, and strategic alignment with CMS enterprise objectives across multiple business components and systems.

· Strategic Roadmap Development : Contractor shall enable creation and execution of comprehensive Shared Services strategic plans and roadmaps

· Cross-Component Alignment – Contractor shall achieve effective coordination between Business owners and system maintainers across organizational boundaries

· Enterprise Architecture Integration – Contractor shall deliver outcomes that ensure alignment with enterprise architecture standards and promote standardization

· Community of Practice Success – Contractor shall enable effective implementation and operation of the Shared Services Community of Practice (CoP) through coordinated event management and facilitated discussions

· Additional Shared Services Support: The contractor shall support the following on-boarding activities, including, but not limited to: engaging tool vendors on license agreements, enterprise org integration and support, identity management, cybersecurity procedures, technical integration of shared services across components and programs and facilitation of stakeholder buy-in and adoption of new Shared Services.

· Enterprise Salesforce Services (ESFS) Support: The contractor shall work in collaboration with the Enterprise Salesforce Services (ESFS) contractor to implement and maintain a Change Control Board (CCB). This CCB will serve as the governing body in prioritizing projects and enhancements for the Salesforce Enterprise Integration (SEI) platform and business applications.

· Marketing and Communications: The contractor shall create marketing and communication materials for Shared Services outlining the Enterprise tools available to support CMS.

Task 1.4: CIO OKR Performance Meetings Support

· Performance Management & Administrative Support: Contractor shall provide comprehensive meeting facilitation, documentation, action item tracking, and data-driven framework development for biweekly CIO OKR Performance Meetings

· Stakeholder Coordination & Cross-Functional Collaboration: Contractor shall facilitate cross-functional teamwork, coordinate stakeholders, and support leadership engagement to accelerate decision-making across OIT and CMS components.

· Data Analytics & Visualization: Contractor shall develop Power BI dashboards, maintain data collection systems, and ensure real-time visibility into progress and roadblocks across all challenge areas.

· Communication & Knowledge Management: Contractor shall create and maintain all meeting communications, reports, SharePoint sites, training materials, and manage the Champion recognition program.

· Technology Platform & Process Improvement: Contractor shall maintain SharePoint platforms, provide technical support, ensure system scalability, and implement continuous process improvements for consistent value delivery Task 1.5: AccessCMS Program Support The contractor shall provide qualified program management services to support the Agency’s CIO Enterprise goals, including the AccessCMS program. The contractor will coordinate with CMS to accomplish the following mission, “To deliver a positive experience where all users can securely and seamlessly connect, with confidence, to the CMS ecosystem.”

The contractor shall work directly with the CMS Product Manager and associated team (CMS Staff and ADOs) to support and ensure the successful project coordination of the people, process, policy, and technology to achieve the following AccessCMS outcomes:

· Security & Compliance Excellence- Contractor shall enable authorization controls that ensure only authorized individuals and systems access appropriate resources, enhancing security and compliance posture

· Enterprise Identity Management- Contractor shall deliver enterprise-class capabilities for managing digital identities, credentials, and access to systems and applications

· Data-Driven Decision Making- Contractor shall provide insights and analytics that improve data-driven decision-making regarding identity and security needs

· User Experience Optimization Contractor shall achieve a user-friendly identity experience that empowers every user to connect with confidence across the CMS ecosystem The contractor shall provide the following program and portfolio management support services:

· Agile / SaFE Program and Project Management Delivery: The contractor shall provide support, using an Agile approach including program and portfolio management best practices to delivery program outcomes. This includes but is not limited to sprint development leveraging Release Train Engineer practices, integration and implementation support across a multi-functional team, program and product level risk management and governance of new projects. The contractor shall use Agile methodologies and collaboration tools such as JIRA, Confluence and M365 Collaboration tools to develop a program management framework for AccessCMS program efforts.

· AccessCMS Program Management Office (PMO) Support, Organization and Management Approach: The contractor shall provide project management support via development of agendas, participation in board meetings and documenting minutes and action items. The contractor shall provide integration services across all aspects of the AccessCMS program. In addition, the contractor shall provide strategic planning advice and guidance on how to best identify and support new AccessCMS projects and assist with implementation support, meeting facilitation, preparation of analytical papers, briefing materials and serving as a liaison to CMS stakeholders. The contractor shall deliver product strategy, roadmaps, stakeholder engagement plans, program charters, SLAs, backlog management tracking, risk registers, and weekly performance reports that meet established quality standards and timeline commitments.

· AccessCMS Governance Support: The contractor shall deliver and enable comprehensive governance of AccessCMS program operations in alignment with OIT Front Office priorities. Success will be measured by effective oversight, performance management capabilities, and strategic alignment with CMS enterprise objectives across multiple business components and systems.

· Strategic Roadmap Development: Contractor shall enable creation and execution of comprehensive strategic plans and program/product roadmaps.

· Cross-Component Alignment: Contractor shall achieve effective coordination between Business owners and system maintainers across organizational boundaries.

· Enterprise Federal Standards Alignment and Integration – Contractor shall deliver outcomes that ensure alignment with federal standards including OMB, NIST, and HHS.

· Human-Centered Design Support: Contractor shall maintain full accountability for the organization, management and HCD strategy and processes in order to achieve specified performance objectives.

· Marketing and Communications Support: Contractor shall create marketing and communication materials, in alignment with CMS standards and based on varying audiences, to socialize and inform stakeholders of the AccessCMS program.

Task 2: Communications Strategy and Organizational Change Management Communications Framework is the systematic approach to internal and external messaging that ensures CMS IT initiatives are clearly understood, supported, and successfully adopted across the organization. The communications framework under this contract should enhance the CIO’s and OIT’s communication effectiveness while strengthening stakeholder engagement through strategic, targeted messaging and comprehensive communication planning

Organizational Change Management (OCM) provides comprehensive support focused on solution-oriented approaches through strategic communication, mentoring, and guidance to support staff navigation through organizational transitions. As part of the change management transformation, the contractor will establish mentoring and guidance frameworks that enable staff to understand, adopt and ultimately embrace organizational change within the broader ecosystem. This includes the people, process, and technology changes needed to respond to evolving environments and achieve the agency’s and CIO’s objectives and priorities. The contractor will design and assist in the execution of OCM strategies as well as create sustainable management processes that can be replicated across future OIT transformation initiatives.

CMS requires an expert team of communication and OCM professionals with demonstrated expertise in advanced communication techniques, enterprise communication planning, and OCM methodologies. The team must possess comprehensive knowledge of CMS’s organizational structure and culture. Team members shall demonstrate the ability to apply specialized communication and OCM expertise (with customization capabilities to meet specific goals and objectives) within complex, fast-paced environments, as evidenced through relevant professional experience and successful project outcomes to include but not limited to the following core competencies:

The contractor shall demonstrate specialized expertise through successful delivery in complex, fast-paced environments, with comprehensive knowledge of CMS's organizational structure and culture. The contractor shall possess customization capabilities to meet specific goals and objectives.

· Strategic Communication Planning: Contractor shall deliver high-impact communication plans that enable successful execution of CIO/OIT initiatives and drive stakeholder alignment

· Unified Messaging and Outreach: Contractor shall assist in developing unified messaging across all OIT communication channels and produce outreach materials that effectively engage target audiences and drive desired behaviors and outcomes.

· Organizational Change Management Excellence: Contractor shall provide OCM support that enables smooth transitions, minimizes resistance, and accelerates adoption of organizational changes

· Message Clarity and Engagement: Contractor shall provide support to efforts to enhance message clarity, engagement, and retention across audiences.

· Performance Measurement and Optimization: Contractor shall enable data-driven communication improvements through effective measurement of communication effectiveness and stakeholder engagement, with actionable insights for continuous optimization

Task 3: IT Governance IT Governance is the framework, processes, and decision-making structures that ensure CMS’s IT resources are used effectively, mission aligned and in compliance with law and policy. IT Governance under this contract should reflect helping the CIO and OIT run and strengthen these governance functions to include but not limited to;

· Governance Framework Excellence: Contractor shall enable a robust, continuously improving IT governance ecosystem through effective framework design, comprehensive documentation, and clearly defined governance boards, decision authorities, and escalation paths

· Transparency and Performance Visibility: Contractor shall deliver mechanisms (dashboards, scorecards, reports, AI tools) that provide actionable visibility into IT decisions, risks, and performance across CMS's portfolios, enabling data-driven governance

· Compliance and Risk Management Alignment: Contractor shall ensure governance processes achieve full alignment with federal policies and CMS enterprise risk management practices, including cybersecurity and privacy standards under FISMA and NIST guidance, through comprehensive review and actionable recommendations

· Governance Operations Excellence: Contractor shall deliver operational and analytical support that enables effective CMS governance board functioning. Contractor shall support efforts to improve IT project triaging, SME accountability, decision documentation and follow up action management that drive accountability and follow-through Task 4: IT Investments IT Investments encompasses the portfolio management, analysis, and optimization of CMS's technology spending to ensure maximum value, alignment with enterprise priorities, and compliance with federal investment requirements. Support here should reflect helping the CIO and OIT make data-driven investment decisions and manage the IT portfolio effectively to include but not limited to;

· Strategic Portfolio Prioritization: Contractor shall enable effective prioritization of initiatives based on mission impact, risk, and strategic value across the comprehensive IT investment portfolio, ensuring resources are directed toward highest-value opportunities

· Performance Measurement and Value Realization: Contractor shall deliver performance measurement frameworks that provide clear visibility into ROI, mission outcomes, and operational efficiency of technology investments, enabling accountability and continuous improvement

· Evidence-Based Decision Making: Contractor shall provide data solutions that enable evidence-based investment decisions through robust data analytics to identify cost categorization and strategic alignment for several of CMS’ IT Project portfolios

· Automated Reporting Capabilities: contractor shall enable efficient, accurate cost categorization reporting through automated solutions that streamline information collection and reduce manual effort while improving data quality and timeliness. Cost categorization should apply to the project/funding number, which can roll up to investment and portfolio levels

IV. Deliverables These deliverables are iterative in nature and prioritization, definition of done and/or decisions to pivot are incorporated within the agile cadence. The structure of the support team will be fluid and adaptable based upon prioritizations, always able, at a minimum, to deliver the competencies identified in the first paragraph. There is an expectation that as the OIT Enterprise Plan advances to later stages of readiness the focus will be on communications and outreach to showcase information on the CIO vision, mission and objectives, and the OIT Enterprise Plan.

The tasks, outcomes and deliverables are subject to adjustment over the course of the project via routine check-ins with the CIO and other stakeholders involved in the project and if needed discussions on any associated personnel need changes will take place.

Deliverables will be defined and refined in collaboration with CMS, but may include:

Measurable: Include milestones and task assignments.

Achievable: Align with resources and stakeholder expectations.

Relevant: Supports project objectives and SOW compliance.

Time-bound: Deliver within 60 days after start of performance period.

Once

Measurable: Code passes agreed functionality and quality checks.

Achievable: Developed using approved tools.

Relevant: Supports research and development objectives.

Time-bound: Delivered on an ongoing basis per sprint schedule.

Ongoing

Measurable: Twice-weekly documented sessions.

Achievable: Scheduled within team availability.

Relevant: Ensures continuous communication.

Time-bound: Twice weekly throughout project.

Twice Weekly

Measurable: Weekly meetings documented with action items.

Achievable: Conducted with key stakeholders.

Relevant: Supports strategic alignment.

Time-bound: Weekly throughout project.

Weekly

Measurable: Weekly meetings with documented outcomes.

Achievable: Scheduled with technical team.

Relevant: Addresses technical risks.

Time-bound: Weekly throughout project.

Weekly

Measurable: Posts and memos published on agreed cadence.

Achievable: Created using CMS-approved channels.

Relevant: Keeps stakeholders informed.

Time-bound: Weekly or bi-weekly.

Weekly / Bi-Weekly

Measurable: Document sprint goals and backlog items.

Achievable: Conducted with development team.

Relevant: Supports iterative progress.

Time-bound: Occurs bi-weekly.

Bi-Weekly

Measurable: Report includes all required sections.

Achievable: Prepared using CMS-approved tools.

Relevant: Provides transparency and progress tracking.

Time-bound: Delivered monthly.

Monthly

Measurable: Align with OMB M-25-21 and M-25-22 mandates.

Achievable: Developed with stakeholder input.

Relevant: Supports federal AI compliance.

Time-bound: Delivered quarterly.

Quarterly

Measurable: Include performance metrics and strategic insights.

Achievable: Based on project data.

Relevant: Enables continuous improvement.

Time-bound: Delivered monthly.

Monthly

Measurable: Document meeting outcomes.

Achievable: Conducted with stakeholders.

Relevant: Promotes knowledge sharing.

Time-bound: Occurs monthly.

Monthly

Measurable: Meet agreed content and quality standards.

Achievable: Developed by SMEs.

Relevant: Supports research objectives.

Time-bound: Delivered bi-monthly.

Bi-Monthly

Measurable: Blueprint includes actionable recommendations.

Achievable: Based on validated data.

Relevant: Guides CMS implementation.

Time-bound: Delivered quarterly.

Quarterly

Measurable: Includes all required sections and insights.

Achievable: Compiled from project outputs.

Relevant: Serves as a reference for future initiatives.

Time-bound: Delivered annually.

Annually

Measurable: Includes all objective outcomes.

Achievable: Based on project tracking tools.

Relevant: Supports planning and prioritization.

Time-bound: Delivered within 30 days prior to end of annual period.

Annually

Measurable: Includes strengths and recommendations.

Achievable: Based on research and analysis.

Relevant: Supports CMS strategic goals.

Time-bound: Delivered within 30 days prior to end of annual period.

Annually

Measurable: Includes comparative analysis.

Achievable: Based on validated data.

Relevant: Supports decision-making.

Time-bound: Delivered within 30 days prior to end of annual period.

Annually

Measurable: Includes all required insights.

Achievable: Compiled from project documentation.

Relevant: Guides continued implementation.

Time-bound: Delivered in last month of final performance period.

End of Final Period

V. Key Personnel CMS requires a PMP certified Project Manager (PM) with relevant experience and subject matter expertise in each Objective area, including:

· Proficient Knowledge of CMS-Similar Infrastructure and Applications

· Qualifications: Bachelor’s degree or higher in Computer Science, Information Technology, or related field.

· Certifications: Preferred certifications include ITIL Foundation, CompTIA Network+, or equivalent.

· Experience: Minimum 5 years working with enterprise-level infrastructure, including distributed and mainframe platforms.

· Experience in Strategy Implementation Guidance

· Qualifications: Degree in IT Management, Business Administration, or related discipline.

· Certifications: PMP or PMI-ACP preferred; TOGAF certification is a plus.

· Experience: At least 5 years of providing strategic IT guidance aligned with industry best practices and emerging trends.

· Technical Writing and Publishing Skills

· Qualifications: Strong command of technical documentation standards and tools.

· Certifications: None required; certification in Technical Communication (e.g., STC) is desirable.

· Experience: Minimum 3 years producing technical reports, manuals, and publications for IT projects.

· Experience in Agile Methodologies, Requirements Analysis, and Cross-Functional Team Leadership

· Qualifications: Degree in IT, Engineering, or related field.

· Certifications: Certified Scrum Master (CSM) or PMI-ACP required.

· Experience: At least 3–5 years leading agile teams and performing requirements analysis.

· Human-Centered Design Expertise

· Qualifications: Training in UX/UI design or Human-Centered Design principles.

· Certifications: HCD or UX certification preferred (e.g., IDEO U, Nielsen Norman Group).

· Experience: Minimum 2–3 years applying HCD approaches in IT solution design.

· Expertise in Communications & Change Management

· Qualifications: Degree in Communications, Organizational Development, or related field.

· Certifications: Prosci Change Management Certification or equivalent preferred.

· Experience: At least 3 years developing and executing communication strategies and change management plans.

The PM will work with the Federal Lead to develop and shape the actions in support of the program. CMS requires a review of complete resumes for all key personnel.

VI. Section 508 Electronic and Information Technology Standards As required by HHSAR 352.239-4, Electronic and Information Technology Accessibility, the Section 508 accessibility standards applicable to this contract or order are identified as follows:

E206 Hardware E206.1 General. Where components of ICT are hardware and transmit information or have a user interface, such components shall conform to the requirements in Chapter 4.

E208 Support Documentation and Services E208.1 General. Where an agency provides support documentation or services for ICT, such documentation and services shall conform to the requirements in Chapter 6.

E302 Functional Performance Criteria

302.1 Without Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that does not require user vision.

302.2 With Limited Vision. Where a visual mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited vision.

302.3 Without Perception of Color. Where a visual mode of operation is provided, ICT shall provide at least one visual mode of operation that does not require user perception of color.

302.4 Without Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that does not require user hearing.

302.5 With Limited Hearing. Where an audible mode of operation is provided, ICT shall provide at least one mode of operation that enables users to make use of limited hearing.

302.6 Without Speech. Where speech is used for input, control, or operation, ICT shall provide at least one mode of operation that does not require user speech.

302.7 With Limited Manipulation. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that does not require fine motor control or simultaneous manual operations.

302.8 With Limited Reach and Strength. Where a manual mode of operation is provided, ICT shall provide at least one mode of operation that is operable with limited reach and limited strength.

302.9 With Limited Language, Cognitive, and Learning Abilities. ICT shall provide features making its use by individuals with limited cognitive, language, and learning abilities simpler and easier.

602 Support Documentation

602.1 General. Documentation that supports the use of ICT shall conform to 602.

603 Support Services

603.1 General. ICT support services including, but not limited to, help desks, call centers, training services, and automated self-service technical support, shall conform to 603.

VII. Assumptions

1. CMS must provide guidance in the form of standards, policies, procedures and oversight of this Task.

2. There may be times when the contractor shall be required to have staff at the CMS complex, as requested by CMS.

3. Contractor personnel who are required to obtain a CMS badge shall undergo a background investigation at the contractor’s expense.

4. There may be times when the contractor shall be required to work in partnership with DEA to complete various areas of work.

5. All contractor personnel shall participate in CMS Information Security Awareness Training.

6. The contractor shall establish connectivity to CMS, to perform required tasks.

7. The contractor agrees to have their employees sign the Rules of Behavior Security Agreement for Intra-connections to CMS Networks before connecting contractor owned equipment to the CMS network. In addition, the contractor agrees to have all equipment being used for connecting to the CMS Network inspected by CMS employees.

8. The contractor shall use the current CMS standard desktop suite versions for all deliverables.

9. All deliverables developed by the contractor shall be made accessible in accordance with Section 508 of the Rehabilitation Act of 1973, as stated in Section J.13 (Section 508 Accessibility of Electronic and Information Technology).

10. Where timeframes are stated, CMS may choose to consider unforeseen circumstances. Therefore, deliverable due dates are as stated unless otherwise agreed to by CMS and the contractor. Throughout this document, unless specifically denoted as workday(s), all timeframes are in calendar days, calendar weeks, and calendar months.

11. All products, including software and all utilities (proprietary and non-proprietary) developed to support the activities and deliverables of this contract, are the property of CMS. The contractor shall deliver all products, including software and utilities (proprietary and non-proprietary), and deliverables of this contract at the request of CMS or upon termination of this contract.

12. The contractor shall provide software and/or licenses for software as required by CMS.

13. The contractor shall be responsible for purchasing any hardware needed to accomplish their tasks.

14. The contractor shall make use of COTS applications that are available at CMS to aid in the testing and validation of the various pieces of the application and tools related to development in a cloud environment.

15. All system software must be developed using CMS standard application development tools and open source software utilized in development of applications residing in the cloud.

16. The contractor shall not design, implement, or maintain any customized or proprietary utilities without prior approval in writing from the COR.

17. The contractor shall comply with OIT dataset naming conventions, JCL conventions, security protocols and all associated documentation. Refer to Sections 6, 7, and 9 of the CMS Data Center Users’ Guide for specific standards.

18. The contractor shall attempt to use test data, instead of production data, for the purposes of testing whenever possible. Production data shall only be used for testing if it is approved by CMS. The data shall be kept secure by the contractor. The data shall be used for no other purposes other than for the test being conducted at the time, and when there is no other alternative available to meet the deadline for a release.

19. All-Fusion ERwin Data Modeler is the standard data-modeling tool used at CMS.

20. Endevor is the standard software configuration management tool used at CMS.

21. CMS shall provide training to contractor staff on CMS unique software and tools (ie: e- CHIMP, Remedy, Dynamic Object Oriented Requirements System (DOORS)) that are required for this contract, upon contractor request.

22. The contractor shall provide contractor staff training on software and tools that are not unique to CMS and may be required for this contract. (For example: Web Sphere, Endevor, Oracle, DataBase2 (DB2), JAVA).

23. The contractor shall provide training to CMS staff on contractor unique software and tools, upon CMS request.

24. The Contractor shall conduct training classes at CMS’s central office site in Baltimore, Maryland or a CMS approved alternate facility. The Government shall provide the room for all meetings. CMS will not provide equipment or office facilities at the CMS site for contractor personnel.

25. Any expected reimbursable travel expense shall be included at the time of award of specific requirements placed hereunder. CMS defines local travel as travel that is less than twelve (12) hours in duration within the Washington Metropolitan Area, including Baltimore, MD, and Virginia, and does not require overnight lodging.

26. Travel performed for personal convenience or daily travel to and from work at the contractor’s facility or local Government facility (i.e.: designated work site) shall not be reimbursed under this contract.

27. If travel is proposed the Contractor’s business proposal shall segregate it from other pricing/elements and the breakout shall include: Names of travelers, destinations (to and from), mode of transportation, mileage, rental cars, hotel, purpose of trip, etc.

28. All travel will be performed on an as needed basis and submitted to the CMS Contracting Officer Representative (COR) for approval prior to execution. Per diem will be reimbursed at Government-approved rates in effect at the time of travel. All travel as well as per diem (lodging, meals and incidentals) shall be reimbursed in accordance with the Federal Travel Regulation (FTR) – For reference purposes refer to the below link: http://www.gsa.gov/portal/content/104790