Section J Attachment 17 - APS V SCRs 0002 v2.xls
XLS spreadsheet 27 KB Posted
- Attached to
- Air Vehicle Planning System V
- Solicitation number
- FA4600-11-R-0028
About this file
Section J Attachment 17 revised by Amendment FA4600-11-R-0028 0002 - APS V
View the file
Other files
Show 40 more
50 files listed here. See the rest on GovTribe.
On GovTribe
Work with this file
- Download the original file
- Contacts named in this file
- Similar government files
- Ask GovTribe AI about this file
Text version
Sheet1
| Est Hrs | Component | Type | Title | Description |
| APS - Main Software Application module | Adaptive | Incorporate additional LAR model provided by weapon to accomplish 6 DOF resolution | APS planners need the ability to change between multiple LAR models due to the varying abilities of weapons and flight restrictions planned by APS. LAR model provided by weapon SPO, need is to integrate the weapon into planning process and automated algorithms. | |
| APS Main Application Software | Corrective | Inconsistent Grav Weapon Data shown on AC DGZ Editor | Test on SCR 8907-G-DGZ-EDITOR: Built new B-2 mission and inserted several GRV points. Opened the AC DGZ Editor and reviewed the weapons assigned to the targets. If the user clicks the "..." button and changes the "Select Weapon" highlighted item to "0/<None>", the AC DGZ Editor value for that target correctly changes to <None>, but the Select Weapon window highlights the 1st weapon in the list. The Select Weapon window isn't retaining the <None> value that the user selected and is displayed on the AC DGZ Editor. (prob log 393) | |
| APS Main Application Software | Adaptive | Enhanced Sortie History tools | Enhance APS 'sortie history' capabilities: 1. Provide a user-accessible GUI window to view the history records on a sortie loaded into the pool. 2. On the sortie history record, add the FPM version number used in routing. 3. Limit the recorded history records to one per day, per ISID, per routing step. 4. If possible, include the EDB version and config where the sortie was flown (i.e., EDB24/OT_Maintenance_39_Y). | |
| APS Main Application Software | Corrective | Problem saving SPADCON profiles | Performing Batch from DB "Spatial Tolerance" actions, and found the Batch Submit window didn't contain the Saved values from my previous session. Re-entered the desired data, and clicked Save. To make sure it "stuck", performed Op Env...Profiles...Save action. At that point, RE crashed. Taillog shows aps_re.x had a SIGSEGV immediately after saving the "Spatial Tolerance" profile. (Prob Log 379) | |
| APS Main Application Software | Adaptive | Optimize database access code | Enhance APS<->EDB performance by identifying and eliminating redundant EDB accesses. The goal is to optimize the database access code | |
| APS Main Application Software | Adaptive | Vertical Terrain Profiler 'Pilots View' window | Modify Vertical Terrain Profiler (VTP) to automatically rescale the Pilots View window when changing Terrain Parameters settings. Any change to the default VTP Terrain Parameters that affect the Pilots View window (i.e., Pilots View Width), followed by resetting the VTP playback, and causes the Pilots View centerline to shift away from center as it tries to fit the new Terrain Parameters in the fixed-width Pilots View. That new centerline then continuously shifts back and forth during replay, instead of staying stable in the center of the pilots View window. | |
| APS Main Application Software | Adaptive | Handling Error Messages for FLEX Targets | Generating FLEX missile with multiple FLEX targets. Most FLEX errors are CAMT failures. However, as I go 'Active' on each FLEX target profile, the Browse Error message closes forcing me to re-open for each FLEX target. VERY iterative for a 50+ FLEX mission!! Worse, I have to scroll through the general Browse Error message to find data related to the specific FLEX target in question. It would be nice to be able to 'pin' the Browse Error window open with it staying scrolled to the last position. Even better: when I'm active on a FLEX target profile and select View/Errors, a Browse Error window opens with data only for that target! | |
| APS Main Application Software | Adaptive | FLEX Damage Expectancy screening | CM FLEX target generation considers both CEP and DE when deciding if a target can be struck. Currently, CAMT will generate a Recoverable error for a FLEX DGZ if the CEP exceeds the (EDB parametric data) 'CEP Threshold', even if the FLEX could still achieve the desired DE on that target. To overcome this error, planners manually increase the CEP Threshold for that DGZ and re-refine the mission. CAMT then successfully FLEXes the target. In FLEX situations where the computed CEP on a DGZ exceeds the CEP Threshold, APS should compare the computed DE to the minimum DE specified in the CM_RTE_REFNMT_PARM table. If the missile would still achieve the minimum desired DE, update the CEP Threshold, report the CEP Threshold error as a Warning, and allow the missile to FLEX. If CAMT computes the missile cannot achieve the minimum DE, allow the FLEX to fail CAMT screening. | |
| APS Main Application Software | Adaptive | Configuration control batch processing test scripts | The APS team developed a set of shell scripts (used during development and integration testing) to batch large quantities of missions through selected APS processes. These scripts bypass the Graphical Interface, but enable the development team to rapidly and efficiently process identical missions on different APS versions, then compare the results to identify code and data problems. These scripts can be equally effective during database cutovers and service release testing. Place these scripts under configuration control, and deliver them as part of the APS baseline. Update the scripts to make them functional in both the contractor's development environment and in the USSTRATCOM production environment. Provide code documentation and user documentation necessary for on-site Contractor use in the production environment. Any script updates required subsequent to the initial baseline delivery will be IAW the APS IV CM and CCB processes. | |
| APS Main Application Software | Adaptive | LO RCS Data Export | APS needs to be able to export the processed LO RCS Data. This will enable the transfer of data between APS and MPS to simplify the necessary data conversions with version changes of CLOAR. | |
| APS Main Application Software | Adaptive | Disable 'OK' button during field edits | Enhance edit field behavior for consistency and to reduce user errors. Several APS windows allow the user to edit data fields by typing values into an edit field, then clicking a check-mark button to apply that edit to the original field. Two examples are 'Dupe Cell' and 'Add/Edit DGZ'. If the user doesn't click the check-mark button, the edits aren't applied, and clicking the window's OK button will process using the original (unedited) data. Enhance APS to disable the window's OK button if the user is in this edit mode. Re-enable the window's OK button after the user exits the edit mode (clicks the check-mark/apply or 'X'/cancel button). | |
| APS Main Application Software | Corrective | Problem saving SPADCON profiles | Performing Batch from DB "Spatial Tolerance" actions, and found the Batch Submit window didn't contain the Saved values from my previous session. Re-entered the desired data, and clicked Save. To make sure it "stuck", performed Op Env...Profiles...Save action. At that point, RE crashed. Taillog shows aps_re.x had a SIGSEGV immediately after saving the "Spatial Tolerance" profile. (Prob Log 379) | |
| APS Main Application Software | Corrective | Inconsistent AR Rebuild with Mating Editor changes | For GDTE Case 2 cell M15. In the process of doing the AR4 tanker change for both the Primary and Spare, I edited each AR fuel by 1 pound before keying Apply after all stages were changed. Got pop-up window listing all stages and sorties effected which implies all stages will be rebuilt. Yet after keying OK to close the window, I noticed via Waypoint Editor that only the last stage edited on the 'Active' bomber was rebuilt. Specifically, before opening the Mating Editor, I opened the Waypoint Editor and changed the AR refueling altitude and speed. Thus each AR had a new altitude with ALTLCK On while I set the AR speed to 390TAS with SPDLCK Off. After making the Mating Editor changes, I noticed the ARIP and FU points remained at the old altitudes and speed implying the event was not rebuilt. My batch Refinement output included multiple errors associated with refuelings. The workaround becomes a laborious Mating Editor process of editing each stage one-at-a-time keying Apply for those changes before proceeding to the next stage edit. I also zero out ARCTs and then manually review the Waypoint Editor for each vehicle before batching. |
Sheet2
Sheet3
File details come from the government source that posted it. Updated .