Resources – DoD IACs

RESOURCES

Below you'll find latest deadlines, policy updates, and resources

Learn More

LATEST DEADLINES AND POLICY UPDATES

Cybersecurity Policy

Posted Jan 15, 2019

Updated January 15th

The goal of the DoD Cybersecurity Policy Chart is to capture the tremendous breadth of applicable policies, some of which many cybersecurity professionals may not even be aware, in a helpful organizational scheme

DD448 and 7600B Policy Change

Posted Apr 3, 2019

Policy Update: DoD 7000.14-R (FMR) Volume 1, Chapter 4 (March 2016).
DTIC’s accounting system, the Defense Agencies Initiative, is an SFIS compliant target accounting system. In order to collect and store the required SLOA data elements, DTIC has provided additional guidance to customers whose order documentation (DD448 or FS Form 7600B) still produces the legacy LOA.

More Information about the *0403 COMPLIANCE REQUIREMENTS

040301. SFIS

SFIS compliance is required for all target accounting systems and target financial business feeder systems that comprise the target environment, as identified in the Enterprise Transition Plan, that support financial transactions. SFIS is also considered for legacy accounting systems and legacy financial business feeder systems on a case-by-case basis. SFIS provides an enterprise-wide standard for categorizing financial information along several dimensions to support financial management and financial reporting functions; enable decision-makers to efficiently compare similar programs and activities across DoD; and provide a level of detail required for information retrieval and auditability. SFIS is aligned to federal-wide
SFIS compliance means a target system must send, receive, capture, store, and maintain the SFIS data constructed as discrete data. Further, systems must meet all applicable SFIS Business Rules. SFIS data element transactions are required to be posted to the financial accounting system using the required USSGL accounts and accounting standards. DoD Component program managers are required to use the SFIS checklist to determine SFIS compliance and to guide implementation and configuration efforts.

040302. SLOA/Accounting Classification

The DoD SLOA/Accounting Classification is a subset of SFIS data elements that is used to ensure accurate accounting transactions and interoperability between systems. The SLOA/Accounting Classification requirement is applicable for all systems that process business events with accounting impacts between the time of commitment through disbursement. This includes, but is not limited to, accounting, contract writing, logistics, civilian pay, military pay, travel, medical, and transportation. Target systems must send, receive, capture, store, and maintain the SLOA/Accounting Classification data constructed as discrete data. Further, systems must meet all applicable SFIS Business Rules.
For legacy accounting systems and legacy financial business feeder systems that have a retirement plan and date, the implementation of SFIS and SLOA/Accounting Classification is considered on a case-by-case basis depending upon its impact on audit readiness.

040303. Interoperability of Data between Systems

Systems that support the financial management purchasing process such as contracts, intergovernmental orders, and payroll for audit readiness purposes must be interoperable with SLOA/Accounting Classification data elements. Supporting transactions are required to be posted to the target accounting system using proper USSGL accounts and accounting standards. A transaction broker and translation service may be used for legacy systems with a retirement plan and date to translate non-SFIS data elements to SFIS data elements. A transaction broker may be used to reduce the number of interfaces, thereby reducing the cost to maintain the interfaces and minimizing the number of interfaces subject to changes in interface controls to support auditability.

TEMPLATES, SAMPLES AND GUIDANCE

IAC MAC TASK ORDER RESOURCES

DOWNLOADS

VERSION

POINT OF CONTACT

Performance Work Statement (PWS)

Template & Guidance

Version 1.2

October 31, 2019

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Notes to Buyer (NTB)

Template & Guidance

Version 1.3

October 31, 2019

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Independent Government Cost Estimate (IGCE)

Please contact CSC for the latest IGCE

Version 1.0

October 1, 2018

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Evaluation Plan

Template

Guidance

Version 1.0

October 1, 2018

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Support Agreement - Interagency Agreement (IAA) General Terms and Conditions (GT&C) Section (FS Form 7600A)

Template

Sample

Guidance

Chrome users:
If you have trouble opening this form
Right click and choose "save link as ..."
Then close Chrome and open the PDF

Documents Updated

Oct 19, 2019

Program Analysis Cell (PAC)

dtic.belvoir.iac.mbx.iac-7600a@mail.mil

Funding Document - Interagency Agreement (IAA) Order Requirements and Funding Information (Order) Section (FS Form 7600B)

Template

Guidance

Checklist

Documents Updated

Oct 19, 2019

Financial Management

dtic.belvoir.rm.mbx.iac-mipr@mail.mil

