Attachment_3_-_Performance_Work_Statement.docx

PERFORMANCE WORK STATEMENT (PWS)

Rapid Mobile Applications Development

PART 1 – GENERAL INFORMATION

1. GENERAL: This is a non-personal services contract to provide Rapid Development of Mobile Applications or assets to be utilized in mobile applications. The Government will not exercise any supervision or control over the contract service providers performing the services herein. Such contract service providers shall be accountable solely to the Contractor who, in turn is responsible to the Government.

1.1 DESCRIPTION OF SERVICES AND INTRODUCTION: The Contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform Rapid Development of Mobile Applications or assets as defined in this PWS except for those items specified as Government furnished property and services. The Contractor shall perform to the standards in this contract.

1.2 BACKGROUND: In keeping with the Army’s pursuit of “right place, right time” training, a vehicle for rapid development of mobile applications come from a variety of locations (Centers of Excellence, Training and Doctrine Command (TRADOC) Centers and Schools, other Army training sites, Joint Forces, etc.). This contract vehicle will ensure a rapid and complete response in the development of those requirements.

1.3 SCOPE: The Contractor shall analyze, design, and develop mobile applications, and multimedia assets used in mobile applications as described in TRADOC Pamphlet (TP) 350-70-12, The Army Distributed Learning Guide.

1.4 PERIOD OF PERFORMANCE: The period of performance shall be for one (1) year from date of award.

1.5 PLACE OF PERFORMANCE: The work to be performed under this contract shall be performed at contractor’s place of business.

1.6 QUALITY CONTROL: The Contractor shall develop and maintain an effective quality control program to ensure services are performed in accordance with this PWS. The Contractor shall develop and implement procedures to identify, prevent, and ensure non-recurrence of defective services. The Contractor’s quality control program is the means by which it is assured that work complies with the contract requirements. The Contractor shall submit the Quality Control Plan (QCP) with its proposal. The QCP shall develop and implement written management procedures to ensure timely delivery and service continuity. These procedures shall be updated as deemed necessary by the Contractor, at any time when the QCP proves to be inadequate to solve site-specific problems. After acceptance of the quality control plan, the Contractor shall obtain the Contracting Officer’s (KO) acceptance in writing of any proposed change to its QCP.

1.7 QUALITY ASSURANCE: The Government will evaluate the contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan. This plan is a Government only document primarily focused on what the Government must do to assure that the Contractor has performed in accordance with the requirements of the contract. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.8 TYPE OF CONTRACT: The Government will award a firm fixed price, non-personal services contract.

1.9 NEW/EMERGING TECHNOLOGY: The Contractor shall obtain approval to use New/Emerging Technology. Technology is rapidly evolving. It is likely that new technology standards will emerge during the period of this contract. It is also likely that additional commercial off-the-shelf mobile application authoring solutions will become available. Based on this possibility the contractor may propose alternative technical solutions and standards. The Contractor shall request approval of use of new/emerging technology from the KO.

1.10 SECURITY REQUIREMENTS:

1.10.1 ANTI-TERRORISM (AT) LEVEL I TRAINING. All Contractor employees, including sub-contractor employees, requiring access to Army installations, facilities, or controlled access areas shall complete AT Level I awareness training within 14 calendar days after contract start date or effective date of incorporation of this requirement into the contract, whichever applies. The Contractor shall submit certificates of completion for each affected Contractor employee and subcontractor employee to the COR (or to the contracting officer, if a COR is not assigned) within 14 calendar days after completion of training by all employees and subcontractor personnel. AT Level I awareness training is available at http://jko.jten.mil.

1.10.2 iWATCH TRAINING: The Contractor and all associated sub-contractors shall brief all employees on the local iWATCH program (training standards provided by the requiring activity ATO). This local developed training shall be used to inform employees of the types of behavior to watch for and instruct employees to report suspicious activity to the COR. This training shall be completed within 30 calendar days of contract award and within 14 calendar days of new employees commencing performance with the results reported to the COR NLT 30 calendar days after contract award.

1.10.3 FOR CONTRACTS THAT REQUIRE OPERATIONS SECURITY (OPSEC) TRAINING. Per AR 530-1, Operations Security, new Contractor employees must complete Level I OPSEC training within 30 calendar days of reporting for duty. All Contractor employees must complete annual OPSEC awareness training.

1.11 PHYSICAL SECURITY: The Contractor shall be responsible for safeguarding all Government equipment, information, and property provided for Contractor use.

1.12 CONTRACTING OFFICER REPRESENTATIVE (COR): The (COR) will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. The COR is authorized to perform the following functions: Assure that the Contractor performs the technical requirements of the contract: perform inspections necessary in connection with contract performance: Maintain written and oral communications with the Contractor concerning technical aspects of the contract: Issue written interpretations of technical requirements, including Government drawings, designs, specifications: monitor Contractor's performance and notifies both the KO and Contractor of any deficiencies; coordinate availability of Government furnished property, and provide site entry of Contractor personnel. A letter of designation issued to the COR, a copy of which is sent to the Contractor, states the responsibilities and limitations of the COR, especially with regard to changes in cost or price, estimates or changes in delivery dates. The COR is not authorized to change any of the terms and conditions of the resulting contract.

