W9124J-18-R-0008,_Atch_5,_ISR_Core_Support_Tasks,_13_Feb_18.pdf

Attachment 5

ISR Core Support Tasks

Correlates to PWS Paragraphs 5.1., 5.2., 5.3., 5.5., 5.6., 5.7.

5.1. Basic Services. The Contractor shall perform the following tasks to support OACSIM as outlined in this PWS.

5.1.1. The Contractor shall communicate both orally and in writing with ISR program stakeholders to gather or provide information to successfully conduct the ISR Data Collection. The Contractor shall communicate in areas such as requirements for upcoming data collections, reporting organizations and alignment with other ACSIM business systems, utilization of data, analysis of data, use of ISRWeb, comprehension of ISR data and ratings, clarity on supporting documentation, metric development, inspection criteria, training opportunities, site visits, and data requests.

5.1.2. The Contractor shall deliver, maintain, and assist in developing the following that are provided for the ISR

Community to utilize:

5.1.2.1. Technical assistance in the form of one-to-one training (up to 3 sessions per quarter);

5.1.2.2. Information papers (not more than 5 per quarter);

5.1.2.3. Informational newsletter (one per quarter); and

5.1.2.4. Frequently Asked Questions (FAQs) (updated weekly).

5.1.3. The Contractor shall also maintain technical references and manuals such as:

5.1.3.1. Implementing instructions (one per ISR component annually with up to one revision per ISR component);

5.1.3.2. ISR-I Component Cost Factors and Mission Weights (updated annually);

5.1.3.3. ISR-I Reports and Graphs Handbook (updated annually);

5.1.3.4. ISR-MC Sortable Database (updated annually);

5.1.3.5. ISR-S Performance Measure Crosswalk (updated annually);

5.1.3.6. ISR-S Pacing Measure Crosswalk (updated annually);

5.1.3.7. ISR-S AMSCO Crosswalk (updated annually);

5.1.3.8. ASIP Crosswalk (updated annually);

5.1.3.9. HQ IIS crosswalk (updated annually);

5.1.3.10. FTE Calculation Methodology (updated annually);

5.1.3.11. Cost Data (FY11-Present) (updated annually);

5.1.3.12. Historical Trends data (updated annually); and

5.1.3.13. System Documentation (updated annually).

5.1.4. The Contractor shall deliver, maintain, and assist in developing the following documents that are provided for the Contractor team and ISR PM’s office to ensure programmatic continuity:

5.1.4.1. System design and modeling validation (updated annually);

5.1.4.2. Functional integration strategies (updated annually);

5.1.4.3. Annual update of the Standard Operating Procedures (SOPs) (updated annually for each component);

5.1.4.4. Annual update of the continuity books and key task job aids for each ISR component and major event

(updated annually);

5.1.4.5. Automated databases (primarily data entry).

5.2. Systems Support, Software and Data Management: The Contractor shall provide systems administration support for the Installation Status Report (ISR) program. The Contractor shall utilize the existing patch management infrastructure to work with the staff to maintain compliance with the requirements imposed by the Army. ISR servers and business systems are configured and maintained in compliance with DoD and Army IT regulations to ensure confidentiality, integrity and availability. The Contractor shall ensure the systems are configured in compliance with current network protocols so OACSIM staff and installation users worldwide are able to utilize the

OACSIM business systems to accurately plan and support installation management requirements.

5.2.1 System Administration. The Contractor shall maintain ISR hardware and software components on the network and ensure business applications are reliable, available, maintainable, and responsive to user requirements

95% of the time during business hours on a daily basis.

5.2.1.1 The Contractor shall ensure business applications meet the specified security and vulnerability standards by applying all required software patches, system updates, and upgrading software versions. The Contractor shall maintain ISR, through system testing and implementation, to support recurring information assurance vulnerability management (IAVM) and computing environment security patches as determined by OACSIM, JSP, CYBERCOM, or DISA, needed to fully support the business processes to include monthly information assurance vulnerability alerts (IAVAs) or published security technical implementation guides (STIGs).

5.2.1.2 The Contractor shall perform quarterly server configuration for application installation, software installation, upgrades and information assurance vulnerability alert (IAVA) patch management on the following:

Microsoft Windows Server Operating System (OS); Microsoft Internet Information Services (IIS); CA

Siteminder/Single Sign On software; Mozilla Firefox; Citrix Presentation Server/XenApp Server; Apache Tomcat;

Microsoft Windows Server Update Service; Adobe Flash Player; Adobe Acrobat Reader; and Java Standard Edition

Runtime Environment/Development Kit. The Contractor shall be required to configure servers as needed to update

STIGs.

5.2.1.3 The Contractor shall perform quarterly requirements analysis on server resource requirements including processors and random access memory (RAM) storage requirements and coordinate requirements with business application support teams and JSP. The Contractor shall perform requirements analysis prior to a technical refresh cycle and as needed when there are system enhancements or changes to the system.

5.2.1.4 The Contractor shall perform weekly reviews to the following software log files (transactions between servers) for potential problems and security issues: Windows Server 2003, IIS, Tomcat, Citrix Presentation

Server/XenApp Server.

