FY22CC IDIQ SOW - RFP Final -29 June 2020.docx

DOCX document 1 MB Posted Jun 29, 2020

Attached to: SAILOR 2025 (S2025) READY RELEVANT LEARNING (RRL) FISCAL YEAR 2022 CONTENT CONVERSION
Solicitation number: S2025-FY22-CC-1
Issued by: Department of the Navy Naval Air Systems Command

About this file

Written by GovTribe AI · Dec 31, 2023

This sources sought notice is seeking capabilities statements from potential offerors for the Sailor 2025 Ready Relevant Learning Fiscal Year 2022 Content Conversion effort. The Naval Air Warfare Center Training Systems Division will award an indefinite delivery/indefinite quantity contract for courseware content conversion of three Navy ratings comprising 34 training paths, 1014 courses, and 16,000 courseware hours over approximately 36 months. Required capabilities include instructional systems design, systems engineering, developing training products for multiple delivery systems including mobile and complex media such as simulations. Responses are due by July 15, 2020 and award is projected for the second quarter of fiscal year 2022. The effort will require facility clearance up to the Secret level. Respondents are asked to describe experience with similar efforts, staffing capabilities, and compliance with standards such as SCORM and xAPI.

View the file

On GovTribe

Work with this file

Download the original file
Contacts named in this file
Similar government files
Ask GovTribe AI about this file

Try for free Login

Text version

The file's text, extracted by GovTribe without its formatting.

STATEMENT OF WORK (SOW)

FOR

SAILOR 20205 (S2025) Fiscal Year (FY) 22 READY RELEVANT LEARNING (RRL)

CONTENT CONVERSION (CC)

Prepared For:

Commander, United States Fleet Forces Command (CFFC) Norfolk, VA 23551-2487 Prepared By:

Naval Air Warfare Center Training Systems Division (NAWCTSD) 12211 Science Drive Orlando, FL 32826

DISTRIBUTION A. Approved for public release. Distribution is unlimited.

This page intentionally left blank.

REVIEWED BY:	DATE: _____________
	Dale Leavy
	S2025 Lead Systems Engineer
	NAVAIR – 5.7.7.

REVIEWED BY:		DATE: _____________
	Dr. Kenisha Thompson
	FY22 Content Conversion (CC) Lead Instructional System Designer
	NAVAIR –

APPROVED BY:		DATE: _______________
	LCDR Maura Betts
	Program Management Office
	NAVAIR –

Change Log

Date

Section Number

Section Title

Change

Table of CONTENTS

