M00264-18-R-0028_USMC_Munitions_Requirements_Process_(MCMRP)_Class_V(W).pdf

PDF 506 KB Posted Aug 24, 2018

Attached to: LOGISTICS INTEGRATION DIVISION (LID) Federal contract opportunity
Solicitation number: M00264-18-R-0028
Issued by: United States Marine Corps

About this file

From the source

M00264-18-R-0028 USMC Munitions Requirements Process (MCMRP) Class V(W)

View the file

On GovTribe

Work with this file on GovTribe

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

SEE ADDENDUM

(No Collect Calls)

M0026418R0028 24-Aug-2018

b. TELEPHONE NUMBER

(703) 432-1086

8. OFFER DUE DATE/LOCAL TIME

12:00 PM 25 Sep 2018

5. SOLICITATION NUMBER 6. SOLICITATION ISSUE DATE

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

STANDARD FORM 1449 (REV. 2/2012)

Prescribed by GSA – FAR (48 CFR) 53.212

(TYPE OR PRINT)

(SIGNATURE OF CONTRACTING OFFICER)

ADDENDA X ARE

26. TOTAL AWARD AMOUNT (For Gov t. Use Only )

23.

CODE 10. THIS ACQUISITION IS

SUCH ADDRESS IN OFFER

17b. CHECK IF REMITTANCE IS DIFFERENT AND PUT

BELOW IS CHECKED

TELEPHONE NO.

M002649. ISSUED BY

18b. SUBMIT INVOICES TO ADDRESS SHOWN IN BLOCK 18a. UNLESS BLOCK

7. FOR SOLICITATION

INFORMATION CALL:

a. NAME

HUGHES, JOY K.

2. CONTRACT NO. 3. AWARD/EFFECTIVE DATE 4. ORDER NUMBER

(TYPE OR PRINT)

30b. NAME AND TITLE OF SIGNER 30c. DATE SIGNED 31b. NAME OF CONTRACTING OFFICER

30a. SIGNATURE OF OFFEROR/CONTRACTOR 31a.UNITED STATES OF AMERICA

1 27a. SOLICITATION INCORPORATES BY REFERENCE FAR 52.212-1. 52.212-4. FAR 52.212-3. 52.212-5 ARE ATTACHED.X

25. ACCOUNTING AND APPROPRIATION DATA

1. REQUISITION NUMBER

20.

ADDITIONAL SHEETS SUBJECT TO THE TERMS AND CONDITIONS SPECIFIED.

OFFEROR TO COMPLETE BLOCKS 12, 17, 23, 24, AND 30

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

M3070018RC00051

ARE NOT ATTACHED

27b. CONTRACT/PURCHASE ORDER INCORPORATES BY REFERENCE FAR 52.212-4. FAR 52.212-5 IS ATTACHED. ADDENDA ARE ARE NOT ATTACHED

(BLOCK 5), INCLUDING ANY ADDITIONS OR CHANGES WHICH ARE

SET FORTH HEREIN, IS ACCEPTED AS TO ITEMS:

. YOUR OFFER ON SOLICITATION

28. CONTRACTOR IS REQUIRED TO SIGN THIS DOCUMENT AND RETURN

% FOR:SET ASIDE:UNRESTRICTED OR X

SMALL BUSINESSX

17a.CONTRACTOR/ CODE FACILITY

OFFEROR CODE

MCINCR - RCO

2010 HENDERSON RD

HUGHES, JOY

QUANTICO VA 22134

18a. PAYMENT WILL BE MADE BY CODE

RATED ORDER UNDER

DPAS (15 CFR 700)

13a. THIS CONTRACT IS A

13b. RATING

CODE15. DELIVER TO CODE M30700 16. ADMINISTERED BY

12. DISCOUNT TERMS11. DELIVERY FOR FOB DESTINA-

TION UNLESS BLOCK IS

MARKED

SEE SCHEDULE

14. METHOD OF SOLICITATION

RFQ IFB RFPX

M30700

3300 RUSSELL RD

QUANTICO VA 22134

SHAWN WADE

TEL: 703-784-3429 FAX: 703-784-4917

(703) 784-1929FAX:

TEL: (703) 432-1086 SERVICE-DISABLED

VETERAN-OWNED

SMALL BUSINESS

8(A)

HUBZONE SMALL

BUSINESS

SIZE STANDARD:

$15,000,000

NAICS:

541690

OFFER DATED

29. AWARD OF CONTRACT: REF.

DELIVER ALL ITEMS SET FORTH OR OTHERWISE IDENTIFIED ABOVE AND ON ANY

COPIES TO ISSUING OFFICE. CONTRACTOR AGREES TO FURNISH AND

EMAIL:

TEL:

31c. DATE SIGNED

SEE SCHEDULE

SCHEDULE OF SUPPLIES/ SERVICESITEM NO. QUANTITY UNIT UNIT PRICE AMOUNT

24.22.21.19.

WOMEN-OWNED SMALL BUSINESS (WOSB)

ELIGIBLE UNDER THE WOMEN-OWNED

SMALL BUSINESS PROGRAM

EDWOSB

