Atch_(1)_S2025_RRL_FY20CC_SOW.docx

DOCX document 2 MB Posted

Attached to
FY20 RRL CC Final RFP Posting
Solicitation number
N6134019R0022
Issued by

View the file

Other files

File Type Posted
FY20_Final_RFP_QA_Amend02.pdf PDF
Atch PDF
N6134019R0022_Amend0002_FINAL_6Aug19.docx DOCX document
N6134019R0022_SecL_SecM_Track_Changes_Amend02.pdf PDF
N6134019R0022_Conformed_Copy_Amend0002.docx DOCX document
N6134019R0022_Amend0002_Announcement_6Aug19.pdf PDF
Atch —
N6134019R0022_Amend0001_SecM_Track_Changes.pdf PDF
N6134019R0022_Conformed_Copy_Amend0001.docx DOCX document
Atch PDF
Atch —
N6134019R0022_Amend0001_Announcement_12Jul19.pdf PDF
N6134019R0022_Amend0001_SecL_Track_Changes.pdf PDF
FY20_Final_RFP_QA_Amend0001.pdf PDF
N6134019R0022_Amend0001.zip ZIP file
N6134019R0022_Amend0001_FINAL_12Jul19.docx DOCX document
TDPC_Contact_List_10Jul19.xlsx XLSX spreadsheet
FY20_CC_RFP_PPQ_Info_2Jul19.pdf PDF
N6134019R0022_FY20CC_RFP_Announcement_28Jun19.pdf PDF
TDPC_Contact_List_5Nov18_(2).xlsx XLSX spreadsheet
Att_(L-1)_Q&A_Form_21Mar2019.xlsx XLSX spreadsheet
DRAFT_RFP_Q&A_Government_POSTING_28Jun19.pdf PDF
Atch_(L-3)_Past_Performance_Questionaire(PPQ).docx DOCX document
Atch_(L-2)_PastPerformanceContractReferenceWorksheet.docx DOCX document
N6134019R0022_FINAL_RFP_28Jun19.docx DOCX document
Atch_(L-4)_Relevancy_Information_of_the_PP_Contract_FINAL_28Jun19.docx DOCX document
FY20_CC_PreSolSign-In_Sheet.pdf PDF
FY20_CC_PreSolConf_rv1.pptx PPTX presentation
N6134019R0022_DRAFT.docx DOCX document
Atch_(L-1)_Q&A_Form_21Mar2019.xlsx XLSX spreadsheet
TDPC_Contact_List_Lot_1_FA_2.xlsx XLSX spreadsheet
Show all 31

On GovTribe

Work with this file

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

Text version

SOW 190004

March 2019

29 March 2019

STATEMENT OF WORK (SOW)

FOR

SAILOR 2025 (S2025) FY20 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.

Change Log

Date
Section Number
Section Title
Change

Table of Contents

