FY26_OSMIS_PWS_v5.docx

PERFORMANCE WORK STATEMENT

Operating and Support Management Information System (OSMIS)

PART l GENERAL INFORMATION

1.1 Description of Services/Introduction: The Contractor shall provide all personnel, equipment, tools, materials, supervision, and other items and non-personal services necessary to provide technical support services to the Deputy Assistant Secretary of the Army for Cost and Economics (DASA-CE) as defined in this PWS except as specified in section Part 3 as government furnished property and services. The contractor shall perform to the standards in this contract.

1.2 Background: The Deputy Assistant Secretary of the Army for Cost and Economics (DASA-CE) Mission is to provide the Army decision-makers with cost, performance, and economic analysis in the form of expertise, models, data, estimates, and analyses at all levels.

1.3 Objectives: The objective of this effort is for the contractor to provide technical support services in the concentrated areas of Operations and Support (O&S) costing; Database Management, Output Products and to provide hosting services to CPP portal in support of the ASA (FM&C) and DASA-CE.

1.4 Scope: The scope under this effort is for the contractor to provide technical support services in the concentrated areas of cost and economic analysis of major weapon system programs and associated acquisition/financial management policies and procedures of the Department of Defense (DoD). This effort supports DASA-CE to meet unmet operational needs in the area of Future Technology Systems and Financial Management and Operations for cost and economic acquisition/financial management policies and procedures of the Department of Defense (DoD). Performed services will be in conformance with current DoD and Army regulations/pamphlets and letters of instruction (LOI) regarding cost analysis.

1.5 Reserved.

1.6 General Information

1.6.1 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 nonrecurrence of defective services. The contractor's quality control program is the means by which he assures himself that his work complies with the requirement of the contract. As a minimum, the contractor shall develop quality control procedures that address the areas identified in Technical Exhibit 1, "Performance Requirements Summary" and the PWS. Quality Control plan shall be delivered to the Contracting Officer’ Representative (COR) and Contracting Officer’s Technical Representative (COTR) within 30 days of start of performance. The QC plan shall be approved by the COR, and any proposed changes to the QC plan by the contractor must receive approval by the COR.

1.6.2 Quality Assurance: The government shall evaluate the contractor's performance under this contract in accordance with the Quality Assurance Surveillance Plan. 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 contractor shall adhere to its company's holiday policy. Listed below are those recognized Government holidays:

Christmas Day

1.6.4 Hours of Operation: The contractor is responsible for conducting business, between the hours of 8:00 a.m. - 4:30 p.m., Monday thru 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. The Contractor must at all times maintain an adequate work force for the uninterrupted performance of all tasks defined within this statement of work 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 work force are essential.

1.6.5 Place of Performance: The majority of the work under this contract will be performed at the contractor's facility.

1.6.6 Reserved.

1.6.7 Security Requirements: Contractor personnel performing work under this contract must have a SECRET security clearance at time of contract award. Security requirements are in accordance with the attached DD Form 254. Attachment 1.

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

1.6.8 Special Qualifications: NIA

1.6.9 Post Award Conference/Periodic Progress Meetings: The Contractor agrees to attend any post award conference convened by the contracting activity or contract administration office in accordance with Federal Acquisition Regulation Subpart 42.5. The contracting officer, Contracting Officer's Representative, Contracting Officer's Technical Representative (COTR), and other Government personnel, as appropriate, may meet periodically with the contractor to review the contractor's performance. At these meetings the contracting officer will apprise the contractor of how the government views the contractor's performance and the contractor will apprise the Government of problems, if any, being experienced. Appropriate action shall be taken to resolve outstanding issues.

These meetings shall be at no additional cost to the Government. It is anticipated there will be approximately twenty-six meetings per performance period. Unscheduled meetings are estimated to be approximately four times per year. The number of meetings is estimated and may be more or less than estimated.

1.6.10 Contracting Officer's Representative (COR): The COR will be identified by separate letter. The COR monitors all technical aspects of the contract and assists in contract administration. 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 this PWS.

1.6.11 Key Personnel - Resumes required

1.6.11.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 and alternate are considered key personnel by the government. 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 the hours 8:00 a.m. - 4:30 p.m., Monday thru Friday except Federal holidays or when the government facility is closed for administrative reasons. Qualifications for Program Manager: Demonstrated experience managing multiple teams, Army-wide database and development of cost factors to support the Army Planning, Programming, Budget and Execution (PPBE) process, or equivalent. Demonstrated experience conducting training in the use and application of Army-wide database and providing Army-wide technical support, or equivalent. Bachelor's Degree, preferably in Business, Engineering, or technical/scientific subject. An advanced degree is desirable. Minimum of 10 years of professional work experience, ideally in leadership or management capacities.

