Attachment A-PWS Cost Analysis Support.docx

Performance Work Statement For Cost Analysis Support (CAS) Services Program Executive Office Combat Support & Combat Service Support (PEO CS & CSS) and Program Executive Office Ground Combat Systems (PEO GCS)

Section C: Description / Specification / Statement of Work

C.1.0 GENERAL INFORMATION.

This is a non-personal services contract to provide Cost Analysis Support (CAS) for the Program Executive Office Combat Support & Combat Service Support (PEO CS & CSS), as well as, Program Executive Office Ground Combat Systems (PEO GCS). 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 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 provides cost analysis support to PEOs GCS and CS&CSS. When workload exceeded the staffing level, additional services were required utilizing the Omnibus contract as individual task orders. The intent of this contract is to provide support to multiple Project Management Offices within both PEOs in addition to other organization, which include:

TACOM Life Cycle Management Command (LCMC) Program Executive Office Soldier (PEO- Soldier) Joint Program Executive Office Chemical Biological Defense (JPEO-CBD) Systems of Systems Engineering and Integration (SoSE&I) 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)

C.1.0.3 Scope.

This PWS applies to services in the areas of cost, economic, and technical analysis of major weapon system programs 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.

C.1.0.4 Period of Performance.

RESERVED.

C.1.0.5 Recognized Holidays.

The contractor is not required to perform services on the following holidays:

New Year’s Day Labor Day Martin Luther King Jr.’s Birthday Columbus Day President’s Day Veteran’s Day Memorial Day Thanksgiving Day Independence 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 Detroit Arsenal, MI; Selfridge Air National Guard Base in Harrison Township, MI; Ft. Belvoir, VA; Quantico, VA; Aberdeen, MD. Periodically Contractor personnel performing services under this PWS may be required to travel and work at an off-site duty location 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 with regard to 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/authorization and 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 Contractor’s 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.

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 Contractor’s equivalent schedule labor category(ies) for the four labor descriptions identified in C.3.1.1 – C.3.1.4 below:

C.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.

C.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 Analysis 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:

Task Area 1: Life Cycle Estimates Task Area 2: Specialized Cost Estimates and Techniques Task Area 3: Cost and/or Benefit Comparisons Task Area 4: Contractor Performance Analysis Task Area 5: Programmatic Support to PMs/PEOs and Higher Head Quarters

C.3.2.1 Task Area 1: Life Cycle Estimates The objective of this task area is to provide estimates and validations or sufficiency reviews of estimates covering the entire cost of the life cycle of a program. Task Orders issued under this task area may require the Contractor to prepare and deliver items listed and described below:

C.3.2.1.1 Program Office Estimates: A complete, detailed, and fully documented material system life cycle cost estimate updated throughout the acquisition cycle and the Planning, Budgeting and Execution System. It estimates the system’s life cycle cost, from cradle to grave. This includes all Research and Development, Procurement, Military Construction, Military Personnel, Operations and Maintenance, and Army Working Capital Funded elements. Reference: DA 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 Life Cycle Cost Estimate: 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, Military Construction, Military Personnel, Operations and Maintenance, and Army Working Capital Funded elements. Reference: DA 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.3 Analysis of Alternatives (AoA): 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). Costs are typically life cycle estimates of each approach. Reference: U.S. Army Handbook Section 5, Analysis of Alternatives (AoA), February 2010, ODASA-CE; DoD AT&L Memorandum, dated December 4, 2009, Subject: Directive-Type Memorandum (DTM) 09-027 – Implementation of the Weapon System Reform Act of 2009.

C.3.2.1.4 Annual Program Resourcing Validation (APRV): Process of updating a program’s Program Office Estimate to support the APRV process and/or provide support to the APRV process. The APRV is the forum to present program life cycle weapon system requirements and funding requests to a cross Program Evaluation Groups (PEG) forum. The APRV is the primary opportunity for Product Managers (PM) and the Life Cycle Management Commands (LCMC) to present their current and emerging requirements to the PEGs. SRs will be conducted for programs/systems approved by the Equipping, Sustaining, and Training PEG Co-Chairs who comprise the APRV Steering Committee. References: To be provided at issuance of task order.