Funding Document - Military Interdepartmental Purchase Request (MIPR) (DD Form 448)

Template

Guidance

Checklist

Chrome users:
If you have trouble opening this form
Right click and choose "save link as ..."
Then close Chrome and open the PDF

Documents Updated

Oct 19, 2019

Financial Management

dtic.belvoir.rm.mbx.iac-mipr@mail.mil

Contract Security Classification Specification (DD Form 254)

Template

Guidance

Chrome users:
If you have trouble opening this form
Right click and choose "save link as ..."
Then close Chrome and open the PDF

Version 1.0

October 1, 2018

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Quality Assurance Surveillance Plan (QASP)

Template & Guidance

Version 1.0

October 1, 2018

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Alternate COR (ACOR) Nomination

Template

Guidance

Version 1.0

October 1, 2018

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

Streamlined Acquisition Strategy Summary (SASS)

SASS prepared by the CSC

Version 1.0

October 1, 2018

Customer Support Cell (CSC)

dtic.belvoir.iac.mbx.csc@mail.mil

ARCHIVE

HDIAC Journal releases Volume 5, Issue 3

November 2, 2018

Volume 5, Issue 3 This issue of the HDIAC Journal provides readers with insight on six of HDIAC’s eight focus areas. First, the Biometrics article—illustrated on the Journal’s cover—presents a novel way of defending against biometric mimicry or “spoofing” in identity verification. Next, the CBRN Defense article details the U.S. Army’s testing of a biologically-based…

DSIAC Journal releases Fall 2018: Volume 5 Number 4

November 2, 2018

Fall 2018: Volume 5 Number 4 Featured Story: The global advancements in additive manufacturing (AM) are far reaching. From a U.S. Department of Defense (DoD) perspective, all the Services (U.S. Air Force, Army, Navy, and Marine Corps) are working to advance AM materials, processes, and manufacturing technologies. The investment is substantial. Read more … Download…

CSIAC Journal releases Volume: 6 Number: 3

November 2, 2018

Innovation Based Ecosystems Journal of Cyber Security and Information Systems Volume: 6 Number: 3 Posted: 11/01/2018 New buzz words like ‘innovation ecosystems’ often symbolize a departure from a legacy system to a more modern system and an underlying shift focus from operations management to service delivery with better user experience, reduce operational cost, minimize disruption, and enable personnel…

Frequently Asked Questions

Information Analysis Center (IAC) Multiple Award Contract (MAC) Task Order

What is an IAC MAC Task Order (TO)?

IAC MAC TOs are requirements for research and analysis that exceed the dollar and time limits of a BCO Task Order. TOs are separately funded work efforts or task orders placed on the IAC MAC indefinite delivery indefinite quantity (MAC IDIQ) contract. TOs are individually competed by one or more of the prime contractors pre-selected on the IAC MAC IDIQ. Through the IAC MAC, requesting agencies can use the IAC MAC as a contracting vehicle, enabling the DoD to obtain specialized support for specific projects.

Will the incumbent contractor performing the work for us now have a chance to compete for a new TO under the IAC MAC?

Are the IAC MAC prime contractors allowed to propose a new subcontractor to perform a TO, if that subcontractor was not on their team originally or is not their team now?

May I contact the individual MAC prime contractors?

How long does it take to get a TO awarded?

What is the process to get a TO awarded?

Who develops the evaluation plan, and who conducts the evaluation of the proposals?

Does the IAC MAC adhere to the Federal Acquisition Regulation (FAR) and Defense Federal Acquisition Regulation Supplement (DFARS)? Was it competed?

My agency requires my IAC MAC TO to include some of our local, agency-specific contract clauses. Can contract clauses be added to our TO that is not part of the IAC MAC contract?

Does the IAC MAC contain any small business preference provisions? Are any of the prime contractor’s small businesses? Does the contract meet Small Business Act requirements?

IAC Funding

What is a Military Interdepartmental Purchase Request (MIPR)?

A military interdepartmental purchase request (MIPR) is the primary method used to transfer funds from one DoD agency to another.

What is Customer Shared Direct Cost (CSDC)?

CSDC is the additional amount paid by customers for MIPR processing and accounting support, contracting office support, and program management support directly related to supporting customer-funded efforts (IAC MAC Task Order and BCO Task Orders). CSDC is used to pay for the direct costs associated with running the DoD IAC program and does not include any indirect costs. CSDC is not a fee paid to DTIC.

What is the current CSDC rate for this FY?

How is CSDC Calculated?