1.6.11.2 **Project Managers. The contractor shall provide Project Managers for Database Management, Output Products. These personnel are considered key personnel. The name of these personnel and alternates who shall act for the contractor when the manager is absent shall be designated in writing to the contracting officer. The Project Manager-Database Management shall have demonstrated experience managing a team and working with Army logistical data and databases to include Structure and Manpower Allocation System (SAMAS), Logistics Intelligence File (LIF), PBUSE: Property Book Unit Supply Enhanced, Army Master Data File, (AMDF), Standard Army Maintenance System (SAMS-E) ,Unit Level Logistics System (ULLS-Aviation/Ground), Logistics Modernization Program (LMP), Global Combat Support System – Army (GCSS-A), General Fund Enterprise Business System (GFEBS), Army Enterprise Systems Integration Program (AESIP), or equivalent. The Project Manager shall also have the ability to identify missing or incomplete data and anomalies using analytical methods and bridge data gaps. The Project Manager-Output Products shall have demonstrated experience managing a team and developing weapon system operating cost factors and individual soldier cost factors, or equivalent. They shall also have demonstrated experience providing engineered and parametric cost factors to support the Army Planning, Programming, Budget and Execution (PPBE) process as well as providing cost factor analysis support to the Army Staff, or equivalent. Bachelor's Degree, preferably in Business, Engineering, or technical/scientific subject. An advanced degree is desirable. Minimum of 10 years of professional work experience, ideally in leadership or management capacities.

1.6.12 Identification of Contractor Employees: All contract personnel attending meetings, answering Government telephones, 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.

1.6.13 Contractor Travel: Contractor will be required to travel CONUS, OCONUS, and within the NCR during the performance of this contract to attend meetings, conferences, and training. Contractor will be authorized travel expenses consistent with the substantive provisions of the Joint Travel Regulation (JTR) and the limitation of funds specified in this contract. All travel requires Government prior approval/authorization by the COR/COTR and notification to the COR.

1.6.14 Other Direct Costs. Reimbursement of reproduction and shipping costs and unscheduled items to be purchased in direct support of this requirement requires the prior written approval of the Contracting Officer's Representative, subject to the limitation of funds specified in this contract, and shall be reimbursed at actual cost plus applicable burden, and without profit.

1.6.15 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 under any applicable regulations, or laws.

1.6.16 Organizational Conflict of Interest: Contractor and Sub-Contractor personnel performing work under this contract may receive, have access to, or participate in the development of proprietary or source selection information (e.g., cost or pricing information, budget information or analyses, specifications or work statements, etc.) or perform evaluation services which may create a current or subsequent Organizational Conflict of Interests (OCI) as defined in FAR Subpart 9.5. The Contractor shall notify the Contracting Officer immediately whenever he/she becomes aware that such access or participation may result in an 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. In the event the Contracting Officer unilaterally determines that any such OCI cannot be satisfactorily avoided or mitigated, the Contracting Officer may affect other remedies as he or she deems necessary, including prohibiting the Contractor from participation in subsequent contracted requirements which may be affected by the OCI.

1.6.17 Phase-Out Plan which enables a smooth transition to replacement services when the contract ends (including technical data rights considerations).

PART 2

DEFINITIONS

AESIP-- Army Enterprise Systems Integration Program AMDF-- Army Master Data File ARCENT-- Army Central ARRG-- Army Requirements Review Group BES-- Budget Estimate Submission AWCF-- Army Working Capital Fund CCI-- Control correlation identifiers CDRL-- Contract data requirements list CERP-- Commander’s Emergency Response Program CLIX-- Supply class IX CL-- Confidentiality Level CLS-- Contractor Logistics Support COA-- Courses of Action COCOM-- Combatant Command CONOPS-- Concept of Operations CONUS-- Continental United States COR-- Contracting Officer's Representative: A representative from the requiring activity assigned by the Contracting Officer to perform surveillance and to act as liaison to the contractor COTR-- Contracting Officer's Technical Representative: A representative from the requiring activity assigned by the Contracting Officer to perform surveillance on the technical aspects of the contract and to act as liaison to the contractor, and the COR.

CPP-- Cost Performance Portal Defective Service-- A service output that does not meet the standard of performance associated with it in the Performance Work Statement.