C.3.2.1.5 Acquisition Program Baseline (APB): 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. Reference: DOD Instruction 5000.2 and the Defense Acquisition Guidebook, dated November 2004, C.3.2.2 Task Area 2: Specialized Cost Estimates and 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: 1) a clearly defined requirement; 2) a statement of cost assumptions; 3) a source identification for basic cost data; 4) and documentation of the methodologies used. 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: DA Cost 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: DA 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: U.S. Army Handbook Section 11, Software Cost Estimating, September 2009, ODASA-CE

C.3.2.2.4 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. References: DA Cost Analysis Manual, March 2020, associated 13 Mar 2020 Implementation Memorandum and U.S. Army Handbook Section 2, Cost Analysis Process Methods and Techniques, (AoA), February 2010, ODASA-CE.

C.3.2.2.5 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: DA Cost Analysis Manual, March 2020, associated 13 Mar 2020 Implementation Memorandum and U.S. Army Handbook Section 12, Cost Risk and Uncertainty Analysis, February 2010, ODASA-CE.

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, 31 January 1995 and Department of the Army Economic Analysis Manual, February 2001.

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 in order to identify the most effective manner of achieving a stated goal or objective. Reference: U.S. Army Cost Benefit Analysis Guide, 2nd Edition, 14 March 2011.

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 April 2011.

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. 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) Plans: 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: DOD 5000.04, Cost and Software Data Reporting (CSDR) Manual.

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.

C.3.2.5 Task Area 5: Support to PMs/PEOs and Higher Head Quarters 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 Headquarters of Army Material Command (HQ AMC), Department of Army (DA) and Office of the Secretary of Defense (OSD) level cost offices in reviews and meetings. References: To be provided at issuance of task order. Comment by Polcyn, Nichole R CIV US USA: Why would a contractor be interfacing with HQ AMC, DA, and OSD since they are not a government employee? Comment by Mary Gross: As Cost Analysts we interact with higher headquarters regularly. Sometimes it could be just to answer questions on a report/document we submitted since many documents we complete have to have approval of HQDA or OSD. And there are times when we need to brief HQDA or OSD on our estimates. As the contractor will be preparing these documents, there is always the possibility the contractor will be interfacing with these agencies in the same capacity as a government employee..

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: DA Cost Analysis Manual, March 2020 and associated 13 Mar 2020 Implementation Memorandum.

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 7.5 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:

(1) Description of estimated cost element and what that cost includes or excludes, as appropriate.

(2) The programmatic information on which the estimate was based.

(3) A list of assumptions, ground rules, constraints on which the estimate was based.

(4) The cost equation used to derive the cost estimate and description of how the methodology was derived. Include variable names and descriptions.

(5) List and description of all sources used to develop each cost estimate. This would include names, dates, titles, page numbers, of all data bases, documents, organizations, points of contact, as appropriate.

C.3.5.4 When contract task includes validation or sufficiency review the Contractor will review documentation to ensure consistency with documentation requirements in paragraph C.3.5.1-3 and GAO best practices.

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 http://asafm.army.mil/proponency/acpo.asp; DOD publications are available from http://www.dtic.mil/whs/directives.

(1) AR 11-18, Cost and Economic Analysis Program, 31 January 1995

(2) Department of the Army Cost Manual, Mar 2020

(3) Department of the Army Economic Analysis Manual, February 2001

(4) Discount Rates for OMB Circular No. A-94

(5) U.S. Army Cost Benefit Analysis Guide, 2nd Edition, 14 March 2011

(6) DA OASA(ALT) Memorandum for Program Executive Officers, Subject: Army Implementation of Under Secretary of Defense (Acquisition, Technology and Logistics) Affordability Initiatives

(7) USD(AT&L) Memorandum, 22 April 2011, Subject: Implementation of Will-Cost and Should-Cost Management

(8) DA OASA(AL&T) Briefing, 9 March 2011, Subject: Army Affordability and Should Cost Update

(9) DOD Product Support Business Case Analysis Guidebook April 2011

(10) DOD MIL-HDBK 881D, Work Breakdown Structures for Defense Material Items, 9 April 2018.

(11) Interim Instruction DOD 5000.02, Operation of the Defense Acquisition System, 25 November 2013

(12) U.S. Army Handbook Section 2, Cost Analysis Process, Methods, and Techniques, February 2010, ODASA-CE

