Attachment_5_-__MAFR_CSE_Change_Request.pdf
PDF 45 KB Posted
- Attached to
- CNS LZ_DZ Storage Facility MAFR Federal contract opportunity
- Solicitation number
- FA4855-18-R-0024
About this file
MAFR CSE Guide
View the file
Other files for this federal contract opportunity
Show all 24
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
Text version
Please wait...
If this message is not eventually replaced by the proper contents of the document, your PDF viewer may not be able to display this type of document.
You can upgrade to the latest version of Adobe Reader for Windows®, Mac, or Linux® by visiting http://www.adobe.com/go/reader_download.
For more assistance with Adobe Reader visit http://www.adobe.com/go/acrreader.
Windows is either a registered trademark or a trademark of Microsoft Corporation in the United States and/or other countries. Mac is a trademark of Apple Inc., registered in the United States and other countries. Linux is the registered trademark of Linus Torvalds in the U.S. and other countries.
MAFR CENTER SCHEDULING ENTERPRISE (CSE) CHANGE REQUEST
Page 1 of
CONTROL#:
PART I
INITIATED BY:
SQ:
DATE/TIME INITIATED:
SQUADRON APPROVAL AUTHORITY:
PART II
Mission # Schedule Change / Reason Change Type Effective Date
SUPPORT AGENCY NOTIFICATIONS
Support Msn # Agency Name Action Date Time Phone #
PART III
SCHEDULING OPERATIONS USE
Mission # Deconfliction Notes Change Type Effective Date Range Management Office
APPROVED
DISAPPROVED
Mission Change Input Date:
Change Input By:
CANNONAFB FORM 12 20140826
Click to sign Click to sign
INSTRUCTIONS
1. The Form 12 is intended to notify 27 SOW Command and Control elements and range personnel of changes to the range schedule, document coordination among supporting units, and to track trend data.
2. The requesting unit completes the Form 12 for any changes to CSE affecting the restricted areas R5104A/B and R5105 and the surface of MAFR that occur after the Range Integration Meeting. Squadrons are responsible for contacting and coordinating the changes with all affected support agencies. Once the change request is submitted and approved, 27 SOAOS/DOOS will return the mission to "Submitted" then notify the squadron that the mission is available to input the requested changes.
3. Units complete Part I and Part II and submit to the 27 SOAOS/DOOS at 27SOAOS.DOOS@cannon.af.mil.
4. The requesting squadron approval authority is normally a squadron ADO or above.
5. For new mission requests, mission numbers may be left blank if the mission has not yet been created in CSE.
6. Indicate the type of change in the Change Type block, e.g., Cnx-Wx, New, Add Tgt, etc.
7. Same day changes to scheduled Electronic Combat Range missions only require coordination with GECCO operators unless the change affects other segments of the mission, or other scheduled missions.
8. Changes to low-level routes, air refueling, and MOAs do not require a Form 12, but must be coordinated through 27
SOAOS/DOOS.
9. Call sign changes prior to mission execution may be accomplished with a coordination Form 12 (no AOS approval required).
10. The Form 12 does not replace the AF Form 2407 procedures outlined in AFSOCI 21-165.
MAFR TIMELINES
The following timelines are the minimum for adding support from Melrose Range contract operations:
Iron Pony 2 Days SRTGT Moving Target 2 Days If at pre-recorded location 1 Week For new location not on impact areas MOUT Sites 3 Days For preparing atmospherics (must include mission plan in request)
OUTSIDE USERS / EXERCISES
Changes within 30 days of execution: Planners will submit changes with the change request form and updated schedule of events up until the Range Integration Meeting preceding the first week of execution.
RANGE INTEGRATION MEETING
All events will be scheduled prior to Range Integration Meeting.
CANNONAFB FORM 12 20140826
(Page 2) 8.2.1.3158.1.475346.466429
| CHECK1: 0 |
| CHECK2: 0 |
| FIELD1: |
| FIELD2: |
| FIELD3: |
| FIELD4: |
| FIELD5: |
| FIELD6: |
| FIELD7: |
| FIELD8: Date & Time (when you want to go to the range): |
| FIELD9: |
| FIELD10: |
| FIELD11: |
| FIELD12: Call Sign: |
| FIELD13: |
| FIELD14: |
| FIELD15: |
| FIELD16: POC & Phone Number (Who's the Range Lead?): |
| FIELD17: |
| FIELD18: |
| FIELD19: |
| FIELD20: Duration (How long you'll be at the range): |
| FIELD21: |
| FIELD22: |
| FIELD23: |
| FIELD24: Purpose (what's your purpose for visit?): |
| FIELD25: |
| FIELD26: |
| FIELD27: |
| FIELD28: # of Vehicle: |
| FIELD29: |
| FIELD30: |
| FIELD31: |
| FIELD32: # of Personnel: |
| FIELD33: |
| FIELD34: |
| FIELD35: |
| FIELD36: Specific range location / area of where you're going: |
| FIELD37: |
| FIELD38: |
| FIELD39: |
| FIELD40: JUSTIFICATION for MODIFICATION (Why - Change/Add/Cancel): |
| FIELD41: |
| FIELD42: |
| FIELD43: |
| FIELD44: Additional info: |
| FIELD45: |
| FIELD46: |
| FIELD47: |
| FIELD48: |
| FIELD49: |
| FIELD50: |
| FIELD51: |
| FIELD52: |
| FIELD53: |
| FIELD54: |
| FIELD55: |
| FIELD56: |
| FIELD57: |
| FIELD58: |
| Enter the date as shown in this example: 25 Aug 2010: |
| FIELD60: |
| FIELD61: |
| FIELD62: |
| FIELD63: |
| FIELD64: |
| FIELD65: |
| FIELD66: |
| FIELD67: |
| FIELD68: |
| FIELD69: |
| FIELD70: |
| FIELD71: |
| FIELD72: |
| FIELD73: |
| FIELD74: |
| FIELD75: |
| FIELD76: |
| FIELD77: |
| FIELD78: |
| FIELD79: |
| FIELD80: |
| FIELD81: |
| FIELD82: |
| FIELD83: |
| FIELD84: |
| FIELD85: |
| FIELD86: |
| FIELD87: |
| FIELD88: |
| FIELD89: |
| FIELD90: |
| FIELD91: |
| FIELD92: |
| FIELD93: |
| FIELD94: |
| FIELD95: |
| FIELD96: |
| FIELD97: |
| FIELD98: |
| FIELD99: |
| FIELD100: |
| FIELD101: |
| FIELD102: |
| FIELD103: |
| FIELD104: |
| FIELD105: |
| FIELD106: |
| FIELD107: |
| FIELD108: |
| FIELD109: |
| FIELD110: |
| FIELD111: |
| FIELD112: |
| FIELD113: |
| FIELD114: |
| FIELD115: |
| FIELD116: |
| FIELD117: |
| FIELD118: |
| FIELD119: |
| FIELD120: |
| FIELD121: |
| FIELD122: |
| FIELD123: |
| FIELD124: |
| FIELD125: |
| FIELD126: |
| FIELD127: |
| FIELD128: |
| FIELD129: |
| CALENDAR1: |
| SIGNATURE1: |
| SIGNATURE2: |
| EF_1: |
File details come from the government source that posted it.