Welcome to the VAMOSC Online Support web site. Here you should find technical notes and information on our product that will assist you in resolving many issues you may have. If you cannot find a solution here, please Contact Us
VAMOSC
and NMCI
What you need to know for a smooth transition!
- How do I import data into Microsoft Excel™?
- How do I resize columns automatically?
- What is the highest classification of data contained on this system?
- Which web browsers are compatible with VAMOSC?
- What’s the difference between accessing VAMOSC and requesting data?
- How long does it take to receive access or to have a data request filled?
- In what format will my data be received?
- What’s the difference between government level access/data and contractor level access/data?
- When I download to excel in NAMSR or NAMSR Plus, some of the Work Unit Codes show up as scientific notation. How can I fix this situation?
- How do I copy data into another application?
- Are Unmanned Aerial Vehicles (UAV) captured in VAMOSC?
- Why does the ATMSR element 5.1.3 - Modification Installs Costs not roll up into 5.1 - Subtotal Modifications Costs?
- Does the ATMSR element 1.2.3 - Support Supplies Costs include Contractor Logistics Support (CLS)?
- What non-cost data are included in the ATMSR Universe?
- What is the difference between the NAMSR and the NAMSR Plus?
- What are the known differences between NAMSR and LMDSS?
- Why do ATMSR and NAMSR report different AVDLR Costs?
- Why do some Aircraft have Labor Hours and BCM data but no AVDLR or Consumable Cost Information?
- What is the difference between Zeroes and Nulls in NAMSR?
- Why are there WUCs with no BCMs but with a corresponding AVDLR Cost in NAMSR?
- 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.)?
- What is the difference between "Unknown" and a null value in the Bureau or Serial Number dimension element?
- Why are flying hours not reported at the TEC/TMS or Major Claimant Level?
- In the NAMSR universe, why do we not add zeros to Work Unit Codes (WUC’s) that are less than 7 digits?
- Are Organizational and Intermediate level aircraft and engine parts data captured in the ATMSR universe?
1. How do I import data into Microsoft Excel™?
Once your query has been completed, click the down arrow next to the Save icon… Save to my computer as… Excel. You will be prompted to name your file.
Note, your browser’s popup blocker must be disabled. To temporarily disable it in Internet Explorer, hold down the Ctrl key. Be sure to hold it down until you are prompted to name your file.
2. How do I resize columns automatically?
Once your query has been completed, click on the column you want to resize, click on the Properties tab, expand the Display section, and select Autofit width.
3. What is the highest classification of data contained on this system?
VAMOSC contains BUSINESS SENSITIVE UNCLASSIFIED information. Detailed depot level data are considered to be business sensitive, and therefore only available to government personnel. However, depot costs are still provided at a summary level, and contractors may be able to get a waiver from the Systems Command (NAVAIR or NAVSEA) to see that business sensitive data via a Memorandum of Agreement. Please contact the VAMOSC program office for more information.
4. Which web browsers are compatible with VAMOSC?
Navy VAMOSC is compatible with the most recent and popular web browsers. Click here to check if your browser is supported.
5. What’s the difference between accessing VAMOSC and requesting data?
Accessing VAMOSC refers to the process where individuals receive user names and passwords so they can access our Oracle database on-line using a front-end program called WebIntelligence. Training is often required for new users of WebIntelligence so it may be far easier to simply request data. In fact, if you suspect you will only need VAMOSC data on an infrequent basis, a data request is the recommended course of action.
6. How long does it take to receive access or to have a data request filled?
Within two to three days you should have access or receive your data.
7. In what format will my data be received?
Your data will be sent via e-mail as an MS Excel™ file attachment unless otherwise specified.
8. What’s the difference between government level access/data and contractor level access/data?
Very little. Detailed depot level data are considered to be business sensitive, and therefore only available to government personnel. However, depot costs are still provided at a summary level, and contractors may be able to get a waiver from the Systems Command (NAVAIR or NAVSEA) to see that business sensitive data via a Memorandum of Agreement. Please contact the VAMOSC program office for more information.
9. When I download to excel in NAMSR or NAMSR Plus, some of the Work Unit Codes show up as scientific notation. How can I fix this situation?
- Run a Query which contains Work Unit Code as a result
- Click on the word “Download” in the upper corner of the query panel
- Click on the option to Save
- Choose a destination for the file
- Rename the file, and change the extension of the file to .txt. For example, Document1.txt
- Open Microsoft Excel
- Click on File, Open. Change the Files of Type to read “All Files.” Open the file that you just saved. For example, Document1.txt
- Use the text import wizard in MS Excel to open the file
- Make sure that Delimited is the box that is checked. Hit next
- Click on comma. Hit next
- Click on the column with the Work Unit Code and switch the column from General to Text
- Click Finish
The file should now show all the Work Unit Codes in text format, which will fix the Scientific Notation problem.
10. How do I copy data into another application?
Once your query has been completed, right-click on the edge of the table and select Copy as text. Then paste (Ctrl-V) the results into any other application, such as Microsoft Word or Excel.
Aviation Questions
1. Are Unmanned Aerial Vehicles (UAV) captured in VAMOSC?
Pioneer (RQ-2) data is contained in the NAMSR Universe.
2. Why does the ATMSR element 5.1.3 - Modification Installs Costs not roll up into 5.1 - Subtotal Modifications Costs?
This element reports the costs for modification installations. Aviation depots normally accomplish these modifications concurrent with other depot maintenance. To avoid double counting these costs they are not included in the summation element 5.1 - Subtotal Modifications Costs.
3. 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.
4. What non-cost data are included in the ATMSR Universe?
The ATMSR provides several metrics against which costs can be evaluated (the "A" 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. These non-cost elements have been expanded to identify Navy and Marine Corps subtotals within the regular and FRS categories.
5. What is the difference between the NAMSR and the NAMSR Plus?
The NAMSR is ideally used to perform high-level queries, whereas the 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 1.5 million records, while the NAMSR Plus has 39 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.
6. What are the known differences between NAMSR and LMDSS?
- 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.
- Years of data available - NAMSR has AV-3M data reported from FY96-FY02. LMDSS reports this data from December 1998 thru January 2003.
- Documentation - NAMSR has a comprehensive User Manual that details processing steps, whereas LMDSS does not.
7. 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. ATMSR AVDLR costs are taken from the CNO Flying Hour Program, and reflect actual transaction prices, be they standard or net price.
8. 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.
9. What is the difference between Zeroes and Nulls in NAMSR?
For the purposes of NAMSR, zero and null values are the same. NAMSR has collected and processed ALL AV-3M and price data for the past 5 years and any zero or null values indicate that there were no Costs, Counts, or Hours associated to that specific WUC, TEC, TMS, TM, or FY.
10. 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.
11. 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.
12. 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).
13. 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).
14. 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). This also means that if you were to pull costs or counts for a particular fiscal year, type/model, and 2 digit WUC, those totals would be greater than the costs or counts for the same fiscal year, same type/model, and 3 digit WUC’s that are children of the original 2 digit WUC. For example, a query for fiscal year 2007, type/model F/A-18, and 2 digit WUC 11 might show AVDLR costs of $16.5M. But, a query for fiscal year 2007, type/model F/A-18, and 3 digit WUC where the corresponding 2 digit WUC is 11 might show AVDLR costs of $15.9M. This indicates that $600K in AVDLR costs were reported only at the 2 digit WUC of 11 in 2007 for the F/A-18. (Note, those were notional, not actual VAMOSC values). The reason VAMOSC does not add the zeros in these cases is due to the large number of additional records that would result, which would effect query performance.
15. 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). Engine maintenance costs are also captured in Intermediate Maintenance Military Personnel Costs (element 2.1.1). 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.
Ships Questions
1. What is the association between the Ship Database and the Shipboard System Database?
There is no direct relationship between the two databases. The shipboard system data do not feed into the ship database, and the ship data do not feed into the shipboard system database. The ship data do inherently include data that are captured at the shipboard system level. The ship data do not, however, include some data that are in the shipboard system database. For example, data that are provided by the system program managers are not included in the ship database, since these data aren't tracked at the individual ship level. Shipboard system database elements that have some PM provided data (i.e., data that aren't included in the ship report) are Other - FM - Program Office, Centrally Provided Material - Program Office, Equipment Rework - Contractor - Program Office, Equipment Rework - Government - Program Office, Other Depot [Maintenance], Engineering & Technical Services - Program Office, Software Support, Replenishment Spares (Issues) - Program Office, and Training - Program Office.2. Why don’t I see all the Navy ships in the VAMOSC database?In past years, VAMOSC only included data for active, full year ships (i.e. ships that were in commission the entire fiscal year) in the ship data. Beginning with the FY98 data, VAMOSC includes all ships - both full year and partial year ships - in the ship databases. The databases are set up so that analysts can query data for only full year active ships if desired by putting a condition on the "Full FY" element. The Naval Reserve Force (NRF) ship data are also in the ship universes beginning with FY98 data, and can also be queried separately if desired by conditioning on the "ship status" element. Also, the ship class averages still include only full FY active ships. The Military Sealift Command (MSC) ship data are contained in a separate database.