Draft PWS for EOS Simulator D0012 Requirement.pdf

PERFORMANCE WORK STATEMENT (PWS) FOR

TASK ORDERS ISSUED UNDER THE INDEFINITE

DELIVERY / INDEFINITE QUANTITY (ID/IQ)

CONTRACT FOR

TRAINING SIMULATORS & MOBILE

APPLICATIONS

DEVELOPMENT & MAINTENANCE

FOR THE

U.S. AIR FORCE, EXPEDITIONARY OPERATIONS

SCHOOL (USAF EOS), NJ

Performance Work Statement (PWS)

Name: USAF EOS TRAINING SIMULATORS & MOBILE APPLICATIONS

DEVELOPMENT & MAINTENANCE

Organization: USAF Expeditionary Operations School (USAF EOS)

Address: 5656 Texas Ave Ft Dix, NJ 08640

EXECUTIVE SUMMARY

The USAF Expeditionary Operations School (USAF EOS) is the Air Force’s Center of Excellence for advanced mobility and expeditionary combat support training and education. The school offers in-resident and online web-based training courses, graduating over 32,000 students annually. The USAF EOS provides for America's defense by preparing Airmen to survive and operate as an indispensable partner in support of Combatant Commanders across a Joint, Interagency, Intergovernmental, and Multi-national (JIIM) Environment. The USAF EOS is a selectively manned schoolhouse dedicated to educating Air Force and DoD personnel across the full range of expeditionary knowledge and skills. The USAF EOS provides in-residence and distance learning instruction to include operations, transportation, logistics, contingency response, aircrew management, theater C2, intelligence, resiliency, and field-craft skills. In addition to the training mission, the USAF EOS also gathers, refines and disseminates Combat Support Tactics, Techniques, Procedures and Lessons Learned for the USAF. The USAF EOS Currently possesses 14 training simulators products and 5 mobile applications which cover various aspect of training students across multiple career fields. The USAF EOS is seeking an external vendor to maintain these training products as well as develop new training products in a timely manner to meet mission needs of the US Air Force when new training requirements are requested.

1. PURPOSE

The USAF EOS will be conducting courseware maintenance required to improve the E-learning process. The contractor will be expected to have the capabilities to:

1) Maintain simulator training products and mobile applications software products,

2) As required, provide requested updates to existing products and,

3) Develop simulator training products and mobile phone applications from storyboards created from Instructional System Development (ISD) workshop or project requirement paper.

2. SCOPE

2.1 The purpose of this PWS is to provide support for education and training of designated airmen approved by the Air Force. This non-personal services performance work statement (PWS) provides support maintenance and updates to simulator training products and mobile applications to support for the USAF EOS online education and training mission.

2.2 The simulator training and mobile applications products will be jointly accomplished by the Government and the contractor to meet USAF EOS standards and capable of meeting rapidly changing course objective requirements, per the direction of the course functional manager.

The government takes responsibility and ownership/data rights for simulator training and mobile applications products that is jointly accomplished by the government and the contractor.

2.3 Work under this contract will include updating and maintenance of established simulator training and mobile applications, develop new simulator training products and mobile applications from storyboards created from Instructional System Development (ISD) workshop or requirement paper.

2.4 The contractor may be required to participate in an (ISD) workshops when new storyboard(s) are needed to discuss details to include but not limited to development of simulator training and mobile applications.

3. CONTRACTOR PERSONNEL

The contractor shall employ degreed, professional, technically qualified personnel who possess the necessary experience and knowledge to perform the tasks, meet all technical requirements, and exercise administrative control necessary to meet the requirements outlined in this PWS.

4. REQUIREMENT(S)/DESCRIPTION OF SERVICE(S)

This (PWS) contain the following contractor requirements:

4.1 Qualifications

Possess and provide National Institute of Standards and Technology (NIST) 800-171 compliance. NIST provides a list of controls that support the development of secure and resilient federal information systems. This catalog of security controls allows federal government agencies the recommended security and privacy controls for federal information systems and organizations to protect against cyber-attacks and is required by many DoD and U.S.

Government contracts, in software development.

Possess and provide Capability Maturity Model Integration (CMMI) Level 3 or higher certification. CMMI is a process improvement training and appraisal program and service administered and marketed by Carnegie Mellon University (CMU) and required by many DoD and U.S. Government contracts, in software development.

Contractor must provide documentation on successfully (CMMI) level 3 or higher audit and in good standing since July 14, 2020.

Contractor must provide documentation on National Institute of Standards and Technology (NIST) 800-171 certification and be in compliance since July 14, 2020.

4.2 Possess Subject Matter Expertise

Must possess knowledge and have previous subject matter experience producing Simulators & AF Mobile Applications for the following process areas for the US Air Force (this subject matter expertise will reduce development time);

1. Air Force Command operations/logistics,

2. Aircraft Operations,

3. Cargo and Transportation and

4. Command and Control-C2

