DRAFT Scope of Work Fiscal Year 25 Cost Analysis Services IDIQ.docx

Executive Office Cost Analyst SOW and Contract Requirements

DESCRIPTION / SPECIFICATION / WORK STATEMENT

C.1.0 General Information This is a non-personal services contract to provide Cost Analysis Support (CAS) for the following organizations, their portfolios of subordinate offices, and the supporting offices that they interface with in support of their assigned missions:

Program Executive Office Combat Support & Combat Service Support (PEO CS & CSS) Program Executive Office Ground Combat Systems (PEO GCS) Interfacing offices:

Development Command - Ground Vehicle Systems Center (DEVCOM GVSC) Detroit Arsenal – DTA TACOM Life Cycle Management Command (LCMC) The Government shall not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn, is responsible to the Government, regardless of the performance location.

C.1.0.1 Description of Supplies and Services / Introduction The contractor shall provide all non-personal services, qualified personnel, and supervision necessary to perform the CAS services as defined in this Performance Work Statement (PWS) except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

C.1.0.2 Background Historically, the TACOM Cost and Systems Analysis Directorate provided cost analysis support to PEOs CS&CSS and GCS when workload exceeded the limits of available staff. Supplemental services were provided through Omnibus contracts and most recently a purpose-built contract that was able to successfully provide support to the Program Management offices within both PEOs and other organizations which included:

TACOM Life Cycle Management Command (LCMC) Program Executive Office Soldier (PEO- Soldier) Joint Program Executive Office Chemical Biological Defense (JPEO-CBD) Marine Corps Systems Command (MARCORSYSCOM) The Office of the Deputy Assistant Secretary of the Army Cost and Economics (ODASA-CE) Program Executive Office for Simulation, Training and Instrumentation (PEO STRI) This contract is a planned replacement for the most recent contract. The planned contract will consist of the same types of cost data collection and analyses, cost projections, and technical reports that have and continue to be required to meet the various missions of the organizations listed above.

C.1.0.3 Scope This PWS applies to services in the areas of cost, economic, and technical analysis of acquisition programs, investment activities, and other sustainment/support workload efforts of the Department of the Army (DA) and United States Marine Corps (USMC) within the Department of Defense (DoD). Services will consist of cost, economic, and technical analysis for combat weapon systems, combat support and combat service support systems, information management systems, as well as associated acquisition and financial management reporting and data analytics.

C.1.0.4 Period of Performance/Ordering Periods The period of performance for any specific task(s) will be included at the task order level. At the IDIQ contract level, there will be five ordering periods, as follows:

The total of the contract-ordering periods is 60 months.

C.1.0.5 Recognized Holidays The contractor is not required to perform services on the day these holidays are observed:

New Years Day Martin Luther King Day Presidents Day Memorial Day Juneteenth Independence Day Labor Day Columbus Day Veterans Day Thanksgiving Day Christmas Day C.1.0.6 Hours of Operation The contractor shall conduct business no more than 40 hours per workweek per employee. The contractor shall maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS and individual Task Orders. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

C. 1.0.7 Place of Performance The contractor shall perform the work under this contract at the contractor’s facility and/or onsite at the Detroit Arsenal (DTA) in the Detroit Arsenal, MI; Selfridge Air National Guard Base in Harrison Township, MI; Ft. Belvoir, VA; Quantico, VA; Aberdeen, MD; Natick, MA; Huntsville, AL. Decisions on the utilization of Telework or Remote Work will be managed on a case-by-case basis subject to the sensitivity of data under analysis. A primary deciding factor for all work situations is whether the situation is in the best interests of the Government in meeting cost, schedule, and performance requirements. Contractor personnel performing services under this PWS may be required to travel and work at off-site duty locations in accordance with paragraph C.1.0.12 of this PWS.

C.1.0.8 Type of Contract The contract type for all task orders issued against this contract will be Firm Fixed Price in accordance with FAR 16.202. Travel will be on a Cost, No Fee (CNF) basis only.

C. 1.0.9 Physical Security The contractor shall be responsible for safeguarding all government equipment, information, and property provided for contractor use.

C.1.0.10 Contracting Officer Representative (COR) A qualified COR will be appointed by the Contracting Officer at the Task Order level. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance; maintain written and oral communications with the Contractor concerning technical aspects of the contract; issue written interpretations of technical requirements, including Government drawings, designs, specifications; monitor Contractor's performance and notifies both the Contracting Officer and Contractor of any deficiencies; coordinates availability of government furnished property; and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially regarding changes in cost or price, estimates, or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting order.