1.13 CONTRACTOR TRAVEL: The Contractor shall be required to travel in support of the contract. The Contractor shall be required to travel to attend meetings, conferences, and training. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and Federal Acquisition Regulation (FAR) 31.205-46 with the limitation of funds specified in this contract. All travel requires Government approval/authorization prior to travel by the COR. The Contractor shall notify the Government in writing when 85% of the provided travel funds have been expended not to exceed $10,000; the Government is not responsible for excess travel charges.

1.14 KEY PERSONNEL: The Contractor shall provide a Project Manager (PM) who shall be responsible for the performance of the work. The name of this person and an alternate who shall act for the contractor when the PM is absent shall be designated in writing to the KO. The PM and alternate shall have full authority to act for the Contractor on all contract matters relating to the daily operation of this contract. The following personnel are considered key personnel by the Government and their qualifications are listed below:

1.14.1 PROJECT MANAGER: The Contractor shall designate a single point of contact to serve as Project Manager (PM) for this contract. The PM shall function as the point of contact between the Government COR and the Contractor. The PM shall provide management support in the performance of the day-to-day management of overall support operations, which includes but is not limited to staff management, deliverable management, schedule management, performance management, cost management, risk management, and configuration/quality control management.

1.14.2 INSTRUCTIONAL DESIGNER AND TECHNOLOGIST: Responsible for developing instructional materials and products and assisting in the technology-based redesign of Section 508 conformant courses and assists other team members in learning about, becoming proficient in, and applying Section 508 conformant instructional technology. The Instructional Designer and Technologist must be capable of performing the 23 Instructional Designer and Technologist tasks at http://www.onetonline.org/link/summary/25-9031.01#Tasks. This position requires a completed M.S. (PhD. preferred) of Education (specialization in Instructional Systems Design or Instructional Design Technology). The degree must have included all nine Instructional Designer and Technologist "knowledge" areas at http://www.onetonline.org/link/summary/25-9031.01#Knowledge. Proposal shall indicate degree of successful design of computer based training software, desktop publishing software, graphics and photo imaging software, video creation and editing software, web page creation and editing, and Section 508 conformance testing.

1.14.3 MULTIMEDIA ARTIST AND ANIMATOR: Responsible for creating special effects, animation, or other visual images using film, video, computers, or other electronic tools and media for use in products or creations, such as Interactive Multimedia Instruction, 3D models, digital Learning Content Objects (LCO), serious computer games, simulations, videos, augmented reality and virtual reality. The Multimedia Artist and Animator shall be capable of performing the 13 Multimedia Artist and Animator tasks at http://www.onetonline.org/link/summary/27-1014.00#Tasks. This position requires a completed B.S. (M.S. preferred) of Computer Science (specialization in Computer Graphics). The degree must have included all six Multimedia Artist and Animator "knowledge" areas at http://www.onetonline.org/link/summary/27-1014.00#Knowledge. In ADDITION to the degree, the Multimedia Artist and Animator shall specify that he or she has five (5) years’ paid experience developing Army IMI and 3D models for digital LCOs, serious games, simulations, videos, and augmented and virtual reality with software similar to that specified in the "Technology used in the Instructional Designer and Technologist" area at http://www.onetonline.org/link/summary/27-1014.00#ToolsTechnology. Proposal shall indicate degree of successful IMI and 3D model (both) development for computer aided design software, desktop publishing software, development environment software, document management software, enterprise application integration software, graphics and photo imaging software, object or component oriented development software, office system software, operating system software, video creation and editing software, and web platform development software.

1.14.4 NARRATOR/VOICEOVER ARTIST: 2 years of experience as a paid professional narrator for e-learning courseware, audio books, documentaries, or educational/business podcasts/videos.

1.14.5 AUDIO/VIDEO SPECIALIST: Two (2) years of experience in audio/video editing and/or post-production.

1.14.6 EDITOR/QUALITY ASSURANCE SPECIALIST: Bachelors in English OR Journalism or five (5) years of copy editing experience reviewing documents for grammar, spelling and punctuation errors. Evaluate mobile applications to ensure they are clearly written, concise, unambiguous, and suitable for the reading comprehension level of the user. Edit mobile applications for proper format, effectiveness of written expression, appropriateness of writing style, use of illustrations, organization of subject matter, and method of indexing.

