EMSO JTIM Engineering Support 09 Oct 2024 v 1.0.docx

Joint Targeting Intelligence Modernization Engineering Services

1 INTRODUCTION

OBJECTIVE

The Secretary of the Air Force, Administrative Assistant’s Concepts, Development, and Management Office - Directorate of Research and Analytics (SAF/CDM/CDMR) explores new concepts, develops emerging opportunities, and manages high-priority projects and programs to provide innovative solutions to Air Force and defense-wide challenges. The sub-directorates, Combatant Command Intelligence – Enterprise Management Support Office (CCI-EMSO) requires engineering, analytical and technical services support to meet current and projected Joint Targeting Intelligence Moderatizaton workload requirements. This work may be for services not previously under contract and some may be follow-on work. The analytical and technical services described in this Performance Work Statement (PWS) directly supports the missions of CCI-EMSO to be the partners of choice for innovation, discovery, and opportunity development within the Department of Defense.

SCOPE

This Contract requires contractor support to serve as Joint Targeting Intelligence Modernization (JTIM) lead integrator.

Pursuant to this contract, the contractor will:

1) Design, develop, troubleshoot, and analyze JTIM family of systems information and systems as defined by the government.

2) Perform JTIM family of systems and enterprise architecture; select and integrate appropriate development and support tools to insure timely and effective delivery to the stakeholders of key architecture findings.

3) Investigate, identify and resolve issues logged internally by QA and end users.

4) Develop and maintain documentation including MSRs, meeting notes, etc.

BACKGROUND

CCI-EMSO is sponsored by the Office of the Undersecretary of Defense for Intelligence and Security OUSD(I&S) to rapidly develop and deliver innovative solutions, analytic assessments, and data-driven findings for high-priority projects and programs supporting the Combatant Commands and the Defense Intelligence Enterprise.

CCI-EMSO use creative and critical thinking, high-performance-multi-discipline teams that collaborate across functional and organizational boundaries and develop products that integrate the best of government, industry, and academia. CCI-EMSO and ISSO explore new and alternative methods, demonstrate technical feasibility, and support near-term operational requirements to deliver tangible products or capabilities.

Combatant Command Intelligence – Enterprise Management Support Office (CCI-EMSO) guides the modernization, alignment, and integration of enterprise Combatant Command Intelligence IT capabilities as part of the Defense Intelligence Enterprise (DIE). CCI-EMSO provides enhanced insight into information technology shortfalls and requirements, assesses emerging enterprise solutions, supports capability modernization and integration initiatives, and implements analytic elements of OUSD(I&S) HERALD Strategy, Digital Transformation.

JTIM is a joint OUSD(I&S) and Joint Staff J2 effort to produce a modern integrated cloud-based capability for the Joint Force targeting enterprise. JTIM includes:

· Developing a Joint Targeting Workflow Manager

· Modernizing existing Enterprise Tools

· Adopting a common DevSecOps platform to facilitate tool and data integration

· Explore additional integration opportunities with outside the JTIM chartered tools

REFERENCES

a) Department of Defense Direction (DODD) 5205.15, The DoD Insider Threat Program, Change Aug 28, 2017

DOD Directives and Instructions are available at https://www.esd.whs.mil/DD/, NIST publications are available at https://csrc.nist.gov/publications, Air Force Instructions are available at https://www.e-publishing.af.mil/. If the contractor has any difficulty, obtaining copies of these documents the Contracting Officer can make them available upon request.

GENERAL REQUIREMENTS

NON-PERSONNEL SERVICES

This is a non-personnel service contract to continue engineering, lead integrator and architecture engineers services for the JTIM family of system. The Government shall not exercise any supervision or control over the contract service providers performing the service herein. The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform this requirement, as defined in this PWS except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

PERIOD of performance This Contract is a Base + three 12-month options. The periods of performance are:

RECOGNIZED HOLIDAYS

The USAF follows the federal government holiday schedule. There is no contract requirement for the contractor to provide services on Federal holidays. When contractor personnel at CDM CCI EMSO facilities they will adhere to the federal holiday schedule, as documented below and are not required to provide service on federal holidays. The same will hold true for any other days that are appropriately designated as a federal holiday during the period of performance:

Independence Day

HOURS OF OPERATION

When the contractor staff work on-site at the CDM CCI EMSO facilities, the contractor is responsible for conducting business between the hours of 0600 to 1800 local time, Monday through Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. The contractor will not be reimbursed when the government facility is closed for the above reasons. The Contractor must maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

Telework is approved by the Contracting Officer Representative.

On site personal are subject to Government closures / shutdowns or adverse weather and shall follow the Government’s policies and procedures. The Contracting Officer will provide specific instructions in the event of a Government shutdown due to funding issues.

2.4 PLACE OF PERFORMANCE

