2020_CADD Training SOW.pdf

Statement of Work

Provide a 100% web based eLearning solution to provide training in the use of Autodesk Architecture, Engineering, and Construction (AEC) design applications. The eLearning solution must meet or exceed the defined requirements in this Statement of Work (SOW).

Requirements

1. Users

1.1. Contract shall accommodate 1,100 users

1.2. Contract shall provide unlimited access (for each user for the duration of the contract) to eTraining material for all Autodesk software titles and Concepts outlined in 6.2 – Training

Modules

1.3. Contract shall allow for custom training content development to accommodate NAVFAC CADD policies

1.4. Solution must be Section 508 compliant

2. Platform Requirements

2.1. GENERAL PLATFORM REQUIREMENT

2.1.1. The entire eLearning solution web based solution must meet the following requirements:

2.1.1.1. eLearning solution should be fully developed at time of award

2.1.1.2. Must be 100% web based

2.1.1.3. Does NOT require the download and installation of any software or mobile code for the normal operation of the training solution.

2.1.2. The entire eLearning solution vendor owned/managed website must meet the following requirements:

2.1.2.1. Must be delivered utilizing the vendors own web based solution.

2.1.2.2. Must not utilize third party delivery solutions such as YouTube, Facebook, MySpace, etc… for content delivery.

2.1.3. The entire eLearning solution website technology must meet the following requirements:

2.1.3.1. Must use standard HTTP or HTTPS protocols for delivery of eLearning.

2.1.3.2. Must not include any form of tunneling protocol that circumvents/traverses firewall security

2.1.3.3. Must be fully compatible with current versions of Chrome, Edge and Internet

Explorer.

2.1.3.4. Must support Low bandwidths

2.2. PLATFORM SECURITY

2.2.1. All user information must meet the following measures for security:

2.2.1.1. No information pertaining to personally identifiable information (PII) will be gathered

(required) by the platform for access to or use of training solutions.

2.2.1.2. PII includes (but not limited to): Date of Birth (DOB), Social Security Number (SSN), address of personal residence, family information, health information, gender, etc…)

2.2.1.3. User data must remain confidential and is NOT considered public knowledge

2.2.1.3.1. No information gathered or metrics derived from the use of the platform will be divulged to a third party.

2.2.1.3.2. All information gathered by the vendor or the platform is considered For

Official Use Only (FOUO) and must not be sold, traded or disseminated to any third party.

2.3. PLATFORM ACCOUNT MANAGEMENT

2.3.1. All user account types must have the minimum following assigments/permissions:

2.3.1.1. Administrators

2.3.1.1.1. Full client site control (add/remove users, create groups, assign rights, etc…)

2.3.1.1.2. Create groups

2.3.1.1.3. Assign training to groups/users

2.3.1.1.4. Create reports and/or report templates

2.3.1.2. Report Users

2.3.1.2.1. Users with elevated rights to view, download and/or print reports

2.3.1.3. Users

2.3.1.3.1. Access to training modules and groups as assigned

2.3.1.3.2. Can assess training reports for self only

2.4. USER ACCOUNT DATA FIELDS

2.4.1. All user accounts must have the minimum following fields and format:

2.4.1.1. First Name (Text)

2.4.1.2. Last Name (Text)

2.4.1.3. Middle Name (Text)

2.4.1.4. Email (Text)

2.4.1.4.1. Must enforce using USN email address (e.g. must have @navy.mil, @fe.navy.mil)

2.4.1.5. User Name (Text)

2.4.1.5.1. Must be the same as their USN email address

2.4.1.6. Discipline (Text)

2.4.1.6.1. Selection from Pull down menu of standard responses

2.4.1.7. Command (Text)

2.4.1.7.1. Selection from Pull down menu of standard responses

2.4.1.8. Site (Text)

2.4.1.8.1. Selection from Pull down menu of standard responses

2.5. All user groups must meet the following requirements:

2.5.1. Platform must provide Group functionality (ability to create logical groups to organize users)

2.5.2. Must have the ability to assign one or more users to a group

3. Reporting Requirements

3.1. All general reporting measures must meet the following requirements:

3.1.1. Data Lifecycle

3.1.1.1. All usage data must be maintained for the life of the contract

3.1.1.2. At contract completion vendor shall provide Naval Facilities Engineering Command with a complete record of all usage data in a Comma Delineated (CSV) or other open source file format.

3.1.2. Reporting

3.1.2.1. Reporting must be 100% web based

3.1.2.2. Platform must have the ability for NAVFAC to generate pre‐built reports for training use without Vendor interaction.

3.1.2.3. Platform must have Ad‐Hoc report capability

3.1.2.4. Platform must have ability for NAVFAC to export raw data into common data format such as TXT (Text File), CSV (Comma Separate Values), etc… without Vendor interaction.

3.1.2.5. Platform must contain graphical representation of usage data (e.g. pie chart, bar graph, etc…)

3.2. All reporting must meet the following requirements:

3.2.1. All reporting must be Web based

3.2.2. Platform must provide the following reports (either pre‐built or Ad‐Hoc):

3.2.2.1. Usage By Discipline

3.2.2.2. Usage By Command

3.2.2.3. Usage By User

3.2.2.3.1. Courses Completed

3.2.2.4. Usage Over Time (monthly, yearly, etc…)

3.2.2.4.1. By User

3.2.2.4.2. By Command

3.2.2.4.3. By Discipline

3.2.2.5. CEU Reporting

3.2.3. To facilitate producing utilization reports, metrics and report data must be persistent and must not be reset at any interval

