attach0009.pdf

PDF 139 KB Posted

Attached to
Route Clearance Interrogation System (RCIS)
Solicitation number
W56HZV15R0156
Issued by

About this file

Attachment 0009 - RCIS Technical Review Criteria

View the file

Other files

File Type Posted
FCL_Sponsorship_Letter_OCT15.pdf PDF
FCL_Notice.docx DOCX document
FCL_Orientation_Handbook_18FEB15.pdf PDF
Q&A_Tracker_4-3-17.pdf PDF
RCIS_-__Administrative_Notice__2.pdf PDF
RCIS_-_QA_Tracker_-_Administrative_Notice.pdf PDF
Q&A_Tracker_2-23-17.pdf PDF
Q&A_Tracker_2-10-17.pdf PDF
Q&A_Tracker_12-29-16.pdf PDF
Attachment_0037_-_Small_Business_Participation_Workbook_10-13-16.xlsx XLSX spreadsheet
RCIS_Type_I_Vehicle_Viewing_Participants.pdf PDF
Q A_Tracker_Batch_1.pdf PDF
RCIS_Type_I_Vehicle_Viewing_Invitation_Revision_1.docx DOCX document
RCIS_Type_I_Vehicle_Viewing_Invitation.pdf PDF
Questions_and_Comments_from_Industry_on_the_Route_Clearance__Interrogation_System_(RCIS)_Program.pdf PDF
Pre-Solicitation_Conference_List_of_Attendees.pdf PDF
One-on-One_Questions.pdf PDF
Attachment_0015_-_RCIS_Program_Plan.pptx PPTX presentation
Attachment_0044_-_Soldier_Workload_Instructions.docx DOCX document
Attachment_0043_-_HFEA_Instructions.docx DOCX document
Attachment_0032_-_SSv_Severity_Scale.ppt PPT presentation
Attachment_0048_-_HSI_Event_Report_Instructions.docx DOCX document
Attachment_0038_-_Equipment_Publications_Defects_List.doc DOC document
Attachment_0036_-_Small_Business_Participation_Workbook_Instructions.docx DOCX document
Attachment_0047_-_HSI_Event_Plan_Instructions.docx DOCX document
Attachment_0022_-_Production_Contractor_Format_Technical_Data_Package_(TDP).docx DOCX document
Attachment_0016_-_VDLS_Account_Access.docx DOCX document
Attachment_0006_-_RCIS_Type_I_Work_Breakdown_Structure_(WBS).xlsx XLSX spreadsheet
Attachment_0011_-_Performance_Work_Statement_Applicable_Documents.docx DOCX document
Attachment_0010_-_RCIS_Pre-TRR_Checklist.docx DOCX document
RCIS_Type_I_CDRL.pdf PDF
Attachment_0018_-_RCIS_Type_I_Test_Summary.xlsx XLSX spreadsheet
Attachment_0008_-_Government_Furnished_Property_(GFP)_List.pdf PDF
Attachment_0020_-_Hardware_Software_List.xls XLS spreadsheet
Attachment_0012_-_MIL_Grade_Connector_Waiver_Form.xlsx XLSX spreadsheet
Attachment_0009_-_Technical_Review_Criteria.pdf PDF
RCIS_Pre-Solicitation_Conf_Invitation__-_Aug_2016.pdf PDF
RCIS_Q A_Tracker_5-12-16.pdf PDF
Postponed_Announcement_-_RCIS_Pre-Solicitation_Conference.docx DOCX document
Postponed_Announcement_-_RCIS_Pre-Solicitation_Conference.docx DOCX document
RCIS_Pre-Solicitation_Conf_Invitation.docx DOCX document
RCIS_Acq_Strategy_Notice_2016.docx DOCX document
attach0006.XLSX XLSX spreadsheet
attach0016.pdf PDF
attach0014.pdf PDF
attach0007.pdf PDF
CDRLs.doc DOC document
RFI-2015.pdf PDF
RFI-Survey.pdf PDF
attach0010.docx DOCX document
Show 40 more

50 files listed here. See the rest on GovTribe.

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

Route Clearance & Interrogation Systems (RCIS)

TECHINICAL REVIEW CRITERIA

28 April 2015

SRR Details Area SRR Review Details

Chairperson APM Appliqué (or designee)

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review Ensures the contractor understands the RCIS Performance Specification and the proposed approach is compliant with these requirements.

Entrance Criteria SRR Agenda Per the DAG Section 4.2.10

Exit Criteria Per the DAG Section 4.2.10

Products/Artifacts

(from the review)

Contractor documentation per contract delivered and accepted.

Government Documents per the DAG Section 4.2.10.

PDR Details Area PDR Review Details

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder

Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review

The Preliminary Design Review (PDR) ensures the preliminary design and basic system architecture are complete, and that there is technical confidence the capability need can be satisfied within cost and schedule goals. The PDR provides the acquisition community, end user, and other stakeholders with an opportunity to understand the trade studies conducted during the preliminary design, and thus confirm that design decisions are consistent with the user’s performance and schedule needs. The PDR also establishes the system’s allocated baseline.

