Attachment_3_-_Task_3_-_Engineering_Enterprise_-_PWS.pdf

Amendment 5

OFFICE OF THE DEPUTY ASSITANT SECRETARY OF DEFENSE FOR SYSTEMS

ENGINEERING

Performance Work Statement in support of

Director, Engineering Enterprise

22 February 2016 Amendment 5

Contents Specific Tasks

1 System Assurance and Program Protection

1.1 Systems Engineering (SE) and SwA Capability

1.2 Joint Federated Assurance Center (JFAC)

1.3 Acquisition Security Database

1.4 CPI Identification and Anti-Tamper

1.5 Microelectronics

1.6 System Assurance and Program Protection Support

1.7 Security Engineering Program Support

2 Engineering Tools and Environments

2.1 Engineered Resilient Systems

2.2 Digital Engineering in Design and Engineering

2.2.1 Establishing and advance a stakeholder community

2.2.2 Digital Artifact Management

2.2.3 Transition current education, training, guidance, and where practical

2.2.4 Assist in cross-cutting efforts in Engineering Tools and Environments

2.3 Modular Open System Architecture (MOSA)

3 Systems Engineering (SE) Policy and Guidance (P&G)

3.1 SE Policy and Documentation

3.2 SE Guidance

3.3 Acquisition Documentation Reviews for SE P&G Implementation

3.4 DAU Course and Community of Practice Content Reviews for Consistency with SE P&G 12

3.5 SE P&G Reporting and Outreach

4 Specialty Engineering

4.1 Manufacturing and Quality Engineering

4.1.1 Manufacturing and Quality Engineering Policy, Guidance, and Outreach

4.1.2 Acquisition Review and Analysis

4.2 Diminishing Manufacturing Sources and Material Shortages (DMSMS)

4.3 Value Engineering

4.4 Human Systems Integration (HSI)

4.5 System Safety Engineering

4.6 Reliability and Maintainability (R&M) Engineering

4.6.1 R&M Engineering, Policy, Guidance and Outreach

4.6.2 Acquisition, Review and Analysis

5 Systems Engineering and Analysis

5.1 Family of Systems (FoS) and Systems of Systems (SoS) Analysis

5.2 Systems of Systems (SOS) and Families of Systems (FOS)

6 Specifications and Standards --Defense Standardization Program Office (DSPO)

7 Workforce Development

7.1 Acquisition Workforce

7.2 Engineering (Non-construction) (ENG(NC)) Workforce

7.3 Workforce Policy and Documentation

7.4 Workforce Data Analytics and Workforce Studies

7.5 Workforce Reporting and Outreach

8 Systems Engineering Specifications and Standards (SESS)

9 Information Technology Support

9.1 Interoperability Senior Review Panel

9.2 Information Technology (IT) Standards

9.3 Spectrum Management

10 International Engagement

10.1 The Technical Cooperation Program (TTCP)

11 Support Tasks

11.1 Data Management

11.2 Communities of Practice

11.3 Training

11.4 Special/Other Requirements (Draft)

11.4.1 Data Rights

11.4.2 Security

11.4.3 Work Location

Support to DASD(SE) Enterprise Engineering

Performance Work Statement (PWS)

Professional Engineering Services for the Office of the Director, Engineering Enterprise

Specific Tasks

1 System Assurance and Program Protection The contractor shall provide professional engineering services to assist the DASD(SE) in execution of systems assurance and program protection tasks. The tasks specified in this PWS are intended to advance the state of practice in DoD engineering centers while supporting related MPS tasks in working directly with acquisition programs. These tasks may best be met with a Subject Matter Experts (SMEs) with expertise in Anti-Tamper (AT), Defense Exportability Features (DEF), Critical Program Information (CPI) identification) , hardware assurance (HwA), trusted microelectronics, software assurance (SwA), and cybersecurity (CS).

In support of MPS responsibilities to work with acquisition programs, these contractor SMEs shall support and facilitate the broad stakeholder review of program protection plans (PPPs) and work with other SMEs in these system assurance / program protection domain areas to provide feedback to those programs on the sufficiency of their approaches to system assurance and program protection. Additionally, the contractor will assist DASD(SE) in writing and promulgating best practices and updating related policy and guidance.

The contractor efforts under this PWS need to be able to support the broad range of system domain areas that are supported, managed, and overseen by the Office of the Secretary of Defense (OSD), e.g., ODASD(SE)/Major Program Support (MPS) Major Defense Acquisition Program (MDAP)/Major Automated Information System (MAIS) Program Support Team Lead domains (i.e., Fixed Wing, Space & Missile Defense, Ships/Subs, Land Combat/Communications, Rotary Wing and C3ISR/Business systems). In addition, the policy, guidance, studies, recommendations, and other products that are developed under this TWS need to consider their applicability and practicality of use across the acquisition lifecycle.

For clearance requirements see subsection of this task.

1.1 Systems Engineering (SE) and SwA Capability

