Sample_PWS.docx

STATEMENT OF WORK

TITLE: Human Systems Integration (HSI) Field Evaluation Services for Army System Acquisition

C.1. SCOPE. This Statement of Work (SOW) identifies the efforts required to provide general field services to support the US Army Research Laboratory (ARL), Human Research and Engineering Directorate (HRED) as it conducts the continuous evaluation of various test & evaluation (T&E) programs. These services are required to support the directorate’s HSI evaluation efforts including the areas of Event Planning and Execution, System Analysis, and Data Base Support. These services will result in technical reports and documentation that support the HRED evaluation mission, and focus in the area of system analysis and data base support for acquisition systems.

C.1.1 BACKGROUND. The ARL-HRED is providing support to the U.S. Army Test and Evaluation Command (ATEC) and Project Managers (PMs) during Operational Assessments (OA) of scheduled systems to meet the acquisition time line for maneuver or business systems. Manpower, personnel, training, human factors, safety, cognitive readiness, situational awareness, anthropometric and workload are key HSI assessment areas of the analysis. This effort requires implementation of a systems approach for examining usability, functionality, and soldier performance from an operator and staff perspective. The approach has three steps. The first step is to identify tasks and behavioral characteristics that are associated with effective performance at the operator, staff, and organizational level for the system being tested. The second step is to develop a framework for measuring how well technology provides the usability, functionality, and performance required at each of the three levels. The third step is developing and integrating validated instruments to implement the measurement framework that is administered in the field. Both qualitative and quantitative data support the HSI assessment. These instruments are used to obtain a general understanding of the knowledge, skills and abilities that are needed by operators or battle staff while using these platforms for monitoring and conducting military missions. They are also used to assess the usability of the platform system design in helping the soldiers complete their tasks.

The continuous evaluation of the systems covered or added in this SOW will employ results from a combination of vendor (contractor) tests, government developmental tests, logistics/HSI demonstrations, and operational tests. Program documents include the operational requirements document (ORD), Test and Evaluation Master Plan (TEMP), and the Operational and Organizational (O&O) plan. Test and Evaluation (T&E) documents include ATEC’s System Evaluation Plan (SEP), the Baseline Correlation Matrix (BCM) and Data Source Matrix (DSM), Emerging Insights (Quick-Look) Report and System Evaluation Report (SER), various Event Design Plans (EDP), and Detailed Test Plans (DTP).

C.1.1.1 The first system that is being evaluated is the General Fund Enterprise Business System - Secrete (GFEBS S). GFEBS-S, the Army’s web-enabled financial, asset and accounting management system will standardize, streamline and share critical secrete data across the active Army, the Army National Guard and the Army Reserve. GFEBS-S will subsume numerous legacy systems. This event will require numerous developmental test and field exercises.

C.1.1.2 The second system is the Global Combat Support System - Army Increment II (GCSS-A (II)) is being developed to provide accurate and consistent supply chain information from the depots to the front line. The new browser-based system the US Army's Standard Army Management Information Systems (STAMIS), the current suite of logistics systems. A COTS hardware solution using Windows NT, it will enhance interfaces with other Combat Service Support automated systems to reduce the amount of data entry required. It is the tactical element of the US Army's Single Army Logistics Enterprise (SALE).GCSS-A (F/T) will create a technical environment and process to integrate economically existing computer-based systems software and hardware using the Common Operating Environment (COE) and shared data environment. It will also expand the GCCS Common Operational Picture (COP) to accommodate combat support information, and will provide 'split base-reach back' capabilities from the foxhole to the sustaining base to allow the combatants to be 'deployed/sustained' by electronic means.

C.1.2 OBJECTIVE. To acquire contractor services to perform field collection, data analysis, and to generate field result reports.

C.2. REQUIREMENTS. The Contractor shall provide services in accordance with the tasks described below to provide continuous evaluation of the systems.

C.2.1 EVALUATION EVENT PLANNING AND EXECUTION.