1.14.7 SOFTWARE DEVELOPER (MOBILE APPLICATIONS): Responsible for developing, creating, and modifying Mobile Learning applications software; may supervise other software developers or computer programmers. The Software Developer (Applications) shall be capable of performing the 11 Software Developer (Applications) tasks at http://www.onetonline.org/link/summary/15-1132.00#Tasks. This position requires a completed B.S. (M.S. preferred) of Computer Science or Computer Engineering. The degree must have included all six Software Developer (Applications) "knowledge" areas at http://www.onetonline.org/link/summary/15-1132.00#Knowledge. In ADDITION to the degree, the Software Developer (Applications) shall prove that he or she have five (5) years’ experience developing successful Mobile Learning DL applications and two years’ paid experience developing successful Mobile Learning DL. Such DL must have been successfully integrated with software similar to that specified in the "Technology used in the Software Developer (Applications)” area at http://www.onetonline.org/link/summary/15-1132.00#ToolsTechnology. Proposal shall indicate degree of successful Mobile Learning software development integrated with application server software, business intelligence and data analysis software, data base management system software, data base reporting software, data base user interface and query software, development environment software, enterprise application integration software, file versioning software, graphical user interface development software, network security equipment software, object or component oriented development software, platform interconnectivity software, program testing software, requirements analysis and system architecture software, transaction security and virus protection software, and web platform development software.

1.14.8 VIDEO GAME DESIGNER: Responsible for designing core features of video games delivered as mobile apps; specifying innovative game and role-play mechanics, story lines, and character biographies; create and maintain design documentation; guide and collaborate with production staff to produce games as designed. The Video Game Designer shall be capable of performing the 22 Video Game Designer tasks at http://www.onetonline.org/link/details/15-1199.11#Tasks. This position requires a completed B.S. (M.S. preferred) of Computer Science (specialization in Computer Graphics). The degree must have included all six Video Game Designer "knowledge" areas at http://www.onetonline.org/link/details/15-1199.11#Knowledge. In ADDITION to the degree, the Video Game Designer shall specify that he or she have five (5) years’ paid experience developing successful Army Games For Training (AGFT) scoring DL that must have included successful development using VBS2 and VBS3 with software similar to that specified in the "Technology used in the Video Game Designer occupation" area at http://www.onetonline.org/link/details/15-1199.11#ToolsTechnology. Proposal shall indicate degree of successful video game software, graphical user interface development software; graphics and photo imaging software, object and component oriented development software, video creation and editing software, augmented reality software, and virtual reality software.

1.15 MEETINGS, MINUTES, MONTHLY STATUS REPORTS AND MILESTONE SCHEDULE:

1.15.1 POST AWARD/KICK OFF MEETING/PERIODIC PROGRESS MEETINGS: The Contractor agrees to attend any post award meeting convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The KO, COR, and other Government personnel, as appropriate, may meet periodically with the Contractor to review the Contractor's performance. At these meetings the KO will apprise the Contractor of how the Government views the Contractor's performance and the Contractor shall apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

1.15.1.1 A post award or kick off meeting will be held for each mApp requirement requested by the Government.

1.15.2 IN-PROCESS/IN-PROGRESS REVIEW (IPR) MEETINGS: The Contractor shall conduct In-process/progress review meetings to review and discuss technical issues of products and/or to discuss issues that affect product delivery - Government review comments, contractor correction requirements, scheduling problems, milestone schedule, and similar issues. These meetings shall be conducted on a weekly or biweekly basis as agreed between Government and Contractor. The Contractor shall provide meeting minutes of all IPRs conducted within three (3) business days of meeting conclusion. When IPRs are not conducted, the Contractor shall submit a progress update within three (3) business days of regularly scheduled meeting. The update shall describe any difficulties or problems encountered, anticipated or which previously existed that could alter the progression of work. The update shall include the current state of development and recommendations for resolution of problem areas.

1.15.3 MONTHLY STATUS REPORTS: Monthly Status Reports shall be provided to COR NLT the 5th day of each month throughout the period of performance. The Monthly Status Report includes tasks accomplished, problems/solutions, lessons learned, and tasks to be accomplished during the next reporting period.

1.15.4 MILESTONE SCHEDULE: The Contractor shall submit a milestone schedule for each mApp development effort requested by the Government. The milestone schedule shall provide a description of the work processes and timing of work effort. The schedule shall allow time for and depict all events of Contractor performance, Government review, and Contractor correction of errors found, resubmission, and acceptance of deliverables. Government review time for each deliverable is ten business days but will be specified during discussion of the milestone schedule at Post Award/Kickoff meeting.

1.16 DATA RIGHTS: The Government has unlimited rights to all documents/material produced under this contract, as stated in the DFARs clauses, Part 227, as included in this contract. All documents and materials, to include the source code of any software, produced under this contract will be Government owned and are the property of the Government with all rights and privileges of ownership/copyright belonging exclusively to the Government. These documents and materials shall not be used or sold by the Contractor without written permission from the KO. All materials supplied to the Government will be the sole property of the Government and may not be used for any other purpose. This right does not abrogate any other Government rights.

