Contractor Manpower Reporting Application Sample Clauses

Contractor Manpower Reporting Application. Accounting for Contractor services: The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the contractor will report ALL contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor is required to completely fill in all the information in the format using the following web address: xxxxx://xxxxxxxxxxxxxxxxxx.xxxx.xxxxxxxx.xxx. The Contractor shall invoice for the CMR cost on the final invoice. The required information includes: (1) Contracting office, Contracting Officer, Contracting Officer’s Technical Representative; (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor name, address, phone number, e-mail address, identity of contractor employee entering data; (5) Estimated direct labor hours (including sub-contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-contractors); (7) Total payments (including sub-contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by contractor (and separate predominant FSC for each sub-contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information); (11) Locations where contractor and sub-contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardization nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of Contractor and sub-contractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor will provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period will be the period of performance not to exceed 12 months ending 30 September of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct extensible Markup Language (XML) data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a contractor’s systems to the secure w...
Sample 1Sample 2Sample 3See All (14)
AutoNDA by SimpleDocs
Contractor Manpower Reporting Application. The Contractor and Subcontractors(s) shall report all Contractor and Subcontractor labor hours required for performance of services under this contract via a secure data collection site. The Contractor and Subcontractor(s) will enter CMR data into DoD's Enterprise- wide Contractor Manpower Reporting Application (CMRA) not later than 31 October each year for the just completed Government Fiscal Year (FY). This applies to all services including imbedded services equal to or greater than the simplified acquisition threshold (SAT) provided in support of Task Orders, engineering assignments or modifications authorized after the incorporating of this requirement/clause into the contract. Services are defined in FAR 37.101. The Contractor and Subcontractor(s) are required to completely fill in all required data fields using the following secure web address: xxxxx://xxx.xxxxx.xxx/.
Sample 1Sample 2
Contractor Manpower Reporting Application. (CMRA). The contractor shall report ALL contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the National Guard Bureau via a secure data collection site. The contractor shall completely fill in all required data fields using the following web address: xxxx://xxx.xxxxx.xxx/. Reporting inputs shall be for the labor executed during the period of performance during each Government fiscal year (FY), which runs October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2017. Contractors may direct questions to the help desk at xxxx://xxx.xxxxx.xxx.
Sample 1
Contractor Manpower Reporting Application. (CMRA). The Contractor shall report ALL 76 contractor labor hours (including subcontractor labor hours) required for performance of services 77 provided under this contract for the Office of the Assistant Secretary of the Army (Manpower & 78 Reserve Affairs) via a secure data collection site. The Contractor is required to completely fill in 79 all required data fields using the following web address: xxxx://xxx.xxxxx.xxx/, and then click 80 on “Department of the Army CMRA” or the icon of the DoD organization that is receiving or 81 benefitting from the contracted services. Reporting inputs will be for the labor executed during 82 the POP for each Government fiscal year (FY), which runs October 1 through September 30. 83 While inputs may be reported any time during the FY, all data shall be reported NLT October 31 84 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk by 85 clicking on “send an email” which is located under the Help Resources ribbon on the right side 86 of the login page of the applicable Service/Component’s CMRA website. 88 C.1.1.7. Access and General Protection/Security Policy and Procedures. All Contractor and sub- 89 contractor personnel performing tasks on this PWS shall comply with the local security policies 90 and procedures of the installation where the work is being performed. The Contractor shall 91 provide all information required for background checks to meet installation access requirements.
Sample 1
Contractor Manpower Reporting Application. The Contractor and Subcontractors(s) shall report all Contractor and Subcontractor labor hours required for performance of services under this contract via a secure data collection site. The Contractor and Subcontractor(s) will enter CMR data into DoD's Enterprise- wide Contractor Manpower Reporting Application (CMRA) not later than 31 October each year for the just completed Government Fiscal Year (FY). This applies to all services including imbedded services equal to or greater than the simplified acquisition threshold (SAT) provided in support of Task Orders, engineering assignments or modifications authorized after the incorporating of this requirement/clause into the contract. Services are defined in FAR 37.101. The Contractor and Subcontractor(s) are required to completely fill in all required data fields using the following secure web address: xxxxx://xxx.xxxxx.xxx/. The Contractor and Subcontractor(s) will use the Contractor Manpower Reporting Application (CMRA) Contractor and Subcontractors Users Guide and the Frequently Asked Questions for instructions on how to input the required information. The guides and frequently ask questions are available at the CRMA link above. The prime contractor will flow this requirement to all Subcontractors meeting the SAP threshold and verify with Subcontractors that inputs are being accomplished as required. In accordance with (lAW) CMRA Contractors User's Guide, the only Contractor that can view the Invoice Amount, Direct Labor Dollars and Direct Labor Hours is the user that enters its original data. All other data is public information. Subcontractors(s) will not be able to view prime Contractor data entered for the Invoiced Amount, Direct Labor Dollars and Direct Labor Hours. At no time will any data be released to the public with the Contractors' name and contract number associated with the data. In accordance with the CMRA Subcontractor User's Guide, only the Subcontractor can input its own data. In addition, the only Subcontractor that view the Direct Labor Dollars and Direct Labor Hours is the user that entered its original data. All other data is public information. Prime Contractors will not be able to view Subcontractor's data entered for the Direct Labor Dollars and Hours. In the event a Federal Acquisition Regulation (FAR), Department of Defense Federal Acquisition Regulation Supplement (DFARS) or Air Force Federal Acquisition Regulation Supplement (AFFARS) clause is established to support CMRA implem...
Sample 1