C.2.1.1 Evaluation Strategy Planning. The Contractor shall develop, update, edit, and review planning briefings such as the Early Strategy Review (ESR), Rock Drill, Concept Integrated Product Review (IPR), and Lens Chart development.

C.2.1.2 System Evaluation Plan (SEP). The Contractor shall develop the HRED evaluation strategy for the continuous evaluation of the specified system. The Contractor shall develop, edit- and review - updates of the HSI portion of the SEP for the specified system. The Contractor shall ensure that particular emphasis is placed on the continuation of the evaluation strategy, analysis methodology, and the data management process. The Contractor shall conduct the analysis planning, to include developing and revising the evaluation focus areas (EFA), measures of effectiveness (MOE), measures of performance (MOP) and data requirements. The Contractor shall provide input to the development of a MOP Methodology Plan for each test event. This shall entail the combined use of multiple data sources as well as the design and execution of integrated testing. The Contractor shall develop survey and interview question sets for each assessment. The Contractor shall provide updates on verification, validation, and accreditation of instrumentation and simulation planned for these events.

C.2.1.3 Deliverables. . The Contractor shall submit all deliverables via electronic disk or secure communications only.

C.2.1.3.1 Briefings and Briefing Material. The Contractor shall provide one draft of each briefing product for Contracting Officer’s Representative (COR) review and modification, followed by one final copy. Government comments provided back to the Contractor are required to be incorporated into the draft product within two business days of receipt and the Contractor shall submit the updated documents to the COR as the final product. The Contractor shall deliver the briefing material via soft copy (electronic media) to the COR within 4 (four) business days.

C.2.1.3.2 Input to System Evaluation Plan. The Contractor shall provide input and updates to the SEP not later than (NLT) four (4) business days after request by the COR. The Contractor shall deliver the plan in an electronic format compatible with Microsoft Office Word software. Upon receipt of remarks or comments provided by the COR, the Contractor has three (3) days to incorporate and update the document. Deviation beyond the number of draft and final submission require COR written approval. The Contractor shall deliver the briefing material via soft copy (electronic media) to the COR.

C.2.2 SYSTEM ANALYSIS.

C.2.2.1 Continuous Evaluation The Contractor shall analyze the effectiveness, suitability, and survivability of a system specified by the COR, with a concentration upon the Suitability Focus Area HSI evaluation. The Contractor shall assess data for the Critical Operational Issues and Criteria (COIC) and Additional Issues (AI) defined by the government and provided as Government Furnished Information (GFI) as appropriate through the use of developmental phase reports, technical test data and other sources. The Contractor shall conduct Operational Testing and Assessments Critical Design Review, Production Qualification/Verification Test events and User Demonstration Assessment to gather data towards system characterization and provide an estimate in contractor format, of the system’s progress towards entry into formal Operational Testing (OT).

C.2.2.2 Developmental and Operational Testing. The Contractor shall witness developmental and operational test events in order to collect data which support acquisition decisions and identify anomalies or potential problem areas that can degrade performance as instructed by the COR. The operational test includes Initial Operational Test and Evaluation (IOTE), or Limited User Tests (LUT). The Contractor shall note the method of test, instrumentation and data collection used, and lessons-learned from the testing methodology. The Contractor shall determine which technical test instrumentation or methodology to utilize in operational test planning. The Contractor shall note the test item configuration and how it differs from the production configuration and the degree to which test results from this configuration are expected to be representative of the performance of the production system. The Contractor shall prepare and deliver results of its Operational Test Readiness Review (OTRR) process.

C.2.2.2.1 Developmental Tests. The Contractor shall review the developmental test planning documents and analyze data and reports to provide a technical assessment of the system’s readiness and maturity for Operational Testing and evaluation. as requested by the COR. The Contractor shall address the technical measures of effectiveness and performance outlined in the SEP.