1.17 ORGANIZATION CONFLICT OF INTEREST (OCI): Contractor and subcontractor personnel performing work under this contract may receive, have access to or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the KO immediately whenever it becomes aware that such access or participation may result in any actual or potential OCI and shall promptly submit a plan to the KO to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the KO and in the event the KO unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the KO may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.18 INVOICING: Wide Area Workflow shall be implemented IAW Defense Federal Acquisition Regulation (DFAR) 252.232-7003 Electronic Submission of Payment Requests and Receiving Reports. Manual invoices will not be accepted.

PART 2 - DEFINITIONS & ACRONYMS

2.1 DEFINITIONS:

2.1.1 ASSET. Multimedia content in its most basic form is composed of Assets that are electronic representations of media, text, images, sound, web pages, objects or other pieces of data that can be delivered to a Web client. An Asset can be described with Asset Meta-data to allow for search and discovery within online repositories, thereby enhancing opportunities for reuse. The mechanism for binding Assets to Asset Metadata is the Content Package.

2.1.2 BUSINESS DAYS. Monday through Friday, except Federal holidays and holidays declared by Executive Order.

2.1.3 CONTENT PACKAGE. Is used to move digital resources or collections of resources between development tools and content repositories. The Content Packaging specification provides a common “input/output” format that any system can support.

2.1.4 CONTRACTOR. A supplier or vendor awarded a contract to provide specific supplies or service to the Government. The term used in this contract refers to the prime.

2.1.5 CONTRACTING OFFICER. A person with authority to enter into, administer, and or terminate contracts, and make related determinations and findings on behalf of the Government. Note: The only individual who can legally bind the government.

2.1.6 CONTRACTING OFFICER'S REPRESENTATIVE (COR). An employee of the U.S. Government appointed by the KO to administer the contract. Such appointment will be in writing and will state the scope of authority and limitations. This individual has authority to provide technical direction to the Contractor as long as that direction is within the scope of the contract, does not constitute a change, and has no funding implications. This individual does NOT have authority to change the terms and conditions of the contract.

2.1.7 DEFECTIVE SERVICE. A service output that does not meet the standard of performance associated with the Performance Work Statement.

2.1.8 DELIVERABLE. Anything that can be physically delivered, but may include non-manufactured things such as meeting minutes or reports.

2.1.9 DEVICE FAMILIES. The following hardware and software characteristics collectively define a mobile device.

· A small form factor.

· At least one wireless network interface for network access (data communications). This interface uses Wi-Fi, cellular networking, or other technologies that connect the mobile device to network infrastructures with connectivity to the Internet or other data networks.

· Local built-in (non-removable) data storage.

· An operating system that is not a full-fledged desktop or laptop operating system1.

· Applications available through multiple methods (provided with the mobile device, accessed through web browser, acquired and installed from third parties).

· The list below details other common, but optional, characteristics of mobile devices.

· Network services:

· One or more wireless personal area network interfaces, such as Bluetooth or near-field communications.

· One or more wireless network interfaces for voice communications, such as cellular.

· One or more digital cameras/video recording devices.

· Microphone.

· Storage.

· Support for removable media.

· Support for using the device itself as removable storage for another computing device.

· Built-in features for synchronizing local data with a different location (desktop or laptop computer, organization servers, telecommunications provider servers, other third party servers, etc.). (Source: NIST Special Publication 800-124 Revision 1)

2.1.10 DISTRIBUTOR’S HOSTING REQUIREMENTS (DHR). Coding, metadata and packaging requirements to host app on distributor’s store/site (such could include one or all as required, as Apple’s App Store, Google Play, Windows Store). Distributor’s Hosting Requirements are in Paragraph 6.3 of this PWS. The TRADOC APP Gateway (TAG) does provide hosting capabilities for limited community distribution, and items identified above used on app distributors store meet TAG standards as well. In instances of applications developed for public consumption, the TAG will link to the commercial stores.

2.1.11 GOVERNMENT FURNISHED INFORMATION (GFI), GOVERNMENT FURNISHED MATERIAL (GFM) GOVERNMENT FURNISHED PROPERTY (GFP) OR GOVERNMENT PROPERTY (GP). Property in the possession of, or directly acquired by, the Government and subsequently made available to the Contractor.

2.1.12 HYBRID. Mobile application which combines the features of native and web based application. Typically written with web based software, but still maintains some of its native capabilities.

2.1.13 KEY PERSONNEL. Contractor personnel that are evaluated in a source selection process and that are required to be used in the performance of a contract. When key personnel are used as an evaluation factor in best value procurement, an offer can be rejected if it does not have a firm commitment from the persons that are listed in the proposal.

2.1.14 MOBILE APPLICATION (mApp). An application designed to run in the browser of a learner-owned mobile device (Mobile Category 1), Hybrid (Mobile Category 2 and 3), or Native apps (Mobile Category 4-5) are written in the device specific programming language.

2.1.15 mAPP CATEGORIES:

2.1.15.1 mApp Category 1 – Mobile friendly website (Responsive Web Design (RWD) Passive; Basic Informational Application).