32g. E-MAIL OF AUTHORIZED GOVERNMENT REPRESENTATIVE

SOLICITATION/CONTRACT/ORDER FOR COMMERCIAL ITEMS

(CONTINUED)

ACCEPTED, AND CONFORMS TO THE CONTRACT, EXCEPT AS NOTED: ______________________________________________________

32a. QUANTITY IN COLUMN 21 HAS BEEN

RECEIVED INSPECTED

32b. SIGNATURE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32c. DATE 32d. PRINTED NAME AND TITLE OF AUTHORIZED GOVERNMENT

REPRESENTATIVE

32e. MAILING ADDRESS OF AUTHORIZED GOVERNMENT REPRESENTATIVE 32f . TELEPHONE NUMBER OF AUTHORIZED GOVERNMENT REPRESENTATIVE

37. CHECK NUMBER

FINALPARTIALCOMPLETE

36. PAYMENT35. AMOUNT VERIFIED

CORRECT FOR

34. VOUCHER NUMBER

FINAL

33. SHIP NUMBER

PARTIAL

38. S/R ACCOUNT NUMBER 39. S/R VOUCHER NUMBER 40. PAID BY

41a. I CERTIFY THIS ACCOUNT IS CORRECT AND PROPER FOR PAYMENT 41b. SIGNATURE AND TITLE OF CERTIFYING OFFICER 41c. DATE

42a. RECEIVED BY (Print)

42b. RECEIVED AT (Location)

42c. DATE REC'D (YY/MM/DD) 42d. TOTAL CONTAINERS

STANDARD FORM 1449 (REV. 2/2012) BACK

Prescribed by GSA – FAR (48 CFR) 53.212

AUTHORIZED FOR LOCAL REPRODUCTION

PREVIOUS EDITION IS NOT USABLE

SEE SCHEDULE

20.

SCHEDULE OF SUPPLIES/ SERVICES

21.

QUANTITY UNIT

22. 23.

UNIT PRICE

24.

AMOUNT

19.

ITEM NO.

M0026418R0028

Section SF 1449 - CONTINUATION SHEET

PWS

PERFORMANCE WORK STATEMENT

FOR LOGISTICS INTEGRATION DIVISION (LID)

UNITED STATES MARINE CORPS MUNITIONS

REQUIREMENTS PROCESS (MCMRP) CLASS V (W)

1. BACKGROUND

1.1. The United States Marine Corps (USMC), as required by the Office of the Secretary of Defense (OSD), quantifies munitions requirements in accordance with DoD Instruction 3000.04, Department of Defense Munitions Requirements Process (DoD MRP). DoD Instruction 3000.04 establishes policy, assigns responsibilities, and prescribes procedures for generating, developing, and disseminating DoD MRP products. It is DoD policy to establish a Total Munitions Requirement (TMR), with guidance from Secretary of Defense Memorandum, “Guidance for the Development of the Force (GDF)”, Secretary of Defense Memorandum, “Guidance for the Employment of the Force (GEF)”, and Under Secretary of Defense for Acquisition, Technology, and Logistics (USD (AT&L)) Memorandum, “DoD MRP Implementation Guidance (DoD MRP IG)” that arm military forces to perform their assigned military missions. Additionally, it is incumbent upon the Services to ensure that munitions requirements developed are visible, accessible, and understandable to the rest of the Department (except where limited by law, policy, or security classification).

1.2. The USMC, through the Munitions Requirements Class V (W) process, determines the USMC’s munitions inventory requirements. The purpose of the MCMRP Class V (W) process is to develop munitions requirements for the USMC ground forces in accordance with the DoD MRP. The requirements are used to develop munitions procurement and maintenance plans and justification of budget requests in the services Planning, Programming, Budgeting and Execution process (PPBE).

1.3. The MCMRP methodology is compliant with the DoD MRP which currently defines the TMR as the sum of the War Reserve Munitions Requirement (WRMR) and the testing and training requirement (TTR). The WRMR is defined as the sum of combat requirement (CR), current operations / forward presence requirements (CO/FPR), and strategic readiness requirement (SRR). Aligned to the component requirements definitions in the DoD MRP, USMC CR consists of munitions required to equip a specified force structure to its designated military capability to meet Combatant Commander requirements in accordance with DoD guidance; CO/FPR consists of munitions required to arm forces to conduct current operations and meet forward presence obligations in accordance with the GEF; SRR consists of munitions needed to arm forces not committed to support combat operations in the assigned major combat operations, as well as those in the strategic reserve, and any additional munitions requirements generated from treaties or statutory obligations to allies; and TTR consists of munitions needed to train the force and test weapon systems. These elements may change as guidance is updated.

1.4. The requirements for those weapons included in the MCMRP process are computed by the contractor under the purview of the Logistics Integration Division (LID). Inputs include scenario descriptions and force employments, weapon inventories, platform and weapon capabilities, weapon Initial Operating Capability (IOC) date, targets, target priorities, and mission parameters and tactics. Most of the requirements are threat-based; however, some are Level-of-Effort (LOE) requirements. Threat-based MCMRP computations are based on destroying the enemy threat allocated to the USMC (ground side only). LOE munitions computations provide weapons to sustain a specific number of days of combat and are the product of rounds per shooter per day, number of shooters, and number of days.