1. Scope	12
1.1 Rating Requirements	12
1.2 Course, Module and Lesson Structure	13
1.3 Content Delivery Modes and Media Types	13
1.4 Content Conversion Process Flows	15
1.4.1 Interactive Multimedia Instruction (IMI) Development Process	15
1.4.2 Performance Support (PS) and Structured On The Job Training (SOJT) Development Process	15
1.4.2.1 PS Hosted in Training Delivery Environments	16
1.4.2.2 PS Hosted in Operational Environments	16
1.4.3 Complex Media Development Process	16
1.4.4 Coordination with Third-Parties	17
1.5 List of SOW Appendices	17
1.6 Terms and Definitions	18
1.7 Government-Furnished Information (GFI)	18
1.8 Government-Furnished Software, Tools and Equipment	18
1.9 Government-Furnished Subject Matter Experts (SMEs)	19
2. Applicable Documents	19
2.1 Government Documents	19
2.2 Department of Defense (DOD) Documents	20
2.3 Department of the Navy (DON) Documents	21
2.4 Sailor 2025 Documents	22
2.5 Authoring Instructional Materials (AIM) Documents	22
2.6 Industry Standards	22
2.7 Other Documents	24
3. Requirements	26
3.1 General Requirements	26
3.1.1 Program Planning	27
3.1.1.1 Life-Cycle Model Management	27
3.1.1.2 Infrastructure Management	27
3.1.1.3 Program Assessment and Control	27
3.1.1.4 Program Decision Management	27
3.1.2 Contract Data Requirements Lists (CDRLs)	27
3.1.3 Online Management System (OMS)	28
3.1.4 Data Library	28
3.1.5 Configuration Management (CM)	28
3.1.6 File Sharing	29
3.1.7 Contractor SMEs	29
3.1.8 Data and Software Rights	29
3.1.9 Contractor Acquired Property	29
3.1.10 Copyrights	29
3.1.11 Risk Management	30
3.1.12 Quality Assurance and Management Plan (QAMP)	30
3.1.13 Communications Plan	30
3.2 Security	30
3.2.1 Classified Processing and Access to Classified Systems	31
3.2.2 Operations Security (OPSEC)	31
3.2.3 Unclassified Contractor-Owned Network Security – Safeguarding of Unclassified Controlled Technical Information	32
3.2.4 Cyber Incident and Compromise Reporting	32
3.2.5 Access to DOD Installations, Government Information and Information Technology (IT) Systems – Personnel Security Background Checks	33
3.2.6 Personnel Security – Background Checks	33
3.2.7 International Traffic and Arms Regulation	34
3.2.8 Personnel Security – Reporting of Adverse or Derogatory Information Related to Contractors	34
3.2.9 Government-Issued Personal Identification Credentials	34
3.2.10 Contractor “Out-Processing” Policy	35
3.2.11 Supply Chain Risk Management (SCRM) For National Security Systems	35
3.2.12 Protection of Critical Program Information (CPI)	35
3.2.13 Transmission of Controlled Unclassified Information (CUI) Via Email	35
3.2.14 Transmission of CUI Via Army Research Laboratory Safe Access File Exchange (ARL SAFE)	36
3.3 Cybersecurity	36
3.3.1 Cybersecurity for Training Content Products	36
3.3.2 Cybersecurity for Other Products	36
3.3.3 Cybersecurity Compliance	36
3.3.4 Cybersecurity Control Considerations	36
3.3.5 Cybersecurity Certification and Accreditation Support	36
3.3.6 Cybersecurity and Personnel Security Requirements for Accessing Government IT Systems - Credentialing Standards	36
3.3.7 Software Integrity Testing and Certification	37
3.3.8 Information Assurance Vulnerability Management Program (IAVMP)	37
3.3.9 Critical Program Information (CPI)	37
3.3.10 Cybersecurity Training & Certification	38
3.4 Management Requirements	38
3.4.1 Lead Integrator	38
3.4.2 Integrated Product Team (IPT)	39
3.4.3 Integrated Management Plan (IMP)	39
3.4.4 Work Planning and Scheduling	39
3.4.5 Development of the Contract Work Breakdown Structure (CWBS)	40
3.4.6 Subcontractor Management and Reporting	40
3.4.7 Schedule Risk Assessment (SRA)	40
3.4.8 Program Progress, Tracking, and Reporting	41
3.4.9 Conferences, Meetings, and Reviews	41
3.4.9.1 Post Award Conference (PAC)	42
3.4.9.2 In-Process Review (IPR) Meetings	43
3.4.9.3 Weekly or Biweekly IPT Meetings	43
3.4.9.4 Data-Gathering Trips	44
3.5 RRL Content Conversion Requirements	44
3.5.1 Instructional Media Design Package (IMDP) Development	45
3.5.1.1 Design for Training Product Delivery Environments	45
3.5.1.1.1 Design for Experience Application Program Interface (xAPI) Requirements	46
3.5.1.1.2 Design for Mobile Requirements	46
3.5.2 IMI, Mobile Ready, Mobile Optimized, and Responsive Design Mobile Website Media Types	46
3.5.2.1 Instructional Media Design Package (IMDP) Development (Updated Style Guide) and Model Products (i.e., Prototypes)	46
3.5.2.2 Instructional Media Package (IMP) (Script Storyboards)	47
3.5.2.3 Instructional Media Package (IMP) (On-screen Lessons [OSLs])	47
3.5.2.4 Courseware Reviews	47
3.5.2.5 Test Package Development (Assessments)	48
3.5.2.6 Course Testing Plan (Administration)	48
3.5.2.7 Training Conduct Support Document (TCSD)	48
3.5.2.8 Training Program Structure Documents (TPSD)	49
3.5.2.9 Training Systems Support Document (TSSD)	49
3.5.2.10 IMI Test & Evaluation (T&E) Program Components (IMI Product Acceptance) for Hosting in NeL Training Environment	49
3.5.2.10.1 NeL Contractor Testing (NeL DT-D1)	50
3.5.2.10.2 NeL Content Test Readiness Review (TRR) ETIM	50
3.5.2.10.3 NeL Government Testing (NeL DT-D2)	50
3.5.2.10.4 NeL DT-D2 Corrections	51
3.5.2.10.5 Government Content Acceptance Testing (GCAT)	51
3.5.2.10.6 Instructional Media Package (Media Source Files)	51
3.5.2.10.7 Instructional Media Package (CD-ROM/DVD)	51
3.5.2.10.8 T3 and Course Pilot Regression Testing	51
3.5.2.11 IMI T&E Program Components (IMI Product Acceptance Testing) for Hosting in Non-NeL Training Environments	52
3.5.2.11.1 NeL Contractor Testing (NeL DT-D1) per SOW 3.5.2.11.1	52
3.5.2.11.2 NeL Content TRR ETIM	52
3.5.2.11.3 NeL Government Testing (NeL DT-D2)	53
3.5.2.11.4 Non-NeL Environments Contractor Internal Testing (Non-NeL DT-D1)	53
3.5.2.11.5 Non-NeL Environments TRR ETIM	53
3.5.2.11.6 Non-NeL Environments Integrated Testing (Non-NeL IT-D1)	54
3.5.2.11.6.1 Non-NeL IT-D1 Entry Criteria	54
3.5.2.11.7 Instructional Media Package (Media Source Files)	54
3.5.2.11.8 Instructional Media Package (CD-ROM/DVD)	54
3.5.2.11.9 T3 and Course Pilot Preparation	55
3.5.2.11.10 T3 and Course Pilot Regression Testing	55
3.5.3 Performance Support (PS) and Structured On-The-job Training (SOJT) Media Types	55
3.5.3.1 PS and SOJT Model Products (i.e. Prototypes)	56
3.5.3.2 PS and SOJt Design	56
3.5.3.3 PS Instructional Media Package (IMP) (Script Storyboards)	57
3.5.3.4 PS Instructional Media Package (IMP) (On-screen Lessons (OSLs))	57
3.5.3.5 PS and SOJT Product Reviews	57
3.5.3.6 PS and SOJT Training Conduct Support Document	57
3.5.3.7 Acceptance Testing (for PS and SOJT products)	58
3.5.3.7.1 Government Content Acceptance Testing (GCAT) (for PS and SOJT products)	58
3.5.3.8 PS and SOJT Instructional Media Package (Media Source Files)	58
3.5.3.9 PS and SOJT Final Acceptance	58
3.5.3.10 Instructional Media Package-IMP (CD-ROM/DVD Inspect/Acceptance) (for PS and SOJT products)	58
3.5.4 Complex Media Types (e.g. PC Simulation, Augmented/Mixed/Virtual Reality, and Immersive Virtual Environment)	59
3.5.4.1 Systems Engineering Processes	59
3.5.4.1.1 System Requirements Definition	59
3.5.4.1.2 System Requirements Analysis	59
3.5.4.1.3 Traceability	60
3.5.4.1.4 System Architectural Design	60
3.5.4.1.5 System Implementation	60
3.5.4.1.6 System Integration	60
3.5.4.1.7 System Verification	61
3.5.4.1.8 System Transition	61
3.5.4.2 Engineering Technical Interface Meetings (ETIMs)	61
3.5.4.2.1 Systems Requirements Review-II/System Functional Review (SRR-II/SFR) ETIM	61
3.5.4.2.1.1 SRR-II/SFR ETIM Entry Criteria	62
3.5.4.2.1.2 SRR-II/SFR ETIM Exit Criteria	63
3.5.4.2.2 Preliminary Design Review (PDR) ETIM	63
3.5.4.2.2.1 PDR ETIM Entry Criteria	65
3.5.4.2.2.2 PDR ETIM Exit Criteria	66
3.5.4.2.3 Critical Design Review (CDR)	66
3.5.4.2.3.1 CDR ETIM Entry Criteria	67
3.5.4.2.3.2 CDR ETIM Exit Criteria	68
3.5.4.2.4 Test Readiness Review	69
3.5.4.3 Software Engineering Processes	69
3.5.4.3.1 Software Requirements Analysis	69
3.5.4.3.2 Software Architectural Design	69
3.5.4.3.3 Software Product Design	70
3.5.4.3.4 Software Implementation	70
3.5.4.3.4.1 Software Unit Construction and Testing	70
3.5.4.3.5 Software Integration	70
3.5.4.3.6 Cold Start Process	71
3.5.4.3.6.1 Software Product Execution	71
3.5.4.3.6.2 Media and Storage Devices	71
3.5.4.4 Test and Evaluation (T&E) Processes	72
3.5.4.4.1 Test Planning and Procedures	72
3.5.4.4.2 Responsibility for Tests	72
3.5.4.4.3 Test Authority	73
3.5.4.4.4 Test Resources and Facilities	73
3.5.4.4.5 Test Methods	73
3.5.4.4.6 Verification Criteria	73
3.5.4.4.7 Configuration	74
3.5.4.4.8 Verification Log	74
3.5.4.4.9 Changes During Testing	74
3.5.4.4.10 Software Changes During Government Testing	74
3.5.4.4.11 Changes After Testing	74
3.5.4.4.12 T&E Non-Conformance Reporting System	75
3.5.4.4.13 Deficiency Review Board (DRB)	75
3.5.4.4.14 Deficiency and Discrepancy Adjudication	76
3.5.4.5 Detailed Tasks for Complex Media (e.g. PC Simulation, Augmented/Mixed/Virtual Reality, and Immersive Virtual Environment Blended Approach) Courseware	76
3.5.4.5.1 Logic Tables	76
3.5.4.5.2 Test Package (Assessments)	76
3.5.4.5.3 Navy Preliminary Evaluation	76
3.5.4.5.4 Training Support Products	76
3.5.4.5.5 Complex Media (e.g. PC Simulation, AR/MR/VR, and IVE Blended Approach) T&E Program Components	77
3.5.4.5.5.1 Baseline Configuration Audit	77
3.5.4.5.5.2 Navy Preliminary Evaluation (per increment – lessons delivered in increments)	78
3.5.4.5.5.3 Pre-Modification Inspection (PMI)	79
3.5.4.5.5.4 Contractor Internal Testing (Simulation DT-D1)	79
3.5.4.5.5.5 Test Readiness Review	80
3.5.4.5.5.6 Integrated Testing (Simulation IT-D1)	82
3.5.4.5.5.7 Train the Trainer for Systems Engineering and Software Engineering Products	83
3.5.4.5.5.8 Course Pilot for Systems Engineering and Software Engineering Products	83
3.5.5 Human Factors Engineering (HFE)	83
3.5.6 Gap Implementation	83
3.5.7 Train the Trainer (T3)	83
3.5.7.1 T3 Entry Criteria	84
3.5.7.2 T3 Exit Criteria	84
3.5.8 Course Pilot	85
3.5.8.1 Course Pilot Entry Criteria	86
3.5.8.2 Course Pilot Exit Criteria	86
3.5.8.3 Regression Testing	87