CRRT-- CERP Review and Reporting Tool DASA-CE-- Deputy Assistant Secretary of the Army for Cost and Economics DoD-- Department of Defense ERP-- Enterprise Resource Planning FTP-- File transfer protocol GCSS-A-- Global Combat Support System – Army GFEBS-- General Fund Enterprise Business System HQDA-- Headquarters, Department of Army JTR-- Joint Travel Regulations LIF-- Logistics Intelligence File LIN-- Line Item Number LMP-- Logistics Modernization Program MAC-- Mission Assurance Category MACOM-- Major Army Command MDAP-- Major Defense Acquisition Program MOA-- Memorandum of agreement NIPERNET-- non-classified Internet Protocol Router NSN-- National Stock Number OCO-- Outside of the Continental United States Operations OCONUS-- Outside of the Continental United States OPTEMPO-- Operational tempo OSMIS-- Operating and Support Management Information System O&S-- Operating and Support OSD-- Office of the Secretary of Defense OWG-- OPTEMPO Working Group PCR-- Proposed Change Request POA&M—Plan of action & milestones POC-- Point of contact POM-- Program Objectives Memorandum PPBE-- Army Planning, Programming, Budget and Execution PRS-- Performance Requirement Summary PWS-- Performance Work Statement QASP-- Quality Assurance Surveillance Plan: An organized written document specifying the surveillance methodology to be used for surveillance of contractor performance.

QC-- Quality Control: Those actions taken by a contractor to control the performance of services so that they meet the requirements of the PWS.

QA-- Quality Assurance: Those actions taken by the government to assure services meet the requirements of the Performance Work Statement.

RMF-- Risk Management Framework SAMAS-- Structure and Manpower Allocation System SSF-- Single Stock Fund SIA-- Systems interface agreement TPSN-- Troop Program Sequence Number UIC-- Unit Identification Code ULLS_G-- Unit Level Logistic System Ground ULLS-- AVIATION/GROUND--Unit Level Logistics System WIC-- Weapon Identifier Code USSOCOM-- United States Special Operations Command V&V-- Verification and validation WIC-- Weapon identifier code

PART 3

GOVERNMENT FURNISHED PROPERTY, EQUIPMENT, AND SERVICES

3.1 GENERAL:

3.1.1. The Government may provide reasonable access to its facilities, key people, data, and documents in support of the project.

PART 4

CONTRACTOR FURNISHED ITEMS AND SERVICES

4.1 General: Except for those items specifically stated to be government furnished in Part 3, the contractor shall furnish everything required to perform this PWS.

4.2 Secret Facility Clearance: Secret Facility Clearance: The Contractor shall maintain a SECRET facility clearance from the Defense Security Service. Contractor's employees, performing work in support of this contract shall have been granted a SECRET security clearance from the Defense Industrial Security Clearance Office. The acquisition will require the contractor to comply with the requirements of the Contract Security Classification Specification (DD Form 254), which will be incorporated into the contract The contractor will be required to safeguard all data and equipment in its possession and report to the appropriate Government organization any incidents involving unauthorized access. The contractor shall comply with FAR Clause 52.204-2 Security Requirements.

PART 5

SPECIFIC TASKS

5.1 Data Collection Activities

5.1.1 Collect usage, demand, ammo, field and depot level maintenance, property book, force structure, pre-positioned stock, bills of materiel, fuel, weapon system specific details (e.g., LIN, NIIN, descriptions, basis of issue plan, component of major items, and associated support items of equipment and personnel), materiel master, personnel, accounts, project codes, rotational and deployment list of units, price and credit, software maintenance, training events and costs, simulator, crew, and CLS cost data.

5.1.2 Collect all relational data required for data mapping and processing.

5.1.3 Collect new data specified from development activities in a timely manner to support near-real time development.

5.1.4 Collect the appropriate parameters in all data that will enable the discernment between relevant analytical subsets (e.g., mission/training specific activities, dates, unit details, weapon system, location, and funding).

5.1.5 Update the data source POC list for the OSMIS database. Provide all SIA or MOA in final or in draft form. Determine data requests that need to be made and provide a draft of the request to DASA-CE. CDRL A001

5.1.6 Determine the status of any outstanding data requests. Keep DASA-CE informed of any problems in acquiring data and provide a Data Source Management Report, on an as-needed basis. Report all late or missing data request in the monthly progress report. CDRL A002

5.1.7 Contractor shall have an advanced understanding of Army enterprise ERP systems LMP/GFEBS/GCSS-A, AESIP, OSMIS, and Vantage. This understanding will be utilized to coordinate and formalize data collection tasks between OSMIS and the source system as well as to inform on potential duplication of data between the systems (e.g., AWCF vs sustainment).

5.1.8 Formally document all data collection activities. These documents should include source details, method of collection, dates data are collected, quality of collected data, definitions for each data field, size of data file, and purpose/use of data in OSMIS. The purpose/use documentation should include both functional descriptions and technical descriptions of the data integrated into OSMIS. CDRL A005

5.1.9 Conduct and automate data collection quality control processes to ensure required data are collected appropriately. Provide data collection quality control documentation, maintain and build upon a set of QA/QC queries to run against data to quickly identify and resolve anomalies, and associated metrics to personnel conducting other tasks on the collected data (e.g., record and compare counts and summations of total dollars and quantity measures with all other data activities) to ensure data validity and integrity throughout the collection (part 5.1), transformation (parts 5.2 and 5.3), publishing (part 5.4), and analytical processes (part 5.6). Provide documentation and metrics to government. CDRL A013.