Interface with government provided Subject Matter Experts (SMEs) through email, phone or meetings to meet updating requirements and ensure courseware is meeting training objectives and development timelines.

Must possess staff with knowledge and have previous subject matter experience developing simulator training from referencing Air Force Technical Orders regarding all aircraft in the Air Force inventory.

Contractor must provide prior produced simulators training and mobile applications products produced within last (3 years) in any of the (1-4) Air Force process areas identified above to qualify for SME experience. Sample products can be provided through web link access or provided in zip file format.

4.3 Possess Instruction System Development (ISD) Expertise

Must be knowledgeable with designing training applications using the Air Force Instructional System Development (ISD) process (AFM 36-2235 volumes 1-10) or Analysis, Design, Development, Implementation, and Evaluation (ADDIE) model.

Utilize AF ISD processes to create training products, with interactive scenarios, assessment quizzes and performance activities with subject matter experts from the field during workshops or training enhancement request.

If required, attend/facilitate ISD workshops at government facility or contractor location to review and collect source information provided by government provided Subject Matter Experts (SMEs).

Contractor must provide documentation to validate ISD expertise for technical evaluation which must include:

1. (1) Simulator development document identifying product requirements from workshop identifying (training/product objective, samples of behavior(s) and build description of each simulator scenario requirement along with identified reference sources)

2. (1) Simulator Storyboard for (2) scenarios identifying (curriculum text content of each scenario, decision tree with selection feedback response, voice over statements, supporting graphics, reference resources and developer notes).

3. (1) Mobile Application development document identifying outline of requirements from workshop that identifies (training/product objective build description for each for mobile application area requirement, with supporting graphics and reference resources and developer notes)

4.4 Possess Technical Support and Expertise

Develop/update simulator training and mobile applications products listed in (Par 6.1.2) “Existing Simulator Training Products and Mobile Applications Listing” with Commercial Off-The-Shelf (COTS) software.

Possess minimum (5 years) experience on creating/setting up scenario-based learning simulators, performance assessment test, setting up simulators by utilizing the built-in functionality on the Moodle Learning Management System and creating/setting up and meeting platform requirements for mobile application products.

Possess minimum (5 years) experience troubleshooting and manually updating SCORM packages that will interface with LMS operations, PC desktop, and experience with troubleshooting mobile application products hosted on Apple or Google Play store or DOD mobile application platform.

Possess minimum (5 years) experience and have licensed copies or access to the following programming/coding software; Unity Pro, Storyline, CSS, JavaScript, JSON, JQuery - Voodoo magic, C#, Playmaker, NGUI, Dialoguer, Visual Studios, JetBrains.

Possess minimum (5 years) experience and have licensed copies or access to the following graphic/audio software; 3DS Max/Maya, Algorithmic Substance, Adobe Premiere/After Effects, Adobe Audition, Adobe Photoshop.

Produce/update media production resources for courseware creation to include: digital photography, graphic artwork, video production, HTML5 animation and sound.

Update/develop courseware to have the ability to: read text content from a data file, integrate multiple media types on a single screen, interact with the Learning Management System (LMS) software, and properly function when integrated in various combinations.

Establish version control for product configuration management.

Update/develop courseware standardized template to match the look and operation of existing products.

Provide and develop all modules and scenario development material to include storyboards (Par 6.2.1) for newly developed products.

Provide government access to contractor provided LMS for operational and update quality check for any updated or developed scenario training products prior to delivery.

Contactor must provide written statement that you possess or have access to licensed copies of the required software products and possess (5 years) experience with the use of such software.

Contactor must provide written statement of possess (5 years) experience troubleshooting and manually updating SCORM packages that will interface with Moodle LMS operations, PC desktop, and mobile application device requirements.

4.5 Meet Required Design, Operational and Government Requirements Prior produced simulator training and mobile applications products within last (3 years) in subject matter areas identified in (par 4.2) must be submitted for evaluation to qualify meeting design requirements.

Provided sample products to validate meeting design requirements in all sub paragraphs below (4.5.1 – 4.5.5).

4.5.1 Training Simulator Design Requirements

Training simulator interactions to be designed up to the level four of high interactions level.

Courseware updates and developed courses must pass functional testing and meet all system operations requirements per established standard identified below.

• Scenario Outline Matches ISD Design or Requirement Document

• Identifies Training Objectives

• Build in Module or Scenario(s) Format

• Multiple Activity-Based (exercises)

• Voice narration with support text content for hearing impaired (508 requirement)

• Navigation that allows multiple paths with appropriate feedback

• Must operate at level (3) or (4) courseware development standards to include the use of avatars, interactive 3D objects

• Has functions with Glossary and Resources

• Tracks Student Progress (bookmarking at each scenario level)

• Final Performance Assessment with feedback and score tracking (may require password to access)

Contactor must be able to provide sample(s) of previous AF developed simulator product(s) in any of the subject matter areas identified in (par 4.2) for technical evaluation. Provided sample(s) must meet all identified design requirements above.