C.1.0.11 Identification of Contractor Employees All contract personnel attending meetings, answering Government telephones, and working in other situations where their contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by contractors are suitably marked as contractor products or that contractor participation is appropriately disclosed.

C. 1.0.12 Contractor Travel The contractor may be required to travel as specified by individually issued Task Orders. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government approval and authorization and a notification to the COR.

C.1.0.13 Organizational Conflict of Interest Contractor and subcontractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services, which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the Contracting Officer to avoid or mitigate any such OCI. The Contractors mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer. In the event the Contracting Officer determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies he or she deems necessary, to include prohibiting the Contractor from participation in subsequent contracting opportunities.

C.1.1 Common Access Card (CAC) Automated Contractor Verification System C.1.1.1 Common Access Card (CAC) Applications The contractor shall appoint an Information Assurance Officer to process CAC applications for its employees and subcontractor employees IAW Federal Acquisition Regulation (FAR) 52.204-9, Personal Identity Verification of contractor Personnel, DoD Directive 8190.3 Smart Card Technology and DoD Instruction 8520.2 PKI and PK Encryption.

C.1.1.2 Requests for Common Access Card (CAC) The contractor shall submit requests for CACs, with the personnel and job titles, via email to the COR.

C.1.1.3 Contractor Verification System (CVS) The Government will establish a CVS application account for each CAC request and provide each contractor and subcontractor employee a User Identification (ID) and password via email.

C.1.1.4 Common Access Card (CAC) Access Contractor and subcontractor employees shall access the CVS account and complete the CAC application within seven calendar days of notification of ID and password.

C.1.1.5 Common Access Card (CAC) Request Status The Government will inform contractor and subcontractor employees via email of the status of the CAC request. The status will be one of the following: (1) Approved; contractor shall proceed to nearest Real-Time Automated Personnel Identification System (RAPIDS) Defense Enrollment and Eligibility Reporting System (DEERS) location to obtain CAC; (2) Returned; additional information or correction to application required by contractor employee; or (3) Rejected; Government in separate correspondence will provide reason(s) for rejection.

C. 1.1.6 Common Access Card (CAC) Approved and Rejected Applications The contractor shall maintain records of all approved and rejected CAC applications.

C.1.1.7 Common Access Card (CAC) Period of Performance Issued CACs may be for a period of performance no longer than two years or the contract performance completion date (inclusive of all options), whichever is earlier. If a requirement for a CAC exists beyond two years, the contractor and subcontractor(s) shall submit a new request.

C.1.1.8 Common Access Card (CAC) Return The contractor and subcontractor(s) shall return issued CACs to the DEERS office IAW FAR 52.204-9. The contactor shall notify the Government of all CACs returned to the DEERS Office.

C. 2.0 MEETINGS

C.2.1 Post Award Start of Work Meeting (SOWM) The contractor shall host a SOWM at its facility, unless the parties agree to some other location, no later than 30 calendar days after contract award. The contractor shall, at a minimum, invite its leadership, PEOs CS&CSS and GCS representatives, the COR and the Contracting Officer. The contractor shall coordinate a mutually acceptable meeting date with the COR. The contractor shall prepare and submit a proposed agenda, via email, for the SOWM at least three business days before the scheduled meeting date, to include an outline of how it will accomplish all awarded tasks CDRL A003.

C.2.2 Task Order Kickoff Meeting The contractor shall host a Kickoff Meeting for each Task Order. The Kickoff Meeting shall include the contractor personnel assigned to the tasks prescribed by the Task Order and PEOs CS&CSS and GCS personnel overseeing the Task Order. The contractor shall hold Kickoff Meetings by phone within 15 calendar days of award of a Task Order, unless otherwise agreed to by PEOs CS&CSS and GCS.

C.2.3 Task Order Status Meeting The contractor shall host Task Order Status Meetings at its facility, unless the parties agree to some other location, as identified by an individual Task Order. The Contractor shall prepare presentation materials IAW CDRL A003 for each status meeting.

C.2.4 Meeting Minutes When required by a Task Order, the contractor shall provide meeting minutes within two business days IAW CDRL A001 (Record of Meeting Minutes).

C.3.0 COST ANALYSIS SUPPORT REQUIREMENTS

The Government will assign services for the contractor to perform under this contract, by a Task Order, and may include tasks from one or more sections of this PWS.

C.3.1 Minimum Labor Qualifications.

All work under this Task Order shall be performed by the Contractor using the Contractors equivalent labor category(s) for the four labor descriptions identified in C.3.1.1 C.3.1.4 below:

3.1.1 Senior Cost Analyst / Program Manager.

