Common use of Status Reporting Clause in Contracts

Status Reporting. All contractors who receive orders shall provide biweekly status reports that describe progress-to-date at order and CLIN levels. At a minimum, biweekly status reports shall include accomplishments during the current reporting period, accomplishments planned for the next reporting period and any issues affecting progress or performance capability. In addition, biweekly status reports shall address each of the following areas, as applicable to each reporting occasion: Costs: staff hours and funds expended per biweekly period, per order, per CLIN, and per application system (identification number, acronym and title). This information shall be rolled up into monthly, quarterly, semi-annual, and annual usage. * Schedule information * Identification of program, order, and CLIN managers and other key personnel and all changes to these personnel • Status of each order and CLIN * Plans and recommendations for future priorities and activation of work items * Program, order, and CLIN impact (positive or negative) on the NRC IT infrastructure (e.g., WAN/LAN operations and capacity, communications, configuration management) • Requirements traceability * Assessment of progress toward enterprise integration • Quality assurance activity * Configuration management activity All contractors who receive orders shall be required to input data into the CISSCO Task Assignment and Control System (CTACS). The data to be entered is general tracking and cost data such as date received, amount, date submitted to NRC, etc, and shall be entered into CTACS within 2 work days of the associated event occurring.

Status Reporting. All contractors who receive orders shall provide biweekly status reports that describe progress-to-date at order and CLIN levels. At a minimum, biweekly status reports shall include accomplishments during the current reporting period, accomplishments planned for the next reporting period and any issues affecting progress or performance capability. In addition, biweekly status reports shall address each of the following areas, as applicable to each reporting occasion: Costs: staff hours and funds expended per biweekly period, per order, per CLIN, and per application system (identification number, acronym and title). This information shall be rolled up into monthly, quarterly, semi-annual, and annual usage. * • Schedule information * Identification of program, order, and CLIN managers and other key personnel and all changes to these personnel • * Status of each order and CLIN * Plans and recommendations for future priorities and activation of work items * Program, order, and CLIN impact (positive or negative) on the NRC IT infrastructure (e.g., WAN/LAN operations and capacity, communications, configuration management) • * Requirements traceability * Assessment of progress toward enterprise integration • Quality assurance activity * • Configuration management activity All contractors who receive orders shall be required to input data into the CISSCO Task Assignment and Control System (CTACS). The data to be entered is general tracking and cost data such as date received, amount, date submitted to NRC, etc, and shall be entered into CTACS within 2 work days of the associated event occurring.

Status Reporting. All contractors who receive orders shall provide biweekly status reports that describe progress-to-date at order and CLIN levels. At a minimum, biweekly status reports shall include accomplishments during the current reporting period, accomplishments planned for the next reporting period and any issues affecting progress or performance capability. In addition, biweekly status reports shall address each of the following areas, as applicable to each reporting occasion: Costs: staff hours and funds expended per biweekly period, per order, per CLIN, and per application system (identification number, acronym and title). This information shall be rolled up into monthly, quarterly, semi-annual, and annual usage. * Schedule information * • Identification of program, order, and CLIN managers and other key personnel and all changes to these personnel • "* Status of each order and CLIN "* Plans and recommendations for future priorities and activation of work items * ° Program, order, and CLIN impact (positive or negative) on the NRC IT infrastructure (e.g., WAN/LAN operations and capacity, communications, configuration management) • * Requirements traceability * • Assessment of progress toward enterprise integration • * Quality assurance activity * Configuration management activity All contractors who receive orders shall be required to input data into the CISSCO Task Assignment and Control System (CTACS). The data to be entered is general tracking and cost data such as date received, amount, date submitted to NRC, etc, and shall be entered into CTACS within 2 work days of the associated event occurring.

Status Reporting. All contractors who receive orders shall provide biweekly status reports that describe progress-to-date at order and CLIN levels. At a minimum, biweekly status reports shall include accomplishments during the current reporting period, accomplishments planned for the next reporting period and any issues affecting progress or performance capability. In addition, biweekly status reports shall address each of the following areas, as applicable to each reporting occasion: Costs: staff hours and funds expended per biweekly period, per order, per CLIN, and per application system (identification number, acronym and title). This information shall be rolled up into monthly, quarterly, semi-annual, and annual usage. * Schedule information * ° Identification of program, order, and CLIN managers and other key personnel and all changes to these personnel • * Status of each order and CLIN * Plans and recommendations for future priorities and activation of work items * Program, order, and CLIN impact (positive or negative) on the NRC IT infrastructure (e.g., WAN/LAN operations and capacity, communications, configuration management) • Requirements traceability * • Assessment of progress toward enterprise integration • * Quality assurance activity * Configuration management activity All contractors who receive orders shall be required to input data into the CISSCO Task Assignment and Control System (CTACS). The data to be entered is general tracking and cost data such as date received, amount, date submitted to NRC, etc, and shall be entered into CTACS within 2 work days of the associated event occurring.

Status Reporting. All contractors who receive orders shall provide biweekly status reports that describe progress-to-date at order and CLIN levels. At a minimum, biweekly status reports shall include accomplishments during the current reporting period, accomplishments planned for the next reporting period and any issues affecting progress or performance capability. In addition, biweekly status reports shall address each of the following areas, as applicable to each reporting occasion: Costs: staff hours and funds expended per biweekly period, per order, per CLIN, and per application system (identification number, acronym and title). This information shall be rolled up into monthly, quarterly, semi-annual, and annual usage. * Schedule information * Identification of program, order, and CLIN managers and other key personnel and all changes to these personnel • Status of each order and CLIN * • Plans and recommendations for future priorities and activation of work items * Program, order, and CLIN impact (positive or negative) on the NRC IT infrastructure (e.g., WAN/LAN operations and capacity, communications, configuration management) • * Requirements traceability * Assessment of progress toward enterprise integration • Quality assurance activity * • Configuration management activity All contractors who receive orders shall be required to input data into the CISSCO Task Assignment and Control System (CTACS). The data to be entered is general tracking and cost data such as date received, amount, date submitted to NRC, etc, and shall be entered into CTACS within 2 work days of the associated event occurring.