Definitions for each interaction level of development can be found at:

https://community.articulate.com/articles/get-to-know-the-3-levels-of-e-learning https://community.articulate.com/articles/get-to-know-the-3-levels-of-e-learning

4.5.2 Training Simulator PC/Online Product Operation Requirements

• Operate using USAF Standard Desktop Configuration

• Operate in Edge browser v44, Chrome v84, Firefox v68 or higher

• PC-Compatible computer/Laptop

• Intel® Core™ i7-6700HQ CPU @ 2.60GHz or Above

• 32G RAM or greater (Windows 10)

• Graphics card 64-bit color or greater

• 64 Bit or compatible sound card (if sound is required)

• 1Gbps Broadband internet access or higher

• Unity WebGLv1.0 or higher (http://unity3d.com)

• Screen Resolution: 1020 x 800 pixels

• Color Display: 256/32 bit or higher

• For product placement on Air Force LMS (Moodle Cloud based LMS) be SCORM 1.2 or

2004 compliant

4.5.3 Mobile Application Design Requirements

Mobile applications will be hosted on Apple or Google Play store or DOD mobile application platform and will need to meet all platform hosting requirements. Contractor will use developer owned accounts to publish mobile applications to both Apple and Google Play store platforms.

• Mobile application Matches ISD Design or Requirement Document

• Identifies Application Use Objective

• Build with Standard Application Format Design

• Provides Navigation/Glossary/Resources functionality

Contactor must be able to provide sample(s) of previous AF developed Mobile Application product(s) in subject matter areas identified in (par 4.2) for technical evaluation. Provided Mobile Application must meet identified design requirements identified above.

4.5.4 Mobile Application Product Operation Requirements

iOS devices requirements iOS 8.0 or higher and be compatible with the following:

• iPhone 5S or later

• iPad Air or iPad Air 2

• iPad Mini 2 or later

• iPad Pro (1st generation) or later

• iPad (5th generation) or later

• iPod touch (6th generation)

Android device requirements

• Operate on Android 5.0 or higher devices

4.5.5 Meet Standard Coding and Government Requirements

Update simulator products and mobile applications as outlined in (Par 6.1.2) “Existing Simulator Training Products and Mobile Applications Listing” that will interface with Moodle LMS operations using SCORM 1.2 and 2004 standards or operate independently on government PC standard desktop configuration. Mobile applications will operate on personal or government owned devices that have access to download and operate downloaded applications from the platform.

Meet or exceed OPM policies for Training and Development Requirements http://www.opm.gov/policy-data-oversight/training-and-development

Meet or exceed section 508 standard design requirements when developing training products https://www.section508.gov/training/

Provide final products and updates with version control to government (Par 10.3).

Update interactive courseware per the requirements established in the update requirement documentation.

Contactor provided sample(s) will be evaluated on meeting section 508 standard design requirements.

4.6 Skilled Labor Hour Category Duties

Project Manager The contractor shall establish and provide a qualified workforce capable of performing the required tasks. The workforce shall include a project/project manager who will oversee all aspects of the requirement. The contractor shall establish and use key performance parameters to monitor work performance, measure results, ensure delivery of contracted product deliverables and solutions, support management and decision-making and facilitate communications. The contractor shall identify risks, resolve problems and verify effectiveness of corrective actions. The contractor shall institute and maintain a process that ensures problems and action items discussed with the Government are tracked through resolution and shall provide timely status reporting during weekly meetings. Results of contractor actions taken to improve performance shall be tracked and lessons learned incorporated into applicable processes. The contractor shall establish and maintain a documented set of disciplined, mature and continuously improving processes for administering all contract and requirement efforts with an emphasis on cost-efficiency, schedule, performance, responsiveness and consistently high-quality delivery. The contractor shall provide transition in and transition out plans as required.

Qualifications: Possess or currently obtaining a PMP certification, have a degree bachelor’s with business project management accreditation, experience with leading and directing projects, participates in ongoing professional development and have excellent communication skills.

Duties: Shall be responsible for the performance of the work under this contract. The name of this person and alternate(s) shall be designated in writing to the CO upon initial assignment and whenever a change in personnel is made.

http://www.opm.gov/policy-data-oversight/training-and-development https://www.section508.gov/training/

Have full authority for the contractor and all contractor employees on all matters relating to daily operation of the contract.

If on leave or off station, designate an alternate who is on station and who can assume his/her duties. In this case, the Program Manager will notify the COR.

Ensure government-provided student feedback tools are used in accordance with Expeditionary Operations School established policies and procedures.

Coordinate academic activities with the Dean of Academics, Unit Commander, Director of Operations, Course Director, and COR, and other organizations and customers as appropriate.

Make recommendations to COR on all matters relating to efficient and effective operations of the training.

Application Developer/Programmer Minimum Qualifications: Possesses a bachelor's degree. 1-3 years of related experience as developer/programmer.

Duties: Designs procedures to solve complex application programming problems, taking computer equipment capacity and limitations, operating time, and form of desired results into consideration. Oversees the development or modification of applications programs. Leads all phases of applications programming. Designs, codes, tests, debugs, and documents applications at the highest levels of complexity. Evaluates applications for quality assurance.

Curriculum Designer Manager Minimum Qualifications: Possesses a bachelor's degree. Typically requires 5 years’ experience in the related area as an individual contributor. 1 - 3 years supervisory experience required. Extensive knowledge of the function and department processes.

Duties: Manages the design of training programs, including classroom lectures, online courses, and self-study sessions, directed at employees, organization members, or those who use the organization's products or services. Oversees team of specialists to ensure training and learning needs are addressed in accordance with policy and strategy.

Graphic Designer Minimum Qualifications: Possesses a bachelor's degree. Must remain abreast of technological advances in the field and be able to identify areas of use in the organization.

Requires 4 to 7 years of related experience.

Duties: Generates and manipulates graphic images, animations, sound, text and video into consolidated and seamless multimedia programs. Uses knowledge of current graphic design software to produce graphic art and visual materials for promotions, advertisements, films, packaging, and informative and instructional material through a variety of media outlets such as websites and CD-ROMs.

Audio Visual Specialist Minimum Qualifications: Possesses an associate's degree. Requires 1-3 years of related experience or additional training, or certification.

Duties: responsibilities include setting up and adjusting audio-visual equipment, performing routine maintenance, creating and editing audio files, or tapes. Works with producers/directors on design, testing, installation and positioning of equipment and props for live events or meetings.

5. PERFORMANCE REQUIREMENTS

5.1 Contractor Management

The Contractor shall perform continual management of the functional areas contained within this PWS and shall provide a Project Manager physically present at the Contractor location during normal duty hours. The Project Manager shall conduct overall management coordination and shall be the central point of contact (POC) with USAF EC for performance of all work under this PWS. A Contractor employee shall be designated to act for the Project Manager when work is being performed outside of duty hours, or during the Project Manager’s absence. Both the Project Manager and the Contractor employee filling in for the Project Manager, shall have full authority to act for the contractor on all Contract matters relating to daily operation of this contract.

5.2 Contractor Responsiveness

The Project Manager or designated alternate shall make reasonable attempts to be available for telephone communication or site attendance, with the government POC during the hours of 0730 to 16:30 hrs Eastern Standard Time Monday through Friday on normal Contractor workdays. A personal answering service is permitted during other than normal Contractor workdays and work hours for receipt of calls with a response time that is as soon as is reasonably practical, or by the next normal Contractor workday.

6. DELIVERABLES

Deliverables include the following as needed.

1) Make updates to existing simulator training products and mobile applications or convert products to higher versions of development software as required and meet all requirements in (Para 6.1) and sub paragraphs