5.2 Data Cleaning and Processing

5.2.1 Execute data cleaning and processing activities for data from all Army ERPs, Vantage, and other data sources as appropriate and/or as identified and approved by the government. These data will include usage, demand, ammo, field and depot level maintenance, property book, force structure, pre-positioned stock, bills of materiel, fuel, weapon system specific details (e.g., LIN, NIIN, descriptions, basis of issue plan, component of major items, and associated support items of equipment and personnel), materiel master, personnel, accounts, project codes, rotational and deployment list of units, price and credit, software maintenance, training events and costs, simulator, crew, CLS cost data, relational data required for mapping and processing purposes, newly collected data, and other relevant data (e.g., historical data) required.

5.2.2 Clean and process new data specified from development activities in a timely manner to support near-real time development.

5.2.3 Review, consolidate, and check the fidelity of ERP, Vantage, AESIP, and other source data collected and ensure accuracy and completeness for OSMIS and DASA-CE purposes and applications. Thoroughly test, validate, and verify collected data to ensure it is “fit for purpose”.

5.2.4 Identify and build Materiel Systems Definitions by Weapon Identifier Code (WIC)/Line Item Number (LIN)/National Stock Number (NSN) and add new weapons systems, as needed. Identify list of new possible adds to the OSMIS database, provide details on the level of OSMIS data fidelity for those NIINs over time (e.g., publishing cost factors for 10 years versus cost estimating relationship available versus complete bill of materiel), and provide list with those details to DASA-CE for review and acceptance. CDRL A003

5.2.5 Formally document all data cleaning and processing activities. These documents should include relevant details recorded in the data collection documentation, descriptions of cleaning and processing applied to the data (e.g., functional descriptions of the cleaning/processing script as well as the scripts themselves), time required to complete these processes, and traceability documentation for all cleaning and processing activities to exhibit how data are transformed for use in OSMIS (e.g., data lineage type of products in Vantage). CDRL A005

5.2.6 Conduct and automate data cleaning and processing quality control activities to ensure required data are cleaned and processed appropriately. Provide data cleaning and processing quality control documentation, maintain and build upon a set of QA/QC queries to run against data to quickly identify and resolve anomalies, and document and share associated metrics to personnel conducting other tasks on the cleaned/processed data (e.g., record and compare with all other data activities counts and summations of total dollars and quantity measures at different data levels like by weapon system, negative dollar values, suspicious demand changes without corresponding force structure nor activity changes) to ensure data validity and integrity throughout the collection (part 5.1), transformation (parts 5.2 and 5.3), publishing (part 5.4), and analytical processes (part 5.6). Provide documentation and metrics to government. CDRL A013.

5.3 Data Mapping and Transformation

5.3.1 Execute data mapping, allocations, and transformation activities using graph database functionality such as Neo4j for data from all Army ERPs, Vantage, and other data sources as appropriate and/or as identified and approved by the government. These data will include usage, demand, ammo, field and depot level maintenance, property book, force structure, pre-positioned stock, bills of materiel, fuel, weapon system specific details (e.g., LIN, NIIN, descriptions, basis of issue plan, component of major items, and associated support items of equipment and personnel), materiel master, personnel, accounts, project codes, rotational and deployment list of units, price and credit, software maintenance, training events and costs, simulator, crew, CLS cost data, relational data required for mapping and processing purposes, newly collected data, and other relevant data (e.g., historical data) required to support areas of interest in OSMIS and for DASA-CE. CDRL A006

5.3.2 Map and transform new data specified from development activities in support of near-real time development as directed by government.

5.3.3 Ensure that the mapped data enables analysts to subset and perform data summarization activities along relevant parameters such as weapon system, commodity group, unit level, part, supply class, location, and others as identified by government and policy.

5.3.4 Identify, review, develop mitigation strategies, and implement government approved solutions for allocation and mapping issues. Continue to improve methodologies for mapping data rules in response to changing policies, operational events, data sources, or data science as approved by government.

5.3.5 Review mapped data for completeness and accuracy to identify any errors or issues. Determine if there are redundant data being provided by any data feed and determine how to mitigate.

5.3.6 Develop the Monthly Army Performance Reviews each month. Adjust OPTEMPO calculations due to G3 revisions in business rules for standard exclusions, exemptions and exceptions categories as required. CDRL A008

5.3.7 Develop monthly activity management report that includes percent fleet reporting, miles/hours executed, and averages at Unit Identification Code (UIC), Troop Program Sequence Number (TPSN) and Major Army Command. (COCOM/MACOM) levels. Develop the Monthly Management Report for both air and ground systems for publication on the 20th of each month. CDRL A009