The Senior Cost Analyst/Program Manager shall serve as the primary interface and point of contact to the Government on all program and contract administrative issues. A minimum of a bachelor's degree in math, statistics, engineering, economics or related discipline, from an accredited college or university is required. A minimum of 15 years of management experience in cost analysis is required. Advanced degrees cannot be substituted for years of experience.

3.1.2 Cost Analyst

The Cost Analyst shall perform the tasks defined in Part 3 of the PWS and lead Junior Cost Analyst(s) in the performance of task orders. A minimum of a bachelor's degree in a mathematics, statistics, engineering, or economics is required. A minimum of 7 years of experience in cost analysis and cost estimating is required. Advanced degrees or certifications cannot be substituted for years of experience.

C. 3.1.3 Junior Cost Analyst The Junior Cost Analyst shall possess a minimum of a bachelor's degree in operations research, mathematics, statistics, engineering, or economics is required. A minimum of 3 years of experience relating to cost analysis and cost estimating is required. Advanced degrees or certifications cannot be substituted for years of experience.

C. 3.1.4 Entry Level Cost Analyst The Entry Level Cost Analyst shall possess a minimum of a bachelor's degree in operations research, mathematics, statistics, engineering, or economics is required.

C.3.2 Cost Analyst Products and Support The Contractor shall perform cost analysis and/or On-Site support under this PWS. Task Orders can include individual efforts, or combinations of efforts, from the following task areas of cost analysis products and services that the Contractor will develop and provide to any of its customers listed in C.1:

C.3.2.1 Task Area 1 Life Cycle Cost Estimates A complete, detailed, and fully documented material system life cycle cost estimate updated to support the Defense Acquisition System, Joint Capabilities Integration and Development System (JCIDS) the Planning, Programming, Budgeting, and Execution (PPBE) system. It estimates the systems life cycle cost, from cradle to grave. This includes all Research and Development, Procurement, Acquisition Operations and Maintenance, Military Construction, Operations and Support, and Disposal elements. Reference: Army Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum. Cost elements included in the life cycle cost estimate are defined in reference.

C. 3.2.1.1 Defense Acquisition System Cost Estimates The Defense Acquisition Systems processes require Life Cycle Cost Estimates (LCCE) to inform programmatic decisions and assess program performance. The LCCE is a document that includes costs incurred during the total life (from project initiation through termination) of a system or aggregation of systems. This includes all Research and Development, Procurement, , Acquisition Operations and Maintenance, Military Construction, Operations and Support, and Disposal elements. Depending on the acquisition program, the purpose of the estimate and the office completing the estimate the LCCE may have a different title. Examples of types of LCCEs include: Program Office Estimate, Independent Cost Estimate, Component Cost Estimate (CCE), Army Cost Position, and Army Cost Estimate. Reference: Army Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum. Cost elements included in the life cycle cost estimate are defined in reference.

C. 3.2.1.2 Cost Informed Requirements Development Requirements documents must identify the overall resources associated with pursuing the capability solution, including materiel and non-materiel costs over its projected lifecycle, and to ensure those resources are planned to be available for successful execution of the program. To support the requirements approval process a Cost Benefit Analysis (CBA) or Analysis of Alternatives (AoA) may be required. A CBA is a structured methodology that determines the costs and benefits of one or more alternatives and compares them in order to identify the best alternative to achieve a stated goal/objective. An AoA provides a systematic and unbiased comparative analysis of operational effectiveness, costs, affordability and risks of potential alternatives. It also provides a comparative analysis of the benefits and costs of proposed solutions(s). Both CBAs and AoAs will include LCCEs of each alternative.. References: U Army Regulation 70-1 (AR 70-1) Army Operation of the Adaptive Acquisition Framework November 2023; Manual for the Operation of the Joint Capabilities Integration and Development System, October 2021; DoD Instruction 5000.84 Analysis of Alternatives, August, 2020; Office of the Secretary of Defense Cost Assessment and Program Evaluation Analysis of Alternatives Cost Estimating Handbook, July 2021.

C. 3.2.1.3 Budget Estimate Formulation Budget formulation estimates can support a number of activities, including acquisition, base support operations, installation management, and personnel requirements. The types of activities will vary based on a variety of factors including the system acquisition category (ACAT) and stage of the system’s lifecycle This task is the process of updating a programs Program Office Estimate to support the PPBE process and/or provide support to the PPBE process. Budget estimate formulations, updates, and course of action analysis may be required to support: Strategic Portfolio Analysis Review (SPAR), Program Objective Memorandum (POM), Budget Estimate Submission (BES), Budget Document (P&R Form) creation, higher headquarters and Congressional Requests for Information (RFIs), the Budget enactment process or budgeting drills. References: To be provided at issuance of task order.

