J-07 FS3i CDRLs 1423_REV_3.2.docx
DOCX document 474 KB Posted
- Solicitation number
- HM0476_20260105
About this file
This is a Contract Data Requirements List (CDRL) document for the Foundation Sustainment Support, Software and Integration (FS3i) contract. The document defines 49 contract data requirement items (CDRLs) that contractors must deliver throughout the contract lifecycle, organized by functional area including program management, agile development, security, quality assurance, testing, operations support, and sustainment activities. Each CDRL entry specifies the data item number, title, delivery frequency, first submission date, subsequent submission dates, format requirements, and detailed content specifications. Key deliverables include management plans (Program Management Plan, Agile Development Management Plan, Risk Management Plan, Configuration Management Plan), monthly status reports (Contract Funds Status Report, End of Sprint Status Reports, Business Management Review, Program Management Review), technical documentation (Software Code and Documentation, Requirements Traceability Matrix, Version Description Document), and readiness checklists (Test Readiness Review, Operational Readiness Review). Most documents must be delivered in Microsoft Office formats (Word, Excel, PowerPoint) without proprietary information for government use and modification. Delivery timelines range from proposal submission through contract award plus specified calendar days, with many items requiring updates throughout contract performance. The CDRL applies to all Task Orders under the FS3i contract unless otherwise specified in individual Task Order Performance Work Statements, and all data items must be delivered via the contractor-provided, government-access-controlled data management system using standardized naming conventions combining sequence number, program name, data item title, version number, and date.
View the file
Other files
| File | Type | Posted |
|---|---|---|
| J-01 FS3i_Base_PWS_v9_01022026.docx | DOCX document | |
| J-02 DD254_HM047625R0016_20250311.pdf | ||
| L-3_Key_Personnel_Resume_Template.docx | DOCX document | |
| L-7_Intellectual_Property_Schedule.docx | DOCX document | |
| J-05 FS3i_ Air_PWS v4.1_01022026.docx | DOCX document | |
| L-4_Small_Business_Participation_Template.xlsx | XLSX spreadsheet | |
| Section_M_v3 122825.docx | DOCX document | |
| J-04 FS3i Common Services Task Order QASP 01022026.docx | DOCX document | |
| L-2_BOE Placeholder.docx | DOCX document | |
| L-5_Master_Project_Template.xlsx | XLSX spreadsheet | |
| L-10_Placeholder.docx | DOCX document | |
| Draft_HM047625R0016.pdf | ||
| J-03 FS3i_Common_Services-TO-PWS-v16_01022026.docx | DOCX document | |
| L-1_OCI_Disclosure_Form.docx | DOCX document | |
| L-6_Past_Performance_Questionnaire.docx | DOCX document | |
| L-8_Facility_Security_Clearance_Level_Template.docx | DOCX document | |
| L-9_Personnel_Security_Clearance_Template.docx | DOCX document | |
| Section_L_v4 01132026.docx | DOCX document | |
| J-06 FS3i Air Task Order QASP-v4.1.docx | DOCX document |
Show all 19
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
UNCLASSIFIED
UNCLASSIFIED
(U) Foundation Sustainment Support, Software and Integration (FS3i)
Contract Number
TBD
Contract Data Requirements List (CDRL) xx/xx/2025 Version 3.1
| Date |
| Description of the change |
| Who made the change |
| Who Authorized the Change |
(U) TABLE OF CONTENTS
| 1 | (U) Introduction | 5 |
| 1.1 | (U) Purpose | 5 |
| 1.2 | (U) Authorities & Applicability | 5 |
| 2 | (U) General Instructions | 5 |
| 2.1 | (U) Delivery Instructions | 5 |
| 2.2 | (U) Naming Conventions | 5 |
| 3 | (U) CDRL Index | 6 |
| 3.1 | (U) Applicable Guidance | 6 |
| 4 | (U) CDRL Detailed Descriptions | 9 |
| 4.1 | (U) Program Management Plan (A001) | 9 |
| 4.2 | (U) Contract Funds Status Report (A002) | 11 |
| 4.3 | (U) Agile Development Management Plan (A003) | 12 |
| 4.4 | (U) End of Sprint Status Report (A004) | 13 |
| 4.5 | (U) Security Plan (A005) | 14 |
| 4.6 | (U) Transition-In Plan (A006) | 15 |
| 4.7 | (U) GFP/Material List (A007) | 16 |
| 4.8 | (U) System Monitoring Plan (A008) | 18 |
| 4.9 | (U) Cloud Migration Plan (A009) | 20 |
| 4.10 | (U) Customer Engagement/Meeting Minutes & Action Items (A010) | 21 |
| 4.11 | (U) Software Code and Software Code Documentation (A011) | 22 |
| 4.12 | (U) Transition-Out Plan (A012) | 23 |
| 4.13 | (U) Configuration Management Plan (A013) | 24 |
| 4.14 | (U) Risk Management Plan (A014) | 25 |
| 4.15 | (U) Quality Control Plan (A015) | 26 |
| 4.16 | (U) Staffing List (A017) | 28 |
| 4.17 | (U) Information Technology Disaster Recovery Plan (A018) | 29 |
| 4.18 | (U) Version Description Document (A019) | 30 |
| 4.19 | (U) Decommissioning Plan (A020) | 32 |
| 4.20 | (U) Deployment/Release Plan (A021) | 33 |
| 4.21 | (U) Buisness Management Review (A022) | 35 |
| 4.22 | (U) Program Management Review (A023) | 36 |
| 4.23 | (U) Deployment Chart (A024) | 37 |
| 4.24 | (U) Task-Order Kick-Off Presentation (A025) | 38 |
| 4.26 (U) Test Readiness Review (TRR) Checklist (A027) | 40 | |
| 4.27 (U) Product Support Strategy Survey and Assessment (PSA) (A029) | 42 | |
| 4.28 (U) Operations Support Plan (OSP) (A030) | 43 | |
| 4.29 (U) Integration Management Plan (IMP) (A031) | 45 | |
| 4.30 (U) Design Review Presentation (DRP) (A032) | 47 | |
| 4.31 (U) Requirements Traceability Matrix (RTM) (A033) | 49 | |
| 4.32 (U) Capability Integration Schedule (CIS) (A034) | 50 | |
| 4.33 (U) Work Breakdown Structure (WBS) (A035) | 51 | |
| 4.34 (U) Risk / Issue / Opportunity Register (RIOR) (A036) | 52 | |
| 4.35 (U) System Performance Optimization Technical Report (SPOTR) (A037) | 53 | |
| 4.36 (U) Software Library Management Report (SLMR) (A038) | 55 | |
| 4.37 (U) Automation Deployment Instructions (A039) | 56 | |
| 4.38 (U) Operational Readiness Review (ORR) Checklist (A041) | 57 | |
| 4.39 (U) Continual Service Improvement (CSI) / (BPR) (A042) | 58 | |
| 4.40 (U) Request for Change (RFC) Management Impact Assessment (A043) | 59 | |
| 4.41 (U) Test Report (A044) | 60 | |
| 4.42 (U) Corrective Action Report (CAR) (A046) | 61 | |
| 4.43 (U) Stakeholder Communication Plan (A047) | 62 | |
| 4.44 (U) Sustainment Support Plan (SSP) (A048) | 64 | |
| 4.45 (U) Machine Learning Performance Report (MLPR) (A049) | 66 | |
| Appendix A: (U) FS3i – Funds Status Report Template | 68 |
(U) Introduction
(U) Purpose
(U) The purpose of this document is to define the Contract Data Requirements List (CDRL) and provide general instructions and guidance associated with the preparation and delivery of the deliverables required under the FS3i contract.
(U) Authorities & Applicability
(U) The authorities for the associated CDRL and the corresponding DD Form 1423-1(s) can be found within section 4 of this document. If additional assistance is needed, please contact the Contracting Officer.
(U) General Instructions
(U) The contractor shall use this CDRL list for all Task Orders (TO) unless otherwise specified.
(U) The contractor shall use each TO Performance Work Statement, along with Block 16 of each CDRL-1423 to verify specific requirements per capability for each TO.
(U) Data Items shall be appropriately classified and portion marked at time of submission. Data Items not properly marked will be rejected as non-compliant.
(U) Delivery Instructions
(U) All Data Items shall be delivered via the Contractor provided, managed, and access-controlled data management system as specified in Base PWS.
(U) Naming Conventions
(U) Data Items shall be created using the following standard naming convention. The naming convention consists of each of the data elements below separated by an underscore (i.e. "_").
a. [Sequence Number] – the Data Item number (Block 1 from 1423-1) D001-D0##
b. [Program Name] – FS3i
c. [Data Item Title] – Title of Data Item (Block 2 from Form 1423-1)
d. [Version number] – X.Y (e.g. v1.1)
e. [Date] - in the format, year (YYYY) + month (MM) + day (DD) (e.g. 20150901)
(U) An example filename that conforms to the standard naming convention is provided below: D003_FS3i_Integrated_Master_Plan_v1.1_20151101.doc
(U) CDRL Index
(U) Applicable Guidance
(U) CDRLs should be the initial, draft, and final submissions, with updates as necessary, as identified within Section 4.0. Any updates required through the life of the Contract, including Contract options and Contract close-out should include updates to these documents.
Table is Unclassified
| CDRL Title |
| CDRL # |
| Program Management Plan |
| A001 |
| Contract Funds Status Report |
| A002 |
| Agile Development Management Plan |
| A003 |
| End of Sprint Status Reports |
| A004 |
| Security Plan |
| A005 |
| Transition-In Plan |
| A006 |
| GFP/Material List |
| A007 |
| Monitoring Plan |
| A008 |
| Cloud Migration Plan |
| A009 |
| Customer Engagement, Meeting Minutes and Action Items |
| A010 |
| Software Code and Software Documentation |
| A011 |
| Transition-Out Plan |
| A012 |
| Configuration Management Plan |
| A013 |
| Risk Management Plan |
| A014 |
| Quality Control Plan |
| A015 |
| Reserved |
| A016 |
| Staffing List |
| A017 |
| Information Technology Disaster Recovery Plan (ITDR) |
| A018 |
| Version Description Document |
| A019 |
| Decommissioning Plan(s) |
| A020 |
| Release Plan |
| A021 |
| Business Management Review |
| A022 |
| Program Management Review |
| A023 |
| Deployment Chart |
| A024 |
Task Order Kickoff Presentation
A025
| Reserved |
| A026 |
| Test Readiness Review checklist |
| A027 |
| Reserved |
| A028 |
| Product Support Strategy Survey and Assessment (PSA) |
| A029 |
| Operations Support Plan (OSP) |
| A030 |
| Integration Management Plan (IMP) |
| A031 |
| Design Review Presentation (DRP) |
| A032 |
| Requirements Traceability Matrix (RTM) |
| A033 |
| Capability Integration Schedule (CIS) |
| A034 |
| Work Breakdown Structure (WBS) |
| A035 |
| Risk / Issue / Opportunity Register (RIOR) |
| A036 |
| System Performance Optimization Technical Report |
| A037 |
| Software Library Management Report |
| A038 |
| Automation Deployment Instructions |
| A039 |
| Reserved |
| A040 |
| Operational Readiness Reviews (ORR) |
| A041 |
| Continual Service Improvement (CSI)/Business Process Reengineering (BPR) |
| A042 |
| Request for Change (RFC) Management Impact Assessment |
| A043 |
| Integration Test Report |
| A044 |
| Reserved |
| A045 |
| Corrective Action Report (CAR) |
| A046 |
| Stakeholder Communication Plan (SCP) |
| A047 |
| Sustainment Support Plan (SSP) |
| A048 |
| Machine Learning Performance Report (MLPR) |
| A049 |
(U) CDRL Detailed Descriptions
(U) Program Management Plan (A001)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
TBD
F. CONTRACTOR
1. DATA ITEM NO.
A001
2. TITLE OF DATA ITEM
Program Management Plan (PMP)
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS Paragraph 7.1 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| R/ASR |
| Proposal |
b. COPIES
8. APP CODE
11. AS OF DATE
N/A
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
See Block 16
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The PMP shall be delivered in Contractor Format in Microsoft Word for Government use and modification without containing any proprietary information.
Block 10: PMP sections shall be revised as required by the Government. Revisions shall be delivered 20 business days after receipt of Government request.
Block 12: Initial PMP shall be delivered with Proposal and shall not exceed 10 pages.
Block 13: Final PMP shall be delivered Award +30 calendar days.
· The PMP shall:
· Present an organization chart and supporting narrative describing the management office the offeror establishes to manage the contractual commitments;
· Define lines of control, responsibilities, functional relationships, and authority between the management office and the offeror's other organizational elements;
· Describe all interfaces between the offeror and the Government and between the offeror and other contractors which are necessary and pertinent to the accomplishment of the contract;
· Describe the management methods the offeror will employ to ensure meeting all preparations, format, and submittal requirements established by the CDRL (DD Form 1423) for data to be delivered to the Government; and present an adequate staffing plan which details how the offeror plans to hire, retain, and transition qualified personnel in for subsequent task orders to ensure successful accomplishment of the proposed technical and management approaches throughout the life of the contract.
· Identify staffing gaps and mitigation activities.
· Include subcontractor teams and expertise provided to overall staffing profile
· Present reach back and/or process plan to source and maintain qualified individuals.
· Provide an acceptable team of personnel with domain knowledge, education and experience to perform the Base PWS tasks for their positions.
· Provide process and procedures to manage and scale FS3i contract to meet future requirements.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le , FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Contract Funds Status Report (A002)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A002
2. TITLE OF DATA ITEM
Contract Funds Status Report
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| DI-MGMT-81468 |
| Base PWS Paragraph 7.1 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| Monthly |
| 30 days after contract award |
b. COPIES
8. APP CODE
11. AS OF DATE
N/A
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
Each Invoice
| Draft |
| Reg |
| Repro |
Block 16:
Notes:
Block 13: Additionally, upon request within 72 hours
The Contractor shall submit the monthly CFSR format found in the Appendix A: FS3i – Funds Status Report Template.
CFSR shall be delivered ten (10) business days after the end of each month.
In addition to the CFSR data, Contractor shall include a detailed report of performance/funding data to be presented by Capability and CLIN.
Capability performance data for period of performance shall include, but not limited to:
-Capability WBS Items, traced to hours/dollars expended, and Remaining funding per Capability.
-Accomplishments and deployments completed and pending.
-Contractual Performance Metrics by Capability and period of performance.
Block 4: Contractor Format Acceptable for Performance data report.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Agile Development Management Plan (A003)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A003
2. TITLE OF DATA ITEM
Agile Development Management Plan (ADMP)
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS Paragraph 4 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| Annually |
| Award +30 Calendar days |
b. COPIES
8. APP CODE
11. AS OF DATE
N/A
13. DATE SUBSEQUENT SUBMISSION
As Required
a. ADDRESSEE
Final
N/A
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The ADMP shall be delivered in Contractor Format in Microsoft Word for Government use and modification without containing any proprietary information.
Notes:
1. The government will provide the contractor a draft ADMP at Contract Kick-off meeting to review and update.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) End of Sprint Status Report (A004)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A004
2. TITLE OF DATA ITEM
End of Sprint Status Report
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS Paragraph 7.1 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| Each sprint |
| End of initial Sprint |
b. COPIES
8. APP CODE
11. AS OF DATE
N/A
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
Update per each sprint
| Draft |
| Reg |
| Repro |
Block 16:
Notes:
1. The Contractor shall submit the End of Sprint Status Report in JIRA and the Knowledge Management.
2. The Contractor shall provide report at the end of each Sprint.
The End of Sprint report shall:
· Identify specific accomplishments of a given sprint.
· Stories planned.
· Stories completed / not completed.
· Risks/issues.
· Sprint goals.
· Identify original schedule, tasks that were added, moved, cancelled.
· Change in requirements, Demos, product owner’s comments.
· The state of backlog.
FS3i PM
FS3i COR
FS3i CO
SharePoint
JIRA
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Security Plan (A005)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
DI-IPSC-81488
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A005
2. TITLE OF DATA ITEM
Security Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS Paragraph 7.6 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| As Required |
Award +30 calendar days
b. COPIES
8. APP CODE
11. AS OF DATE
N/A
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
N/A
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The Security Plan shall be delivered in Microsoft Word for Government use and modification without any proprietary information.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Transition-In Plan (A006)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A006
2. TITLE OF DATA ITEM
Transition-In Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS |
WBS # 6.41
IPF/FS3i
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| N/A |
| At Proposal |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| As directed by Government. |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The Transition-In Plan shall be delivered in Microsoft Word for Government use and modification without containing any proprietary information. The Transition-In Plan shall not exceed 10 pages.
Block 12: The Transition-In Plan shall be delivered with Proposal
The Transition-In Plan shall:
· Provide transition approach, key activities/tasks, rationale and schedule assuming full responsibility of capabilities NLT Government Designated date.
· A detailed resource assigned schedule outlining 15-30-45-day plans.
· Identify relevant risks and proposed mitigation.
· Identify the environments to be transitioned.
· Provide assumptions.
· Identify GFE/GFI required to affect transition.
· Required Subject Matter Expert (SME) participation.
· Provide overall time-phased staffing plan.
· Provide ramp-up profile to execute the transition.
· Provide a Transition Readiness Review Checklist.
· Provide recommendations to PMO for further investigation (CDRLs A022)
· Operational Transitions (paragraph 5.41) shall include support to a Government Operational Review
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) GFP/Material List (A007)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A007
2. TITLE OF DATA ITEM
GFP/Material List
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS Paragraph 7.4 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| As Required |
| Award +30 calendar days. |
b. COPIES
8. APP CODE
11. AS OF DATE
N/A
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
Updates as required by the Government.
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The GFP/Material List shall be delivered in Microsoft Excel for Government use and modification without containing any proprietary information.
Block 12: The GFP/Material List shall be delivered Award +30 calendar days.
Block 13: Updates as required by the Government.
The Material List shall contain the following:
· Contract Number
· Contractor Point of Contact
· Date of Last Physical Inventory
· Inventory with the following:
· Item Name
· Asset Identification Number or Unique Item Identifier
· Item Description
· Manufacturer Name
· Manufacturer Part Number
· Manufacturer Model Number
· Serial Number
· Quantity
· Location
· Type of Government Property – Government Furnished Property (GFP) or Contractor Acquired Property (CAP)
· Current condition of equipment, per the equipment condition status listed below as applicable:
· Condition A – Serviceable Usable without Qualification
· Condition B – Serviceable Usable with Qualification
· Condition D – Serviceable Test/Modification
· Condition F – Unserviceable Reparable
· Condition H - Condemned
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) System Monitoring Plan (A008)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A008
2. TITLE OF DATA ITEM
System Monitoring Plan
3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.)
Contractor Format Acceptable
5. CONTRACT REFERENCE
Base PWS WBS# 6.20, 6.21, 6.26
6. REQUIRING OFFICE
IPF/FS3i
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| R/ASR |
| Proposal + 60 calendar days |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| Update as directed by Government |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The System Monitoring Plan shall be delivered in Microsoft Word for Government use and modification without containing any proprietary information.
Block 10. Sections of the System Monitoring Plan shall be revised as directed by the Government. Revised Plan shall be delivered within 15 calendar days after request from the Government.
Block 12. The Initial System Monitoring Plan shall be delivered with the Proposal and shall not exceed 10 pages.
Block 13. Updates to System Monitoring Plan shall be delivered as directed by the Government within 5 business days.
The System Monitoring Plan shall provide the contractor’s approach for monitoring all systems under the contractor’s care. These include but are not limited to:
· Proactively detecting, identifying, and fixing operational issues such as incidents, performance problems, system degradations, for the entire operational baseline including subsystems, COTS, GOTS, FOSS, databases, etc.
· Cloud, and Cloud services in all security domains where the systems reside.
· If applicable, the system’s on premises assets (software, servers, network, storage, etc.).
· Where applicable, during testing and deployment to operations.
· Diagnostic information to help isolate issues with a system or system component and resolve them quickly.
The System Monitoring Plan shall include the contractor’s approach to gain efficiencies this includes but is not limited to:
· Using automation to reduce the cost of day-to-day operations (i.e., reducing the number of resources needed to sustain the operational baseline).
· Using automation to reduce the cost of testing, integrating, and deploying capabilities to the operational baseline.
· Leveraging Cloud pricing policy to optimize the cost of Cloud usage.
· The approach to right sizing of Cloud services.
The System Monitoring Plan shall include the contractor’s approach for monitoring the health of the operational baseline, at the minimum, the plan shall include:
· The ability to identify system component’s anomalies, performance issue, or degradation and provide metrics and measures that show the failing component.
· Description of automated detection for discovering anomalies related to systems or systems components, performance degradation, malfunctioning processes, hanging or looping processes, etc.
· Where possible provide self-healing solution to resolve, anomalies, performance degradation, hanging or looping processes, and other issues with operational baseline.
· Description of the metrics selected for monitoring and the rationale for selecting those metrics. The metrics collected and reported shall include but are not limited to:
· Operational metrics such as system and components availability, Cloud storage capacity allocated and used capacity for S3, EBS, etc.
· Cloud Services usage and utilizations i.e., RDS CPU time, memory, disk and network usage,
· Where applies, response times and EC2 utilizations for execution for batch, ETL, and interactive transactions.
· Description of the approach for setting alerts and alarms that will monitor the end-to-end heath of the systems.
· Description of the threshold values that will trigger alerts and alarms, the rationale for choosing these threshold values and the process/procedures that will be followed if threshold values are breached.
The Contractor shall propose a dashboard, based on dashboard best practices, to visualize monitoring data that shows the end-to-end status and health of a system. At the minimum the dashboard shall:
· provide the capability to identify systems / system components and other areas needing attention, such as network outages, a spike in incident reports, or high utilization of IT resources.
· Provide actionable information i.e. showing system degradation.
· Provide the capability to drilldown, set filters, print and downloads the information.
· Provide the capability to produce real-time updates at the system level.
· Provide the capability to have customize widgets and tailoring dashboard reports to view the underlying data.
Based on the information in this PWS the Contractor shall propose a System Monitoring Plan to meet the CDRL A008 intent.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Cloud Migration Plan (A009)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A009
2. TITLE OF DATA ITEM
Cloud Migration Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS 6.37 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| As Required |
| as directed by the Government |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| as directed by the Government |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The Cloud Migration Plan shall be delivered in Microsoft Word for Government use and modification without containing any proprietary information.
Block 12. The Cloud Migration Plan shall be delivered as directed by the Government.
Block 13. Revisions to the Cloud Migration Plan sections shall be delivered as directed by the Government.
The Cloud Migration Plan shall provide:
- Detail of the operational components/services to be migrated to the cloud.
- Detail of the cloud architecture costs to support the migration of the components/services.
- Detail the schedule and dependencies for migrating the applications and services, supporting databases, and data to the cloud. Include security assessment and accreditation steps for authorization to operate.
- Detail of the risks and mitigations to reduce operational downtimes during migration.
- Detail, if any, additional resources and personnel required to support the operational cloud environments.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Customer Engagement/Meeting Minutes & Action Items (A010)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A010
2. TITLE OF DATA ITEM
Customer engagement/Meeting Minutes & Action Items.
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
Base PWS Paragraph 7.1
6. REQUIRING OFFICE
Contractor Format Acceptable
IPF/FS3i
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| As Required |
| See Block 16 |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| See Block 16 |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The item shall be delivered in Microsoft Word and/or Excel for Government use and modification without containing any proprietary information.
Block 10: Revisions shall be delivered as directed by the Government.
Block 12. When directed by the Government, the items shall be delivered NLT five (5) working days after the event/meeting/engagement.
The Meeting Minutes and Action Items shall address in depth the following:
· The purpose and objective of the meeting or trip
· The meeting or trip location
· A summary of the discussions that occurred
· Relevant conclusions/recommendations based on the meeting or trip
· Action items resulting from the meeting or trip
· List of attendees or participants
· Briefing charts, if presented, shall be attached for information only
· Mandatory minutes/action items included with all TEMs w/ PMO, Program Kick-off, PMRs, RPEs, Ad Hoc per request at the direction of the Government.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Software Code and Software Code Documentation (A011)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A011
2. TITLE OF DATA ITEM
Software Code and Software Code Documentation
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
Base PWS 6.16 to 6.19, 6.43
6. REQUIRING OFFICE
Contractor Format Acceptable
IPF/FS3i
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| As Required |
| See Block 16 |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| See Block 16 |
| Draft |
| Reg |
| Repro |
Block 16:
Block 12: Provide for first operational release.
Block 13: Provide for first operational release.
Notes:
1. All Software Code and Software Code Documentation shall be delivered in the Government provided environment i.e. Git Hub for Government use and modification without containing any proprietary information.
2. All software must meet Government testing, inspection, and acceptance criteria before delivery.
3. All software must meet NGA 503 compliance specifications.
4. The Software Code Documentation shall be delivered 10 business days after required by the Government.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Transition-Out Plan (A012)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A012
2. TITLE OF DATA ITEM
Transition-Out Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS WBS# 6.42 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| As Required |
| As directed by the Government. |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| As directed by the Government. |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The Transition-Out Plan shall be delivered in Microsoft Word for Government use and modification without containing any proprietary information.
Block 12. The Transition-Out Plan shall be delivered as directed by the Government within 30 calendar days of the request.
Block 13. Revisions to the Transition-Out Plan sections shall be delivered as requested by the Government. Revised Plan shall be delivered 5 business days after request from the Government.
The Transition-out Plan shall:
-identify the key GFE/GFI artifacts supporting operational applications, databases, configuration management, governance, helpdesk, training, release cadence and schedules, application interfaces, software, and material required to transition from current Release train and O&M activities to a new contractor.
· Detail transition–out schedule including any dependencies, risks, and: proposed mitigation.
· Identify (if required) travel requirement to introduce the new personnel to the key product owners and contractors developing FS3i services.
· Detail key personnel and subject matter experts activities and how will they remain available throughout the transition.
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Configuration Management Plan (A013)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A013
2. TITLE OF DATA ITEM
Configuration Management Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS WBS# 6.3 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| R/ASR |
| Award +30 Calendar Days |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| Update as directed by the Government |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The Configuration Management Plan shall be delivered in Microsoft Word for Government use and modification without containing any proprietary information.
Block 10. Revised Configuration Management Plan shall be delivered as directed by the Government.
Block 12: Configuration Management Plan shall be delivered to the Government Award + 30 calendar days.
Block 13. Update to Configuration Management Plan shall be delivered as directed by the Government.
The Configuration Management Plan shall:
· Detail tools and resources for configuration management, monitoring, and reporting.
· Detail the configuration management activities require to maintain FS3i’s application program interfaces (APIs) used for external development and internal operational and maintenance activities.
· Detail processes and tools to monitor, manage, and report on the test and operational baselines’ Problem incidents (PBIs)/Discrepancy Reports (DRs).
· Ranking of configuration discrepancies and anomalies for the purpose of risk assessments. An example of ranking could be High, Medium, and Low.
FS3i PM
FS3i COR
FS3i CO
SharePoint
CM
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Risk Management Plan (A014)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A014
2. TITLE OF DATA ITEM
Risk Management Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
| Contractor Format Acceptable |
| Base PWS Paragraph 7.1 |
| IPF/FS3i |
| 7. DD 250 REQ |
| 9. DIST STATEMENT |
| 10. FREQUENCY |
| 12. DATE OF FIRST SUBMISSION |
| 14. DISTRIBUTION |
| N/A |
| F |
| R/ASR |
| Award +30 calendar days. |
b. COPIES
8. APP CODE
11. AS OF DATE
| 13. DATE SUBSEQUENT SUBMISSION |
| a. ADDRESSEE |
Final
N/A
| N/A |
| See Block 16 |
| Draft |
| Reg |
| Repro |
Block 16:
Block 4: The Risk Management Plan shall be delivered in Microsoft Word for Government use and modification without containing any proprietary information.
Block 10: Revisions to Risk Management Plan sections shall be delivered as requested by the Government.
Block 12: Risk Management Plan shall be delivered to the Government Award + 30 calendar days.
Block 13. Updates to Risk Management Plan shall be delivered as directed by the Government.
The Risk Management Plan shall address in depth each major section identified below:
· Risk Management Strategy and Process
· Responsible/Executing Organizational Component
· Risk Management Process and Procedures
· Risk Identification
· Risk Analysis
· Risk Mitigation Planning
· Risk Mitigation Implementation
· Risk Tracking
FS3i PM
FS3i COR
FS3i CO
SharePoint
15. TOTAL
| G. PREPARED BY |
| H. DATE |
| I. APPROVED BY |
| J. DATE |
Tbd, FS3i COR
Bao Le, FS3i Program Manager
DD FORM 1423-1, FEB 2001 Computer Generated PREVIOUS EDITION MAY BE USED. Page 1 of 1 Pages
(U) Quality Control Plan (A015)
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item) Form Approved OMB No. 0704-0188
The public reporting burden for this collection of information is estimated to average 110 hours per response, including the time for reviewing instructions, searching existing data sources, gathering and maintaining the data needed, and completing and reviewing the collection of information. Send comments regarding this burden estimate or any other aspect of this collection of information, including suggestions for reducing the burden, to Department of Defense, Washington Headquarters Services, Directorate for Information Operations and Reports (0701-0188), 1215 Jefferson Davis Highway, Suite 1204, Arlington VA 22202-4302. Respondents should be aware that notwithstanding any other provision of law, no person shall be subject to any penalty for failing to comply with a collection of information if it does not display a currently valid OMB control number. Please DO NOT RETURN your form to the above address. Send completed form to the Government Issuing Contracting Officer for the Contract/PR No. listed in Block E.
| A. CONTRACT LINE ITEM NO. |
| B. EXHIBIT |
| C. CATEGORY: |
D. SYSTEM/ITEM
E. CONTRACT/PR NO.
F. CONTRACTOR
1. DATA ITEM NO.
A015
2. TITLE OF DATA ITEM
Quality Control Plan
3. SUBTITLE
| 4. AUTHORITY (Data Acquisition Document No.) |
| 5. CONTRACT REFERENCE |
| 6. REQUIRING OFFICE |
This is the start of the file's text. The full file is on GovTribe.
File details come from the government source that posted it. Updated .