Attachment 01 JEDD Performance Work Statement.pdf

Performance Work Statement (PWS) - Joint Education and Doctrine Support

1. Objective

Acquire high quality analytic, editorial, publishing, and online development and distribution of products that support the Chairman of the Joint Chief of Staff’s (CJCS) statutory requirement to provide education and doctrine to the joint force and manage the Universal Joint Task List (UJTL) to directly support readiness reporting and training.

2. Background

Title 10 United States Code directs the Chairman to develop joint doctrine for the Armed Forces, formulate policies for Joint Professional Military Education (JPME), and evaluate the preparedness and readiness of the joint force.

The Joint Education and Doctrine Division (JEDD), Joint Staff (JS) J-7, manages joint doctrine development and electronic publishing, provides oversight of JPME programs, and maintains the UJTL for the Chairman by leveraging unique government capabilities split between the Pentagon and the Joint Staff J-7 element located in

Suffolk, Virginia. The Government’s requirements for both the Pentagon and Suffolk on-site staff and off-site staff are executed under a single contract vehicle to enable the contractor to optimize resources, provide flexibility, and bring best value to the government. Specific geographic locations are not required for off-site personnel but must be in the Continental United States.

The Joint Doctrine Program is responsible for maintaining the CJCS’s doctrine library to ensure that the most current and relevant principles and practices are available to the Warfighter. Maintaining the joint doctrine library involves continually assessing the products and publications that comprise it and regularly updating those determined to be out of date. In addition to maintaining the existing library, the Joint Doctrine Program develops new publications and products, when required to fill a void in existing doctrine. The program is also responsible for managing the Department of Defense (DoD) terminology program and developing the U.S. position on the North

Atlantic Treaty Organization’s (NATO) Allied doctrine and terminology. To execute these responsibilities the Joint

Doctrine Program establishes policy, conducts program management and analysis, schedules projects, staffs and coordinates products, edits content, and publishes approved doctrine products. The Joint Doctrine Program is conducted from locations in the Pentagon and Suffolk, Virginia.

The JPME Program is responsible for developing policies that governs officers and enlisted JPME and the National

Defense University. The JPME Program coordinates and executes post-graduation assessments, provides oversight to the Military Education Assessment Advisory Committee (MEAAC) and manages the joint accreditation of JPME programs. The JPME Program is also responsible for developing and maintaining the Joint Accreditation

Management Information System (JAMIS) that automates data collection, analysis, and reporting required to evaluate the effectiveness of JPME programs in achieving program learning outcomes. The JPME Program is conducted from the Pentagon.

The UJTL Program is responsible for policy, program management, scheduling, staffing, coordination, and publishing of approved tasks within the UJTL to directly support planning, readiness reporting, and training. The

UJTL is used by all Combatant Commands (CCMDs), Combat Support Agencies (CSAs), National Guard Bureau

(NGB) and Services to determine and report mission readiness, as well as develop and assess joint training. Joint

Mission Essential Task Lists (JMETLs) must be selected from the approved UJTL in Defense Readiness Reporting

System (DRRS) to report readiness. Services and CSAs map up or are command linked to the UJTs they support.

UJTs are developed and revised using the UJTL Task Development Tool (UTDT), a collaborative software program used by the Joint Community to establish baseline standards for mission essential tasks. The UJTL program is conducted from Suffolk, Virginia.

3. Scope

This PWS includes task order deliverables that support JEDD. Although each requirement and deliverable are distinct, all are inter-related through mature and well-defined Chairman’s programs to provide joint doctrine, JPME policy, and the UJTL for the joint warfighter.

4. Applicable Documents

The most current revisions of the following documents are related to this project:

CJCSI 5120.02 Joint Doctrine System

CJCSM 5120.01 Joint Doctrine Development and Revision Process

JSM 5100.07 Organizations and Functions of the Joint Staff for Joint Force Development, J-7

CJCSI 3500.02 Universal Joint Task List Program

CJCSI 5705.01 Standardization of Military and Associated Terminology

CJCSM 3500.04 Universal Joint Task Manual

CJCSI 1800.01 Officer Professional Military Education Policy

CJCSI 2700.01 Rationalization, Standardization, and Interoperability Activities

CJCSI 5123.01 Charter of the Joint Requirements Oversight Council and Implementation of the Joint Capabilities

Integration and Development System

CJCSI 5711.01 Action Processing Policy and Procedures

Part 117 of Title 32, Code of Federal Regulations - National Industrial Security Program Operating Manual

(NISPOM)

DoDM 8140.03 Cyberspace Workforce Qualification and Management Program

DoDI 8500.01 Cybersecurity

DoDI 8510.01 Risk Management Framework for DoD Systems

CJCSM 1810.01 Outcomes-Based Military Education Procedures for Officer Professional Military Education

DoDI 8910.01 DoD Implementation of the Paperwork Reduction Act

DoDI 1322.35, Vol. 1 Military Education: Program Management and Administration

DoDD 7730.65 DoD Readiness Reporting System

DoDI 7730.66 Readiness Reporting Guidance for Defense Readiness Reporting System

CJCSM 3500.03 Joint Training Manual for the Armed Forces of the United States

CJCSI 3500.01 Joint Training Policy for the Armed Forces of the United States