How can I de-obligate my funds and/or move my funds from one TAT or CAT to another?

De-obligation of Funds

In order to de-obligate funds or move funds from one technical area task (TAT) or core analysis task (CAT) to another the sending agency must work with the DTIC to perform the following tasks:

- The sending agency needs to ensure that the funds are available for de-obligation. In other words, confirm with the IAC that the funds have not been nor will be expended.
- The sending agency must submit a MIPR to de-obligate the funds from the TAT or CAT.
- Once both of the tasks above have been accomplished the contracting office will issue a modification to the delivery order that de-obligates those funds.
- Once the contracting office has issued the modification to the delivery order that de-obligates those funds, the sending agency can then send a second MIPR re-submitting the funds to another TAT or CAT.

DTIC and the contracting office will work with the IAC to ensure the amount can successfully be de-obligated. Once the IAC confirms that the funds are available for de-obligation (i.e. have not been expended), DTIC will process and accept the de-obligation MIPR.

If the IAC has expended the funds, the customer will be notified. Please note that if it is determined by the contracting officer's representative (COR) , contracting officer and the IAC that the delivery order being de-obligated is in contract closeout, the de-obligation cannot be processed.

De-obligation of Reimbursable Funds

In order to de-obligate reimbursable funds, the customer must submit a MIPR requesting the de-obligation of funding to dtic.belvoir.rm.mbx.iac-mipr@mail.mil. Once DTIC, the contractor and the contracting office agree on the de-obligation amount, the de-obligation process will begin.

De-obligation of Direct Cite Funds

Since DTIC does not have any visibility on the disbursement history for direct cite funding, the customer should contact the contracting officer's representative (COR) to begin the de-obligation process. The COR will work with the customer, contracting officer and the contractor to determine if there is funding available for de-obligation.

Once the de-obligation amount is agreed upon, the customer must submit a MIPR and the de-obligation approval documentation to dtic.belvoir.rm.mbx.iac-mipr@mail.mil.

Moving Funds from one Technical Area Task to another Technical Area Task or to a Core Analysis Task

Customer will be required to perform this task in two parts:

- Submit a MIPR amendment removing funding from the original Technical Area Task or Core Analysis Task
- Then submit a new basic MIPR adding the funding to the new Technical Area Task or Core Analysis Task

Line of Accounting Change

Customer will submit a MIPR citing the removal of funding from the incorrect line of accounting and then a line adding funding to the correct line of accounting.

For any other movement of funding scenarios, contact us at dtic.belvoir.rm.mbx.iac-mipr@mail.mil.

What kinds of funds can be used on the contract?

DTIC does not place restrictions on types of funds that may be accepted under IAC contracts. The sending organization must verify that funds are appropriate for the intended purpose, citing the approved performance work statement to identify scope. Limitations on the original appropriation sent to DTIC remain; use of DTIC's RDT&E authority does not change the conditions and limitations imposed on the use of funds (per DoD FMR Volume 11A, Chapter 3, 030104).

Basic Center of Operations (BCO) Task Order

What is the basic center of operations (BCO)?

What is a BCO Task Order (TO)?

TOs are separately funded work efforts over and above basic IAC BCO products and services that are awarded to one of our three BCOs, depending on the scope of the work required. Through the BCO TO program, requesting agencies can use the IAC program as a contracting vehicle, enabling the DoD to obtain specialized support for specific projects. TOs are of a limited dollar amount and duration depending on which BCO performs the work. Generally speaking, one year is the time limit on TOs and $1 million dollars in value.

What is the BCO TO process?

In the TO process, the government service or agency requiring the work drafts their requirements in a statement of objectives (SOO). The IAC can assist customers in drafting this document. Once a SOO is completed, it is reviewed by the contracting officer's representative and the contracting officer to ensure it meets the scope and constraints of the IAC BCO that will perform the work. Based on the requirements identified in the SOO, the IAC prepares a technical and cost proposal, which is subject to approval by the customer and the contracting officer. Once the technical and cost proposal is approved, the contracting officer will award the TO.

DEFENSE TECHNICAL INFORMATION CENTER

8725 John J. Kingman Road
Fort Belvoir, Virginia 22060-6218
1.800.CAL.DTIC (1.800.225.3842)
https://Discover.DTIC.mil

Administrator
Contact Us
Information Analysis Centers
Employment
Mission Statement
Submit Documents
USD(R&E)

Accessibility / Section 508
FOIA
Link Disclaimer
No Fear Act
Policy Memoranda
Privacy, Security & Copyright
Recovery Act
USA.Gov