1.SCOPE1
1.1Background4
1.2Government Furnished Information (GFI)4
1.3Government Furnished Software, Tools, Equipment5
1.4Government Furnished Subject Matter Experts (SMEs)5
2.APPLICABLE DOCUMENTS5
2.1Government Documents5
2.2Department of Defense (DOD) Documents7
2.3Department of Navy (DON) Documents8
2.4S2025 Documents8
2.5Authoring Instruction Materials (AIM) Documents9
2.6Industry Standards9
2.7Other Documents10
3.REQUIREMENTS11
3.1General Requirements11
3.1.1Program Planning11
3.1.1.1Life Cycle Model Management11
3.1.1.2Infrastructure Management11
3.1.1.3Program Assessment and Control12
3.1.1.4Program Decision Management12
3.1.2Contract Data Requirements Lists (CDRLs)12
3.1.3Online Management System (OMS)12
3.1.4Data Library12
3.1.5Configuration Management (CM)13
3.1.6File Sharing13
3.1.7Integrated Product Team (IPT)13
3.1.8Contractor SMEs13
3.1.9Data and Software Rights14
3.1.10Contractor Acquired Property14
3.1.11Copyrights15
3.1.12Risk Management15
3.1.13Quality Assurance and Management Plan (QAMP)15
3.1.14Communications Plan15
3.2Management Requirements15
3.2.1Lead Integrator15
3.2.2Integrated Management Plan (IMP)16
3.2.2.1Work Planning and Scheduling16
3.2.2.2Development of the Contract Work Breakdown Structure (CWBS)16
3.2.2.3Subcontractor Management and Reporting17
3.2.2.4Schedule Risk Assessment (SRA)17
3.2.3Program Progress, Tracking, and Reporting17
3.2.4Conferences, Meetings, and Reviews18
3.2.4.1Post Award Conference (PAC)18
3.2.4.1.1PAC Entry Criteria19
3.2.4.1.2PAC Exit Criteria19
3.2.4.2Design Engineering Technical Interchange Meeting (ETIM)20
3.2.4.2.1Design ETIM Entry Criteria20
3.2.4.2.2Design ETIM Exit Criteria20
3.2.4.3Development ETIM20
3.2.4.3.1Development ETIM Entry Criteria21
3.2.4.3.2Development ETIM Exit Criteria21
3.2.4.4Test ETIMs21
3.2.4.5In-Process Review (IPR)21
IPR Entry Criteria22
IPR Exit Criteria22
3.2.4.6Data-Gathering Trips22
3.2.4.7Working Group (WG) or Content Design Meetings (CDMs)22
3.2.4.8Additional Meetings23
3.2.5Security23
3.2.5.1Classified Processing and Access to Classified Systems23
3.2.5.2Operations Security (OPSEC)23
3.2.5.3Unclassified Contractor-Owned Network Security - Safeguarding of Unclassified Controlled Technical Information24
3.2.5.4Cyber Incident and Compromise Reporting25
3.2.5.5Access to DOD Installations, Government Information, and Information Technology (IT) Systems - Personnel Security Background Checks25
3.2.5.6Personnel Security – Background Checks26
3.2.5.7International Traffic and Arms Regulation26
3.2.5.8Personnel Security – Reporting of Adverse or Derogatory Information related to Contractors26
3.2.5.9Government-Issued Personal Identification Credentials26
3.2.5.10Contractor “Out-processing” Policy27
3.2.5.11Supply Chain Risk Management (SCRM) For National Security Systems27
3.2.5.12Protection of Critical Program Information (CPI)27
3.2.5.13Transmission of Controlled Unclassified Information (CUI) via e-mail27
3.2.5.14Transmission of CUI via Army Research Laboratory Safe Access File Exchange (ARL SAFE)27
3.2.6Cybersecurity28
3.2.6.1Cybersecurity for training content products28
3.2.6.2Cybersecurity for other products28
3.2.6.3Cybersecurity Compliance28
3.2.6.3.1Cybersecurity Control Considerations28
3.2.6.3.2Cybersecurity Certification and Accreditation Support28
3.2.6.3.3Cybersecurity and Personnel Security Requirements for Accessing Government IT Systems - Credentialing Standards29
3.2.6.4Software Integrity Testing and Certification29
3.2.6.5Information Assurance Vulnerability Management Program (IAVMP)29
3.2.6.6Critical Program Information (CPI)29
3.2.6.7Cybersecurity Training & Certification29
3.3Instructional Design Requirements30
3.3.1Design Phase30
3.3.1.1Instructional Media Design Package (IMDP) Development (Style Guide)30
3.3.1.1.1Conventions31
3.3.1.1.2Interface and Design Controls31
3.3.1.2Model Product Creation31
3.3.1.2.1Performance Support (PS) Model Product Creation32
3.3.1.2.2Structured On the Job Training (SOJT) Model Product Creation32
3.3.1.2.3Interactive Courseware (ICW) Model Product Creation32
3.3.1.2.4Instructor Facilitated Interactive Training (IFIT) Model Product Creation33
3.3.1.3Lesson Design Strategy (LDS) Development for Self-Directed Interactive Training (SDIT) and IFIT Courses33
3.3.1.3.1Flow Diagrams Development34
3.3.1.3.2Courseware Overview34
3.3.1.3.3Integrated Course Schedule35
3.3.1.3.4Course Structure Format35
3.3.1.3.5Assessments (Test) Design Strategy35
3.3.1.3.6Performance Tracking Control Features35
3.3.2Development Phase35
3.3.2.1Instructional Media Usage36
3.3.2.2Photos and Graphics36
3.3.2.2.1Photo / Graphic Traceability Cross Reference Matrix36
3.3.2.2.2Photo and Graphic Capture38
3.3.2.3Development Phase: SDIT and IFIT38
3.3.2.3.1Script Storyboards (SSBs) Development38
3.3.2.3.2On-Screen Lessons (OSLs) Development39
3.3.2.3.3Tests and Assessments Creation39
3.3.2.3.3.1Test Banks39
3.3.2.3.3.2Test Administration Materials39
3.3.2.3.3.3Assessment Items39
3.3.2.3.3.4Checks on Learning (COL)40
3.3.2.3.3.5Posttests40
3.3.2.3.3.6Assessment Item Cross-Reference Chart40
3.3.2.3.3.7Answer Keys40
3.3.2.3.4Instructor Facilitated Interactive Training Curriculum Package Creation40
3.3.2.3.4.1Instructor Guides (IGs) and Lesson Plans (LPs) Creation40
3.3.2.3.4.2Instructor Guidance41
3.3.2.3.4.3Instructor Training Handouts and Presentation Materials Creation41
3.3.2.3.4.4Instructional Visual Aids41
3.3.2.3.4.5Trainee Guides (TGs) or Student Guides (SGs) Creation41
3.3.2.3.4.6Student Guidance41
3.3.2.4Development Phase: PS and SOJT42
3.3.2.4.1Performance Support (PS) Development42
3.3.2.4.2SOJT Development42
3.3.3Implementation Phase43
3.3.3.1Training Course Control Data (TCCD)43
3.3.3.1.1Training Planning Data43
3.3.3.1.2Training Project Plan (TPP)43
3.3.3.1.3Training Course Data43
3.3.3.2Training Systems Support Procedures44
3.3.3.2.1Training Syllabus44
3.3.3.2.2Skill Progression44
3.3.3.2.3Training Resource Requirements44
3.3.3.2.4Training Exercises44
3.3.3.2.5Training Exercise Formulation44
3.3.3.3Train the Trainer (T3)45
3.3.3.3.1T3 Entry Criteria45
3.3.3.3.2T3 Exit Criteria45
3.3.3.4Pilot45
3.3.3.4.1Pilot Entry Criteria46
3.3.3.4.2Pilot Exit Criteria46
3.3.4Evaluation Requirements Phase46
3.3.5Delivery Requirements Phase46
3.3.5.1Delivery of Training Solution Products46
3.3.5.2Developmental Source Material46
3.3.5.3Instructional Media Source (Data) Files47
3.3.5.4Transportability and Maintainability of Data47
3.3.5.4.1Advanced Distributed Learning (ADL) Data Requirements47
3.3.6CD-ROM or DVD Inspection or Acceptance47
3.3.6.1Learning Management System (LMS) Integration47
3.3.6.2Content and Functional Integrity47
3.4Systems Engineering Requirements48
3.4.1Risk Management48
3.4.2Media Requirements Development & Definition48
3.4.2.1Requirements Development and Management48
3.4.2.2Media Trade Studies48
3.4.2.3Media Design and Development48
3.4.3Media Requirements Verification & Validation49
3.4.4Technical Reviews and Meetings49
3.4.4.1Working Group Meetings49
The Contractor shall participate as an active member in the following identified working groups and conduct formal meetings per the requirements of their working group charters:49
3.4.4.1.1Technical Interchange Meetings (TIM)49
3.4.4.2Government Facilities Access50
3.4.5Content Conversion (CC) Requirements50
3.4.5.1Requirements Analysis Phase50
3.4.5.2Design Phase50
3.4.5.2.1Training Environments51
3.4.5.2.1.1Display Resolutions and Aspect Ratios51
3.4.5.2.2Design Implementations to Reduce TRANET VDI Bandwidth Usage51
3.4.5.2.3Experience Application Program Interface (xAPI) Requirements52
3.4.5.3Mobile Requirements53
3.4.5.4Development Phase53
3.5Test and Evaluation (T&E)53
3.5.1Testing Requirements53
3.5.2Responsibility for Tests54
3.5.3Test Authority54
3.5.4Test Resources and Facilities54
3.5.5Test Methods54
3.5.6Verification Criteria55
3.5.7Configuration55
3.5.8Verification Log55
3.5.9Changes During Testing55
3.5.9.1Software Changes During Government Testing55
3.5.10Changes After Testing55
3.5.11T&E Non-Conformance Reporting System56
3.5.11.1Deficiency Review Board (DRB)56
3.5.11.2Deficiency and Discrepancy Adjudication56
3.5.12T&E Program Components for NeL Training Environment57
3.5.12.1NeL Test Track Contractor Testing (DT-D1)57
3.5.12.1.1NeL Content Announcement Form Completion57
3.5.12.1.2NeL Content Acknowledgement Form Completion57
3.5.12.2Test ETIM #157
3.5.12.3NeL Test Track Government Testing (DT-D2)58
3.5.12.3.1DT-D2 Changes58
3.5.12.4Test ETIM #258
3.5.12.5Government Content Acceptance Testing (GCAT)58
3.5.12.5.1GCAT NeL Review Changes59
3.5.12.5.2ATLAS GCAT Changes59
3.5.12.6Content Installation & Validation59
3.5.12.7Regression Testing59
3.5.13T&E Program Components for Non-NeL Environments59
3.5.13.1Non-NeL Environments Contractor Internal Testing (DT-D1)60
3.5.13.2Test ETIM60
3.5.13.3Non-NeL Environments Integrated Testing (IT-D1)61
3.5.13.3.1IT-D1 Entry Criteria61
3.5.13.4Content Installation & Validation62
3.5.13.5Regression Testing62
3.6Delivery Requirements63
3.6.1Software Product63
3.6.1.1Installation and Configuration Procedures63
3.6.1.2Media and Storage Devices64
3.6.1.3Cold Start and Installation Procedure Media64
3.6.1.4Automated Processes64