C. 3.2.1.4 Affordability Analysis Affordability analysis is required to support the Defense Acquisition System, JCIDS, and PPBE processes. A LCCE may be required to develop program affordability goals and caps. LCCEs will be maintained and assessed against affordability criteria (including goals, caps, and program funding). Affordability analysis may be an iterative process including the updating LCCEs, assessing affordability, and adjust program requirements, schedules or funding. Examples of affordability assessment processes or documents include Cost Informed Trade Assessments (CITA), Cost as an Independent Variable (CAIV), Program Funding and Quantities (Spruill) Chart, Unit Cost target assessments, and Buy to Budget Drills. References: To be provided at issuance of task order.

C. 3.2.2 Task Area 2: Specialized Cost Estimates and Data Analysis Techniques The objective of this task area is for the Contractor to prepare and provide estimates that are more specialized. Task Orders issued under this task area may require the Contractor to prepare and deliver items and perform services listed and described below:

C. 3.2.2.1 Cost Estimate.

A prediction of costs consisting of:

Further defined as: the estimated cost of a component or aggregation of components that is developed by using historical cost data and /or mathematical models. Reference: ArmyCost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum.

C. 3.2.2.2 Cost Analysis The act of developing, analyzing, and documenting cost estimates through various analytical approaches and techniques. It is the process of analyzing and estimating incremental and total resources required to support past, present and future systems. In its application to future resource requirements, it becomes an integral step in selection of alternatives by the decision maker. Reference: Army Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum.

C. 3.2.2.3 Software Cost Estimate A cost estimate / life cycle cost estimate for software for a system. Reference: Army Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum.

C. 3.2.2.4 Data Collection Data are the foundation of every cost estimate and reliable cost estimates are rooted in historical data. The data collection plan should emphasize the collection of current and relevant technical, programmatic, cost, and risk data. Data collection is a lengthy process and continues throughout the development of a cost estimate and through program execution. Many types of data need to be collected: technical, schedule, program, and cost data. In addition to gathering historical data from other programs, cost analysts should develop plans to collect data on the current program throughout program execution. It is best practice to continuously collect new data. Cost analysts should assess current data processes and data sources. Process steps investigated should include, but are not limited to, the data source(s) currently utilized, data gaps, data cleansing, data assumptions, and frequency of data refreshes. Examples of potential data collection includes both government data (program budget and accounting data, program schedules and technical reports) and contractor data (catalog prices, contractor CDRLs, forward pricing rate agreements). References: Army Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum; GAO Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs, March 2020; and DoD Instruction 5000.73 entitled Cost Analysis Guidance and Procedures, March 2020.

C. 3.2.2.5 Development of Methodologies, Models, Databases, Tools or Applications The design and development of cost estimating approaches, spreadsheets, models, tools, techniques, methods which are used to support the cost analysis, cost estimating process. Analysts build most DoD cost estimating models in Microsoft Excel or Automated Cost Estimating Integrated Tools (ACEIT). Some organizations have built Microsoft Excel templates in an effort to bring consistency to model building and facilitate their management. The Army requires the use of ACEIT on all ACAT I and II programs. There are also many tools available to support specific parts of the cost estimating process such as statistical analysis, software cost estimating, data visualization, and simulation. In addition to Microsoft Excel and ACEIT, system dynamics models and data science applications like R and Python are becoming popular for specific analysis, especially as data files get larger. Data visualization tools include software applications like Microsoft Power BI, Tableau, and Qlik. Analysts need to select tools to support the cost estimating process. Analysts should not tailor the cost estimating process simply to accommodate the constraints of any particular tool. References: Army Cost Analysis Manual, March 2020, associated 13 Mar 2020 Implementation Memorandum DoD Cost Estimating Guide December 2020; GAO Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs, March 2020; and DoD Instruction 5000.73 Cost Analysis Guidance and Procedures, March 2020.

C. 3.2.2.6 Risk, Uncertainty or Sensitivity Analysis Cost uncertainty analysis is the process of identifying and quantifying the uncertainties associated with elements of the cost estimate in the areas such as cost, technical and schedule. Risk is the probability of the unfavorable outcome. Sensitivity analysis is an analysis whereby different values of certain key variables are tested to see how sensitive investment results are to possible change in assumptions. It is a method of evaluating the riskiness of an investment. References: Army Cost Analysis Manual, March 2020, associated 13 Mar 2020 Implementation Memorandum and Joint Agency Cost Schedule Risk & Uncertainty Handbook, March 2014.