5.3.8 Support ad hoc queries that are not available in the relational database as required. Make methodology improvements for new initiatives as required.

5.3.9 Formally document all data mapping and transformation activities. These documents should include relevant details recorded in the prior data activity documentation (e.g., collection, cleaning, and processing reports/documentation), descriptions of mapping and transformation applied to the data (e.g., functional descriptions of the mapping/transformation script as well as the scripts themselves), time required to complete these processes, and traceability documentation for all mapping and transformation activities to exhibit how data are transformed for use in OSMIS (e.g., data lineage type of products in Vantage). CDRL A005

5.3.10 Conduct and automate data mapping and transformation quality control activities to ensure required data are mapped and transformed appropriately. Provide data mapping and transformation quality control documentation, maintain and build upon a set of QA/QC queries to run against data to quickly identify and resolve anomalies, and associated metrics to personnel conducting other tasks on the cleaned/processed/mapped/transformed data (e.g., record and compare counts and summations of total dollars and quantity measures with all other data activities) to ensure data validity and integrity throughout the collection (part 5.1), transformation (parts 5.2 and 5.3), publishing (part 5.4), and analytical processes (part 5.6). Provide documentation and metrics to government. CDRL A013.

5.4 Data Publishing and Help Desk

5.4.1 Execute data publishing activities for transformed (i.e., production database) usage, demand, ammo, field and depot level maintenance, property book, force structure, pre-positioned stock, bills of materiel, fuel, weapon system specific details (e.g., LIN, NIIN, descriptions, basis of issue plan, component of major items, and associated support items of equipment and personnel), materiel master, personnel, accounts, project codes, rotational and deployment list of units, price and credit, software maintenance, training events and costs, simulator, crew, CLS cost data, relational data required for mapping and processing purposes, newly collected data, and other relevant data (e.g., historical data) required to support areas of interest in OSMIS and for DASA-CE on the site in the appropriate format for visualization and data sharing. These publications must be made in a timely fashion in support of the development efforts in improving near real-time data reporting. At a minimum, publish the annual relational database no later than the last week in April unless conditions require a delay and the delay has been approved by DASA-CE. Publish monthly data no later than one month after the data are collected, processed, and transformed. As progress is made towards near real-time data reporting capabilities, publish relational database according to those design changes. CDRL A006

5.4.2 Publish Monthly Army Performance Reviews each month. CDRL A008

5.4.3 Publish monthly activity management report that includes percent fleet reporting, miles/hours executed, and averages at Unit Identification Code (UIC), Troop Program Sequence Number (TPSN) and Major Army Command. (COCOM/MACOM) levels. CDRL A009

5.4.4 Provide data files to those government organizations that coordinate with DASA-CE via policy and/or agreements, both current (e.g., sustainment health metrics, readiness data to HQDA G3, CONOPS data to OSD) and future according to the scheduled date (e.g., monthly, quarterly, or annually).

5.4.5 Perform maintenance and updates to the OSMIS websites to ensure complete and accurate results and functionality for users and according to government requirements in a timely manner.

5.4.6 Maintain and update OSMIS common landing page as defined by government.

5.4.7 Provide OSMIS relational database user support and training.

5.4.8 Contractor shall be responsible for managing, monitoring, addressing, and reporting help desk requests.

5.4.9 Formally document all data publishing and help desk activities. These documents should include relevant details recorded in the prior data activity documentation (e.g., collection, cleaning, and processing reports/documentation), descriptions of published data (e.g., functional descriptions of the publishing/aggregation scripts as well as the scripts themselves), time required to complete these processes, and traceability documentation for all data publishing/aggregation activities to exhibit how data are transformed for use in OSMIS (e.g., data lineage type of products in Vantage). This product will also include descriptions of the fields and relationships among the data contained in the historical database published for OSMIS user community, cost factor databases, and all other published data collections. CDRL A005

5.4.10 Conduct and automate data publishing quality control activities to ensure all published data are appropriate. Provide data publishing quality control documentation, maintain and build upon a set of QA/QC queries to run against data to quickly identify and resolve anomalies, and associated metrics to personnel conducting other tasks on the cleaned/processed/mapped/transformed data (e.g., record and compare counts and summations of total dollars and quantity measures with all other data activities) to ensure data validity and integrity throughout the collection (part 5.1), transformation (parts 5.2 and 5.3), publishing (part 5.4), and analytical processes (part 5.6). Provide documentation and metrics to government. CDRL A013.

5.5 Database and System Administration, Maintenance, and Monitoring

5.5.1 Contractor has the overall responsibility for maintaining computer systems, databases, and software for OSMIS requirements to include maintaining the source data as received, making multiple backups of the source data, keeping abreast of new software to enhance system performance, and maintaining and updating the historical database. Modify computer code to reflect changing Army business practices, policy, and initiatives. Perform maintenance as required to maintain customer access to the OSMIS relational database. CDRL A004.