List of Tables

Table 1: Government Documents6
Table 2: Department of Defense (DOD) Documents7
Table 3: Department of Navy (DON) Documents8
Table 4: S2025 Documents8
Table 5: Authoring Instruction Materials (AIM) Documents9
Table 6: Industry Standards10
Table 7: Other Documents11
Table 8. Rating and Classification Requirements14
Table 9: Photo/Graphic Traceability Cross Reference Matrix38

List of Figures

Figure 1: Content Conversion Process1
Figure 2: RRL Training Strategies and Training Support Products2
Figure 3: Training Environment and Devices3

MARCH 2019

March 2019

STATEMENT OF WORK (SOW)

FOR

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

CONTENT CONVERSION (CC)

SCOPE

This Statement of Work (SOW) documents the Contractor tasks for the design, development, testing, and delivery of products in support of the Sailor 2025 (S2025) Fiscal Year 2020 (FY20) Ready Relevant Learning (RRL) Content Conversion (CC) effort. Figure 1 identifies the process for converting content into various product types outlined within the SOW.

Figure 1: Content Conversion Process

The project is to employ innovative instructional design and assessment strategies in conjunction with new and modernized technology to support the ratings accession training while simultaneously supporting the broader S2025 overarching goal of improving Sailors’ transfer of training to the operational work environment. Figure 2 identifies training strategies and training and performance support products that will be used to support the RRL effort.