C. 3.2.2.7 Data Analytics and Visualization Data analytics is the process of analyzing raw data to help identify and solve problems. Data analytics methods includes developing tools and visualizations to communicate information and present the results of analysis. Data analytics and visualization tools include dashboards, databases, automated reports, and statistical analyses. Developing data analytics and data visualization solutions should be a collaborative process to identify stakeholder needs, and the data and methodologies required to meet mission needs. Analyst should develop custom dashboards and reports, improve existing reporting processes, and ensure stakeholder accessibility of developed tools and reports. References: To be provided at issuance of task order.

C. 3.2.3 Task Area 3: Cost and/or Benefit Comparisons The objective of this task area is for the Contractor to prepare and provide analysis that is used to compare costs and/or benefits of alternative courses of action. A comprehensive list and description of the work that may be required from the Contractor under this task area is shown below:

C. 3.2.3.1 Economic Analysis A systematic approach to identify, analyze and compare costs or benefits of alternative courses of action that will achieve a given set of objectives. This approach is taken to determine the most efficient and effective manner to employ resources. References: AR 11-18, Cost and Economic Analysis Program, August 2019, Department of the Army Economic Analysis Manual, February 2001, and DoDI 7041.03 Economic Analysis for Decision-Making, October 2017.

C. 3.2.3.2 Cost Benefit Analysis A structured methodology of forecasting and comparing the anticipated costs and benefits of alternative courses of action to identify the most effective manner of achieving a stated goal or objective. Reference: U.S. Army Cost Benefit Analysis Guide, V3.3, February 2018.

C. 3.2.3.3 Business Case Analysis A decision-making tool or framework to systematically identify, analyze, and compare benefits and costs of alternative courses of action. Reference: DOD Product Support Business Case Analysis Guidebook June 2024.

C. 3.2.4 Task Area 4: Contractor Performance Analysis The objective of this task area is for the Contractor to prepare and provide analysis of contactor data reporting documentation. Support to these processes includes: (1) Preparing plans and plan revisions. (2) Preparing and reviewing waiver requests. (3) Preparing and reviewing CDRL and scope of work language. (4) Providing recommendations to the PMO and plan approval authority. (5) Reviewing data submissions for completeness and accuracy. A comprehensive list and description of the work that may be required from the Contractor under this task area is shown below:

C. 3.2.4.1 Cost and Software Data Report (CSDR) The intent of CSDRs is to capture expenditure, technical, and programmatic data on efforts that are significant either for a current program or when a similar effort may be required for a future program. The collected data is the primary data source utilized when completing cost estimates. The CSDR Plan specifies the work breakdown structure (WBS) elements, the specific collection of Contractor cost data reporting (CCDR) and software resources data reporting (SRDR) data by program or contract, reporting frequency, and other supporting material such as the resource distribution table (RDT), the project applicability matrix (PAM), and technical characteristics. Reference: DoDM 5000.04, Cost and Software Data Reporting, May 2021.

C. 3.2.4.2 Earned Value Management Analysis Analysis of variance in contract costs and schedules. Extends to assistance with Integrated Baseline Reviews (IBR), development of WBS/CCDR Plan, analysis of CPR/CFSR monthly reports and providing EV training. AR 70-1 Army Operation of the Adaptive Acquisition Framework November 2023; DoD Instruction 5000.85 Major Capability Acquisition, , August 2020; and DoD EVMS Interpretation Guide (EVMSIG), March 2019.

C.3.2.4.2 Tailored Cost and Technical Data Collection Tailored cost and technical data collection can be used when CSDRs or EVM are determined to be not appropriate or additional data is required. Examples of tailored requirements include Bill of Materials, Project Expenditure Report, and Average Unit Manufacturing Cost Estimates. CDRLs will be developed based on specific program requirements. References: Army Cost Analysis Manual, March 2020, associated 13 Mar 2020 Implementation Memorandum;DoD Cost Estimating Guide December 2020, GAO Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs, March 2020, and DoD Instruction 5000.73 entitled Cost Analysis Guidance and Procedures, March 2020.

C. 3.2.5 Task Area 5: Support to PMs/PEOs and Headquarters Elements The objective of this task area is for the Contractor to prepare and provide programmatic support to Project Management Offices. Task Orders issued under this task area may require the Contractor to prepare and deliver items and perform services listed and described below:

