TRD_A1.pdf

Rev G

FA9200-05-C-0001, P00057

Attachment 3

Page A1-1

APPENDIX A1

TEST WING ENTERPRISE SYSTEM (TWES) SUPPORT

1.0 PURPOSE.

2.0

The purpose of TWES Support is to manage and maintain information in databases used to generate data products, including Job Order Cost Accounting System (JOCAS) entries for billing customers, range utilization information, and charts, reports, spreadsheets, and presentations.

2.1. The TWES is a dynamic computer-based system that resides on a local area network. The database is managed by Microsoft SQL Server. This system provides on-line access to near-real-time data used to make critical day-to-day management decisions pertaining to the Eglin Range O&M Contract and other 46

GENERAL.

th

2.2. TWES support develops and maintains Visual Basic and web-based software applications. The application development effort spans the complete life cycle process for software development. These applications provide tools for researching and analyzing information.

Test Wing (TWES) resources. The TWES is located in Building 955.

2.3. TWES support consists of software developers/systems analysts and database management personnel that provide services required by the Government. Data obtained from PWS-required reports and other data sources are input into various databases using electronic transfer and/or manual entry. Standardized reports, charts, workbooks, and presentations are produced. Product frequency and distribution are prescribed by the Government. In addition to the standardized reports, special requests for information from the database are made as required. These special requests are satisfied in three basic ways: (1) execute existing stored procedures or queries, (2) develop specific software for reorganization of the computerized data elements, and (3) compile data from existing reports into an Excel workbook or PowerPoint presentation.

3.0

3.1. The Contractor shall provide TWES software development and maintenance support, including:

CAPABILITIES.

3.1.1. Software and systems analysis and process reengineering for Contractor-managed information technology (IT) components, including:

1. Performing needs analyses to define opportunities for new or improved business processes.

2. Identifying and specifying requirements for IT architecture.

3. Providing analyses of information technologies, architecture, and standards.

4. Conducting feasibility studies and trade-off analyses.

5. Preparing business cases, cost estimates, systems scope, and objectives.

Page A1-2

6. Developing overall functional and technical requirements and specifications.

7. Integrating systems and components, including procedures, databases, policies, software, and hardware.

8. Planning implementation.

9. Ensuring the rigorous application of information security/information assurance policies, principles, and practices within the TWES.

10. Providing customer interface support, including formal and informal training.

11. Applying knowledge of systems development life cycle management concepts.

12. Providing expertise in interfacing to the Job Order Cost Accounting System and related accounting systems.

13. Providing expertise on Eglin range resources and the Eglin mission scheduling process and software.

14. Briefing visiting military and civilian personnel as required.

3.1.2. Development and maintenance of software applications managed by the Contractor. The Contractor shall design and develop new applications for maintaining data and providing user interfaces. These interfaces will be specified by the Government and include data management functions, reports, charts, and other outputs. Software development involves applications and tools provided by the Government, including.

1. Microsoft SQL Server,

2. Oracle Database Management System

3. Microsoft Access.

4. Microsoft Excel,

5. Visual Basic

6. .Net Framework.

7. Web-based applications.

3.1.3. Development and maintenance of complex software applications involving a broad range of data, including financial management, logistics, resource scheduling and utilization, mission information, mission effectiveness, aircraft flying hours, flight/ground profiles, and other data as specified by the Government.

3.2. The Contractor shall provide TWES operations support. Typical support actions are to:

3.2.1. Provide accurate instrumentation utilization and cost data into the database and ensure availability for on-line display by noon the third workday following the event.

3.2.2. Review Post Mission Reports (formerly known as AAC Forms 57), submitted by the Government, for accuracy and crosscheck the reports with the mission request. The Contractor shall resolve conflicting data to the Government's satisfaction before final entry into the database. This includes off-station as well as local missions. The Contractor shall ensure this data is available for on-line display by 0730 on the second workday after the mission day or the most recent revision day.

Page A1-3

3.2.3. Prepare cost entries for input into the Job Order Cost Accounting System (JOCAS) for supply expenditures, man-hour expenses, temporary duty (TDY) expenses, chargeable product code units, other-than-labor-and-material expenses, and AAC aircraft product code (ground/flying) units. Mission scheduling product code units and cost entries are electronically transferred to the JOCAS, and reports are sent electronically biweekly and monthly.