Entrance Criteria PDR Agenda Action items from the SRR have been closed

Per the DAG Section 4.2.12

Exit Criteria Per the DAG Section 4.2.12

Products/Artifacts

(from the review)

Government Documents per the DAG Section 4.2.12.

CDR Details Area CDR Review Details

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review

The Critical Design Review (CDR) confirms the system design is stable and is expected to meet system performance requirements, confirms the system is on track to achieve affordability and should cost goals as evidenced by the detailed design documentation, and establishes the system’s initial product baseline.

Entrance Criteria CDR Agenda Action items from the PDR have been closed

Per the DAG Section 4.2.13

Exit Criteria Per the DAG Section 4.2.13

Products/Artifacts

(from the review)

Government Documents per the DAG Section 4.2.13.

SVR/FCA Details Area SVR/FCA Review Details

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder

Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review

The System Verification Review (SVR) is the technical assessment point at which the actual system performance is verified to meet the requirements in the system performance specification and is documented in the system functional baseline. The Functional Configuration Audit

(FCA) is the technical audit during which the actual performance of a system element is verified and documented to meet the requirements in the system element performance specification in the allocated baseline.

Entrance Criteria

SVR/FCA Agenda Action items from the CDR have been closed

Per the DAG Section 4.2.14

Exit Criteria Per the DAG Section 4.2.14

Products/Artifacts

(from the review)

Government Documents per the DAG Section 4.2.14.

PRR Details Area PRR Review Details

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder

Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review

The Production Readiness Review (PRR) for the system determines whether the system design is ready for production, and whether the developer has accomplished adequate production planning for entering

Low-Rate Initial Production (LRIP) and Full-Rate Production (FRP).

Production readiness increases over time with incremental assessments accomplished at various points in the life cycle of a program.

Entrance Criteria

PRR Agenda Action items from the SVR/FCA have been closed

Per the DAG Section 4.2.15

Exit Criteria Per the DAG Section 4.2.15

Products/Artifacts

(from the review)

Government Documents per the DAG Section 4.2.15.

TRR Details Area TRR Review Details

Chairperson APM Appliqué (or designee)

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review

The Test Readiness Review (TRR) is a technical review designed to ensure that the subsystem or system under review is ready to proceed into formal test. The TRR assesses test objectives, test methods and procedures, scope of tests, and safety and confirms that required test resources have been properly identified and coordinated to support planned tests. The TRR verifies the traceability of planned tests to program requirements and user needs. It determines the completeness of test procedures and their compliance with test plans and descriptions. The TRR also assesses the system under review for development maturity, cost/ schedule effectiveness, and risk to determine readiness to proceed to formal testing.

Entrance Criteria

Program manager's and T&E WIPT's determination that preliminary, functional, and pre-qualification test evaluation results form a satisfactory basis to initiate formal, system-level testing.

System has stabilized in configuration Compliance with Pre-TRR checklist

Exit Criteria

Necessary stakeholders were involved.

All planned tests verify a requirement that is directly traceable back to a system specification or other program requirement.

The system under test (i.e. configuration) is sufficiently mature, defined, and representative to accomplish planned test objectives and or support defined program objectives.

All planned preliminary, informal, functional, unit level, subsystem, system, and qualification tests were conducted, and are the results are satisfactory.

All expected results are known and their affect on the program is also known.

All planned tests resources (people, test article or articles, facilities, data systems, support equipment, logistics, etc.) are identified.

All risks associated with the tests are known and mitigation plans are complete.

Hazards and ESOH risks associated with the specific testing are identified.

The necessary “Safety Releases” from the Program Manager (PM) are provided to developmental and operational testers prior to any test using personnel.

A fall-back plan (should a technical issue or potential showstopper arise during testing) is available.

Products/Artifacts

(from the review)

Completed and approved test plans for the system under test.

Completed identification and coordination of required test resources.

Previous component, subsystem, and system test results form a satisfactory basis for proceeding into planned tests.

Identified risk level acceptable to the program leadership.

PCA Details Area PCA Review Details

PMO Participants PdM ALUGS

Members of RCIS IPT(Contracting, Cost Analysis, Scheduler, LSE, Engineering, Software, Test, Logistics)

Contracting Officer

Anticipated

Stakeholder

Participant

Organizations

PM Force Projection

PdM CE/MHE

PdM AMS

MSCoE

ATC/ATEC

Anticipated Peer and

Program-Independent

SME Participant Orgs.

TARDEC

Purpose of the review

The Physical Configuration Audit (PCA) is a formal examination to verify the “to be fielded” configuration of a validated system against its design and manufacturing documentation. The objective of the PCA is to resolve any discrepancies between the production-representative item that has successfully passed Operational Test and Evaluation (OT&E) and the associated documentation currently under configuration control.

Entrance Criteria

PCA Agenda Action items from the PRR have been closed

Per the DAG Section 4.2.16

Exit Criteria Per the DAG Section 4.2.16

Products/Artifacts

(from the review)

Government Documents per the DAG Section 4.2.16.

File details come from the government source that posted it. Updated .