The contractor shall support DASD(SE) in advancing the state of practice of SwA as a system security engineering (SSE) discipline that operates continuously across the acquisition lifecycle. This shall include the development or review of policy, acquisition and technical guidance, strategy, methods, technology expertise, operation, and technology roadmaps, as directed by the government. The contractor shall support implementation activities outlined in the 2011 National Defense Authorization Act (NDAA), Section 932 Report to Congress, 2013 NDAA Section 933, 2014 NDAA Section 937, subsequent NDAA sections addressing SwA, and preparation and collection of data for related Government Accountability Office (GAO) and DoD Inspector General (IG) inquiries.

The contractor shall support the development and recommendation to DASD(SE) of SwA policy, guidance and methodologies that effectively implement SwA into programs and SE processes and disciplines to address each of the six defense acquisition program models and agile development. The contractor shall also review, and as directed by DASD(SE), support the update of processes for the development of SwA acquisition implementation guidance which aligns with the acquisition lifecycle and addresses SwA methodologies appropriate for each of the system domain areas. SwA guidance shall also supplement and compliment the Program Protection Plan Outline and Guidance (PPP O&G) and Defense Acquisition Guidebook (DAG) activities, including updates to maintain alignment with evolving acquisition needs as directed by DASD(SE). Guidance for the PPP O&G is anticipated to be reviewed annually. The contractor shall, as directed by DASD(SE):

(1) Develop and provide SwA-related assessments and recommendations

(2) Interface with other DoD organizations and agencies, other Government departments and agencies, Federally Funded Research and Development Centers (FFRDCs), industry, academia, and coordination and standards bodies

(3) Provide assistance to the DASD(SE) staff in preparing responses, briefs and reports

(4) Support additional actions to implement the Department’s SwA strategy that include review and development of acquisition documentation, e.g., updates to the DoD 5000 series and associated Instructions/Guidebooks, and efforts to further the community of SwA SME support and coordination that involves the National Security Agency (NSA), Services, agencies, other Government departments and agencies and other coordination and standards bodies.

The contractor shall support the preparation of SwA-related findings, assessments, planning, recommendations and reports to DoD senior leaders with a focus on SE and technical and strategic direction.

The contractor shall support MPS in their MDAP/MAIS program engagements and reviews with SMEs based on program mission, status, and context, to provide comments, recommendations, and information, e.g., SwA best-practices, to the programs. The contractor shall support the development of SME input to Director, MPS for various program reviews.

The contractor shall support and advance the operation of the DoD SwA Community of Practice which brings together organizations across the DoD and the Federal Government to further the state of practice of SwA and SSE. This shall include meeting coordination and support, participation using SMEs, action tracking and support, report development, support for working groups, including SwA metrics, coordination and sharing, workforce training, and SwA contract language, test and evaluation, SwA User Guidebook, and portal maintenance and content development.

Work under this section will require the lead contractor to hold a TS/SCI clearance.

1.2 Joint Federated Assurance Center (JFAC)

The contractor shall use SME to support JFAC operation, including the JFAC Steering Committee, which meets quarterly or as needed, the Action Officer (AO) Working Group (WG) which meets bi-weekly, the SwA WG which meets bi-weekly, and the HwA Technical WG which meets as needed, and shall coordinate with the JFAC Coordination Center (CC).

Activities include supporting the execution and update of the JFAC Concept of Operations (CONOPS), the DoD-wide assurance capability gap analysis and resource planning, the JFAC Integrated Management Schedule (IMS), portal and portal content support for NIPR, SIPR, and JWICS, Full Operational Capability (FOC) planning and implementation, and updates to the JFAC Strategic Plan, as directed by DASD(SE). The contractor shall provide SME support to the planning and oversight of SW and HW assurance tasks remediating capability gap finding.

Tasks include preparation of plans, briefs, findings, assessments, reviews, recommendations, minutes, actions and action tracking point papers, executive summaries, coordination, and reporting that may go to DoD senior leaders.

Work under this section will require the lead contractor to hold a TS/SCI clearance.

1.3 Acquisition Security Database

The contractor shall assist the DASD(SE) in the oversight and management of the ASDB, which supports the program protection process by providing the DoD CPI repository and cross- DoD Component access and searches of stored CPI in support of horizontal protection analysis of CPI in support of acquisition programs. In addition to CPI, ASDB supports the update and access to other key program information,, such as the program’s use of related critical technologies in the United States Munition List, Commerce Control List, and other technologies as identified by the PMOs.

The ASDB is currently being redeveloped and re-hosted at the Defense Technical Information System. This effort’s completion is scheduled to occur by the end of FY15. The contractor shall assist with the management of technical activities in support of the DTIC technical team’s development effort. This effort includes the requirements, design, testing of each Sprint and the Initial Operational Capability and FOC, as well as support of the related ASDB management reviews, e.g., In-Progress Reviews, and technical reviews, e.g., Sprint Reviews.

The contractor shall also assist with the on-going management and support of the ASDB, e.g., help desk activities and update of databases as required to maintain the Annual Defense Business System Management Committee Certification.

The contractor shall support leadership of the quarterly ASDB Configuration Control Board, oversight of the execution of the ASDB support agreement, as well as the monthly stakeholder meetings.

The contractor shall also support the update of related policy and guidance as needed governing the management and use of ASDB.

1.4 CPI Identification and Anti-Tamper