1.5. Computer models have been developed to assist in developing inventory requirements. Currently there are three over-arching computer models in the MCMRP modeling suite. They are the Class V(W) WRMR Software System (WRMRSS), Ammunition Funding Analyzer (AFA), and the Requirements Generator (ReqGen). The MCMRP Class V (W) modeling suite is operational on Personal Computers (PC’s) and has been provided with a Graphical User Interface (GUI) to simplify use. These models contain over 300,000 lines of code in C, C+, VBA, and XAML.

2. SCOPE

2.1. This Performance Work Statement (PWS) specifies the technical and program support required for the United States Marine Corps Munitions Requirements Process (MCMRP) Class V (W) in accordance with the Office of the Secretary of Defense (OSD) and the Office of the Commandant of the Marine Corps (CMC) guidance.

2.2. The scope of work required by this contract requires operation and sustainment of methods and resources to produce ammunitions requirements models, analysis and modification of the models, database development and management, validation, verification and possibly accreditation, data entry, requirements computation, assessment of results, documentation and on-call munitions requirements analysis to support the Logistics Integration Division (LID), Capabilities Development Directorate (CDD), Deputy Commandant Combat Development & Integration (DC CD&I) as authorized by Marine Corps Order (MCO) 8007.1A which delegates responsibility to LID for the MCMRP Class V (W) process.

3. GENERAL REQUIREMENTS

3.1. Contractor Qualifications.

3.1.1. The MCMRP Class V (W) requires several specialized disciplines under one service contract to successfully complete all phases; highly analytic/applied mathematics discipline, application of analytic techniques and modeling warfare concepts-of-operations, experience in the MCMRP modeling suite or significant experience in mathematical modeling methods, data collection and analysis work in programs of similar complexity and scope, computer science and software design, and experience in USMC warfare, warfare systems and munitions capabilities, performance, attributes, employment procedures and effects.

3.1.2. The contractor must understand the principles of applied math and computational techniques upon which the MCMRP system software was designed and be able to operate and make changes to the system software modeling code. All of the models described within this document will be furnished to the servicing contractor in a ready to use status as Government Furnished Equipment (GFE). All changes to the models and the methodologies that the contractor makes during the period of performance of the contract must be thoroughly tested and documented by the contractor and provided as a deliverable to the LID. Contractor must adhere to the Risk Management Framework (DoDI 8510.01) in the electronic manipulation of GFE data and to address any information assurance related configuration changes that may result from such reviews.

3.1.3. The effort will require the Contractor to have recent experience with developing munitions requirements numbers (not Joint Capabilities Integration and Develop System requirements), gain access to numerous classified and unclassified systems/databases in accordance with mission requirements, and be familiar with USMC organizational structure, weapon systems, and munitions. The Contractor will be working closely with Ammunition Integration Officer, LID, CDD, DC CD&I in planning the MCMRP update cycle. The LID will be a conduit to most organizations pull/push of data to support the MCMRP, but the Contractor may have to communicate with other organizations to obtain information and data, and to document justification for assumption and data changes.

Primary examples include Operational Analysis Division and Total Force Structure Division of CD&I for scenario data and force composition used in modeling, and Joint Technical Coordination Group for Munitions Effectiveness to ensure integration of the Joint Munitions Effectiveness Manual methods for munitions effectiveness estimates with the MCMRP computational methods.

3.1.4. MCMRP documentation regarding models, database and reports on POM requirements are the responsibility of the contractor. The documents published in support of the MCMRP are listed in paragraph C-6, and are subject to change.

3.2. Security Requirements.

3.2.1. ALL CONTRACTOR PERSONNEL REQUIRING ACCESS TO CLASSIFIED INFORMATION AND

ASSIGNED TO THIS PROGRAM SHALL POSSESS A SECRET CLEARANCE. The Prime Contractor and all Sub-contractors (though the Prime Contractor) shall certify in writing to the Government that personnel supporting this contract are "Qualified U.S. Contractors" per DoD Directive 5220.22-M Chapter 2 Section 2.

Qualified U.S. Contractors are restricted to U.S. citizens, persons admitted lawfully into the United States for permanent residence, and are located in the United States. All personnel identified on the certification and/or supporting this contract shall be in compliance with Department of Defense (DoD), Department of the Navy (DoN), and Marine Corps Information and Personnel Security Policy to include completed background investigations (as required) prior to classified performance. This contract shall include a DoD Contract Security Classification Specification (DD-254 Form) as an attachment. The Contractor shall have a valid Secret Facility Clearance prior to classified performance or classified meetings at the Contractor’s facility. The Government shall assist the Contractor in gaining access to Government agencies and installations related to the systems in question. The Contractor shall ensure that the employees are on the approved Government access list prior to entering any access controlled area.

The Contractor shall notify the Government by written notice within 24 hours of Contractor personnel being added or removed from the access control list.

