Att_(15)_DMSMS_Case_Sheet_(CDRL_LR0D)_Rev_E_2015.05.06.xlsx

XLSX spreadsheet 41 KB Posted

Attached to
CDL SRQ-4 Solicitation Federal contract opportunity
Solicitation number
N00019-16-R-3001
Issued by
Department of the Navy Naval Air Systems Command

View the file

Other files for this federal contract opportunity

Other files attached to CDL SRQ-4 Solicitation, newest first.
File Type Posted
Att_(10)_PPL_CDRL_LR04.docx DOCX document
Attch_L2_Past_Performance_Questionnaire.docx DOCX document
Att_(07)_CDRL_Cross_Reference_Matrix.xlsx XLSX spreadsheet
Att_(11)_EDFP_CDRL_LR05.docx DOCX document
Att_(03)_TEMPEST_Control_Plan_Description.doc DOC document
Att_(12)_PHST_CDRL_LR08.docx DOCX document
Att_(14)_DMSMS_Quarterly_Report__CDRL_LR0C__Rev_L_2013.02.15.docx DOCX document
Attch_L5_GFE _GFP _GFF _GFI_List-(Blank_Form).xls XLS spreadsheet
CDL_SRQ_Final_CDRLs_9_15_2016.pdf PDF
Attch_L4_Cost-Price_Summary_Table _4_Dec_2015.xls XLS spreadsheet
Att_(16)_DD254_08_Sept_2016.pdf PDF
Att_(06)_GFE-GFP.xlsx XLSX spreadsheet
Att_(09)_LMI_CDRL_LR03.xls XLS spreadsheet
Att_(05)_FRACAS_Failure_Determination.doc DOC document
Attch_L3_CPAR_Update_Questionnaire _18_Dec_2015.doc DOC document
Att_(04)_Contractor_Data_Assertions_(to_Propose).docx DOCX document
N00019-16-R-3001_15_Sept_2016.docx DOCX document
Att_(13)_BOM_Template_(CDRL_LR0B)_w_Macros_rev_3_1.10.2014_0221.xlsx XLSX spreadsheet
Att_(08)_Contractor's_Small_Business_Plan_(to_Propose).doc DOC document
Show all 19

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

Case Sheet Instructions:

Fill out the top sections of the form to row 16 (Solution Required). If a solution is required and parts can still be procured, Fill out Table 1. Table 1 will automatically fill in the Life of Type Buy blocks. If other options should be considered, fill out the additional option blocks as needed.

Brief Title Priority CDRL # Case Sheet # Related Case Sheets OMIS Case Log #

Date Submitted Last Time Buy Date Action Needed by Date NHA Impact Date

OEM Company NameOEM Technical POC
NamePhoneE-Mail
PMA299 IPT Program ImpactedPMA299 IPT Program POC
NamePhoneE-Mail

Next Higher Assy (P/N & Nomenclature) QTY WRA Affected (P/N & Nomenclature) QTY System Affected (P/N & Nomenclature) QTY