C. 3.2.5.1 Milestone Support Support for milestone reviews to include preparation of cost related milestone documentation to interfacing with Project Management Offices, Program Executive Offices, Headquarters of Army Material Command (HQ AMC), Department of Army (DA), United Status Marine Corps, Department of Navy and Office of the Secretary of Defense (OSD) level cost offices in reviews and meetings. References: To be provided at issuance of task order.

C. 3.2.5.2 Cost Analysis Requirements Description A document that describes the salient features of both the acquisition program and the system itself and provides the basis for the Life Cycle Cost Estimates (LCCEs) Reference: Army Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum. DoD Instruction 5000.73 entitled Cost Analysis Guidance and Procedures, March 2020.

C.3.2.5.3 Cost Estimation Review and Approval Processes Depending on the cost estimating product, acquisition pathway of the program, ACAT level or equivalent and decision being supported, estimates have a variety of cost estimate approval processes. Independent review is an evaluation method for internal control. Independent reviews check the accuracy and reliability of cost data, promotes efficiency within the discipline of cost analysis, and encourages adherence to prescribed cost analysis managerial policies. Some examples of review and approval processes include Cost Estimate Validation, DASA-CE Sufficiency Review, Cost Review Board Working Group, Program Manager approval and PEO/Milestone Decision Authority approval. These reviews and approval processes may require providing copies of the estimate, formal documentation of the estimate, responding to reviewer questions, updating the estimate as required, briefing results and obtaining documented approval. References: To be provided at issuance of task order.

C.3.2.5.4 Acquisition Program Baselines (APB) and Program Management Controls (PMC) Contract between the Program Manager (PM) and the Milestone Decision Authority (MDA) documenting program performance, schedule, and cost goals (objectives). APB provides reference point for measuring program status. A Program Management Control (PMC) may be used to establish guardrails for monitoring program performance when a formal APB is not appropriate. Reference: Army Regulation 70–1 Army Operation of the Adaptive Acquisition Framework November 2023.

C.3.2.5.5 Acquisition Program Reporting Recuring program reports of program status relative to APB, PMC or standard metrics. Examples of acquisition reporting requirements includes Management Acquisition Reports (MAR), Defense Acquisition Executive Summary (DAES), Selected Acquisition Reports, Program Identification Data (PID), Program Status Reports, and maintenance of Program Master List data. Reference: Army Regulation 70–1 Army Operation of the Adaptive Acquisition Framework November 2023.

C. 3.2.6 Task Area 6: Knowledge Management Analyst should have both the requisite formal training and substantial on-the-job training to develop and update cost estimates and provide other data analysis products. Continuous learning by participating in data analysis, cost estimating, and data tools training is important for keeping abreast of the latest techniques and maximizing lessons learned. Analyst should attend such workshops to keep their skills current. Maintaining skills is essential if subject matter experts are to be relied on to apply best practices in their roles. Under this task, the contractor shall develop a training and development program that includes outreach and knowledge management for the requested community.

C. 3.2.6.1 Software and Technology:

Data analysis tools are consistently evolving and improving. Under this task the contractor will provide research support and guidance on available information technology (IT) and infrastructure. The Contractor shall strategize with the Government to leverage existing available technology, data, and resources to solve data cost needs identified. The Contractor shall also identify additional technology gaps and inform the Government of available software, assets, and tools that may impact the viability of the project(s). References: To be provided at issuance of task order.

C. 3.2.6.1 Training: Under this task, the contractor shall develop training for required federal and contractor staff on analytics and cost estimating tools, methodologies, and processes (to include ACEIT, Excel, R, Python, DAX, Power BI, etc.) The contractor shall develop training programs to improve the technical competency and data literacy of the workforce, to include analytical software (R, Python, Power BI, etc.) analytical methodologies (statistical analysis, data visualization, database architecture) and cost estimating tools (ACEIT, etc.). The contractor may be required to develop tailored training for project stakeholders on tools developed under this contract. References: To be provided at issuance of task order.

C. 3.3 Documentation Software The Contractor shall develop, integrate and document all cost estimates utilizing any unique software requirements specified in the task order. If utilizing the software Automated Cost Estimate Integrated Tools (ACE-IT), version 8.1 or higher must be used.

C. 3.4 Result Justification The Contractor must be able to present and justify the methodologies used and the results obtained for all assigned task orders at all meetings and briefings. The Contractor shall provide personnel to explain the reports, analysis or other product provided under this contract to support briefings to any organization within the US Department of Defense or any other entity of the United States Government.

C. 3.5 Documentation C. 3.5.1. For each Task Order the Contractor shall provide the Government a fully documented report and/or ACE-IT file IAW CDRL A002. All backup material, working papers, source material, and electronic files and spreadsheets shall accompany the full report and are the property of the Government.