3.2.2. The Contractor shall be required to store, access and handle unclassified and classified (SECRET) information and documentation. Overarching security requirements and Contractor access to classified information shall be specified in the DD-254 form. Security management efforts, inclusive of retention of clearances and document handling and storage, are not to be charged to the Government and should be considered part of the Contractor’s indirect labor base. The Government will not be responsible for getting subcontract companies cleared through any security measures. The Government will sponsor the Contractor’s access to other Government facilities as required.

Additional Contractor badging requirements will be delineated on the DD-254. The Contractor shall access Communication Security (COMSEC) information and Secured Internet Protocol Router Network (SIPRnet) at their facilities.

4. Tasks. The contractor shall provide munitions inventory requirements and overarching analysis with supporting justification to inform decision. The results will be utilized to assess program inventory objectives and priorities for munitions programs investment strategies and to support USMC programming. Documentation of this effort by the contractor will provide traceability for these results. In fulfilling the requirements specified herein, the services shall demand ingenuity, creativity, careful attention to detail and sound study. Where appropriate, the Contractor shall provide recommendations to the Government on how to make the MCMRP process and products more meaningful and operationally relevant. The Contractor shall support all MCMRP MRP/POM cycles in progress during the period(s) of performance. Contractor must review and understand MCMRP requirements/instructions each cycle.

The procedures of execution within each of these MCMRP cycles may be similar and overlapping, yet could change drastically. The Contractor must be able to adapt to these changes.

4.1. Task 1: Analysis

4.1.1. The Contractor will be required to provide on-site support as needed. This may consist of information exchange that warrants in-person meeting, and participation in formal Ammunition Working Group events in accordance with MCMRP activities. On-site Support may include demonstrating use of modeling tools such as the Shortfall Calculator and Ammunition Funding Analyzer, providing insight into modeling tools, methodologies, and sharing other relevant information as necessary.

4.1.2. The Contractor shall attend and support combatant command Phased Threat Distribution (PTD) working groups, typically 1-3 per year. This requires in-depth knowledge and understanding of targets, weaponeering, target pairing, munitions capabilities and effects, and USMC capabilities. The Contractor shall ensure that threat data is entered into the models and a detailed analysis of the MRP threat allocations is used to prepare MRP change recommendations. Any discussions, issues, assumptions, methodology, and database changes related to the models shall be documented and taken for action if directed by the LID. Additionally, when requested provide a PTD Comparison that will identify an accurate and easily identifiable method of comparing two or more PTD’s with summary narratives of changes.

4.1.3. The Contractor shall provide on-call support to the LID. Be prepared to support short notice MCMRP tasks, changes, updates, and surge during periods of high operational tempo.

4.1.4. Once all MRP data is collected, make computations to develop ammunition requirements and prepare output reports and brief. The Contractor shall deliver MRP Reports below as directed by LID. Submission dates and reporting requirements will be derived from Joint Staff and/or OSD guidance each cycle. Guidance can be from the current DoD MRP Instruction, Implementation Guidance, Executive Steering Group direction, and Joint Staff offices. Note, the mix of reports and data elements are subject to change at any time and contractor must be able to adapt.

4.1.4.1. Total Munitions Requirement (TMR). There are multiple versions of the TMR. One version is directed by OSD/Joint Staff guidance, and the others are directed by the LID to support internal Marine Corps use. Regardless of version, the TMR is a summary of all ammunition requirements. Contractor must be prepared to provide an abbreviated unclassified version, and multiple classified versions.

4.1.4.2. Unconstrained Reports. Reports are in accordance with applicable instruction and guidance. Common reports include Out Year (OY) TMR and OY consumption. The unconstrained run basically removes financial constraints on munitions inventory or availability. The unconstrained TMR represents the optimum mix of munitions to attrite the allocated threat and is the official source of munitions requirements. While a majority of the munitions in the unconstrained run are the most capable variants of the USMC ground mix, some legacy munitions may be modeled on a case by cases basis, determined by the LID.

4.1.4.3. Constrained Reports. Reports are in accordance with applicable instruction and guidance. Common reports include Near Year (NY) and OY Total Munitions Assessment (TMA), and NY and OY consumption. The purpose of the constrained run is to support the development of the OSD required sufficiency assessments used to inform programmers and DoD leaders during the POM deliberations. The constrained run limits the model to current inventory and the projection of future inventories based on a specific budget. The results of the constrained run are called the constrained munitions assessment. The sufficiency assessment will identify output changes between the constrained and the unconstrained run and other risk metrics relevant to the modeling methods. Operational planners assess these metrics against their operational plans in order to prepare a munitions assessment.

4.1.4.4. Total Munitions Assessment (TMA) and Sufficiency Assessment. This report may vary each cycle, but primarily serves the following functions: identifying targets not killed; time required to kill assigned targets; and estimated losses. The Contractor shall deliver the TMA/SA no later than 30 days after completion of the computations. Government shall review within 10 days. Availability of the data and DoD submission dates may encroach upon this timeline.

4.1.4.5. TMA Sufficiency Assessment. The TMA Sufficiency Assessment shall, as directed by OSD, validate that the TMR is sufficient to support the entire Marine Corps ground munitions requirement. The final report shall be submitted annually after the completion of the MCMRP computation phase and shall include all changes included in the computations and a record of all submissions and issue resolution. Contractor format is acceptable with concurrence of the LID. Annual updates shall be submitted on a similar basis.