3.2.4. All reporting data shall be downloadable to a vendor neutral file format (e.g. CSV, TXT, etc…)

4. Administrative Functionality

4.1. All user account creation must meet the following requirement:

4.1.1. Platform must support the bulk creation of user accounts using a common file format (TXT, CSV, etc…) to upload to platform.

4.2. All user account management must meet the following requirements:

4.2.1. User must be able to reset password (via the website log in page) if forgotten

4.2.2. Vendor and Administrators must be able to reset user passwords

5. Training Module General Requirements

5.1. All unified interface must meet the following requirement:

5.1.1. All training modules must contain the same general features defined here.

5.2. All unified interface requirements must meet the following:

5.2.1. Video Area

5.2.1.1. Must have volume controls

5.2.1.2. Must have Play, Pause, Stop, Advance controls

5.2.1.3. Must have Full Screen option

5.2.2. Index

5.2.2.1. Index must include links to all material for which the indexed word applies

5.2.2.2. Index must be searchable

5.2.2.3. Index must be collapsible

5.2.3. Table of Contents (ToC)

5.2.3.1. ToC must be searchable

5.2.3.2. ToC must be collapsible

5.2.4. Book Marks

5.2.4.1. Platform must support the creation of Bookmarks by the end user that will be persistent.

5.2.4.2. Bookmarks must have ability to be shared between users

5.2.4.3. Platform must support the creation of global bookmarks which will allow administrators to create and share bookmarks with all users

5.2.4.4. Must provide the capability to bookmark videos

5.2.5. Place Holders

5.2.5.1. Platform must support the ability to save a user’s place in the training module

6. Training Content Requirements

6.1. All training components in each module must have the following components:

6.1.1. General Components

6.1.1.1. All training content will include the necessary profiles, GUI configuration files, support files and any other necessary instructions to configure the user’s software to match the training configuration.

6.1.1.2. Must include step by step processes, images and all information necessary to complete the learning objective

6.1.2. Video (pre‐recorded or live)

6.1.2.1. Must have a clear and unobstructed view of the material being covered

6.1.3. Training Material

6.1.3.1. This includes data used for training module (e.g. DWG files, spreadsheets, etc…) and all other user data necessary to complete the training module.

6.2. All training modules must meet the following requirements:

6.2.1. Training modules must include, at a minimum, all of the following software titles:

6.2.1.1. Autodesk AutoCAD 2018 – 2020

6.2.1.2. Autodesk AutoCAD MEP 2018 – 2020

6.2.1.3. Autodesk AutoCAD Civil 3D 2018 – 2020

6.2.1.4. Autodesk AutoCAD Map 3D 2018 – 2020

6.2.1.5. Autodesk AutoCAD Raster Design 2018 – 2020

6.2.1.6. Autodesk Inventor Professional 2018 – 2020

6.2.1.7. Autodesk Revit 2018 – 2020

6.2.1.8. Autodesk Navisworks 2018 – 2020

6.2.1.9. Autodesk Architecture, Engineering & Construction Collection 2018‐2020

6.2.1.9.1. All applications of this suite not already covered in the aforementioned products

6.2.1.10. AutoCAD Based 3D Modeling Concepts and Techniques

6.2.1.11. Revit Based 3D Modeling Concepts and Techniques

6.2.1.12. Building Information Modeling (BIM) Concepts and Techniques

6.2.2. Each training module must include:

6.2.2.1. Migration guides from 2018 through 2020

6.2.2.2. New Feature (What’s New) guide

6.2.2.3. Beginner Level Training

6.2.2.4. Intermediate Level Training

6.2.2.5. Advanced Level Training

6.2.3. Each training module must cover all commands, functions and interface(s)

6.2.3.1. Each command, function and interface must be reflected in the index

6.2.4. Each training module must include a Customization Guide

6.2.4.1. Creation and manipulation GUI elements

6.2.4.2. Creation and use of styles, display systems, object libraries, etc…

7. General Requirements

7.1. Continuing Education Units (CEU)

7.1.1. All training which provide CEU’s must be clearly identified for end users and in tracking data

7.1.2. All training which provide CEU’s must provide proof of completion certificate

7.2. All training support must meet the following requirements:

7.2.1. Vendor must provide training support for the core working hours (0800 to 1700 EST)

7.2.2. Vendor must provide phone support

7.2.2.1. Support must provide live phone support for the core working hours

7.2.2.2. Support must cover all training courses available

7.2.3. Vendor must provide email support

7.2.3.1. Vendor must provide response within 48 working hours of initial contact

7.2.4. Vendor must provide a Knowledge Base

7.2.5. Vendor must provide Feedback and Suggestions

7.2.5.1. Feedback and Suggestions interface must be provided to allow users and administrators to notify vendor of missing content, requested content, etc…

7.3. PRICING MODEL

7.3.1. All pricing models must meet the following requirements:

7.3.1.1. Pricing must be “Per User”

7.3.1.1.1. Per User pricing must grant each paid user account unlimited and unrestricted access to, at a minimum, all training resources outlined section 5.2 – Training

Modules

7.3.1.2. Pricing must not be “per module” or “per usage”

7.3.1.2.1. Per Module describes a pricing model that charges a fee for each training module or class per user.

7.3.1.2.2. Per Usage describes a pricing model that charges a fee for a time unit

(minutes/hours) per user

7.3.1.3. Per User pricing must grant each paid user access to, at a minimum:

7.3.1.3.1. All support features outlined in section 7.2 – Training Support

7.3.1.3.2. Access to all training modules and features in section 6.2 – Training Modules