5.5.2 Ensure the government purchases the appropriate license requirements (i.e., number and type by personnel and function).

5.5.3 Provide support to CAVE database and system administration, maintenance, and monitoring activities as appropriate for OSMIS requirements.

5.5.4 Upon specific request and prioritization, research and fully utilize Army and DoD DaaS and Analytical platforms (e.g. Vantage and ADVANA) to improve data sourcing, transformation, modeling and analysis processes of DASA-CE’s cost estimation and analysis applications. The functionality of these platforms should be fully leveraged to reduce (1) the current on-premises computing infrastructure/ data storage requirements, (2) software licenses, and (3) labor associated the development and sustainment of OSMIS.

5.5.5 Formally document all database and system administration, maintenance, and monitoring. These documents should include relevant details recorded in the data activity documentation (e.g., collection, cleaning, and processing reports/documentation), descriptions of databases, systems, maintenance, and monitoring activities (e.g., functional descriptions of all scripts as well as the scripts themselves), time required to complete these processes, and traceability documentation for all of these activities to exhibit the architecture and relationships among the system of the systems. CDRL A005

5.6 OSMIS Analytical Design and Support

5.6.1 Execute OSMIS analytical design and support activities for data from all Army ERPs, Vantage, and other data sources as appropriate and/or as identified and approved by the government.

5.6.2 Contractor will identify, document, and review OSMIS business and data cleaning rules, allocation methodologies, and the scope of data collection instantiated in the system. Contractor will provide recommended updates to those rules, methodologies, and scope to government for approval and then implement them in the system. Contractor will propose and implement government approved methods to automate the application of and future updates to those rules, methodologies, and scope. Contractor will include cloud technology considerations for updating these rules and the implementation. Contractor will review and implement government approved methods for handling data issues applied in industry, academics, and other communities.

5.6.3 Based upon changes in maintenance policy, formulate recommended business and data processing rules and methodologies for review and approval of government, and evaluate and report the impacts resulting from the implementation of those rules. In particular, perform this task in support of cost factor development activities and other major DASA-CE priorities. Identify new data parameters and data sources that may be integrated into government-led analysis to broaden analytical applications of OSMIS data and functionality. Make methodology improvements for new initiatives as required.

5.6.4 Provide subject matter expertise in the logistics, financial, operational, statistical, Vantage, OSMIS, and Army ERP areas to include how the ERPs relate to one another in support of all OSMIS design, development, maintenance, and application activities to include support in ad-hoc studies and HQDA meetings.

5.6.5 Develop POM, BES, Presidents Budget, and Year of Execution (YoE) Cost Factors as required by AO2G. Develop Class IX, III, II, and IV cost factors for each cost factor event as directed by government. Develop additional cost factors (depending upon AO2G guidance); e.g., BES, CONOPS, Exchange Pricing, funding letter, or any other special event. Identify top cost driver parts for pricing and provide the associated data files as directed by government. Develop cost factors using government approved predictive analytics methodology. Utilize failure factors to develop engineered cost factors for system with insufficient data availability or cost estimates when no other data are available. Provide support in developing or updating current published Army Cost Position, Engineered Estimates, or CLS cost factors for Army weapon systems. CDRL A007

5.6.6 Develop USSOCOM flying hour cost factors using SOF unique aspects of the flying hour program for the POM, BES, and Presidents Budget events. Participate in annual meeting to discuss and review current methodology and review end of year reporting requirements and timelines. CDRL A007

5.6.7 Provide cost factors and support for other government deliverables and activities (e.g., IDA, sustainment health metrics, and Operating & Support sustainment reviews). CDRL A007

5.6.8 Provide additional cost factor data in support of the entire OPTEMPO funding process such as annualized demand data, coordinating/ adjust schedules, and other deliverables as required.

5.6.9 Provide pre-POM support and support DASA-CE on any Army Working Capital Fund (AWCF) Operations Oversight Group (AO2G) issues as required. Provide POM, BES, Presidents Budget, and execution analytical support as required. Respond to cost factor issues raised by the COCOMs or AO2G as required.

5.6.10 With government guidance and approval, identify, recommend, design, and implement predictive analytics methods and supporting statistical analysis techniques for the development and analysis of cost factors estimates and other government-led studies.

5.6.11 Contractor shall support the government-led review of the Army Operating and Support Management Information System (OSMIS) and methods for tracking and assessing O&S costs for MDAPs.

5.6.12 Contractor shall document the salient characteristics of systems and methods used by major subordinate commands for tracking and assessing O&S costs for MDAPs during formulation of command operating budgets and subsequent budget execution.

5.6.13 Contractor shall provide a description of system and methods used to develop budgets and programs for MDAPs at the headquarters level. For example, what reviews are held? When are these reviews held? How are the results from these reviews considered in the development of budgets and programs? Contractor description shall include supporting data systems and the process by which data is fed into the headquarters.