The contractor will work on-site within CDM CCI EMSO facilities in the National Capitol Region (NCR). Currently CDM CCI EMSO hosts sites at Fort Washington, MD, Fairfax, VA, and the Warrington Training Center. On-site contractors will work within a Sensitive Compartmented Information Facility (SCIF).

2.5 SECURITY

On site technical service contractor personnel performing work under this contract must have a TOP SECRET clearance with SCI eligibility to work within the CDM facility and support JTIM integration and architecture engineering.. A Secret Background Investigation is required to access the DAF NIPRnet and SIPRnet environment. The security requirements are in accordance with the attached DD254.

2.6 PHYSICAL SECURITY

The contractor shall be responsible for safeguarding all government equipment, information and property provided for contractor use and in compliance with CDM security standard operating procedures.

2.7 POST AWARD CONFERENCE/PERIODIC PROGRESS MEETINGS

The contractor shall contact the COR within five (5) business days of contract award to schedule Kick-Off meeting.

The contractor agrees to attend any post award conference convened by the contracting activity or contract administrative office in accordance with Federal Acquisition Regulation (FAR) Subpart 42.5. The Contracting Office (CO), Contracting Officers Representative (COR) and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. This includes a monthly Program Management Review (PMR) meeting. At these meetings, the CO will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues. These meetings shall be at no additional cost to the government.

Additionally, the contractor shall:

· Conduct project specific meetings (project team members) to ensure team activities are cohesive and effective, weekly with EMSO JTIM Technical Leads

· Conduct monthly crosstalk technical/analytical team knowledge exchange with DAF C-InT operations staff

· Schedule monthly PMR/Technical Interexchange Meeting with the CCI EMSO Director Technical Leads

· Other events such as discussions and demonstrations with distinguished visitors as required and coordinated with the DAF C-InT Technical Lead.

Meetings may be on-site in-person meeting or virtual as conditions dictate.

2.8 CONTRACTING OFFICER REPRESENTATIVE (COR)

The (COR) will be identified by separate letter. 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, and

· coordinate 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.

2.9 IDENTIFICATION OF CONTRACTOR EMPLOYEES

All contract personnel attending meetings, working at DAF CDM facilities, 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.

2.10 TRAVEL

Contractor will be required to travel CONUS/OCONUS during the performance of this contract to attend meetings, conferences, and training. The government can not accurate project the specific travel dates at this time and request the contractor provide a travel plug of $25,000 in the first year with inflation included in the following years. Specific travel dates, locations, and durations will be provided by the COR as known.

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.

2.11 DATA RIGHTS AND NON-COMMERCIAL COMPUTER SOFTWARE.

· The Government’s rights in non-commercial technical data and software deliverables shall be governed by DFARS 252.227-7013 and DFARS 252.227-7014, respectively. The Government's rights in commercial technical data deliverables shall be governed by DFARS 252.227-7015. All non-commercial software deliverables shall be properly marked in accordance with the marking requirements set forth in DFARS 252.227-7014(f). Technical data and software deliverables with non-conforming restrictive markings shall be rejected and corrected by the Contractor at the Contractor's expense, in accordance with DFARS 252.227-7013(h)(2) and DFARS 252.227- 7014(h)(2) respectively. A current version of the Data Rights Assertion List governing all Prime and sub-Contractors (including sub-contractors from previous Task Orders) shall be included in the Proposal.

· The Government’s rights in commercial technical data shall be governed by DFARS 252.227-7015.

· The Government shall not award this contract or any task order unless the corresponding commercial software license agreements are reviewed and approved by the Contracting Officer. The Government shall not accept any commercial software license terms that conflict with federal procurement law or do not satisfy user needs. Commercial Software License terms that are unacceptable to the Government include (but are not limited to) indemnification provisions (and other types of provisions that include unauthorized or unbudgeted funding obligations), attorney's fees provision, state or foreign choice of law/jurisdiction provisions, binding arbitration provisions, and injunctive relief provisions.

2.12 ORGANIZATIONAL CONFLICTS 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 and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies, as he or she deems necessary, including prohibiting the contractor from participation in subsequent contracted requirements which may be affected by the OCI.

2.13 GOVERNMENT FURNISHED PROPERTY/INFORMATION

The Government may provide government configured laptops to support remote work using AFNet security stacks. The contractor will be responsible for any GFE provided until its return.

Performance REQUIREMENTS Successful execution of this task requires an extensive set of skills to serve as the JTIM Integrator (JTIM Integrated Master Schedule shown in Appendix A). Critial skills required are:

· Hands-on knowledge and experience in DevSecOps platforms, including but not limited to those offered by commercial vendors such as AWS.

· Systems Engineering experience that spans multiple domains, including but not limited to ISR, Targeting, Object Based Intelligence.

· Engineering research projects that attest to competence in related areas.

· Solution Architecture and Database Engineering in mission critical areas.

· 6. Over The Horizon Radar (OTHR) expertise.