(13) U.S. Army Handbook Section 5, Analysis of Alternatives (AoA), February 2010, ODASA-CE

(14) U.S. Army Handbook Section 11, Software Cost Estimating, September 2009, ODASA-CE

(15) U.S. Army Handbook Section 12, Cost Risk and Uncertainty Analysis, February 2010, ODASA-CE

(16) DOD AT&L Memorandum dated December 4, 2009, Subject: Directive-Type Memorandum (DTM) 09-027 Implementation of the Weapon System Reform Act of 2009.

(17) DOD Instruction 5000.2 and the Defense Acquisition Guidebook, dated November 2004

(18) DOD 5000.04, Cost and Software Data Reporting (CSDR) Manual

(19) DOD Instruction 7041.04, July 3, 2013, Subject: Estimating and Comparing the Full cost of Civilian and Active Duty Military Manpower and Contractor Support

(20) DOD Instruction 5000.73 Cost Analysis Guidance and Procedures dated 13 Mar 2020

C.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 0008) for personnel supporting PdD AWS 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. In order 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; and

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 conducts an investigation of 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. The procedures for the protection of CUI are below and in DFARS 252.204-7012.

C.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 Description: “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 general 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.e., email and file transfers) must use NIST/NIAP-approved cryptographic products/algorithms, e.g., DoD-approved Public Key Infrastructure Certification or AMRDEC Safe Exchange at https://safe.amrdec.army.mil/safe. These are available at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm. This encryption requirement includes communications that contain passcodes to teleconferences or web conferences where there is a reasonable expectation that CUI may be discussed. When encryption is not available, a government collaborative suite (aka Integrated Digital Environment [IDE]) must be used to transmit CUI.

C.5.1.5.3.2 Contractor-hosted collaborative suites may be used for digital transmission and/or dissemination of CUI by personnel not located on a government backbone (e.g., NIPRNET), provided the following conditions apply: 1) use only NIST/NIAP-approved cryptographic products/algorithms. The latest validation lists may be obtained at http://iase.disa.mil/pki/eca or http://csrc.nist.gov/groups/STM/cmvp/documents/140-1/140val-all.htm; and 2) use an internally hosted service that does not use a third-party collaborative suite service provider.

C.5.1.5.3.3 Do not post CUI to web pages that are publicly available or have access limited only by domain/IP restrictions. As permitted by other contract provisions, CUI may be posted to web pages that control access through the use of a DoD approved Public Key Infrastructure Certification and that provide protection via use of secure sockets, or other equivalent technologies. These are available at http://iase.disa.mil/pki/eca.

C.5.1.5.3.4 As new technologies become available in the electronics arena, care should be given to providing a reasonable degree of protection from known vulnerabilities.

C.5.1.5.3.5 The Internet is “Public Access”. CUI must be reviewed and officially approved by the PEO GCS Public Affairs Officer for public release before placing on the Internet. This is not applicable when the Internet is used for e-mail transmissions and encryption is used as noted above.

C.5.1.6 Disposal: Destroy CUI documents by any means approved for the destruction of classified information, i.e. cross-cut shredding or other means that would make it difficult to recognize or reconstruct the information. The contractor shall ensure any covered defense information provided by the Government under this contract is destroyed or sanitized from contractor-owned media and reported in accordance with NIST Special Publication (SP) 800-88, Rev 1, Guidelines for Media Sanitization, December 2014, or returned to the owning organization upon the completion of the contract or as directed by the Contracting Officer.

C.5.1.7 Report of Loss of CUI: Report any loss of CUI to the Government Security Manager. Initial reports shall be made as expeditiously as possible in all cases within 72 hours of discovery. If additional information is required after submission and review of the initial report, guidance will be provided at that time. Mark any reports For Official Use Only, exemptions 2 and 5 apply. Initial report content shall include the following information as available.

· Applicable dates, including dates of compromise and dates of discovery

· Threat methodology, including all known resources used (e.g. IP addresses, domain names, software tools)

· Account of what actions the threat(s) may have taken on victim system/network

· What information may have been compromised or lost, and its potential impact on government programs