4.1.4.6. MCMRP Summary of Requirements. The set of munitions requirements approved for use in POM/Budget development shall be summarized for promulgation by LID. A summary report shall list the requirement for each MCMRP weapon for each year computations are done, providing the value for each component of the requirement (CR, CO/FPR, SRR, WRMR, TTR, TMR) and shall include detailed results for combat loadout, combat expenditure, training, treaty obligations, maintenance pipeline, etc.). Preliminary reports shall be submitted after each interim model run conducted throughout the MCMRP cycle. Note, the components are subject to change.

Contractor format is acceptable with concurrence of the LID.

4.1.4.7. MCMRP Combat Loadout Summary. The combat loadout computed for development of the MCMRP requirements will be documented (pre-MCO and post-MCO). For each weapon the report shall list the number of platforms by class and how many are allocated to support the MRP components, the loadout by class and by year, and the computed value of the combat loadout. Preliminary reports shall be submitted after each interim model run conducted throughout the MCMRP cycle. The final shall be submitted annually after the completion of the MCMRP computation phase. The report shall include all weapon types for each year computations are performed. Contractor format is acceptable with concurrence of the LID.

4.1.4.8 Operational Plan (OPLAN) Requirements Report. The results of OPLAN requirements computations shall be documented. OPLAN requirements are calculated using a data base specifically tailored to a specified OPLAN. This run typically occurs once in an annual cycle and is linked to the final database that reflects the published requirements. Results shall be documented in an analysis report which may be as detailed as a Summary of Requirements Report, and may also require a Daily Munitions Expenditure Report, Target Destruction Analysis Report, Munitions Selection Analysis Report, or Comparison Report. The report shall be submitted annually after the completion of the MCMRP computation phase. Contractor format is acceptable with concurrence of the LID.

4.1.4.9. Munitions Consumption Dashboard. This is a spreadsheet that depicts a graphic representation used to analyze consumption data for each MRP. It provides an overview, detailed kills by munitions type and target element, expenditures by munition type and by target element, expenditures per kill by munition and target type, and summary tabs.

4.1.4.10. Shortfall Calculator. Contractor will update and provide the Shortfall Calculator with each new TMR and as requested. The contents and capabilities of the Shortfall Calculator change often and Contractor must be able to incorporate changes for new data requirements. Current capabilities include inventory projections, funding shortfalls, charts, and the ability to conduct “what-if” drills for funding changes.

4.1.4.11. Incremental Combat Requirements. Providing combat requirements for individual modelled plans incrementally (normally in 10 day increments) assists component commands and supporting establishments with conducting logistics supportability analysis. These reports shall be provided as necessary.

4.1.4.12. TMR Comparison and Output Brief. This requires comparison between TMR elements of two or more sets of data, and summary of all changes. This normally consists of comparison of each Department Of Defense Identification Code with individual notes, and a summary of major changes common throughout the documents being compared.

4.1.4.13. Combat Planning Factors. Derived from modelling of the combat requirement, combat planning factors are used to generate requirements for the other WRMR elements. The combat planning factor reports identify combat load and consumption data by weapon type broken down by ground combat element (GCE) and non-GCE. The consumption rates are broken out into assault and sustain rates. Current formats are sorted by weapons type and by ammunition type. It also include ancillary rates for applicable ammunition.

4.1.5. The Contractor shall submit a monthly progress report to the COR no later than the tenth (10th) day of the following month for work accomplished from the first (1st) through the final calendar day of the previous month.

This report shall be provided in electronic media compatible with conventional MS Office application. The report shall include at a minimum the following information:

• Comparison of planned versus actual task order performance by PWS and WBS elements, by Division;

• Task progress during the past month, plan for the forthcoming month;

• Problems (actual or anticipated) requiring Government action and summary of action required;

• Travel costs, including purpose of trips, duration and related actions, by Division;

• Total contract staffing by position and assignment;

• Personnel turnover, utilization of subcontractor, and future staffing projections; and

• Deliverables accepted or rejected, inclusive of the final day of the month, as well as the reason for rejection and timeline for resubmission.

4.1.6. Provide final report documentation for each cycle. This is a list of products summarizing all details of each MRP cycle. This list may vary each cycle, and additional products may be required as necessary.

• Executive Summary

• Process Briefing

• Methodology Briefing

• Database Report

• Possible Input Gaps

• Compilation Files of Input Data Updates

• Guides for Updating Input Exhibits

• User Manual for WRMR Software System

• Tutorial for WRMR Software System: Data Management Utility

• Overview for WRMR Software System

• Flow Diagram for WRMR Model

• Commented Source Code for WRMR Software System

• User Manual for Requirements Generator

• Requirements Generator 101

• Commented Source Code for Requirements Generator

• User Manual for Ammunition Funding Analyzer

• Ammunition Funding Analyzer 101

• Commented Source Code for Ammunition Funding Analyzer

4.1.7. No later the 5 working days upon conclusion of any trip or working group participation, provide a summary report of all discussions, topics, actions, and other relevant information as it pertains to the Contractor participating in MCMRP activities.