C.2.2.3 Draft System Evaluation Reports / System Analysis Reporting. The Contractor shall analyze data and shall develop input for analysis products (reviews / briefings / reports). The Contractor shall develop draft reports with scored data based on the format required by DA PAM 71-3 and/or ATEC PAM 73-1 provided as GFI as applicable. The Contractor shall prepare briefings for COR review.

C.2.2.4 Deliverables. . The Contractor shall submit all deliverables via electronic disk or secure communications only.

C.2.2.4.1 Briefings and Briefing Material. . The Contractor shall provide one draft of each briefing product for Contracting Officer’s Representative (COR) review and modification, followed by one final copy. Government comments provided back to the Contractor are required to be incorporated into the draft product within two business days of receipt and the Contractor shall submit the updated documents to the COR as the final product. Deviation beyond the number of draft and final submission require written COR approval. The Contractor shall deliver the briefing material via soft copy (electronic media) to the COR within 4 (four) business days.

C.2.2.4.2 Technical Notes, System Evaluation Report (SER), System Assessments (SA). The Contractor shall provide details of the effort performed in the continuous evaluation of the system for incorporation in post-trip reports. The Contractor shall enter test observations, analysis, and results into an evaluation database provided as GFP as required by the COR. The Contractor shall deliver draft technical analysis reports; provide input to T&E documents detailing summary test planning, results, and other system data and information 7 days after testing is complete.

C.2.3 EVALUATION FIELD TEAM EFFORT.

C.2.3.1 Data Collection and Analysis During the Experiments. The Contractor is required to go to a test sight to observe and collect data upon direction by the COR. The Contractor shall use Access and reduce data, perform analysis, summarize data, develop insights, conduct interviews and prepare briefings during the test event. The Contractor shall provide in-progress analysis and make insights to the COR during the test event. The Contractor shall employ the same individual who developed the SEP to observe the actual experiment.

C.2.3.2 Performance Analysis. The Contractor shall observe testing of the specified system at the test site and shall gather data in its own format in the areas of organization, doctrine, tactics, survivability, and threat. The Contractor shall collect technical performance data from events such as Critical Design Reviews, Contractor Testing, User Assessments, and PM testing, such as Production Qualification Test (PQT) and other available tests or simulations.

C.2.3.3 Evaluation. The Contractor shall provide input to a integrated process team for a system program manager specified by the COR. The Contractor shall review system software/hardware documentation to ensure it accurately describes the product being developed and tested. The Contractor shall collect and analyze data on system software products to assess software progress and maturity. The Contractor shall research the status of embedded system software development activities and review the status of development in accordance with DA PAM 73-7 Software Test and Evaluation Guidelines provided as GFI. The Contractor shall identify inconsistencies or discrepancies in documentation, traceability, or testability of software requirements by comparing the documentation to the actual system. .

C.2.3.4 Analytic and Reduction. The Contractor shall reduce and analyze data prepare reports based on GFI; and provide continuous evaluation at the test site and after the test, at any location directed by the COR.

C.2.3.5 Document Review. The Contractor shall review system-related documents in concert with the framework of other system-related documents provided as GFI. Examples of such documents include:

Capability Development Document (CDD) Combat Developer’s Analysis (CDA) Critical Operational Issues and Criteria (COIC) Development Test Plan (DTP) Failure Definition and Scoring Criteria (FDSC) Initial Capability Document (ICD) Mission Needs Statement (MNS) Operational Requirement Document (ORD) System Threat Assessment Report (STAR) Simulation Support Plans Test and Evaluation Master Plan (TEMP) V&V Reports Logistics/HSI Demonstration Plan New Equipment Training (NET) Plan and the Program of Instruction (POI) Test System Technical, Operator and/or Maintainer Operating Manuals and supporting TTP materials

C.2.3.6 Deliverables. The Contractor shall submit all deliverables via electronic disk or secure communications only.

C.2.3.6.1 The Contractor shall document critical events throughout the test. At the completion of each trial, the Contractor shall document observations and shall provide input to the initial insight report and briefing packet.

