Common use of Project Status Clause in Contracts

Project Status. The Contractor shall submit a bi-weekly report for orders having an estimated cost or fixed price in excess of $250,000 unless otherwise specified in the order. The status report shall contain at a minimum the: * Estimated baseline costs compared to actual costs, * Actual performance versus scheduled performance, 0 Changes to order specific metrics and; 0 Any problems or issues that may result in a schedule delay or cost overrun; This report shall be submitted to the Contracting Officer, the Project Officer, and the specific technical monitor for each order. One copy of a summary report which rolls up all the individual order data shall be submitted to the Contracting Officer and the Project Officer. Notwithstanding the reporting requirement, the Contractor shall notify the Contracting Officer, the Project Officer, and the specific technical monitor for any order when a schedule slip or cost overrun is projected. The NRC may require the Contractor to use an NRC generated format or may accept a proposed Contractor format that, will be determined on an order specific basis. A.11 PROJECT OFFICER The Contracting Officer's authorized technical representative hereinafter referred to as the project officer for this BPA is: Name: Xxxxx Xxxxxxx Address: U.S. Nuclear Regulatory Commission Mail Stop T-6F1 5 Washington, DC 20555 Telephone Number: (000) 000-0000 a. Performance of the work under this BPA is subject to the technical direction of the NRC project officer. The term "technical direction" is defined to include the following: 1. Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work or changes to specific travel identified in the Statement of Work), fills in details, or otherwise serves to accomplish the contractual statement of work. 2. Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description. 3. Review and, where required by the BPA, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the BPA. b. Technical direction must be within the general statement of work stated in the BPA. The project officer does not have the authority to and may not issue any technical direction which: 1. Constitutes an assignment of work outside the general scope of the BPA or associated orders. 2. Constitutes a change as defined in the "Changes" clause of the GSA contract. 3. In any way causes an increase or decrease in the total fixed price or the time required for performance of any orders. 4. Changes any of the expressed terms, conditions, or specifications of The BPA or associated orders. 5. Terminates the BPA, settles any claim or dispute arising under the BPA, or issues any unilateral directive whatever. c. All technical directions must be issued in writing by the project officer or must be confirmed by the project officer in writing within ten (14) working days after verbal issuance. A copy of the written direction must be furnished to the CO. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the CO. d. The contractor shall proceed promptly with the performance of technical directions duly issued by the project officer in the manner prescribed by this clause and within the project officer's authority under the provisions of this clause. e. If, in the opinion of the contractor, any instruction or direction issued by the project officer is within one of the categories as defined in paragraph (c) of this section, the contractor may not proceed but shall notify the CO in writing within five (5) working days after the receipt of any instruction or direction and shall request the CO to modify the BPA or associated order accordingly. Upon receiving the notification from the contractor, the CO shall issue an appropriate modification or advise the contractor in writing that, in the CO's opinion, the technical direction is within the scope of this article and does not constitute a change under the "Changes" clause. f. Any unauthorized commitment or direction issued by the project officer may result in an unnecessary delay in the contractor's performance and may even result in the contractor expending funds for unallowable costs under the BPA or associated order. g. A failure of the parties to agree upon the nature of the instruction or direction or upon the contract action to be taken with respect thereto is subject to 52.233-1 - Disputes. h. In addition to providing technical direction as defined in paragraph (b) of the section, the project officer shall: 1. Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the CO changes in requirements. 2. Assist the contractor in the resolution of technical problems encountered during performance. 3. Review all costs requested for reimbursement by the contractor and submit to the CO recommendations for approval, disapproval, or suspension of payment for supplies and services required under orders associated with this BPA. 4. Assist the contractor in obtaining the badges for the contractor personnel. 5. Immediately notify the Personnel Security Branch, Division of Facilities and Security (PERSEC/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return the individual's badge to PERSEC/DFS within three days after their termination. a. Contractors shall submit invoices in accordance with the schedule specified in each order up to the established price ceiling. b. Contractors shall provide the following detailed information with each invoice, unless otherwise specified in the order. 1. Each invoice will clearly define all costs by order. Costs by order will be further identified by system/project and for each system/project, costs will be identified by major categories of work performed, i.e. maintenance, system development, administrative, and purchases of equipment and software. Major categories of work will be defined for each order. This information will provide a reconciliation of costs for all orders and will facilitate reporting requirements. 2. Labor data for each order will include hours worked and associated costs by labor category. 3. All burdened cost presentations provided by the Contractor shall be inclusive of; overhead charges, other direct costs, (i.e., local travel, copying, supplies, phone, delivery, temporary secretarial support, etc.), general and administrative charges, and Contractor fee. Burdened costs will be clearly identified and separated on the invoice by system/project and for each major category of work performed for each system/project. 4. Invoices will provide a compilation of costs on a monthly, year to date, and total project basis. c. Fixed price or performance based orders shall provide details of the line items as specified in each order. d. Regardless of the type of order issued, any incentives shall be invoiced separately. e. Three Phases of System Development Invoices must distinguish development costs by three phases of systems development: 1. The preliminarydesignphase (SDLCM components 1 - 3) includes determining system performance requirements; system specifications; and demonstrating software alternatives. Generally, activities leading up to the selection of software and/or proceeding with the next (development) phase. 2. The developmentphase (SDLCM components 4 & 5) includes designing software configurations and interfaces; coding; installing on hardware; and, testing software including parallel processing. 3. The post-implementation'operationapl hase (SDLCM components 6 & 7) includes converting data from the old to the new system; operating the software; providing ongoing training; undertaking preventive maintenance; and, developing/executing reports. Contractors shall consult with the project officer if there is any question-as to which project phase costs should be classified as on the invoice.

Appears in 1 contract

Samples: Contract

AutoNDA by SimpleDocs

Project Status. The Contractor shall submit a bi-weekly report for orders having an estimated cost or fixed price in excess of $250,000 unless otherwise specified in the order. The status report shall contain at a minimum the: * 0 Estimated baseline costs compared to actual costs, * Actual performance versus scheduled performance, 0 a Changes to order specific metrics and; 0 a Any problems or issues that may result in a schedule delay or cost overrun; This report shall be submitted to the Contracting Officer, the Project Officer, and the specific technical monitor for each order. One copy of a summary report which rolls up all the individual order data shall be submitted to the Contracting Officer and the Project Officer. Notwithstanding the reporting requirement, the Contractor shall notify the Contracting Officer, the Project Officer, and the specific technical monitor for any order when a schedule slip or cost overrun is projected. The NRC may require the Contractor to use an NRC generated format or may accept a proposed Contractor format that, will be determined on an order specific basis. A.11 PROJECT OFFICER The Contracting Officer's authorized technical representative hereinafter referred to as the project officer for this BPA is: Name: Xxxxx Xxxxxxx Xxx Xxxxxx Address: U.S. Nuclear Regulatory Commission Mail Stop T-6F1 5 9 Washington, DC 20555 Telephone Number: (000) 000-0000 a. Performance of the work under this BPA is subject to the technical direction of the NRC project officer. The term "technical direction" is defined to include the following: 1. Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work or changes to specific travel identified in the Statement of Work), fills in details, or otherwise serves to accomplish the contractual statement of work. 2. Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description. 3. Review and, where required by the BPA, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the BPA. b. Technical direction must be within the general statement of work stated in the BPA. The project officer does not have the authority to and may not issue any technical direction which: 1. Constitutes an assignment of work outside the general scope of the BPA or associated orders. 2. Constitutes a change as defined in the "Changes" clause of the GSA contract. 3. In any way causes an increase or decrease in the total fixed price or the time required for performance of any orders. 4. Changes any of the expressed terms, conditions, or specifications of The the BPA or associated orders. 5. Terminates the BPA, settles any claim or dispute arising under the BPA, or issues any unilateral directive whatever. c. All technical directions must be issued in writing by the project officer or must be confirmed by the project officer officer-in writing within ten (14) working days after verbal issuance. A copy of the written direction must be furnished to the CO. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the CO. d. The contractor shall proceed promptly with the performance of technical directions duly issued by the project officer in the manner prescribed by this clause and within the project officer's authority under the provisions of this clause. e. If, in the opinion of the contractor, any instruction or direction issued by the project officer is within one of the categories as defined in paragraph (c) of this section, the contractor may not proceed but shall notify the CO in writing within five (5) working days after the receipt of any instruction or direction and shall request the CO to modify the BPA or associated order accordingly. Upon receiving the notification from the contractor, the CO shall issue an appropriate modification or advise the contractor in writing that, in the CO's opinion, the technical direction is within the scope of this article and does not constitute a change under the "Changes" clause. f. Any unauthorized commitment or direction issued by the project officer may result in an unnecessary delay in the contractor's performance and may even result in the contractor expending funds for unallowable costs under the BPA or associated order. g. A failure of the parties to agree upon the nature of the instruction or direction or upon the contract action to be taken with respect thereto is subject to 52.233-1 - Disputes. h. In addition Inaddition to providing technical direction as defined in paragraph (b) of the section, the project officer shall: 1. Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the CO changes in requirements. 2. Assist the contractor in the resolution of technical problems encountered during performance. 3. Review all costs requested for reimbursement by the contractor and submit to the CO recommendations for approval, disapproval, or suspension of payment for supplies and services required under orders associated with this BPA. 4. Assist the contractor in obtaining the badges for the contractor personnel. 5. Immediately notify the Personnel Security Branch, Division of Facilities and Security (PERSEC/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return the individual's badge to PERSEC/DFS within three days after their termination. a. Contractors shall submit invoices in accordance with the schedule specified in each order up to the established price ceiling. b. Contractors shall provide the following detailed information with each invoice, unless otherwise specified in the order. 1. Each invoice will clearly define all costs by order. Costs by order will be further identified by system/project and for each system/project, costs will be identified by major categories of work performed, i.e. maintenance, system development, administrative, and purchases of equipment and software. Major categories of work will be defined for each order. This information will provide a reconciliation of costs for all orders and will facilitate reporting requirements. 2. Labor data for each order will include hours worked and associated costs by labor category. 3. All burdened cost presentations provided by the Contractor shall be inclusive of; overhead charges, other direct costs, (i.e., local travel, copying, supplies, phone, delivery, temporary secretarial support, etc.), general and administrative charges, and Contractor fee. Burdened costs will be clearly identified and separated on the invoice by system/project and for each major category of work performed for each system/project. 4. Invoices will provide a compilation of costs on a monthly, year to date, and total project basis. c. Fixed price or performance based orders shall provide details of the line items as specified in each order. d. Regardless of the type of order issued, any incentives shall be invoiced separately. e. Three Phases of System Development Invoices must distinguish development costs by three phases of systems development: 1. The preliminarydesignphase (SDLCM components 1 - 3) includes determining system performance requirements; system specifications; and demonstrating software alternatives. Generally, activities leading up to the selection of software and/or proceeding with the next (development) phase. 2. The developmentphase (SDLCM components 4 & 5) includes designing software configurations and interfaces; coding; installing on hardware; and, testing software including parallel processing. 3. The post-implementation'operationapl hase (SDLCM components 6 & 7) includes converting data from the old to the new system; operating the software; providing ongoing training; undertaking preventive maintenance; and, developing/executing reports. Contractors shall consult with the project officer if there is any question-as to which project phase costs should be classified as on the invoice.

Appears in 1 contract

Samples: Contract

Project Status. The Contractor shall submit a bi-weekly report for orders having an estimated cost or fixed price in excess of $250,000 unless otherwise specified in the order. The status report shall contain at a minimum the: * ° Estimated baseline costs compared to actual costs, * Actual performance versus scheduled performance, 0 Changes to order specific metrics and; 0 Any problems or issues that may result in a schedule delay or cost overrun; This report shall be submitted to the Contracting Officer, the Project Officer, and the specific technical monitor for each order. One copy of a summary report which rolls up all the individual order data shall be submitted to the Contracting Officer and the Project Officer. Notwithstanding the reporting requirement, the Contractor shall notify the Contracting Officer, the Project Officer, and the specific technical monitor for any order when a schedule slip or cost overrun is projected. The NRC may require the Contractor to use an NRC generated format or may accept a proposed Contractor format that, will be determined on an order specific basis. A.11 . A.1 1 PROJECT OFFICER -t_ The Contracting Officer's authorized technical representative hereinafter referred to as the project officer for this BPA is: Name: Xxxxx Xxxxxxx Xxx Xxxxxx Address: U.S. Nuclear Regulatory Commission Mail Stop T-6F1 5 9 Washington, DC 20555 Telephone Number: (000) 000-0000 a. Performance of the work under this BPA is subject to the technical direction of the NRC project officer. The term "technical direction" is defined to include the following: 1. Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work or changes to specific travel identified in the Statement of Work), fills in details, or otherwise serves to accomplish the contractual statement of work. 2. Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description. 3. Review and, where required by the BPA, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the BPA. b. Technical direction must be within the general statement of work stated in the BPA. The project officer does not have the authority to and may not issue any technical direction which: 1. Constitutes an assignment of work outside the general scope of the BPA or associated orders. 2. Constitutes a change as defined in the "Changes" clause of the GSA contract. 3. In any way causes an increase or decrease in the total fixed price or the time required for performance of any orders. 4. Changes any of the expressed terms, conditions, or specifications of The the BPA or associated orders. 5. Terminates the BPA, settles any claim or dispute arising under the BPA, or issues any unilateral directive whatever. c. All technical directions must be issued in writing by the project officer or must be confirmed by the project officer in writing within ten (14) working days after verbal issuance. A copy of the written direction must be furnished to the CO. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the CO. d. The contractor shall proceed promptly with the performance of technical directions duly issued by the project officer in the manner prescribed by this clause and within the project officer's authority under the provisions of this clause. e. If, in the opinion of the contractor, any instruction or direction issued by the project officer is within one of the categories as defined in paragraph (c) of this section, the contractor may not proceed but shall notify the CO in writing within five (5) working days after the receipt of any instruction or direction and shall request the CO to modify the BPA or associated order accordingly. Upon receiving the notification from the contractor, the CO shall issue an appropriate modification or advise the contractor in writing that, in the CO's opinion, the technical direction is within the scope of this article and does not constitute a change under the "Changes" clause. f. Any unauthorized commitment or direction issued by the project officer may result in an unnecessary delay in the contractor's performance and may even result in the contractor expending funds for unallowable costs under the BPA or associated order. g. A failure of the parties to agree upon the nature of the instruction or direction or upon the contract action to be taken with respect thereto is subject to 52.233-1 - Disputes. h. In addition to providing technical direction as defined in paragraph (b) of the section, the project officer shall: 1. Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the CO changes in requirements. 2. Assist the contractor in the resolution of technical problems encountered during performance. 3. Review all costs requested for reimbursement by the contractor and submit to the CO recommendations for approval, disapproval, or suspension of payment for supplies and services required under orders associated with this BPA. 4. Assist the contractor in obtaining the badges for the contractor personnel. 5. Immediately notify the Personnel Security Branch, Division of Facilities and Security (PERSEC/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return the individual's badge to PERSEC/DFS within three days after their termination.. A.12 INVOICE SUBMISSION a. Contractors shall submit invoices in accordance with the schedule specified in each order up to the established price ceiling. b. Contractors shall provide the following detailed information with each invoice, unless otherwise specified in the order. 1. Each invoice will clearly define all costs by order. Costs by order will be further identified by system/project and for each system/project, costs will be identified by major categories of work performed, i.e. maintenance, system development, administrative, and purchases of equipment and software. Major categories of work will be defined for each order. This information will provide a reconciliation of costs for all orders and will facilitate reporting requirements. 2. Labor data for each order will include hours worked and associated costs by labor category. 3. All burdened cost presentations provided by the Contractor shall be inclusive of; overhead charges, other direct costs, (i.e., local travel, copying, supplies, phone, delivery, temporary secretarial support, etc.), general and administrative charges, and Contractor fee. Burdened costs will be clearly identified and separated on the invoice by system/project and for each major category of work performed for each system/project. 4. Invoices will provide a compilation of costs on a monthly, year to date, and total project basis. c. Fixed price or performance based orders shall provide details of the line items as specified in each order. d. Regardless of the type of order issued, any incentives shall be invoiced separately. e. Three Phases of System Development Invoices must distinguish development costs by three phases of systems development: 1. The preliminarydesignphase (SDLCM components 1 - 3) includes determining system performance requirements; system specifications; and demonstrating software alternatives. Generally, activities leading up to the selection of software and/or proceeding with the next (development) phase. 2. The developmentphase (SDLCM components 4 & 5) includes designing software configurations and interfaces; coding; installing on hardware; and, testing software including parallel processing. 3. The post-implementation'operationapl hase (SDLCM components 6 & 7) includes converting data from the old to the new system; operating the software; providing ongoing training; undertaking preventive maintenance; and, developing/executing reports. Contractors shall consult with the project officer if there is any question-as to which project phase costs should be classified as on the invoice.

Appears in 1 contract

Samples: Contract

AutoNDA by SimpleDocs

Project Status. The Contractor shall submit a bi-weekly report for orders having an estimated cost or fixed price in excess of $250,000 unless otherwise specified in the order. The status report shall contain at a minimum the: * Estimated baseline costs compared to actual costs, * Actual performance versus scheduled performance, 0 Changes to order specific metrics and; 0 Any problems or issues that may result in a schedule delay or cost overrun; This report shall be submitted to the Contracting Officer, the Project Officer, and the specific technical monitor for each order. One copy of a summary report which rolls up all the individual order data shall be submitted to the Contracting Officer and the Project Officer. Notwithstanding the reporting requirement, the Contractor shall notify the Contracting Officer, the Project Officer, and the specific technical monitor for any order when a schedule slip or cost overrun is projected. The NRC may require the Contractor to use an NRC generated format or may accept a proposed Contractor format that, will be determined on an order specific basis. A.11 PROJECT OFFICER The Contracting Officer's authorized technical representative hereinafter referred to as the project officer for this BPA is: Name: Xxxxx Xxxxxxx Xxxxxxxx Xxxxxxxx Address: U.S. Nuclear Regulatory Commission Mail Stop T-6F1 5 T-6D2 Washington, DC 20555 Telephone Number: (000) 000-0000 a. Performance of the work under this BPA is subject to the technical direction of the NRC project officer. The term "technical direction" is defined to include the following: 1. Technical direction to the contractor which shifts work emphasis between areas of work or tasks, authorizes travel which was unanticipated in the Schedule (i.e., travel not contemplated in the Statement of Work or changes to specific travel identified in the Statement of Work), fills in details, or otherwise serves to accomplish the contractual statement of work. 2. Provide advice and guidance to the contractor in the preparation of drawings, specifications, or technical portions of the work description. 3. Review and, where required by the BPA, approval of technical reports, drawings, specifications, and technical information to be delivered by the contractor to the Government under the BPA. b. Technical direction must be within the general statement of work stated in the BPA. The project officer does not have the authority to and may not issue any technical direction which: 1. Constitutes an assignment of work outside the general scope of the BPA or associated orders. 2. Constitutes a change as defined in the "Changes" clause of the GSA contract. 3. In any way causes an increase or decrease in the total fixed price or the time required for performance of any orders. 4. Changes any of the expressed terms, conditions, or specifications of The the BPA or associated orders. 5. Terminates the BPA, settles any claim or dispute arising under the BPA, or issues any unilateral directive whatever. c. All technical directions must be issued in writing by the project officer or must be confirmed by the project officer in writing within ten (14) working days after verbal issuance. A copy of the written direction must be furnished to the CO. A copy of NRC Form 445, Request for Approval of Official Foreign Travel, which has received final approval from the NRC must be furnished to the CO. d. The contractor shall proceed promptly with the performance of technical directions duly issued by the project officer in the manner prescribed by this clause and within the project officer's authority under the provisions of this clause. e. If, in the opinion of the contractor, any instruction or direction issued by the project officer is within one of the categories as defined in paragraph (c) of this section, the contractor may not proceed but shall notify the CO in writing within five (5) working days after the receipt of any instruction or direction and shall request the CO to modify the BPA or associated order accordingly. Upon receiving the notification from the contractor, the CO shall issue an appropriate modification or advise the contractor in writing that, in the CO's opinion, the technical direction is within the scope of this article and does not constitute a change under the "Changes" clause. f. Any unauthorized commitment or direction issued by the project officer may result in an unnecessary delay in the contractor's performance and may even result in the contractor expending funds for unallowable costs under the BPA or associated order. g. A failure of the parties to agree upon the nature of the instruction or direction or upon the contract action to be taken with respect thereto is subject to 52.233-1 - Disputes. h. In addition to providing technical direction as defined in paragraph (b) of the section, the project officer shall: 1. Monitor the contractor's technical progress, including surveillance and assessment of performance, and recommend to the CO changes in requirements. 2. Assist the contractor in the resolution of technical problems encountered during performance. 3. Review all costs requested for reimbursement by the contractor and submit to the CO recommendations for approval, disapproval, or suspension of payment for supplies and services required under orders associated with this BPA. 4. Assist the contractor in obtaining the badges for the contractor personnel. 5. Immediately notify the Personnel Security Branch, Division of Facilities and Security (PERSEC/DFS) (via e-mail) when a contractor employee no longer requires access authorization and return the individual's badge to PERSEC/DFS within three days after their termination. a. Contractors shall submit invoices in accordance with the schedule specified in each order up to the established price ceiling. b. Contractors shall provide the following detailed information with each invoice, unless otherwise specified in the order. 1. Each invoice will clearly define all costs by order. Costs by order will be further identified by system/project and for each system/project, costs will be identified by major categories of work performed, i.e. maintenance, system development, administrative, and purchases of equipment and software. Major categories of work will be defined for each order. This information will provide a reconciliation of costs for all orders and will facilitate reporting requirements. 2. Labor data for each order will include hours worked and associated costs by labor category. 3. All burdened cost presentations provided by the Contractor shall be inclusive of; overhead charges, other direct costs, (i.e., local travel, copying, supplies, phone, delivery, temporary secretarial support, etc.), general and administrative charges, and Contractor fee. Burdened costs will be clearly identified and separated on the invoice by system/project and for each major category of work performed for each system/project. 4. Invoices will provide a compilation of costs on a monthly, year to date, and total project basis. c. Fixed price or performance based orders shall provide details of the line items as specified in each order. d. Regardless of the type of order issued, any incentives shall be invoiced separately. e. Three Phases of System Development Invoices must distinguish development costs by three phases of systems development: 1. The preliminarydesignphase (SDLCM components 1 - 3) includes determining system performance requirements; system specifications; and demonstrating software alternatives. Generally, activities leading up to the selection of software and/or proceeding with the next (development) phase. 2. The developmentphase (SDLCM components 4 & 5) includes designing software configurations and interfaces; coding; installing on hardware; and, testing software including parallel processing. 3. The post-implementation'operationapl hase (SDLCM components 6 & 7) includes converting data from the old to the new system; operating the software; providing ongoing training; undertaking preventive maintenance; and, developing/executing reports. Contractors shall consult with the project officer if there is any question-as to which project phase costs should be classified as on the invoice.

Appears in 1 contract

Samples: Contract

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!