The contractor shall support the update of the DoD Instruction (DoDI) 5200.39 and the development and update of the DoD Manual supporting implementation of the on-going and any future updates to the DoDI 5200.39.

The contractor shall also support the on-going approval process for the DoD Directive (DoDD) for Anti-Tamper, any future updates to this DoDD, as well as the development and update of related policy and guidance, e.g., the Anti-Tamper Program Management Guidebook, Anti- Tamper Technical Implementation Guidebook, Anti-Tamper Security Classification Guidance, in coordination with the Anti-Tamper Executive Agent (ATEA), the DoD Component Offices of Primary Responsibility (OPR) for AT, the broader AT community, and related working groups and forums developing this policy and guidance.

The contractor shall support the review of, and provide recommended updates to, related Defense Exportability Features (DEF) policy and guidance developed by Director, International Cooperation (D, IC), OUSD(AT&L), to ensure its continued alignment to AT and broader program protection.

The contractor shall support DASD(SE) in the review of the planned implementation of AT within PPPs in coordination with the ATEA for AT and D, IC for DEF.

AT policy and guidance shall supplement and compliment the PPP O&G and DAG. Guidance is anticipated to be reviewed annually and assessed, as required, if updates are needed, e.g., based on PPP review feedback.

The contractor shall also support the review of the Anti-Tamper Roadmap, which is developed and maintained by the ATEA.

The contractor shall support the DASD(SE) as chair of the Anti-Tamper Integrated Product Team (IPT), and in other forums, such as the quarterly AT Summits and bi-annual National AT Reviews, as required, to facilitate the development and update of policy and guidance for AT, oversee the capabilities of the DoD Component OPRs for AT, advance the state of AT technology, and develop and oversee incident response procedures.

Most of the work is SECRET//NOFORN but TS or TS/SCI may be required.

1.5 Microelectronics

The contractor shall support DASD(SE) in the advancement of HwA, to include the continued development and update of the trusted microelectronics strategy for Application-Specific Integrated Circuits, Field Programmable Gate Arrays, and other microelectronics, and HwA policy, guidance, studies and other activities in support of DoDI 5200.44.

The contractor shall support DASD(SE) in the advancement of trusted microelectronics, to include policy, guidance, studies and other activities related to the Trusted Foundry, e.g., the ongoing Trusted State-of-the-art Microelectronics Study, and the Defense Microelectronics Activity (DMEA) program to accredit Trusted Suppliers.

The contractor shall support DASD(SE) in the review of the planned implementation of HwA within PPPs. The contractor shall develop and recommend to the DASD(SE) HwA policy, guidance and best practices that align its implementation across the acquisition lifecycle, e.g., legacy system sustainment, and that is appropriate for various system domain areas.

Methodologies shall extend beyond counterfeit approaches and address approaches to the detection and mitigation of malicious insertion. HwA, to include trusted microelectronics, policy and guidance shall supplement and compliment the PPP O&G and DAG. Guidance is anticipated to be reviewed annually and assessed as required if updates are needed, e.g., based on PPP review feedback.

The contractor shall support preparation of findings, assessments, recommendations and reports to DoD senior leaders with a focus on SE and technical and strategic direction. The contractor shall support review and comment on acquisition documentation and related policies and guidance and shall support MDAP/MAIS program engagements and reviews based on and related to this task area's activities, outputs (recommendations, practices) and subject matter.

The contractor shall provide monthly updates for this task to senior leaders, substantiated by study, analysis and reporting. The contractor shall provide SME support in this area to Director, MPS as needed.

Work in this area is TS/SCI and may be FRD (Formerly Restricted Data)

1.6 System Assurance and Program Protection Support

The contractor shall support Dir, MPS by advise MDAP and MAIS Program Management Offices (PMOs) on the application of system assurance and program protection principles and practices. The contractor shall assist the PMO in identifying system assurance and program protection risks and mitigating strategies, to include review and comment on a broad range of requirements, acquisition and contract documentation. Where applicable, the horizontal protection of programs should be considered and addressed, e.g., cross-program application of best practices and reuse where practical. On a selected basis, the contractor shall support the accomplishment of vulnerability assessments of MDAPs and MAISs to include the review of systems design factors, the Integrated Development Environment and technical practices, threat and supply chain risk management, and program protection planning and practices. The contractor shall provide system assurance and program protection training and oversight to ensure use of appropriate system assurance processes, methods and tools for selected MDAPs and MAISs.

DASD(SE) works with an average of 60 programs per year on system assurance and program protection.

1.7 Security Engineering Program Support.

The contractor shall assist the ODASD(SE)/MPS staff to help transfer knowledge of best practice countermeasures and program protection planning to acquisition program engineering and security staffs. These engagements include vulnerability analyses to determine supply chain risk, criticality analyses to determine CPI, technology or components that require protection and pathfinders with programs to pilot best practices and methodologies.

The contractor shall provide SE and security risk analysis support to these engagements, as well as assisting ODASD(SE)/MPS in documenting knowledge gained from them. The contractor shall help maintain this knowledge in a form that is easily sharable with other programs and the SE community. The contractor shall support development of guidebooks and education and training for SSE.