2) Produce new simulator training products and mobile applications and meet all requirements in (Para 6.2) and sub paragraphs

3) Meet all design, operational and government requirements in (Par 4.5 and sub paragraphs)

6.1 Updates Existing Simulators and Mobile Applications

Perform Updates/ Enhancements/ Critical Bug Fixes as requested by the government on existing courseware. The government will provide detailed descriptions, source documents, and desired outcomes for the requirements for contractor to provide a Rough Order of Magnitude (ROM) estimate, for price and schedule, for requested services as outline in the weekly status meetings. The contractor will provide ROMs for all work requested. ROM to include all detailed descriptions, source documents, meetings with SMEs, desired outcomes for the requirements and itemized price breakout by CLIN. ROMs are valid for 60-days; contractor can extend ROM with valid explanation/reasoning. Once the ROM is approved, a task order has been created and work has started, any work that is out-of-scope from the original effort, must be incorporated into a new ROM and provided to the COR for approval prior to the out-of-scope work starting.

Actions related to maintaining and upgrading the courseware include but are not limited to the addition of:

1) Add new reference sources or changes to scenario or application processes

2) Add New or updating equipment or avatar personnel with current apparel

3) Replace curriculum or (media) with new/updated material

4) Add scenario or other operation features into training or mobile application

5) Correct operation capabilities in training to operate correctly on LMS or convert products to higher versions of development software

6.1.1 Update Timeline Requirement

Meet required timeline established by Multi-functional team for updates based on identified status of changes by government. Contractor production time requirements are established from COR’s initial email request and are capitalized into contractor’s corresponding ROM for price and schedule. Contractor shall coordinate its efforts to ensure that any concurrent work meets schedule requirements. . Average workload will usually fall between workload of 3 to 5 project per month. Any additional work required by the contractor that exceeds the delivery time outlined in the original quote must be provided to the COR and approved prior to the additional work starting or being invoiced.

6.1.2 Existing Simulator Training Products and Mobile Applications Listing

(This listing is not all inclusive and may change due to course attrition or deletion)

Simulator Training Products