C. 3.5.2. Documentation submitted by the Contractor shall comply with format and content requirements as specified in the executed Task Order and shall be in accordance with Government policy, guidance, and regulations. See paragraph C.3.6.

C. 3.5.3. Documentation shall contain sufficient detail to allow independent recreation or validation of the estimate with information provided. For each estimated element of cost, at a minimum documentation shall include:

References: Army Cost Analysis Manual, March 2020, DoD Instruction 5000.73 entitled Cost Analysis Guidance and Procedures, March 2020, DoD Cost Estimating Guide December 2020, and GAO Cost Estimating and Assessment Guide: Best Practices for Developing and Managing Program Costs, March 2020.

C. 3.5.4. When a contract task requires a Cost Estimation Review and Approval as defined in paragraph C.3.2.5.3 the Contractor will review documentation to ensure consistency with documentation requirements in paragraph C.3.5.1-3.

C. 3.6 Additional Policy, Guidance and Regulations Individual Task Orders may require delivery of documents subject to Federal Government, DoD, or Army policy, guidance, or regulation. The Contractor shall deliver required documents according to the policies, guidance, regulations identified below, and as designated in the applicable Task Order and CDRL data items identified. The Contractor shall comply with all updates to the below documents. Publications are available from the COR or via the Internet at the specified URLs. Army publications are available from http://www.apd.army.mil, and https://www.asafm.army.mil/Cost-Materials/Policy-Guidance/DOD publications are available from http://www.dtic.mil/whs/directives.

4.0 ADDITIONAL CONSIDERATIONS

C.4.1 Monthly Status Report (MSR) The Contractor shall prepare and submit monthly task order status reports summarizing progress within the reporting period, track progress against completion schedule and highlight any roadblocks or issues IAW CDRL A004.

C.4.2 Integration of Effort The contractor shall be solely responsible for the management of its employees, consultants, and subcontractors, and the execution and integration of all work performed.

C.4.3 Identification Contractor personnel, consultants, and subcontractor personnel shall identify themselves as contractors during meetings and telephone conversations, and in electronic messages and all other correspondence related to this contract or any of the issued Task Orders.

C.4.4 Non-Disclosure Agreements (NDA) The contractor is responsible for providing executed NDAs (Attachment 0006) for personnel under this contract, and any applicable Task Orders, to protect all proprietary, restricted, competition sensitive, or any other restricted (e.g. non-foreign disclosure due to public law) data that will be used or accessed during performance of the contract.

C.4.5 Disclosure of Information There shall be no disclosure or publication of information developed under this contract or any of the issued Task Orders unless the contractor obtains prior written approval from the Contracting Officer. To comply with Defense Federal Acquisition Regulation Supplement (DFARS) 252.204-7000, Disclosure of Information, copies of the information for release are required at least 45 calendar days prior to the scheduled release date. The contractor shall send copies to the locations found at DFARS 525.204-7000.

C.4.6 Off-Duty Employment Contractor personnel, consultants, and subcontractor personnel shall neither employ nor establish a compensatory arrangement with any person who is an employee of the United States Government, either civilian or military, without verifying that the employee has complied with the Joint Ethics Regulation (DoD 5500.7-R) and any appropriate department regulation pertaining to off-duty employment for Government personnel.

C. 4.7 Restrictions/Prohibited Activities The Government expressly prohibits contractor personnel, consultants, and subcontractor personnel from performing the following tasks, IAW with the Federal Acquisition Regulation (FAR), its supplements, and other applicable laws and regulations:

a) Preparing any statement of requirements, objectives, or needs for advisory and assistance services.

b) Evaluating the qualifications of any potential source or proposal for an order or contract for advisory and assistance services.

c) Formulating evaluation criteria, acquisition plans, solicitations, or strategies for the acquisition of advisory and assistance services.

(d) Preparing documentation for other orders or contracts for advisory and assistance services.

C. 4.8 Accident Investigation / Reporting and Responsibilities Accident investigation and reporting to higher command levels will remain with the U.S. Army at the host installation.

C. 4.8.1 Damage to Government Property The contractor shall report to the COR, within one hour of an accident, all available facts relating to each instance of damage to Government property and material or injury to Task Order personnel.

C. 4.8.2 Securing Accident Area The contractor shall immediately secure the accident area and wreckage until released by the accident investigation authority from the host installation. The COR will prepare the notification of release of equipment impacted by the accident or wreckage.

C.4.8.3 Accident Cooperation If the Government investigates the accident, the contractor shall cooperate fully with Government personnel until the investigation is completed.

C. 5.0 SECURITY REQUIREMENTS