2 Engineering Tools and Environments

2.1 Engineered Resilient Systems

The contractor shall perform all necessary activities in support of the Program Element (PE) established in FY2016 as they relate to the technical advancement of the Engineered Resilient Systems (ERS).

Activities within this task include but are not limited to: liaison with other DASD(SE) elements, including the Systems Engineering Research Center and the Defense Modeling and Simulation Office, to leverage activities in other areas, and assessment of their activities to ensure that the elements are converging and leveraging where appropriate. Critical thinking shall also be required to identify necessary activities for Engineered Resilient systems which require input on, or advancement by other DASD(SE) elements. The contractor shall also be required to advise the technical lead for ERS on activities related to transition of ERS capabilities.

The contractor shall assist in establishing the yearly work effort for ERS, and for monitoring and tracking the technical maturity of the activities. Liaison with, and travel to, the performers sites may be required. Analysis of the work plans prior to execution year may be required. The contractor may also be required to perform research in to big data analytic tools, visualization tools, and high performance computing techniques. Knowledge of modeling techniques and domain application areas will be needed.

The contractor will be required to provide input to, and draft reports, presentations, etc., in order to convey the progress of the ERS elements, as well as to project the upcoming year's activities.

The contractor shall also provide critical thinking and advice on the transitional elements of ERS. This function includes, but is not limited to development of transition plans, identification and facilitation of efforts which could be used as pilots to further SE development, as well as benefit advancing the effort, participation in ERS working groups, development or modification of policy, guidance, and education/training materials, and liaising with Services in their use of ERS tools and techniques. The contractor shall be able to assess both the technology and the processes developed by ERS, as both should be considered transitional elements. It will also require analysis of usability dimension when advising on whether the tool is ready to enter the mainstream of SE. Work will also be required to assess areas of further development in the ERS tool suite, where there is a lack of focus (e.g.

manufacturability). Business and financial management follow-up and tracking will be required, as will mapping of research initiatives into the ERS roadmap, and tracking of task completion. Business and financial management follow-up and tracking will be required, as will mapping of research initiatives into the ERS roadmap, and tracking of task completion.

2.2 Digital Engineering in Design and Engineering.

Tasks include, but are not limited to:

2.2.1 Establishing and advance a stakeholder community

This community is to lead, and cultivate efforts to define and develop artifacts and answer questions, to assist programs and components in transitioning to a model-centric approach to engineering and acquisition; additionally, collaboration with established groups such as INCOSE MBSE, and NDIA. This effort will entail a focus on model usage, and will develop and expand the idea of use of digital artifacts in general. An enabler of model-centric activities is the idea to use, and produce computationally relevant artifacts - models (organized data, algorithms, processes), production of digitized artifacts for current acquisition practice, such as, but not limited to, SEPs and TEMPs, as well as assisting in characterizing vendor tools to aid in program selection.

The contractor shall assist with whitepapers, briefings, and analysis of current program use of models, in development of the weapon systems, and transition of those lessons into usable practice across the range of acquisition activities, identifying key players and enablers which influenced successful execution of digital engineering design.

The contractor shall assist in the identification of instantiation points, where model-centric tools and techniques, as well as digital artifacts, can be introduced into the defense acquisition system; building of transition plans, and creation of education modules to assist in training users of model-centric tools, as well as decision makers.

The contractor shall establish a taxonomy and definitions to build the digital system model.

Work with an expanding community of practice to identify elements to include in the taxonomy, and viewpoints into the taxonomy itself for use across the spectrum of activities in the defense acquisition system. This effort will also include the creation of the digital thread taxonomy, which acts on the data contained in the DSM, to produce the needed digital artifact or analysis. This will include, but not be limited to:- identify a method for characterizing and organizing elements of the digital thread (tools and methods to operate on digital system model) to support analysis and development of weapon systems, at any point in the system lifecycle.

2.2.2 Digital Artifact Management

A related activity which will gain significance as the digital artifacts emerge in understanding and use, is the overlap with the contracting and legal workforce as it related to data and intellectual property issues. The contractor shall engage with this community in order to gain understanding and benefit of their activities for the engineering community. This includes, but is not limited to attendance of meetings, production of minutes, and completion of actions and white papers to aid in understanding the significance of the problem and solutions paces.

2.2.3 Transition current education, training, guidance, and where practical Support DASD(SE) in the transition of current education, training, guidance and where practical, policy from document centric to model centric activities

2.2.4 Assist in cross-cutting efforts in Engineering Tools and Environments Assist in cross-cutting efforts in Engineering Tools and Environments; function as main action officer for tasks, collaboration, etc

2.3 Modular Open System Architecture (MOSA).

The scope of this task is to refresh the body of policy, guidance, research, and practice on the planning and use of MOSA in system acquisition. MOSA is an element of the USD AT&L Efficiency Policy (September 2009). The contractor shall provide an initial report to the DASD (SE) NLT 60 days after contract award that identifies, organizes, summarizes, and analyses the portfolio of MOSA policy and guidance documents in DOD and annually update this report. The contractor shall provide technical SME support to the DASD (SE) regarding MOSA to facilitate assessment of policy and programs and DASD (SE) participation with other DOD organizations and open architecture working groups. IAW BBP3.0 direction, support generation and conveyance of SE input to the initiative on Modular Open Systems Architecture. This includes, but is not limited to participation in meetings and workshops, Generation of input material, review of, and generation of modifications to products from the initiative (based on the initiative scope) and participation in related areas where MOSA principles can be applied, or are affected (e.g. program protection, cyber vulnerability, SW generation). Liaising with the BBP 3.0 initiative on Technical insertion and technical refresh.