· User Interface (UI) built with web standard technologies.

· Available at a Uniform Resource Locator (URL).

· Not installed on mobile device.

· Not available in the marketplace.

· Detects device family accessing website and provides appropriate view format.

· Different views created for mobile and desktop device families to take advantage in difference in screen size.

· Development time for this level is approximately 60 days.

2.1.15.2 mApp Category 2 – Hybrid; HTML5/HTML/CSS/JS in mobile app wrapper with no network access (after initial download).

· Installed on mobile device.

· Available in the marketplace.

· Inserted graphics, photographs, illustrations, small videos, simple charts and diagrams.

· Use of non-network data device features (e.g. accelerometer, camera, compass, Bluetooth, touchscreen, SD card-storage.)

· Development time for this level is approximately 120 days.

2.1.15.3 mApp Category 3 – Hybrid; HTML5/HTML/CSS/JS in mobile app wrapper with network access (after initial download).

· mApp Category 2 capabilities.

· Use of network data device features (e.g. internet, Global Positioning System (GPS)-Mapping.)

· Posting to Social Media sites (YouTube, Facebook, Twitter, Instagram, etc.)

· Push notifications.

· Rich Site Summary (RSS) feeds for updated content.

· Report status (xAPI).

· Development time for this level is approximately 120 days.

2.1.15.4 mApp Category 4 – Native; Games and or visualizations involving 3D models with no network access (after initial download).

· mApp Category 2 capabilities.

· Initiate complex animated demonstrations, operations and/or procedures and games.

· Development time for this level is approximately 180 days or longer based on circumstances.

2.1.15.5 mApp Category 5 – Native; Games and or visualizations involving 3D models with network access (after initial download).

· mApp Category 3 capabilities.

· Complex combining of device features (e.g. mashup such as geolocation combined with social networking for location-based gaming.)

· Initiate complex animated demonstrations, operations and/or procedures and games.

· Development time for this level is approximately 180 days or longer based on circumstances.

2.1.16 NATIVE. Application software that is programed for a specific device platform which allows full functionality of all the mobile device’s features.

2.1.17 PHABLET. Smartphone/tablet hybrids. Feature-rich devices with screen sizes between 5-6 inches.

2.1.18 PHYSICAL SECURITY. Actions that prevent the loss or damage of Government property.

2.1.19 QUALITY ASSURANCE. The Government procedures to verify that services being performed by the Contractor are acceptable in accordance with established standards and requirements of this contract.

2.1.20 QUALITY ASSURANCE SPECIALIST. An official Government representative concerned with matters pertaining to the contract administration process and quality assurance/quality control. Acts as technical advisor to the KO in these areas.

2.1.21 QUALITY ASSURANCE SURVEILLANCE PLAN (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

2.1.22 QUALITY CONTROL. All necessary measures taken by the Contractor to assure that the quality of an end product or service shall meet contract requirements.

2.1.23 RESPONSIVE DESIGN. The same content and syntax (manipulated by JavaScript and/or CSS media queries) respond by rearranging layouts when the viewport dictates to provide an adaptive user experience for each device.

2.1.24 SCRIPTS. A script guides the content of the production, and determines the actions required to develop and produce video. Scripts include a product treatment that contains the concept, purpose, and it translates the treatment into a detailed guide showing scenes, sequences, dialogue, narration, graphics, music, camera angles, etc., required to develop the program. The script includes identification of resource requirements, such as personnel, location, and equipment; and clearly describes to the approving authority what the program will provide. Scripts may be substituted for storyboards when the IMM is heavily video-based.

2.1.25 SUBCONTRACTOR. One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

2.1.26 WIRED AND WIRELESS NETWORKING. The basic infrastructure needed to move, manage, store, retrieve, and maintain information in, from, or to remote locations from either a central location or other remote locations. Traditional wired networks may include dial-up modem connectivity, Integrated Services Digital Network (ISDN), Ethernet, T1, T3, Asynchronous Transfer Mode (ATM), Fiber Channel or optical cable based information delivery systems. Wireless networking would allow Very Short Range (VSR) delivery via technologies like infrared (IR) Microcellular, and Radio Frequency (RF) as well as long range technologies like analog, Cellular, Satellite, Cellular Digital Packet Data (CDPD) or Wireless ATM. This area would also likely address the additional technologies like encryption and security protocols required to keep the data being moved secure from all manner of intrusion.

2.1.27 WORLD WIDE WEB. Often referred to as WWW or the Web, this usually refers to information available on the Internet/intranet/extranet that can be easily accessed with access software usually called a browser. Organizations publish their information on the Web in a format known as HTML (Hypertext Markup Language); this information is usually referred to as their home page.

2.1.28 xAPI. Experience Application Programing Interface (xAPI) is Advanced Distributed Learning’s (ADL) specification that describes an interface and the storage/retrieval rules to enable the tracking of learning experiences. Statements of experience are delivered to and stored in a Learning Record Store (LRS).

2.2 ACRONYMS:

PART 3 – GOVERNEMNT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. GOVERNMENT FURNISHED ITEMS AND SERVICES:

3.1 GOVERNMENT FURNISHED INFORMATION (GFI): All required GFI will be supplied by Government Proponent to the Contractor within 15 business days following request for mApp development. This information shall be protected and returned upon completion of the contract.

PART 4 – CONTRACTOR FURNISHED ITEMS AND SERVICES

4. CONTRACTOR FURNISHED ITEMS AND RESPONSIBILITIES:

4.1 The Contractor shall furnish all supplies, equipment, facilities and services required to perform work under this contract that are not listed under Section 3 of this PWS.

4.2 On line Review system: The Contractor shall provide an online review system for review of wireframe, visual, audio and interactive products which provides for contextual commenting. Unless otherwise specified, text-based products shall be delivered electronically (via email, online review system, etc.) for review. The purpose of the review is to provide content reviewers with the ability to review, resolve conflicting comments, and submit comments to the Mobile Application by the contractor.

4.3 The Contractor shall provide its own access to the Internet for downloading of items available provided by the Government by that delivery method, specifically access to https://safe.amrdec.army.mil/.

4.4 The Contractor shall develop, manage, and deliver contractually required data. This requirement includes all data deliverables cited in the PWS and all source documents and electronic files required to prepare the deliverable items.

4.5 The Contractor shall provide control and configuration management of all contractually required data and provide this data to the Government as required by contract, including that produced by subcontractors performing under this contract.

4.6 Where word processing or other software templates are used for design and storyboards, the Contractor shall deliver the templates and completed documents supporting the work, completed project files and the printed audit trail documentation IAW project milestone schedule.

4.8 The Contractor shall obtain releases for all copyrighted materials used, referenced, or included in any product developed under this contract. The Contractor shall indemnify the Government for any liability arising as a result of the unauthorized use of patented items. The Contractor shall provide legal certification, or license, from the owner that permits Government use if copyrighted material is delivered IAW DFARS 252.227-7020, Rights in Special Works (Jun 1995).

4.9 The Contractor shall ensure that all deliverables meet the quality requirements of the contract. When products are submitted by the Contractor for acceptance by the Government, the Contractor shall submit reports of testing and certify that quality testing was conducted and that products comply with quality requirements as established under this contract.

4.10 The Contractor shall deliver mobile products to the Government for content review, technical testing, and application code vetting. Based on this review, the Contractor shall make, at no additional cost to the Government, changes to the mobile applications that the Government identifies as necessary to ensure accuracy, functionality or operability. The standard for implementation of agreed upon changes is 100% implementation of required changes and no new errors in previously reviewed products.

4.11 The Contractor shall comply with Distributor’s Hosting Requirements (DHR). Hosting requirements may change during the period of performance. The Contractor shall follow the DHR in effect at the time the product is to be deployed.

4.12 The Contractor shall register with the hosting marketplace/s and acquire any necessary Software Development Kit (SDK), Native Development Kit (NDK), frameworks or emulators required to develop the product.

PART 5 –SPECIFIC TASKS/DELIVERABLES

5. SPECIFIC TASKS AND DELIVERABLES:

5.1 BASIC SERVICES. The Contractor shall provide services for the development of mobile applications and supporting deliverables.

5.2 ANALYSIS REPORTS: Analysis reports provide information for the development of mobile applications. The Contractor shall analyze Government provided information and compile a report of its results.

5.2.1 GOVERNMENT FURNISHED INFORMATION (GFI) REPORT: The Contractor shall analyze GFI and provide a written report to support the quality and quantity of Government Furnished Information. The Contractor shall submit a GFI report within 15 calendar days of receipt of GFI from the Government. This report shall address all materials identified and provided by the Government to design and develop the mobile application. This report shall state if the GFI is available, unavailable, not required, not current, or inadequate. The Contractor also shall explain why the GFI is inadequate, if applicable.

5.2.1.1 ACCEPTANCE PROCESS AND CRITERIA: The Proponent will review and accept that the GFI Analysis Report. The report can be delivered in Word or Excel but must include the elements listed above. The TCM Mobile Instructional Systems Specialist (ISS) shall review and accept that the GFI Analysis Report satisfies the specifications in the compliance documents. Upon passing both the proponent and TCM Mobile review, TCM The Army Distributed Learning Program (TADLP) COR will issue acceptance of the GFI Analysis Report.

5.2.2 MOBILE APPLICATION ANALYSIS (MAA) REPORT: This report shall recommend the type of mobile content (e.g., job aid checklist, quick reference, practical exercise simulation, etc.), the level of interactivity, a brief conceptual description and an explanation of how training shall be doctrinally enhanced or supported with mobile content. The report shall also identify external resources (e.g., internet connectivity, social media, RSS feeds), recommended mobile devices, mApp category, and target file size.

5.2.2.1 ACCEPTANCE PROCESS AND CRITERIA: The report shall be delivered in Word or Excel but shall include the elements listed above. The Government will review the report and TADLP will sign acceptance.

5.3 DESIGN: Design of mobile applications provides the user with an engaging user experience that serves to enhance understanding and transferability of knowledge. The Contractor shall provide information to the Government that demonstrates its understanding of the task and its recommended design.

5.3.1 DESIGN AND DEVELOP WIREFRAMES/STORYBOARDS: The Contractor shall develop wireframe/storyboards in a navigation framework to document User Experience (UX), interactivity, learner input, as well as any backend interfaces-API endpoints). Storyboards shall be developed using word processing software such as MS Word or presentation software such as MS PowerPoint or in a commercial/Government-off-the-shelf wireframe/storyboarding tool that meets Army education/training technical and functional standards. The Contractor shall develop wireframe/storyboard documentation that presents design of the screens/pages to be developed including the type and number of images, video/audio or interactive widget recommendations. Wireframes/storyboards are designed to explain concept, the user experience and gain approval for the mApp. The wireframes/storyboards shall be considered the alpha deliverable of the mApp development and pricing for wireframes/storyboards shall be included in the mApp (level 1-5). The final wireframe/storyboard shall be Government-approved before development of the mobile application. Wireframes/Storyboards, at minimum, shall include for each intended page/screen:

· Navigation.

· Appearance (CSS).

· Color scheme.

· Graphics and textual information.

· User interface components.

· Transitions and gestures.

· Portrait and landscape views.

5.3.1.1 ACCEPTANCE PROCESS AND CRITERIA: The proponent will review and accept that the Storyboards:

· Provide a visual depiction of each page/screen that details the visual, audio, branching, navigation and interactive elements

· Provide a 508 compliance plan section on each page/screen the describes how the page/screen and its elements shall be accessible (if some elements cannot be made accessible, an explanation shall be provided why the element cannot be made accessible along with a strategy for providing an equivalent alternative activity)

5.4.9.1.2. The TCM Mobile Instructional Systems Specialist (ISS) shall review and accept that the Wireframe/Storyboards includes the elements depicted in paragraph 5.3.1.

5.4.9.1.3. The TCM Mobile Technical Specialist (Tech) shall review and accept that wireframe/storyboards include an acceptable compliance plan on each page/screen.

5.4.9.1.4. Upon passing both the proponent and the TCM Mobile reviews, TCM TADLP COR will issue the acceptance of the Wireframe/Storyboards.

5.5 DEVELOP MOBILE APPLICATION: Development of the mobile application is based on the mobile app category and number of platforms (for different device families and hosting marketplaces).

5.5.1 REQUIRED FEATURES: The Contractor shall develop the mApp with the following features:

· Support devices in the mobile and desktop device families.

· Content display shall adapt to the different screen sizes within a device family.

· Support both portrait and landscape views. Landscape views shall be optimized for the display screen in landscape mode (an alternative layout/navigation) and not just a larger version of the portrait view.

· Develop different views for devices in different device families to take advantage of the difference in screen size (e.g. a tablet can support a split view with multiple content areas or a menu and a content area where a smartphone may only support one content area). The exception to this requirement is when full-screen gaming or simulations are required.

· Detect device features and notify learner that a function may be disabled if the device feature to support the function is not available (e.g. lack of camera, no internet available, etc.)

· Request learner permission to access device features (e.g. internet, GPS location, contact list, etc.)

· Launch image/splash screen shall identify mApp as approved Army application.

· mApps shall be identifiable as the same app across different distributor platforms. The mApp must present the same content but will not operate in exactly the same manner (e.g. tab bars are at the top of the screen for Android but at the bottom of the screen for iOS). Follow distributor guidelines on maintaining platform unique UX/UI (e.g. navigation, buttons, etc.).

· Accessible images and figures: All images shall follow Web Content Accessibility (WCAG) Techniques, and other requirements as to provide accessible images, graphics, and figures.

· Accessible videos: All images shall follow Web Content Accessibility (WCAG) Techniques and other requirements to provide accessible videos shall be captioned or be accompanied by text transcript.

· Images: deliver highest quality image supported by device family.

· Audio and Video: Audio and Video shall play in all devices.

· Support other languages (right to left (RTL) reading order) as required.

5.5.2 DESIGN TOOLS: The Contractor may use any tool in the design and development process as long as the resultant deliverable product from that tool meets standards and specifications contained in this PWS.

5.5.3 METADATA: The Contractor shall provide all metadata as required by the Distributor’s Hosting Requirements and Accessibility metadata (e.g. ONIX).

5.6 IMPLEMENTATION: The step in preparation for fielding the mobile application. The contractor shall perform all steps required to implement hosting on the chosen platform/s.

5.6.1 PROOF OF TESTING: Emulator logs from a representative number of devices from each device family (for example, an app for both tablets and smartphone for all three platforms (Android, Apple, and Windows) would require 6 versions).