C.2.3.6.2 Document Review. As a result of the document reviews the contractor shall submit comments in accordance with DA Form 2028 format, or other format approved by the COR and provided as GFI such as a format similar to the Army Requirements Oversight Council document comments matrix. The Contractor shall submit comments to the COR within seven (7) business days of receipt of the document.

C.2.4 DATA BASE EFFORT.

C.2.4.1 Data Base Construction and Tools. The Contractor shall create, populate and query the ATEC database of information about the system provided as GFI. The Contractor shall create database tools to perform data storage, reduction, analysis and summery on data collected during a T&E event such as a test or OA, and provide analysis and reporting of system performance.

C.2.4.2 Data-Mining. The Contractor shall perform data-mining of previous documentation to ensure completeness and consistency with relationship’s identified between data and requirements viz a viz the Operational Test Command information provided as GFI. The Contractor shall have access and support share-point processes related to the evaluation.

C.2.4.3 Database Programming. The Contractor shall plan for the development of routines and procedures to support the calculation of each Measure of Performance (MOP) and the evaluation of their respective Critical Operational Issue and Criteria (COIC) and the Additional Issue(s) (AI). The Contractor shall conduct a complete end-to-end demonstration prior to the start of any applicable test event. The Contractor shall modify and execute the MOP calculation programs. The Contractor shall ensure the plan includes provisions for calculations to be executed at the test or event site (i.e. Quick-Look / Emerging results).

C.2.4.4 Project Management. The Contractor shall develop and maintain an up-to-date Microsoft Project file which contains the information needed to manage the key events and products for the systems under evaluation as the continuous evaluation moves toward completion of the System Evaluation Report.

C.2.4.5 Deliverables. Contractor shall submit all deliverables via electronic disk or secure communications only.

C.2.4.5.1 Data Bases. During test events, the Contractor shall submit an electronic copy of the Evaluation Event Data Base to the COR, at least once per day, or within two-hours of receipt of the request by the COR, including all relevant data from the associated event up to that point in time. The Contractor shall update the Evaluation Event Data Base as new data is obtained by the evaluation team during tests or other events in a format that allows for queries for system evaluation purposes.

C.2.4.5.2 Data Queries. The Contractor shall submit the results of data queries of the Evaluation Event Data Base or other databases used by the COR and provided to the contractor during test events, in formats such as tables, charts, spreadsheets, or other similar media.

C.2.4.5.3 Data Analysis. The Contractor shall provide tables, graphs, briefings, data bases or other formats which show the results obtained from the comparison or crosswalk of data collected to the requirements which will allow the Analysis Support Team (AST) to perform analysis and arrive at conclusions on the capabilities and limitations of the specified system.

C.3. PROGRESS REPORTING. The Contractor shall provide status reports on a monthly basis to the COR. These reports shall detail activities for the month, projected activities, problem areas, and monthly, cumulative, and projected expenditures; this includes the status of funds, programs, and test documents. The Contractor shall deliver monthly reports by the 15th business day of each month for the preceding month.

C.4. TRAVEL.

C.4.1 Travel by Contractor personnel will require prior approval from the COR. Performance locations include the contractor's site, and other sites such as National Training Center in Ft. Irwin, CA, Ft. Monmouth, NJ, Ft. Lewis, WA, Ft. Polk, LA, and Ft. Stewart, GA. One person may be required up to 65 days for one trip.

C.5. TRAINING.

C.5.1 No additional academic training of contractor personnel is required to execute this SOW. In the event that system-specific training is required to familiarize contractor personnel with system design or operational concepts, the contractor shall obtain approval of that training from the COR.

C.6. GOVERNMENT FURNISHED ITEMS IN GENERAL.

C.6.1 The COR will provide the Contractor with supporting documentation for the assigned system/program effort within 10 (ten) business days. The COR will arrange for the Contractor to gain access to meetings, briefings, orientations, and test activities on a need-to-know basis.

C.6.2 All Government furnished reference material, information, data, equipment, hardware, and software provided to the Contractor will remain the property of the U.S. Government.