LIST OF TABLES

Table 1. Rating and Classification Requirements	13
Table 2. Content delivery modes and Media Types	15
Table 3. Government Documents	20
Table 4. DOD Documents	21
Table 5. DON Documents	22
Table 6. Sailor 2025 Documents	22
Table 7. AIM Documents	23
Table 8. Industry Standards	23
Table 9. Other Documents	25

LIST OF FIGURES

Figure 1. IMI Levels 1 – 3 (and Mobile Ready, Mobile Optimized and Responsive Design Mobile Website) Content Conversion Process	16
Figure 2. Training Environment and Devices	17
Figure 3. Complex Media (e.g., PC Simulation, Augmented/Mixed/Virtual Reality and Immersive Virtual Environment) Content Conversion Process	18

This page intentionally left blank.

Statement of Work for the RRL FY22 Content Conversion 29 June 2020 ii

STATEMENT OF WORK (SOW)

FOR

SAILOR 2025 (S2025) FY22 READY RELEVANT LEARNING (RRL)

CONTENT CONVERSION (CC)

Scope This Statement of Work (SOW) defines the basic requirements to be performed under this Ready Relevant Learning Fiscal Year 22 Content Conversion (RRL FY22 CC) Indefinite Delivery/Indefinite Quantity (ID/IQ) contract. The detailed requirements will be defined in this ID/IQ SOW and each specific Delivery Order (DO). This ID/IQ documents the contractor tasks for the design, development, testing, and delivery of products in support of the RRL FY22 Content Conversion (CC) effort (see especially Appendices C, G, H, J, L, M, N, O). The contractor shall employ innovative instructional systems design (see Appendices H, L, and M), systems engineering, and training assessment approaches in conjunction with new and modernized technologies (see Appendix G) to support specified ratings accession training while simultaneously supporting the broader S2025 overarching goal of improving Sailors’ transfer of training to the operational work environment. The following represents examples of the broader Sailor 2025 (S2025) goals:

· Converting and/or improving designated courses so they are compatible with the waterfront or shipboard environment and contribute to the acquisition of actionable knowledge (i.e., practical knowledge that will be activated by and recognized as relevant to operational work contexts and events).

· Employing modernized media, instructional, and motivational strategies that are engaging (see Appendices G and H).

· Scheduling the converted and/or improved content closer in time to when the training will be put into practice in the work environment.

Rating Requirements The Naval Air Warfare Center Training Systems Division (NAWCTSD), as the RRL Training Systems Program Manager (TSPM), is responsible for A School and accession C School content conversion in support of RRL. The contractor shall perform tasks for the design, development, testing, and delivery of products for the ratings listed in Table 1 (highest classification is Unclassified FOUO unless otherwise noted). The contractor shall also prepare for and conduct Train-the-Trainer (T3) events (SOW 3.5.13) and Course Pilot events (SOW 3.5.14) as part of this effort.

Table 1. Rating and Classification Requirements

Rating

Highest Information Classification

Facilities Access Classification

When Classification Required

Fire Controlman (AEGIS) (FCA)

Unclassified

At Contract Award

Gunner’s Mate (GM)

Unclassified

At Contract Award

Fire Controlman (FC)

Unclassified

At Contract Award

Course, Module and Lesson Structure Using the Government provided Functional Requirements Documents (FRDs) and corresponding SOW Appendix A, Knowledge Capture Reports (KCRs), Military Characteristics Documents (MCDs), and supporting data workbooks as a basis, the contractor shall determine the course, module, and lesson structure for each course for each rating and shall design, develop, test, and deliver products meeting the specified requirements.

Content Delivery Modes and Media Types Training products are grouped under four content delivery modes: Instructor-Facilitated Interactive Training (IFIT), Self-Directed Interactive Training (SDIT), Structured On-The-Job Training (SOJT), and Performance Support (PS) (see Appendices C, G, and J). Table 2 shows the four overarching content delivery modes and a high-level view of associated media types to support the RRL effort, as identified in the FRD and MCD.