CJCSI 3401.02 Force Readiness Reporting

NIST SP 800-37 Guide for Applying the Risk Management Framework to Federal Information Systems

DoDI 5200.44 Protection of Mission Critical Functions to Achieve Trusted Systems and Networks

Joint Staff J-7 Universal Joint Task List (UJTL) Program Standard Operating Procedures

5. Requirements

The following section specifies the performance requirements and associated tasks for the contract.

5.1 Provide Program Management oversight of the Joint Staff’s Joint Doctrine, JPME and UJTL programs.

The contractor shall provide a monthly summary of tasks completed, status of tasks in progress, issues, labor hours expended, and travel costs for the previous month at the third work breakdown structure task level encompassing the

Joint Staff Doctrine, JPME and UJTL Programs, and Joint Doctrine, Education and Training Electronic Information

System (JDEIS) efforts within 10 business days after closing of contractor’s monthly accounting period (A001).

The contractor shall ensure tasking is within the task order scope and funding levels, and report any emergent issues with staffing, funding, or contract scope to the government’s Contracting Officer Representative (COR) within 5 business days with a proposed solution. The contractor shall also provide a quarterly progress review (A002) addressing specific accomplishments, planned activities, key personnel changes, funding, travel, and issues/problems. Contractor oversight may be performed at the location that provides the best value to the government unless specified otherwise in the following sections.

Performance Standards

Standard:

1. Monthly Status Report submitted within 10 business days after closing of contractor’s monthly accounting period (A001).

2. Quarterly Progress Review is held within 10 business days after the end of each quarter (A002).

3. Identification of proposed plan and timeline for correction of emergent deficiencies to COR in cost, schedule, or manning within 5 business days after problem is identified.

4. The contractor shall ensure the continuity of all projects with qualified personnel during turn-over of task order personnel.

5. Billets filled with qualified personnel within 45 business days of identification of a manning shortage or turnover.

AQL:

1. 90% of contractor positions must be filled within 45 days.

2. 95% of cost and schedule deficiencies must be resolved within the specified timeframe agreed upon by the government and the contractor.

3. 95% of deliverables are submitted on time.

Consequence for Non-Compliance:

Products lacking sufficient detail will be returned for revision, or feedback will be provided for improvement in future reports. Deliverables provided more than week after the due date may be documented in the contractor’s

Contractors Performance Assessment Reporting System (CPARS). Continued non-compliance may be addressed per

7.2 - Quality Assurance Surveillance Plan (QASP).

Deliverables

A001 Monthly Status Report to include Monthly Invoice and Expenditure Report

A002 Quarterly Progress Review

5.2 Joint Doctrine Support

The contractor shall provide support in the areas of project management; doctrine subject matter expertise in the

Joint Doctrine development and revision process; publication formatting, electronic publishing; and distribution of joint doctrine; and terminology. A Top Secret clearance with access to Special Compartmented Information

(TS/SCI) is required for all personnel on-site at the Pentagon and is only required for contractor personnel in Suffolk needing access to TS/SCI information in performance of the contract. The contractor shall utilize the tools and applications that facilitate the assessment and development of joint doctrine publications. Use of innovative methods

