THE PURPOSE OF THIS MODIFICATION IS TO UPDATE ITEM G. KEY PERSONNEL.

该任务订单的目的是获得软件支持、操作和维护 支持ITAC应用程序组合中的系统，包括几个关键应用程序 在国家心肺和血液研究所（NHBLI）和国立卫生研究院使用 （NIH）。国家心肺血液研究所（NHLBI）维护着一个应用程序组合， 支持NHLBI内部和外部的受众。这对我们的 信息技术和应用中心（ITAC），以保持所有应用程序的最新，安全， 而且没有窃听器这涉及到内容、结构、代码和图形的更新。不像软件 由新的功能需求驱动的发展，维持主要由 非功能性需求。这些变化可能是环境的变化， 软件运行，并且软件可能需要被修改以继续如最初那样运行 设计了其中一种情况是硬件和软件生命周期结束政策的结果， 如果没有供应商的支持，任何硬件或软件都不能继续生产，或者 开源软件，社区支持。在这里，软件可能需要更新，以便 继续运行，不后退。这至少需要严格的测试，以确保 没有回归，在最复杂的情况下，它可能需要更新代码以使用新版本的库， 在某些情况下，用替代品取代支持软件和库。在其他情况下 维护可能涉及直接或通过客户对后端数据库进行更新 工具.管理用户和角色、更新参考数据以及验证和修复数据负载都属于 到这一类。此外，维护小组还应验证软件， 从所有ITAC开发合同过渡到维持组合，并升级到 政府在代码中的任何缺陷，并建议潜在的补救措施。最后，软件 投资组合必须保持适当的安全文件，以确保相关当局 运营（ATO）仍然有效，并符合政策，标准和法规。 NHLBI将这些维持活动分为以下几类： 限于）： ·纠正性维护 ·自适应维护 ·预防性维护 ·应用程序操作支持 ·过渡支持 ·系统评估和授权 为维持一个可靠和运作良好的资讯科技维修支援环境， 重要的是，资源已准备就绪并可用于支持停机、紧急情况和应用程序 必要时部署。解决停机、紧急情况和应用程序部署可能 需要7天24小时的支持，这将需要在正常工作时间以外提供资源 在工作日和周末。 政府打算让维持承包商提供软件评估， 在维持组合中的应用，包括但不限于性能评估， 代码质量和安全性。随着软件从主动型过渡到主动型， 软件必须根据一套 验收标准。因此，需要将维持职能与 开发团队和适当的检查和平衡，以确保过程的完整性。

The purpose of this task order is to acquire software sustainment, operations and maintenance support for systems within the ITAC application portfolio, including several critical applications utilized across National Heart Lung and Blood Institute (NHBLI) and National Institutes of Health (NIH). The National Heart, Lung, and Blood Institute (NHLBI) maintains an application portfolio that supports audiences both internal and external to the NHLBI. It is of significant importance for the Information Technology and Applications Center (ITAC) to keep all applications up-to-date, secure, and bug-free. This involves updates to content, structure, code, and graphics. Unlike software development which is driven by new functional requirements, sustainment is driven primarily by non-functional requirements. These changes may be changes in the environment in which the software operates, and the software may need to be modified to continue operating as originally designed. One case of this is the result of the hardware and software end of life policy that states that no hardware or software can remain in production without vendor support, or in the case of open source software, community support. Here the software may need to be updated in order to continue operation without regression. At a minimum this would require rigorous testing to ensure no regression, at the most complex it may require updating code to use new versions of libraries or in some cases to replace supporting software and libraries with alternatives. In other cases sustainment may involve making updates to backend databases either directly or through custom tools. Managing users and roles, updating reference data and validating and fixing data loads all fall into this category. Additionally the sustainment team will be expected to validate software that transitions into the sustainment portfolio from all ITAC development contracts and escalate to the government any deficiencies in code and suggests potential remediations. Finally, the software portfolio must maintain the appropriate security documentation to ensure the relevant Authorities to Operate (ATO) remain valid and in compliance with policy, standards and regulations. The NHLBI categorizes these sustainment activities into the categories which include (but is not limited to): • Corrective Maintenance • Adaptive Maintenance • Preventative Maintenance • Application Operations Support • Transition Support • System Assessment and Authorization To maintain a dependable and well-functioning IT maintenance support environment, it is important that resources are ready and available to support outages, emergencies, and application deployments, as necessary. Resolving outages, emergencies, and application deployments may require 24 x 7 support, which would entail having resources available beyond typical business hours during the week and on weekends. The government intends the Sustainment contractor to provide an evaluation of software applications in the Sustainment portfolio to include but not limited to assessment of performance, code quality and security. This role will be particularly critical as software transitions from active development into the sustainment portfolio and the software must be evaluated against a set of acceptance criteria. Therefore, the sustainment functions requires separation from the development teams and appropriate checks and balances to ensure the integrity of the process.