NOTE: there is no traditional Instructor-Led Training Computer-Assisted Instruction (ILT-CAI) media type or instructional strategy in the RRL Content Conversion effort; rather, the contractor shall design and develop interactive multimedia instruction (IMI) for use as IFIT that meets the requirements for being hosted in Navy eLearning (NeL). In context for Ready Relevant Learning, “IMI” is the preferred term and shall be interpreted generically as electronic media, replacing both Interactive Courseware (“ICW”) and “ILT-CAI” as terms regardless of whether the product is instructor-led or student-led, and including considerations for software management tools (e.g. Learning Management System, Learning Record Store).

Table 2. Content Delivery Modes and Media Types

Media

Delivery Method

IFIT

SDIT

SOJT

In Training Environment

In Operation Environment

Actual Equipment

Augmented Reality (AR)

Checklist

Decision Tables

Demonstration Animation

Demonstration Video

Electronic Performance Support System (EPSS)

Full System Trainer

Hybrid Mobile App

Immersive Virtual Environment (IVE)

Intelligent Tutoring System

Job Aid (JA)

Level 1 IMI

Level 2 IMI

Level 3 IMI

Mixed Reality (MR)

Mobile Friendly/Mobile Ready Website

Mobile Optimized Website

Mobile Web App

Native App

Paper/Paper-based

PC Simulation

Picture/Diagram

Responsive Design Website

Technical Training Equipment

Training Aid

Training Support Material

Virtual Reality (VR)

Content Conversion Process Flows Depending on the specific content delivery method and media type, the contractor shall follow slightly different development process flows with different CDRL deliverables, some following traditional ISD processes, some following systems engineering processes, and some blending the two.

Interactive Multimedia Instruction (IMI) Development Process The contractor shall follow a systematic approach for converting content into IMI, Mobile Ready, Mobile Optimized, and Responsive Design Mobile Website media types detailed within the SOW (see SOW Appendices C and G). Figure 1 identifies such a high-level process.

Figure 1. IMI Levels 1 – 3 (and Mobile Ready, Mobile Optimized and Responsive Design Mobile Website) Content Conversion Process Performance Support (PS) and Structured On The Job Training (SOJT) Development Process The contractor shall follow a systematic approach for converting content into Performance Support (PS) and Structured On-the-job Training (SOJT) media types detailed within the SOW (see SOW Appendices C and G). SOJT products shall be designed, developed and tested to be hosted in MyNavy Portal. The contractor shall design, develop, and test PS products to be used in both (1) a training setting and hosted in a training environment, such as NeL, and (2) an on-the-job operation setting and hosted in an operation environment, such as MyNavy Portal. Each host environment may have specific requirements that affect media development and test.

PS Hosted in Training Delivery Environments The contractor shall create and convert PS products to be used in a training setting (i.e. training aids, training support materials, supplemental training materials), following the same general process in Figure 1, to be hosted within specific training environments (e.g. NeL). Figure 2 identifies some of the training environments and devices capable of presenting training content within the current Naval training enterprise.

Figure 2. Training Environment and Devices PS Hosted in Operational Environments The contractor shall create and convert on-the-job PS products to be hosted within specific workplace (operation) environments and devices capable of presenting PS content within the current Naval training enterprise (e.g. MyNavy Portal).

Complex Media Development Process The contractor shall follow a systematic approach for converting content into complex media types (e.g. PC simulation, Augmented/Mixed/Virtual Reality, and Immersive Virtual Environment (IVE)) detailed within the SOW (see SOW Appendices C and G).

Figure 3 identifies such a high-level process that blends the traditional IMI development process with the Systems Engineering Process specifically for these types of media products.

NOTE: Any reference in an FRD (and SOW Appendix A), KCR, MCD, and supporting data workbook to “VSIM” or “ICW 4” or a variant of that term shall be interpreted as complex media (either, or a blend of, PC simulation, Augmented/ Mixed/Virtual Reality, or Immersive Virtual Environment (see SOW Appendix C)).

Figure 3. Complex Media (e.g., PC Simulation, Augmented/Mixed/Virtual Reality and Immersive Virtual Environment) Content Conversion Process Coordination with Third-Parties As required, the contractor shall coordinate with the Government and any third-party contractor responsible for developing complex media (e.g. PC simulation, Augmented/Mixed/Virtual Reality, or Immersive Virtual Environment system development (e.g. Government labs, Multipurpose Reconfigurable Training System (MRTS) 3D, PORTS, etc.)). In such cases contractor shall be required to design and develop training support materials that work together with the third-party developed system.

List of SOW Appendices To complete this effort, the contractor shall follow the guidance and requirements in the following Content Conversion appendices to this SOW:

· Appendix A (per rating): rating requirements covered by this SOW.

· Appendix B: acronyms used within this SOW.

· Appendix C: terms and definitions used within and outside this SOW regarding RRL Content Conversion.

· Appendix D: list of the Contract Data Requirements Lists (CDRLs) identified within this SOW.

· Appendix E: Risk Assessment Example Format.

· Appendix F: descriptions of the four RRL content delivery modes.

· Appendix G: operational definitions of engaging instructional strategies to be used in content development under this SOW.

· Appendix H: list of Bloom’s taxonomy action verbs.

· Appendix I: description of media type characteristics.

· Appendix J: mobile learning roadmap.

· Appendix K: Experience Application Program Interface (xAPI) requirements for this SOW.

· Appendix L: guidance on Naval Educational Training Center (NETC) RRL Single User Gaming and Simulation.

· Appendix M: guidance on NETC RRL Video Streaming.

Terms and Definitions Appendix C provides the terms definitions that are critical to this SOW. These terms and definitions supersede any similar terms and definitions that may be found in other sources. If the contractor and the Government have differences in opinion over interpreting a given term, Appendix C shall be the baseline from which a mutual agreement can be made.

Government-Furnished Information (GFI) The Government will provide the following, along with other relevant GFI:

1. Functional Requirements Document (FRD), corresponding SOW Appendix A, and corresponding supporting data workbook for each rating

1. Military Characteristics Document (MCD) for each rating

1. Knowledge Capture (KC) data for each rating

1. Access to existing data for each rating, if available, in Content Planning Module/Learning Object Module (CPM/LOM), such as existing Trainee Guides, Lesson Plans, Training Course Control Document (TCCD), Training Project Plan (TPP), Curriculum Outline of Instruction (COI)

1. Examples of existing courseware for each rating if available (The contractor shall prepare as though no existing courseware materials are available)