1 C-17 & C5 Aerial Port Expeditor Simulator, 2 Joint Inspection Simulator, 3 Airlift Planner Simulator, 4 Installation Deployment Officer Simulator, 5 AMC Command and Control Simulator, 6 Tanker Airlift Control Center (618th AOC) Simulator, 7 Pallet Build-up Simulator, 8 Aircraft Maintenance Course & Status Simulator, 9 Air Terminal Operations Center Simulator, 10 Passenger Service Center Simulator, 11 M1 & M2 Unit Deployment Manager Course and Simulator, 12 Aircraft Maintenance Production (MAF, CAF & GSC) Simulator, 13 SARMS Simulator, 14 AF Missile Status Simulator

Mobile Applications

Existing training product/project service update request based on status set by COR on needs of mission requirement.

High Status Request 7-14 business days completion (after ROM /approved, and task order issuance.

Medium Status Request 15-30 business days completion, (after ROM is approved and task order issuance.

Low Status Request 31-60 business days completion, (after ROM is approved, and task order issuance.

1 Mobile Applications -Cargo Restraint, 2 Mobile Applications -Center of Balance, 3 Mobile Applications -Unit Deployment Manager, 4 Mobile Applications -Airman’s Manual, 5 Mobile Applications –Joint Inspection Reference Pocket Guide

6.2 New Simulator Training Product and Mobile Application Development

6.2.1 New Simulator Training Product (Storyboards)

The contractor shall support the design and development of systems and applications and their integration into the overarching enterprise architecture. The contractor shall provide all required design and development documents, and supporting architectural documentation, for any frameworks as identified in this PWS. See AFH 36-2235 V5 pg. 272 for further guidance.

6.2.2 System Performance Testing

The Contractor shall deliver several major document or software releases throughout the development phases for approval as detail in the weekly meetings. A description of each release is listed in Par 6.2.5 through 6.2.9 below. The Contractor shall supply all releases on the Internet for evaluation. All source files used to develop training on (COTS) software to include story boards, and source support media such as videos and graphics shall be provided to the Government at contract completion.

6.2.3 Interim Deliveries during Development

The Contractor shall design and develop the course modules, as defined in the ISD workshop or as provided to them by the COR. The Contractor shall provide an initial “on-line” draft of each course module for Government review, including all course content, graphics, exercises, test questions, and remedial content for government review.

The Contractor shall provide the Government with access to the Contractor’s server so that the Government can review the draft products, as they will appear over the Internet within an existing LMS or system to allow full functionality of product operation. The Contractor shall incorporate into the final course all corrections or updates provided by the Government during this “on-line” review.

6.2.4 Meet Priority and Delivery Schedule

Provide training development storyboards design documents within 30 days after ISD workshop or after material is provided by the COR.

Provide access to project management web site for courseware development and maintenance update tracking.

Incorporate government recommendations to the design documents within 5-15 workdays of receipt from government.

Meet product development milestone dates established in design document No Later Than (NLT) 7 days past (i) established deadlines in design document, (ii) initial Milestone or Alpha deliverable, or (iii) final delivery NLT 6 months after initial ISD workshop for each project, for whichever of (i), (ii), or (iii) is best applicable to the circumstance.

Deliver final courseware files via (Contractor or Government) secure File Transfer Protocol (FTP) system.

Fix identified programming/product errors within 7-14 days after being identified by the government during the initial testing review period of 60 calendar days after delivery.

6.2.5 Design Document Release

When developing new training courseware the design document (story boards IAW AFH 36- 2235 V5 pg 272) shall contain a listing of program features, functionality and user interaction algorithms along with the technical approach to convert the existing course/application content to electronic form. All major components and overall product architecture shall be defined. Alfa, Beta and final software release dates shall be established based on time to fully develop courseware. The design document will also include milestone dates for completion of training product.

6.2.6 Alpha Software Release

The alpha software is a complete working version of the courseware program with sample content loaded into at least one program area. The menu system shall contain final graphical artwork, buttons and hyper-links. Sample content can be evaluated for usability prior to formatting the remainder of the content for import into the training product. Content will be evaluated until product meeting requirements as outlined during the weekly meeting. Preferred platform for product evaluation shall be on the Contractor’s web site.

6.2.7 Beta Software Release

The beta software release is the final test version of the product. The beta software release contains no known errors or omissions with the exception of final narration audio, which shall be imported after any required beta release changes are incorporated. The beta release shall contain the full functionality of the design document with final content loaded into each program area. After evaluation of the beta software release by the COR and SMEs per established milestones, the Contractor shall meet with personnel to resolve any software abnormalities or non-conformance with the design document or operation requirements (Par 4.5 through 4.5.8).

6.2.8 Final Software Release

The final software release is the finished product ready for duplication and release to the user base. It contains no known errors or omissions and conforms to the design document and any agreed upon changes that resulted from the beta software release evaluation.

6.2.9 Voice Narration Final Release (If Required)

The final simulator product release shall include created high quality digital voice with artificial voice software (sounds exactly like human speech) or professional voice talent narration.

Currently all voice narration shall be in English.

6.3 Data Deliverables Review

The Government reserves the right to review all data deliverables for a period of 60 working days upon receipt of final version of course files through FTP delivery process. No data deliverable will be assumed to be accepted by the Government until the 60-day period has passed, unless the Government explicitly states otherwise. If required, assist with loading final products on Government-hosted LMS or mobile application platforms.

Sequence Number

Data Item Description

Title

A016 DI-ILSS-80872 Training Materials

A021 DI-IPSC-81427A Software Development Plan (SDP)

A040 DI-IPSC-81488 Computer Software Product

A048 DI-MGMT-80227 Contractor's Progress, Status and Management Report

The Government requires all deliverables that include Scientific and Technical Information (STINFO), as determined by the Government, be properly marked IAW DoD Directive 5230.24 and AFI 61-204 prior to initial coordination or final delivery. Failure to mark deliverables as instructed by the Government will result in non-compliance and non-acceptance of the deliverable. The contractor shall include the proper markings on any deliverable deemed STINFO regardless of media type, stage of completeness or method of distribution. Therefore, even draft documents containing STINFO and STINFO sent via e-mail require correct markings.

Additionally, as required by individual Task/Delivery Orders, the contractor shall formally deliver as a CDRL all intellectual property, software, licensing, physical records, files, documents, working papers and other data for which the Government shall treat as deliverable

7. MEETINGS

The Contractor shall attend, participate in, and furnish input during:

7.1 Weekly status meetings

The weekly meetings will include, but not limited to all milestones, comment and review areas on new courseware development or update maintenance requirements.

7.2 Quarterly status meetings

The quarterly (in progress review) meetings will outline the work accomplished during the last quarter period and problems encountered/anticipated on each training product.

Meeting attendees shall at times include Contractor managerial, supervisory, and other personnel knowledgeable of the subject matter.

8. TRANSFERRING TRAINING PRODUCT FILES

Files will be transfer to the Contracting Officer Representative (COR) through the Department of Defense Secure Exchange File Exchange (SAFE).

9. CONTRACT PROCESS

9.1 Task Orders. Contracting Officer Representative (COR) will assign project requirements as needed and perform monthly verification of services performed for each task order NLT 10 working days after 1st of each month for contractor payment.

9.2 Travel

Three to five ISD design meetings may be held at the Government facility or Contractor facility or through a teleconference review process on an annual basis. A joint decision will determine which avenue would be appropriate for each project. Contractor personnel may be required to travel in performance of assigned functions consistent with the scope of this PWS. The contractor shall coordinate with the Course Director and submit a request for travel to the CO identifying the purpose, location, dates, personnel (name and title) needed for the travel, and an estimate of total cost(s) to the government (General and Administration expenses should not be included). It will not be unusual for the government to require the contractor to travel on short notice.

Costs for transportation may be based upon mileage rates, actual costs incurred, or a combination thereof, provided the method used results in a reasonable charge. Travel costs will be considered reasonable and allowable only to the extent that they do not exceed, on a daily basis, the maximum per diem rates in effect at the time of the travel.

Travel will be a cost reimbursable item IAW FAR 31.205-46 and Joint Travel Regulations (JTR) Vol. II, Appendix D, Part III. Five days after completion of travel, the contractor shall submit an invoice via Wide Areas Work Flow (WAWF) with a detailed breakdown of reimbursable travel costs incurred and receipts for all expenses of $75.00 or more.

The Joint Travel Regulations (JTR), while not wholly applicable to Contractors, shall provide the basis for the determination as to what is reasonable and allowable. Maximum use is to be made of the lowest available customary standard coach or equivalent airfare accommodations available during normal business hours. All necessary travel meeting the above criteria shall be approved in advance by the Contracting Officer. Exceptions to these guidelines shall be approved in advance by the Contracting Officer. Additional travel may be required for the optional tasks and will be approved and funded as required via Technical Direction Letters.

Travel will only be allowed for new course development.

If any travel arrangements cause additional costs to the requirement that exceed those previously negotiated, written approval by CO is required, prior to undertaking such travel.

Costs associated with contractor travel shall be in accordance with FAR Part 31.205-46, Travel Costs. The contractor shall travel using the lower cost mode transportation commensurate with the mission requirements. When necessary to use air travel, the contractor shall use economy class or similar accommodations to the extent they are available and commensurate with the mission requirements. Travel will be reimbursed on a cost reimbursable basis; no profit or fee will be paid.

9.3 Place of Performance The place of performance shall be performed at the contractor location. Travel to Government facilities may be required at the request of the Contract Officer Representative (COR). The contractor may be requested by the (COR) to perform work at the (Government) site if the need arises such as attending ISD design meetings to initiate the development of courseware. The contractor may also be provided access to government learning management system (Moodle) to build or load course content.

9.4 Billable Amounts

In order for amounts to be billed, deliverable services must have been requested by the COR and performed in direct support of a requirement in the PWS. In the course of business, situations may arise where Government facilities may not be available for performance of the PWS requirements (i.e., base closure due to weather, Force Protection conditions, etc.). When the base is officially closed no contractor services will be provided and no charges will be incurred and/or billed. Contractor employees shall not be directed to attend such events by the Government. Since a contract employee is not a government employee, the contract employee cannot be granted the same duty time activities as Government employees. Participation in such events is not billable and contractor employee participation should be IAW the employees’ company’s policies and compensation system.

The contractor will provide the government with a percentage-complete on requested monthly work performed, based on the ROMs provided and/or approved, broken down by project.

Government will be invoiced monthly for routine maintenance performed by the task order.

For non-routine service requests approved through a ROM may be invoiced on a monthly basis.

Invoices shall be accompanied by an approved ROM and a percentage complete for the month invoiced.

Tasking Procedure:

a. For each App/Project needed, the Government will issue a Task Order Request (TOR) for ROM Price and Schedule

b. Contractor will provide a ROM for pricing and timing purposes, in response to the TOR.

c. If the TOR’s ROM is approved by the Government, the Government will issue a Task

Order (TO) for that App/Project, in the amount, and for the schedule, as provided in the corresponding ROM.

d. Contractor will report on each TO with percentage complete, schedule, program issues, etc.

e. Contractor will invoice the total fixed price of each TO, by invoicing on a monthly basis for the period of performance for each TO, in approximately equal monthly amounts.

f. All TOs, when summed together, would need to remain within the corresponding ceiling Value and Funding, for the IDIQ Period of Performance to which the TOs apply, and the Contractor will provide a chart in the Monthly Report to demonstrate this.

9.5 Contractor Identification

When granted access to attending any ISD workshop at the government facility by the COR all contractor/subcontractor personnel shall be required to wear AF-approved or provided picture identification badges so as to distinguish themselves from Government employees. When conversing with Government personnel during business meetings, over the telephone or via electronic mail, contractor/subcontractor personnel shall identify themselves as such to avoid situations arising where sensitive topics might be better discussed solely between Government employees. Contractors/subcontractors shall identify themselves on any attendance sheet or any coordination documents they may review. Electronic mail signature blocks shall identify their company affiliation. Where practicable, contractor/subcontractors occupying collocated space with their Government program customer should identify their work space area with their name and company affiliation.

9.6 Base Access

If the contractor does not possess a facility clearance the government will request one. The COR will be the point of contact for base access.

9.6.1 Pass and Identification Items

The contractor shall ensure the following identification items as required for contract performance are obtained for employees:

1) DoD Common Access Card (AFI 36-3026).

2) Base-specific identification as required by local base and/or building security policies.

3) Failure to return all government issued identification upon termination of contract or service, termination of employees or expiration of the identification may result in withholding of final payment.