5.6.14 Contractor shall provide a description of the system(s) and methods used to assess O&S costs in decision reviews at Milestones A, B, and C in the Army and in the Office, of the Secretary of Defense. This effort will include an examination of the degree to which O&S costs are assessed in the conduct of Analyses of Alternatives.

5.6.15 Contractor shall demonstrate successful experience in developing solutions to analyze enterprise data at the scale of OSMIS while meeting timelines for the POM process.

5.6.16 Formally document all cost factor related activities. These documents should include relevant details recorded in the prior data activity documentation (e.g., collection, cleaning, and processing reports/documentation), descriptions of published data (e.g., functional descriptions of the publishing/aggregation scripts as well as the scripts themselves), time required to complete these processes, and traceability documentation for all cost factor development activities to exhibit how data are transformed for use in cost factors (e.g., data lineage type of products in Vantage). This product will also include descriptions of the fields and relationships among the data contained in the cost factor database. CDRL A005

5.6.17 Conduct and automate cost factor quality control activities to ensure all data are appropriate. Provide cost factor quality control documentation, maintain and build upon a set of QA/QC queries to run against data to quickly identify and resolve anomalies, and associated metrics to personnel conducting other tasks on the cleaned/processed/mapped/transformed data (e.g., record and compare counts and summations of total dollars and quantity measures with all other data activities) to ensure data validity and integrity throughout the collection (part 5.1), transformation (parts 5.2 and 5.3), publishing (part 5.4), and analytical processes (part 5.6). Provide documentation and metrics to government. CDRL A013.

5.7 Risk Management Framework (RMF)

5.7.1 Overall responsibility for maintaining OSMIS computer systems and ensuring non-classified Internet Protocol Router (NIPERNET) connectivity in accordance with DoD specifications and accreditations. Maintain RMF certification and documentation for OSMIS at a MAC Level [ II ] and a Confidentiality Level of [ CL ] Unclassified, Sensitive in support of CAVE RMF activities.

5.7.2 Collect, review, update, and upload artifacts into eMass. Identify, collect, manage, populate, and V&V information required for eMass in support of CAVE RMF activities.

5.7.3 Contractor will support CAVE RMF activities and execute monthly monitoring activities.

5.7.4 Contractor shall support CAVE RMF activities to maintain and update POA&M. Identify and collect information required for POA&M. Provide monthly review of the POA&M with new and/or updated artifacts loaded at the CCI level to government. Provide monthly status updates, progress reports, and mitigation plans to the government.

5.7.5 Plan, coordinate, execute, and document scans and other RMF related activities in support of CAVE RMF activities.

5.7.6 Plan, coordinate, schedule, execute, and document required meetings with relevant parties in order to collect and update RMF documentation and the eMass system in support of CAVE RMF activities.

5.7.7 Identify, develop, and provide all required memos and other associated documentation required for the entire RMF process in support of CAVE RMF activities.

5.7.8 Identify, plan, coordinate, execute, and document tasks, roles and responsibilities, and deliverables required for the sustainment of RMF in support of CAVE RMF activities.

5.8 Project Management, Reporting, and Communications

5.8.1 Upon request, contractor will provide technical computer system, server, and website details. Contractor will provide data and reports as specified by government.

5.8.2 Contractor will identify and assign the appropriate subject matter expert to attend HQDA workgroups and provide assistance for DASA-CE areas of responsibility.

5.8.3 Contractor will plan, coordinate, and execute appropriate meeting updates with government on a regular basis to inform on any issues, progress, and requested support.

5.8.4 Contractor shall provide a detailed monthly cost report in EXCEL spreadsheet which outlines the monthly hours and costs expended by labor category. Hours and costs should align with project tasks accomplished in the month. Report shall be delivered to DASA-CE on the 20th of each month. CDRL A011

5.8.5 Contractor shall provide monthly progress updates to government that describe the ongoing, completed, and planned tasks and the associated progress. CDRL A010

5.9 OSMIS Development– OPTIONAL TASK CLIN

5.9.1 Design, develop, test, and with government approval, integrate development capabilities into OSMIS.

5.9.2 Identify new and current automation and cloud technologies, develop a plan to integrate these technologies, present the plan to government for approval, and integrate these automation and cloud technologies into all applicable processes for OSMIS, cost factors, and other DASA-CE cost data reporting.

5.9.3 Design, develop, test, and integrate appropriate procedures and processes required to publish near-real time OSMIS data to users. Execute these processes to move from annual cost data reporting to quarterly within 2 years and then at the monthly level in the following two years. Develop plans to process and publish data based on event versus time-based (i.e., process and publish when transactional data are updated in OSMIS source data). CDRL A006