Emphasis in these areas will be on technical enablers to modularity, to aid the program manager and systems engineering staff.

The task shall also include identification of effect of MOSA on the DSM, DT, and other digitial engineering initiatives, as those develop. This work includes, but is not limited to effects on taxonomy structure, insertion points, guidance and best practices, and development of briefings and white papers.

In addition to the BBP related work, update the SE guidance web page on OSA; manage the SE input to, and responses to tasking from the OSA DSC WG. In concert with the SE Workforce development lead, update and manage updates to the curriculum within the Engineering FIPT scope regarding modularity and open systems. Work collaboratively with FFRDC and UARC personnel to scope work, research, and results to fit within the bounds of modularity, and open systems impacts to systems engineering.

The lead support SME or Engineering will require a TS/SCI clearance

3 Systems Engineering (SE) Policy and Guidance (P&G)

3.1 SE Policy and Documentation

The contractor shall propose recommended SE policy development or changes for DASD(SE) consideration and, when accepted, develop, prepare and coordinate draft policy for DASD(SE) approval. The contractor shall support the DASD(SE) in reviewing and assessing the DODI

5000.02 and DODI 5134.16 for currency and completeness, and, as necessary, preparing periodic updates. The contractor will ensure comments submitted against drafted policy are adequately adjudicated and will coordinate with DoD Components, including the Director, Defense Procurement and Acquisition Policy (DPAP), and participate on DPAP’s Defense Acquisition Policy Working Group (DAPWG).

The contractor shall review proposed DoD issuances and other documents to ensure SE equities are appropriately addressed and ensure SE is consistently integrated into non-DASD(SE) issuances.

The contractor shall assess these proposed issuances and documents, assigned to DASD(SE) for review and coordination, and prepare draft comments in coordination matrix format for

Government approval and submission. The contractor will then track and verify submitted comments are adequately adjudicated.

3.2 SE Guidance

The contractor shall propose, for DASD(SE) consideration, recommendations for new and revised guidance necessary to ensure compliance with acquisition and SE policy. When recommendations are accepted by the DASD(SE), the contractor shall develop, prepare and coordinate draft guidance for DASD(SE) approval. The contractor shall support the DASD(SE) by preparing periodic updates to the Defense Acquisition Guidebook, Chapter 4 on Systems Engineering and contribute to other chapters, as necessary, to ensure appropriate SE guidance is addressed across the lifecycle and integrated throughout the DAG.

The contractor will ensure comments submitted against drafted guidance are adequately adjudicated and will coordinate with appropriate DoD Components.

3.3 Acquisition Documentation Reviews for SE P&G Implementation The contractor shall review program documentation (i.e. Systems Engineering Plans, Acquisition Strategies, Acquisition Program Baselines, Requests for Proposal, Acquisition Decision Memorandum, etc) to ensure they are consistent with SE policy and they consider SE guidance. The contractor shall assess these program documents, assigned for review and coordination, and prepare draft comments in coordination matrix format for Government approval and submission.

The contractor will then track and verify submitted comments are adequately adjudicated. The contractor will assess areas where program documentation is routinely inconsistent with SE policy and make recommended policy and/or guidance changes to resolve these issues.

3.4 DAU Course and Community of Practice Content Reviews for Consistency with SE P&G

The contractor shall review the Defense Acquisition University’s (DAU’s) courseware for the Engineering (ENG) and Production, Quality, and Manufacturing (PQM) career fields, and ensure they are consistent with SE P&G. The contractor shall assess these courses and, when necessary, prepare draft comments in coordination matrix format for Government approval and submission. The contractor will coordinate with DAU and verify submitted comments are adequately adjudicated.

The contractor shall review and monitor the content of the Acquisition Community Connection’s (ACC’s) Systems Engineering Community of Practice (SECoP) for consistency with acquisition and SE P&G. The contractor shall assess SECoP content and, when necessary, prepare draft comments in coordination matrix format for Government approval and submission. The contractor shall coordinate with the SECoP editor and verify submitted comments are adequately adjudicated.

3.5 SE P&G Reporting and Outreach

The contractor shall provide recommended inputs for DASD(SE) weekly staff meetings and weekly activity reports. The contractor shall provide technical and management inputs to data calls, briefings, articles, and reports as required. The contractor shall develop, prepare, and coordinate meeting minutes for high level meetings such as the DAG Chapter 4 Working Group.

4 Specialty Engineering The contractor shall provide specialty engineering technical and analytical services in support of DASDSE policy, guidance and acquisition responsibilities as described below.

(Estimate approximately 45 CONUS trips with 10% being local for specialty engineering.)

4.1 Manufacturing and Quality Engineering

