This page provides details of the selected work element.
SOWRevision | Planned | Updated | Contractor Comments (optional) | BPA Comments (optional) |
---|---|---|---|---|
1. 67971 (02/01/2015 - 01/31/2016) | $127,621 | $127,626 | ||
Work Element Budget (Current Performance Period) | $127,626 | $127,626 |
Sort | Type | Title | Start | End | Status | Modified By | Modified Date |
---|---|---|---|---|---|---|---|
A | DELIV | All BPA Contract Documents | 2/13/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM | |
Description: FY15 Pisces SOW, Excel budget (with sub-contractor budgets if applicable), Property Inventory, and FY14 September Accruals (work performed but not invoiced by 9/30/2014). | |||||||
B | FISMA1 | Attach initial FISMA Compliance Attestation (BPA risk category Low) | 2/1/2015 | 1/15/2016 | Concluded | David Byrnes (Inactive) | 8/5/2015 10:28:43 AM |
Description: BPA contractors are required to protect their data and electronic systems consistent with the federal FISMA law (Federal Information Security Management Act of 2002). Your contract has been rated as low risk by BPA Cyber Security. The designated signatory for your organization may vary. Check with your COTR to see if BPA has already obtained, or will soon obtain through previous contracts, the attestation. If not, please work with your COTR to obtain a signed attestation confirming your organizations compliance with FISMA. Attestations can be in the form of a formal memorandum, letter, or email. An email will need to be cut and pasted into a word processing program. All attachments must be saved and uploaded as PDF. A sample attestation communication that describes the minimum information required can be found as a Pisces attachment at {https://pisces.bpa.gov/release/documents/DocumentViewer.aspx?doc=P137862}. Upload the attestation to Pisces under the new FISMA Attestation File Type, and type in the title as Low-risk FISMA attestation. This milestone is considered complete when the contractor has uploaded an electronic copy of a signed attestation. Deadline: Start and end dates are both the first day of the contract. | |||||||
C | DraftNew | Begin drafting contract renewal documents and conduct internal review as needed | 8/1/2015 | 9/1/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Your statement of work, line-item budget, and (if required) property inventory for your next contract are due to BPA at least 5 months prior to the contract start date (longer if your internal processes require more time to get the contract signed and in place prior to the start date). | |||||||
D | FISMA2 | Confirm that FISMA compliance documentation for any subsequent contract is current | 9/1/2015 | 9/30/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Contact your COTR and check in Pisces to confirm that the FISMA compliance documentation for your subsequent contact is still current. If not, work with COTR to update documentation. (Due 125 days before the contract end date). BPA contractors are required to protect their data and electronic systems consistent with the federal FISMA law (Federal Information Security Management Act of 2002). Your contract will be rated as low risk by BPA Cyber Security. | |||||||
E | Submit | Submit contract renewal package (SOW, Excel budget, property inventory) to BPA COTR | 10/1/2015 | 10/16/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Once your statement of work (SOW) in Pisces is complete, and you have attached your line-item budget (LIB) and property inventory (PI) (if required), click the “Submit” button on the SOW tab to notify your COTR the package is ready for review. | |||||||
F | FixCmts | Address comments and revise SOW, LIB, and PI as needed to get BPA manager approval | 11/1/2015 | 11/13/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Once your COTR and his or her BPA manager have reviewed your contract renewal package and returned any comments to you, you will need to provide responses and changes as needed to achieve approval from the BPA manager, who will then forward the package to the Contracting Officer. This should be completed at least two months prior to the next contract start date, but may need to be 3 or 4 months depending on your internal processing time for contract signatures. If you have subcontracts that need to be signed prior to the contract start, it should be a minimum of 4 months. | |||||||
G | Sign&Rtrn | Return signed contract to BPA’s Contracting Officer within 30 days | 11/30/2015 | 12/18/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Respond to the CO and COTR indicating any problems with the contract within 20 days, or return the signed contract to the BPA Contracting Officer (CO) within 30 days. | |||||||
H | FinInv01 | Submit final invoice for prior contract within 90 days to facilitate contract closeout | 4/1/2015 | 4/30/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Within 90 days of the last day of the PRIOR contract, the contractor shall issue a final invoice. In instances where more than 90 days is needed (e.g., because subcontractors have not invoiced), the contractor shall: 1. review records, 2. estimate all outstanding costs, and 3. provide BPA with a single, cumulative estimate of all completed, but uninvoiced work. This amount shall be emailed to FWinvoices@bpa.gov and the COTR. | |||||||
I | ACCR01 | Accrual - Submit September estimate to BPA | 8/10/2015 | 9/10/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: Provide BPA with an estimate of contract work that will occur prior to September 30 but will not be billed until October 1 or later. Data must be input in to Pisces by September 10 (begins Aug 10, ends Sep 10). | |||||||
J | CostSh01 | Facilitate inputting Cost Share information into Pisces at the Project level | 9/30/2015 | 11/1/2015 | Concluded | David Byrnes (Inactive) | 4/7/2015 1:07:38 PM |
Description: There are multiple contractors under this project, and I am not the lead project Proponent. I will email federal FY Cost Share information for my contract to the lead project Proponent by Nov 1. |