Jump to content


Member Since 08 Dec 2008
Offline Last Active Today, 01:22 PM

Posts I've Made

In Topic: Contractor Manpower Reporting

30 December 2014 - 08:29 AM

CMRA = Contractor Manpower Reporting Application. The CMRA is a web based application developed by the Army in order to collect data on services that they contract for. Section 807 of the National Defense Authorization Act of 2008 required DoD to provide an annual inventory of contracted services to congress. The other services were using FPDS data to develop their inventory. More recently DoD has gone to standardized systems accross the board. They are calling this the enterprise CMRA (eCMRA). In reality it is the same web based application that the Army developed, now being used by the other services.

In Topic: Contractor Manpower Reporting

24 December 2014 - 10:19 AM

Sounds like you are a contractor.  I work for the Government, and have been using the CMRA for a few years.  Have you tried e-mailing the CMRA help desk?  Here is what I can tell you based on my experience. I don't believe you can create any sort of "enterprise" login for the CMRA.  One of the limitations I noticed with CMRA, at least on the Government side, is that once an individual (COR) "claims" a contract, then only that individual can view the specifics of that contract. There is no way to transfer the contract to anyone else. So if the person who claimed the contract moves to a new job, then their replacement is out of luck as far as using the CMRA to do any research on that contract.  I would imagine their are similar limitations for those individuals with a contractor or subcontractor role in the application. As for your questions regarding administering components, contracting organization, etc., are you referring to the NDAA Elements section?  If so, that is not the contractors responsibility to complete, so you need not worry about it.  As stated on the CMRA Contract Details screen, "Note: COR/COTRs and Contracting Officers are responsible for entering NDAA data. Contractors are not responsible for this data.".  I am not surprised that you have got little to no information from the contracting office, in my experience contracting officers and specialists know very little about the CMRA as they typically don't use it.  You would be better off asking the COR for the contract, as COR's do the bulk of the data input and review on the Government side.  But I will also say that many COR's don't fully understand the CMRA, and in my experience many don't use it at all.  As for training, I have not heard of any such training, and to be honest don't see a need for training, it is a pretty straight forward system to use.

In Topic: Funny or tragic? Part I

16 October 2014 - 12:02 PM

In my experience a lot of people tend to confuse the various justification documents and formats from different parts  (6, 8, 16) of the FAR.  The Army's Computer Hardware Enterprise Software and Solutions (CHESS) program contracts are also Part 16 contracts, but the ordering guides instructs you to prepare justifications using the FAR Part 8 format.  I just ran across a question on the Ask A Professor site when an individual asked about preparing Class Brand Name Justifications for Part 8 buys, and the answer given was that it is possible in accordance with FAR Part 6.  Here is a link to that particular Q&A: https://dap.dau.mil/...estionID=120988

In Topic: SEWP Software Maintenance Question

15 September 2014 - 03:04 PM

Good stuff sdvr!  I had never ran accross that on the SEWP site before. Thanks!

In Topic: SEWP Software Maintenance Question

10 September 2014 - 11:43 AM

Also see this thread:




I tend to use GSA as my yard stick for software maintenance now.  I see how the specific product is classified on GSA.  Does it fall under Special Item Number (SIN) 132-32 or 132-24? Assuming the product is on GSA of course.  Based on that, I make my decision on whether it is a product (paid up front), or a service (paid in arrears).  While that is not an authoritative source, it does give me some backup information that I can use as a rationale for making my decision.