4.1.1 Manufacturing and Quality Engineering Policy, Guidance, and Outreach The contractor shall review DoD manufacturing and quality policies, practices and procedures in coordination with representatives from the Services, Defense Logistics Agency (DLA), Missile Defense Agency (MDA), and Defense Contract Management Agency (DCMA), MIBP on proposed manufacturing and quality policy changes.

The contractor shall support DASD(SE) in the interaction and outreach with industry association quality and manufacturing organizations associated with the MRL working groups to continuously refresh the manufacturing and quality body of knowledge. This includes NDIA division meetings, NNMI, AIA, SAE, and professional quality societies such as the American Society for Quality (ASQ). The contractor shall consult and interact with industry association quality organizations associated with the NDIA, NNMI, AIA, and professional manufacturing and quality societies such as the American Society for Quality (ASQ).

The contractor shall continuously refine the Manufacturing and Quality Engineering body of knowledge (BoK) by participating in the quarterly and annual MRL BoK refresh, MRL criteria matrix review, guidebook updates, user roll-out activities of AS-6500 and other professional associations.

The Contractor shall propose to the DASD(SE) updates to the Manufacturing and Quality Engineering sections of the DAG to reflect life cycle manufacturing and quality activities. The Contractor’s proposed updates to the DAG must be properly integrated and synchronized with the DoD’s Systems Engineering processes and Technical Reviews (i.e. ASR, SRR, SFR, PDR, CDR, etc).

The Contractor shall support DASD(SE) with planning and administration of the Manufacturing and Quality Component Senior lead meetings. These meetings will occur a minimum of six times a year. The contractor shall provide administrative support for the manufacturing and quality meetings to include preparing read-ahead packages, distributing invitations, taking minutes, recording action items, as well as developing agendas and briefings for the advisory group meetings.

The contractor shall provide recommended Manufacturing and Quality inputs for DASD(SE) weekly staff meetings and weekly activity reports. The contractor shall provide technical and management Manufacturing and Quality inputs to data calls, briefings, articles, and reports as required.

4.1.2 Acquisition Review and Analysis.

The Contractor shall participate in MPS Program Support Team Lead domain (Fixed Wing, Space & Missile Defense, Ships/Subs, Land Combat/Communications, Rotary Wing and C3ISR/Business systems) program engagements to assess the engineering and management activities associated with the planning, design, and implementation of manufacturing engineering, quality processes and capacities to execute the program’s acquisition strategy and production schedule at each appropriate phase of the acquisition cycle.

The scope of the Manufacturing and Quality Engineering acquisition review and analysis task includes reviews to support the MPS MDAP/MAIS Program Support Team Lead domain (Fixed Wing, Space & Missile Defense, Ships/Subs, Land Combat/Communications, Rotary Wing and C3ISR/Business systems) program engagement, Nunn-McCurdy and other acquisition certification reviews, Component and program office requested reviews, system engineering and manufacturing readiness reviews, and other reviews conducted consistent with policy and program directions. Additionally a level of interaction with programs reviewed over the past two years will be required. Based on previous history, it is likely that the need for quick reaction manufacturing reviews will be required to meet unplanned requirements.

Accomplishment of this task requires the contractor attend on-site contractor and program office reviews and meetings as necessary and work in an OSD team environment. The activity requires the contactor staff to synthesize significant programmatic and technical data and information to develop a complete understanding of user and contract requirements as well as the programmatic (cost, schedule, EVM) and technical status of the program to include cost, schedule, technical performance, manufacturing and quality engineering methods. This includes a range of manufacturing and quality technical assessment activities encompassing all aspects of manufacturing and quality engineering development planning and execution to include methods and tools, risk management, IMP/IMS, integration with the requirements of the systems engineering process, etc. The contractor shall adhere to ODASD (SE) criteria and guidance such as the DAPS and other methodologies or as otherwise directed in accomplishing these reviews. The contractor shall participate in MPS program engagements, and other reviews in the development and adjudication of review findings.

The contractor shall present all proposed review findings before submission for adjudication.

The contractor shall perform on-going surveillance of reviewed programs to refresh review findings and advise ODASD (SE) of significant changes in the program baseline or performance. This effort will be planned and managed to be consistent with the reporting and monitoring needs of the PSA process. It is anticipated that a minimum of 25 engagements during the 12 month period.

Manufacturing and quality engineering reviews include, but are not limited to the following program acquisition documents: Acquisition strategies, systems engineering plans, test and evaluation master plans, Defense Acquisition Executive System Manufacturing Reviews, Preliminary and Critical Design Review Reports. It is anticipated that a minimum of 90 acquisition documents will be reviewed during the 12 month period. The Contractor shall:

(1) Review assigned documents to determine adherence to applicable R&M policy, guidance, and best practice;

(2) Document, justify, and provide proposed comments using prescribed formats and tools for approval by DASD (SE)

(3) Interface with program offices as well as OSD/Component staff during this process as appropriate; and

(4) Participate in DASD (SE) and other OSD led adjudication reviews of these documents.