Figure 2: RRL Training Strategies and Training Support Products

The effort will facilitate the creation and conversion of training products to be hosted within specific training environments. Figure 3 identifies the training environments and devices capable of presenting training content within the current Naval training enterprise.

Figure 3: Training Environment and Devices For this effort, the Naval Air Warfare Center Training Systems Division (NAWCTSD), as the RRL Training Systems Program Manager, is responsible for A School and accession C School CC, in support of RRL, for the following ratings (Highest classification is Unclassified FOUO unless otherwise noted):

· Aviation Electrician’s Mate (AE)

· Basic Engineering Common Core (BECC)

· Boatswain’s Mate (BM)

· Damage Controlman (DC)

· Engineman (EN)

· Engineering Professional Apprenticeship Career Track (EPACT)

· Electrician’s Mate (EM)

· Gas Turbine System Technician (Electrical); (GSE)

· Gas Turbine System Technician (Mechanical); (GSM)

· Hull Maintenance Technician (HT)

· Quartermaster (QM)

· Machinist’s Mate (MM(SUR))

· Machinery Repairmen (MR)

· Aviation Structural Mechanic-Safety Equipment (AME)

· Master at Arms (MA)

· Mineman (MN)

· Religious Program Specialist (RP)

· Seaman Professional Apprenticeship Career Track (SPACT)