9.6.2 Computer and Network Access Requirements

Contractor personnel working on this contract must be designated in one of the below AIS positions and complete the required security investigation to obtain the required security clearance. This must be accomplished before operating government furnished computer workstations or systems that have access to Air Force e-mail systems or computer systems that access classified information. The contractor shall comply with the DoD 5200.2-R, Personnel Security Program and AFMAN 33-152, User Responsibilities and Guidance for Information Systems, requirements. (Please check one):

( X ) AIS-II Position - Noncritical-Sensitive Positions. Security Clearance:

UNCLASSIFIED

based on a NACLC/ANACI background investigation. Responsibility for systems design, operation, testing, maintenance and/or monitoring that is carried out under technical review of higher authority in the AIS-I category, includes, but is not limited to; access to and/or processing of proprietary data, information requiring protection under the Privacy Act of 18 1974 and Government-developed privileged information involving the award of.

( ) AIS-III Position - Nonsensitive Positions. No security clearance required but is a

Trusted Position based on a favorable NACI background investigation. All other positions involved in U.S. Government computer activities.

9.6.3 Reporting Requirements

The contractor shall comply with requirements from AFI 71-101, Volume-1 and Criminal Investigations, and Volume-2 Protective Service Matters. Contractor personnel shall report to an appropriate authority any information or circumstances of which they are aware may pose a threat to the security of DoD personnel, contractor personnel, resources and classified or unclassified defense information. Contractor employees shall be briefed by their immediate supervisor upon initial on-base assignment and as required thereafter.