5.2.1.5 The Contractor shall support vulnerability alert processes IAW DoD 8500 for maintaining information system certification and accreditation (C&A) on the Army network every three (3) years unless a major change is made to the system. The Contractor shall perform the following tasks: create and organize documentation required to comply with hosting environment requirements; and address any vulnerabilities; execute security readiness review (SRR) scripts and address any vulnerabilities. The Contractor shall provide the Government with a monthly

Security Vulnerabilities report, which shall be stored on the government network.

5.2.1.6 The Contractor shall create and manage ISR user accounts and provide technical assistance to system end users, and support teams for other OACSIM business systems.

5.2.1.7 The Contractor shall maintain the following system documentation and shall no less than annually complete:

contingency plans; network diagrams; and software system configuration requirements and technical documentation to include code, algorithms, application program interfaces (APIs) and user manuals IAW section 5.2.20.

5.2.1.8 The Contractor shall report all system downtimes that are not a part of regular scheduled outages immediately (within one hour during business hours) to the COR/Program Manager including when a system fails to provide or perform its primary function. The Contractor shall have all mission support systems that are mission assurance category III (MAC III) operating within three (3) to five (5) business days IAW DoDI 8500.2. The

Contractor shall submit a system’s outage report to the COR/Program Manager outlining duration and remedy.

5.2.1.9 The Contractor shall coordinate security patch implementation and software upgrades to maintain information assurance vulnerability management (IAVM) compliance, report compliance to the Pentagon Computer

Incident Response Team (PENTCIRT) and address vulnerabilities identified in the network scans completed by JSP.

The Contractor shall submit a quarterly technical report on all critical and high vulnerabilities to the PM. The report shall be stored on the government network.

5.2.1.10 The Contractor shall ensure all system administration activities will support compliance with DoD and

Army regulations.

5.2.1.11 The Contractor shall utilize the existing patch management infrastructure to work with the staff from the

OACSIM business applications to maintain compliance with the requirements imposed by the Army. OACSIM servers and business systems are configured and maintained in compliance with DoD and Army IT regulations to ensure confidentiality, integrity and availability.

5.2.1.12 The Contractor shall ensure the systems are configured in compliance with current JSP and Defense

Information Systems Agency (DISA) network protocols so that OACSIM staff and installation users worldwide are able to utilize the OACSIM business systems to accurately plan and support installation management requirements.

5.2.1.13. The Contractor shall communicate all scheduled system outages to system users with 24 hours minimum notice.

5.2.1.14. The Federal Information Security Management Act (FISMA) requires that all systems on DoD networks operate with valid network authorizations (ATO/IATOs) to complete Annual Contingency Tests, Security Controls

Test, and Annual Security Reviews. To ensure ISR remains FISMA compliant, the Contractor shall execute the requisite Annual Security Review, Contingency Test, and Security Control Test with the accompanying

Memorandums for Record for signature by the Government PM. These reviews include the annual update of the ISR Contingency Operations Plan, Information Assurance Vulnerability Management Plan, and Incident

Response Plan. The Contractor shall maintain all FISMA documents on the government network. The Contractor shall complete and submit of all FISMA requirements to DAIM-IT prior to mandated suspense date.

5.2.1.15. The Contractor shall ensure that the ISR system remains compliant with the OSD Business Enterprise

Architecture (BEA) Acquire-to-Retire Process. The Contractor shall perform an annual analysis of the BEA business processes, data structure, data elements, requirements definition and data mapping in support of the consolidation of Army-wide real property and related data from source systems.

5.2.1.16. The Contractor shall complete all technical documentation and system documentation for ISR server certification and approval by the Government Program Manager annually. The Contractor shall ensure ISR server accreditation is completed in accordance with guidelines set forth by the DoD Risk Management Framework (DoDI

8510.01). The Contractor shall complete the requisite documentation for RMF compliance to include, but not limited to, System Security Categorization, Project Management Plan, Privacy Impact Assessment, Vulnerability

Management Branch (VMB) Checklist, SwARM Form, and IT Contingency Plan. The Contractor shall stay current on eMASS training requirements in order to perform security control assessments within eMASS. The Contractor operating in the capacity of the ISSO will be designated, per appointment memo, as one of the ISR ISSOs.

5.2.2. The Contractor shall update and maintain the reporting organization structure within ISRWeb annually as part of the annual change management process and publication of the annual Data Collection Memorandum. As part of the annual review of the organizational structure, the Contractor shall work with HQDA stakeholders to integrate additional enduring installations (standard as well as virtual installations) and organizations into the ISR reporting process.

5.2.3. The Contractor shall apply automated quality assurance and quality control validations, as laid out in the ISR

Continuity Books and Implementing Instructions, to ISR data submissions prior to locking quarterly.

5.2.4. The Contractor shall provide automated ISR Readiness Rating Summaries to provide comparative analysis for ACSIM Directorates, Army Staff, and Army Secretariat. Readiness summaries, commander’s comments and other supporting data for specific installations shall be provided in “trip books” upon the request of OACSIM leadership (not to exceed 5 per quarter).