· Prior knowledge of Intelligence, Surveillance and Reconnaissance (ISR), coupled with domain knowledge of joint targeting lifecycle (JTC) experience.

· In-depth knowledges of the JTIM FOS capabilities and requirements, to include Coalition Intelligence Systems

· In-depth knowledge of the Key Performance Measures, Operational, System, High Level Requirements and Derived Low Level Requirement requirements that make up the JTIM FOS

· Informent Exchange Requirements internal and external to the JTIM FOS

· Expert DoD and Intelligence Community system architecture, systems and system integration

This work is designed to provide these high-level capabilities.

· System Engineering-

· System Integration and Test Support

· System Migration Support

· Coalition Sharing

· Enteprise Architecture (Optional)

Specific tasks are in the following subparagraphs.

System Engineering The contractor shall have the capability to guide and coordinate the development and integration of new technologies into existing system architectures of major Military Intelligence Programs. The contractor shall utilize systems integration engineering and solutions architecture approaches to ensure that time-critical task objectives and system criteria requirements are fulfilled. Specific required capabilities are:

1. Provide system engineering and integration support for JTIM. This includes all aspects of system architecture, engineering, integration and supporting activities. Contribute to System Engineering Plans (SEP), ensure all JTIM FOS programs are apprised of the proposed system engineering approach.

2. Provide Cloud and DevSecOps engineering expertise, as it relates to JTIM

3. Provide Cyber Architecture support for JTIM

System Integration and Testing Support The Contractor shall deliver subject matter expertise for system engineering, especially regarding the integration and test of diverse technical areas across JTIM development such as, system development, deployment and integration, resource design, information sharing/interoperability, information assurance, and data engineering. Specific capabilities required are:

1. The Contractor shall provide System Engineering as a resource for CCI EMSO users, such as the Government, or other Contractors.

2. Technical integration of existing Program(s) such as DIEE, IMEA and JTT into WARPATH, which the workflow application under development.

3. The Contractor shall attend planning and development workshops, meetings, and engagements as needed to provide system engineering expertise.

4. The Contractor shall ensure that all integration and deployment efforts make use of Government-Approved JTIM solutions, be they software, packages, tools, or other resources

Critical to this task area is insuring senior leadership within EMSO, J2T and OUSD(I&S) are aware of the complex technical and management issues to related to a successful outcome for JTIM.

System Migration Support The contract shall support various combatant commands (CCMD) in planning and scheduling their targeting workiload into JITC. This includes analyzing CCMD system s to ensure any updates they needed for are in place, effective, and suitable to enable the migration to the JIWM solutions. The contractor will provide technical oversight to ensure the necessary underlying components such as DIA’s MIDB and MARS are ready for the JTIM modernization efforts. Further, the contractor will insure all required Cyber certifications (IATT and ATO) for the JTIM applications are in order.

In support of this task area the contractor will create a migration checklist that is used with each CCMD system to insure all critical aspects are addressed, analyzed, and planned.

Coalition Sharing The contractor will support the EMSO engineering support for all coalition sharing activities within JTIM, including solution design, migration plans, and analyzing system development, deployment and integration activities.

Enterprise Architectures (Optional Task) Under this optional task the contractor shall provide upto four full time Enterprise Architects to support EMSO intelligence enterprise architecture mission. The contractor shall be competent using Dassults CAMEO Enterprise Architecture software to develop business process models, JCIDS documentation (including ICDs, CDDs DODAF views), determine novel execution and operating strategies, and derive resource requirements. The contractor will support CCI EMSO’s mission to guide and coordated CCMD, Agency, and Service Enterprise Arcitectures in the establishment of the Joint Intelligence Archetecture. Key activies in this optional task area:

1. Providing DoDAF architectural documentation and specifications in support of annual OUSD(I&S) guidance, the CCI EMSO Program of Work with OUSD I&S, or related annual directives.

2. Capturing and sharing existing architecture documentation relevant to the CCMD or to CCI EA, to include specific service provider, system, component command, or other technical architectures in within the government furnished Cameo Magic, EA software/knowledge management tool, and others within the Assessment Environment, to establish an enterprise baseline.

3. Provide technical support services to implement and operate the CCI EMSO’s Enterprise Architectural capability (Cameo within AWS) and support enterprise architects with it us.

4. Provide and updating an EA Style Guide to be reviewed quarterly.

Service Delivery Summary

deliverables The Contractor shall create, maintain, and update the deliverables in the performance of this PWS as indicated below. Any deliverable defined in this PWS shall be submitted to the COR, and signed by a representative designated by the company unless otherwise noted. Digitally signed email is a suitable transition method. The list of deliverables is in Table 1. See basic contract for additional information.

Table 1. Deliverables

UNCLASSIFIED//FOR OFFICIAL USE ONLY

DRAFT 10/09/2024

UNCLASSIFIED//FOR OFFICIAL USE ONLY

Appendix A – JTIM Integrated Master Schedule (IMS) image1.png image2.png image3.png