9.6.4 Physical Security

Contractor employees shall comply with base Operations Plans/instructions for FPCON procedures, Random Antiterrorism Measures (RAMS) and Operation Security (OPSEC), Emergency Management (EM) and local search/identification requirements. The contractor shall safeguard all government property including controlled forms provided for contractor use.

At the close of each work period, government training equipment, facilities, support equipment and other valuable materials shall be secured.

9.6.5 Wireless Electronic Devices

The following devices are not allowed in areas where classified information is discussed, briefed or processed: cell phones, camera cell phones, cordless telephones, wireless microphones, wireless keyboards, wireless mice, wireless or Infrared Local Area Networks (LANs). The term “Area” above refers to a room and/or to a space the size of a 3-meter radius sphere, centering on the classified source. In areas where classified information is discussed, briefed or processed, wireless pointer/mice devices are allowed for presentations only. This is an acceptable EMSEC risk. All other Personal Electronic Devices, PEDs. All other wireless PEDs not specifically addressed above, that are used for storing, processing and/or transmitting information shall not be operated in areas where classified information is electronically stored, processed or transmitted.

9.6.6 Operating Instructions

The contractor will adhere to the all Air Force activity Operating Instructions (OI) and local Security Program Management for internal circulation control, protection of resources and to regulate entry into Air Force controlled areas during normal, simulated and actual emergency operations to include local written OIs.