(e.g. using federal government-approved Artificial Intelligence (AI), such as Large Language Models (LLM) to support analytical, writing, and editing tasks associated with doctrine development and improve efficiency or effectiveness of work performance and product(s) are highly encouraged. Only those AI tools authorized by the government on approved networks or environments shall be used. Contractor personnel shall not input, upload, or otherwise expose any classified, Controlled Unclassified Information (CUI) or sensitive data into non-government approved AI tools, nor into government tools where the information is processed at a classification level higher than the tool classification level. All use of AI tools shall comply with applicable DoD policies, data protection standards, and information security requirements. Sufficient support must be available throughout the duty day to work on the various information suites on which doctrine resides, to include the Non-classified Internet Protocol (IP)

Router Network (NIPRNet), Secure Internet Protocol Router Network (SIPRNet), and the Joint Worldwide

Intelligence Communications System (JWICS).

1. Trip Reports shall be submitted within five (5) business days of travel completion and shall, at a minimum, provide the purpose of the trip, dates, locations visited, key activities, key achievements, challenges, lessons learned and recommendations (A003).

2. Informational briefings shall be submitted five (5) business days prior to start of Joint Doctrine Planning

Conference (JDPC), Configuration Management Working Groups, or Joint Working Groups (JWG s) (A004).

Briefings shall be of high quality, containing factually correct, relevant, concise and actionable information tailored to the O-6/GS-15 level.

3. Running assessments supporting the development and revision of joint doctrine should be completed no later than one month prior to the start of a publication revision (A005). They shall provide an in-depth analysis identify content gaps, redundancies, and areas for improvement.

4. Update of UJTL citations/table in Joint Doctrine Publications should be completed no later than one month prior to the start of a publication revision (A006).

5. Allied doctrine research reports to be completed within ten (10) business days of assignment (A007).

6. Special studies to be completed within four (4) to six (6) weeks following assignment (A008).

7. Draft emerging doctrine publications to be completed within four (4) to six (6) months following assignment

(A009).

8. Editorial assessments are proactive and support a collaborative doctrine development and revision process;

content adhering to joint doctrine style manuals and formatting standards. (A010).

9. Coordination drafts shall be edited and formatted for upload to Joint Doctrine Development Tool (JDDT) within five (5) business days (A011).

10. Allied publications shall be formatted for upload to JDDT within five (5) business days (A012).

11. Review of consolidate comment resolution matrices (CRM) shall be conducted concurrently during adjudication and completed within five (5) business days without hindering the overall production timeline

(A013).

12. Graphics to be developed, edited, or formatted within five (5) business days of request (A014).

13. Signature drafts to be developed within fifteen (15) business days (A015). The contractor shall produce signature drafts in Microsoft Word (.docx) and Adobe (.pdf) and IAW joint doctrine editorial standards.

14. Electronically publish updates to Joint Doctrine (parsed and stored as rapidly searchable datasets) within five

(5) business days (A016).

15. Monthly list of DoD dictionary term changes completed no later than the fifth (5th) business day of the month

(A017).

16. Joint terminology research reports completed within ten (10) business days following the approval of the program directive (PD) (A018).

17. Allied terminology research reports completed within ten (10) business days following assignment (A019).

1. 98% product submission within approved government timelines and 100% in accordance with applicable

CJCSI/CJCSMs and internal doctrine standard operating procedures (SOPs).

2. Zero factual errors and no more than one minor formatting or grammatical error per product unless it is a review not intended as a comprehensive edit as specified in Sections 5.2.4 and 5.4.2.1 below.

Products with factual, major formatting and grammatical errors, lacking sufficient detail, or not compliant with policy or SOPs will be returned for revision, or feedback will be provided for improvement in future reports.

Continued non-compliance shall be addressed per 7.2 - Quality Assurance Surveillance Plan (QASP).

A003 Doctrine Trip Reports

A004 Informational Briefings

A005 Running Assessments

A006 UJTL Citations and Table

A007 Allied Doctrine Research Reports

A008 Special Studies

A009 Emerging Doctrine Publications

A010 Editorial Assessment of Joint Doctrine Publications

A011 Edited and Formatted Coordination Drafts of Joint Doctrine Publications (for JDDT)

A012 Formatted Allied Publications (for JDDT)

A013 Adjudicated Consolidated Comment Resolution Matrices Reviews

A014 Graphics (new or edited)

A015 Signature Draft

A016 Electronic Publishing

A017 Monthly DoD Dictionary Term Change Report

A018 Joint Terminology Research Report

A019 Allied Terminology Research Report

5.2.1 Implement and Sustain On-site Doctrine Project Management Support

Provide on-site project management support for the joint doctrine development process, including tracking and reporting the progress of individual publication efforts, managing organizational workflows, and supporting the development and implementation of SOPs. Support shall also include the facilitation of meetings and conferences organized by military and government personnel, to include project meetings, weekly doctrine reviews, JWGs, and the semi-annual JDPC. The contractor shall ensure that trip reports are submitted within five (5) business days of travel completion (A003).

5.2.2 Working Group, Conference, and Meeting Support

The contractor shall coordinate doctrine working groups, conferences, and other meetings as required. Required support includes developing read-ahead packages, assisting with briefing development, establishing, and managing distributed collaboration capability (e.g.: Microsoft Teams, video teleconferencing, etc.), annotating CRM changes during JWGs, as well as providing escort for events within the division and on-site/off-site event facilitation.

Required support may also include the development and presentation of information briefings (A004) on doctrine matters. Anticipate providing support for up to two (2) annual JDPCs per year, two (2) Configuration Management

Working Groups per year, and up to one (1) JWG per month during the period of this task order. Briefings shall be submitted within five (5) business days prior to start of JDPC, Configuration Management Working Group, or JWG.

Location of these meetings will be at the discretion of the government in providing the most cost-effective venue for the audience in question, generally in the vicinity of either the Pentagon, the JS J-7 Suffolk building, virtually, or combination thereof. When requested by the government, the contractor shall provide meeting space with sufficient technology equipment and support to host or facilitate these events.

5.2.3 On-site Subject Matter Expertise to the Joint Doctrine Development and Revision Process

The contractor shall provide on-site doctrine analysis to be split between the Pentagon and JS J-7 Suffolk supporting the development and revision of joint doctrine with detailed and in-depth analysis of doctrine and related information to enable the government to maintain the joint doctrine library with the most current and relevant content. The contractor shall perform up to six (6) comprehensive reviews and running assessments (A005) of joint doctrine to identify content gaps, redundancies, and areas for improvement. Running assessments should be completed no later than one month prior to the start of a publication revision.

As part of the doctrine revision process, or when administrative or urgent changes are made to signed/published publications, the contractor shall review, analyze, and validate UJTL citations in the publication, incorporate new

UJTL citations, and update the publication’s associated UJTL table within the JP. Contractor should anticipate updating UJTL citations and table for up to fifteen (15) JPs annually (A006). Update of UJTL citations and table should be completed no later than one month prior to the start of a publication revision.

5.2.3.1 Support Allied Doctrine Revision

The contractor shall review and analyze allied doctrine publications to support revisions efforts. Support shall include reviewing and analyzing allied doctrine publications and CRMs and producing research reports to inform government on issues such as alignment of doctrine concepts or identifying gaps or deficiencies in the publication.

Provide input and analysis on up to ten (10) allied doctrine research reports (A007). Reports to be completed within ten (10) business days of assignment.

5.2.3.2 Produce Special Studies

The contractor shall produce special studies on topics related to joint doctrine publication development, evolving operational practices, or other force employment or design-related issues, as directed by the government. These studies are intended to support the development and refinement of joint doctrine by providing original analysis and insights. Topics for special studies will be determined by the government and may include, but are not limited to, emerging concepts, wargames, exercises, and lessons learned. Each study is generally expected to be completed within 4 to 6 weeks of assignment. The contractor is expected to coordinate and collaborate with other Joint Staff directorates, Services, Combatant Commands, and members of the Joint Doctrine Development Community (JDDC) as needed to inform the study. Anticipate up to up to sixteen (16) special studies annually (A008).

5.2.3.3 Produce Emerging Doctrine Reviews and Reports

The contractor shall produce emerging doctrine. Emerging doctrine provides an in-depth analysis of concepts, wargaming, and experimentation, and their potential impact to current joint doctrine. Emerging doctrine can identify emerging capabilities and/or operational trends/imperatives, for incorporation into current joint doctrinal publications. Emerging doctrine can also take the form of a specific appendix to a current joint publication. This task includes analysis and publication development/revision to incorporate relevant Joint Warfighting Concept

(JWC) content in support of warfighter actions during Elite Constellation (EC) or similar events, wargames, and/or exercises; incorporating content from other emerging doctrine; and updating joint doctrine as informed by EC lessons learned. Anticipate up to two (2) emerging doctrine publications annually (A009). Development of emerging doctrine is generally expected to take 4 to 6 months following assignment.

5.2.4 Editorial Support for Joint Doctrine Publication Development

The contractor shall provide editorial assessment to assist the JDDC during the creation and revision of joint doctrine publications. The support includes active participation in collaborative environments (e.g., Microsoft

Teams) to identify and resolve formatting, grammatical, and stylistic issues early in the drafting process, thereby streamlining workflow and enhancing the overall quality of the publications. The editorial assessment is not intended to be a comprehensive edit but should focus on identifying and flagging critical issues including but not limited to grammatical errors (such as use of passive voice), unclear or ambiguous language, terminology inconsistent with joint doctrine, and language that is difficult to understand. Make recommend solutions and improvements aligned with established joint doctrine style guides as well as standards and best practices. Provide constructive feedback to authors that facilitates iterative improvements without impeding content development.

Editorial assessments must adhere to joint doctrine style manuals and formatting standards. Anticipate the review and assessment of up to fifteen (15) joint doctrine publications annually (A010).

5.2.4.1 Edit and Format Coordination Drafts

The contractor shall edit and format coordination drafts of joint doctrine publications (e.g., joint publications, Joint

Doctrine Notes (JDNs), and emerging doctrine) for upload into JDDT. Editors shall complete the review and formatting within five (5) business days. This review is not intended as a comprehensive edit but shall focus on identifying and flagging significant issues, including major grammatical and spelling errors. Formatted publications may include quotes, vignettes, images, and graphics. The contractor shall use government-directed tools, platforms, and methods to complete these tasks and shall be prepared to edit, format, and upload up to fifteen (15) joint publications (A011) annually. The contractor shall format and upload up to eight (8) allied publications into JDDT

(A012).

5.2.4.2 Review and Edit Consolidated Comment Resolution Matrix

The contractor shall collaboratively review up to fifteen (15) adjudicated JWG CRMs annually (A013), ensuring adjudicated items are free of major technical and grammatical errors and consistent with joint doctrine standards.

Reviews shall be conducted concurrently during adjudication and completed within five (5) business days without hindering the overall production timeline.

5.2.4.3 Graphics Support

Provide graphic technical assistance to include the development of original graphics or editing of current graphics for both electronic and paper publications; conversion of electronic graphic files from one format to another;

processing video and photo files; processing files to portable document format; installing hyperlinks in electronic files; and maintenance of photo library and other graphic archival data. Contractor shall anticipate developing or editing up forty (40) graphics (A014).

5.2.4.4 Edit and Format Signature Draft

The contractor shall use the approved CRM to prepare a signature draft of joint doctrine publications. The contractor shall produce signature drafts in Microsoft Word (.docx) and Adobe (.pdf) and IAW joint doctrine editorial standards. The contractor shall anticipate preparing (editing and formatting) up to fifteen (15) joint publications annually with each signature draft developed within fifteen (15) business days (A015).

5.2.5 Publish and Distribute Joint Doctrine and Associated Products Electronically

The contractor shall electronically publish and distribute joint doctrine and associated products identified in this work statement using the online capabilities and tools described in Section 5.3 below. (A016) Joint publications and select other content shall be parsed and stored as rapidly searchable datasets which facilitates cross-indexing, linking and discovery of joint doctrine and related content. Content updates shall be completed within 5 business days following the approved update/change/addition/deletion to joint doctrine publications.

5.2.6 Maintain the Online Terminology Research Databases

The contractor shall maintain databases of approved joint terminology that are searchable online as part of the Joint

Electronic Library (JEL)/Joint Electronic Library Plus (JEL+) (Personal Identity Verification (PIV) Protected)

(NIPRNet and SIPRNet) web portals and provide a monthly report of DoD Dictionary term changes (A017) to the

DoD Terminologist or other designated government representative in a formatted excel spreadsheet. Incorporate proposed changes to terms and definitions provided by the DoD Terminologist into the Joint Terminology Master

Database (JTMD) for new or revised JPs and/or IAW DoD Dictionary of Military and Associated Terms, CJCSI

5120.02, CJCSI 5705.01, or other official DoD directives and memorandums. Prepare and forward joint terminology research reports outlining terms sourced to JPs to the lead agent (A018) within ten (10) business days following approval of the Program Directive (PD) to assist in the publication revision. The contractor shall anticipate preparing up to fifteen (15) joint terminology research reports annually. The contractor may also support the review of allied terminology by providing allied terminology research reports (A019). The contractor shall anticipate preparing up to eight (8) allied terminology research reports annually and to be completed within ten (10) business days following assignment.

5.3 Maintain and update electronic publishing capability and online tools for product development and staffing.

The Contractor shall maintain and update the electronic publication and distribution capabilities of the following

Joint Doctrine, Education, and Training Electronic Information System (JDEIS) applications: Joint Electronic

Library (JEL) on the internet, JEL+, an approved PIV protected DoD hosting network or enclave, and JEL+

SIPRNet, an approved classified network. The Contractor shall also maintain and update electronic tools for the online development, collaboration, revisions, updates, and electronic staffing of joint publications on the NIPRNet

Joint Doctrine Development Tool (JDDT) (also referred to as JDDT-N) and associated Joint Master Terminology

Database (JTMD); JDDT SIPRNet (also referred to as JDDT-S) for classified and limited distribution publications;

tracking and actions related to joint publications through their development cycle on the Joint Publication

Management Tool (JPMT); development and staffing of Universal Joint Tasks (UJTs) on the UJTL Task

Development Tool (UTDT); and accredit DoD educational institutions and support congressionally mandated annual reporting on the JPME Joint Accreditation Management Information System (JAMIS). The user interface and other

"look and feel” aspects of JEL and JEL+ are determined by the Government and may require contractor revision.

The contractor shall estimate the hardware/software cost for the 5 NIPR and 2 SIPR applications and 2 websites across three separate environments: Production, Test/Staging, and Development. All online publishing capabilities and tools shall be delivered with full authority to operate (ATO) on approved networks and service providers and associated documentation (A020). The Contractor shall have experience and be proficient in designing database tables and schema designs to support, document, optimize, and improve application development responsiveness.

Use of innovative methods (e.g. using federal government-approved AI, LLM) to improve efficiency or effectiveness of work performance and product(s) are highly encouraged. Only those AI tools authorized by the government within approved networks or environments shall be used. Contractor personnel shall not input, upload, or otherwise expose any classified, CUI, or sensitive data into non-government approved AI tools. All use of AI tools shall comply with applicable DoD policies, data protection standards, and information security requirements.

The contractor shall hold weekly informal JDEIS IT updates and monthly collaboration meetings with the

Government system owner/Program Manager (PM).

1. Tasks that have the potential to interrupt DoD community users’ accessibility to JDEIS applications (UTDT, JDDT, JDDT SIPR, JPMT and JPME JAMIS) are performed outside of normal work hours.

2. Online publishing capabilities and tools delivered with full ATO (A020) for each: JEL, JEL+, JEL+SIPR, JDDT, UTDT, and JAMIS.

3. Briefing slides for JDEIS meetings, working groups, and conferences submitted a minimum of 1 week prior to event. (A021)

3. Bi-Annual JEL, JEL+, and JEL+ SIPRNet metrics and other status reports shall be delivered every 6 months from the start of the contract. (A022).

4. Business practices, procedures, and rules for all JDEIS applications shall be updated within one (1) month of new tool launch or update (A023).

5. Update of application user guides NLT one (1) month when after requested by the government, a new version is deployed, and/or major updates or new features have been added (A024).

6. Confirmation of application help ticket receipt and/or closure within 48 hours, and no longer than 1 week to resolve.

7. Document all externally received requests, bugs, and enhancement within record or helpdesk within 48 hours of receipt

8. Validation testing, acceptance support and installation for interim patches and new software completed within one (1) month of the launch of a new tool or update (A025).

9. Deployment instructions for all JDEIS applications within 4 months of contract award and within a month of when a new version is deployed (A026).

10. JDEIS applications maintained and updated no less than once weekly

11. JDEIS NIPR and SIPR ATO sixty (60) to ninety (90) days prior to Authorization Termination Date (ATD)

(A027).

12. Fulfill all requested Risk Management (RMF) requirements 2 weeks prior to government suspense date.

(A028)

13. Maintain, backup, and provide updates to the database after a large database update or change, or at a minimum, on a monthly basis as required for policy compliance.

15. ATO Conditions mitigated within 30 days of the Authorization Termination Date, or per a POA&M when applicable (A029).

16. Operationalize API for data exchange within 4 months of contract execution and training and/or documentation 1 month following (A030).

1. Electronic publication and distribution capabilities 100% compliant with established guidelines in CJCSI

5120.02 and Joint Staff internal SOPs.

2. 0% Data loss

3. Non-recurrence of defective services.

4. 100% compliance with Risk Management Framework (RMF) requirements.

5. 95% completion within approved government timelines.

6. 100% compliance with Defense Information Systems Agency (DISA), Joint Staff and DoD policy and guidelines.

The contracting officer may issue a formal Corrective Action Request requiring the contractor to address the non-compliance and provide a plan to prevent future occurrences. Continued non-compliance shall be addressed per 7.2 -

Quality Assurance Surveillance Plan (QASP).

A020 Online Publishing Capabilities and Tools and ATO documentation packages

A021 JDEIS Informational Briefs

A022 JEL, JEL+, and JEL+ SIPRNet Metrics

A023 JDEIS Business Rule, Practices, and Procedures

A024 JDEIS Application User Guide Updates

A025 JDEIS Validation Testing

A026 Deployment Instructions for all JDEIS Applications

A027 JDEIS Authority to Operate

A028 Documentation of RMF Requirements IAW Accreditation and Assessment Procedures

A029 Mitigated ATO Conditions

A030 Operationalized Application Program Interface

A031 Zero Trust Architecture

5.3.1 Support for organizational processes, JDEIS meetings, working groups, and conferences.

Support JDEIS meetings, working groups, and conferences. Provide support for various organizational processes, meetings, and conferences facilitated by military and government employees, project meetings, JDEIS meetings, and working groups. This task includes the development and presentation of briefings on JDEIS matters with drafts provided for review/recommendations/approval a minimum of 1 week prior to the meeting, working group or conference. (A021). Anticipate providing support for up to four (4) annual working groups or trainings during the period of this task order. Location of these meetings shall be at the discretion of the government in providing the most appropriate venue for the audience in question, generally in either the Pentagon area, Suffolk, or virtually.

5.3.2 Joint Education and Doctrine Tools

Electronic tools requiring maintenance and updates include the JEL, JEL+ (NIPRNet and SIPRNet), the JDDT on the NIPRNet (also referred to as JDDT-N), JDDT SIPRNet (JDDT-S) for the Joint Doctrine Program; UTDT for the

UJTL Program and to support readiness and training; and the JAMIS for the JPME Program; as well as other supporting applications such as JTMD, JPMT (if resources permit), the Application Program Interface (API) to provide automatic doctrine, UJTL, and terminology updates to dependent systems and processes.

5.3.2.1 Joint Electronic Library (JEL)

The online JEL website shall be maintained and accessible under jcs.mil and the contractor must comply with required updates. Regarding content, the JEL shall contain publications and other information approved for public release (or a redirect link) at the discretion of the government.

5.3.2.2 Joint Electronic Library + (JEL+)

The JEL+ website shall only be maintained and accessible through the designated Service Provider and/or network service provider (currently DISA) with the understanding that future hosting location may change as systems continue to evolve and mature. The JEL+ shall contain, at minimum, electronic publishing of all material contained on the JEL website including all unclassified joint publications, the most current approved joint terminology to include all approved DoD acronyms and abbreviations, and content restricted to government-only access. Flat files

(static files) in JEL+ mirror the JEL’s content plus draft publications and otherwise restricted content.

5.3.2.3 Joint Electronic Library + SIPRNet (JEL+ SIPRNet)

JEL+ SIPRNet shall be maintained on the SIPRNet classified network and will contain, at minimum, electronic publishing of all content maintained on the JEL+ website plus all classified Joint Publications (JPs), annexes, UJTL classified measures, and related content.

5.3.2.4 Joint Doctrine Development Tool (JDDT)

JDDT NIPRNet, is a government online product development, coordination and staffing tool that shall be maintained on NIPRNet for the development, revision, and coordination of U.S. joint doctrine products. The contractor shall maintain JDDT (and JPMT, if applicable) and provide the capability to accommodate Allied doctrine editing, adjudication, and publication (if resources permit).

5.3.2.5 Joint Doctrine Development Tool (JDDT) SIPR

JDDT SIPRNet is a government online product development, coordination, and staffing tool that shall be maintained on SIPRNet for the development, revision, and coordination of classified and limited distribution joint doctrine products, and limits contributions to those with the appropriate permissions.

5.3.2.6 Joint Terminology Master Database (JTMD)

The JTMD, hosted within JDDT, shall be maintained on NIPRNet as the repository for all terms and definitions, past and present, including shortened word forms, found in the DoD Dictionary of Military and Associated Terms

(i.e. DoD Dictionary). When JPs are signed, the glossary of the JP shall be used to update the JTMD and DoD

Dictionary. This database shall be used to populate the DoD Dictionary Search feature in JEL+.

5.3.2.7 Joint Publication Management Tool (JPMT)

JPMT shall be maintained on the NIPRNet to assist with management of the Joint Doctrine Program and the near real time tracking of each JP through its full lifecycle to include development, assessment, revision, and maintenance. JMPT is available through links on JDDT and JEL+ website. Update and maintenance of this tool shall be based on the direction of the government and associated SOPs delineated for doctrine revision and maintenance.

5.3.2.8 Universal Joint Task List (UJTL) Task Development Tool (UTDT)

UTDT is as a UJTL product development, coordination, staffing, and publication tool for UJTs that shall be maintained on NIPRNet. Enhancements to the tool may include Service Task listings and updates, as well as the

Joint Conditions library maintained by the UJTL Program, as required for policy compliance.

5.3.2.9 JPME Joint Accreditation Management Information System (JAMIS)

The JAMIS is a searchable JPME database and information retrieval system set in an accessible and easy-to-manipulate form to support oversight and compliance monitoring and other senior leader and congressional reporting requirements of JPME programs as articulated in CJCSI 1800.01 and CJCSM 1810 series instructions.

The system facilitates user submission of compliance data and generates standardized reports to facilitate accreditation decisions and meet other requirements as directed. The JAMIS contains the key data elements corresponding to JPME program educational compliance and the government anticipates some revisions to the data fields shall be required. The contractor shall provide statistical calculations, data mining (querying) and automated data report generation features (data visualization) to facilitate required reporting. The contractor shall produce appropriate metrics to examine system performance and evaluate aspects of information content and presentation with the aim of improving the systems and their contents as appropriate. The JAMIS shall be maintained, adapted and accessible through DISA with the understanding that future hosting location may change as systems continue to evolve and mature. This requirement is different from the Prospective Research Topic Database not addressed in this task order.

5.3.3 Provide reports and documentation

Include technical requirements, software and network diagrams, design documents, deployment instructions, business requirement documents, and all other application reports and documentation required by DISA, network operator, or by the request of the government. Support the Risk Management Framework (RMF) with required data and information related to and required for the recertification and reaccreditation of the JDEIS Information

Technology (IT) Enterprise (JEL, JEL+, JEL+ SIPRNet and applications, databases, servers, and other systems), and its components for continued DoD-sanctioned operations, IAW the appropriate DoD hosting agency or enclave.

Assist in routine coordination of the RMF requirements and documentation, in conjunction with DISA, and/or network service provider. This includes documentation requirements of hybrid and service provider owned controls within the record. Provide awareness of upgrades and enhancements to the system required for Section 508 compliance or software development life cycle (SDLC) and research resource requirements. This task may include

RMF required documentation updates, scan reports or documentation (e.g. software assessment risk management

(SwARM)), and other necessary documentation required by network operator to maintain ATO.

5.3.4 Develop capabilities to facilitate and exploit the “data mining” of JEL, JEL+, and JEL+ SIPRNet platforms.

Produce metrics on usage rates, frequency of user access to various features and types of content, etc., in order to examine system performance and evaluate aspects of information content and presentation with the aim of improving the systems and their contents as appropriate, as well as articulate the userbase and impact to users of this system to leadership and in response to taskers. The contractor shall prepare and submit JEL, JEL+, and JEL+

SIPRNet metrics and other status reports bi-annually. (A022).

5.3.5 Adapt, Repair, Update, and Manage all JDEIS applications with integral linkage to JEL+.

Adapt JDEIS applications and related databases; repair bug fixes and tool issues; update and develop the applications, databases, and versions to address stakeholder requirements and policy compliance; and manage and maintain all tools as directed by the government or determined by prioritization.

5.3.6 Update and Promulgate business practices, procedures, and rules for all JDEIS applications.

The contractor shall develop and maintain business rules, practices, and procedures for all JDEIS applications and databases, to include system diagrams and related documentation no later than (NLT) one (1) month of new tool launch or update (A023).

5.3.7 Provide training to government personnel and users on use of JDEIS applications.

This task may include training to the JDDC, UJTL Development Community (UDC), JPME, and others, as deemed necessary by the government. This task also includes the update of application user guides NLT one (1) month after requested by the government, a new version is deployed, and/or major updates or new features have been added.

(A024)

5.3.8 Maintain a UJTL Database.

The Contractor will maintain a searchable UJTL database and information retrieval system in an accessible, and easy-to-manipulate form, so it can support users, reduce revision and development time, and meet other requirements as directed, to include designated data exchange capabilities that remain compliant with Government

IT specifications.

5.3.9 Technical/Help desk Support

Provide operations and maintenance on-call technical support as well as a help desk capability (email, phone, and/or in application help tickets) for JEDD developed software applications and databases (also referred to as JDEIS applications) hosted on the DISA network (or current service provider/network operator) and within other Joint Staff approved domains. Confirmation of application help ticket receipt and/or closure within 48 hours, and no longer than 1 week to resolve.

5.3.10 Maintain a running online record of problems reported and resolutions.

The contractor shall document all problems and enhancements requested, respond and address, accordingly, escalating those requests to the Government Information Systems Owner (ISO) that cannot be resolved by the contractor or requires future prioritization due to IT Lifecycle requirements. All externally received requests, bugs, and enhancement within record or helpdesk shall be documented within 48 hours of receipt.

5.3.11 Provide validation testing, acceptance support and installation for interim patches and new software.

The contractor shall provide validation testing, user acceptance support, and installation of interim patches, new software, and system updates for JDEIS tools and supporting applications (e.g., JEL, JEL+, JDDT-N, JDDT-S, UTDT, UJTL, JAMIS, JTMD, and JPMT) within one (1) month of the launch of a new tool or update. The contractor will seek Government approval prior to release (A025).

5.3.12 Software and Database Documentation

Maintain full and complete software and database documentation and back-up IAW generally accepted DoD and industry standards and practices. Develop and provide to the government deployment instructions for all JDEIS applications within 4 months of contract award and within a month of when a new version is deployed (A026). The deployment instructions will include any interconnected outsourced IT-based processes and interconnected IT platforms with connection rules and requirements. Include un-compiled and compiled source code, configuration files, HyperText Markup Language (HTML), eXtensible Markup Language (XML), and executable and non-executable files used in the fully functional systems.

5.3.13 Provide IT System Management

The Contractor shall maintain and update no less than once weekly JDEIS applications, to include the JEL, JEL+, and JEL+SIPRNet, JDDT, JDDT SIPRNet, UTDT, JPMT (as necessary) and JAMIS based on this document and/or as amended by mutual agreement with the Government. JEL+, and JEL+ SIPRNet provide a searchable database of approved joint doctrine, cross-referenced to other datasets and the UJTL; other datasets shall be included at

Government direction. Manage and maintain existing tabs, databases, and elements as required on JEL+. The

Contractor shall deploy a capability for network-centric data sharing with designated other DoD IT systems and maintain the JEL on the Internet to provide public-facing access for all relevant unlimited-distribution content.

Changes to software and delineation of priorities to be executed by the Contractor to JDEIS applications will be approved by the Government ISO.

5.3.13.1 Risk Management Framework/Authority to Operate/Cybersecurity Management.

The contractor shall provide systems with ATO and manage cybersecurity. The following DoDM 8140.03 minimum level of certifications are applicable for support to:

1. Maintain databases of approved joint terminology that are searchable online as part of the JEL+ (NIPRNet and

SIPRNet) web portals and research databases: Information Assurance Technical (IAT) I

2. Maintain a deployed version of the JDDT-N and JDDT-S as an integral feature of the JEL+ portal on NIPRNet and SIPRNet: IAT I

3. Develop capabilities to facilitate and exploit the “data mining” of JEL, JEL+, and JEL+ SIPRNet: IAT I

4. Adapt, Repair, Update, and Manage the UTDT: IAT I

5. Develop, Implement, and Maintain the UJTL Database: IAT I

6. Provide Life Cycle Maintenance for user support and software maintenance: IAT I

7. Provide validation testing, acceptance support and installation for interim patches and new software: IAT I

8. Provide IT System Management for JEL, JEL+, JEL+ SIPRNet, JDDT, UTDT and JAMIS: Information

Assurance Management (IAM) I

9. Provide Risk Mitigation Plan (RMP): IAT I

10. Perform Software Development: IAT I

11. Conduct software development: IAT I

12. DoD Common Access Card/Public Key Infrastructure and Personal Identity Verification authentication: IAT I

Source Code: IAT I

13. Procedural Language/Structured Query Language Procedures: IAT I Support Cybersecurity: IAT I

14. Cybersecurity/Information Assurance plan: IAT I

15. Deployment Guide: IAT I

16. System Security Plan: IAT I

17. Critical Security Modules: IAT I

5.3.13.2 Information System Security and Cybersecurity.

The contractor shall provide cyber security and information system security support for all systems and applications delivered under the terms of this contract. Analyze, develop, design, implement, and maintain an organizational or system-level cybersecurity program that includes cybersecurity architecture, requirements, objectives and policies, cybersecurity personnel, and cybersecurity processes and procedures. Assess the information system and report monthly and annual cybersecurity compliance through means of required reporting, as determined by the network operator, authorizing official, or DoD policies. The role of both Information System Security Manager (ISSM) and

Information Systems Security Officer (ISSO) are to be assigned and fulfilled by the contractor. The contractor shall update and maintain the security plan to include technical, administration, and procedural cybersecurity program policies; designation of cybersecurity personnel; identification of the cybersecurity requirements; cybersecurity objectives; and cybersecurity strategy. The contractor shall ensure the system complies with all applicable cybersecurity policies and fulfills all cybersecurity requirements required for JDEIS compliance to have authority to operate on the network as mandated by the service provider and the authorizing official sixty to ninety day prior to the ATD (A027).

5.3.13.3 Risk Management Framework and Authority to Operate.

The contractor shall maintain continuous monitoring of the JDEIS information system through the RMF to maintain and sustain the system’s ATO. This task shall entail continuously assessing JDEIS controls, to include those considered “hybrid,” for compliance and risk, developing plans of actions and milestones for those outstanding controls, and close coordination with the IT/ Cybersecurity Service Provider potentially through service level agreements or other required documentation required for ATO compliance. Analyze, process, and mitigate all controls in response to ATO requirements and all independent security control assessments (e.g. Validation &

Verification (V&V)) processes, throughout the ATO assessment period. The ISSM and ISSO designated by the contractor shall fulfill all RMF requirements 2 weeks prior to government suspense date to include categorizing the system(s); selecting, implementing and assessing security controls; preparing and submitting system authorization;

and continuous monitoring, remediation and updates of security controls to include identifying and assessing system security controls; developing, documenting, providing to the government a System-level Security Plan and Security

Assessment Report; preparing, loading and maintaining required system documentation (artifacts); preparing required authorization documents such as Plan of Action and Milestones (POA&M); and continuously monitoring controls and applying remediation or updates (A028), when necessary, for applicable…