C.5.2 Public Release Requests The contractor shall screen all information submitted for determination of public release to ensure it is both unclassified and technically accurate. The contractor shall provide a letter of transmittal certifying a screening was conducted and that the contractor attests that the information is unclassified and technically accurate, to the best of the contractor's knowledge. The contractor shall not release program information outside of program channels until the Government review process is complete. The contractor shall submit all requests for public release approval through the Procuring Contracting Officer (PCO) for a review by Government technical and security personnel and by the Government's Public Affairs Officer (PAO). The PCO will, after appropriate review, either authorize or reject the request to disseminate Government information publicly. Note that authorization may be given contingent on specified changes being made to the material for which public release has been requested. The program requires 45 calendar days to process the request and render a decision. Requests for public release shall be sent electronically via encrypted email using cryptographic products that are National Institute for Standards and Technology/National Information Assurance Partnership (NIST/NIAP) approved or mail a Compact Disc/Digital Video Disc (CD/DVD) using U.S. Postal First Class mail.

C.5.3 Operations Security (OPSEC) Requirements The contractor is not required to produce an OPSEC Plan. U.S. contractors with access to CUI (e.g. technical information, information marked with a distribution statement or FOUO) information shall be required to follow the PEO GCS OPSEC Plan, Attachment 0007. To ensure awareness of the PEO GCS OPSEC Plan, the contractor shall provide annual training for personnel supporting this contract on the contents of the MBTS OPSEC Plan. The contractor shall ensure that new personnel receive PEO GCS OPSEC Plan specific training within 30 days of program assignment. Personnel who have taken the PEO GCS OPSEC Plan training within the last 12 months shall be considered compliant unless the PEO GCS OPSEC Plan has been revised since the last training. The contractor shall report IAW CDRL A005.

C.5.4 OPSEC Awareness Training Requirements All contractor employees shall complete “OPSEC Awareness for Military Members, DoD Employees and Contractors” training. This training is available at: https://securityawareness.usalearning.gov/opsec/. All training shall be completed and reported IAW CDRL A006 (OPSEC Awareness Training Report). An alternative method is to conduct face-to-face training in a classroom or auditorium setting, using a sign-in or attendance sheets in lieu of certificates. The instructor will be OPSEC Level II certified to perform this alternative training method.

C.5.5 Common Access Card (CAC) or Installation Access Identification: Issuance of a CAC is authorized under this contract if one of the following requirements under Issuance is met.

C.5.5.1 Issuance: The contractor employee shall be issued a CAC only if duties involve one of the following: (1) Logical access to a DoD network that requires a CAC for login or a DoD website that only accepts the CAC for login access; or (2) Both physical access to a DoD facility and access, via logon, to DoD network on-site or remotely. Access to a DoD network must require the use of a computer with Government-controlled configuration or use of a DoD-approved remote access procedure in accordance with Defense Information Systems Agency; or (3) Physical access to multiple DoD facilities or multiple non-DoD federally controlled facilities on behalf of the DoD on a recurring basis for a period of 6 months or more. Contractor employees who meet these requirements shall be issued a CAC as explained at http://www.cac.mil/common-access-card/getting-your-cac/for-contractors/. Contractor employees who do not meet the requirements for a CAC but are required to have access to a government installation shall be sponsored for an installation Identification card by the contracting officer’s representative (COR) and provide all information to comply with adjudication standards and procedures using the National Crime Information Center Interstate identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13), applicable installation, facility and area commander agreements and other theater regulations.

C.5.5.2 Protection and Handling of Identification (ID) Cards and Reporting Lost or Stolen Cards: For CAC, refer to http://www.cac.mil/common-access-card/managing-your-cac/. Installation identification or badge shall be displayed while on the installation on the front of the outer garment between the shoulder and waist. The contractor is responsible for ensuring all ID cards are properly safeguarded and accounted for at all times. The contractor shall immediately file an installation police report in cases of loss, theft, forgery, or damage and report to the COR.

C.5.5.3 Return of ID Cards: The Contractor shall ensure that all employees, including all subcontractor employees at all tiers, return installation and/or access badges in accordance with (IAW) FAR 52.204-9 to the Visitor Control Center for deactivation and destruction. If a Contractor employee’s badge is not returned, the Contractor shall report, as soon as the incident is discovered, the unrecovered badge to the Installation Police. Contractor employees in possession of a CAC shall be responsible for turning in the CAC IAW FAR 52.204-9 and providing the CAC to the COR.