This DO also includes:

· Train-the-Trainer (T3)

· Pilot

The appendices are as follows:

· Appendix A provides a list of rating requirements.

· Appendix B provides a list of acronyms and definitions used within this SOW.

· Appendix C provides a list of terms and definitions used within this SOW.

· Appendix D provides a list of the Contract Data Requirements Lists (CDRLs) linked with the Instructional Design Requirements identified within this SOW.

· Appendix E provides a Risk Assessment Example Format.

· Appendix F provides a list of conference meetings duration and locations.

· Appendix G provides the definitions of the performance and training strategies.

· Appendix H provides explanations for operationally engaging instructional strategies to be used in development.

· Appendix I provides a list of Bloom’s taxonomy action verbs.

· Appendix J provides a list of media capabilities and training delivery environments for media solutions at different levels of interactivity.

· Appendix K provides a list of media definitions.

· Appendix L provides a mobile learning roadmap.

· Appendix M lists the Experience Application Program Interface (xAPI) requirements.

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

· Appendix O provides guidance on NETC RRL Video Streaming.

· Appendix P provides the S2025 RRL Media Map.

Background The work outlined in this SOW contributes to the broader S2025 effort that has the overarching goal of improving Sailors’ transfer of training to the operational work environment. The following represents examples of the broader 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).

· Modernizing media that is engaging.

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

Government Furnished Information (GFI) The Government will provide the following references:

a. Functional Requirements Document (FRD) Appendix C data for AE, QM, DC, EM, EN, GSE, GSM, HT, MM, MR, BECC, EPACT, BM

b. Preliminary Analysis Results Data for ratings AME, MA, RP, SPACT, MN

c. FRD Reports (one document for each rating, etc.)

d. Knowledge Capture (KC) photos for each rating

e. KC data for each rating

f. Training Guides, Lesson Plans, TCCD, COI for each rating

g. Existing courseware (ICW, IMI, etc.) examples for ratings

h. NETC Style Guide

Government Furnished Software, Tools, Equipment The Government will not furnish software (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 a developer’s seat, within the test bed, for the Contractor to debug training materials tested. 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

Document Number
Document Title and/or Description
22 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
NIST SP 800-44
Guidelines on Securing Public Web Servers

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)

· Copies of the CFR sections can be obtained from http://www.pmddtc.state.gov/regulations_laws/itar_offical.html.

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

· Copies of 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.

Table 1: Government Documents

Department of Defense (DOD) Documents

Document Number
Document Title and/or Description
DODI 1322.26
Development, Management, and Delivery of Distributed Learning dated 16 Jun 2006
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

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 ADL Products and Systems (Part 5 of 5)
MIL-PRF-29612B
Performance Specification Training Data Products

· 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/)

Table 2: Department of Defense (DOD) Documents

Department of Navy (DON) Documents

Document Number
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
SECNAVINST 5000.36A
Department of the Navy Information Technology Application and Data Management
SECNAVINST 5870.4A
Copyright, dated 16 Aug 2005
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 http://www.doncio.navy.mil/PolicyView.aspx?ID=73