4.2. Task 2: Maintenance

Munitions requirements generation will require the Contractor to ensure databases and models (WRMR, ReqGen, and AFA) are updated with all applicable information to determine combat expenditures, combat loads for the various forces, and all other MRP reporting. The LID will provide some products and corresponding documentation to the Contractor as Government Furnished Information (GFI), and as necessary, Contractor shall coordinate with all applicable entities for data inputs required to develop the Total Munitions Requirement and all associated reports.

All changes to the models and the methodologies that the Contractor makes shall be thoroughly tested and documented. Contractor is responsible for maintaining, updating, testing, and all other functions pertaining to the models. Models are subject to being verified, validated and accredited. All aspects of requirements generation including processes, procedures, documentation, models, etc., are subject to audit from multiple agencies.

Deliverables include WRMR model database report and compilation files, software delivery, and regression test reports, as described below.

4.2.1. MCMRP Data Base Report. The MCMRP database shall be documented or revised based on data changes approved for the POM computations. The database report shall be organized in a manner to allow for easy comparison with past cycle input submissions with intuitive categories. The report shall be submitted as needed, at least annually, after the completion of the MCMRP computation phase and shall represent all changes included in the computations as previously submitted in the compilation report (Deliverable C-6.4.1)). Contractor format is acceptable with concurrence of the LID. The report shall be composed of the following categories: Background and Scenarios; Formations / Forces; Munitions; Threat; Enemy IADS (if applicable); Cost Data.

4.2.2 Results of Parametric Analysis Report. The results of parametric analysis shall document the parametric runs made to examine the impact of data base and assumption changes on the requirements. Each report shall describe the data changes investigated in the analysis and compare results of the parametric run with the approved MCMRP, along with an explanation of why changes occurred. Results shall be documented in an analysis report which may be as detailed as a Summary of Requirements Report, a Daily Munitions Expenditure Report, Target Destruction Analysis Report, Munition Selection Analysis Report, Comparison Report, or a short report specifically tailored to the analysis performed. The report shall be submitted annually after the completion of the MCMRP computation phase. Contractor format is acceptable with concurrence of the LID.

4.2.3 Software Development Plan. The software development plan shall document model descriptions, commented source code, and copies of both the source code and executable software. The report shall be submitted annually after the completion of the MCMRP computation phase. Updates shall be submitted to maintain consistency with model changes and improvements. Contractor format is acceptable with concurrence of the LID.

5. FACILITIES, TRAVEL AND OTHER DIRECT COSTS

5.1. Services shall be performed primarily off-site at the Contractor’s facilities with occasional on-site visits at the Government site. The Contractor shall provide suitable infrastructure to manage program requirements throughout the contract’s period of performance to support the scope of services.

5.2. CONUS and OCONUS travel must be reimbursed in accordance with the Joint Travel Regulation (JTR). All travel must be approved in advance by the designated COR under this contract. Per Diem shall be in accordance with http://www.defensetravel.dod.mil/site/perdiemCalc.cfm. Local travel within a 50-mile radius of the Contractor’s location shall also be reimbursed per the JTR. The expected level of travel is detailed below:

OCONUS Number of Trips (Base)

Number of Trips (Option 1)

Number of Trips (Option 2)

Duration (days)

Combatant Command HQ location 1-3 1-3 1-3 5

CONUS Number of Trips (Base)

Number of Trips (Option 1)

Number of Trips (Option 2)

Duration (days)

Quantico, VA, (MCMRP Class V (W) Working Group)

4 per year 4 per year 4 per year 5

Note: Duration does not include travel days.

6. DELIVERABLES, HANDLING, AND USE OF ITEMS AND INTELLECTUAL PROPERTY.

6.1. Deliverables are identified within the Tasks and summarized within this PWS/contract. Execution of the PWS tasks will frequently yield deliverables in the form of, but not limited to, reports, papers, and presentation packages such as PowerPoint briefings, slides, computations with backup information, databases and database-related items, website and website-related items, graphics, visual aids, and meeting minutes. Reports shall contain information in sufficient detail to ensure that a professionally qualified third party can follow the logic of the report(s). Government review comments shall be incorporated into the final deliverable in the form of revisions, deletions, additions, and corrections.

6.2. The Contractor shall not use Contractors or third-party proprietary items and/or materials unless otherwise agreed upon in writing by the Contracting Officer prior to the commencement of the work.

6.3. No data, materials, information or other items (hereinafter singularly or collectively “Items”) created or provided expressly for this PWS shall be used by the Contractor for any purpose other than those that are in support of, or for performance under, this PWS without the prior written permission of the Contracting Officer. The Contractor is obligated to protect from unauthorized use or disclosure all Government confidential or classified material and/or Government-owned proprietary, and/or Personally Identifiable Information or Personal Privacy, Items obtained in the course of performance under the Government contract, as long as such Items remains proprietary, confidential, sensitive, or classified. Any information obtained in the course of duties, or the performance of services, under this contract including, but not limited to, information that may be made available for use that related to the technical data, trade secrets, processes, operations, style of work, or apparatus, or to the technical data, statistical data, amount or source of any income, profits, losses, or expenditures of any person, firm, partnership, corporation, or association is included in this clause (and with “items”). Contract personnel shall not publish, divulge, disclose, or make known Items in any manner, or to any extent not authorized by the Contracting