4.2 Diminishing Manufacturing Sources and Material Shortages (DMSMS) The contractor shall coordinate with L&MR, the Department lead for DMSMS, to review the engineering design considerations for the DMSMS portions of LCSPs. The contractor shall also review acquisition strategies and Systems Engineering Plans to assess program strategies to address obsolescence, DoD industrial base issues, parts obsolescence management, technology needs, manufacturing sources and material shortages. The Contractor shall propose to the DASD(SE) updates to the DMSMS sections of the DAG to reflect life cycle DMSMS activities.

4.3 Value Engineering

The contractor shall support ODASD(SE) in the implementing DoDI 4245.14 Value Engineering requirements for the DoD. The Contractor shall review OMB Circular A-131 updates and assess impacts to the Department’s policy and guidance. The Contractor shall propose written updates to the DAG and the SD-24 Guidebook.

The contractor shall support DASDSE in the call for DoD’s VE performance metrics, tracking their collection, analysis, evaluation and subsequent submission to OMB. The Contractor shall support the call for DoD’s VE plans, tracking their collection, analysis and evaluation. The contractor shall support the DASDSE in the review of the Component’s VE plans for compliance with the issued criteria and provide an assessment of DoD’s overall planning effectiveness. The contractor shall provide annual assessments of the DoD’s VE program using the metrics and plans submitted by the Components. The Contractor shall support the DASDSE in the request for VE award nominations, tracking their collection, and supporting MAG deliberations with their evaluation and preparation of announcement memo. The Contractor shall support the planning for the annual VE Awards Ceremony hosted by USD(ATL). This entails supporting DASDSE with the following: Reserving the Pentagon Auditorium, Request for Master of Ceremonies, Request for Speaker, preparation of press release announcing the winners, keynote preparation, preparation of certificates, invitations, award attendance management, printing of programs, rehearsals and seating arrangements the day of the ceremony.

The contractor shall support ODASD(SE) in the review and update of VE training for CLE

001. The Contractor shall support ODASD(SE) in fostering recognition for DoD VE achievement awards by reviewing the annual VE Achievement Awards nominations and support the hosting of the annual VE Achievement Award Ceremony.

The Contractor shall support DASD(SE) with planning and administration of the VE Management Advisory Group (MAG). The VE MAG will meet a minimum of six times a year.

The contractor shall provide administrative support for the VE MAG to include preparing read-ahead packages, distributing invitations, taking minutes, recording action items, as well as developing agendas and briefings for the advisory group meetings.

The contractor shall provide recommended VE inputs for DASD(SE) weekly staff meetings and weekly activity reports. The contractor shall provide technical and management inputs to data calls, briefings, articles, and reports as required. The contractor shall develop, prepare, and coordinate VE MAG meeting minutes and maintain the VE Milsuite site.

4.4 Human Systems Integration (HSI)

The contractor shall review DoD HSI policies and engineering management practices and procedures. The contractor shall also perform reviews of System’s Engineering plans and relevant HSI program plans. The scope of these reviews will be limited to at least six plans each. The Contractor will review assigned documents to determine adherence to applicable HSI policy, guidance, and best practice. The Contractor shall propose, for DASD(SE) consideration, recommendations for new or revised Human System Integration guidance. When recommendations are accepted by the DASD(SE), the Contractor shall develop, prepare and coordinate draft guidance for DASD(SE) approval.

The contractor shall support the Joint HSI Steering Committee co-chaired by the DASD(SE)/EE, the Joint HSI Working and HSI Standards development working groups. The Steering Committee and Working Group meets semiannually at the initiation of the co-chairmen with the HSI and standards working groups meeting at least quarterly. The contractor shall provide administrative support for the committee and working groups to include preparing read-ahead packages, taking minutes, recording and following up on action items.

The contractor shall review and monitor the content of the Acquisition Community Connection’s (ACC’s) Human Systems Integration (HSICoP) for consistency with acquisition and SE P&G. The contractor shall assess HIS CoP content and, when necessary, prepare draft comments in coordination matrix format for Government approval and submission. The contractor will coordinate with the HSI CoP editor and verify submitted comments are adequately adjudicated.

The contractor shall provide recommended HSI inputs for DASD(SE) weekly staff meetings and weekly activity reports. The contractor shall provide technical and management HSI inputs to data calls, briefings, articles, and reports as required.

4.5 System Safety Engineering .

The contractor shall coordinate with the DoD safety community on guidance and tools related to Systems Safety considerations in design. The contractor shall survey Services/industry via NDIA to identify gaps in MIL-STD-882E content for hardware, software and review of safety Data Item Descriptions for standard task options. The contractor shall perform a System Safety policy/guidance gap analysis and propose to DASD(SE) the process to close the gaps (e.g.

Department policy issuances, DAG Chapter 4, SEP Outline, MIL-STD-882E, DAU system safety training). The Contractor shall continuously refresh the System Safety body of knowledge and propose to the DASD(SE) updates to the System Safety section of the DAG to reflect updates to the system safety body of knowledge.