9.6.7 Government Authorization

The contractor shall ensure its employees do not allow government issued keys to be used by personnel other than current authorized contractor employees. Contractor employees shall not use keys to open work areas for personnel other than contractor employees engaged in performance of duties, unless authorized by the government functional director.

9.6.8 Access Lock Combinations

Access lock combinations are “For Official Use Only” and will be protected from disclosure to unauthorized personnel. The contractor will adhere to the Air Force activity operating instructions ensuring lock combinations are not revealed to un-cleared /unauthorized persons and ensure the safeguard procedures are implemented. The contractor is not authorized to record lock combinations without written approval by the government functional director.

9.6.9 Security Combinations

Combinations to security containers, secure rooms or vaults are classified information and must be properly safeguarded. Only contractor employees, who have the proper security clearance and the need-to-know, will be given combinations to security containers, secure rooms or vaults.

Contractor employees are responsible for properly safeguarding combinations. Contractor employees will not record security containers, secure rooms or vaults combinations without written approval by the government functional director. Contractors will not change combinations to security containers, secure rooms or vaults without written approval by the security officer and the government functional director.

9.6.10 Security Alarm Access Codes

Security alarm access codes are “For Official Use Only” and will be protected from unauthorized personnel. Security alarm access codes will be given to contractor employees who require entry into areas with security alarms. Contractor employees will adhere to the Air Force activity operating instructions and will properly safeguard alarm access codes to prevent unauthorized disclosure. Contractors will not record alarm access codes without written approval by the government functional director.

9.6.11 Freedom of Information Act Program (FOIA)

The contractor shall comply with DoD Regulation 5400.7-R/Air Force Supplement, DoD Freedom of Information Act Program, requirements. The regulation sets policy and procedures for the disclosure of records to the public and for marking, handling, transmitting and safeguarding for Official Use Only (FOUO) material. The contractor shall comply with AFI 33- 332, Air Force Privacy Act Program, when collecting and maintaining information protected by the Privacy Act of 1974 authorized by Title 10, United States Code, Section 8013. The contractor shall maintain records in accordance with Air Force manual (AFMAN) 33-363, Management of Records; and disposed of in accordance with Air Force Records Information Management System (AFRIMS) Records Disposition Schedule (RDS) located at https://www.my.af.mil/gcss-af61a/afrims/afrims/.

9.6.12 Traffic Laws

The contractor and their employees shall comply with all installation traffic regulations.

9.6.13 Cellular Phone Operation Policy

The contractor shall comply with local base policies regarding cellular phone operation.

9.6.14 Security Education and Training

The contractors are required to participate in the government’s in-house and web-based security training program under the terms of the contract. The government will provide the contractor with access to the on-line system. Annually, all contractors will complete all required security training. Required annual training includes, Force Protection (FP), Information Protection (IP), Cybersecurity and OPSEC. If contract team members will be using the SIPRNet, users will also have to comply with the organizational Derivative Classification Training as a condition of access.

9.6.15 Standards of Performance

9.6.15.1 The contractor shall not employ persons for work on this contract if such employee is identified to the contractor by the Contracting Officer (CO) as a potential threat to the health, safety, security, general well-being, or operational mission of the installation and its population.

9.6.15.2 Contractor employees shall wear appropriate attire with the contractor’s name/picture badge, or USAF issued civilian ID with employee’s and contractor’s name. Contractor employees may remove their ID if participating in instruction requiring physical activity.

9.6.15.3 The contractor shall not employ any person who is an employee of the U.S.

Government if employing that person would create a conflict of interest.

9.6.15.4 Contractors will comply with CCAF and EC-established Policies on Professional and Unprofessional Relationships and will take immediate action to resolve violations of the prohibition on unprofessional relationships.

9.6.15.5 Unprofessional relationships include relationships involving faculty, staff, and students.

Whether pursued on or off duty relationships are unprofessional when they detract from the authority of superiors or result in (or reasonably create the appearance of) favoritism, misuse of office or position, or the abandonment of organizational goals for personal interests.

10. QUALITY CONTROL

10.1 Quality Control Plan (QCP)

The contractor shall be responsible for establishing, implementing, and maintaining a current QCP for training. The contractor shall submit a QCP with the proposal, which will identify the standards, processes, procedures, and checklists for all tasks performed.