3.2.4. Review the Aerospace Usage Data, submitted by the Government in electronic format, for accuracy. The Contractor shall upload this data into the database for on-line display by 0730 on the second workday following the event.

3.2.5. Collect, verify and enter into the database AAC aircraft ground usage, mission hours, blackboard mission request data, equipment utilization, and equipment unavailability. This data shall be entered into the database daily.

3.2.6. Maintain the master facility title/facility number/supply location code table for validating all contract expenditures. The Government will task changes to this table.

3.2.7. Maintain mission information by daily electronic transfer of mission scheduling data into the historical database. The Contractor shall update mission information to reflect all changes made after the AAC Daily Operations Order is published. The number of changes varies each day due to various factors. The Contractor shall code each non-scheduled mission to reflect the reason for being non-scheduled. The Contractor shall compare all mission information forms with actual aircraft status to ensure correct aircraft tail number and appropriate mission disposition entries are made in the database. The Contractor shall file and maintain each mission request form with the corresponding Post Mission Report.

3.2.8. Maintain the master range resource table used by the Eglin Center Scheduling Enterprise (CSE) system. The Contractor shall coordinate changes and additions to the table with appropriate organizations (Appendix B6).

3.2.9. Maintain the equipment availability data table to support the CSE on a daily basis.

The Contractor shall periodically review and update resource characteristics, including resource turn times, resource availability, and resource codes. The Contractor shall coordinate changes or additions to the database with appropriate organizations.

3.2.10. The Contractor shall support the Earned Value Cost Analysis System by electronically transferring base-lined work breakdown structure (WBS) codes to the CSE and JOCAS. The Contractor shall also create and maintain the JOCAS rate file for conversion to the EVCAS rate file structure.

3.2.11. Provide all flight, ground, and safety profiles in digital format into the CSE. The Contractor shall update the digital profile form once the Profile Standardization Board has approved a profile and annotated changes. The Contractor shall verify the changes.

Once changes have been verified, the profile is approved for scheduling in the profile system. The Contractor shall distribute the approved profile as directed by the Government. The Contractor shall maintain a hard copy of all approved profiles for

Page A1-4 review. The Contractor shall delete profiles from the profile system and destroy hard copies only IAW procedures established by the Government.

3.2.12. The Contractor shall enter programmed maintenance actions into the CSE. The Contractor shall coordinate programmed maintenance actions with appropriate organizations. (Appendix A3)

3.2.13. The Contractor shall enter actual employee billing expense data, task costs (other than labor and material data), and obligated task costs (other than labor and material data) into the database monthly via electronic transfer. The Contractor shall enter supply expenditure and due-ins and man-hour data into the database daily. These data shall be available for on-line display by noon on the second workday after either the event or the most recent revision day. The Contractor shall resolve errors found in the actual employee billing expenses and in task costs (other than labor data) to the Government's satisfaction.

3.3. The Contractor shall perform TWES queries and produce data products, including:

3.3.1. Standard reports, charts, and presentations produced on a weekly, bimonthly, monthly, quarterly, semi-annual, and/or annual basis (approximately 60 per month).

Detail and summary management reports and charts reflecting facility costs, facility earnings, and equipment utilization are produced monthly.

3.3.2. Specialized reports, charts, and presentations developed throughout the fiscal year (approximately 6 per month) to support studies and other management concerns. Special reports, charts, and presentations are produced from the database, as tasked by the Government. Requirements may include reports that are readily available from the on-line system, or may require manual extraction of information from reports or research from other sources of information. The Contractor shall complete these reports in a timely manner.

3.3.3. Reports required to maintain Product and Service Codes and corresponding rates to support the financial aspect of the range.

3.4. The Contractor shall distribute all pertinent reports, charts, and presentations to the requestor, or as directed by the Government.

3.5. The Contractor shall ensure continuity of the TWES database, including:

3.5.1. Ensuring accuracy and accessibility of historical information including any legacy databases or systems.

3.5.2. Retaining all source data and computerized historical data for a period of five years after the close of the fiscal year to which they pertain.

3.1.3. Development and maintenance of complex software applications involving a broad range of data, including financial management, logistics, resource scheduling and utilization, mission information, mission effectiveness, aircraft flying hours, flight/g