The contractor shall review DoD system safety policies and engineering management practices and procedures. The contractor shall also perform reviews of System’s Engineering plans and relevant safety program documents. The Contractor will review assigned documents to determine adherence to applicable safety policy, guidance and best practice. The Contractor shall propose, for DASD(SE) consideration, recommendations for new or revised System Safety policy or guidance. When recommendations are accepted by the DASD(SE), the Contractor shall develop, prepare and coordinate draft guidance or policy for DASD(SE) approval. These reviews will be limited to 6 acquisition documents and 3 engagements to provide data on the state of practice for system safety engineering. The reviews and engagements will include acquisition strategies, systems engineering plans and limited program engagements such as PDR, CDR, PSA and component and program office focused safety requested reviews. The contractor shall provide written reports, records, briefing presentations, action items, and minutes to support ODASD(SE) staff.

The contractor shall provide recommended System Safety inputs for DASD(SE) weekly staff meetings and weekly activity reports. The contractor shall provide technical and management System Safety inputs to data calls, briefings, articles, and reports as required.

May require support at the TS level.

4.6 Reliability and Maintainability (R&M) Engineering

4.6.1 R&M Engineering, Policy, Guidance and Outreach

The contractor shall continually review and evaluate legislation, DOD acquisition policy, R&M Body of Knowledge (to include but not limited to Government and non-Government Standards & Handbooks, Parts Requirement & Application Guide, standard document 18 (SD-18), R&M design & test documents, reliability growth modeling techniques and plans, physics based reliability estimation techniques, RAM-C reports, service policies, R&M standard work packages from Industry/Government, publications, etc.) and R&M technology advances to assess impacts to DOD R&M policy, guidance and practice. The Contractor shall support the promulgation of R&M guidance and lessons learned via the DASD(SE) SE website and the DAU R&M CoP.

The Contractor shall propose written updates to the DAG aligned by phase of the DoD acquisition life cycle The Contractor’s proposed updates to the DAG must be properly integrated and synchronized with the technical baseline, DoD Systems Engineering Technical Review process and other key functional areas (T&E and product life cycle support).

The Contractor shall provide ODASD(SE) support in monitoring DAU's progress in the development of R&M training courses (CLE-301R&M, RAM-C Rationale course, advance topics in R&M engineering and the R&M engineering modules 12 & 13 of ENG-301).

The contractor shall review and monitor the content of the Acquisition Community Connection’s (ACC’s) R&M (R&M CoP) for consistency with acquisition and SE P&G and R&M engineering best practices. The contractor shall assess R&M CoP content and, when necessary, prepare draft comments in coordination matrix format for Government approval and submission. The contractor will coordinate with the R&M CoP editor and verify submitted comments are adequately adjudicated.

The contractor shall maintain and, at the direction of the Government, support updates to the RAM-C manual with content driven by and directly attributable to policy. The contractor shall participate in all RAM-C reviews and periodically interface with PMOs, Service representatives, and other members of DASD(SE) government and contractor staff to identify and assess potential areas for improvement in the RAM-C Manual.

The Contractor shall support DASD(SE) with planning and administration of the quarterly R&M working groups with the Services, Agencies and other DoD components to include preparing read-ahead packages, distributing invitations, taking minutes, recording action items, as well as developing agendas and briefings for the working group meetings.

The contractor shall support DASD(SE) in the interaction and outreach with industry association R&M organizations and societies to continuously refresh the R&M body of knowledge. The contractor shall support DASD(SE) by preparing for and participating in RAMS, workshops, panels and symposia, and by preparing and submitting papers and presentations as directed by DASD(SE).

The contractor shall also provide policy analyses, written reports, records, agendas, briefing presentations, action items, minutes, to support DASD (SE) staff participation in conferences and other activities.

The Contractor shall also assess the current DAES Reliability Growth Reporting and develop recommendations on the implementation of RGC phase II requirements. The contractor shall develop analytical methods to assimilate individual DAES spreadsheets to establish trending data, techniques to establish triggers, growth effectiveness parameters, etc.

The contractor shall also support DASD(SE) in the development of the health assessment of R&M engineering for the Department. The Contractor will use standardized data from program acquisition review and analysis as elements for this assessment. The contractor shall develop an analytical model and assessment methodology for DASD(SE) approval.

The contractor shall provide recommended R&M inputs for DASD(SE) weekly staff meetings and weekly activity reports. The contractor shall provide technical and management R&M inputs to data calls, briefings, articles, and reports as required.

4.6.2 Acquisition, Review and Analysis.

The scope of the R&M Engineering acquisition review and analysis task includes reviews to support the MPS MDAP/MAIS Program Support Team Lead domain (Fixed Wing, Space & Missile Defense, Ships/Subs, Land Combat/Communications, Rotary Wing and C3ISR/Business systems) program engagement, Nunn-McCurdy and other acquisition certification reviews, Component and program office requested reviews, system engineering and R&M engineering technical reviews, and other reviews conducted consistent with policy and program directions. It is likely that the need for quick reaction R&M reviews will be required to meet unplanned requirements. Accomplishment of this task requires the contractor attend on-site contractor and program office reviews and meetings as necessary and work in an OSD team environment. The activity requires the contactor staff to synthesize significant programmatic and technical data and information to develop a complete understanding of user and contract requirements as well as the programmatic (cost, schedule, EVM) and technical status of the program to include cost, schedule, technical performance, R&M engineering methods.