-
Are Unmanned Aerial Vehicles (UAV) captured in VAMOSC?
MQ-8B, RQ-2, RQ-7, and RQ-4 data is contained in the NAMSR Universe. In ATMSR, there is limited RQ-4, RQ-7 and MQ-8 data.
-
Does the ATMSR element 1.2.3 - Support Supplies Costs include Contractor Logistics Support (CLS)?
CLS costs have been consolidated into element 7.0 in recognition that CLS may include tasks that are well beyond what is normally associated with organizational-level maintenance. For CNET aircraft, CLS is reported within element 1.2.3 for FY89 and prior.
-
What non-cost data are included in the ATMSR Universe?
The ATMSR Universe provides several metrics against which costs can be evaluated (the "A" series and “P” series elements). These non-cost elements include aircraft numbers, total annual flying hours, barrels of fuel consumed, total average age year end (in months), total average flight hours in life year end, O-level Personnel Counts, and I-level Personnel Counts. These non-cost elements have been expanded to identify Navy and Marine Corps subtotals within the regular and FRS categories.
-
What is the difference between the NAMSR and the NAMSR Plus?
The NAMSR Universe is ideally used to perform high-level queries, whereas NAMSR Plus affords the user access to an increased volume and depth of data and hence greater flexibility in structuring queries of a more in-depth nature. To this end, the NAMSR has approximately 3.1 million records, while NAMSR Plus has over 117 million records. One consequence of the increased volume of data reported in the NAMSR Plus is that users should expect queries in this universe to take considerably longer than a similar query in the NAMSR.
-
What are the known differences between NAMSR and LMDSS/DECKPLATE?
Note that beginning in FY12, DECKPLATE became the sole provider of NAMSR data. Prior to then, data was provided by LMDSS and other sources.
TECs – NAMSR reports data for Aircraft by TMS and TM which includes costs, counts, and labor hours that were reported against the Aircraft, Mission Mounted Equipment, Auxiliary Power Units, Peculiar Support Equipment, and Trainers for that specific TMS or TM. For example, a user that queries data for the F/A-18 will receive all the data reported against the Aircraft TEC (A_), the F/A-18 Mission Mounted Equipment TEC (B_), the F/A-18 Auxiliary Power Unit TEC (P_), the F/A-18 Peculiar Support Equipment TEC (S_), and the F/A-18 Trainer TEC (V_). LMDSS only returns the data reported against the Aircraft TEC (A_). Users in NAMSR have the ability to only select TEC as well
Documentation NAMSR has a comprehensive User Manual that details processing steps, whereas LMDSS does not.
-
Why do ATMSR and NAMSR report different AVDLR Costs?
Net price assumption – NAMSR assumes that a carcass is turned in every time, and that the customer is charged the Net Price each time, which does not always occur. For each BCM, the Net Price of the NIIN is used. ATMSR AVDLR costs are taken from the CNO Flying Hour Program, and reflect actual transaction prices, be they standard or net price. The calculation in ATMSR uses a per hour rate which is another difference between ATMSR and NAMSR.
-
Why do some Aircraft have Labor Hours and BCM data but no AVDLR or Consumable Cost Information?
NAMSR reports only that maintenance and material data that is reported in AV-3M. CLS data that is not reported in AV-3M (requisition data for many of the CLS Aircraft, such as T-45) is not captured in NAMSR.
-
What is the difference between Zeroes and Nulls in NAMSR?
For the purposes of NAMSR, zero and null values are the same. Any zero or null values indicate that there were no Costs, Counts, or Hours associated to that specific WUC, TEC, TMS, TM, or FY.
-
Why are there WUCs with no BCMs but with a corresponding AVDLR Cost in NAMSR?
In cases such as this the Job Control Number on the Maintenance Action Form (MAF) matched with the Record Type 60 (DD1348), but the Work Unit Code on the 2 documents was different. The BCM is reported against the WUC on the MAF, while the AVDLR Cost is reported against the WUC on the Record Type 60.
-
Why do some of the dimension elements (Bureau Number, Serial Number, COG, NIIN, CAGE, Part Number) have null values but report data (BCM, Failure Count, etc.)?
This occurs when there is data for a specific element, but the dimension in question cannot be found. For example, a BCM reported against a CAGE and Part Number, but that CAGE / Part Number combination could not in turn be matched to a Repairable NIIN and COG from the Price File or Haystack. In the case of a Bureau Number with null data, it could be that data was reported against a TEC, such as Common Support Equipment, which does not report against a specific Bureau Number.
-
What is the difference between "Unknown" and a null value in the Bureau or Serial Number dimension element?
A null value implies that the data was not reported against a specific Aircraft (TEC's beginning with "A, K, or N") or Engine TEC (TEC's beginning with "J, R, or T"). "Unknown" denotes that the data was reported against a specific Aircraft or Engine TEC, but that the Bureau Number or Serial Number reported was not valid (for Aircraft a valid Bureau Number is based on a range of values from AIRRS; for Engines any numeric value is considered valid).
-
Why are flying hours not reported at the TEC/TMS or Major Claimant Level?
Flight hours for the NAMSR Plus are taken directly from the ATMSR, which receives and processes data from the CNO and CNET Flying Hour Programs. Due to differences in the TEC's reported in the NAMSR and the ATMSR (the NAMSR has data reported at the "General Equipment" level, e.g. AMA9, whereas the ATMSR does not), it is impossible to accurately report data at any level lower than Type/Model. Additionally, the NAMSR and the ATMSR define Major Claimant differently (the NAMSR reports data against 16 Major Claimants as defined by the OPNAV 4790.2H, whereas the ATMSR reports data for only 4 Major Claimants).
-
In the NAMSR universe, why do we not add zeros to Work Unit Codes (WUC’s) that are less than 7 digits?
Maintenance activity is not always reported at the 7-digit Work Unit Code (WUC) level. If the maintainer who filled out the Maintenance Action Form identified a WUC that was less than 7 digits, then that is exactly what the NAMSR universe reports. Therefore, while some items are reported at the full 7-digit WUC level, others are reported at higher level WUC’s (i.e. fewer than 7 digits). When pulling WUCs beyond WUC 2, you may see a blank/null value appear under the WUCs. This is because that WUC is at a higher level than you are pulling.
-
Are Organizational and Intermediate level aircraft and engine parts data captured in the ATMSR universe?
Yes. O and I level aircraft and engine parts data are captured in AVDLR Costs (elements 1.2.4.1 and 4.1.2.4.1) and Support Supplies Costs (elements 1.2.3 and 4.1.2.3). However, we do not know what portion of those costs are for aircraft or engines, and we do not know the breakdown between Organizational and Intermediate level. Some engine maintenance costs are also captured in Intermediate Maintenance Military Personnel Costs (element 2.1.1) but all costs in ATMSR are mapped to the aircraft TMS.