1. Applicable Style Guides Government-Furnished Software, Tools and Equipment The Government will not furnish software (Microsoft [MS] Office, Adobe Acrobat, etc.) or tools. The Government will not furnish equipment, hardware, software personnel, personnel, or materials for the Contractor’s use during this effort. The Government will provide access to a test bed at NAWCTSD for TRANET-U VDI content for the Contractor to test training materials. The Contractor shall provide the necessary hardware, software, tools, personnel, materials, and facilities, not otherwise furnished by the Government, to perform the tasks specified by this SOW.

Government-Furnished Subject Matter Experts (SMEs) Government SME access will be provided on a not-to-interfere basis. The Government is sensitive to overburdening SMEs. NAWCTSD will serve as the liaison between the fleet, Type Commander (TYCOM), Learning Centers (LCs) and/or Schoolhouses and the Contractor to coordinate access to SMEs in support of SOW activities and requirements. Location for SME support will be provided by the Government. The Government’s SMEs will be available face-to-face for key data collection activities (interviews, workshops, and reviews) and will be available for providing follow up information via phone, video-teleconference (VTC), or by Defense Collaboration Services (DCS), whenever practical.

Applicable Documents The following represent a list of applicable guidance documents for this effort. In the event of a conflict between the SOW and the references cited herein, the contents of this SOW take first precedence. Nothing in this SOW, however, supersedes applicable laws and regulations, unless a specific exemption has been obtained. These documents will be provided to the Contractor as GFI, if they are not readily available to the Contractor via the Internet. For all documents listed below, the latest versions apply.

Government Documents Table 3. Government Documents

Document Number

Document Title and/or Description

22 Code of Federal Regulations (CFR), Parts 120-130

Foreign Relations, Chapter 1 Department of State, Subchapter M, International Traffic in Arms Regulations (ITAR)

National Security Agency (NSA) Configuration Guide

NAVAIRINST 4355.19E

System Engineering Technical Review Process

National Institute of Standards and Technology (NIST) Special Publication (SP) 800-44

Guidelines on Securing Public Web Servers

United States (U.S.) Office of Personnel Management (OPM) Final Credentialing Standards for Issuing Personal Identity Verification

21 CFR 1040

Code of Federal Regulations (CFR), Title 21, Part 1040, Performance Standards for Light-Emitting Products

29 CFR 1910

Occupational Safety and Health Standards (OSHS)

Institute of Electrical and Electronics Engineers (IEEE) Std. 15288-2015

Systems and Software Engineering- Systems Life Cycle Processes

· Copies of the CFR sections can be obtained from https://www.pmddtc.state.gov/ddtc_public?id=ddtc_public_portal_homepage.

· Copies of U.S. Code can be obtained from https://ile-help.nko.navy.mil/ile/content/policy/section508.aspx.

· Copies of Defense Intelligence Security Agency (DISA) Configuration Guide can be obtained from http://disa.mil/.

· Copies of CFR documents can be obtained from http://www.gpo.gov/fdsys/browse/collectionCfr.action?collectionCode=CFR

· Copies of Federal Acquisition Regulation (FAR) clauses can be obtained from http://farsite.hill.af.mil/vffara.htm.

· Copies of NSA Configuration Guides can be obtained from http://www.nsa.gov/ia/mitigation_guidance/security_configuration_guides/index.shtml.

· Copies of National Institute of Standards and Technology (NIST) documents can be obtained from http://csrc.nist.gov/publications/PubsSPs.html. Copies of OSHA standards can be obtained from http://www.osha.gov.

· Copies of OPM document can be obtained from http://www.opm.gov/investigate/resources/index.aspx.

· Copies of IEEE Std 15288-2015 can be obtained from http://www.ieee.org/.

Department of Defense (DOD) Documents Table 4. DOD Documents

DOD Document Number

Document Title and/or Description

Department of Defense Instruction (DODI) 1322.26

Distributed Learning (DL) dated 05 October 2017

