Procedures for Requesting Convoy Movement Orders in Kansas National Guard, Summaries of Law

Download Procedures for Requesting Convoy Movement Orders in Kansas National Guard and more Summaries Law in PDF only on Docsity! REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015 2    Chapter 1: OVERVIEW 1-1 Purpose. This Standing Operation Procedure (SOP) establishes the Kansas Army National Guard (KSARNG) military transportation procedures. lt prescribes policy and establishes guidelines for planning, organizing, coordinating and conducting military convoy operations throughout the State of Kansas. It establishes procedures for requesting convoy movement orders produced by the Transportation Coordinators – Automated Information Management System II (TC-AIMS II). A working knowledge of the references indicated is recommended for proper execution of convoy movements. 1-2 Applicability. This SOP applies to Kansas National Guard (KSNG) units conducting convoy operations, Reserve Component (RC) unit convoy movements, Active Component (AC) moves over public highways, and any other non-stated Department of Defense (DoD) component in which movement originates in the State of Kansas (crossing other states lines or not). 1-3 Defense Movement Coordinator (DMC). Appointed by The Adjutant General, is located at the State Movement Control Center (SMCC) and is the single approving authority for AC, RC, Reserve Officer Training Corps, and National Guard for highway permits and convoy clearance requests. The DMC will: a. Create and maintain Traffic Circulation Plans (TCP) within TC AIMS II, a state highway network database in coordination with the Kansas Department of Transportation (KDOT) that will identify: 1. Routes suitable for convoy use with speed and route selection factors designated for each. 2. Route restrictions for weight, height, width, length, and cargo type. 3. Convoy rest areas, vehicle capacity, and use restrictions on each. 4. Locations and access routes to and from DoD installations within Kansas; such as Armories, Reserve Centers, active installations, or training areas. 5. Air and sea ports and major railroading facilities. 6. Secure holding areas. 7. Logistic support facilities for fuel, maintenance, subsistence, and billeting to support convoy operations. b. Receive requests for convoy movement from Active Component, Reserve, and National Guard units originating convoys within Kansas. Approve, schedule, de-conflict, and provide a Convoy Movement Order (CMO) for all convoys that comply with civil laws and military regulations. c. Direct and coordinate all Army highway movements within Kansas and movements of other services. d. Establish an SMCC to approve, manage, and track convoys. e. Maintain files on unit highway moves coordinated and approved by SMCC. Files will include state and local authorities (police, highway, etc.) and other highway regulatory authorities as necessary. f. Monitor military highway movements and provide planning, execution, and visibility data upon request. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   5   Chapter 2: MOVEMENT 2-1 Transportation Support. a. Transportation Movement Request (TMR) NGKS 55-12, submitted to arrive at the SMCC in accordance with DMC timetable (ANNEX A) prior to the requested movement date to allow for adequate mission analysis and acceptance by the transporting unit or arrangement for commercial transportation (ANNEX B). b. As much lead time as possible should be provided in order to evaluate the feasibility and capability of KSNG units to perform the move. c. As much information as possible is needed to be included into the TMR, including proposed funding of movement, so that if Kansas cannot support the mission then the Reserves, Active Component, or a commercial carrier have the opportunity to accept or decline the movement of mission essential equipment by the required date. d. TMR from one branch of service to another is restricted. The requesting element must submit a memorandum through their chain of command to their respective transportation offices. The request must include the models, NSNs. quantities, dimensional data (height, length, width, and actual weights), the points of movement, and the local POCs. e. A subordinate unit will not approach another subordinate unit from any branch of service once the need for outside transportation support is acknowledged. f. All KSNG elements will follow this guidance in negotiating with another state, Reserves, and the Active Components. 2-2 Definition of a Convoy. A convoy consists of: a. Six or more vehicles temporarily organized to operate as a column with or without escort, proceeding together under a single commander. b. When 10 or more vehicles per hour are dispatched to the same destination over the same route, they will be considered a convoy. c. One (1) vehicle constitutes a convoy (special permit) if it exceeds width, height, or weight restrictions outlined in KDOT Regulations or is transporting ammunition or hazardous materials over public highways. 2-3 Responsibilities and Appointments. a. Appointment of key movement personnel will be accomplished as outlined in FORSCOM/ARNG Reg. 55-1. (matrix of appointments, ANNEX C) b. Unit commanders and/or unit movement officers will ensure submission of DD Form 1265, Request for Convoy Clearance, and DD Form 1266, Request for Special Hauling Permit to the DMC/SMCC, as described in DOD 4500.9-R, Part Ill, Mobility and ANNEX A of this SOP. Computerized forms, utilizing TC-AIMS II, will be used. c. State Movement Control Center (SMCC) will coordinate and secure permits for oversize, overweight and Hazardous material convoy movements with the KDOT. d. Convoy commanders will disseminate special instructions and routes as outlined in the Convoy Movement Order (CMO). The convoy commander will ensure safety briefings as prescribed in DOD 4500.9-R, Part III, Mobility, Appendix F, para 13h are conducted. A copy of the CMO will be carried by each truck commander as it serves as REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   6   the authority for the convoy to travel on state roads. This is a written order issued from a higher headquarters. e. Drivers of vehicles will obey all special instructions as outlined in the CMO. Drivers will be familiar with the route and all safety briefing considerations. f. Permitted loads will follow the route directions, speed restrictions, and special instructions as detailed in the KDOT issued permit. In the event that there is a route conflict between the CMO and the permit; the permit always takes precedence. 2-4 Convoy Movement Authority. No convoy movement will be made over public highways without approval. a. The DMC through the SMCC in Kansas is the only approving authority for all convoys originating in Kansas and will issue the convoy clearance number (CCN) which authorizes convoy movement. b. If obtaining CCN a through normal procedures would delay the accomplishment of a required mission, an emergency movement may be approved telephonically by a member of the SMCC. c. Requests for AC units must be submitted through the Installation Transportation Office (ITO). d. The DMC will provide active military installations and USAR RRC/DRU headquartered within Kansas state boundaries a 24-hour contact number for emergencies and names and daytime phone numbers of the other states' DMCs (ANNEX D). 2-5 Convoy Clearance Requests and Special Hauling Permits. a. Requests for convoy clearances are submitted in TC-AIMS II Convoy Planning Module and DD Form 1265. Requests for special hauling permits to move oversized/ overweight vehicles on public roads are submitted on DD Form 1266 (see ANNEX B for DD 1266 sample). NOTE: Only identical vehicles with loads of uniform weight and dimensions may be listed on the same DD Form 1266. Each vehicle driver must have a copy of the approved DD Form 1266 and specific permit issued from KDOT for their vehicle and load. b. During peacetime, the DD Form 1265 and DD Form 1266 will be submitted to arrive at the SMCC in accordance with DMC timetable (ANNEX A), in accordance with FORSCOM guidance, prior to the date of ARNG and USAR moves. The SMCC will process the peacetime RC convoy request and provide a CCN to the unit in accordance with DMC timetable (ANNEX A) prior to the move. With approval by the DMC, units moving distances of 50 miles or less over regularly traveled routes between armories and established weekend training sites are not required to submit a convoy clearance request or use convoy vehicle markings (This does not apply to oversize/overweight or HAZMAT vehicles). AC units will submit requests through the installation to the SMCC in accordance with DMC timetable (ANNEX A) prior to movement. c. For crisis response movements, requests will be submitted as soon as possible prior to the movement. The CCNs will be provided back through the chain of command to the unit as soon as the requests are processed but NLT 24 hours prior to convoy REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   7   movement. If the UMC is unable to contact the DMC and/or immediate action is required, the UMC is authorized to process AC unit requests so long as notification of movement is made and emergency movement is valid. d. The convoy commander should identify specific checkpoints, the required location and duration of each halt, and request any logistical support and additional routing instructions. The movement must be conducted as the CMO directs, i.e. routing, departure times, rest halts, etc. Deviations are not authorized without prior coordination with the DMC. 2-6 Convoy Operations. a. Convoy operations will be conducted in accordance with DoD 4500.9-R, Part III, Mobility, FORSCOM/ARNG Reg. 55-1, FM 3-35, and civilian laws in a manner that ensures safety in keeping with road and traffic conditions. b. Convoy Vehicle Distances: For normal operations, an individual vehicle or cargo truck will maintain a minimum interval of four seconds from the vehicle it is following. All trucks towing trailers will maintain a minimum interval of eight seconds (300ft is Kansas standard distance). At speeds above 40 mph, during darkness, or when operating in inclement weather or other instances of reduced visibility, the time/distance will be increased. c. March Discipline. Principles of march discipline will be observed and the timeline detailed on the March Table of the CMO will be followed. d. Law Enforcement Support. Request for military and/or civilian law enforcement support required along the convoy route will be coordinated through the DMC if required. e. Entering Major Highways. When police support is available, vehicle operators will enter the highway in compliance with the police officer’s signals. When police support is not available, military personnel will be designated to direct military vehicle operators, only to ensure safe and orderly flow onto the highway. In this instance, vehicles may be infiltrated or closed to a distance not less than 20 yards, whichever appears to be in the best interest of traffic safety based on the convoy commander’s evaluation. Vehicle operators will be instructed to use acceleration lanes when available to establish operating speed before entering the traffic lane. Prescribed vehicle distance will be attained after all vehicles are on the highway and will be maintained for safe and efficient convoy operations. Vehicles will not operate on road shoulders to allow civilian traffic to pass. f. Scheduling Rest Halts. Rest halts will be scheduled for a minimum of fifteen minutes at the end of the first hour of convoy movement and for a minimum of 10 minutes at the end of every second hour thereafter. Departure from this rule is authorized when suitable rest facilities are not available at these intervals. During these rest halts drivers will inspect their vehicles for safety items, (i.e., lights, tires, trailer connections, cargo security, blocking, bracing, tie-down, and security). 1. The DMC will maintain current information on rest areas. This information will be made available to convoying units and will include the location and facilities available at each rest area. Pre-convoy planning will include provisions for use of these facilities. Rest halts on controlled-access highways will be made only at rest areas designated by the DMC. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   10   (a) This number will identify the convoy during the entire movement. It will be placed on both sides and, if possible, on the front of all vehicles of the convoy. Additionally, it will be placed on the top or hood of the lead and trail vehicles of each march unit to ensure identification from the air. The number will be printed clearly and in a contrasting color to the background. (b) It will be composed of two letters indicating the state of origin, convoy number assigned by that HQ, and a letter or letters indicating type of movement, (e.g., “C”-Convoy, “E”-Explosives, “S”-Outsize, or “H”- Hazardous). These letters will be used for individual vehicles or for a convoy containing over dimensional vehicles or load, for example, identification “KS40008C” indicates that the convoy originates in the State of Kansas and was the eighth convoy approved in 2014. The letter “C” indicates that there are no explosives, hazardous or outsize items of equipment included in the convoy. (c) The elements of a convoy may be identified by adding a letter behind the last letter of the convoy number. (d) Numbers may be applied to vehicles with chalk, grease pencil, or crayon. The number will be printed clearly and in a contrasting color to the background. 5. During emergencies the SMCC has established procedures to assign CCNs (ANNEX F). 2-8 Safety/Hazardous Material Movement. a. Highway Warning Kit: Every vehicle will be equipped with the basic type of warning kit. Vehicle operators will be instructed in their proper use prior to the departure of the convoy. In the event of an emergency, the placement of emergency warning devices will be lAW the provisions of DoD 4500.9-R, Part lll, Mobility and ATP 4-11 to provide maximum warning to other traffic on the roadway. They may be requisitioned on the basis of one kit per vehicle. (NSN 9905-00-148-9456 (Set of three)). b. If ammunition is to be drawn from the Ammunition Supply Point (ASP) at Ft. Riley, a DD Form 626, Motor Vehicle Inspection should be filled out before pickup of ammunition. After the pickup of ammunition, a DD Form 2890, Department of Defense Multimodal Dangerous Goods Declaration will be given to each driver prior to departing the ASP. These forms should be retained as long as the vehicle is transporting ammunition. These forms are valid for use until return of unexpended ammunition to the ASP and will be updated to reflect the reduced amount of ammunition transported. c. First Aid Kits: All vehicles must carry an approved first aid kit. d. Fire Extinguishers: All vehicles will be equipped with an approved fire extinguisher suitable for extinguishing gasoline and electrical fires. At minimum, ammunition laden vehicles will have two (2) 10lb B/C fire extinguishers. e. Chock Blocks: Chock blocks will be used as required at rest halts, rest overnight (RON) sites, upon reaching the training site, and upon return to home station. f. Vehicle Safety Markings: Safety reflector tape is required on all convoy vehicles, to include trailers as referenced in DoD 4500.9-R, Part ill, Mobility (ANNEX E). g. Refueling Operations: Proper safety equipment such as spill kits, and procedures to include vehicle grounding, must be followed in all refueling operations. h. Convoy Commanders Check list: FORSCOM Form 285-2, Commanders should use this checklist or similar checklist before, during, and after convoy movements. Movement should not proceed until each item is checked "GO". REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   11   i. Rotating Amber Warning Lights (RAWLs): RAWLs will be utilized, as a minimum, on lead and trail vehicles, and all vehicles transporting superloads. j. Driving Lane: Normal travel for convoys will be in the extreme right lane on a multi- lane road. An exception is when the right lane directs the convoy away from the designated route. Only proper planning, especially in the route reconnaissance can avoid potential problems at interchanges and other critical points. k. Single Vehicles: The dispatching of single vehicles either in the advance detachment or in the trail party is highly discouraged. l. Prevention of Motor Vehicle Accidents: Analysis has shown that most accidents are caused by driver error. Proper selection, training and supervision of drivers will help to prevent these errors, and will reduce accidents to a minimum. Convoy Commanders will review DA PAM 385-30, Risk Management before each convoy operation. m. Placards: Those vehicles that transport hazardous materials must display proper placards using the United Nations (UN) placard system, as outlined in Code of Federal Regulations (CFR) 49. Hazardous materials are those materials or substances which have been determined by the Secretary of Transportation to be capable of posing an unreasonable risk to health, safety, and property when transported. Transportation of these items also requires a DD Form 2890, Department of Defense Multimodal Dangerous Goods Declaration. These hazardous materials include, but are not limited to: 1. Explosives 2. Gasses (Non-Flammable, Flammable, and Poisonous) 3. Flammable liquids 4. Flammable solids Corrosive materials 5. Oxidizers and organic peroxides 6. Poisons and infectious materials 7. Radioactive materials 8. Corrosive materials 9. Miscellaneous Placards should be obtained through commercial supply channels. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   12   Chapter 3: REPORTS 3-1 Types of Reports. a. Travel b. Accident c. Computerized Movement Planning and Status System (COMPASS) 3-2 Travel (required from National Guard, Active Component, and Reserves). a. Travel under normal conditions. 1. Report crossing start point (SP) via text or voice to phone number listed in CMO within 30 minutes of crossing SP. 2. Report arrival at release point (RP) via text or voice to phone number listed in CMO within 30 minutes of crossing RP. 3. When reporting, indicate unit, CCN, location of point (SP or RP), and time of crossing. b. Travel under declared emergency. 1. Report as stated for normal conditions through unit’s higher headquarters to SMCC. 2. Report arrival and departure from rest halts and check points (CP) as indicated by unit’s higher headquarters and the SMCC to maintain in-transit visibility. 3. Higher Headquarters will communicate with Joint Operation Center (JOC) / Emergency Operations Center (EOC) and the SMCC. 3-3 Accident. a. Contact emergency services before making any other phone calls. Ensure the health, welfare, and safety of all persons involved in the accident. b. All accidents/incidents involving the Kansas Army National Guard personnel, equipment, or facilities will be reported by the most expeditious means through chain of command to the JOC/EOC. c. Report via text or voice to number listed in CMO any delay due to accident or obstruction of the State Highway network. d. Active Component and Reserves will report through their channels and in accordance with their SOP for accident reporting. However, contact on the number provided on the CMO must be made to notify of any delay due to accident or obstruction of the State Highway Network. 3-4 COMPASS. This report provides information on the movement of major end items and personnel for deployment purposes. It accounts for the dimensional data and weight in short tons of each item and the number of personnel authorized for each unit. In-depth details of the uses of this report are found in FORSCOM/ARNG Reg. 55-2, Unit Movement Data Reporting. This report generates the authorized Organizational Equipment List (OEL) that is included as Annex W of a Mobilization Plan. a. This is, at a minimum, an annual requirement from FORSCOM that is submitted as initial (loading of fresh data from PBUSE), but supplemental submissions are required when a significant change occurs. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   15   j. Annex J – Pre-movement maintenance support requirements. k. Annex K – Enroute maintenance support. l. Annex L – Air transportation (Not applicable if air movement is not required from HS to MS). 1. Appendix 1 – Air load plans. 2. Appendix 2 – Listing of pintle-hook vehicles (only if authorized to ship major end items by air). 3. Appendix 3 – Air loading procedures. (a) TAB A – Planeload Commander’s SOP. (b) TAB B – Load team SOP. (c) TAB C – Shoring material requirements. (d) TAB D – 463L pallet and tie-down requirements. (e) TAB E – Motor and Aviation fuels required for movement of organic air equipment. (f) TAB F – Special Handling Hazardous Cargo Certification. m. Annex M – Convoy requirements. 1. Appendix 1 – DD 1265 Request for Convoy Clearance 2. Appendix 2 – DD 1266 Request for Special Hauling Permit (oversize/overweight vehicles and loads as required). 3. Appendix 3 – Copy of Convoy Commander’s Checklist (FORSCOM Form 285- 2-R). 4. Appendix 4 – Copy of Driver Strip Maps. 5. Appendix 5 – Convoy Commander’s Safety Briefing; that addresses the following: (a) Drivers are licensed for vehicles being driven. (b) If hazardous material is part of the load, identify hazard on DD Form 1750, OEL, and DD Form-836. (c) Vehicle properly prepared for movement:  shipping configuration  fuel levels  secured secondary loads shackles  purging requirements  flags  convoy signs  highway warning kits  first aid kits (d) Convoy speeds. n. Annex N – Rail Requirements (Not applicable if rail movement is not required from HS to MS). 1. Appendix 1 – Security Guard SOP. 2. Appendix 2 – Load team SOP. 3. Appendix 3 – Documentation and procedures for rail loaded equipment that includes at a minimum the following: (a) Rail Load Plan. (b) Load teams assigned and trained. (c) Duty Appointment Memorandums. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   16   (d) Training Validated. (e) Vehicle properly prepared for movement:  Shipping configuration  Fuel levels  Secondary loads secured  Shackles  Markings (EIC and SUN)  Military Shipping Label (MSL)  Purging requirements  First aid kits (f) Vehicle placarded if hazardous material is part of the load. o. Annex O – Commercial Movement Requirements. 1. Appendix 1 – Packing Lists (DD 1750); see Annex W. 2. Appendix 2 – FORSCOM Form 285-1-R p. Annex P – Facilities/Equipment (Facilities enroute and MHE required for loading and unloading at HS and MS). q. Annex Q – POC listing of law enforcement, DCSLOG, USPFO, MS DOL, MS ITO, DMC, maintenance support facilities, and medical treatment facilities. r. Annex R – Safety; Deliberate Risk Assessment Worksheet (DRAW) that addresses each risk identified in each phase from alert to arrival at MS. s. Annex S – N-Hour Sequence (identifies and schedules movement tasks from alert notification through arrival at MS). t. Annex T – Plan Coordination Documentation (all Memorandum of Agreements with outside entities, e.g. arrangements for catering or meals at HS or commercial fueling enroute to MS). u. Annex U – Appointment Memorandums and Training Certificates (or verification of enrollment to gain certification). 1. UMO (Primary and Alternate) at company and detachment level. 2. HAZMAT Certifier (Primary and Alternate - This can be satisfied by assigning a Soldier from another unit within the MSC or from the unit’s supporting Field Maintenance Shop (FMS) so long as prior coordination is made) at company and detachment level. 3. TC-AIMS II Operator (Primary and Alternate) at company level. 4. Container Control Officer (Primary and Alternate) at company and detachment level. 5. Container Re-inspector (Primary and Alternate) at company level. 6. Unit Load Team at company and detachment level. v. Annex V – Plan Approval (plan submitted through chain of command to the DMC, request for approval memorandum with transmittal document is placed in this annex until approval memorandum from DMC is issued). w. Annex W – Unit Movement Data 1. Appendix 1 - OEL printout -- cross matches with DD Form 1750 and FORSCOM Form 285-R using shipment unit number. OELs will be reviewed annually by the JFHQ-KS DMC. Vehicle Load Card (FORSCOM Form 285-R) -- cross matches with OEL and packing list using Shipping Unit Number (SUN) sequence. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   17   2. Appendix 2 - Packing List (DD Form 1750) for air, rail, convoy and commercial movement -- cross matches with OEL and FORSCOM Form 285-R using SUN sequence. 3. Appendix 3 - HAZMAT documentation. 4-5 Vehicle Load Cards. Guidance on FORSCOM Form 285-R: a. Placed in Annex W, Appendix 1 in SUN sequence. b. Annotate vehicles as empty and without a secondary load. c. Create DD Form 1750 for each 4X4 tri-wall cardboard container at a number commensurate with the amount of unit equipment that will fit into that size container. d. Create DD Form 1750 for each 20 foot and ISU container that is required to hold the 4X4 tri-wall cardboard containers and equipment that is too big for the 4X4 (this will also assist in identifying the BBPCT material that will be required for your move that you will detail in Appendix E) e. Create Load Cards for 20 foot containers and unit organic ISU containers (This will assist in identifying Commercial Movement Requirements in Appendix O). 4-6 OEL. Current printout is available on the KSNG Share Point, J4 Logistics, Military Trans Public Documents, OELs (http://ngkssharepoint/J4_Logistics/Military_Trans/Pages/default.aspx). 4-7 Sample MOBPLAN. Available on KSNG Share Point, J4 Logistics, Military Trans, Public Documents, Unit Movement at same web address listed above. 4-8 MOBPLAN is not complete until submitted through the Chain of Command to the DMC, and approval memorandum is returned and signed by DMC. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   20   ANNEX C: Transportation Movement Request (TMR) and DD 1266 Sample REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   21   REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   22   REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   25   ANNEX F: Convoy Signs and Vehicle Marking F-1 Front of Lead Vehicle F-2 Rear of Trail Vehicle F-3 Front of Convoy Commander REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   26   F-4 Rear of Convoy Commander F-5 Marking for Rear of All Trucks in Red Reflective Paint, Tape, or Reflective Material REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   27   ANNEX G: Emergency Convoy Requests G-1 Upon contact with SMCC or DMC during a declared emergency verbal approval for convoy movement can be granted. G-2 The emergency CCN will follow this sequence: KS4E005S would designate Kansas convoy (first two letters) in 2014 (number “4”) granted emergency movement (letter “E” following the year) fifth convoy (sequence number “005”) and outsized cargo (letter “S” at end). G-3 All vehicles will be appropriately marked as prescribed in this SOP, as stated in 2- 7b, and this number will identify the convoy during the entire movement. G-4 The DMC and SMCC are the only approving authorities for issuing an Emergency CCN unless operating in a designated combat zone. REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   32   Annex J: Glossary AC Active Component ARNG Army National Guard AT Annual Training BBPCT Bracing, Blocking, Packing, Crating, and Tie-down CCN Convoy Clearance Number CCO Container Control Officer CDDP Command Deployment Discipline Program CFR Code of Federal Regulations CMO Convoy Movement Order COMPASS Computerized Movement Planning and Status System CP Check Point DCSLOG Deputy Chief of Staff for Logistics DMC Defense Movement Coordinator DoD Department of Defense DOL Directorate of Logistics DRAW Deliberate Risk Assessment Worksheet DRU Direct Reporting Unit EIC End Item Code EOC Emergency Operation Center FORSCOM Forces Command GVW Gross Vehicle Weight HAZMAT Hazardous Material HS Home Station IAW In Accordance With IC-UMO Intermediate Command - Unit Movement Officer ITO Installation Transportation Office JFHQ-KS Joint Forces Headquarters for Kansas JOC Joint Operation Center KDOT Kansas Department of Transportation KSARNG Kansas Army National Guard KSNG Kansas National Guard LIN Line Item Number MHE Material Handling Equipment MOBPLAN Mobilization Movement Plan MS Mobilization Station MSL Military Shipping Label MTOE Modified Table of Organization and Equipment NLT No Later Than NSN National Stock Number OCIE Organizational Clothing and Individual Equipment OEL Organizational Equipment List REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014 JFHQ-KS SOP 55-12 12 February 2015   33   OPORD Operation Order PBUSE Property Book Unit Supply Enhanced POC Point of Contact RAWL Rotating Amber Warning Light RC Reserve Component RP Release Point RRC Regional Readiness Command RTI Regional Training Institute SAAM Special Assigned Airlift Mission SMCC State Movement Control Center SOP Standing Operating Procedures SP Start Point SUN Shipping Unit Number TC-AIMS II Transportation Coordinators – Automated Information Management System II TCP Traffic Circulation Plan TDA Table of Distribution and Allowances TMR Transportation Movement Request UIC Unit Identification Code UMC Installation Unit Movement Coordinator UMD Unit Movement Data UMO Unit Movement Officer UN United Nations USAR United State Army Reserve USPFO United States Property and Fiscal Office REQUEST FOR SPECIAL HAULING PERMIT 1. CONVOY NUMBER 2. UIC 3. DATE (YYYYMMDD) SECTION I - GENERAL 4. ORGANIZATION 5. STATION 6. DATE OF MOVEMENT (YYYYMMDD) a. STARTING b. COMPLETION 7. POINT OF ORIGIN 8. DESTINATION 9. ARRIVAL AT STATE LINES 10. ROUTING (Stipulate US Routes, State Routes, etc.) a. DATE (YYYYMMDD) b. TIME c. STATE LINE 11. ESCORT REQUIREMENTS SECTION II - VEHICLE AND LOAD DATA DESCRIPTION a. TYPE (2-ton, etc.) b. NO. OF VEHICLES c. REGISTRATION NUMBER d. HEIGHT e. WIDTH f. LENGTH g. WEIGHT h. 12. VEHICLE (1) TRUCK (Empty) (2) TRUCK-TRACTOR (Empty) (3) TRAILER (Empty) (4) SEMI-TRAILER (Empty) (5) OTHER (Specify) (Empty) 13. LOAD 14. OVERALL (Vehicle and load) 15. DESCRIPTION OF LOAD (Brief general description: Organization impediments, etc.) (Within security limitations) 16. LOAD OVERHANG a. FRONT b. REAR c. LEFT SIDE d. RIGHT SIDE DD FORM 1266, SEP 1998 PREVIOUS EDITION IS OBSOLETE. 17. NUMBER OF AXLES AXLE 1 a. AXLE 2 b. AXLE 3 c. AXLE 4 d. AXLE 5 e. AXLE 6 f. AXLE 7 g. AXLE 8 h. TOTAL i. 1 A 2 B C D E F G 18. NUMBER OF TIRES 19. TIRE WIDTH (Inches) 20. TIRE SIZES 21. AXLE LOAD (Empty) 22. AXLE LOAD (Loaded) 23. AXLE SPACING (See Item 17 for identification) A SPACING B SPACING C SPACING D SPACING E SPACING F SPACING G SPACING H SPACING 24. REMARKS 25. MOVEMENT BY HIGHWAY IS ESSENTIAL TO NATIONAL DEFENSE IN THE INTEREST OF NATIONAL DEFENSE 26. REQUESTING AGENCY 27. APPROVING AGENCY INSTRUCTIONS GENERAL: DD Form 1266, "Request for Special Hauling Permit" will be used to obtain special hauling permits for the movement of over- size/overweight vehicles over public highways when accompanying a convoy or when traveling separately. This form, in duplicate and accompanied by letter of transmittal, will be forwarded through the local transportation officer so as to reach the appropriate headquarters not less than ten (10) working days prior to the starting date of the movement. transmittal will contain complete itinerary and explanation of the movement. (1) letter of transmittal is sufficient when several DD Forms 1265 and 1266 involving one (1) movement are forwarded to the appropriate headquarters. In cases where bona-fide emergencies exist, the information contained in this form and DD Form 1265 may be transmitted to the appropriate headquarters by telephone or electronic transmission. In this event, reference will be made to item numbers in the sequence in which they appear on the forms. will be so indicated. SPECIFIC: Item 12.a, b., c., and d. - Complete nomenclature of vehicles involved. one unit may be included, provided units are identical in equipment, load characteristics, routing and movement date. Item 12.e. - Note all units other than standard highway vehicles; road equipment, guns, etc. Item 12.d. - Indicate the registration number for each unit or combination of units. Item 17 - Indicate appropriate number of axles by inserting number in proper circles. Item 24 - For movement through the District of Columbia, include name of manufacturer of equipment. H e. DATE (YYYYMMDD)d. 28. REQUESTED BY a. NAME (Last, First, Middle Initial) b. c. TITLE e. DATE (YYYYMMDD)d. 29. APPROVED BY a. NAME (Last, First, Middle Initial) b. c. TITLE Letters of One Items which do not apply More than Total number of units shall be indicated prominently. Use additional page if required. Block out circles not applicable. SIGNATURE GRADE SIGNATURE GRADE DD FORM 1266 (BACK), SEP 1998 DD FORM 2875 INSTRUCTIONS Always use the <TAB> key to advance to the next field. REQUEST DETAIL: Type of Request. Choose either Initial, Modification, Deactivate, or Activate. Date. Date of request. System Name. Application platform to be initiated, modified or deactivated. Location. Physical location of the computer to be used with the application. PART I: The following information is to be provided by the user when establishing or modifying their account. After completing PART 1, the user must first obtain the security manager's signature, and then provide the form to the UAM. (1) Name. The last name, first name, and middle initial of the user. (2) Organization. The user's current organization (e.g. DISA, SDI, DoD, government agency, or commercial firm name). (3) Office Symbol/Department. The office symbol within the current organization (e.g. SDI). (4) Telephone Number/DSN. The Defense Switching Network (DSN) phone number of the user. If DSN is unavailable, the commercial number. (5) Official E-mail Address. The user's official e-mail address. (6) Job Title/Grade/Rank. The civilian job title, military rank or "CONT" if user is a contractor. (7) Official Mailing Address. The user's official mailing address. (8) Citizenship. US, Foreign National, or Other. (9) Designation of Person. Military, Civilian, or Contractor. (10) IA Training and Awareness Certification Requirements. User must indicate if he/she has completed the Annual Information Awareness Training and the date. (11) User's Signature. User must click in the field to enact a digital signature from their CAC card, with the understanding that they are responsible and accountable for their password and access to the system(s). (12) Date. The date that the user signs the form. PART II: The information below requires the endorsement of the user's Supervisor/UAM or Government Sponsor. (13) Justification for Access. A brief statement is required to justify establishment of an initial USER ID. Can also be used to explain the purpose of the request. (14) Type of Access Required. Place an "X" in the appropriate box. (Authorized - Individual with normal access. Privileged - Those with privilege to amend or change system configurations.) (15) User Requires Access To. Place an "X" in the appropriate box. Specify category. (16) Verification of Need to Know. To verify that the user requires access as requested. (16a) Expiration Date for Access. The user must specify expiration date if less than 1 year. (17) Supervisor's Name (Print Name). The supervisor or representative prints his/her name to indicate that the above information has been verified and that access is required. (20a)Supervisor's Signature. Supervisor must click in the field to enact a digital signature from their CAC card. Signature is required by the endorser or his/her representative. (19) Date. Date supervisor signs the form. (20) Supervisor's Organization/Department. Supervisor's organization and department. (18) E-mail Address. Supervisor's e-mail address. (20b) Phone Number. Supervisor's telephone number. (21) Signature of Information Owner/OPR. Signature of the functional appointee responsible for approving access to the system being requested. (21a) Phone Number. Functional appointee telephone number. (21b) Date. The date the functional appointee signs the DD Form 2875. (22) Signature of Information Assurance Officer (IAO) or Appointee. The IAO or Appointee of the office responsible for approving access to the system being requested must click in the field to enact a digital signature from their CAC card. (23) Organization/Department. IAO's organization and department. (24) Phone Number. IAO's telephone number. (25) Date. The date IAO signs the DD Form 2875. (26) Name. Repeat data entry of requesting user’s name. (27) Optional Information. This item is used to clarify TC-AIMS II requests for Initiation and Modification. For Initiation, only the ADD Access area is used. For Modification, the ADD Access and/or REMOVE access areas can be used. The information in these areas aid the PD TIS CSC in account creation and maintenance. In both areas, field definitions are: Unit Name: the user’s assigned UIC name Assigned UIC: the user’s Assigned Unit ID in the CoC Responsible UIC: the most senior parent UIC in the CoC for the user is used as the Responsible Unit ID Preference UICs: subordinate units to the user’s Responsible UIC Preference Jobs: define the level of access or capability granted to the user within different categories of the TC-AIMS II applications Primary Job Role(s): user’s functional job responsibility(s). C. PART III: Security Manager's Certification of Clearance. (28) Type of Investigation. The user's last background investigation (e.g., NAC, NACI, or SSBI). (28a) Date of Investigation. Date of last investigation. (28b) Clearance Level. The user's current security clearance level (Secret or Top Secret). (28c) IT Level Designation. The user's IT designation (Level I, Level II, or Level III). (29) Verified By. The Security Manager or representative prints his/her name to indicate that the above clearance and investigation information has been verified. (30) Security Manager Telephone Number. The telephone number of the Security Manager or his/her representative. (31) Security Manager Signature. The Security Manager or his/her representative indicates that the above clearance and investigation information has been verified. (32) Date. The date that the form was signed by the Security Manager or his/her representative. PART IV: This information is site specific, and can be customized by the DoD, functional activity, or customer (e.g. the Customer Service Center, IT OPS, etc.) with approval of the DoD. This information will specifically identify the access required by the user. DISPOSITION OF DD FORM 2875: Request Initiation: The Request Detail and Part I of this form must be filled out, and digitally signed, by the user requesting access. When the user (requestor) attempts to digitally sign the form in Part I, the user will be forced to save the form, and must rename the form using the following format “SAAR-UserName.PDF”. Transmission: The form must be forwarded by e-mail, to each entity or person, that’s required to fill out and digitally sign the form. Typically the form would pass from the requesting user to the Security Manager, then from the Security Manager to the Unit Account Manager (UAM), then from the UAM to PD TIS Customer Service (the Support and Operations Center). c4isr.support@us.army.mil <mailto:c4isr.support@us.army.mil> is the URL for PD TIS Customer Service (the Support and Operations Center). Filing: Original SAAR, with digital signatures in Parts I, II, and III, must be maintained on file for one year after termination of a user's account. DD FORM 2875 INSTRUCTIONS, AUG 2009 TRANSPORTATION REQUEST All transportation requests must be sent through Defense Movement Coordinator (NGKS- LOT-MC) 2737 S. Kansas Avenue, Topeka, KS 66611.  Requests are due to the supporting SMCC NLT 60 days before date of movement.  Requests for overweight/oversize loads must accompany this form with a DD 1266. 1LT Ruffin phone 785-274-1286 (commercial), 785-806-1781 (cell), Fax 785-274-1643, or e-mail: ng.ks.ksarng.list.j4-dmc@mail.mil DATE OF REQUEST: TMR #: MSN# REQUESTING UNIT NAME AND ADDRESS: POINT OF CONTACT: TELEPHONE: FAX: EMAIL: DATE OF MOVEMENT: Start Date: Completion Date: POINT OF ORIGIN/POC Name and Number: (Bldg #, Grid, or Street) DESTINATION: POC Name and Number: (Bldg #, Grid, or Street LOAD DESCRIPTION LIN / NSN: NOMENCLATURE (Do not use abbreviations): BUMPER/ SER: Funding/ POC for Funding: Special Handling or Oversized load data: Do not write below this line. Estimated Cost Civilian Contractor: Mission Support: APPROVED DISAPPROVED Authorized Battalion Representative Signature: NGKS Form 55-12 Oct 2014