Officer. When the Contractor’s need for any Items ends, the Items shall be returned promptly (within ten (10) business days) to the appropriate Government program personnel. However, the obligation not to discuss, disclosure, release, reproduce or otherwise provide or make available such Items, or any portion thereof, shall continue, even after completion of this contract. Any actual or suspected unauthorized use, disclosure, release, or reproduction of any Items, or violation of this agreement, of which the company or any employee is or may become aware, will be reported promptly (within one (1) business day) to the Contractor’s Program Manager, who will inform the Contracting Officer with five (5) business days of receiving such report.

6.4. All items and/or deliverables generated by the Contractor under this PWS, and all associated intellectual property, in whatever form, created, generated, or produced under this PWS shall become the property of the U.S.

Government/Marine Corps and not the Contractor, subcontractor, or individual author or researcher; therefore, the U.S. Government/Marine Corps shall have the irrevocable, royalty-free, worldwide right to use, modify, reproduce, perform, display, release, or disclose such items, in whole or in part, in any manner, and for any purpose whatsoever, and to have or authorize others to do so. The contract will include DFARS 252.227-7020.

6.5. All Contractor developed databases and database related items, all website and website-related items, analyses, studies, applications, information, and all associated intellectual property, completed or in progress under the contract shall be solely and fully owned by the Government. During the transition period, the Contractor shall turnover such documents, information, and all associated intellectual property, to the Government if not already delivered.

6.6. Distribution, Media and Format. Unless otherwise directed by the COR, see the PWS for required distribution, media, and format. The Marine Corps shall have unrestricted access and use of all deliverables upon delivery. The Contractor shall provide all deliverables in a version, format, and media used/useable and modifiable by the Marine Corps.

7. ENTERPRISE-WIDE CONTRACTOR MANPOWER REPORTING APPLICATION (ECMRA)

7.1. The Contractor shall report ALL contract labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the MCMRP CLASS V (W) support via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: https://doncmra.nmci.navy.mil.

7.2. Reporting inputs will 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. Contractors may direct questions to the help desk, linked at: https://doncmra.navy.mil.

8. NON-DISCLOSURE AGREEMENTS

8.1. All Contractor personnel receiving access to Government data or data from another Contractor through this effort must provide a signed non-disclosure statement prior to start of services. This statement shall be submitted to the Contracting Officer with a copy to the Contracting Officer’s Representative (COR). All non-disclosure agreements shall be signed by all Contractor personnel involved in this effort and returned within five (5) business days after receipt of award.

9. AUTHORITY OF GOVERNMENT PERSONNEL

9.1. The Contracting Officer is the only person who can legally modify a resulting contract or obligate the Government for expenditure of funds.

9.2. Only the Contracting Officer has the authority to authorize deviation from the terms and conditions of any resulting contract, including deviations from specifications and requirements. In the event the Contractor does deviate, without written approval of the Contracting Officer, such deviations shall be at the risk of, and any cost related thereto shall be borne by the Contractor. Any matter concerning a change to the scope, prices/costs, terms, or conditions of this contract shall be referred to the Contracting Officer.

10. Performance Requirement Summary (PRS)

Task Deliverable Performance Standard

Acceptable Quality Level (AQL)

Surveillance Method

Task 1: Analysis

4.1.1. Provide on-

Site support (as needed)

Participate in AWG, and other necessary in-person meetings approximately 4 times/year

Provide SME support and contribute during applicable events

Participation: 100%

Effectiveness: 95%

10.1.a 10.1.d

4.1.2. Attend and

support PTD Working Groups

Gather all data required to model requirements; 1-3 times/year

Provide SME support and perform all modeling activities

Participation: 100%

Effectiveness: 95%

10.1.a 10.1.d

4.1.3. Provide on-

call support

Respond to telephonic and/or email inquiries in a timely manner

Contractor available and accurately responds to unscheduled inquiries during normal working hours throughout the contract period

Accuracy: 95%

Timeliness: 95% 10.1.a – 10.1.e

4.1.4. Make

computations to develop ammunitions requirements and prepare output products

Many primary and additional reports identified within Para 4.1.4.

Provide accurate MRP data in a timely manner according to the PA&M for each cycle, and update as required.

Accuracy: 100%

Timeliness: 100% 10.1.a – 10.1.f

4.1.5. Provide

monthly progress report

Submit reports as identified in Para 4.1.5

Reports will provide status of MRP actions.

Accuracy: 95%

Timeliness: 95%

10.1.d

4.1.6. Provide final

report documentation

Submit reports and documents identified in Para 4.1.6

These reports are instrumental with documenting the process and for auditing

Accuracy: 98%

Timeliness: 95%

10.1.d 10.1.f

4.1.7 Trip report Within 5 working

days upon completion of any trip, provide a

Reports capture pertinent interactions and

Accuracy: 95%