(https://adlnet.gov/dodi/dodi-xapi)

DODI 5000.02

Operation of the Defense Acquisition System

DODI 8500.01

Department of Defense Instruction 8500.01 Cyber Security dated 14 Mar 2014

DODI 8510.01

Risk Management Framework (RMF) for DoD Information Technology (IT), Change 1, dated 24 May 2016

DODI 5220.22-M

National Industrial Security Program Operating Manual, dated 28 Feb 2006

DOD 8570.01-M

Information Assurance (IA) Workforce Improvement Program, dated 19 Dec 2005 w/Change 4, 11/10/2015

DOD Implementation Plan for Advanced Distributed Learning (ADL) dated 19 May 2000

Military Handbook (MIL-HDBK)-881D

Work Breakdown Structures for Defense Materiel Items

MIL-HDBK-29612-1A

Department of Defense Handbook for Guidance for Acquisition of Training Data Products and Services (Part 1 of 5)

MIL-HDBK-29612-2A

Department of Defense Handbook for Instructional Systems Development/Systems Approach to Training and Education (Part 2 of 5)

MIL-HDBK-29612-3A

Development of Interactive Multimedia Instruction (Part 3 of 5)

MIL-HDBK-29612-4A

Department of Defense Handbook Glossary for Training (Part 4 of 5)

MIL-HDBK-29612-5A

Department of Defense Handbook for Advanced Distributed Learning (ADL) Products and Systems (Part 5 of 5)

MIL-PRF-29612B

Performance Specification Training Data Products

MIL-HDBK-217F, Notice 2

Reliability Prediction of Electronic Equipment

MIL-HDBK-472, Notice 1

Maintainability Prediction

· Copies of DOD Directives and Instructions can be obtained from the DOD Issuances Website (http://www.dtic.mil/whs/directives/).

· DOD Implementation Plan for ADL can be obtained from http://prhome.defense.gov/Portals/52/Documents/RFM/Readiness/docs/adl_implementplan.pdf.

· Copies of the DOD Specifications and Handbooks can be obtained online from the DOD Single Stock Point or from the Acquisition Streamlining and Standardization Information System (ASSIST) website (http://everyspec.com/DoD/DoD-HDBK/)

Department of the Navy (DON) Documents Table 5. DON Documents

DON Documents

Document Title and/or Description

DON Department of Defense Information Assurance Certification and Accreditation Process (DIACAP) Handbook Version 1, dated 15 July 2008

NETCINST 5510.1

Content Segmentation and Classification Guide

NETCNOTE 1500.6

Metadata Instruction

NMCI.10011.01.UA3.E

Core Build Contents Version 2.3, 02 Aug 07

Copies of the Navy Marine Corps Intranet (NMCI) Core Build Standard can be obtained from http://www.nmci-eds.com/downloads/core-build

OPNAVINST 1500.76C

Naval Training System Requirements, Acquisition, and Management

Secretary of the Navy Instruction (SECNAVINST) 5000.36A

Department of the Navy Information Technology Application and Data Management

SECNAVINST 5870.4A

Secretary of the Navy (SECNAV) M-5239.1

Department of the Navy Information Assurance Program, Information Assurance Manual, dated Nov 2005

SECNAV M-5510.36

Department of the Navy, Information Security Program, dated Jun 2006

· Copies of the CON DIACAP Handbook can be obtained from https://www.doncio.navy.mil/tagResults.aspx?ID=96

· Copies of the DON documents can be obtained online from the Navy’s Integrate Learning Environment website: https://www.secnav.navy.mil/doni/Directives/Forms/AllItems.aspx

Sailor 2025 Documents Table 6. Sailor 2025 Documents

Document Number

Document Title and/or Description

Ready Relevant Learning (RRL) Analysis Standard Operating Procedure (SOP) for Sailor 2025 (includes process flows)

Authoring Instructional Materials (AIM) Documents Table 7. AIM Documents

Document Number

Document Title and/or Description

AIM Content Planning Module (CPM) User’s Manual

AIM Learning Object Module (LOM) User’s Manual

· Copies of the AIM documentation can be obtained from https://www.public.navy.mil/netc/ntt/pdfs/End_to_End_Process_SOP_(7-11-14)_Final.pdf

Industry Standards Table 8. Industry Standards

Document Owner

Document Title and/or Description

ADL Co-Laboratories

Shareable Content Object Reference Model (SCORM) 2004—SCORM is a collection of standards and specifications adapted from multiple sources to provide a comprehensive suite of e-learning capabilities that enable interoperability, accessibility and reusability of Web-based learning content. SCORM documents and important information about SCORM can be obtained from: http://www.adlnet.gov/policy.

ADL Co-Laboratories

SCORM 2004 Conformance Testing Tool—This is a self-testing tool downloaded from http://www.adlnet.org to verify SCORM compliant courseware.

ADL Co-Laboratories

The Advanced Distributed Learning Registry (ADL-R): Best Practices for Updating Registered Content https://www.atsc.army.mil/tadlp/implementation/scorm/conformance/tools_scorm.asp

Experience API SCORM Profile

Guidelines for representing SCORM data and events as xAPI Statements. Provides a representation of the SCORM® data model as well as limited SCORM®-specific features, but uses xAPI for run time communications and tracking. The SCORM® profile was created as a compatibility approach to xAPI. It can be used to:

· create content that can track to both a Learning Management System (LMS) and learning record store (LRS)

· convert existing SCORM® data to xAPI Statements that can be stored in an LRS

· track experiences from a learning record provider in a manner consistent with how they would've been tracked in SCORM® (http://adlnet.github.io/xAPI-SCORM-Profile/)

xAPI LRS Conformance Requirements

The Experience API (xAPI)Conformance Requirements for Learning Record Stores

(https://adl.gitbooks.io/xapi-lrs-conformance-requirements/content/)

cmi5 (Case Mix Index) Profile Specification

A profile specification for xAPI that describes packaging, launch, and important data capture concepts for traditional LMSs that include an LRS.

(https://github.com/AICC/CMI-5_Spec_Current) Aviation Industry CBT Committee (AICC)

ANSI/ASQ Q9000-2000

Quality Management Systems - Fundamentals and Vocabulary

ANSI/ASQ Q9001-2000

Quality Management Systems - Requirements

ANSI/ASQ Q9004-2000

Quality Management Systems - Guidelines for Performance Improvements

ANSI Z535.1-2006 (R 2011)

Safety Colors

ANSI Z535.2-2011

Environmental and Facility Safety Signs

ANSI Z535.3-2011

Criteria for Safety Symbols

ANSI Z535.4-2011

Product Safety Signs and Labels

ANSI Z535.5-2011

Safety Tags and Barricade Tapes (for Temporary Hazards)

IEEE Std. 12207-2008, 2nd Edition

Systems and Software Engineering – Software Life Cycle Processes

Integrated Master Schedule (IMS) Global Learning Consortium

Question & Test Interoperability (QTI) Specification

Joint ADL Co-Lab

Best Practices Guide for Design and Development of SCORM Assessments (https://adlnet.gov/research/scorm/scorm-2004-4th-edition/scorm-2004-4th-edition-conformance-test-suite/)

· Copies of the industry standard documents can be found by visiting the web addresses indicated.

· Copies of the following Industry Standards can be obtained from the American National Standards Institute (ANSI)/American Society for Quality Control (ASQC) (http://www.ansi.org).

· (Copies of the ANSI/Institute of Electrical and Electronics Engineers (IEEE) documents are available from http://standards.ieee.org/ or IEEE Service Center, 445 Hoes Lane, Piscataway, NJ 08854-1331.)

Other Documents Table 9. Other Documents

Document Number

Document Title and/or Description

CJCSI 6510.01F

IA and Computer Network Defense (CND)

Executive Order 13465

Economy and Efficiency in Government Procurement Through Compliance with Certain Immigration and Nationality Act Provisions and Use of an Electronic Employment Eligibility Verification System, dated 6 June 2008 (Amendment to Executive Order 12989 of 13 February 1996)

NMCI.10011.01.UF0.E

Core Build Contents Version 7, 22 May 2012

NAVAIRINST 5000.21B

Naval Systems Command (SYSCOM) Risk Management Policy dated 24 Jan 2008

Unnumbered Document

Joint ADL Co-Lab, ADL Acquisition Guidance, dated 9 Aug 2006

NAVPERS 18068F

Volume I Navy Enlisted Occupational Standards

Unnumbered Document

NeL Content Hosting Frequently Asked Questions (FAQ)

Unnumbered Document

Navy Education and Training Center (NETC) Course Hosting Process

Unnumbered Document

Content Hosting and Report Management Service (CHaRMS) Developer User Guide V2

Unnumbered Document

Virtual Desktop Infrastructure (VDI) Specifications Brief

Unnumbered Document

VDI Risk Management Framework package

Unnumbered Document

Mobile Learning & Technology Roadmap

· Copies of the CJCSI document can be obtained from http://www.dtic.mil/dtic/

· Copies of the Presidential document can be obtained from the Federal Register at http://edocket.access.gpo.gov/2008/pdf/08-1348.pdf

· Copies of the NMCI document can be obtained from the Navy’s Integrate Learning Environment website (https://www.public.navy.mil/netc/ile/Default.aspx).

· Copies of the SCORM documents can be obtained from http://www.adlnet.gov/capabilities/scorm/scorm-2004-4th#tab-resources.

· Copies of the Joint ADL Co-Lab document can be obtained from https://adlnet.gov/collaboration/dadlac.

· Copies of NAVAIRINST 5000.21B can be obtained from https://directives.navair.navy.mil/.

OPNAVINST 11010.20H

Facilities Project Instruction

· Copies of these instructions are available at http;//doni.daps.dla.mil

MIL-STD_130N

Department of Defense (DoD) Standard Practices – Identification Markings of U.S. Military Property

· Copies of this standard is available online at: http://quicksearch.dla.mil/qsSearch.aspx

DOD 5010-12M

Procedures for Acquisition Management of Technical Data

· The publication shown above is available at http://www.dtic.mil/whs/directives/corres/pdf/501012m.pdf

Defense Federal Acquisition Regulation Supplement (DFARS) 252.211-7003

Item Identification and Valuation (August 2008)

DFARS 252.239-7001

Information Assurance Contractor Training and Certification (January 2008)

· DFARS clauses are downloadable from http://www.acq.osd.mil/dpap/dars/dfarspgi/current/index.html

DFAR 2.101

Definitions

DFAR 52.204-9

Personal Identity Verification of Contractor Personnel

DFAR 52.222-54

Employment Eligibility Verification

DFAR 252.204-7012

Safeguarding Covered Defense Information and Cyber Incident Reporting

· DFAR clauses are downloadable from http://farsite.hill.af.mil/vffara.htm

DODD 8140.01

Cyberspace Workforce management, dated 11 August 2015

DODI 8520.02

Public Key Infrastructure (PKI) and Public Key (PK) Enabling, dated 24 May 2011

NIST SP 800-53r4

National Institute of Standards and technology (NIST) – Security and Privacy Controls for Federal Information Systems and Organizations, dated 22 January 2015

CNSSI 1253

Committee on National Security Systems Instruction (CNSSI) – Security Categorization and Control Selection for National Security Systems, dated 27 March 2014

SECNAV M-5239.2

Department of the Navy Cyberspace Information Technology and Cybersecurity Workforce management and Qualification manual, dated June 2016

(The above documents are available from the following sources:

· DOD Instructions, Directives, and Manuals are available at http://www.esd.whs.mil/DD/DoD-Issuances/

· NIST Special Publications are available at https://csrc.nist.gov/Publications

· CNSSI Instructions are available at https://www.cnss.gov

· SECNAV Manuals are available at https://doni.documentservices.dla.mil/manuals-secnav.aspx)

DoN NAVEDTRA Documents

NAVEDTRA 130B (series)

Task Based Curriculum Development Manual, (Volumes 1-3)

NAVEDTRA 131B (series)

Personnel Performance Profile Based Curriculum Development Manual, Volumes (1 – 3)

NAVEDTRA 132 (series)

Navy School Testing Program Management Manual

NAVEDTRA 136

Naval Education and Training Command Integrated Learning Environment Course Development and Life Cycle Maintenance

· Copies of the NAVEDTRA documents are available for download from https://www.public.navy.mil/netc/ntt/pdfs/

Naval Air Systems Command Instructions (NAVAIRINST)

NAVAIRINST 4355.19E

Systems Engineering Technical Reviews, dated 6 February 2015

· Copies of the NAVAIRINSTs are available for download from https://directives.navair.navy.mil

NAWCTSD Documents

NAVAIR Training Systems Domain Guide

Naval Air Systems Command Training Systems Domain Guide, version 1.0, dated October 2016

Security Assessment Procedures Document

NAWCTSD Assessment Procedures for the Omnibus Standalone-Unclassified Training Systems, dated 22 September 2016

· Copies of these NAWCTSD documents will be provided as part of the contract or Government Furnished Information (GFI)

Non-Government Documents

Industry Standards

ANSI = American National Standards Institute ISO = International Organization for Standardization

ANSI/ASQ/ISO 9001-2015

Quality Management Systems - Requirements

· Copies of the ANSI/ISO document is available from http://www.ansi.org

Electronic Industries Alliance (EIA)/SAE International

SAE/EIA-649-B

Configuration Management Standard

SAE/EIA-649-1 2014

Configuration Management Requirements for Defense Contracts

SAE/EIA 748-C

Earned Value Management Systems

GEIA-HB-649-A

Configuration Management Standard Implementation Guide, Revision A of February 2016

· Copies of the EIA/SAE documents are available from http://ansi.org

Institute of Electrical and Electronics Engineers (IEEE)/ISO/International Electrotechnical Commission (IEC)

IEEE/ISO/IEC

Systems and Software Engineering – Software Life Cycle Processes

· Copies of the IEEE/ISO/IEC documents are available from http://www.ieee.org

Requirements The Contractor shall organize, coordinate, and control program activities to ensure compliance with contract requirements and timely delivery of products specified herein.

General Requirements The Contractor shall provide the necessary hardware, software, personnel, supervision, management, materials, services, equipment, facilities, technical, logistics, and clerical support to perform the tasks specified in this SOW. The requirements defined herein form the basis for work performed for the Government during the entire contract. The Contractor shall meet the requirements of the SOW in accordance with (IAW) the guidance documents provided and the contents of this document.

Program Planning The purpose of the program planning process is to produce and communicate effective and workable program plans. The Contractor shall define, document, manage, and apply program planning processes IAW IEEE Std 12207-2008, sections 6.1.2.3.4.5, 6.3.1, and 7.1.1.3.1.

Life-Cycle Model Management The purpose of the life cycle model management process is to define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures for use by the program. The Contractor shall define, document, manage, and apply life cycle model management, at the program level, IAW IEEE Std 12207-2008, section 6.2.1. References to the organizational implementation of life cycle model management within IEEE Std 12207-2008, section 6.2.1 shall only apply to the program.

Infrastructure Management The purpose of the infrastructure management process is to provide the enabling infrastructure and services to the program and program objectives throughout the life cycle. The Contractor shall define, document, manage, and apply infrastructure management, at the program level, IAW IEEE Std 12207-2008, section 6.2.2. References to the organizational implementation of infrastructure management within IEEE Std 12207-2008, section 6.2.2 shall apply only to the program.

Program Assessment and Control The purpose of the program assessment and control process is to determine the status of the program and direct program plan execution. The Contractor shall define, document, manage, and apply program assessment and control IAW IEEE Std 12207-2008, section 6.3.2.

Program Decision Management The purpose of the decision management process is to select the most beneficial course of program action where alternatives exist. The Contractor shall define, document, manage, and apply a program decision management process IAW IEEE Std 12207-2008, section 6.3.3.

Contract Data Requirements Lists (CDRLs) The Contractor shall update, improve, manage, and deliver acceptable contractually required data. The Contractor shall implement data management procedures and policies to provide control and configuration management (CM) of contractually required data. CDRL items shall be submitted via NAWCTSD form 4330/60 (Data Item Transmittal or Acceptance or Rejection Sheet [DITS]). The Contractor shall:

a.	Ensure data items to be delivered to the Government meet the quantity and quality requirements of the CDRL.
b.	Establish data management procedures and policies to provide control and CM of contractually required data. To ensure sub-Contractors meet the contract data requirements set forth in the CDRL, the prime Contractor shall maintain control of work completed by sub-Contractors.
c.	Establish and maintain data libraries consisting of technical manuals, parent system technical description, and software documentation for the work completed for academic training systems and other data pertaining to training systems.

Online Management System (OMS) The Contractor shall establish, implement, and make available an OMS throughout the entire contract completion date. The Contractor shall use the OMS as a tool for communication between the Contractor and the Government. The Contractor shall maintain deliverables (all versions) and corresponding Government comments on the OMS. The Contractor shall include on the OMS supporting materials, agendas, and minutes for conferences (e.g., Post Award Conference [PAC]), meetings (e.g., Integrated Product Team [IPT]), reviews (e.g., In-Progress Report [IPR]) and materials (presentations, agendas, etc.). The Contractor shall make available the OMS to be used at the PAC.

Data Library The Contractor shall establish and maintain a data library consisting of non-proprietary documentation, data, and information. The Contractor shall record and maintain a master listing of non-proprietary contract related documentation, data, and information used, maintained, updated, and improved for use in this effort. File sharing (Section 3.1.6) between the Contractor and the Government reviewers shall be provided. An intuitive file structure and naming convention, file directories, and final deliverables shall be provided on the file-sharing website (i.e., OMS Section 3.1.3). The latest version of files (text, graphics, animations, videos, etc.) shall be made available by close of business on Fridays for download by the Government.

Configuration Management (CM) The Contractor shall define, document, manage, and apply a CM process. CM shall be controlled by the Contractor to ensure only files associated with a specific date, location, and rating are in the directory for those files. The Contractor shall notify the Government, via e-mail, what directories on the OMS have new or revised files by close of business each Friday.

File Sharing The Contractor shall allow for file sharing between the Contractor and the Government reviewers. An intuitive file structure and naming convention, file directories, and final deliverables shall be provided on the OMS (see Section 3.1.3). The Contractor shall provide the Government notification, via e-mail, of the latest version of files (text, graphics, animations, videos, etc.) by close of business on Fridays for download by the Government.

Contractor SMEs The Contractor shall employ personnel who are recent SMEs in the domain areas specific to the applicable ratings with experience in operations and/or maintenance as required by rating. The Government strongly encourages the Contractor to utilize SMEs (i.e., domain, Engineer and Instructional Design) to ensure technical accuracy, data, information, and reports developed by the Contractor meet Government specification and requirements. The Contractor shall ensure personnel assigned to the contract have the appropriate security clearance necessary to access information and facilities required (see Table 1).

Data and Software Rights The Contractor shall provide the Government with Licensing/Ownership Rights. All technical data and computer software, including, but not limited to source files, two- and three-dimensional imagery, three-dimensional models and wire-frames, video, audio, animations, design documentation, other supporting documentation, and courseware developed by the Contractor with Government funding, not private funding, are property of the Government and are not to be used for resale to any Government agency, organization, or command. If the Contractor is involved in any future efforts with the Government, pursuant to the Government’s Unlimited Rights as provided for under the contract, the Government will not be charged again for the technical data and computer software developed under this contract when provided to, or expected to be used by, or for the use by any Government agency, organization or Command including, any modifications, derivative, works, and any integrated products created through a non-segregable interface to the technical data or computer software.

Contractor Acquired Property During the performance of this SOW, the contractor shall transfer title of contractor acquired property procured for the performance of the efforts in this SOW in accordance with the Government Furnished Property (GFP) clauses of the delivery order.

Copyrights The Contractor shall follow Federal copyright laws and DON Instructions (Secretary of the Navy Instruction [SECNAVINST] 5870.4A, Copyright) during the effort. Media assets, content, and files that are not expressly created or written by the Contractor shall be accompanied with copyright permission requests and copyright granted documentation. The Contractor shall cultivate and maintain a copyright database (to be included in the Software Product Design CDRL A002) to record and track information and documentation pertaining to copyright content. Delivery shall be in accordance with CDRL A002.

Risk Management The Contractor shall conduct risk management reviews to allow program systematic control of the uncertainty in the project’s ability to meet cost, schedule, and performance requirements. The Contractor shall provide the Government visibility into the contractor’s tools, assessment, mitigation, and control techniques. The Contractor shall perform risk management activities and tasks as specified in IEEE Std 15288-2015, section 6.3.4.3. The Contractor shall lead and conduct a monthly joint risk working group for the program. The Contractor shall present and discuss the status of risk items during all scheduled conferences, meetings, and reviews using the 5x5 risk cube described in enclosure (1) of NAVAIRINST 5000.21B.

Quality Assurance and Management Plan (QAMP) The Government shall not serve as the Contractor’s quality assurance team. The Contractor shall define, document, manage, and apply a QAMP, including flowcharts, documenting multiple reviews at the program and corporate level. The Contractor shall document processes (e.g., inter-rater agreements for data categorization) and management controls employed to ensure requirements are met. The QAMP shall, at a minimum, include specific work required and methods used to determine product quality and technical adequacy and include methods for conducting intermittent and ongoing reviews of deliverables.

Communications Plan The Contractor shall define, document, manage, and apply a Communications Plan including internal and external communications. The Contractor shall document the Communications Plan methods relative to planning, developing, accomplishing, and reporting management, technical, and administrative tasks relevant to requirements.

Security The security requirements specified herein shall apply to the Contractor and subcontractors.

This is the start of the file's text. The full file is on GovTribe.

File details come from the government source that posted it. Updated Jun 29, 2020.