Annex 3 - PrSM Inc 4 RFS - Technical Data Request.docx

UNCLASSIFIED

DEPARTMENT OF THE ARMY

U.S. ARMY COMBAT CAPABILITIES DEVELOPMENT COMMAND

AVIATION & MISSILE CENTER

5400 FOWLER ROAD

REDSTONE ARSENAL, ALABAMA 35898-5000

DRAFT

FCDD-AMT-M

SUBJECT: PrSM Increment 4 Technical Data Request

FCDD-AMT-M March 31, 2026

SUBJECT: Precision Strike Missile (PrSM) Increment 4 Technical Data Request

1. The PrSM Increment 4 Data Request is for the purpose of representing system performance to evaluate theoretical feasibility of the proposed solution. Provide as much information as is available. Do not provide classified information.

2. Tabular data is to be delivered as .csv with clear descriptions of table formats.

3. Assumptions:

a. Start simulation data at motor ignition. Do not include prelaunch or egress.

b. Simulation should launch from 0 Latitude 0 Longitude directly North with a launch elevation of 54.7 degrees.

c. Do not include wind model.

d. Accounting for oblate spheroid rotating earth (WGS-84).

4. Requested Data Table:

Simple Evaluation Data[footnoteRef:2] [2: Simple Evaluation Data is needed to recreate the proposed system solution. Enhanced Evaluation Data will improve the evaluation to more accurately represent the proposed solution.]

Enhanced Evaluation Data1

5. Data Table Expanded Specifications

a. Trajectory: Trajectory data should provide a full nominal trajectory including position, velocity, acceleration, angle of attack (AoA), and Euler angles over the duration of the flight. Should include the following coordinate systems: Latitude, Longitude, Altitude (LLA); Earth Centric Earth Fixed (ECEF); and Body Frame.

b. Flight Vehicle Geometry: CAD or dimensioned drawings showing overall shape and dimensions of the flight vehicle

c. Propulsion: Propulsion data should include thrust and mass flow rate tables to be used in the simulation. Airbreathing motors (if applicable) thrust and mass flow rate should be as multi-dimensional tables (altitude/Mach/AoA). If motor utilizes some form of fuel rate control, include profile/propulsion strategy.

d. Aerodynamics: Full aerodynamic lookup tables for force and moment coefficients (functions of Mach, total AoA, roll, and control surface deflection contributions).

e. Mass Properties: Full mass properties parameters, including: overall weight, center of gravity location, and moments of inertia. Include mass properties at propulsion breakpoints such as burnout or staging (if applicable).

f. Actuator: Actuator data should include parameters for a 2nd order CAS model, including natural frequency, bandwidth, and damping terms.

g. Lethal Mechanism: Include warhead and fuze type (height of burst, contact, delay, etc.), explosive charge mass, fragment mass etc. as applicable.

h. Seeker: Field of regard, detection range etc. as applicable

i. Monte Carlo: Monte Carlo data should include impact circular error probability (CEP) and statistical distribution of Monte Carlo draw parameters (gaussian/uniform, sigma values, etc.)

j. Autopilot: Autopilot block diagram.

k. Stability Margins: Stability margin data including gain and phase margins throughout flight (for times in nominal trajectory, for various flight conditions, etc.).

l. IMU: If applicable, provide an IMU datasheet containing limits, tolerances, and errors associated with the IMU.

m. Navigation: If applicable, should include the pseudo truth update source and rates associated with said aid.

n. Z-data: Per “TEST AND DATA REDUCTION PROCEDURES FOR MUNITIONS" 61 JTCG/ME-1-9, Chapter 2, Can include missile debris in addition to warhead fragments.

UNCLASSIFIED

image1.png