Atch (1)_FY24_CC_DRAFT_SOW_31May23.docx
DOCX document 304 KB Posted
- Solicitation number
- N6134023R0073
View the file
Other files
Show all 28
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
Statement of Work for the FY24 Content Conversion Effort 31 May 2023
STATEMENT OF WORK (SOW)
FOR
READY RELEVANT LEARNING (RRL)
FISCAL YEAR 2024 (FY24) CONTENT CONVERSION (CC)
FOR
aVIATION tECHNICIAN (at) AND AIRCREW (AW) RatingS 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
31 May 2023
DISTRIBUTION A. Approved for public release. Distribution is unlimited.
This page intentionally left blank.
Change Log
| Date |
| Section Number |
| Section Title |
| Change |
Statement of Work for the FY24 Content Conversion Effort 31 May 2023 vii Table of CONTENTS
| Para. | Title | Page |
| 1 | Scope | 6 |
| 1.1 | Rating Requirements | 6 |
| 1.2 | Course, Module and Lesson Structure | 7 |
| 1.3 | Content Delivery Modes and Media Types | 7 |
| 1.4 | Coordination With Third Parties | 8 |
| 1.5 | List of SOW Appendices | 8 |
| 1.6 | Terms and Definitions | 9 |
| 1.7 | Terms and Definitions | 9 |
| 1.8 | Government-Furnished Information (GFI) | 9 |
| 1.9 | Government-Furnished Software, Tools, and Equipment | 10 |
| 1.10 | Government-Furnished Subject Matter Experts (SMEs) | 10 |
| 2 | Applicable Documents | 10 |
| 2.1 | Government Documents | 10 |
| 2.2 | Department of Defense (DOD) Documents | 11 |
| 2.3 | Department of the Navy (DON) Documents | 12 |
| 2.4 | Authoring Instructional Materials (AIM) Documents | 13 |
| 2.5 | Industry Standards | 13 |
| 2.6 | Other Documents | 14 |
| 3 | Requirements | 17 |
| 3.1 | General Requirements | 17 |
| 3.1.1 | RRL Content Conversion Planning | 17 |
| 3.1.1.1 | Life-Cycle Model Management | 17 |
| 3.1.1.2 | Infrastructure Management | 17 |
| 3.1.1.3 | Program Assessment and Control | 17 |
| 3.1.1.4 | Program Decision Management | 18 |
| 3.1.2 | Contract Data Requirements Lists (CDRLs) | 18 |
| 3.1.3 | Online Management System (OMS) | 18 |
| 3.1.4 | Scrum Board Requirements | 19 |
| 3.1.5 | Configuration Management (CM) | 19 |
| 3.1.6 | Contractor Subject Matter Experts (SMEs) | 19 |
| 3.1.7 | Quality Assurance and Management Plan (QAMP) | 19 |
| 3.1.7.1 | Control of Government-Furnished Information (GFI) | 19 |
| 3.1.8 | Communications Plan | 20 |
| 3.2 | Security | 20 |
| 3.2.1 | Operations Security (OPSEC) | 20 |
| 3.2.2 | Unclassified Contractor-Owned Network Security – Safeguarding of Unclassified Controlled Technical Information | 21 |
| 3.2.3 | Cyber Incident and Compromise Reporting | 21 |
| 3.2.4 | Access to DOD Installations, Government Information and Information Technology (IT) Systems – Personnel Security Background Checks | 21 |
| 3.2.5 | Personnel Security – Background Checks | 22 |
| 3.2.6 | International Traffic and Arms Regulation | 22 |
| 3.2.7 | Personnel Security – Reporting of Adverse or Derogatory Information Related to Contractors | 22 |
| 3.2.8 | Government-Issued Personal Identification Credentials | 23 |
| 3.2.9 | Contractor “Out-Processing” Policy | 23 |
| 3.2.10 | Protection of Critical Program Information (CPI) | 23 |
| 3.2.11 | Transmission of Controlled Unclassified Information (CUI) Via Email | 23 |
| 3.2.12 | Transmission of CUI via DOD Safe Access File Exchange (DOD SAFE) | 24 |
| 3.3 | Cybersecurity | 24 |
| 3.3.1 | Critical Program Information (CPI) | 24 |
| 3.3.2 | Cybersecurity Training and Certification | 24 |
| 3.3.3 | Software Integrity Testing and Certification | 25 |
| 3.4 | Management Requirements | 25 |
| 3.4.1 | Integrated Product Team (IPT) | 25 |
| 3.4.2 | Work Planning and Scheduling | 26 |
| 3.4.3 | Subcontractor Management and Reporting | 26 |
| 3.4.4 | Risk Management | 26 |
| 3.4.5 | Program Progress, Tracking, and Reporting | 27 |
| 3.4.6 | Conferences, Meetings, and Reviews | 27 |
| 3.4.6.1 | Post Award Conference (PAC) | 27 |
| 3.4.6.2 | In-Process Review (IPR) Meetings | 29 |
| 3.4.6.3 | Daily Standup Meeting, and or Biweekly Sprints | 29 |
| 3.4.6.4 | Sprint Planning Meetings | 29 |
| 3.4.6.5 | Sprint Demos and Product Design Reviews | 29 |
| 3.4.6.6 | Systems Engineering IPT (SEIT) Sprints | 29 |
| 3.4.6.7 | Data-Gathering Trips | 30 |
| 3.5 | RRL Content Conversion Requirements | 30 |
| 3.5.1 | Training Material Design | 30 |
| 3.5.1.1 | Design for Training Product Delivery Environments | 31 |
| 3.5.1.1.1 | Design Implementations to Reduce TRANET Virtual Desktop Infrastructure (VDI) Bandwidth Usage | 32 |
| 3.5.1.1.2 | Design for Experience Application Program Interface (xAPI) Requirements | 33 |
| 3.5.1.1.3 | Design for Mobile Requirements | 34 |
| 3.5.2 | IMI, Media Types | 34 |
| 3.5.2.1 | NETC Style Guide Updates | 34 |
| 3.5.2.2 | Lesson Prototypes | 35 |
| 3.5.2.3 | Photos and Graphics | 35 |
| 3.5.2.4 | Test Package Development (Assessments) | 36 |
| 3.5.2.5 | Course Testing Plan (Administration) | 36 |
| 3.5.2.6 | Training Conduct Support Document (TCSD) | 37 |
| 3.5.2.7 | Training Program Structure Documents (TPSD) | 37 |
| 3.5.2.8 | Training Systems Support Document (TSSD) | 37 |
| 3.5.2.9 | Test & Evaluation for IMI | 38 |
| 3.5.2.9.1 | T&E Program Components for NETC LMS-deployed IMI (LMS IMI) | 38 |
| 3.5.2.9.1.1 | LMS CHaRMS Record Process | 38 |
| 3.5.2.9.1.2 | LMS System Integration & Testing (LMS SI&T) | 38 |
| 3.5.2.9.1.3 | LMS Government Content Acceptance Testing (LMS GCAT) | 39 |
| 3.5.2.9.2 | T&E Program Components for Stand-Alone Configuration IMI (SAC IMI) | 39 |
| 3.5.2.9.2.1 | SAC Contractor Internal Testing | 39 |
| 3.5.2.9.2.2 | SAC Government Content Acceptance Testing (SAC GCAT) | 39 |
| 3.5.2.10 | T3 and Course Pilot Preparation | 40 |
| 3.5.2.10.1 | Instructional Media Package (Media Source Files) | 40 |
| 3.5.2.10.2 | Instructional Media Package (Final Curriculum Delivery) | 40 |
| 3.5.3 | Complex Media (VSIM) Types | 40 |
| 3.5.3.1 | Systems Engineering Processes | 40 |
| 3.5.3.1.1 | System Requirements Analysis | 40 |
| 3.5.3.1.2 | Traceability | 41 |
| 3.5.3.1.3 | System Architectural Design | 41 |
| 3.5.3.1.4 | Test Readiness Review | 41 |
| 3.5.3.1.5 | Design Baseline | 41 |
| 3.5.3.2 | Agile/Scrum Approach to Software Engineering | 42 |
| 3.5.3.2.1 | Agile Software Development | 42 |
| 3.5.3.2.2 | Complex Media (VSIM) SPD | 42 |
| 3.5.3.2.3 | Release Backlog In-Progress Review (RBIPR) | 42 |
| 3.5.3.2.4 | Complex Media (VSIM) Design Technical Interchange Meeting (TIM) | 43 |
| 3.5.3.2.4.1 | Complex Media (VSIM) Design TIM Entry Criteria | 44 |
| 3.5.3.2.4.2 | Complex Media (VSIM) Design TIM Exit Criteria | 44 |
| 3.5.3.2.5 | Complex Media (VSIM) In-Progress Reviews | 45 |
| 3.5.3.2.6 | Software Architectural Design | 45 |
| 3.5.3.2.7 | Software Product Design | 45 |
| 3.5.3.2.8 | Software Implementation | 45 |
| 3.5.3.2.8.1 | Software Unit Construction and Testing | 46 |
| 3.5.3.2.9 | Software Integration | 46 |
| 3.5.3.2.10 | Cold Start Process | 46 |
| 3.5.3.2.10.1 | Software Product Execution | 46 |
| 3.5.3.2.10.2 | Software Media Marking | 46 |
| 3.5.3.2.10.3 | Media and Storage Devices | 47 |
| 3.5.3.3 | Test & Evaluation for Complex Media (VSIM) | 47 |
| 3.5.3.3.1 | Test Methods | 47 |
| 3.5.3.3.1.1 | Quality of Test Data | 47 |
| 3.5.3.3.1.2 | Code Analysis | 48 |
| 3.5.3.3.2 | Software Changes during Test | 48 |
| 3.5.3.3.3 | Non-Conformance Reporting System | 48 |
| 3.5.3.3.4 | T&E Program Components for Complex Media (VSIM) | 49 |
| 3.5.3.3.4.1 | Internal Contractor Testing (Simulation DT-D1) | 49 |
| 3.5.3.3.4.2 | Test Readiness Review (TRR) | 49 |
| 3.5.3.3.4.3 | Government Acceptance Testing (Simulation IT-D1) | 50 |
| 3.5.3.3.4.4 | Test Discrepancy Review Board (TDRB) | 50 |
| 3.5.3.4 | Detailed Tasks for Complex Media (VSIM) | 50 |
| 3.5.3.4.1 | Complex Media (VSIM) SI Appendices to the Rating SPD | 51 |
| 3.5.3.4.2 | Training Support Products | 51 |
| 3.5.3.4.2.1 | Complex Media (VSIM) T3 and Course Pilot Preparation | 51 |
| 3.5.3.4.2.2 | Instructional Media Package (Media Source Files) | 51 |
| 3.5.3.4.2.3 | Instructional Media Package (Final Curriculum Delivery) | 51 |
| 3.5.4 | Human Factors Engineering (HFE) | 52 |
| 3.5.5 | Train the Trainer (T3) | 52 |
| 3.5.5.1 | T3 Entry Criteria | 52 |
| 3.5.5.2 | T3 Exit Criteria | 53 |
| 3.5.6 | Course Pilot | 53 |
| 3.5.6.1 | Course Pilot Entry Criteria | 54 |
| 3.5.6.2 | Course Pilot Exit Criteria | 54 |
| 3.5.6.3 | Regression Testing Following T3 and Course Pilot Events | 54 |
| 3.5.6.3.1 | Post Pilot GCAT | 55 |
| 3.5.6.3.2 | Post-Pilot Complex Media (VSIM) Regression Test | 55 |
Statement of Work for the FY24 Content Conversion Effort 31 May 2023
Statement of Work for the FY24 Content Conversion Effort 31 May 2023
Table of CONTENTS
Para. Title Page viii
LIST OF TABLES
| Table and Title | Page | |
| Table 1. Rating Classification Requirements | 1 | |
| Table 2. Content Delivery Modes and Media Types | 3 | |
| Table 3. Government Documents | 5 | |
| Table 4. DOD Documents | 6 | |
| Table 5. DON Documents | 7 | |
| Table 6. AIM Documents | 7 | |
| Table 7. Industry Standards | 8 | |
| Table 8. Other Documents | 9 |
Table 9. Photo/Graphic Traceability Cross Reference Matrix
STATEMENT OF WORK (SOW)
FOR RRL FY24 CC
FOR AVIATION TECHNICAIN (AT) AND AIRCREW (AW) RATINGS
1 Scope This Statement of Work (SOW) defines the basic requirements to be performed under this Ready Relevant Learning Content Conversion (RRL CC) Indefinite Delivery/Indefinite Quantity (ID/IQ) contract for Fiscal Year 2024 Content Conversion (FY24CC). The detailed requirements will be defined in this ID/IQ SOW and each specific Delivery Order (DO). This ID/IQ SOW documents the contractor tasks for the design, development, testing, and delivery of products in support of the RRL CC effort using innovative instructional systems design, systems engineering, and training assessment approaches in conjunction with new and modernized technologies to support accession training while simultaneously supporting the broader Sailor 2025 (S2025) overarching goal of improving Sailors’ transfer of training to the operational work environment. The following represents examples of the broader S2025 goals:
a. Modernize and/or improving designated courses through the conversion, development and modification of data, as prescribed by the government, 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).
b. Employing modernized media, instructional, and motivational strategies that are engaging (see Appendices G and I).
In context of RRL, Content Conversion focuses on the instructional design, strategies, media, and content within a given course. The effort requires using Fleet-validated data and designing, developing and delivering improved training products that meet the concepts of innovative instructional systems design and modernized technologies. Content Conversion is far more involved than simply converting existing media from one format to another (e.g., converting PowerPoint or Flash files to HTML5), it includes correcting content errors, developing new content, modernizing and developing new media, and resolving content discrepancies in erroneous data as part of the effort.
This effort requires agile methodologies. The increasing complexity of systems, decentralization of tools and technologies, and rapid pace of change pose challenges in delivering meaningful, secure, and modern capabilities that meet user expectations on time and within budget. In the context of RRL, addressing these challenges requires a significant change in approach to planning, acquiring, and delivering capability to the warfighter. This methodology identifies key focus areas that merit special attention to the NAVAIR mission encompassing “Speed to the Fleet” by:
· Fostering a paradigm shift from a waterfall to an Agile approach in training systems solutions.
· Encouraging incremental approaches to planning, designing and delivering.
· Providing continuous elaboration of requirements and design.
· Expecting daily collaboration between Government and contractor cross-functional teams. In this, Government is embedded as part of the contractor workflow, product backlogs and sprint cycles.
· Developing mutually agreed-upon definition of done for a sprint/release cycle, and metrics informing the Government about the quality of capability developed and delivered allow the Government to continually assess contractor performance toward achieving program outcomes.
· Demonstration of Minimum Viable Products (MVP) to identify capabilities that will be deployed.
Rating Requirements The contractor shall perform tasks for the design, development, testing, and delivery of products for the ratings listed in Table 1 (highest classification of GFI is SECRET).
Table 1. Rating Classification Requirements
| Rating |
| Highest Information Classification |
| Facilities Access Classification |
| When Classification Required |
Aviation Technician (AT)
· Aviation Electronics Technician – Intermediate (ATI)
· Aviation Electronics Technician – Organizational (ATO)
| SECRET |
| SECRET |
| At Contract Award |
Aircrew Ratings
· Naval Aircrewman Mechanical (AWF)
· Naval Aircrewman Helicopter (AWS)
· Naval Aircrewman Operator (AWO)
· Naval Aircrewman – Tactical Helicopter (AWR)
· Naval Aircrewman – Avionics (AWV)
| SECRET |
| SECRET |
| At Contract Award |
Course, Module and Lesson Structure Using the Government provided Functional Requirements Document (FRD), Instructional Performance Requirements Document (IPRD), Instructional Media Requirements Document (IMRD), complex media (e.g., Virtual simulation (VSIM)) fidelity data, and requirements workbook (SOW Appendix A) as a basis, the contractor shall determine the course, module, and lesson structure for each AT and AW rating’s curricula. The contractor shall derive the requirements for the software solutions, design, develop, test, and deliver products meeting the specified requirements.
Content Delivery Modes and Media Types Training products are grouped under two content delivery modes: Instructor-Facilitated Interactive Training (IFIT) and Self-Directed Interactive Training (SDIT) (see Appendices C and F). Table 2 shows the two overarching content delivery modes and a high-level view of associated media types to support the RRL effort, as identified in the requirements workbook and complex media fidelity data.
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”) with “SDIT” and “ILT-CAI” with “IFIT” 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 |
| Actual Equipment |
| X |
| Actual Equipment Trainer |
| X |
| Augmented Reality (AR) |
| X |
| Checklist |
| X |
| X |
| Decision Tables |
| X |
| X |
| Demonstration Animation |
| X |
| X |
| Demonstration Video |
| X |
| X |
| Hybrid Mobile App |
| X |
| X |
| Immersive Virtual Environment (IVE) |
| X |
| X |
Intelligent Tutoring System
X
| Level 1 IMI |
| X |
| X |
| Level 2 IMI |
| X |
| X |
| Level 3 IMI |
| X |
| X |
| Mixed Reality (MR) |
| X |
| Mobile Friendly/Mobile Ready Website |
| X |
| X |
| Mobile Optimized Website |
| X |
| X |
| Native App |
| X |
| X |
| Paper/Paper-based |
| X |
| X |
| Personal Computer (PC) Simulation |
| X |
| X |
| Picture/Diagram |
| X |
| X |
| Responsive Design Website |
| X |
| X |
| Training Aid |
| X |
| X |
| Training Support Material |
| X |
| X |
| Virtual Reality (VR) |
| X |
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., VSIM, Augmented/Mixed/Virtual Reality, or Immersive Virtual Environment) system development (e.g., Government labs, Multipurpose Reconfigurable Training System (MRTS) 3D, PORTS). In such cases, the contractor shall 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 this SOW to include the following Content Conversion appendices to this SOW:
· Appendix A: 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: Risk Assessment Example Format.
· Appendix E: Descriptions of the RRL content delivery modes.
· Appendix F: Operational definitions of engaging instructional strategies to be used in content development under this SOW.
· Appendix G: List of Bloom’s taxonomy action verbs.
· Appendix H: Description of media type characteristics.
Terms and Definitions Appendix C provides the terms and definitions that are critical to this SOW. These terms and definitions supersede any similar terms and definitions that may be found in other sources.
Terms and Definitions Appendix C provides the terms and definitions that are critical to this SOW. These terms and definitions supersede any similar terms and definitions that may be found in other sources.
Government-Furnished Information (GFI) The Government will provide the following on an as-is basis for the ratings:
a. Complex media fidelity data for each rating, as available.
b. IPRD, at DO award.
c. IMRD, at DO award.
d. FRD, at DO award.
e. Initial Training Project Plan (TPP) for each course, at DO award.
f. Initial Training Course Control Document (TCCD), at DO award.
g. Existing Trainee Guides, Lesson Plans, Training Course Control Document (TCCD), Training Project Plan (TPP), Curriculum Outline of Instruction (COI) ) for each rating, as available, at DO award.
h. Access to existing data for each rating in Content Planning Module/Learning Object Module (CPM/LOM), if available, such as existing Trainee Guides, Lesson Plans, TCCD, TPP, COI, NLT 30 days after DO award.
i. Examples of existing courseware, if available, at contract award. (For RRL the Government does not intend to provide all existing IMI or source files as GFI to discourage the contractor from simply copying and pasting content into a different format. The contractor shall plan as though no existing courseware materials are available.)
j. Applicable Style Guides, if available, at contract award. Updates, if available, NLT 30 days after contract award.
k. Technical Publications (e.g., technical manuals), if available, at contract award. Updates, if available, NLT 30 days after contract award.
Government-Furnished Software, Tools, and Equipment The contractor shall request access to the NAWCTSD TRANET-U Virtual Desktop Infrastructure (VDI) 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’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 approved virtual meeting tools, 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 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 |
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
Copies of Defense Intelligence Security Agency (DISA) Configuration Guide can be obtained from http://disa.mil/.
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.
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 5200.39 |
| Critical Program Information (CPI) Identification and Protection Within Research, Development, Test, and Evaluation (RDT&E) dated October 15, 2018 |
| DODI 5200.48 |
| Controlled Unclassified Information (CUI) dated March 6, 2020 |
| 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-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 |
| Copyright, dated 16 Aug 2005 |
| 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 |
| RRLGM #21-0005A |
| RRL Guidance Memorandum, NETC Approved Content Authoring Tools, 26 October 2022 |
| RRLGM #22-0001 |
| Ready Relevant Learning Guidance Memorandum, Implementation of Practical Applications of Learning Science (PALS), 13 May 2022 |
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
Authoring Instructional Materials (AIM) Documents Table 6. 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 7. 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) |
| 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 American National Standards Institute (ANSI)/American Society for Quality Control (ASQC) Standards can be obtained from the (http://www.ansi.org).
Other Documents Table 8. Other Documents
| Document Number |
| Document Title and/or Description |
| CJCSI 6510.01F |
| IA and Computer Network Defense (CND) |
| 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 |
| NETC Common Reference Profile (https://netc.usalearning.net/xapi-library/resources/pdf/NETC-Common-Reference-Profile.pdf) |
| Unnumbered Document |
| NETC E-learning Profile (https://netc.usalearning.net/xapi-library/resources/pdf/NETC-E-learning-Profile.pdf) |
| Unnumbered Document |
| NETC Performance Support Profile (https://netc.usalearning.net/xapi-library/resources/pdf/NETC-Performance-Support-Profile.pdf) |
| Unnumbered Document |
| NETC Simulation Base Profile (https://netc.usalearning.net/xapi-library/resources/pdf/NETC-Simulation-Profile.pdf) |
| Unnumbered Document |
| NETC xAPI Glossary |
(https://netc.usalearning.net/xapi-library/resources/pdf/NETC-xAPI-Glossary.pdf)
| Unnumbered Document |
| NETC xAPI Implementation Guidelines (https://netc.usalearning.net/xapi-library/resources/pdf/NETC-xAPI-Implementation-Guidelines.pdf) |
| Unnumbered Document |
| OPNAV N96, Surface Training Advanced Virtual Environment (STAVE) Interoperability Standard (SIS) Version 2.0, February 2021 (or latest version) |
| Unnumbered Document |
| The Scrum Guide, The Definitive Guide to Scrum: The Rules of the Game, November 2020 (or latest), by Ken Schwaber and Jeff Sutherland |
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.
| 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.
Requirements The contractor shall organize, coordinate, and control RRL content conversion 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.
RRL Content Conversion Planning The contractor shall
a. Identify objectives and constraints of the contract
b. Establish a work breakdown structure based on the system architecture
c. Define achievement criteria for the life cycle stages delivery dates and dependencies on external resources
d. Define roles, responsibilities, accountabilities and authorities
Life-Cycle Model Management The contractor shall define, maintain, and assure availability of policies, life cycle processes, life cycle models, and procedures.
Infrastructure Management The contractor shall provide the infrastructure to support organization and program objectives throughout the life cycle of the contract.
Program Assessment and Control The contractor shall track the status of the program, technical and process performance that ensures the performance is in accordance with the plans and schedules that satisfy the technical objectives.
Program Decision Management The contractor shall
a. Select the most beneficial course of action for the government where alternatives exist
b. Inform the government of decisions encountered
c. Record the decisions and rationale to support future decision-making.
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. The contractor shall:
a. 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.
b. Establish and maintain data libraries via an online management system 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 a secure, web-accessible OMS hosted at the contractor’s location throughout contract/order performance, with the functionality for Government content reviewers and project managers to review, consolidate, and submit deliverable review comments produced by the contractor. The OMS shall serve as a data library consisting of documentation, data, and information used, maintained, updated, and improved for use in this effort. The contractor shall use the OMS as a tool for communication between the contractor and the Government. The contractor’s OMS shall have the functionality to share files between the contractor and the Government reviewers with an intuitive file structure and naming convention, file directories, working files released for Government comment, and final deliverables. The contractor shall maintain deliverables (all versions) and Government comments on the OMS. Reviewers will submit review comments for documents, IMI and supporting materials, and complex media in external files via a comment resolution matrix (CRM). The contractor shall provide an OMS with the following basic characteristics and functionality:
a. Accessible via standard internet browsers supported by NMCI computers.
b. Control access through login and password protection.
c. Traceability of each comment.
The contractor shall also include 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 the OMS available for initial use at the PAC.
Scrum Board Requirements The contractor shall provide browser-based access to its Scrum Board hosted at the contractor’s location. The contractor shall maintain and make visible to the government at all times during the contract performance a current Scrum Board, including at a minimum the product backlog, sprint backlog, increments, and expected government engagement in each sprint. The contractor shall provide a Scrum Board with the following basic characteristics and functionality:
a. Accessible via standard internet browsers supported by NMCI computers.
b. Control access through login and password protection.
Configuration Management (CM) The contractor shall define, document, manage, and apply a CM process. The contractor shall control CM to ensure only files associated with a specific date and location 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.
Contractor Subject Matter Experts (SMEs) The contractor shall employ personnel who are recent technical content SMEs in the AT and AW domain areas with experience in operations and maintenance as required by the rating. The Government requires the contractor to employ Instructional Systems Design and Systems Engineering SMEs 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).
Quality Assurance and Management Plan (QAMP) 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.
Control of Government-Furnished Information (GFI) The contractor shall perform the following tasks to control GFI as part of the quality management process:
a. Examine upon receipt, consistent with practicality, to detect damage.
b. Log receipt and track each GFI item.
c. Provide storage that precludes deterioration.
d. Protect from improper use or disposition.
e. Verify and audit IAW the contractor’s GFI control and management process.
f. Confer with Government at contract closeout whether to return or destroy each GFI item.
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. The contractor shall comply with applicable on-site security regulations related to Government installation and facility access. The contractor shall meet the personnel security clearance requirements for handling classified data and accessing classified spaces (up to SECRET-NOFORN) IAW the DD-254. Contractor personnel shall submit Joint Personnel Adjudication System (JPAS) visit requests to applicable schoolhouse/Learning Center (LC) and will be issued unescorted badges by the schoolhouse/LC for building access. The contractor shall work with the NAWCTSD security representative for issuance of Common Access Cards (CACs). The contractor shall comply with applicable on-site security regulations related to facility access and building access. The contractor shall safeguard U.S. Government controlled unclassified information (CUI) (sensitive information) IAW the contractor’s locally-established Security/Operations Security (OPSEC) Plan (if the contractor already has an established plan). The contractor shall enforce these safeguards throughout the life of the contract including the transport and delivery phases and the disposition and storage of CUI at contract completion.
Operations Security (OPSEC) The contractor shall develop, implement, and maintain an OPSEC program to protect controlled unclassified and classified activities, information, equipment, and material used or developed by the contractor and any subcontractor during performance of the contract. The OPSEC program shall be IAW National Security Decision Directive (NSDD) 298. If the contractor does not have an established OPSEC Plan that addresses the protection of critical information, sensitive, proprietary, or CUI, the Government can provide a template for the contractor’s internal development of an OPSEC Plan. The contractor shall prepare the OPSEC Plan IAW the CDRL B006. Additional OPSEC program planning guidance can be found in DI-MGMT-80934C, OPERATIONS SECURITY (OPSEC) PLAN and NAVAIR OPERATIONS SECURITY (OPSEC) REQUIREMENTS (Annex included with CDRL B006). The OPSEC program, at a minimum, shall include:
a. Assignment of responsibility for OPSEC direction and implementation.
b. Issuance of procedures and planning guidance for the use of OPSEC techniques to identify vulnerabilities and apply applicable countermeasures.
c. Establishment of OPSEC education and awareness training to include Basic OPSEC training, produced by the Interagency OPSEC Support Staff (IOSS), which can be found at https://www.opsecprofessionals.org/articles/onlineopsectraining.html.
d. OPSEC1301 OPSEC Fundamentals.
e. Provisions for management, annual review, and evaluation of OPSEC programs.
f. Flow down of OPSEC requirements to subcontractors when applicable.
Unclassified Contractor-Owned Network Security – Safeguarding of Unclassified Controlled Technical Information The safeguarding of Controlled Unclassified Technical Information applies to prime contractors and their subcontractors (if applicable) for information resident on or transiting through contractor unclassified information systems. The contractor shall provide security to safeguard unclassified controlled technical information on their unclassified information systems from unauthorized access and disclosure. The contractor shall take means (defense-in-depth measures) necessary to protect the confidentiality, integrity, and availability of Government CUI.
a. The contractor shall manage and maintain contractor-owned unclassified IT network assets used to process U.S. Government CUI (sensitive information).
1. The security requirements in National Institute of Standards and Technology (NIST) Special Publication (SP) 800-171, “Protecting Controlled Unclassified Information in Nonfederal Information Systems and Organizations,” http://dx.doi.org/10.6028/NIST.SP.800-171 that is in effect at the time the solicitation is issued or as authorized by the Contracting Officer, as soon as practical, but not dated prior to December 31, 2017. The contractor shall notify the DOD Chief Information Officer (CIO), via email at osd.dibcsia@mail.mil, within 30 days of contract award, of any security requirements specified by NIST SP 800-171 not implemented at the time of contract award; or
2. Alternative but equally effective security measures used to compensate for the inability to satisfy a particular requirement and achieve equivalent protection accepted in writing by an authorized representative of the DOD CIO; and
b. Apply other information systems security measures when the contractor reasonably determines that information systems security measures, in addition to those identified in paragraph (b)(1) of FAR 252.204-7012, may be required to provide adequate security in a dynamic environment based on an assessed risk or vulnerability.
Cyber Incident and Compromise Reporting The contractor shall report to DOD certain cyber incidents that affect unclassified controlled technical information resident on or transiting contractor unclassified information systems set forth IAW the contract clauses. The contractor shall also provide the report to the NAWCTSD Contracting Officer, NAWCTSD Security Manager, and the NAWCTSD Information Systems Security Manager (ISSM).
Access to DOD Installations, Government Information and Information Technology Systems – Personnel Security Background Checks The contractor shall comply with the following:
a. The Common Access Card (CAC) shall be the principal identity credential for supporting interoperable access to DOD installations, facilities, buildings, controlled spaces, and access to U.S. Government information systems. The contractor shall coordinate with the appropriate NAWCTSD TPOC, Government sponsor, and NAWCTSD Security Office Trusted Agents for issuance of the CAC via the Trusted Associate Sponsorship System (TASS) Program. More information for obtaining the CAC can be found at http://www.cac.mil/common-access-card/getting-your-cac/for-contractors/.
b. Contractor personnel whom do not have a security clearance, but require a CAC in performance of their sensitive duties (including access to controlled unclassified information, but not access classified information), shall coordinate with the NAWCTSD Security Office to complete a TIER 1 background investigation, submission of fingerprints and the Standard Form SF-85. The contractor shall submit the Standard Form SF-85 to the NAWCTSD Security Office for processing. There shall be no additional National Agency Check with Local Agency Checks (NACLC)/TIER-3 submissions for contractors holding a valid national security clearance. The Government may issue the credential upon favorable return of the Federal Bureau of Investigations (FBI) fingerprint check, pending final favorable completion of the TIER 1.
c. Access to restricted areas, CUI or Government Information Technology by contractor personnel shall be limited to those individuals who have been determined trustworthy as a result of the favorable completion of a NACLC/TIER-3R or who are under the escort of appropriately cleared personnel. Where escorting such persons is not feasible, a NACLC/TIER 3 shall be conducted and favorably reviewed by the appropriate DOD component, agency, or activity prior to permitting such access. A classified visit, due to content or space, request is required to access SECRET spaces.
d. The contractor shall comply with the cybersecurity and personnel security requirements for accessing U.S. Government IT systems specified in the contract. The contractor shall review and become familiar with the credentialing standards presented in OPM Memorandum for Issuing Personal Identity Verification cards to use as an aid in their employee selection process. The NAWCTSD Security Office will apply the credentialing standards and execute the credentialing process for individual contractors.
Personnel Security – Background Checks Contractor personnel shall undergo the company internal vetting process prior to gaining access to U.S. Government CUI. To comply with immigration law, the contractor shall use the Employment Eligibility Verification Program (E-Verify).
International Traffic and Arms Regulation The contractor shall ensure that foreign persons, as defined under section 120.16 of the International Traffic in Arms Regulation (ITAR) (22 CFR, Parts 120 – 130), are not given access to U.S. Government CUI, sensitive information, defense articles, defense services, or technical data, as defined in the ITAR, Part 120, without proper issuance of an export license from the U.S. Government authority.
Personnel Security – Reporting of Adverse or Derogatory Information Related to Contractors The contractor shall report to the NAWCTSD Security Office adverse or derogatory information pertaining to on-site Contractor Service Support (CSS) personnel (when applicable) or contractor personnel in direct support of this contract. Information reported to the Government Contracting Agency shall be integrated and reported in Contractor Performance Assessment Reporting System (CPARS) on contractor performance of PERsonnel SECurity (PERSEC) related aspects of contractor performance.
a. Adverse or derogatory information reporting of contractor personnel. Example: Domestic Violence arrest; or other violent or sexual crime arrest or self-report.
b. When contractor personnel receive a revocation of an Interim or denial for the issuance of a CAC until final adjudication.
c. When a denial or suspension of clearance occurs for a contractor employee.
d. When contractor employee receives a final denial of eligibility for a security clearance.
Government-Issued Personal…
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 .