Related to Contractor Manpower Reporting Application

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 1.50 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0150. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. The sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing. Annual Master Contract Sales Report. Upon request, Contractor shall provide to Enterprise Services a detailed annual Master Contract sales report. Such report shall include, at a minimum: Product description, part number or other Product identifier, per unit quantities sold, and Master Contract price. This report must be provided in an electronic format that can be read by compatible with MS Excel. Small Business Inclusion. Upon Request by Enterprise Services, Contractor shall provide, within thirty (30) days, an Affidavit of Amounts Paid. Such Affidavit of Amounts Paid either shall state, if applicable, that Contractor still maintains its MWBE certification or state that its subcontractor(s) still maintain(s) its/their MWBE certification(s) and specify the amounts paid to each certified MWBE subcontractor under this Master Contract. Contractor shall maintain records supporting the Affidavit of Amounts Paid in accordance with this Master Contract’s records retention requirements.

  • Regulatory Applications (a) Western and PNB and their respective Subsidiaries shall cooperate and use their respective reasonable best efforts to prepare all documentation, to effect all filings and to obtain all permits, consents, approvals and authorizations of all third parties and Governmental Authorities necessary to consummate the transactions contemplated by this Agreement. Western and PNB shall use their reasonable best efforts to make all required bank regulatory filings, including the appropriate filing with the Regulatory Authorities. Each of Western and PNB shall have the right to review in advance, and to the extent practicable each will consult with the other, in each case subject to applicable laws relating to the exchange of information, with respect to all material written information submitted to any third party or any Governmental Authority in connection with the transactions contemplated by this Agreement. In exercising the foregoing right, each of the parties hereto agrees to act reasonably and as promptly as practicable. Each party hereto agrees that it will consult with the other party hereto with respect to the obtaining of all material permits, consents, approvals and authorizations of all third parties and Governmental Authorities necessary or advisable to consummate the transactions contemplated by this Agreement and each party will keep the other party appraised of the status of material matters relating to completion of the transactions contemplated hereby. (b) Each party agrees, upon request, to furnish the other party with all information concerning itself, its Subsidiaries, directors, officers and shareholders and such other matters as may be reasonably necessary or advisable in connection with any filing, notice or application made by or on behalf of such other party or any of its Subsidiaries to any third party or Governmental Authority.

  • Commercialization Reports Throughout the term of this Agreement and during the Sell-Off Period, and within thirty (30) days of December 31st of each year, Company will deliver to University written reports of Company’s and Sublicensees’ efforts and plans to develop and commercialize the innovations covered by the Licensed Rights and to make and sell Licensed Products. Company will have no obligation to prepare commercialization reports in years where (a) Company delivers to University a written Sales Report with active sales, and (b) Company has fulfilled all Performance Milestones. In relation to each of the Performance Milestones each commercialization report will include sufficient information to demonstrate achievement of those Performance Milestones and will set out timeframes and plans for achieving those Performance Milestones which have not yet been met.

  • Research Reports Distributor acknowledges that Dealer may prepare research reports relating to the Fund that are not to be used for marketing purposes (“Research Reports”). Distributor hereby authorizes Dealer to use the name of the Fund, Distributor and BREDS in Research Reports.

  • Root-­‐zone Information Publication ICANN’s publication of root-­‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

  • Third-Party Applications Oracle or third party providers may offer Third Party Applications. Except as expressly set forth in the Estimate/Order Form, Oracle does not warrant any such Third Party Applications, regardless of whether or not such Third Party Applications are provided by a third party that is a member of an Oracle partner program or otherwise designated by Oracle as “Built For NetSuite,” "certified," "approved" or “recommended.” Any procurement by Customer of such Third Party Applications or services is solely between Customer and the applicable third party provider. Customer may not use Third Party Applications to enter and/or submit transactions to be processed and/or stored in the Cloud Service, unless Customer has procured the applicable subscription to the Cloud Service for such use and access.

  • Research Use Reporting To assure adherence to NIH GDS Policy, the PI agrees to provide annual Progress Updates as part of the annual Project Renewal or Project Close-out processes, prior to the expiration of the one (1) year data access period. The PI who is seeking Renewal or Close-out of a project agree to complete the appropriate online forms and provide specific information such as how the data have been used, including publications or presentations that resulted from the use of the requested dataset(s), a summary of any plans for future research use (if the PI is seeking renewal), any violations of the terms of access described within this Agreement and the implemented remediation, and information on any downstream intellectual property generated from the data. The PI also may include general comments regarding suggestions for improving the data access process in general. Information provided in the progress updates helps NIH evaluate program activities and may be considered by the NIH GDS governance committees as part of NIH’s effort to provide ongoing stewardship of data sharing activities subject to the NIH GDS Policy.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information.

  • Job Postings and Applications ‌ If a vacancy or a new job is created for which union personnel might reasonably be recruited, the following shall apply: (a) If the vacancy or new job has a duration of thirty (30) calendar days or more, the vacancy or new job including salary range, a summary of the job description, the required qualifications, the hours of work, including start and stop times and days off, the work area and the commencement date shall, before being filled, be posted for a minimum of seven (7) calendar days, in a manner which gives all employees access to such information, provided that no employees shall be entitled to relieve other regular employees under this clause on more than two (2) occasions in one calendar year unless the Employer and the Union otherwise agree in good faith. (b) Notwithstanding (a) above, if a temporary absence is one of less than ninety (90) calendar days, the work of the absent employee may be performed by employees working in float pool positions, where float pools exist. (c) Notwithstanding (a) above, if the vacancy is a temporary one of less than ninety (90) calendar days and the work is not being performed by a float employee, the position shall not be posted and instead shall be filled as follows: (i) where practicable by qualified regular employees who have indicated in writing their desire to work in such position consistent with the requirements of Article 14. Should a vacancy under this Article result in backfilling of more than one (1) vacancy (including the initial vacancy) the second (2nd) vacancy may be filled by an employee registered for casual work unless the Employer and the Union agree otherwise in good faith. If the application of this paragraph requires the Employer to pay overtime to the employee pursuant to Article 19, the proposed move shall not be made. An employee who accepts work under this provision is not eligible to work in another Article 16.01(c) assignment that conflicts with the accepted one. Probationary employees and employees undergoing a qualifying period shall not be considered for a 16.01(c) assignment in a different classification. (ii) by employees registered for casual work in accordance with the casual addendum. (iii) in cases of unanticipated or unplanned temporary absences, such temporary absence may first be filled under (c)(ii) for a period of up to seven (7) days. (d) A part-time employee who has accepted a casual assignment which conflicts with a temporary vacancy referred to in paragraph (c)(i) above shall be considered unavailable for such temporary vacancy. A part-time employee who has accepted a temporary vacancy referred to in paragraph (c)(i) above which conflicts with a casual assignment shall be considered unavailable for such casual assignment. Where an employee declines an offer to work under (c)(i) the Employer need not offer the work again to that employee under (c)(ii), if she/he is also registered for casual work. (e) Existing local agreements will be in force and effect (including termination clauses) unless changed by mutual agreement by the parties at the local level. (f) Where the local agreement covering access to work by part-time employees (former “15.01c”) does not contain a termination clause, the agreement may be terminated on giving of six (6) months’ notice by either party. (g) By mutual agreement, the parties may vary the job posting process set out in Article 16.01.

  • zone Information Publication ICANN’s publication of root-zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!