Timeliness: 95%

10.1.d relevant summary report perceptions of the Contractor

Task 2: Maintenance

4.2. Maintain all

models, including VV&A when applicable

Model maintenance is continuous, and VV&A is random

Models updated and operational providing accurate data; maintain VV&A of models

Accuracy: 100%

Timeliness: 98%

10.1.f

4.2.1/4.2.2/4.2.3 Maintenance Reports

Submit reports as identified in Para

4.2.1 – 4.2.3

Information required for continuity and audit.

Accuracy: 98%

Timeliness: 95%

10.1.d 10.1.f

10.1. Surveillance Methods. Surveillance of Contractor performance is the method used by the Government to determine whether the contractor is effectively and efficiently complying with all terms and conditions of the contract. The below listed methods of surveillance shall be used in the administration of this PRS

a. Direct Observation – Execution of this contract involves frequent communication between the contractor and customer enabling continuous surveillance of performance.

b. Validated user/customer complaints – Formal

c. Progress or status meetings.

d. Analysis of contractor’s progress reports and outputs.

e. Performance reporting.

f. Audit

10.2 Consequences of non-compliance includes not exercise options, negative CPARS entry, and termination.

ITEM NO SUPPLIES/SERVICES QUANTITY UNIT UNIT PRICE AMOUNT

0001 12 Each Task 1- Analysis

FFP

IAW with PWS Task 1 FOB: Destination

PURCHASE REQUEST NUMBER: M3070018RC00051

NET AMT

0002 12 Each Task 2- Maintenance

FFP

IAW with PWS Task 2

Travel

COST

Travel in support of line items 0001 and 0002 shall be conducted IAW JFTR. All travel must be approved in advance by the COR and in writing. The travel exenses incurred under the line item shall not exceed:: $4,275.00

ESTIMATED COST

1001 12 Each OPTION Task 1- Analysis

FFP

IAW with PWS Task 1

1002 12 Each OPTION Task 2- Maintenance

FFP

OPTION Travel

COST

Travel in support of line items 1001 and 1002 shall be conducted IAW JFTR. All travel must be approved in advance by the COR and in writing. The travel exenses incurred under the line item shall not exceed:NTE: $4,275.00

2001 12 Months OPTION Task 1- Analysis

FFP

2002 12 Months OPTION Task 2- Maintenance

FFP

OPTION Travel

COST

Travel in support of line items 2001 and 2002 shall be conducted IAW JFTR. All travel must be approved in advance by the COR and in writing. The travel exenses incurred under the line item shall not exceed: $4,275.00

3001 12 Each OPTION Task 1- Analysis

FFP

3002 12 Each OPTION Task 2-Maintenance

FFP

OPTION Travel

COST

Travel in support of line items 3001 and 3002 shall be conducted IAW JFTR. All travel must be approved in advance by the COR and in writing. The travel exenses

4001 12 Months OPTION Task 1- Analysis

FFP

4002 12 Each OPTION Task 2- Maintenance

FFP

OPTION Travel

COST

Travel in support of line items 4001 and 4002 shall be conducted IAW JFTR. All travel must be approved in advance by the COR and in writing. The travel exenses

5001 6 Each OPTION Task 1- Analysis_FAR 52.217-8 extension

FFP

Up to six (6) month extension of Task 1 services IAW FAR 52.217-8 OPTION TO

EXTEND SERVICES (NOV 1999).

5002 6 Each OPTION Task 2- Maintenance_FAR 52.217-8 ext

FFP

Up to six (6) month extension of Task 2 services IAW FAR 52.217-8 OPTION TO

EXTEND SERVICES (NOV 1999).

OPTION Travel_FAR 52.217-8

COST

Travel in support of line items 5001 and 5002 to be conducted IAW JFTR . All travel must be approved in advance by the COR and in writing.Expenses incurred for travel under this line item shall not exceed $2,000.00

INSPECTION AND ACCEPTANCE TERMS

Supplies/services will be inspected/accepted at:

CLIN INSPECT AT INSPECT BY ACCEPT AT ACCEPT BY

0001 N/A N/A N/A Government 0002 N/A N/A N/A Government 0003 N/A N/A N/A Government 1001 N/A N/A N/A Government 1002 N/A N/A N/A Government 1003 N/A N/A N/A Government 2001 N/A N/A N/A Government 2002 N/A N/A N/A Government 2003 N/A N/A N/A Government 3001 N/A N/A N/A Government 3002 N/A N/A N/A Government 3003 N/A N/A N/A Government 4001 N/A N/A N/A Government 4002 N/A N/A N/A Government 4003 N/A N/A N/A Government

5001 N/A N/A N/A Government 5002 N/A N/A N/A Government 5003 N/A N/A N/A Government

DELIVERY INFORMATION

CLIN DELIVERY DATE QUANTITY SHIP TO ADDRESS DODAAC /

CAGE

0001 POP 30-DEC-2018 TO

29-DEC-2019

N/A M30700

3300 RUSSELL RD

QUANTICO VA 22134

SHAWN WADE

703-784-3429

M30700

0002 POP 30-DEC-2018 TO

29-DEC-2019