Original P/N Data
P/NNSN/NIINCage CodeManufacturer
SCD Part:
Vendor Part:
Part Description:
Sourcing Issues:[Discuss the nature of the obsolescence problem and delineate any assumptions made.]
Recommended Action
Solution Required (Select YES/NO)YesSelect Recommended Solution (From Pull Down Menu)
Can Parts Be Procured (Select YES/NO)Yes
Quantity and Cost are autofilled from the Procurement Calculator WorksheetQuantityCostOrder DateReceived DateSpan of Coverage Part Buy is Good For
Part Procurement:0$ - 0
Recommended Action Description:
Recommended Action Advantages:
Recommended Action Disadvantages:
Recommended Action Cost Summary:
Recommended Action P/N Data (Note: If recommended action is for a new P/N fill in the following information:)
P/NNSN/NIINCage CodeManufacturer
SCD Part:
Vendor Part:
Part Description:
Additional Options Considered
Option 1:Select Option Solution (From Pull Down Menu)
QuantityUnit PriceTesting Cost (If Needed)Part buy CostNRE COSTTotal Cost
Option 1 Description:
Option 1 Advantages:
Option 1 Disadvantages:
Option 1 Cost Summary:
Option 1 P/N Data (Note: If Option 1 is for a new P/N fill in the following information:)
P/NNSN/NIINCage CodeManufacturer
SCD Part:
Vendor Part:
Part Description:
Option 2:Select Option Solution (From Pull Down Menu)
QuantityUnit PriceTesting Cost (If Needed)Part buy CostNRE COSTTotal Cost
Option 1 Description:
Option 1 Advantages:
Option 1 Disadvantages:
Option 1 Cost Summary:
Option 2 P/N Data (Note: If Option 2 is for a new P/N fill in the following information:)
P/NNSN/NIINCage CodeManufacturer
SCD Part:
Vendor Part:
Part Description:
Distribution Reviewers: (To be filled in by the people involved in reviewing the case sheet submittal. For a list of possible reviewers see the distribution worksheet.
CDRL Reviewer Name:Phone:E-Mail:COMMENTS

Stage 1 Reviewer Name: Phone: E-Mail: COMMENTS

Stage 2 Reviewer Name: Phone: E-Mail: COMMENTS

Stage 3 Reviewer Name: Phone: E-Mail: COMMENTS

From the list below select either PRI, PR2, PR3 or PRI4 and insert into the priority cell in row 3.
PRI 1 – Emergent Requirements - Time sensitive issue. Requires a formal 30 day review cycle time.PRI 1 – These are complex time sensitive issues that require an expedited review cycle in order to prevent a significant near-term impact and/or to place a purchase by the LTB date. Any issue that has a LTB date less than 60 days of the EOL notice with no suitable alternatives would qualify as a PRI 1. In most PRI 1 cases the alternative to LTB will involve re-design or a similar complex resolution. All PRI 1’s require a full review cycle.
PRI 2 – Expedite Requirements. Requires a formal 30 day review cycle time.PRI 2 – These are complex time sensitive issues that require an expedited review cycle in order to prevent a significant near-term impact and/or to place a purchase by the LTB date. Any issue that has a LTB date between 60 and 90 days of the EOL notice with no suitable alternatives would qualify as a PRI 2. In most PRI 2 cases the alternative to LTB will involve re-design or a similar complex resolution. All PRI 2’s require a full review cycle.
PRI 3 – AoA/Case Sheet Long Lead and/or NRE RequirementsPRI 3 – These are issues where enough time is available to identify a solution without any immediate impacts. These can be complex issues and may have a LTB date greater than 90 days of the EOL notice and/or present no immediate impact to production and existing contracts. In most cases consideration needs to be given to more complex resolutions that may involve redesign, re-qualification and similar activities or require additional time to investigate options for a cost effective long-term solution. All PRI 3’s require a full review cycle. This is the default priority for most Case Sheets.
PRI 4 – Notification only. - Normal Routing RequirementsPRI 4 – These are issues that have standard/routine solutions and are provided primarily for notification only. These issues do not present any impact to in-process or near-term pending contracts. This information is provided mainly for awareness of issues and limitations to aid in strategic planning and long-term sustainment considerations. PRI 4’s require distribution to affected parties but no formal review process is required.
Priority Boundaries for Case Sheets (Examples of Assignment of Priority)
Priority 1 - Emergent Requirements
- EOL notice for LTB is 0-60 days and/or part is high demand
- Spares/Repair stock depleted (reported by OEM, NAVSUP, DLA)
- Fleet requirement for a mission readiness issue
- Long lead items of a mission critical nature that are needed in a EOL LTB
Priority 2 - Expedite Requirements
- EOL notice for LTB is 60-90 days
- Spares/Repair stock is nearly depleted and a solution needs to be identified
- Fleet has identified an DMSMS Sustainment issue that needs to be addressed
- Long lead items of a mission critical nature that are needed in a EOL LTB
Priority 3 - AoA/Case Sheet Long Lead and/or NRE Requirements
- Although options were considered, no solution has been identified and we have time to work the issue
- NRE is required for a solution
- Long term requirements/efforts have been identified
- Where PMA-299 has time to assess the situation and identify possible ideas for solutions
Priority 4 - Normal Routing Requirements
- Case Sheet is for Information Only and only for notification
- An FFF no cost alternative part has been identified and implemented
- RoHS part substitution (engineering assessment is completed and part is OK for use)
- Lower priority issue where broker market parts available in great quantity
- EOL notice for LTB is greater than 120 days and part is in low demand
The contents of this form are protected to enable form functions. To unprotect the form, select Tools, Protection, Unprotect Sheet. There is no password.
CDRL Reviewer Name:
See the "Reviewer & Distribution" Tab. The Obsolescence SME (Subject Matter Expert) name(s) who reviewed the case sheet.
Stage 1 Reviewer Name:
See the "Reviewer & Distribution" Tab. The PMA-299 Technical and Engineering name(s) who reviewed the case sheet.
Stage 2 Reviewer Name:
See the "Reviewer & Distribution" Tab. The Leadership name(s) who Acknowledged, Reviewed and Concurred with the options listed on the case sheet.
Stage 3 Reviewer Name:
See the "Reviewer & Distribution" Tab. The Program Manager(s) who gave Final Approval of Recommended DMSMS Solution.
Select Recommended Solution (From Pull Down Menu)
1.) There is an approved alternate part on the BOM or SCD.
2.) OEM has Sufficient Stock on Hand (See Table 1).
3.) DLA has stock on hand.
4.) Life of Type Buy (LOT Buy) or Bridge Buy can be done.
5.) Continue to Manufacture (Extend Production).
6.) Another approved manufacturer makes this part.
7.) There is Aftermarket Production Capability - testing may be required.
8.) Parts are available from the Broker Market - testing may be required.
9.) Reclamation is available - testing may be required.
10.) There is a ROHS P/N Change.
11.) A FFF alternate part exist - testing may be required.
12.) A substitute part (not quite FFF) exists - testing may be required.
13.) Part can be emulated - testing may be required.
14.) A prior emulated part exists - testing may be required.
15.) Resolution requires redesign – testing is required.
16.) There is a Tech Refresh / Tech Insertion planned that will solve the obsolescence problem at the SRU and WRA levels.
17.) An obsolescence health check has been performed at the NHA/SRU level and there are other obsolescence issue on the NHA/SRU that require further study to come up with the best resolution for solving the obsolecence problems.
18.) An obsolescence health check has been performed at the WRA level and there are other obsolescence issue on the WRA that require further study to come up with the best resolution for solving the obsolecence problems.
19.) COTS - DMSMS Options to support extended production are available from the vendor.
20.) COTS - Extended Warranty or Repair Period is available.
21.) COTS - Third Party Repair is Available.
22.) COTS - A New Source is available.
23.) COTS - Data Rights can be purchased.
24.) Other (details in comments).
Yes
No
Select Option Solution
Select Option Solution (From Pull Down Menu)
1.) There is an approved alternate part on the BOM or SCD.
2.) OEM has Sufficient Stock on Hand (See Table 1).
3.) DLA has stock on hand.
4.) Life of Type Buy (LOT Buy) or Bridge Buy can be done.
5.) Continue to Manufacture (Extend Production).
6.) Another approved manufacturer makes this part.
7.) There is Aftermarket Production Capability - testing may be required.
8.) Parts are available from the Broker Market - testing may be required.
9.) Reclamation is available - testing may be required.
10.) There is a ROHS P/N Change.
11.) A FFF alternate part exist - testing may be required.
12.) A substitute part (not quite FFF) exists - testing may be required.
13.) Part can be emulated - testing may be required.
14.) A prior emulated part exists - testing may be required.
15.) Resolution requires redesign – testing is required.
16.) There is a Tech Refresh / Tech Insertion planned that will solve the obsolescence problem at the SRU and WRA levels.
17.) An obsolescence health check has been performed at the NHA/SRU level and there are other obsolescence issue on the NHA/SRU that require further study to come up with the best resolution for solving the obsolecence problems.
18.) An obsolescence health check has been performed at the WRA level and there are other obsolescence issue on the WRA that require further study to come up with the best resolution for solving the obsolecence problems.
19.) COTS - DMSMS Options to support extended production are available from the vendor.
20.) COTS - Extended Warranty or Repair Period is available.
21.) COTS - Third Party Repair is Available.
22.) COTS - A New Source is available.
23.) COTS - Data Rights can be purchased.
24.) Other (details in comments).

