Statement of Work.docx

Statement of Work (SOW) Operational and Training Services as of April 29, 2021 Army Research Laboratory (ARL)

C.1 Background The Army Research Lab (ARL) Materials Development and Transition Branch (MDTB) performs a large amount of mechanical testing, with twelve (12) machines focused on mechanical testing using GRANTA MI-based software. These machines can run continuously and generate thousands of individual test results per week. At present though, ARL has no ability to examine current data without expending significantly labor-intensive and manual efforts. A materials database will automate this required capability. The operational and training services required on GRANTA –MI based solution described in this SOW is highly automated, requiring no additional manual intervention beyond copying the test results to the correct location. With these services, ARL would be able to focus more on material research and less on the data management. Likewise, an inherent attribute of the data management database system is it will archive all data collected from the mechanical testing machines.

C.2 Objective and Scope This SoW will focus on delivering a configured GRANTA MI database and corresponding set of Python scripts to perform the automated import. The scripts will include an initial configuration to support the format of example files, and these configurations will be extensible to allow ARL to modify them as the test programs on each test frame are modified. Enhanced support, which includes personalized training and python scripts (programming), shall be available to ARL immediately following the delivery of the script to resolve any minor issues identified as the solution is rolled out.

This SoW also provides training, allowing ARL to make the full use of the GRANTA MI suite to browse, search, and report on the imported test data. This training shall allow ARL to manage the imported data through the web browser and to export the data as an input for data analysis.

This SoW reflects current ARL policies and practices, allowing offerors to propose and price a solution to known requirements. It is anticipated that specific training requirements and resulting objectives may change over the life of this contract. These changes may result in ARL modifying this contract to incorporate in-scope changes.

C.3 Point of Contact (POC) The ARL POC shall facilitate support requirements and coordination with ARL support staff as required in execution of the technical requirements over the period of performance in compliance with ARL IT and human resource requirements.

C.3 Technical Requirements

The following paragraphs outline the potential efforts for accomplishing the objective and scope of this effort. Under this contract, the Government may issue tasks for efforts provided below.

C.3.1 Automated Data Import This work package shall focus on automating the import of Bluehill CSV tensile data generated by ARL. A Python script shall be developed that polls a networked file share nightly. If the script finds data in this location it will process the data files, extract the relevant information, create new records in GRANTA MI, and then archive the imported files on ARL systems. The data generated by the Bluehill test frame software shall contain all information required to define the structure of the database, in addition to the raw data itself. The Python script shall also be flexible enough to import data from all tensile test frames in use at ARL. The Python script shall be configurable, allowing fields and channels in the Bluehill CSV output to be mapped to attributes in GRANTA MI. Units shall be fixed, such that a field with a certain name is always exported in the same units. The script shall import data from the CSV output and will not extract data from the proprietary Bluehill binary files.

C.3.2 Training and Support To ensure ARL can extract as much value as possible from the GRANTA MI software, training and support shall be given at both the end-user and administrator level to key personnel. This shall enable them to maintain the tools delivered as part of this project and to develop their own tools for importing, exporting, and processing data stored in GRANTA MI.

In advance of the training, the contractor shall provide a summary of the session so ARL attendees can decide if the training is relevant for their specific GRANTA MI role. Each training session shall be provided to up to 20 attendees. Training materials shall be supplied in PowerPoint format, and support will be given to ARL to allow them to generate their own internal training courses and materials for their end-user community if required.

C.3.2.1 Support Sessions

The contractor shall provide 10 support days, to be used as required on an ad-hoc basis, which will be used to help troubleshoot any issues that occur in with the GRANTA MI Software. Type of ad hoc support will be tailored to meet the specific needs of ARL employees to learn, use and design databases using GRANTA–MI. For example these specific needs may include but not limited to;

· Helps user efficiency, in code development.

· Helps ensure system efficiency and creates best practice.

· Ensures consistent user practice.

· Helps with users skills.

· Opportunity to learn about new functionality and processes.

C.3.2.2 Training Sessions

The training will be broken into the following 5 sessions, which shall cover the following topics:

Session 1: Finding data in GRANTA MI

· Browsing Data

· Searching Data

· Reporting on Data

Session 2: Importing data into GRANTA MI

· Excel Import

· Text Import

Session 3: Building GRANTA MI database

· Structuring data

· Data types

· Control of Data, including Access Control and Version Control

Session 4: user Experience modifications

· Homepages

· Profiles

Session 5: Python Scripting API

C.3.3 Project Management This Work Package shall focus on the organizational aspects of the project, including reviewing and refining the technical requirements, documenting the outcomes of the project kick-off workshop in a solution design, and initializing the project processes and regular meetings. The project kick-off workshop is typically delivered as an on-site meeting but can be performed remotely if required via WebEx die to COVID-19 restrictions.

C.4 Deliverables

C.5 SECURITY REQUIREMENTS/ACCESS TO FACILITY

C.5.1 Access and general protection/security policy and procedures.

This standard language is for contractor employees with an area of performance within Army controlled installation, facility, or area. Contractor and all associated sub-contractors employees shall provide all information required for background checks to meet installation access requirements to be accomplished by installation Provost Marshall Office, Director of Emergency Service or Security Office. Contractor workforce must comply with all personal identity verification requirements (FAR clause 52.204-9, Personal Identity Verification or Contract Personnel) as directed by DoD, 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.

C.5.2

For contractors that DO NOT require CAC, but require access to a DoD facility or installation. Contractor and all associated sub-contractors employees shall comply with adjudication standards and procedures using the National Crime Information Center Interstate Identification Index (NCIC-III) and Terrorist Screening Database (TSDB) (Army Directive 2014-05/AR 190-13, applicable installation, facility and area commander installation/facility access and local Security policies and procedures (provided by Government Representative), or, at OCONUS locations, in accordance with status of forces agreements and other theater regulations.

C.5.3 The Contractor will coordinate with the COR, to gain access to the facility as required.

image1.emf