Attachment_9_-_WinMASP_EOA_Export_QA_Checklist.pdf

WinMASP EOA Export QA Checklist

Purpose: The following checklist is to be completed by MSC personnel when processing WinMASP End of Availability (EOA) Data.

UIC:__________________________________________

REQUIREMENTS

Y N

1. Did the on-site representative provide the complete WinMASP database?

AAPPX10 “APL”:

1. Make sure all HM&E, electronic, and Ordnance APLs/AELs have the correct Ordnance indicator and AINAC code..

2. Are all MLAPL values valid and in the correct format?

3. Are all part number/CAGEs populated?

4. Were all X-RIC PART_NO + CAGE researched to determine if there was already an existing equipment?

5. Were the X-RIC Nomenclatures looked at to ensure that they have the valid AINAC?

6. Were all electronic RIC nomenclatures checked to ensure part numbers match if applicable, and that the part_no does not have the CAGE in it. (8-digit RICs)

AAPPX10 “ AEL”:

7. Ensure that all AELs have a unique PART_NO.

8. Make sure all HM&E, electronic, and Ordnance APLs/AELs have the correct Ordnance indicator and AINAC code.

AAPPX50:

1. Were all the T-NICNs in the AAPPX50 file researched to determine if there was already an existing T- NICN, Navy NICN or NIIN for the same part?

2. Ensure that all “00000” CAGEs were researched and cage was updated accordingly.

3. Are the SM&R fields populated?

4. Is Unit of Issue populated for every niin?

5. Is the AIC field populated for every record containing an AIC_QTY > 0 and vice versa?

6. Are all QTY_PC > 0?

7. Is there a valid BRF for each item?

8. Is the COG and FSC filled in for NIINs?

11. Do all records in the AAPPX50 have a UNIT_PRICE > “0.00”?

14. Are all PART_NO, CAGE, and DESCR filled in for each record?

16. Was the DESCR checked to ensure no asbestos was added.

AAPPX50 “AEL”:

1. AEL items with an ANC of 1 should have a QTY_PC = ‘ ‘, AR, SEL

1. Do all parts related to AELs have unique, identifiable part numbers.

2. Do AEL NIINs that have a part number of TOTALQTY for AELs have a QTY_PC that is not SEL?

V09_2:

1. Was the V09 printed out and reviewed?

2. Do all AELs have an MCC of “X”? Are all MECs = ‘V’ for MCC = “3” or “4”, MECs = ‘N’ for MCC = “2” or “1”? Are all MCC/MECs filled in for Add and Change transactions? Do all APLs have a numeric

MCC?

3. Make sure all HM&E APLs (>8 digits) have an HM&E SAC (always only 5 digits) and electronic APLs (8 digits) have an electronic SAC (usually longer than 5 digits).

WinMASP EOA Export QA Checklist

REQUIREMENTS

Y N

4. Are the ISC, VSAC, and DOVC fields all properly filled in with valid codes for Add and Change transactions?

5. Proper part no/cage information for all Add/Change transactions (make sure any changes to V09 part_no/cage are also made in the PX10/PX50 files as well)

6. HSCs are properly assigned and the EFD and ESD fields are populated?

7. Were the SOA and EOA baseline counts for this ship compared to ensure the baseline stayed intact and was improved?

RECORD COUNTS:

COUNTS: ADDS CHANGES DELETES TOTAL

Text File Before Load

Loaded

DOC

1. Was MASP DOC_ID and DOC_CAGE compared to the CLIP DOC_ID and CAGE?

2. Was DOC without CAGE default with AAPPX10 CAGE?

3. Was DOC_CAGE compared with CLIP VAL_CAGE?

4. Do all records in DOC file contain data?

5. Were there any DOCs not in DOC_RIC? What was disposition?

DOC_RIC

1. Do the DOC and DOC_RIC files have the same number of unique records?

SRI SNSL:

1. Was the SRI_SNSL.TXT file checked to ensure that ALL NIINs had a derivation code?

OSI SNSL:

1. Was CLIP checked to determine whether there are any records with a DERIV = ‘5’ in the OSI_SNSL for this ship? (These are ACR allowances for OSI – there is no deviation code for OSI allowances).

AEL SNSL:

1. If AELs exist as adds on the V09, is there a corresponding AEL_SNSL.TXT file with data present?

Completed by: