PWS_DATR_Attachment_1.docx

PERFORMANCE WORK STATEMENT (PWS)

DISTRIBUTED LEARNING (DL)

DIAGNOSTIC, ADVISEMENT AND TECHNICAL RESEARCH (DATR)

Part 1

General Information

1. General. This is a non-personal services contract to provide DL DATR. The Government shall 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/Introduction. The contractor shall provide all personnel, equipment, supplies, facilities, transportation, tools, materials, supervision, and other items and non-personal services necessary to perform DL DATR as defined in this Performance Work Statement except for those items specified as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2. Background. The TRADOC Capability Manager – The Army Distributed Learning Program (TCM-TADLP) has funded development of DL content in which issues have been identified that affect usability and playability. DL training content that employs an interactive multi-media instruction training strategy is generally referred to as courseware. Currently, there is no capability to determine the source of the issues and identify the measures to correct them. There exists a need to identify, document, and distribute the solutions to the issues to ensure courseware play on Army Learning Content Management Capability (ALCMC) platforms.

1.3. Objectives. The Contractor shall diagnose the cause of identified technical issues within DL content packages and files, and generate documentation explaining the cause and method to correct the issue. The Contractor shall build DL content packages that implement the corrections identified in documentation developed in support of the diagnosis task. The Contractor shall conduct technical research of standards and specifications applicable to DL development and delivery, and identify standards and specifications related to Army DL.

1.4. Scope. The work of the DATR is to provide diagnosis, analysis, technical research, and solution identification as the basis for the development of technical specifications and requirements pertaining to all Army DL fielded on ALCMC platforms which are the Army Learning Management System (ALMS) (Saba 5.5), and Enterprise Lifelong Learning Center (ELLC) (Blackboard 9.1) and upgraded versions of base software. The DATR team shall generate solutions and documentation that are applicable to all Army DL fielded on ALCMC platforms.

1. 5. Period of Performance. The period of performance shall be for one (1) Base Year of 12 months and two (2) 12-month option years. The Period of Performance reads as follows:

1.6. General Information

1.6.1. Quality Control (QC). 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 he/she assures himself/herself that his/her work complies with the requirement of the contract. The Contractor shall submit the Quality Control Plan (QCP) with their proposal. The QCP will develop and implement written management procedures to ensure timely delivery and service continuity. These procedures will be updated as deemed necessary by the Contractor and/or the Government, at any time when they prove to be inadequate to solve site-specific problems. Any changes to the QCP will be provided to the Contracting Officer’s Representative (COR) for approval in writing prior to implementation. After acceptance of the quality control plan, the Contractor shall receive the Contracting Officer’s (KO) acceptance in writing of any proposed change to his QC system.

1.6.2. Quality Assurance (QA). The Government shall evaluate the Contractor’s performance under this contract in accordance with the Quality Assurance Surveillance Plan (QASP). This plan is primarily focused on what the Government must do to ensure that the Contractor has performed in accordance with the performance standards. It defines how the performance standards will be applied, the frequency of surveillance, and the minimum acceptable defect rate(s).

1.6.3. Recognized Holidays. The following days have been established as legal public holidays for federal service:

1.6.4. Hours of Operation. The Contractor is responsible for conducting business, between the hours of 0800-1700 hours Monday through Friday except Federal holidays or when the Government facility is closed due to local or national emergencies, administrative closings, or similar Government directed facility closings. For other than firm fixed price contracts, the Contractor will not be reimbursed when the Government facility is closed for the above reasons. The Contractor must at all times maintain an adequate workforce for the uninterrupted performance of all tasks defined within this PWS when the Government facility is not closed for the above reasons. When hiring personnel, the Contractor shall keep in mind that the stability and continuity of the workforce are essential.

1.6.5. Place of Performance. The work to be performed under this contract will be performed at Fort Eustis, Virginia area or off-site Contractor facilities. The Government may, by COR direction, direct Contractor personnel to work both on or off-site.

1.6.6. Type of Contract. The Government will award a firm-fixed price contract.

1.6.7. Information Technology (IT)/Common Access Card (CAC). Contractor personnel performing work under this contract will require National Agency Check with Inquiries (NACI) for the life of the contract. Contractor personnel performing under this must be able to obtain and maintain a favorable suitability/fitness determination under 5 Code of Federal Regulation (CFR) 731 or equivalent. The Government will submit background investigations for positions that require a CAC and/or IT access only. For Contractors, the minimum requirement for access to classified federal information systems is as follows: IT- I access, a Single Scope Background Investigation (SSBI/SF 86); IT-II access, a National Agency Check with Local Agency and Credit Check (NACLC/SF 86); and IT- III access, a NACI SF 85. Prior to CAC issuance, the National Agency Check (FBI 10 point FBI fingerprint check) must be completed without adverse comment, and the NACI or equivalent MUST BE INITIATED. CACs will not be issued before the fingerprint check results have been completed and the investigation has been submitted. FINGERPRINTS AND THE APPROPRIATE INVESTIGATION WILL BE SUBMITTED BY THE GOVERNMENT.

If Contractors has Joint Personnel Adjudication System (JPAS) access they should take an owning relationship for each individual performing duty in support of this performance work statement/task order (TO). Visit Requests shall be sent to the Army Training Support Center (ATSC) Security Management Office (SMO) Code (W3E9AA6). In the event the Contractor does not have access to JPAS, the Contractor shall submit a Visit Authorization Letters (VAL) to the ATSC Security Manager, location, Building 1900 Fort Eustis, Virginia 23604-5166, for “each” person providing support to the contract. VAL is only authorized when electronic means are not available. In accordance with (IAW) Army Regulation (AR) and Air Force Instructions, all prospective Contractors shall undergo a verification process to determine the trustworthiness and suitability prior to being granted access to federal property. Limited access with escort may be granted (at the installation’s discretion) for an interim period while investigations are being conducted.

Installation Security Office will submit all background investigations on prospective Contractors requiring CAC and/or network access.

733 Security Forces squadron will conduct background checks on all Contractor personnel requiring access to the installation.

AFI 31-601, Industrial Security Program Management, implements the Air Force’s industrial security program.

5304.404-90 Additional contract clauses

1.6.7.1. Physical Security. The Contractor shall be responsible for safeguarding all Government equipment, information and property provided for Contractor use. At the close of each work period, Government facilities, equipment, and materials shall be secured.

1.6.7.2. Anti-Terrorism (AT) Level I Training. All Contractor employees, including subcontractor 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 https://atlevel1.dtic.mil/at.

1.6.7.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.6.7.4. Access and General Protection/Security Policy and Procedures. This standard language text is for contractor employees with an area of performance within an Army controlled installation, facility or area. Contractor and all associated sub-contractors employees shall comply with applicable installation, facility and area commander installation/facility access and local security policies and procedures (provided by government representative). The contractor shall also provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshal Office, Director of Emergency Services or Security Office. Contractor workforce must comply with all personal identity verification requirements as directed by Department of Defense (DoD), Headquarters, Department of the Army (HQDA) and/or local policy. In addition to the changes otherwise authorized by the changes clause of this contract, should the Force Protection Condition (FPCON) at any individual facility or installation change, the Government may require changes in contractor security matters or processes.

1.6.7.5. For Information Assurance (IA)/IT) Training. All Contractor employees and associated subcontractor employees must complete the DoD IA awareness training before issuance of network access and annually thereafter. All Contractor employees working IA/IT functions must comply with DoD and Army training requirements in DoD Directive 8570.01, DoD 8570.01-M, and AR 25-2 within six months of employment.

1.6.7.6. For IA/IT Certification. Per DoD 8570.01-M, DFARS 252.239.7001, and AR 25-2, the Contractor employees' supporting IA/IT functions shall be appropriately certified upon contract award. The baseline certification as stipulated in DoD 8570.01-M must be completed upon contract award.

1.6.8. Post Award Conference (PAC)/Periodic Progress Meetings. The Government shall host the PAC within ten (10) working days of award. The Program Manager and any subcontractor personnel shall attend this post award conference. The Contractor shall present a proposed draft of the integrated management plan during the PAC. The Government shall explain the work effort under this contract to possibly include design, rationale, assumptions, and methodologies to be incorporated into performing the required tasks. In addition, the team shall discuss Government Furnished Equipment/Information (GFE/I) and scheduling of the initial monthly review. The Government and the Contractor shall use this meeting to communicate the roles and responsibilities of team members and present the planned approach to all members.

1.6.9. Meetings. The Contractor shall conduct monthly In Process Review (IPR) Meetings as specified in the contract terms and conditions. The Contractor shall prepare and deliver the meeting minutes within ten (10) working days after completion of meetings for review and comment by Government representatives. Use of Video Teleconference Centers (VTC)/Defense Connect Online (DCO) shall be considered for all meetings as a first consideration in lieu of travel.

1.6.9.1. Weekly Status Update Meetings. The Contractor shall conduct telephonic weekly status meetings throughout the TO. The purpose of these reviews shall be to apprise the Government of program status. The Contractor shall keep the Government informed of actions completed for the previous month and projected actions for the next month, to include but not limited to all completed/projected travel, meetings, conferences, and briefings.

1.6.9.2. 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 Contracting Officer 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.6.10. Key Personnel. All personnel under this contract shall have the applicable skills, education as required and experience to perform all tasks under this contract to meet the Government’s objectives. It is the Contractor’s responsibility to ensure that all personnel meet the appropriate labor categories to execute all contract requirements. All personnel shall be competent and have the required skills and aptitude in their respective fields in accordance with established commercial industry standards. In addition, the Contractor is required to fill any vacancies under this contract or subsequent task orders within ten business days. The following personnel are considered key personnel by the Government:

1.6.10.1 Program Manager. The Contractor shall provide a Program Manager 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 manager is absent shall be designated in writing to the contracting officer. The Program Manager or alternate shall have full authority to act for the Contractor on all contract matters relating to daily operation of this contract. The Program Manager or alternate shall be available between 8:00 a.m. to 5:00 p.m., Monday through Friday except Federal holidays or when the Government facility is closed for administrative reasons. The Program Manager (PM) shall possess an active Project Management Institute Project Management Professional certification, Defense Acquisition Workforce Improvement Act Level III certification in Program Management, or other recognized Information Systems program management certifications. The PM shall have relevant experience at a comparable level of responsibility in projects of similar size, scope and complexity. Experience working with the United States military is desired. Recent experience shall include a combination of managerial and technical skills demonstrating the ability to manage complex projects. The PM shall have knowledge of and experience with educational technologies that provide automated support to learning and learning management.

1.6.10.2 Site Chief/Systems Engineer. The Site Chief shall possess a Master of Science degree in Systems Engineering. The Site Chief must possess ten years of general computer network experience – that can include teaching such subjects at the university level, five years of experience with the Windows Operating Server & client systems, and two years experience performing complex software diagnosis. He or she shall perform high-level systems analysis, evaluation, design, integration, documentation, and implementation of very complex applications that require a thorough knowledge of administrative and technical skills. He or she shall direct and participate in all phases of system development with emphasis on planning, analysis, evaluation, integration, testing and acceptance phases. He or she shall apply higher-level business or technical principles and methods to very difficult technical problems to arrive at automated engineering solution. He or she shall design and prepare technical reports and related documentation, and make charts and graphs to record results. He or she shall prepare and deliver presentations and briefings as required by Task Order.

1.6.10.3. Managed Systems Engineer. The Managed Systems Engineer shall possess a Bachelor of Science degree in Computer Science. The Managed Systems Engineer must possess five years of general computer network experience – that can include teaching such subjects at the university level, five years of experience with the Windows Operating Server & client systems, and two years experience performing complex software diagnosis. He or she shall perform duties such as site surveys, architecture design, system evaluation, system analysis, and infrastructure assessment. He or she shall performs duties on tasks that require expertise in system/processor architecture, wired for management baseline, desktop management interface, SNMP, client/server architecture, operating systems, software applications, network protocols, routers, switches, remote access servers, and firewalls.

10.6.10.4. Software Architect – Senior. The Senior Software Architect shall possess a Master of Science degree in Computer Engineering or Computer Science. The Senior Software Architect must possess five years of general computer network experience – that can include teaching such subjects at the university level, five years of experience with the Windows Operating Server & client systems, and two years experience performing complex software diagnosis. He or she shall possess current CompTIA Security+SYO-401, and Certified Ethical Hacker (CEH) certifications that are needed to use toolsets required for this work. He or she shall develop new software code or make major enhancements to existing software. He or she may be called upon to lead a development team in diagnosis of highly complex software systems. He or she shall act as highest-level technical expert, addressing problems of systems integration, compatibility, and multiple platforms. He or she shall be responsible for assigned project completion and to perform feasibility analysis on potential future projects to management.

1.6.10.5. Software Architect – Intermediate. The Intermediate Software Architect shall possess a Bachelor of Science degree in Computer Engineering or Computer Science. The Intermediate Software Architect must possess three years of general computer network experience – that can include teaching such subjects at the university level, three years of experience with the Windows Operating Server & client systems, and one year experience performing complex software diagnosis. He or she shall help develop new software code or help make major enhancements to existing software. He or she may be called upon to participate in a development team in diagnosis of highly complex software systems. He or she shall act as a technical expert, addressing problems of systems integration, compatibility, and multiple platforms. He or she shall be responsible for assisting assigned project completion and to help perform feasibility analysis on potential future projects to management.

1.6.10.6. Software Engineer. The Software Engineer shall possess a Bachelor of Science degree in Computer Engineering or Computer Science. The Software Engineer must possess three years of general computer network experience – that can include teaching such subjects at the university level, three years of experience with the Windows Operating Server & client systems, and one year experience performing complex software diagnosis. He or she shall conduct or participate in multidisciplinary research and collaborates with equipment designers and/or hardware engineers in the planning, design, development, and utilization of electronic data processing systems software. He or she shall determine computer user needs; advise hardware designers on machine characteristics that affect software systems such as storage capacity, processing speed, and input/output requirements; design and develop compilers and assemblers, utility programs, and operating systems.

0.6.10.7. Technical Editor. The Technical Editor must possess two years of experience documenting complex software diagnosis. An Associate or Bachelor’s degree is preferred but not required – such degree shall not replace requirement for two years experience. He or she shall be responsible for content of technical documentation. He or she shall check technical documents for spelling, grammar and content problems (e.g., missing instructions or sections; redundant or unnecessary sections). Accuracy of content may fall under this position or the software engineer, depending on the expertise of the editor. He or she ensures that documents follow the style laid out in the organization's style guide and may also be responsible for maintaining the style guide. Technical Editor suggests revisions to the style guide as appropriate.

16.10.8. Personnel. The Contractor shall identify labor categories as it pertains to the Department of Labor’s Health & Welfare categories and projected hours to perform each task.

1.6.11. Identification (ID) of Contractor Employees. All contract personnel attending meetings, answering Government telephones, when briefing Government personnel, in Government e-mails, and working in other situations where their Contractor status is not obvious to third parties are required to identify themselves as such to avoid creating an impression in the minds of members of the public that they are Government officials. They must also ensure that all documents or reports produced by Contractors are suitably marked as Contractor products or that Contractor participation is appropriately disclosed. The Contractor shall provide each employee a Photo ID badge on contract start date or on employment start date. The ID badge shall be made of nonmetallic material, be easily readable, and shall contain the following minimum information:

1.6.11.1. Conduct of Personnel. The Contractor’s employee’s conduct shall be in accordance with DoD-5500 7-R Joint Ethics Regulations. The removal from the job site or dismissal from the premises shall not relieve the Contractor of the requirement to provide sufficient personnel to perform the services as required by this statement of work. IAW Army Regulation and Air Force Instructions, the authority of the Installation Commander to control and deny entry to all or part of the installation is absolute. The individual concerned has no right to appeal.

1.6.12. Data Rights. The Government has unlimited rights to all documents/material produced under this contract. All documents and materials, to include the source codes of any software, produced under this contract shall 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 may not be used or sold by the Contractor without written permission from the Contracting Officer. All materials supplied to the Government shall 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.6.12.1. Government Technical Data, Computer Software Rights and Rights in Works. The Government shall retain unlimited rights (See Defense Federal Acquisition Regulation Supplement (DFARS) 252.227-7013 and 7014) to the software and technical data developed under this contract that are not otherwise designated as "works" by the Contracting Officer, with "works" as defined in DFARS 252.227-7020.

1.6.12.2. Commercially or Independently Developed Software. The Contractor shall ensure that the license for the software necessary for performance of the work is transferable to the Government at no additional cost. The Contractor shall prepare and submit a plan to transfer the software and licenses to the Government thirty (30) working days prior to contract completion or termination.

1.6.12.3. Ownership. All data, materials, data/databases, files, graphics, broadcasts, photographs, software, codes, equipment, compact disks (CD)s, and other deliverables provided by the Government or developed under this contract shall remain the property of the Government unless part of the public domain or previously owned or copyrighted by other sources.

1.6.12.4. Third Party Copyrighted Data. The Contractor shall not incorporate, without the written approval of the COR, any copyrighted works to be delivered under this contract unless the Contractor is the copyright owner or has obtained for the Government the necessary license rights prior to delivery of such works.

1.6.12.5. Records Keeping Maintenance. The Contractor shall maintain, and support the maintenance of accurate files of documentation, records, and reports required under the terms of this contract IAW AR 25-1, Army Knowledge Management and IT, and AR 25-400-2, Army Records Information Management System.

1.6.13. Organizational 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 OCI as defined in Federal Acquisition Regulation (FAR).

The Contractor shall notify the Contracting Officer 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 Contracting Officer to avoid or mitigate any such OCI. The Contractor’s mitigation plan will be determined to be acceptable solely at the discretion of the Contracting Officer and in the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may effect 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.6.14. Invoicing. Wide Area Workflow shall be implemented IAW Defense Federal Acquisition Regulation (DFAR) 252.232-7003 Electronic Submission of Payment Requests and Department of Defense (DD)250, Receiving Reports. Manual invoices will not be accepted.

PART 2

DEFINITIONS & ACRONYMS

2. Definitions and Acronyms:

2.1. Definitions:

2.1.1. 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.2. 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.3. Contracting Officer’s Representative (COR). An employee of the U.S. Government appointed by the contracting officer to administer the contract. Such appointment shall be in writing and shall 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.4. Defective Service. A service output that does not meet the standard of performance associated with the Performance Work Statement.

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

2.1.6. Key Personnel. Contractor personnel that are evaluated in a source selection process and that may be required to be used in the performance of a contract by the Key Personnel listed in the PWS. 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.7. Physical Security. Actions that prevent the loss or damage of Government property.

2.1.8. Quality Assurance. The Government procedures to verify that services being performed by the Contractor are performed according to acceptable standards.

2.1.9. Quality Assurance Surveillance Plan (QASP). An organized written document specifying the surveillance methodology to be used for surveillance of Contractor performance.

2.1.10. 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.11. Subcontractor. One that enters into a contract with a prime Contractor. The Government does not have privity of contract with the subcontractor.

2.1.12. Work Day. The number of hours per day the Contractor provides services in accordance with the contract.

2.1.13. Work Week. Monday through Friday, unless specified otherwise.

2.1.14 Acronyms:

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3. Government Furnished Items and Services:

3.1. Government Furnished Equipment/Information (GFE/I). The Government shall provide the Contractor access to any non-classified existing target platform documentation, training materials, and any additional supporting documents, publications, and technical manuals required to support this contract. The Contractor shall return all GFI to the Government within 10 calendar days after completion of work.

3.1.1. Government Furnished Property. The Government will provide, CAC cards, office space, office supplies, telephone service, workstations, computers, and storage space at the place of performance. The Government’s property shall be used only in performance of required tasks, or unless otherwise approved by the KO.

3.1.2. Government Furnished Software. The Contractor will be provided with software equivalent to that used by Government personnel, as required by the contract.

3.1.3. Government Furnished Information. The Contractor will be provided with information equivalent to that used by Government personnel, as required by the contract. Any Government information furnished to the Contractor is for “Official Use Only” and limited to this scope of this contract.

3.2. Meetings. The Contractor shall conduct meetings as specified in the contract terms and conditions and task order. The Contractor shall prepare and deliver the meeting minutes within ten (10) working days after completion of meetings for review and comment by Government representatives. Use of VTC and/or DCO shall be considered for all meetings as a first consideration in lieu of travel.

PART 4

SPECIFIC TASKS

4. Specific Tasks:

4.1. Basic Services. These tasks support the development of documentation for identified issues within existing Army DL fielded on ALCMC platforms, and being developed for fielding on ALCMC platforms. The deliverables associated with these tasks will serve as the basis for Army DL development and fielding specification documents authored by The Office of the TCM-TADLP and released to the Army DL development community. Contractor personnel shall be required to perform activities associated with but not limited to the tasks identified below. Performance of these tasks shall result in specified deliverables to the Government.

4.2. Task 1: Diagnose – The Government will provide to the Contractor pieces of content with identified issue(s). The Contractor shall determine the source of the issue and provide a documented explanation of the issue and corrective measures to be followed.

· The Contractor shall identify browser issues related to type and version that may cause conflict with the proper functioning of Army DL content.

· The Contractor shall identify browser plug-in and add on issues that may cause conflict with the proper functioning of Army DL content.

· The Contractor shall identify configuration settings that may cause conflict with the proper functioning of Army DL content.

· The Contractor shall identify scripting errors that may cause conflict with the proper functioning of Army DL content.

· The Contractor shall identify and categorize other issues that may cause conflict with the proper functioning of Army DL content.

4.3. Task 2: Advisement – The Contractor shall provide solutions based on prior diagnosis. The solutions shall include functioning samples. Functioning samples are code that has been applied in content that plays on ALCMC delivery platforms.

· The Contractor shall document solutions using Government approved documentation format.

· The Contractor shall generate code to correct issues identified through diagnosis and analysis.

· The Contractor shall validate proper functioning of code through testing on specified ALCMC delivery platforms.

· The Contractor shall build and maintain a code repository based on a Government approved format.

· The Contractor shall generate advisements on issues with high priority content as directed by the Government on as needed basis.

· The Contractor shall generate advisements based on research of current and emerging DL anti-cheating techniques.

4.4, Task 3: Research – The Contractor shall explore current and existing standards, specifications and recommendations for DL development and delivery. The Government shall provide access to current copies of all Army regulations, pamphlets, guides and documentation applicable to Army DL. Research findings shall be provided to the Government in the form of research reports.

· The Contractor shall review World Wide Web Consortium (W3C) recommendations to identify areas that are applicable to Army DL development and delivery.

· The Contractor shall research and identify web standard, specification, and recommends validation tools that are applicable to Army DL.

· The Contractor shall research current Sharable Content Object Reference Model (SCORM) related strategies.

· The Contractor shall research current and emerging DL anti-cheating techniques.

· The Contractor shall research current and emerging DL delivery methods including but not limited to learning management systems, mobile web, and mobile applications.

4.5. Task 4: Migration – The Contractor shall review content being migrated from expiring Learning Management Systems (LMSs) and ensure proper technical functionality on the ALCMC delivery platforms. Documentation of the corrective measures shall be provided to the Government in the form of a report.

· The Contractor shall review documented technical issues identified in migration content and determine and document corrective measures.

· The Contractor shall validate the corrective measures on the development and test environment for the ALCMC delivery platform.

· The Contractor shall implement validated corrective measures within affected content packages.

· The Contractor shall assist the Government with specific short-duration courseware related tasks.

4.6. CONTRACTOR MANAGEMENT REPORTING (CMR). The Office of the Assistant Secretary of the Army (Manpower & Reserve Affairs) operates and maintains a secure Army data collection site where the Contractor shall report ALL Contractor manpower (including subcontractor manpower) required for performance of this contract. The Contractor shall completely fill in all the information in the format using the following web address https://Contractormanpower.army.pentagon.mil. The required information includes: (1) Contracting Office, Contracting Officer, Contracting Officer’s Technical Representative (COTR) or also known as the Contracting Officer’s Representative (COR); (2) Contract number, including task and delivery order number; (3) Beginning and ending dates covered by reporting period; (4) Contractor's name, address, phone number, e-mail address, identity of Contractor employee entering data; (5) Estimated direct labor hours (including sub-Contractors); (6) Estimated direct labor dollars paid this reporting period (including sub-Contractors); (7) Total payments (including sub-Contractors); (8) Predominant Federal Service Code (FSC) reflecting services provided by Contractor (and separate predominant FSC for each sub-Contractor if different); (9) Estimated data collection cost; (10) Organizational title associated with the Unit Identification Code (UIC) for the Army Requiring Activity (the Army Requiring Activity is responsible for providing the Contractor with its UIC for the purposes of reporting this information); (11) Locations where Contractor and sub-Contractors perform the work (specified by zip code in the United States and nearest city, country, when in an overseas location, using standardized nomenclature provided on website); (12) Presence of deployment or contingency contract language; and (13) Number of Contractor and sub-Contractor employees deployed in theater this reporting period (by country). As part of its submission, the Contractor shall provide the estimated total cost (if any) incurred to comply with this reporting requirement. Reporting period shall be the period of performance not to exceed 12 months ending September 30 of each government fiscal year and must be reported by 31 October of each calendar year. Contractors may use a direct XML data transfer to the database server or fill in the fields on the website. The XML direct transfer is a format for transferring files from a Contractor’s system to the secure website without the need for separate data entries for each required data element at the website. The specific formats for the XML direct transfer may be downloaded from the website.

PART 5

APPLICABLE PUBLICATIONS

5. Applicable Publications (Current Editions):

5.1. Applicable Documents. The following documents provide guidance to include, compliance specifications for assistance during the diagnostic and advisement process, as well as platform configurations for the content.

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

ATIA Technical Architecture Profile v1.4, <http://www.atsc.army.mil/tadlp/contractors/capdl/config/index.asp>, 26 Apr 01.

Advanced Distributed Learning (ADL™) Initiative’s Sharable Content Object Reference Model (SCORM®), 2004 download from the Advanced Distributed Learning SCORM® 2004 Documentation Download page, <http://www.adlnet.gov/resources/SCORM-2004-3rd-Edition-Specification?type=technical_documentation> Version SCORM® 2004 – 3rd Edition.

Business Rules, Best Practices and Examples for Army SCORM® 2004 Compliant Courseware, <http://www.atsc.army.mil/tadlp/contractors/capdl/compliance/scorm_business_rules.asp Note: Compliance is required with the Army Business Rules contained in this document. Best Practices and Examples are provided for guidance only.

ALMS Content Developer’s Standards, Guidelines and Best Practices https://www.dls.army.mil/pdf/ALMS%20Standards,%20Guidelines%20and%20Best%20Practices.pdf, the latest version at time of contract award.

Product Development Requirements. The latest version at time of Task Order Request. These specifications cover the product development specification for both the web version and the CD-ROM version of IMI self-paced courseware. <http://www.atsc.army.mil/tadlp/contractors/capdl/compliance/product_reqs.asp>

U.S. Army Acceptance Criteria for Incremental Testing and Fielding of SCORM® 2004 Compliant Courseware, <http://www.atsc.army.mil/itsd/imi/Accept_Criteria.asp>, the latest version at time of Task Order Request as required by TO.

5.3. All requirements included in this contract 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 under this contract as required by DFARS 252.227-7020.

5.4. Personally Identifiable Information. The use of social security numbers and other personally identifiable information (PII) is forbidden in web based courseware. With the rise of personal identity theft, we must 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

5.5. Guidance Documents. The contractor shall ensure all work conforms to the guidance in the following:

Military Performance Specification 29612B (MIL-PRF-29612B), <http://www.atsc.army.mil/itsd/imi/documents/MilHdbk/MIL-PRF- 29612B.pdf>

5.4. The Contractor must abide by all applicable regulations, publications, manuals, and local policies and procedures.

PART 6

ATTACHMENT/TECHNICAL EXHIBIT LISTING

6. Attachment/Technical Exhibit List:

6.1 Attachment 1/Technical Exhibit 1 – Performance Requirements Summary (PRS)

Corrective Actions

· Sufficient personnel, material, equipment, facilities, and services provided to accomplish contract/task order requirements PWS 3

· Program and Project Managers available and empowered IAW PWS 1.6.10-1.6.11.1

· KO and COR review to identify trends

· COR and Government technical personnel notify contractor Project Manager of observed late delivery and poor quality. Provide memo for COR file.

· KO and COR meet contractor Program Manager quarterly to identify trends and issues. Contractor prepares a plan to correct problems.

· Documentation in contract files and CPARS as appropriate

· KO and COR review multiple task orders to identify trends Same as PRS #1

PRS #3.

Deliver on time

· QCP within 30 days of award.

· CMR reporting NLT 31 Oct annually

· Adherence to IMS

· KO and COR monitor contract level deliverables.

· QA including COR monitor contract.

Same as PRS#1

PRS #4.

Manage data

· No instances of inability to use data due to copyright infringement claims.

· Withhold payment for deliverables until they meet requirements.

PRS #5.

Deliver Quality Products Quality:

· Quality Control Plan (QCP) provided IAW PWS 1.6.1 and 1.6.2

· Implementation of QCP results in delivery of quality products.

· Withhold payment for deliverables until they meet requirements.

PRS #6.

Respond Quickly

· Proposal complies with timelines IAW request for proposal.

· Products delivered as scheduled

· KO and COR monitor response times.

· Technical Evaluation Board determine if proposed delivery times match RFP requirements

· COR monitor execution Do not award contract if proposal does not comply with requirements.

During TO execution:

· Notify contractor Project Manager of required corrections.

· Withhold payment for deliverables until they meet requirements.

PRS #7.

Safeguard Sensitive Information

· No reported instances of failure to comply.

· Secure sensitive/classified information.

· Notify contractor Project Manager of required corrections

The following listing provides various types of Surveillance as examples to select from and should not be included on the final document:

Random Sampling: Appropriate for frequently recurring tasks. Evaluate randomly selected samples of the lot to determine the acceptability of the entire lot.

Random Inspection Guide, Method of surveillance, Lot size, Sample size, Performance requirement, Sampling procedure, Inspection procedure 100 Percent Inspection: Appropriate for tasks that occur infrequently. Inspect and evaluate performance each time task is performed Periodic Surveillance: Evaluation of samples selected on other than 100% or statistically random basis. (i.e., monthly, quarterly, semi-annually etc.)

Validated Customer Complaint: Complaints must be validated.

6.2. Attachment 2/Technical Exhibit 2 – Deliverables Schedule

30 days

10 days after IPR Meeting

Weekly

Biweekly

60 days

Biweekly

Bimonthly

60 days

Biweekly

Bimonthly