BiNOD CDRL D008 Functional_Physical Configuration Audit (FCA-PCA) Plan .pdf
PDF 91 KB Posted
- Attached to
- Binocular Night Observation Device (BiNOD) Federal contract opportunity
- Solicitation number
- W91CRB-25-R-0007
About this file
This is a Contract Data Requirements List (CDRL) DD Form 1423-1 for a Physical/Functional Configuration Audit Plan (Data Item D008) associated with the Binocular Night Observation Device (BiNOD) program. The document requires the contractor to develop and submit a PCA/FCA Plan that describes how physical and functional configuration audits will be conducted down to the spareable item level, including test methods, tools, and fixtures required to support the system.
The plan must be submitted electronically with a draft due 30 days after Government DT and OT completion, followed by Government review within 15 business days. The final plan is due within 30 days of receiving Government comments. Key content requirements include: hardware/software configuration items to be audited, documentation review requirements (engineering drawings, specifications, test plans, manuals), audit scope and schedule, and team composition details. Distribution is required to PCO, COR, and APM with one copy each of draft and final versions. The plan must be approved by the IPPT prior to conducting the audit and must include visual inspection of all interface, mating and interconnection dimensions of subcomponents.
View the file
Other files for this federal contract opportunity
Show all 50
Binocular Night Observation Device (BiNOD) has more files on GovTribe.
On GovTribe
Work with this file on GovTribe
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
DD FORM 1423-1, FEB 2001
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
PREVIOUS EDITION MAY BE USED.
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 the Department of Defense, Executive Services and Communications Directorate (0704-0188). 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 organization. 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:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
1. DATA ITEM NO. 2. TITLE OF DATA ITEM 3. SUBTITLE
4. AUTHORITY (Data Acquisition Document No.) 5. CONTRACT REFERENCE 6. REQUIRING OFFICE
7. DD 250 REQ
8. APP CODE
9. DIST STATEMENT
REQUIRED
10. FREQUENCY
11. AS OF DATE
12. DATE OF FIRST SUBMISSION
13. DATE OF SUBSEQUENT
SUBMISSION
14. DISTRIBUTION
a. ADDRESSEE
b. COPIES
Draft Final
Reg Repro
15. TOTAL
16. REMARKS
17. PRICE GROUP
18. ESTIMATED
TOTAL PRICE
G. PREPARED BY H. DATE I. APPROVED BY J. DATE
Page of Pages
CONTRACT DATA REQUIREMENTS LIST
(1 Data Item)
A. CONTRACT LINE ITEM NO. B. EXHIBIT C. CATEGORY:
TDP ________ TM _______ OTHER
D. SYSTEM/ITEM E. CONTRACT/PR NO. F. CONTRACTOR
16. REMARKS (Continued)
DD FORM 1423-1, FEB 2001 Page of Pages
| 1_DATA_ITEM_NO: D008 |
| 2_TITLE_OF_DATA_ITEM: Physical/Functional Configuration Audit Plan |
| 3_SUBTITLE: |
| 4_AUTHORITY_Data_Acquisit: DI-SESS-80858C |
| 5_CONTRACT_REFERENCE: SOW 4.6 |
| 6_REQUIRING_OFFICE: PdM, Soldier Maneuver Sensors |
| 7_DID_250_REQ: LT |
| 8_APP_CODE: N/A |
| DIST_STATEMENT: B |
| 10_FREQUENCY: See Blk 16 |
| 11_AS_OF_DATE: See Blk 16 |
| 12_DATE_OF_FIRST_SUBMISSI: See Blk 16 |
| 13_DATE_OF_SUBSEQUENT_SUB: See Blk 16 |
| addressee1: PCO |
| draft1: 1 |
| reg1: 1 |
| repro1: |
| addressee2: COR |
| draft2: 1 |
| reg2: 1 |
| repro2: |
| addressee3: APM |
| draft3: 1 |
| reg3: 1 |
| repro3: |
| addressee4: |
| draft4: |
| reg4: |
| repro4: |
| addressee5: |
| draft5: |
| reg5: |
| repro5: |
| addressee6: |
| draft6: |
| reg6: |
| repro6: |
| addressee7: |
| draft7: |
| reg7: |
| repro7: |
| addressee8: |
| draft8: |
| reg8: |
| repro8: |
| addressee9: |
| draft9: |
| reg9: |
| repro9: |
| addressee10: |
| draft10: |
| reg10: |
| repro10: |
| addressee11: |
| draft11: |
| reg11: |
| repro11: |
| addressee12: |
| draft12: |
| reg12: |
| repro12: |
| addressee13: |
| draft13: |
| reg13: |
| repro13: |
| addressee14: |
| draft14: |
| reg14: |
| repro14: |
| addressee15: |
| draft15: |
| reg15: |
| repro15: |
| addressee16: |
| draft16: |
| reg16: |
| repro16: |
| addressee17: |
| draft17: |
| reg17: |
| repro17: |
| addressee18: |
| draft18: |
| reg18: |
| repro18: |
| addressee19: |
| draft19: |
| reg19: |
| repro19: |
| addressee20: |
| draft20: |
| reg20: |
| repro20: |
| addressee21: |
| draft21: |
| reg21: |
| repro21: |
| addressee22: |
| draft22: |
| reg22: |
| repro22: |
| addressee23: |
| draft23: |
| reg23: |
| repro23: |
| addressee24: |
| draft24: |
| reg24: |
| repro24: |
| addressee25: |
| draft25: |
| reg25: |
| repro25: |
| addressee26: |
| draft26: |
| reg26: |
| repro26: |
| addressee27: |
| draft27: |
| reg27: |
| repro27: |
| addressee28: |
| draft28: |
| reg28: |
| repro28: |
| addressee29: |
| draft29: |
| reg29: |
| repro29: |
| addressee30: |
| draft30: |
| reg30: |
| repro30: |
| addressee31: |
| draft31: |
| reg31: |
| repro31: |
| addressee32: |
| draft32: |
| reg32: |
| repro32: |
| addressee33: |
| draft33: |
| reg33: |
| repro33: |
| addressee34: |
| draft34: |
| reg34: |
| repro34: |
| addressee35: |
| draft35: |
| reg35: |
| repro35: |
| addressee36: |
| draft36: |
| reg36: |
| repro36: |
| addressee37: |
| draft37: |
| reg37: |
| repro37: |
| addressee38: |
| draft38: |
| reg38x: |
| repro38: |
| total_draft: 3 |
| total_repro: 0 |
| 16_REMARKS: Block 9. Include DISTRIBUTION STATEMENT B: Distribution authorized to U.S. Government Agencies only per the I2 Security Classification Guide. Other requests for this document shall be referred to Product Manager Soldier Maneuver Sensors, SFAE-SDR-SMPT-SMS, 9625 Middleton Road, Fort Belvoir, VA 22060-5824. Date of determination is date product is generated. |
The draft PCA/FCA Plan shall be submitted electronically and via letter of transmittal 30 days after Government DT and OT are completed.
The Government will complete review/comment/approval of the draft PCA/FCA Plan within 15 business days of receipt from the contractor.
The contractor shall submit the final PCA/FCA Plan NLT 30 days after receipt of Government comments or approval.
The PCA/FCA Plan shall describe how the physical and functional configuration audit will be conducted for the system(s), down to the spareable item level for the design that successfully completes contractor PQT and Government DT/OT, including any TMDE, special tools, and fixtures required to support/sustain the system(s). The PCA/FCA plan shall also propose a location and schedule for the audit, and identify the individuals who will conduct the audit. The PCA/FCA plan shall also identify the interface control and product items to be audited.
Format Contractor format is acceptable.
Content
• The PCA/FCA shall include all hardware and software developed for this contract and any hardware or software that is to be modified as a result of this contract.
• The PCA/FCA Plan shall be approved by the IPPT prior to the commencement of the PCA/FCA.
• The PCA/FCA shall be conducted on all interface, mating and interconnection dimensions, and shall include a visual inspection of all subcomponents, as a minimum.
(continued on next page)
| 17_PRICE_GROUP: |
| ESTIMATED_TOTAL_PRICE: |
| G_PREPARED_BY: |
| H_DATE: |
| 1_APPROVED_BY: |
| J_DATE: |
| Page: 1 |
| reg38t: 3 |
| A_CONTRACT_LINE_ITEM_NO: 0000 |
| B_EXHIBIT: |
| TDP: |
| TM: |
| OTHER: Configuration Management |
| DSYSTEMITEM: BiNOD |
| E_CONTRACTPR_NO: |
| FCONTRACTOR: |
| 16_REMARKS_Continued: Physical/Functional Configuration Audit Plan (cont'd) |
Content (cont'd):
The Plan is to include information on:
• The purpose and objective of the audit in terms of the contract requirements
• Identify the physical hardware configuration items to be audited:
o Nomenclature o Specification / part number o Serial number (if applicable)
• Identify the documentation to be audited:
o Engineering drawings o Applicable specifications o Engineering Change Proposals o Test plans and procedures o Operating and support manuals o Configuration documentation release procedures o Request for deviations/ waivers
• Scope of audit which includes a summary of the hardware requirements against which the audit will be conducted as specified in work statements, specifications and approved plans.
• Location and schedule of the audit
• Team Composition o Identify the Army Representatives and their function in the audit o Identify Contractor Representatives and their function in the audit
| Page2: 2 |
| of_pages: 2 |
| Reset: |
File details come from the government source that posted it. Updated .