24 August 2015 Attachment 15 DMSMS Case Sheet RFP: N00019-16-R-3001

PID: N00019-15-P1-PMA299-0097

Table 1 Procurement Calculator Instructions:

Fill out the quantities and costs for the items for which you have information. Please leave all other cells blank. If the info does not reflect the entire life cycle of the platform, the solution will be considered a bridge buy until additional info can be gathered.

Table 1 Procurement Calculator
CASE SHEET TRACKING INFORMATION
CDRL #Case Sheet #OMIS OCL #SCD P/NVendor P/NNHA P/NWRA P/NSystem P/N
FY (Fiscal Year) Part Quantities
FYQTY per System# of Production SystemsParts Needed for Production# of Spare SystemsParts Needed for SparesParts Needed for Field Repairs (Default 10%)Anticipated Fallout
(Default 15%)Total Parts Required for USA NavyParts Needed for FMSTotal Parts Required. USA Navy + FMS
FY-1500000
FY-1600000
FY-1700000
FY-1800000
FY-1900000
FY-2000000
FY-2100000
FY-2200000
FY-2300000
FY-2400000
FY-2500000
FY-2600000
FY-2700000
FY-2800000
FY-2900000
FY-3000000
Totals0000000000
Part Buy Quantities ( USA Navy)
LTB DateTotal Parts Required# of Production Systems# of Spare SystemsParts On HandShortfallTesting Cost (If Needed)Unit PriceProcurement Cost
0000$ - 0
Part Buy Quantities (FMS)
LTB DateTotal Parts Required# of Production Systems# of Spare SystemsParts On HandShortfallTesting Cost (If Needed)Unit PriceProcurement Cost
0000$ - 0
Part Buy Quantities ( USA Navy + FMS)
LTB DateTotal Parts Required# of Production Systems# of Spare SystemsParts On HandShortfallTesting Cost (If Needed)Unit PriceProcurement Cost
0000$ - 0
Note: Parts Needed for Repairs is calculated by using a default of 10% of total fleet assets will fail and then 10% of these assets will require a new part. Total fleets assets is based on how many aircraft/systems are projected to be in the fleet at the beginning of a particular fiscal year.
Note: Parts Needed for Anticipated Fallout is calculated by using a Default of 15% of the total number of parts projected to be used in a given year. Total Number of Parts used in a Year = (Total Parts Needed for Production) + (Total Parts needed for Spares Production) + (Total Parts needed for Repairs).
The contents of this form are protected to enable form functions. To unprotect the form, select Tools, Protection, Unprotect Sheet. There is no password.

&A

Table 3 System Calculator

Table 3 System Calculator
SYSTEM P/NITEM DESIGNATORSYSTEM NOMENCLATURE
FYUS NAVYFMS
IS THERE A CONTRACT IN PLACE FOR FY (YES OR NO)# of Production Systems# of Spare SystemsTotal Systems Required for USA NavyIS THERE A CONTRACT IN PLACE FOR FY (YES OR NO)# of Production Systems# of Spare SystemsTotal Systems Required for FMS Navy
FY-1500
FY-1600
FY-1700
FY-1800
FY-1900
FY-2000
FY-2100
FY-2200
FY-2300
FY-2400
FY-2500
FY-2600
FY-2700
FY-2800
FY-2900
FY-3000
Totals000000
15 April 2015LR0D Attachment 15
&ARFP: N00019-16-R-3001

PID: N00019-15-P1-PMA-299-0097

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