5.2.5. The Contractor shall provide approximately 450 data extracts (annually) in support of ad-hoc (end-user specific) data requests (this does not include data requests related to the Army Strategic Readiness Assessment

(ASRA)). All ad hoc data requests shall be stored on the government network. The Contractor shall gather requirements, perform quality checks on the data, and review the results with the requesting agency on the data provided within one week of receipt of the data request, unless otherwise agreed to with the requesting agency, the

ISR Government Program Manager and the ISR Contractor Support Team program manager

5.2.6. The Contractor shall provide approximately 70 automated data extracts in support of recurring end of quarter deliverables.

5.2.6.1. The Contractor shall provide a Common Levels of Support (CLS) data extract to the respective Army component leads on a quarterly basis.

5.2.6.2. The Contractor shall provide data in support of the Defense Readiness Reporting System - Army (DRRS-A) on a quarterly basis within fifteen calendar days after system lock.

5.2.6.3. The Contractor shall calculate ratings and upload the ratings and associated comments to the Strategic

Management System (SMS), or other designated system, on a quarterly basis to support the Army Campaign Plan

(ACP).

5.2.6.4. The Contractor shall provide support for the Joint Forces Readiness Report (JFRR), Army Strategic

Readiness Assessment (ASRA), Strategic Readiness Update (SRU), Chief of Staff of the Army (CSA) Priorities

Briefs. The Contractor shall provide data extracts (estimated at 30 reports with approximately 200 data elements per quarter) and commander’s comments (approximately 30 comments for 25 installations quarterly) in support of the

Army Strategic Readiness Assessment (ASRA) or Strategic Readiness Update (SRU) process. Data support may include customized scope rollups that must be manually calculated outside of ISRWeb, requiring additional QA/QC to ensure accuracy. The Contractor shall attend meetings and provide meeting minutes upon request in support of the ASRA/SRU (up to 10 per month) to receive input on data requests, to include coordination of annual measure reviews and updates.

5.2.6.5. The Contractor shall calculate ratings and upload the ratings to the Strategic Management System (SMS), or other designated system, on a quarterly basis to support the Ready and Resilient Campaign (R2C).

5.2.6.6. The Contractor shall provide data and ratings on a quarterly basis for approximately 36 additional data extracts.

5.2.7. The Contractor shall centrally manage, process, and validate data files (toploads) for all ISR components to enable the successful completion of the ISR data collection, in accordance with the procedures outlined within the

ISR continuity books. For ISR Services (Cost) this includes GFEBS, STANFINS, and Funds 22 files) received and applied prior to the annual ISR-Services (Cost) collection. The Contractor shall generate the topload templates, provide the topload templates to the data POCs, process received topload files, load toploads to test server, validate toploads, and load the toploads to the production server. See the Appendix to this document for a list of ISR toploads.

5.2.7.1. The Contractor shall centrally manage, process, and validate data files (toploads) for non-environmental metrics for the ISR Infrastructure, ISR Mission Capacity, ISR Services (Performance), and ISR Services (Cost) components. The Contractor shall provide a Topload Status Report beginning on the 15th day of the start of each fiscal year quarter and continue to do so on a weekly basis until all ISR-I, ISR-MC, ISR-S (Performance), and ISR-S

(Cost) non-environmental toploaded data has been successfully uploaded onto the ISRWeb production server. Files shall be stored on the Government network.

5.2.7.2. The Contractor shall centrally manage, process, and validate data files up to 50 environmental toploaded metrics for the ISR Mission Capacity component. The Contractor shall provide a Topload Status Report beginning on the 15th day of the start of each fiscal year quarter and continue to do so on a weekly basis until all ISR-MC environmental toploaded data has been successfully uploaded onto the ISRWeb production server. Files shall be stored on the Government network.

5.2.8. The Contractor shall maintain Memorandums of Agreement (MOAs) and System Integration Agreements

(SIAs) with systems from which ISR receives data and for which ISR provides data (see Topload Appendix). The

Contractor shall review MOAs and SIAs annually to ensure they are current and coordinate with the ISR Program

Manager for signature NLT August 31st.

5.2.9. The Contractor shall provide approved release notes to inform ISRWeb users of system functionality updates and changes as well as publish release notes on the ISR website within 15 days after the beginning of each quarter.

Files shall be stored on the government network.

5.2.10. The Contractor shall maintain a central database to track on-going and requested process and software change requests (Change Management Process Initiatives or CMPIs). Relevant CMPI data shall be updated and distributed to the component commands on a weekly basis. The Contractor shall develop a procedure to coordinate relevant change requests with each component command.

5.2.11. The Contractor shall maintain and update OACSIM’s ISR website. The Contractor shall include information related to ISR data collections and training on the ISR website, to include links to recorded training and job aids (5.1.4.4.)

5.2.12. The Contractor shall maintain and update ISRWeb monthly to ensure it supports the collection and reporting of all Army performance metric programs, as identified by the ISR Program Manager. The Contractor shall make enhancements to ISRWeb to support the collection and reporting of information. This may include, but is not limited to website changes such as posting program news, updates and announcements, and adding web-links to training sessions and other materials needed to support the ISR collection process. The Contractor shall update software on internet-based servers that host ISRWeb as required by ACSIM’s Information Technology Division or the Joint Service Provider. The Contractor shall be proficient in the software specified in 1.6.26.3. as detailed in

1.6.26.3.