5.9.4 Design, develop, test, and integrate appropriate procedures, processes, and applications to allow direct access to the OSMIS data lake (i.e., raw and all curated data collections) for internal DASA-CE analysts without the standard developer requirements for that access (e.g., no security plus certification requirement for internal DASA-CE analysts).

5.9.5 Research all Army cost element structure data gaps within OSMIS, identify appropriate data to mitigate those gaps, and develop, test, and integrate those data into OSMIS from data collection through data publishing and analytics processes and products upon approval of government.

5.9.6 Research additional fields/levels of data that will support new areas of DASA-CE cost data analytics (e.g., maintenance significant part, bench stock, shop stock, demands at logistics readiness centers, AWCF sales, common authorized stockage lists, basis of issue plan, component of major items, associated support items of equipment and personnel, major units, categories for other unit related types, supersession NIINs, current/near-real time property book at the equipment number level, logistics readiness center data, CL III package product demands, interchangeable parts, purchase order record details, work order record details, GFEBS financial details, credit at transaction level, and rotational unit data).

5.9.7 Finalize the development of the ‘NIIN fits-on NIIN’ query capability for OSMIS user community and publish for use.

5.9.8 Research, design, develop and integrate aviation and ground ‘NIIN fits-on NIIN’ efforts into all OSMIS data processes.

5.9.9 Research and integrate total overall asset inventory categories specified in the sustainment health metrics requirement across all of OSMIS.

5.9.10 Identify and reduce complexities, identify tasks that may be automated and automate, and improve each OSMIS function as appropriate to enable future development in the continuously changing data and technology environments.

5.9.11 Data Collection Development.

5.9.11..1 Work with data sources to provide the most economical, efficient, and fully-automated transfer of data. Application programming interface (API) transfer of data would be preferable. Gain access to databases where automated procedures can be developed to pull data according to a designed schedule, test, and formalize the procedures. Improve data collection activities to ensure optimal performance of OSMIS.

5.9.11..2 Expand the depth and breadth of all data areas normally collected by OSMIS by researching, identifying, testing, and collecting available datasets, additional fields, and other meta data to improve DASA-CE cost data collections. Identify new data sources or agencies that need to provide single or multiple data sources to OSMIS (e.g. Vantage, GCSS-A, GFEBS, LMP, and AESIP). Continue to improve OSMIS by adding new data sources and provide updates to government and documentation for all newly added data sources and the associated data collection details. Identify new and current parameters in all data that will enable the discernment between relevant analytical subsets (e.g., mission/training specific activities, dates, unit details, weapon system, location, and funding).

5.9.12 Data Publishing and Help Desk Development.

5.9.12..1 Contractor will research, recommend, and implement government approved design features of the OSMIS site. These designs will include considerations for how to present both near real-time data and fully processed, reviewed, and verified data in a format that is transparent by OSMIS users. Contractor will research, integrate, and update government approved data visualization and analytic capabilities on the OSMIS site. Contractor will research, integrate, and update data file sharing functionality that will enable larger and larger data downloads from the OSMIS site.

5.9.12..2 Design, develop, test, and publish OSMIS users’ statistics as specified by government.

5.9.12..3 Publish other OSMIS data such as CLII and CLIV demands, current monthly materiel master, newly added parameters/metadata/fields, current property book, and fleet reporting metrics.

5.9.12..4 Adjudicate cost data reporting issues in OSMIS related to NIINs not having pricing data in user selected pricing file using the cost factor business rules to update most recent pricing values using the joint inflation calculator to the user selected year.

5.9.12..5 Design, develop, test, and publish OSMIS user support capabilities (e.g., chat bot for questions and searches).

5.9.13 OSMIS Analytical Design and Support Development.

5.9.13..1 Integrate all business rules, cost factors, and cost factor data into a single data lake and provide access via appropriate applications to internal DASA-CE analysts without normal developer certification requirements.

5.9.13..2 Contractor will provide support to government-led studies and analysis efforts.

5.10 Army Budget Office Support – OPTIONAL TASK CLIN

5.10.1 Conduct ad hoc reporting, special studies, and data analytics as directed by DASA-BU using data from AESIP Hub, GCSS-Army, LMP and other logistics and financial data sources as appropriate and/or as identified and approved by the government.

5.10.2 Integrate data across systems in order to merge logistics, financial, and policy information into coherent, functionally correct data displays and reports to be used in the daily business management operations of the ASA (FM&C).

5.10.3 Provide Quarterly Reports in support of Supply Operations and Support Management Information System. Contractor will provide SFDLR Quarterly Reports, SFDLR Quarterly Average Reports, and Annual Serviceable/Unserviceable Return Percentage Reports.

5.10.4 Provide Supply Operations and Management Monthly Project Progress Report by the 15th of each month. CDRL A012

5.11…