Common use of Task Area 3 - Doctrine Development Clause in Contracts

Task Area 3 - Doctrine Development. The Contractor shall provide Doctrine Development support. This type of support typically includes, but is not limited to conducting research and analysis for the purpose of revising and updating MCoE, DOD, or DA documents and manuals concerning doctrine. MCoE responsibilities include: doctrine for Armor, Infantry, Stryker, and Cavalry formations; gunnery strategies for Armor, Infantry, and Cavalry (rifle through tank); supporting Mission Essential Task List (METL) development; doctrinal/publication editorial and graphic art support. The Contractor shall submit all work products to the COR or designated MCoE official for review and approval. 5.4.1. Task functions include, but are not limited to: (a) Assisting TRADOC’s Combined Arms Center (CAC) in the writing, coordination, integration, and review of selected key (Joint critical) Army doctrine; (b) Reviewing capstone / keystone / other Joint-critical Army doctrine to ensure proper linkages to Joint doctrine; (c) Identifying Joint- critical Army manuals by publication to avoid duplication of effort with Combined Arms Doctrine Directorate (CADD), CAC and other branch proponent DOTDs; and, (d) Participating in key Army working groups, doctrine working groups and meetings, symposiums, and councils that impact Joint-critical Army doctrine implications. 5.4.2. The MCoE is the proponent for 115 doctrinal publications, each of which is scheduled for review every two years. Accordingly, TOs issued in this area will potentially encompass efforts associated with the review and revision of anywhere from one to all publications. Such effort will include the collection and analysis of lessons learned from Army operations, the identification of trends, review capstone doctrinal publications to identify doctrinal disconnects, and the identification of emerging technologies that may impact on the conduct of combined arms full spectrum operations. Generally, revisions begin with the capstone document and cascade to the supporting/subordinate document(s).