5.2.13. The Contractor shall sustain the navigation functionality within the data input applications for all components and make other adjustments to achieve a common look and feel across the applications (i.e. provide for an overall installation level commander’s readiness rating and entry of installation level comments in ISR-I, consistent with ISR-S and ISR-MC capabilities).

5.2.14. The Contractor shall sustain the functionality within ISRWeb to allow for the inclusion of a user linked date and time stamp (this system log is a current system functionality) as data are uploaded into the data input applications, either manually or electronically, as identified by the ISR Program Manager

5.2.15. The Contractor shall calculate a holistic ISR Rating that combines ISR-Services, ISR-Infrastructure, and

ISR Mission Capacity ratings, and shall develop a methodology for developing mission capacity ratings for virtual installations. The Contractor shall update holistic ratings quarterly and display them in ISRWeb.

5.2.16. The Contractor shall coordinate with the Headquarters, Installation Infrastructure System (HQ IIS) program manager and the HQIIS program Contractor program manager to maintain HQ IIS data within ISRWeb. This shall include coordination regarding updating the organizational structure of ISR to keep current with the Army’s structure, assisting with data and query questions, and providing data for ad hoc queries, up to 20 per quarter.

5.2.17. The Contractor shall support the collection of Army-wide Common Levels of Support (CLS) data. The

Contractor shall collect CLS metrics as part of the ISR-S (Performance) data input module and coordinate as needed with CLS metric owners to ensure metrics approved as part of IMCOM’s internal CLS metric approval process are incorporated during the annual change management process.

5.2.18. The Contractor shall collect and perform automated quality assurance checks on the most current four years of ISR-S (Cost) data collected. The Contractor shall perform these quality checks on the reporting organization and service level costs, pacing measures, demographics, and population data prior to Commander certification. The

Contractor shall provide the four years of cost data to the PM and DASA-CE annually within 15 working days of the locked ISR-S (Cost) collection.

5.2.19. The Contractor shall provide an end of quarter data extract of the locked end of quarter dataset on a DVD within 15 days to the ISR PM. The Contractor shall provide the data extract from the Current Year viewer and Data

Input application that reside on the ISRWeb production server for all ISR components.

5.2.20. The Contractor shall provide a download of the ISRWeb code on a monthly basis on a DVD by the 10 th of each month. Files shall be loaded on the government server.

5.2.22. ISRWeb Migration to Consolidated Data Center.

5.2.22.1. The Contractor shall work with the Government and Commercial Cloud Service Provider (CSP) technical engineers to ensure all system software and/or versions are migrated to and maintained on the CSP hosting environment in accordance with DoD/Army policies and CSP Infrastructure as a Service (IaaS) hosting technical requirements.

5.2.22.2. The Contractor in collaboration with the Government shall develop a pre migration test plan for migration to a CSP environment. The test plan shall include but is not limited to change documents (customizations/ enhancement/patch levels), system interface assessments, business process flows, and consultations with users of the application.

5.2.22.3. The Contractor in collaboration with the Government shall develop a post migration test plan and test the system in the migrated environment. The test plan shall include but are not limited to requirements documents, scripted and unscripted testing, functional specifications, business process flows or definitions, and change documents (customizations/enhancement/patch levels). The Contractor shall ensure testing and validation is integrated throughout the project lifecycle to ensure the applications meet requirements.

5.2.22.4. The Contractor shall ensure the testing environment mirrors the production environment. The Contractor shall execute regression, unit, and integration testing. All test plans shall be written before conducting any testing.

The Contractor shall develop a post migration test report that includes information of all post-migration testing. The test report shall at a minimum include what cases failed and verification of all changes.

5.2.22.5. The Contractor shall ensure integration testing is performed on hardware and software in the cloud service provider environment. The Contractor shall test to verify the systems are performing optimally in the new environment. This shall include but is not limited to stress-testing the applications by applying differing workloads and measuring how the application responds in terms of throughput, latency, memory utilization and processor loads. The Contractor shall record and compare measurements of performance on the old system in terms of system metrics, as well as application metrics, with similar metrics in the new system.

5.2.23 The Contractor shall complete tasks related to preparation to receive ratings obtained from engineer-based facility assessments (Enterprise SMS (i.e. Builder)). The Contractor shall perform an analysis between the ratings obtained from engineer-based assessments and tenant based assessments on an annual basis. The contractor shall work with USACE Enterprise SMS representative and government representatives to develop a system interface agreement and procedures for managing toploads provided by Enterprise SMS. The Contractor shall also develop modifications to the ISR-I implementing instructions and training materials to reflect integration of the Enterprise

SMS system.

5.2.24 The Contractor shall be responsible for the sustainment of the government provided Business Enterprise

Architecture document and artifacts based on the format and templates provided by DoD/ACSIM/ISRWeb Program

Manager. The Enterprise Architecture artifacts are used to assert compliance with the NDAA guidelines and must be continuously maintained throughout the operation and sustainment period of this contract. The Government has an electronic copy of the Business Enterprise Architecture document on file with text and process diagrams

(artifacts), including but not limited to the Operational Activity Model, Organizational Relationships chart, Process

Models, Business Rules, etc. that shall be updated to reflect system changes. The Business Enterprise Architecture document, including artifacts, shall be reviewed and updated at least annually.