5.6.1.1 DOCUMENTS, SOURCE FILES, AND PROJECT FILES: The Contractor shall deliver templates and completed documents supporting the specific product to the Government. The Contractor shall deliver complete project files and audit trail documentation to the Government. The Contractor shall deliver all source files (graphics, animations, audio files, and etc.) as part of the final delivery package. This delivery will shall be in raw code as well as the packaged app in required format/s specified in the Distributor’s Hosting Requirements. Delivery of raw code shall also include all application assets (i.e. movie, audio, link lists, etc.) that may be required for user experience. Finally, all mobile application description statements shall be packaged with assets and raw code in final delivery.

5.7 CONTRACTOR MANAGEMENT REPORTING (CMR): The Contractor shall report ALL Contractor labor hours (including subcontractor labor hours) required for performance of services provided under this contract for the Department of the Army via a secure data collection site. The Contractor is required to completely fill in all required data fields using the following web address: http://www.ecmra.mil, and then click on “Department of the Army CMRA” or the icon of the DoD organization that is receiving or benefitting from the contracted services. Reporting inputs shall be for the labor executed during the period of performance during each Government Fiscal Year (FY), which runs from October 1 through September 30. While inputs may be reported any time during the FY, all data shall be reported no later than October 31 of each calendar year, beginning with 2013. Contractors may direct questions to the help desk by clicking on “Send an email” which is located under the Help Resources ribbon on the right side of the login page of the applicable Service/Component’s CMR website at http://www.ecmra.mil. As part of its submission, the Contractor shall also provide the estimated total cost (if any) incurred to comply with this reporting requirement.

PART 6 – APPLICABLE PUBLICATIONS

6. APPLICABLE PUBLICATIONS (CURRENT EDITIONS)

6.1 The Contractor shall abide by the version of all applicable regulations, publications, manuals, and local policies and procedures current at time of award. Army Regulations: Official Department of the Army Publications and Forms (http://www.army.mil/usapa/

· Army Regulation 350-1, Army Training and Leader Development

· Army Regulation 380-5, Department of the Army Information Security Program

6.2 COMPLIANCE DOCUMENTS: The Contractor shall ensure all work complies with the following:

· TRADOC Regulation 350-70, Army Learning Policy and Systems, http://www.tradoc.army.mil/tpubs/regs/TR350-70.pdf, 6 Dec 11 or current edition.

· TRADOC Pamphlet 350-70-12, Distributed Learning – Managing Courseware Production and Implementation, http://www.tradoc.army.mil/tpubs/pams/tp350-70-12.pdf, 3 May 13 or current edition.

· Protection Profile for Mobile Device Fundamentals, https://www.niap-ccevs.org/Profile/Info.cfm?id=381, Version 3.0, June 10, 2016

· Advanced Distributed Learning (ADL™) Initiative’s Experience API (xAPI), https://github.com/adlnet/xAPI-Spec/blob/1.0.1/xAPI.md, Version 1.01.

· All requirements are subject to DFARS 252.227-7020 to include all documents, materials and source codes of any software. The Contractor shall mark all works delivered as required by DFARS 252.227-7020.

· Personally Identifiable Information: The use of social security numbers and other personally identifiable information (PII) is forbidden in web based mobile apps. With the rise of personal identity theft, the Contractor shall be especially sensitive to the use of any information in the text or graphics that could jeopardize personal information. Compliance information is found at http://www.atsc.army.mil/tadlp/content/nomination/dl_pii.asp

· Section 508 Compliance and Accessibility Requirements: The Contractor shall ensure all mobile products required through this contract comply with the provisions of Section 508 and shall meet all applicable accessibility standards.

· Section 508 Standards (current standards to provide coverage during WCAG integration phase). http://www.access-board.gov/guidelines-and-standards/communications-and-it/about-the-section-508-standards

· WCAG (Broad coverage of all products created, will eventually replace existing 508 standards): http://www.w3.org/TR/WCAG20/

· United States Government Printing Office Style Manual, http://www.gpo.gov/fdsys/pkg/GPO-STYLEMANUAL-2008/pdf/GPO-STYLEMANUAL-2008.pdf, 2008 or current edition.

6.3 DISTRIBUTOR HOSTING REQUIREMENTS:

· Android Design Principles -http://developer.android.com/design/get-started/principles.html

· Guidelines for Universal Windows Platform Apps (UWP) -https://msdn.microsoft.com/library/windows/apps/hh465424.aspx

· Apple’s Mobile Human Interface Guidelines (HIG) -https://developer.apple.com/library/ios/documentation/UserExperience/Conceptual/MobileHIG

6.4 CONFIGURATIONS:

Configurations shall include devices from both the mobile and desktop device families. Specific devices shall be identified.

6.5 REFERENCES:

· Army Training Support Center – TCM TADLP http://www.atsc.army.mil/TADLP

· Security Technical Implementation Guides (STIGs) http://iase.disa.mil/stigs/index.html

PART 7 -…