· Copies of the DON documents can be obtained online from the Navy’s Integrate Learning Environment website (http://www.secnav.navy.mil/rda/Policy/Forms/AllItems.aspx?RootFolder=%2frda%2fPolicy%2fSECNAVINST%205000&FolderCTID=0x012000C996D88A9F817948AB69758011503AE2).

· Copies of the Secretary of the Navy (SECNAV) documents can be obtained from http://doni.daps.dla.mil/allinstructions.aspx.

Table 3: Department of Navy (DON) Documents S2025 Documents

Document Number
Document Title and/or Description

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

Appendix G
Sailor 2025 RRL Performance and Training Strategies
Appendix J
Sailor 2025 RRL Content Conversion Media Type Characteristics
Appendix K
Sailor 2025 RRL Content Conversion Media Definitions
Appendix I
Sailor 2025 RRL Content Conversion Use of Bloom’s Taxonomy Action Verbs
Appendix H
Sailor 2025 RRL Content Conversion Operational Engaging Instructional Strategies
Appendix P
Sailor 2025 RRL Media Map

Table 4: S2025 Documents

Authoring Instruction Materials (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

AIM 2 User’s Manual

Copies of the AIM documentation can be obtained from (https://studylib.net/doc/18638038/netc-e2e-sop---authoring-instructional-materials--aim/)

Table 5: Authoring Instruction Materials (AIM) Documents 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
AICC
Aviation Industry CBT Committee (AICC) Guidelines and Recommendations (AGRs) can be obtained from http://www.aicc.org. Recommended documents to download include:

· AGR 007—Courseware Interchange

· AGR 008—Digital Video

· AGR 009—Icon Standards: User Interface

· AGR 010—Web-based Computer Managed Instruction (CMI)

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
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-3rd-edition/scorm-2004-3rd-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.)

Table 6: Industry Standards 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
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
NETC RRL IT Roadmap
Unnumbered Document
Mobile Learning & Technology Roadmap
Unnumbered Document
NETC RRL Video Streaming Guidance
Appendix N
NETC RRL Single User Gaming and Simulation Guidance

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

Table 7: Other Documents

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 DO. The Contractor shall meet the requirements of the SOW 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 DO 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.

Integrated Product Team (IPT) The Contractor shall define, document, implement, and maintain an IPT structure for the entire DO duration. The IPT provides a forum for discussion and resolution of concerns voiced by either Government or Contractor personnel. IPT membership may consist of multi-functional stakeholders working together with a product-oriented focus. The IPT will consist of Government and Contractor personnel and have a Government chair. The IPT establishes a Government and Contractor IPT partnership beneficial to achieving program goals and allows for participation and feedback among IPT members. Specific IPT or Working IPT (WIPT) at a minimum shall include weekly IPT or WIPT meetings (frequency of recurrence may be changed to a mutually agreed upon frequency); date and time shall be determined at the PAC and be mutually agreed upon. The Contractor shall provide a recap email to the IPT or WIPT members of each IPT or WIPT meeting. The Contractor shall include in the IPT or WIPT recap email, date of meeting, attendees, discussion topics, action items, and date of next IPT or WIPT meeting. VTC or Webinar shall be used where suitable for time efficiency and for cost saving measures. At no time shall the Contractor accept guidance from the IPTs that shall have a cost, schedule, or performance impact upon the effort. In the event an IPT identifies an out-of-scope requirement, this requirement shall be passed to the NAWCTSD PCO.

Contractor SMEs The Government strongly encourages the Contractor to 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. Table 8 identifies the rating, information classification, facilities access classification and when Contractor personnel would need to have the classification in order to meet content conversion courseware.

Table 8. Rating and Classification Requirements

Rating
Information Classification
Facilities Access Classification
When Classification Required
AE
Unclassified FOUO
Unclassified
At Contract Award
BECC
TBD
TBD
TBD
QM
Unclassified NOFORN
Unclassified
At Contract Award
DC
Secret NOFORN
Unclassified
At Contract Award
EM
Unclassified FOUO
Unclassified
At Option Execution
EN
Unclassified FOUO
Unclassified
At Option Execution
GSE
Unclassified FOUO
Unclassified
At Option Execution
GSM
Unclassified FOUO
Unclassified
At Option Execution
HT
Unclassified FOUO
Unclassified
At Option Execution
MM(SUR)
Secret NOFORN
Unclassified
At Contract Award
MR
TBD
Unclassified
TBD
EPACT
TBD
Unclassified
TBD
BM
TBD
Unclassified
TBD
AME
TBD
Unclassified
TBD
MA
TBD
Unclassified
TBD
RP
TBD
Unclassified
TBD
MN
TBD
TBD
TBD
SPACT
TBD
Unclassified
TBD

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 DO, 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 CDRL A005) to record and track information and documentation pertaining to copyright content. Delivery shall be in accordance with CDRL A005.

Risk Management The Contractor shall implement and execute risk management processes that meet the requirements of the RRL TSPM Risk Management Plan (RMP). The Contractor shall coordinate and perform assessments of risks and formulate plans to mitigate risks. The Contractor shall participate in the FY20CC Joint Government and Contractor Risk Management Boards (RMBs). The Contractor’s responsibilities shall include identifying and assessing risks, formulating risk mitigation plans, and completing risk mitigation steps. The Contractor shall make available risk assessments and mitigation status utilizing TBD to support effective and timely mitigation of risks. The Contractor shall provide status of risks at reviews and meetings. The Contractor shall define, document, and deliver the FY20CC Risk Management Plan IAW CDRL A001. The Contractor shall manage risk using the FY20CC Risk Management Plan and Appendix E Risk Assessment Example Format.

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.

Management Requirements The Contractor shall organize, coordinate, and control the project activities to ensure compliance with requirements and the timely delivery of the product and services required. The Contractor shall provide the necessary management functions to support the effort.

Lead Integrator The Contractor shall function as a Lead Integrator. A Lead Integrator is a Contractor who provides management oversight of subcontractor(s), ensuring integration, standardization, and uniformity of Government requirements within a large scale contract, focusing primarily on instructional systems design and systems engineering products providing training support products and courseware delivered via traditional methods and using software-based delivered methods. The Contractor, as a Lead Integrator, shall manage all aspects of the contract including ensuring the timely award of all subcontracts, integration of their subcontractors’ plans and status into appropriate schedules with sufficient detail, monitoring the subcontractors’ staffing plans, and execution of those staffing plans to the required levels with the necessary skills. The Contractor shall reserve the right for themselves, and for the Government accompanied by a representative of the prime contractor, to send personnel into the subcontractor’s facilities to monitor and evaluate subcontracted activities. The Contractor shall ensure that the subcontractors’ technical efforts are accomplished per contract requirements. The Contractor shall monitor subcontractor quality, configuration management, risk processes, and ensure that subcontractors use objective criteria to measure performance.

Integrated Management Plan (IMP) The Contractor shall develop a detailed IMP describing the Contractor’s organization, assignment of functions, duties, responsibilities, management procedures and policies, plans for deliverable intermittent and ongoing reviews, and reporting requirements for the effort. The Contractor shall detail management and control processes to integrate activities within SOW requirements, schedule requirements, and quality assurance activities. The Contractor shall prepare and deliver the IMP IAW CDRL B001.

Work Planning and Scheduling The Contractor shall document the work planning and scheduling of content conversion requirement processes including Government responsibilities (i.e., review of deliverables) and the interaction between Government and Contractor for the content conversion requirements for the design, development, and delivery of the training products. The Contractor shall develop, implement, control, and maintain an Integrated Master Schedule (IMS) that presents the Contractor’s plans and schedules to meet the requirements of the contract. The Contractor shall develop and document a tiered scheduling system based on the Contract Work Breakdown Structure (CWBS) elements showing program milestones and prerequisite events, conferences, reviews, data submittals, deliveries, materials, travel, and other direct costs. The Contractor shall integrate contract deliverables and subcontractor schedules into the IMS. The Contractor shall construct the IMS to ensure that the program milestones are met and to ensure that deliveries meet the requirements of the contract. Contractor schedule information delivered to the Government or presented at program reviews shall originate from the IMS. The Contractor shall perform analyses of the IMS tasks, compare the IMS tasks to the schedule baseline, report potential or existing problem areas, and recommend corrective actions to eliminate or reduce schedule impact. The Contractor shall use the IMS as a day-to-day execution tool and to periodically assess progress in meeting program requirements. For any Agile methodologies utilized during the development phase, the Contractor shall detail release planning including Epics/Capabilities and Features, at a minimum, within their period of detail planning for those products. The Contractor shall prepare the IMS IAW the Integrated Program Management Report (IPMR), CDRL B002.

Development of the Contract Work Breakdown Structure (CWBS) The Contractor shall develop, document, maintain and apply a CWBS and CWBS dictionary that define the work structures required to perform the work required by the contract IAW Military Standard-881D (MIL-STD-881D). The Contractor shall use the CWBS as the framework for contract planning, budgeting, and reporting of cost, schedule, and performance. The Contractor shall extend this CWBS to control accounts, work packages, and lower levels that represent the plan to accomplish the entire contract work scope consistent with internal organizations and processes. The Contractor shall define and describe each element of the CWBS in the CWBS dictionary. During the performance of the contract, the Contractor shall not change the approved CWBS or associated definition, or the reporting elements, without written approval from the Government. The Contractor shall prepare the CWBS and Dictionary IAW CDRL B003.

Subcontractor Management and Reporting The Contractor shall ensure the timely award of all subcontracts, integration of their subcontractors’ plans and status into appropriate schedules with sufficient detail, monitoring the subcontractors’ staffing plans, and execution of those staffing plans to the required levels with the required skills. The contractor shall reserve the right for themselves, and for the Government accompanied by a representative of the prime contractor, to send personnel into the subcontractor’s facilities to monitor and evaluate subcontracted activities. The Contractor shall ensure that the subcontractors’ technical efforts are accomplished per contract requirements. The Contractor shall monitor subcontractor quality, CM, risk processes, and ensure that subcontractors use objective criteria to measure performance. The Contractor shall flow down separate IPMR reporting requirements to subcontractors IAW the IPMR CDRL B002 for subcontracts exceeding $20M.

Schedule Risk Assessment (SRA) The Contractor shall participate in Government conducted Probabilistic SRA as per the SRA frequency and direction delineated in the CWBS and Dictionary IAW CDRL B003. SRAs are conducted to determine how major areas of uncertainty in the schedule could impact contractual milestones, including assumptions and potential effects of the identified schedule risks. In addition to the paths identified in the IPMR CDRL B002, the Contractor shall also report optimistic, pessimistic, and most likely remaining durations and rationale for the values for each task and activity on the following paths: driving path to the next Major Milestone, the next three near-driving paths to the next Major Milestone. A complete SRA shall be performed outside of routine scheduled occurrences, at the request of the Government, when the schedule is a significant issue due to operational requirements, funding limitations, and when scheduling is considered a major risk element to the acquisition effort. If the Contractor conducts internal SRAs as part of their standard business practices (i.e., independent of those executed with the Government), the Contractor shall provide the result of those assessments to the Government. The Contractor shall document and report the results of the SRAs in the Contractor’s Progress, Status, and Management Report CDRL B004.

Program Progress, Tracking, and Reporting The Contractor shall track, measure, monitor, assess, summarize, and report the work progress, and schedule performance information under the contract to the Government. The Contractor shall identify program risks, perform risk analysis, risk handling, risk monitoring, and create a risk reporting matrix using Naval Systems Commands (SYSCOM) Risk Instruction, signed 21 July 2008, as guidance. The Contractor shall use Appendix E – Risk Assessment Example Format for an example of a risk reporting matrix, supporting identified risks, and the risk analysis format. The Contractor shall prepare and deliver the Contractor’s Progress, Status, and Management Report IAW CDRL B004.

Conferences, Meetings, and Reviews The Contractor shall conduct, attend, and participate in conferences (e.g., PACs), meetings (e.g., Content Design Meetings [CDMs]), reviews (e.g., IPRs, Engineering Technical Interchange Meetings [ETIMs]), and scheduled trips (e.g., for data gathering, reviews, photo capture) at either Government or Contractor facilities. Duration, location, and frequency are outlined in Appendix F. Conferences, meetings, and reviews shall be co-chaired by a Government and a Contractor representative. The Contractor shall have key personnel and support available to carry out the meetings. Subcontractors shall be required to attend conferences, meetings, and reviews when required to address key elements of the program. The Contractor shall make available facilities for Government only meetings during conferences, meetings, and reviews. The Contractor shall prepare presentation and other materials, as required, to aid in the conduct of the conferences, meetings, and reviews (i.e., intermittent and ongoing reviews of deliverables). The Contractor shall prepare the Conference Agenda and Conference Minutes for each conference, meeting, review, and scheduled trip IAW CDRLs B005 and B006, respectively. Once set, changes to the scheduled meeting shall be submitted via e-mail to and approved by the Government PM.

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.