5.3. Management Support for OACSIM:

5.3.1. The Contractor shall support the integration of the frequency and delivery of oral and written communications across all ISR components as well as the look of all ISR deliverables to ensure a common level of support to customers.

5.3.2. The Contractor shall provide for and maintain a master calendar of the ISR data collection, training, and

ISRWeb system schedules to allow for informed decision making with regards to task priorities. The Contractor shall provide a separate calendar for the ISR System, each ISR component, and integration efforts. The Contractor shall develop the master calendar weekly using Microsoft Excel or another similar Gantt chart format that is identified by the ISR Program Manager.

5.3.3. The Contractor shall maintain and update a centralized database of program points of contact that includes, but is not limited to, Army Staff Proponents, Component Subject Matter Experts, and Component ISR Managers.

5.3.4. The Contractor shall assist in providing hands-on support to ISR reporting organizations, component headquarters, and Army Headquarters elements and to support ISR customers both within and outside of the NCR.

This shall include preparation of briefing and training slides and trip reports within five days of the completion of travel. The Contractor shall provide support at the following anticipated locations outside of the NCR (visits within the NCR to USARC HQ and ARNG HQ (one time annually) are also anticipated:

Component Command Training Sessions/Command Site Visits

ISR Component Leads, Program Manager

Anticipate no more than 4 trips per year (one for each component command) to conduct site visits and centralized training. 1 centralized training event hosted all components (see below) will replace

To include: AMC or ASC HQs, Huntsville, AL or Rock Island, IL (or others similar location as identified by AMC/ASC); IMCOM HQs, San Antonio, TX (or similar location); and one centralized training for USAR HQ and ARNG HQ (at locations similar to Fort Knox, KY for centralized USAR training, and Virginia Beach, VA to conduct ARNG training).

Travel by Air

Provide support on the implementation of ISR for facilities, mission capacity, and services.

Installation Support

Anticipate no more than 2 local trips annually to conduct site visits, briefs and working sessions with local Garrisons/organizations (i.e. Fort Belvoir, Fort Myer-Henderson Hall, etc.).

Provide support on the implementation of ISR for facilities, mission capacity, and services.

Provide technical support as needed for the filming of an updated ISR training video

Travel by Air for one Component lead (ISR-I) for filming of ISR-I inspection training video

OCONUS Support

Anticipate a maximum of two trips over the length of the contract. An OCONUS support site visit will be held at some point during the sixty (60) months in lieu of the annual IMCOM site visit or training session detailed under Component Command Training Sessions/Command Site Visits, above.

To include: German/Italian Installations; Korean Installations, Japan Installations

Provide support on the implementation of ISR for facilities, mission capacity, and services.

Centralized Training

ISR Leads and SMEs

Anticipate a maximum of one annual centralized training session scheduled over the length of the contract. A centralized training session will occur in lieu of one of the annual site visits or training sessions detailed under Component Command Training Sessions/Command Site Visits, above.

Little Rock, AR

Provide hands-on training for the accredited ISR training courses.

5.3.5. Briefing and Training Support.

5.3.5.1. The Contractor shall provide briefing support (personnel and briefing material) for meetings within the

NCR to include development of draft briefings addressing ISR overview, component specific data and rating status, shall provide support during briefings, and shall support on follow up tasks (data requests, providing support answering questions) originating from briefings..

5.3.5.2. The Contractor shall support conferences, in-person training sessions, Garrison Staff and Command briefs, and briefings to Component Command and ACSIM leaders, etc. outside of the NCR, when such sessions can be scheduled to occur with Component Command Training Sessions/Command Site Visits as detailed in 5.3.4., above, or when Garrisons, Component Commands, and other ISR users provide additional funding to support similar sessions.

5.3.5.3. A maximum of 60 training sessions will be developed for presentation on Defense Collaboration Services

(DCS). One DCS training session must be developed per topic and conducted live for installations on DCS. The session must be recorded and posted on the ISR website so it can be accessed by ISR users working at installations throughout the world (Europe, Pacific, and across the U.S.). The Contractor shall develop one accompanying job aid for each training topic that shall be posted on the ISR webpage for users.

5.3.5.4. The Contractor shall provide support to develop filmed training materials in concert with Government personnel from OACSIM and within the Army Multimedia & Visual Information Directorate, to include contributing to the development of and reviewing draft scripts, contributing background materials for inclusion in a revised ISR-Infrastructure inspection training video and other ISR training sessions, and participating in filming of training sessions in the NCR region.

5.3.5.5. In preparation for dashboard development, the ISR Support Team will conduct local site visits in order to conduct working groups to assist with development of streamlined reporting processes intended to reduce workload.

Locations will be selected considering installation types, missions, and readiness reporting requirements. Training will be provided to ISR users and ISR Overviews will be provided to installation staff and Commanders as outlined above during these site visits in order to improve understanding of the program and data accuracy/consistency. No more than two site visits anticipated annually; site visits will be included in the 2 local site visits, or in lieu or in concern with one of the annual site visits or training sessions detailed under Component Command Training

Sessions/Command Site Visits, as detailed in 5.3.4, above.

5.3.6. The Contractor shall support the execution of the annual ISR Change Management Process.

5.3.6.1. The Contractor shall provide a centralized change management issue submission system that allows for the automated submission of change management issues. The Contractor shall provide an electronic form for the submission of the change management issues that is accessible via the ISR website and ISR AKO home page. The

Contractor shall coordinate for chain of command review of change management issues received by base-level reporting organizations. The Contractor shall provide a consolidated list of all issues submitted during the annual collection period. The Contractor shall provide PM approved responses to the issues submitted. The Contractor shall also develop an approved method for sharing relevant change management issues with each component command.

5.3.6.2. The Contractor shall assist in planning for the ISR Communities of Practice (CoPs) and support the action officer level reviews of ISR measures and inspection criteria at the CoPs. The Contractor shall support NTE two

CoPs for each ISR-I booklet, ISR-S service, and ISR-MC focus area as forums for information exchange to improve the ISR data collection process. To support this, the Contractor shall anticipate holding approximately 350 CoPs.

The Contractor shall assist in facilitating the integration of ISR metrics with CLS metrics and ensure there is not a duplication of metrics collected. In preparation for the CoPs, the Contractor shall assist in developing read aheads and final briefing slides and provide issue reports for review by meeting participants.

5.3.6.3. The Contractor shall provide support for OACSIM Resources Directorate (OACSIM RD) Installation

Service Standards Working Group (ISS WG). The in depth review of ISR and CLS metrics requires ISR Support

Team to participate in multiple weekly working group meetings (approximately 3 per week) to review regulatory drivers, performance work statements, manpower studies, common levels of support, and other documentation for each service to determine baseline service standards. Each Service (or group of services) Sub-Working Group

(SWG) may require a multiple day offsite conference to begin the review, followed by weekly SWG meetings. All updates received to the metrics must be incorporated into ISRWeb and supporting documentation (e.g. worksheets).

The ISR support team shall also review performance and pacing metric worksheets developed by metric owners and

ACSIM RD staff. The Contractor shall also meet annually with OACSIM RD to review and finalize all business rules for the annual cost collection.

5.3.6.4. The Contractor shall assist in planning for the ISR Change Management Advisory Group (CMAG) and support the action officer level approval of proposed measures and criteria at the CMAG. In preparation for the

CMAG, the Contractor shall make preparations for the CMAG, to include reserving the conference room and preparing for the event (i.e. setting up phone and internet access), shall assist in developing read-aheads and final briefing slides, and provide component summary documents that outline changes as a result of metric and booklet reviews and the proposed metrics for the upcoming data collections. The Contractor shall provide the OACSIM approved responses to the ISR Community members who submitted issues for consideration. All data shall be stored on the Government server.

5.3.6.5. The Contractor shall assist in planning for the ISR Council of Colonels (CoC) and support the execution of the ISR CoC which is the forum to approve the annual programmatic and system changes for the next fiscal year’s

ISR data collection. In preparation for the CoC, the Contractor shall make preparations, to include reserving the conference room and preparing for the event (i.e. setting up phone and internet access), shall assist in developing briefing slides and provide a summary of changes and the proposed metrics for the upcoming data collections. All data shall be stored on the Government server.

5.3.7. The Contractor shall update the ISR PM on a weekly basis (In-Progress Review meeting) on the status of the preparation of all upcoming major events to include the CMAG, CoC, and hands-on training events. The Contractor shall anticipate between four and six reviews per major event and shall provide updates to a calendar of required activities and information on the status of outstanding tasks. All data shall be stored on the Government server.

5.3.8. The Contractor shall provide hard copy documentation of the subsequent fiscal year’s data collection for

ACSIM approval within 15 days of the CoC. All data shall be stored on the Government server.

5.3.9. The Contractor shall provide functional assistance in support of the ISR data collection. The Contractor’s functional assistance shall include helping with data input issues, clarifying metrics and weightings, assisting with data validations, responding to inquiries on toploads, etc. The Contractor shall maintain a centralized system to assist the ISR community during the ISR data collection to include technical issues and automated tracking of all incoming issues.

5.3.10. The Contractor shall provide weekly ISR Programmatic Priorities and shall coordinate a weekly conference call where the program priorities for the week will be discussed. All data shall be stored on the Government server.

5.3.11. The Contractor shall provide a weekly ISR Data Collection Status Report to include analysis and email addresses for distribution to the ISR Program Stakeholders. The Contractor shall provide the Status Reports weekly once the toploads are loaded into ISRWeb and continue providing Status Reports until each Army component has completed its quarterly data collection.

5.3.12. The Contractor shall ensure full compliance with the latest version of the Department of Defense (DoD)

Real Property Inventory Model (RPIM). The Contractor shall coordinate with ACSIM staff to ensure program compliance with the RPIM.

5.3.13. The Contractor shall assist in updating the Installation Quick Reference Guides in Adobe Portable

Document Format (PDF) format for the Active Army (to include IMCOM, AMC, and USAREUR), ARNG, and

USAR. The format of the Quick Reference Guides shall be reviewed annually as part of the change management process. Input on formatting of the Guides shall be obtained from the component commands and HQDA stakeholders, to ensure the guides meet readiness reporting needs. The Contractor shall create the guides to include the ISR-I, ISR-MC, and ISR-S ratings by installation as well as the Essential Facility Review (EFR) data. The

Contractor shall coordinate as needed with the FAS program to ensure the most up to date EFR data is included.

The Contractor shall provide an electronic copy of each Army component’s (Active Army, ARNG, and USAR)

Quick Reference Guide on a quarterly basis and prepare a DD282 form for a print order to allow for hard copy printing.

5.3.14. The Contractor shall provide support for the Army Campaign Plan (ACP) to include preparation of briefings and support materials. The Contractor shall coordinate with ACP subtask owners for input into briefings and support material. The Contractor shall attend up to one meeting per quarter to support the ACP.

5.3.15. The Contractor shall work with IMCOM G3/5/7 to expand/modify the Microsoft Access Service coversheets/Unified Service Package format to be consistent with recommendations provided by IMCOM. The draft worksheet format shall be reviewed by Component Command and ACSIM representatives for approval.

5.3.16. The Contractor shall assist in preparing the annual data collection memorandum and supporting documentation. The Contractor shall provide the most recently approved supporting documentation including the reporting requirements, reporting organization structure, and Army Management Structure Code (AMSCO) crosswalk for the applicable fiscal year, as well as topload reporting requirements. The Contractor shall publish the signed data collection memo and supporting documentation to the ISR website annually.

5.3.17. The Contractor shall assist in facilitating one working group meeting for each ISR component (ISR-I, ISR-

MC, and ISR-S) per quarter and shall facilitate one ISR component overview trends brief annually. The Contractor shall assist in coordinating the meetings and preparing the briefing slides. Minutes for each meeting shall be stored on the Government server.

5.3.18. The Contractor shall attend all requirements, functional, and technical meetings with a government representative, provide technical representation at the meetings, and document the functional and technical requirements needed to develop, sustain, or enhance the system. The Contractor shall create the meeting minutes to support requirements documentation. The Contractor shall provide meeting minutes to the PM for approval and then distribute them to affected stakeholders for their review, concurrence, and recommended changes. The

Contractor shall provide any recommended changes to the PM for approval, make changes as needed, and distribute to affected stakeholders. The Contractor shall assist in coordinating these technical and functional meetings to support system development, sustainment, and enhancement. The Contractor shall distribute meeting minutes to the stakeholders within five business days of the meeting. The Contractor shall anticipate providing approximately 300 meeting minutes.

Paragraph 5.4 excluded

5.5. IMCOM (G3/5/7) Support – Provide on-site, dedicated support at Fort Sam Houston for the IMCOM G3/5/7 for ISR-I, ISR-MC, and ISR-S.

5.5.1. The Contractor shall ensure that all information provided to IMCOM regarding the ISR program and data collections is current.

5.5.2. The Contractor shall communicate both orally and in writing with IMCOM’s ISR Community to gather or provide information to successfully conduct the ISR Data Collection. The Contractor shall communicate in areas such as requirements for upcoming data collections, utilization of data, analysis of ISR and CLS data, use of

ISRWeb, comprehension of ISR and CLS data and ratings, clarity on supporting documentation, metric development, inspection criteria, training opportunities, and data requests. The Contractor shall assist with the management of Helpline & FAQ issues, topload issues, and role requests in support of IMCOM garrisons, shall coordinate annual review/validation of IMCOM reporting org structure and provide feedback to OACSIM, assist with the maintenance of ISR quarterly reporting requirements, help field/resolve validation errors or any other problems that prevent the GC from certifying their report, shall provide individual training to HQ IMCOM or

Directorate level staff, shall participate in monthly OACSIM/IMCOM ISR Support Team forums to identify, coordinate and ensure effective implementation of business process improvements, shall coordinate Directorate/G

Staff Coordination Reporting Structure, shall maintain the IMCOM ISR Standard Operating Procedures (SOP), shall support the maintenance of the IMCOM ISR Continuity Binder, and shall coordinate IMCOM's review/response for periodic Army staffing of AR 210-14.

5.5.3. The Contractor shall participate in the ISR Change Management Process and assist IMCOM throughout the process to include: assisting ISR/CLS Change Management Vision and Strategy development, assisting in the publication and execution of the annual IMCOM CoP and development of Change Management Guidance (conduct

IPRs, provide training to HQ IMCOM SMEs, etc.), shall assist with the development/maintenance of the ISR/CLS

STRATCOM Plan (includes SharePoint page management), shall assist with all IMCOM related CMPIs from

OACSIM to manage them through resolution/close-out, shall incorporate documentation for all IMCOM requested changes to the Unified Service Packages for the next FY, shall assist with the preparations for IMCOM leadership for the annual OACSIM Change Management Advisory Group, shall assist with the preparations for IMCOM leadership for the annual OACSIM Change Management Council of Colonels.

5.5.4. The Contractor shall provide briefing support (personnel and electronic briefing material) to the Government both within and outside of the Fort Sam Houston area for meetings and trainings (both in-person and via webinar) to include ISR overviews, component specific materials and instructions, and the current rating status. The Contractor shall assist the government in organizing meetings and training events.

5.5.5. The Contractor shall maintain and update the centralized POC database with IMCOM’s ISR points of contact that includes, but is not limited to, Component Headquarters Subject Matter Experts, and Installation/Garrison ISR managers and functional leads. The Contractor shall provide updates to the POC database to ACSIM or other points of contact in digital format using Microsoft software. Update IMCOM ISR/CLS POC contacts monthly and provide updates to OACSIM quarterly.

5.5.6. The Contractor shall participate in ISR Working Group Meetings with ACSIM and the other Component

Commands and help ensure the correct Component Command POCs are informed of the upcoming meetings.

Anticipate participation in HQDA level working groups (ISS, AP3, Army Readiness, Data Integrity, COLS), in IMCOM level working groups (RIE, Performance Management OPT, etc.), development/maintenance of

ISR/CLS STRATCOM Plan (includes SharePoint page and G Drive management), support of G3/5/7 Readiness

Branch with ISR data/expertise as requested (for ASRA and DRRS-A reporting), management of ISR activities for

IMCOM Directorates, and coordination with AMC and USAR ISR Program Managers as necessary to resolve ISR-related issues with the LRCs or Reserve Installations.

5.6. OACSIM Installation Services Division Support – Provide on-site, dedicated support at the Pentagon for the

OACSIM-Installation Services Housing (ISH) Division (ISR-I and ISR-S data) to support DAIM-IS with Strategic

Readiness Updates (SRU) and the Army Strategic Readiness Assessment (ASRA). The individual performing the function shall have an approved secret clearance in place in order to allow work on the task to begin as soon as possible.

5.6.1. The Contractor shall ensure that all information provided to OACSIM regarding the ISR program and data collections is current.

5.6.2. The Contractor shall perform an average of one data query per week on barracks, housing and other IS area of responsibility related ISR information (primarily ISR-I and ISR-S), up to 48 queries on an annual basis. Results shall be provided to DAIM-ISH in the form of excel spreadsheets, which can be filtered on unique facility identifiers such as RPUID.

5.6.3. The Contractor shall complete analysis on data trends for IS area of responsibility ISR-I Q and F-ratings, scores and cost, and ISR-S Service ratings and cost data, in order to identify anomalies and/or changes. At least once per quarter, they shall analyze updated quarterly DAIM-IS barracks, housing and other IS area of responsibility data trends from ISR-I and ISR-S, and display the results in a PPT presentation. The results shall be provided to DAIM-

ISH using Excel or PowerPoint to display the data.

5.6.4. The Contractor shall provide support to IS personnel to pull reports and data on various IS area of responsibility data from ISR (ISR-I Q and F ratings, scores and costs, ISR-S Service Q-ratings and costs, to include by-quarter pulls and analysis by RPUID and ISR-S metric). The Contractor shall be prepared to complete at least one query on average a week to DAIM-ISH. The Contractor will coordinate with Government and contract personnel to obtain Real Property Planning and Analysis (RPLANS) data related to barracks, housing and other IS areas of responsibility. The results should be delivered to DAIM-ISH in an Excel format.

5.6.5. The Contractor shall provide support to DAIM-ISH to ensure that correct and complete ISR data is passed to the Electronic Military Housing (eMH) system using a provided eMH template. The purpose of the task is to ensure correct topload information is passed between the two systems, that the same Q-rating is displayed between the two systems, allowing for automated data runs between the two systems. The Contractor shall assist with the revision of the topload document needed to pass data between the two systems if required. The Contractor shall facilitate a toplaod between the two systems once per quarter. Topload data shall be provided as part of an Excel Flat-file, delivered to DAIM-ISH that can be uploaded into eMH. ISH will provide the flat file attributes.

5.6.6. The Contractor shall plan to attend three meetings per month in support of the ASRA in conjunction with other tasks. The Contractor shall provide briefing support up to once per quarter (personnel and electronic briefing material) to the government in the NCR (both in-person and via webinar) to include ISR overviews, component specific materials and instructions, and the current rating status. The Contractor shall assist the government in organizing meetings and training events.

5.6.7. The Contractor shall provide support to DAIM-ISH for any Housing/Barracks/IS Area of Responsibility

Installation Service Standards Working Group (ISS WG) meetings. The ISS WGs are OACSIM RD led supplements to the ISR change management process. The in depth review of ISR and CLS metrics may require ISR

Support Team participation in weekly working group meetings (approximately 3 per week) to review regulatory drivers, performance work statements, manpower studies, common levels of support, and other documentation for each service to determine baseline service standards. Each Service (or group of services) Sub-Working Group

(SWG) may require a multiple day offsite conference to begin the review, followed by weekly SWG meetings. The

Contractor shall support the OACSIM-OD ISR support team as needed in the process of updating changes made to metrics, as part of the change management process. Tasks could include coordinating with metric subject matter experts regarding metrics, participation in the review of performance and pacing metric worksheets, development of the worksheets, and assistance incorporating revisions into ISRWeb.

5.6.8. The Contractor shall coordinate with the DAIM-OD ISR team regarding updates to the centralized ISR POC database for DAIM-IS ISR points of contact including, but not limited to, HQDA functional leads, Headquarters

Subject Matter Experts, and Component command ISR managers and functional leads.

5.7. Contract Data Requirements. The Contractor shall provide a monthly status report.