C. 5.1 Classification The contract will not require access to CLASSIFIED information in performance of this contract. The contractor will have access to Controlled Unclassified information (CUI). CUI provided to or generated pursuant to this contract shall be protected. for the protection of CUI are below and in DFARS 252.204-7012.

5.1.1 General.

There are types of information that are not classified but that require application of access and distribution controls and protective measures for a variety of reasons. This information is known as controlled unclassified information (CUI). The types of information considered CUI for the program are information marked For Official Use Only by the U.S. Government and technical information. When handling CUI material, all personnel are to comply with these requirements and follow their company policy and/or applicable Proprietary Information Agreements (PIA) concerning the protection of proprietary information in situations not clearly stated herein.

C. 5.1.2 Technical Information Description.

Any recorded information related to experimental, developmental, or engineering works that can be used to define an engineering or manufacturing process, or can be used to design, procure, produce, support, maintain, operate, repair, or overhaul program material. The information may be graphic or pictorial delineations in media (e.g., computer software, drawings, or photographs), text in specifications, related performance or design documents, or computer printouts. Examples of technical information include research and engineering data, engineering drawings, and associated lists, specifications, standards, process sheets, manuals, technical reports, catalog-item identifications, and related information, and computer software documentation.

C. 5.1.3 For Official Use Only (FOUO) Information is now referred to as Controlled Unclassified Information (CUI).

For Official Use Only (FOUO) is a Government designation applied to UNCLASSIFIED information that may be exempt from mandatory release to the public under the Freedom of Information Act (FOIA). FOUO information includes information identified as such in the Security Classification Guide or information from a government document marked FOUO.

C. 5.1.4 CUI Markings.

Marking of FOUO documents will be in accordance with Army Regulation (AR) 25-55. Information extracted from an FOUO document will carry the FOUO marking until formally reviewed by the government. AR 25-55 can be found at http://www.apd.army.mil/ProductMaps/PubForm/AR.aspx . Marking of Technical information will include the statement provided in the Security Classification Guide. If the contents of the technical document require more than one Distribution Statement, apply the most restrictive statement. This does not preclude additional mandated markings as may be required by the contract.

C. 5.1.5 Protection of CUI Information C. 5.1.5.1 Access CUI may be released only to an individual who has a valid need for such access in connection with the accomplishment of a lawful and authorized Government purpose. Information in any media format may only be disseminated on a need-to-know basis. The need-to-know restricts the use or dissemination of CUI data to those individuals or organizations with direct affiliation with the given program or project. Further dissemination of such information will be at the discretion of the Government Security Manager. Personnel no longer requiring access to CUI must dispose (see Disposal below) or surrender any in their possession and terminate future access to it.

C.5.1.5.2 Storing / Handling During working hours, take reasonable steps to minimize risk of access to CUI by unauthorized personnel. After working hours, when not in physical possession of the owner, all CUI (whether hardcopy or optical media (e.g., DVDs, CDs) that contain CUI) must be afforded a reasonable degree of physical protection to prevent theft of program information (e.g., store CUI information in locked desks or file cabinets, locked rooms, cable lock laptops, storing in a trunk, storing out of site or similar means). Do not display CUI in public places (e.g., airports, airplanes, restaurants). Electronic storing and processing of CUI shall be in accordance with DFARS 252.204-7012 Safeguarding Controlled Defense Information and Cyber Incident Reporting. Do not process CUI on public computers (e.g., those available for use by the public in kiosks, hotel business centers), public wireless networks or computers that do not have access control. Personally owned computers and personally owned devices are not authorized to process CUI. Portable electronic devices (e.g., smartphones, laptop computers, and tablets), non-portable computers, and removable media (e.g., external hard drives, flash drives, USB drives; not including optical media) must be physically and electronically protected as described in this instruction and the DFARS 252.204-7012.

C. 5.1.5.3 Dissemination.

CUI printed documents and material may be transmitted through mail channels, commercial carrier or hand-carried without formal courier orders. FOUO information may be disseminated to DoD personnel and DoD contractors to conduct official business for the program. If dissemination is required outside of DoD personnel or DoD contractors, contact the Government Security Manager for approval. Technical information will follow the release instructions identified in the Distribution Statement. Use secure communications whenever possible; however, land-line telephones are more secure than cellular telephones and should be used whenever available for discussions involving CUI. Transmit voice and facsimile transmissions only when you have a reasonable assurance that only authorized recipients will have access to the transmission. Digital transmission shall comply with the below.

C. 5.1.5.3.1. All transmission and/or dissemination of CUI (i.