cascading effect on existing NAS capabilities, and therefore the Requirement requirements associated with these investments may have a consolidates significant set of CPRs. existing functionality Duplication of functionality may or may not result in identification of CPRs. A program whose business case depends on having Requirement redundant or duplicate systems, may want to consider identifying removes existing duplicate functionality requirements as CPRs. However, merely functionality having duplicate functionality requirements without a strong business is not a strong indicator for having CPRs. Requirement duplicates existing New functions are often critical to a business case. If program’s functionality the requirement provides a new capability, consider it for CPR designation; however, just because a requirement is new, it does not mean that it is necessarily a CPR. (E.g., a function to turn off nuisance alarms benefits controllers, but is not critical to the program). Requirement Not all CPRs are new functions to the agency. The purpose of improves existing some investments is to enhance existing capabilities (e.g. via a function Tech Refresh). If the benefits for the program are tied to those performance improvements, then those performance requirements could be CPRs. Requirement Safe movement of aircraft is a primary mission of the agency. A affects NAS safety requirement that directly affects NAS safety is a candidate for CPR status. Requirement Information security is critically important to the FAA. A affects NAS requirement that directly contributes to Information security is a Information candidate for CPR status. Security Requirement has a Functionality is not the only characteristic of a program that can direct effect on an be critical. Interface requirements often enable the significant external interface benefits of a program. If an interface requirement is necessary to provide the benefits of the program, heavily consider the requirement as a candidate for CPR status. Examples of these can include addition, modification, removal, or consolidation of cables between two systems. Given the criteria outlined in Tables 2 and 3, it may be necessary to use an objective means to determine which requirements are critical to the investment. Section 4.6 Decision Analysis (in the SEM) outlines several methods for doing this. Document the means and the results for determining the CPRs in this appendix or the VRTM.
cascading effect on existing NAS capabilities, and therefore the requirements associated with these investments may have a significant set of CPRs. Duplication of functionality may or may not result in identification of CPRs. A program whose business case depends on having redundant or duplicate systems, may want to consider identifying duplicate functionality requirements as CPRs. However, merely having duplicate functionality requirements without a strong business is not a strong indicator for having CPRs. New functions are often critical to a program’s business case. If the requirement provides a new capability, consider it for CPR designation; however, just because a requirement is new, it does not mean that it is necessarily a CPR. (E.g., a function to turn off nuisance alarms benefits controllers, but is not critical to the program). Requirement consolidates existing functionality Requirement removes existing functionality Requirement duplicates existing functionality Requirement improves existing function performance Not all CPRs are new functions to the agency. The purpose of some investments is to enhance existing capabilities (e.g. via a Tech Refresh). If the benefits for the program are tied to those improvements, then those performance requirements could be CPRs. Requirement affects NAS safety Safe movement of aircraft is a primary mission of the agency. A requirement that directly affects NAS safety is a candidate for CPR status. Requirement affects NAS Information Security Information security is critically important to the FAA. A requirement that directly contributes to Information security is a candidate for CPR status. Requirement has a direct effect on an external interface Functionality is not the only characteristic of a program that can be critical. Interface requirements often enable the significant benefits of a program. If an interface requirement is necessary to provide the benefits of the program, heavily consider the requirement as a candidate for CPR status. Examples of these can include addition, modification, removal, or consolidation of cables between two systems. Given the criteria outlined in Tables 2 and 3, it may be necessary to use an objective means to determine which requirements are critical to the investment. Section 4.6 Decision Analysis (in the SEM) outlines several methods for doing this. Document the means and the results for determining the CPRs in this appendix or the VRTM.
programreq.docx